Anonymous | Login | Signup for a new account | 12-17-2024 08:43 PST |
Main | My View | View Issues | Change Log | Docs |
Viewing Issue Simple Details [ Jump to Notes ] | [ View Advanced ] [ Issue History ] [ Print ] | ||||||||
ID | Category | Severity | Reproducibility | Date Submitted | Last Update | ||||
0004441 | [Resin] | major | always | 03-18-11 14:21 | 07-25-11 14:13 | ||||
Reporter | cdan | View Status | public | ||||||
Assigned To | ferg | ||||||||
Priority | normal | Resolution | fixed | ||||||
Status | closed | Product Version | 4.0.16 | ||||||
Summary | 0004441: Can't enlist transaction ActiveMQ Exception | ||||||||
Description |
We are still able to reproduce the issue reported in 0004327 even with 4.0.16. [15:20:31.908] {main} Failed to enlist resource ManagedPoolItem[connectionFactory,2,ActiveMQManagedConnection] in transaction because of exception: javax.transaction.xa.XAException javax.transaction.xa.XAException at org.apache.activemq.TransactionContext.start(TransactionContext.java:312) at org.apache.activemq.ra.LocalAndXATransaction.start(LocalAndXATransaction.java:136) at com.caucho.env.dbpool.ManagedPoolItem.start(ManagedPoolItem.java:759) at com.caucho.transaction.TransactionImpl.enlistResource(TransactionImpl.java:378) at com.caucho.transaction.UserTransactionImpl.begin(UserTransactionImpl.java:259) at com.caucho.transaction.UserTransactionProxy.begin(UserTransactionProxy.java:142) at com.caucho.ejb.util.XAManager.beginRequired(XAManager.java:162) at com.my.cvs.repository.controller.LookupMDBeanForCollectors__MessageProxy.setMessageDrivenContext(LookupMDBeanForCollectors__MessageProxy.java:171) at com.caucho.ejb.message.MessageManager.createMessageListener(MessageManager.java:336) at com.caucho.ejb.message.MessageManager.createEndpoint(MessageManager.java:290) at com.caucho.ejb.message.MessageManager.createEndpoint(MessageManager.java:280) at com.caucho.ejb.message.JmsResourceAdapter$Consumer.<init>(JmsResourceAdapter.java:345) at com.caucho.ejb.message.JmsResourceAdapter.endpointActivation(JmsResourceAdapter.java:261) at com.caucho.ejb.message.MessageManager.start(MessageManager.java:249) at com.caucho.ejb.manager.EjbManager.start(EjbManager.java:596) at com.caucho.ejb.manager.EjbManager.environmentStart(EjbManager.java:670) at com.caucho.loader.EnvironmentClassLoader.startListeners(EnvironmentClassLoader.java:904) at com.caucho.loader.EnvironmentClassLoader.start(EnvironmentClassLoader.java:888) at com.caucho.server.webapp.WebApp.start(WebApp.java:3109) at com.caucho.env.deploy.DeployController.startImpl(DeployController.java:630) at com.caucho.env.deploy.StartAutoRedeployAutoStrategy.startOnInit(StartAutoRedeployAutoStrategy.java:77) at com.caucho.env.deploy.DeployController.startOnInit(DeployController.java:493) at com.caucho.env.deploy.DeployContainer.start(DeployContainer.java:171) at com.caucho.server.webapp.WebAppContainer.start(WebAppContainer.java:713) at com.caucho.server.host.Host.start(Host.java:676) at com.caucho.env.deploy.DeployController.startImpl(DeployController.java:630) at com.caucho.env.deploy.StartAutoRedeployAutoStrategy.startOnInit(StartAutoRedeployAutoStrategy.java:77) at com.caucho.env.deploy.DeployController.startOnInit(DeployController.java:493) at com.caucho.env.deploy.DeployContainer.start(DeployContainer.java:171) at com.caucho.server.host.HostContainer.start(HostContainer.java:542) at com.caucho.server.cluster.Server.start(Server.java:1225) at com.caucho.server.cluster.ServletService.start(ServletService.java:72) at com.caucho.env.service.ResinSystem.startServices(ResinSystem.java:508) at com.caucho.env.service.ResinSystem.start(ResinSystem.java:476) at com.caucho.server.resin.Resin.start(Resin.java:892) at com.caucho.server.resin.Resin.initMain(Resin.java:1020) at com.caucho.server.resin.Resin.main(Resin.java:1297) |
||||||||
Additional Information |
http://bugs.caucho.com/view.php?id=4327 [^] |
||||||||
Attached Files | |||||||||
|
Notes | |
(0005179) ferg 04-07-11 09:55 |
How is your ActiveMQ and message bean configured in Resin? |
(0005180) cdan 04-07-11 10:01 |
Hello, My resin-web.xml is like this: <web-app xmlns="http://caucho.com/ns/resin" [^] xmlns:resin="http://caucho.com/ns/resin/core"> [^] <connection-factory class="org.apache.activemq.ra.ActiveMQManagedConnectionFactory" name="connectionFactory"> <resource-adapter class="org.apache.activemq.ra.ActiveMQResourceAdapter"> <init server-url="tcp://localhost:61616?wireFormat.maxInactivityDuration=0"/> [^] </resource-adapter> </connection-factory> <jms-queue name="CollectorQueue" class="org.apache.activemq.command.ActiveMQQueue"> <init physicalName="CVS.COLLECTORS"/> </jms-queue> <ejb-message-bean class="com.test.cvs.repository.controller.LookupMDBeanForCollectors" message-consumer-max="5"> <destination>#{CollectorQueue}</destination> </ejb-message-bean> <resource jndi-name="CVS.COLLECTORS" name="request" type="org.apache.activemq.command.ActiveMQQueue"> <init physicalName="CVS.COLLECTORS"/> </resource> </web-app> |
(0005183) ferg 04-07-11 13:37 |
Thanks. As a workaround, you can use the non-JCA ActiveMQ ConnectionFactory and Queue. Something like: <web-app ... xmlns:amq="urn:java:org.apache.activemq" xmlns:amqc="urn:java:org.apache.activemq.command" xmlns:ee="urn:java:ee"> ... <amq:ActiveMQXAConnectionFactory> <brokerURL>tcp://...</brokerURL> [^] </amq:ActiveMQXAConnectionFactory> <amqc:ActiveMQQueue ee:Named="CollectorQueue"> <physicalName>CVS.COLLECTORS</physicalName> </amqc:ActiveMQQueue> ... |
(0005397) ferg 07-25-11 14:13 |
The JCA drivers are currently discouraged in Resin (until we see sufficient demand for implementing JCA 1.6). Instead, use the non-JCA JMS driver. |
Mantis 1.0.0rc3[^]
Copyright © 2000 - 2005 Mantis Group
37 total queries executed. 30 unique queries executed. |