[ https://issues.apache.org/activemq/browse/AMQ-1054?page=comments#action_37585 ] Shoaib Akhtar commented on AMQ-1054: ------------------------------------
Hi James and Guy, I ran the above test with ActiveMq 3.1 on Windows Xp service pack 2 on jdk 1.5.0.9 and as mentioned by Guy it worked perfectly well. And the line i mentioned in my previous entry (i.e. return (ActiveMQXid[]) receipt.getResult(); ) evaulated to as follows receipt.getResult()=org.activemq.message.ActiveMQXid[0] and as you can see in previosu post that for 4.0.2 it evaulated to receipt.getData() = org.apache.activemq.command.DataStructure[0] I know there has been lot of changes in 3.1 nad 4.0.2 but somehow this bug was introduced as you can see that ActiveMQXid[0] and .DataStructure[0] has a lot of differnce as the former can be casted to ActiveMQXid[] or XATransactionId[] in new version but the DataStructure[0] could not be. So i am sure that ActiveMq code has definetly a problem here and the URL mentioned by Guy on JOTM also support this (though i could not find those lines in code) but i guess that this problem should be resolved quickly as both atomikos and activemq are great products and form an excellent combination with each other. > XA recover fails for 4.0.1 > -------------------------- > > Key: AMQ-1054 > URL: https://issues.apache.org/activemq/browse/AMQ-1054 > Project: ActiveMQ > Issue Type: Bug > Environment: Java, JDK 1.4, Windows, Atomikos TransactionsEssentials > for the JTA/XA part > Reporter: Guy Pardon > Attachments: pom.xml > > > XAResource.recover seems to fail for 4.x of ActiveMQ: > ERROR IN RECOVERY [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 > 08:43:35,152 > [Lorg.apache.activemq.command.DataStructure; [thread: > SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,152 > at: > org.apache.activemq.TransactionContext.recover(TransactionContext.java:508) > [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,152 > at: com.atomikos.datasource.xa.XATransactionalResource.recover(Unknown > Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,152 > at: com.atomikos.datasource.xa.XATransactionalResource.endRecovery(Unknown > Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,152 > at: com.atomikos.icatch.imp.TransactionServiceImp.recover(Unknown Source) > [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 > at: > com.atomikos.datasource.xa.XATransactionalResource.setRecoveryService(Unknown > Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 > at: com.atomikos.icatch.system.Configuration.addResource(Unknown Source) > [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 > at: com.atomikos.jms.QueueConnectionFactoryBean.checkSetup(Unknown Source) > [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 > at: com.atomikos.jms.QueueConnectionFactoryBean.createQueueConnection(Unknown > Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 > at: com.atomikos.jms.QueueConnectionFactoryBean.createConnection(Unknown > Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 > Also see http://www.atomikos-support.com/forums/viewtopic.php?t=351 (where I > borrowed this stack trace from). We have seen similar things in other > applications that tried to use ActiveMQ. I think this is a class cast error > in ActiveMQ... > With 3.1 there is no problem. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
