You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "John Liptak (Created) (JIRA)" <ji...@apache.org> on 2012/03/19 17:46:40 UTC
[jira] [Created] (AMQ-3773)
org.apache.activemq.ra.ActiveMQEndpointWorker run should not be
synchronized
org.apache.activemq.ra.ActiveMQEndpointWorker run should not be synchronized
----------------------------------------------------------------------------
Key: AMQ-3773
URL: https://issues.apache.org/jira/browse/AMQ-3773
Project: ActiveMQ
Issue Type: Bug
Components: JCA Container
Environment: JBoss AS 7.1
Reporter: John Liptak
from http://activemq.2283324.n4.nabble.com/ActiveMQEndpointWorker-run-method-cannot-be-synchronized-td4330542.html
There has been a discussion on the JBoss 7 forums about errors getting the ActiveMQ resource adapter working correctly in JBoss (see https://community.jboss.org/message/648857)
When JBoss attempts to deploy the rar file, it was throwing this error:
ERROR [org.apache.activemq.ra.ActiveMQEndpointWorker] (MSC service thread 1-4) Work Manager did not
accept work: : javax.resource.spi.work.WorkException: IJ000257:
org.apache.activemq.ra.ActiveMQEndpointWorker$1: Run method is synchronized
One member on the forum modified the source code for org.apache.activemq.ra.ActiveMQEndpointWorker and took out the "synchronized" keyword from the "run" method (line 97), and this fixed the problem. I modified the code as well and it fixed my problem too. According to a JBoss representative, ActiveMQ is out of spec on this, and claims that this should be fixed on the ActiveMQ side.
Please consider modifying this class. Otherwise, nobody will be able to use the resource adapter with JBoss.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (AMQ-3773)
org.apache.activemq.ra.ActiveMQEndpointWorker run should not be
synchronized
Posted by "John Liptak (Closed) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQ-3773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
John Liptak closed AMQ-3773.
----------------------------
Resolution: Duplicate
https://issues.apache.org/jira/browse/AMQ-3748
> org.apache.activemq.ra.ActiveMQEndpointWorker run should not be synchronized
> ----------------------------------------------------------------------------
>
> Key: AMQ-3773
> URL: https://issues.apache.org/jira/browse/AMQ-3773
> Project: ActiveMQ
> Issue Type: Bug
> Components: JCA Container
> Environment: JBoss AS 7.1
> Reporter: John Liptak
> Labels: jboss, jca, resource
>
> from http://activemq.2283324.n4.nabble.com/ActiveMQEndpointWorker-run-method-cannot-be-synchronized-td4330542.html
> There has been a discussion on the JBoss 7 forums about errors getting the ActiveMQ resource adapter working correctly in JBoss (see https://community.jboss.org/message/648857)
> When JBoss attempts to deploy the rar file, it was throwing this error:
> ERROR [org.apache.activemq.ra.ActiveMQEndpointWorker] (MSC service thread 1-4) Work Manager did not
> accept work: : javax.resource.spi.work.WorkException: IJ000257:
> org.apache.activemq.ra.ActiveMQEndpointWorker$1: Run method is synchronized
> One member on the forum modified the source code for org.apache.activemq.ra.ActiveMQEndpointWorker and took out the "synchronized" keyword from the "run" method (line 97), and this fixed the problem. I modified the code as well and it fixed my problem too. According to a JBoss representative, ActiveMQ is out of spec on this, and claims that this should be fixed on the ActiveMQ side.
> Please consider modifying this class. Otherwise, nobody will be able to use the resource adapter with JBoss.
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (AMQ-3773)
org.apache.activemq.ra.ActiveMQEndpointWorker run should not be
synchronized
Posted by "John Liptak (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQ-3773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
John Liptak updated AMQ-3773:
-----------------------------
duplicate of https://issues.apache.org/jira/browse/AMQ-3748, sorry.
> org.apache.activemq.ra.ActiveMQEndpointWorker run should not be synchronized
> ----------------------------------------------------------------------------
>
> Key: AMQ-3773
> URL: https://issues.apache.org/jira/browse/AMQ-3773
> Project: ActiveMQ
> Issue Type: Bug
> Components: JCA Container
> Environment: JBoss AS 7.1
> Reporter: John Liptak
> Labels: jboss, jca, resource
>
> from http://activemq.2283324.n4.nabble.com/ActiveMQEndpointWorker-run-method-cannot-be-synchronized-td4330542.html
> There has been a discussion on the JBoss 7 forums about errors getting the ActiveMQ resource adapter working correctly in JBoss (see https://community.jboss.org/message/648857)
> When JBoss attempts to deploy the rar file, it was throwing this error:
> ERROR [org.apache.activemq.ra.ActiveMQEndpointWorker] (MSC service thread 1-4) Work Manager did not
> accept work: : javax.resource.spi.work.WorkException: IJ000257:
> org.apache.activemq.ra.ActiveMQEndpointWorker$1: Run method is synchronized
> One member on the forum modified the source code for org.apache.activemq.ra.ActiveMQEndpointWorker and took out the "synchronized" keyword from the "run" method (line 97), and this fixed the problem. I modified the code as well and it fixed my problem too. According to a JBoss representative, ActiveMQ is out of spec on this, and claims that this should be fixed on the ActiveMQ side.
> Please consider modifying this class. Otherwise, nobody will be able to use the resource adapter with JBoss.
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira