This content has been marked as final.
Show 18 replies
-
15. Re: Could not find new XAResource to use for recovering non-
chtimi2 Apr 9, 2009 11:22 AM (in response to chtimi2)I have tried reverting back the order out of curiosity, and it still works.
Then i promptly put your order back :) (just in case) -
16. Re: Could not find new XAResource to use for recovering non-
tcoates1362 Jul 21, 2009 8:23 PM (in response to chtimi2)I've been having the same problem and I'm hoping someone can help me.
I'm using JBoss 4.2.3.GA and JBoss Messaging 1.4.4.GA. I'm seeing the following warning in the log after a transaction is rolled back - which is something that can happen in my application as a normal course of business.2009-07-21 17:07:53,125 [WARN] ~Thread-5(com.arjuna.ats.jta.logging.loggerI18N): [com.arjuna.ats.internal.jta.resources.arjunacore.norecoveryxa] [com.arjuna.ats.internal.jta.resources.arjunacore.norecoveryxa] Could not find new XAResource to use for recovering non-serializable XAResource < 131075, 28, 26, 1--3f5737a6:1264:4a6657eb:72-3f5737a6:1264:4a6657eb:7f>
My jbossjta-properties.xml contains this:<properties depends="arjuna" name="jta"> <property name="com.arjuna.ats.jta.recovery.XAResourceRecovery.JBMESSAGING1" value="org.jboss.jms.server.recovery.MessagingXAResourceRecovery;java:/DefaultJMSProvider"/> <!-- Support subtransactions in the JTA layer? Default is NO. --> <property name="com.arjuna.ats.jta.supportSubtransactions" value="NO"/> <property name="com.arjuna.ats.jta.jtaTMImplementation" value="com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionManagerImple"/> <!-- com.arjuna.ats.internal.jta.transaction.jts.TransactionManagerImple --> <property name="com.arjuna.ats.jta.jtaUTImplementation" value="com.arjuna.ats.internal.jta.transaction.arjunacore.UserTransactionImple"/> <!-- com.arjuna.ats.internal.jta.transaction.jts.UserTransactionImple --> </properties>
and my jms-ds.xml looks like this:<?xml version="1.0" encoding="UTF-8"?> <connection-factories> <!-- ==================================================================== --> <!-- JMS Stuff --> <!-- ==================================================================== --> <!-- The JMS provider loader --> <mbean code="org.jboss.jms.jndi.JMSProviderLoader" name="jboss.messaging:service=JMSProviderLoader,name=JMSProvider"> <attribute name="ProviderName">DefaultJMSProvider</attribute> <attribute name="ProviderAdapterClass"> org.jboss.jms.jndi.JNDIProviderAdapter </attribute> <!-- The combined connection factory --> <attribute name="FactoryRef">java:/XAConnectionFactory</attribute> <!-- The queue connection factory --> <attribute name="QueueFactoryRef">java:/XAConnectionFactory</attribute> <!-- The topic factory --> <attribute name="TopicFactoryRef">java:/XAConnectionFactory</attribute> <!-- Uncomment to use HAJNDI to access JMS <attribute name="Properties"> java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces java.naming.provider.url=localhost:1100 </attribute> --> </mbean> <!-- The server session pool for Message Driven Beans --> <mbean code="org.jboss.jms.asf.ServerSessionPoolLoader" name="jboss.messaging:service=ServerSessionPoolMBean,name=StdJMSPool"> <depends optional-attribute-name="XidFactory">jboss:service=XidFactory</depends> <attribute name="PoolName">StdJMSPool</attribute> <attribute name="PoolFactoryClass"> org.jboss.jms.asf.StdServerSessionPoolFactory </attribute> </mbean> <!-- JMS XA Resource adapter, use this to get transacted JMS in beans --> <tx-connection-factory> <jndi-name>JmsXA</jndi-name> <xa-transaction/> <rar-name>jms-ra.rar</rar-name> <connection-definition>org.jboss.resource.adapter.jms.JmsConnectionFactory</connection-definition> <config-property name="SessionDefaultType" type="java.lang.String">javax.jms.Topic</config-property> <config-property name="JmsProviderAdapterJNDI" type="java.lang.String">java:/DefaultJMSProvider</config-property> <security-domain-and-application>JmsXARealm</security-domain-and-application> <max-pool-size>20</max-pool-size> </tx-connection-factory> </connection-factories>
I can get the warning to go away by clearing out the data directory and restarting, but as soon as my app does another rollback, the warning is back.
I read through a lot of posts and wiki articles on this, but I don't see what I'm doing wrong. Can someone help me out?
Thanks! -
17. Re: Could not find new XAResource to use for recovering non-
gaohoward Jul 21, 2009 10:21 PM (in response to chtimi2)Can you describe in more details how to reproduce it? Thanks.
-
18. Re: Could not find new XAResource to use for recovering non-
frankthetank Jul 31, 2009 4:05 AM (in response to chtimi2)Thanks!!!
I had the same issues and they were only resolved after clearing the temp files.
This should be noted in the documentation.
Also, do I only need to do it once or every time I start JBoss?