why still getting

[gan.gary]

my JBoss hit this:

org.jboss.mq.SpyJMSException: Cannot authenticate user; - nested throwable: (java.io.IOException: Client is not connected)
2008-11-08 03:03:40,515 ERROR [STDERR] at org.jboss.mq.SpyJMSException.getAsJMSException(SpyJMSException.java:72)
2008-11-08 03:03:40,515 ERROR [STDERR] at org.jboss.mq.SpyJMSException.rethrowAsJMSException(SpyJMSException.java:57)
...
2008-11-08 03:03:40,703 ERROR [STDERR] at java.lang.Thread.run(Thread.java:595)
2008-11-08 03:03:40,703 ERROR [STDERR] Caused by: java.io.IOException: Client is not connected
2008-11-08 03:03:40,703 ERROR [STDERR] at org.jboss.mq.il.uil2.SocketManager.internalSendMessage(SocketManager.java:288)
2008-11-08 03:03:40,703 ERROR [STDERR] at org.jboss.mq.il.uil2.SocketManager.sendMessage(SocketManager.java:244)
2008-11-08 03:03:40,703 ERROR [STDERR] at org.jboss.mq.il.uil2.UILServerIL.authenticate(UILServerIL.java:277)
2008-11-08 03:03:40,703 ERROR [STDERR] at org.jboss.mq.Connection.authenticate(Connection.java:1067)
2008-11-08 03:03:40,703 ERROR [STDERR] ... 57 more

and later I keep getting this warning:

2008-11-12 08:41:15,187 WARN [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, 29, 27, 1-acc434c:7d2:49140acf:5add5eacc434c:7d2:49140acf:5add5f

After I do this,
http://www.jboss.org/file-access/default/members/jbossmessaging/freezone/docs/userguide-1.4.0.SP3/html_single/index.html#recovery
the warning is still there. Any idea?

[gan.gary]

from JBoss WIki: http://www.jboss.org/community/docs/DOC-12826
for resolution #2 :

2. Make sure the java:/DefaultJMSProvider is defined and working correctly. It's configured in the jms-ds.xml file or the hajms-ds.xml file

I think it's configured by default in "C:\jboss-4.2.2.GA\server\default\deploy\jms\jms-ds.xml". but working correctly??? How? Thru' JBoss Mgt COnsole?

for resolution #3:

"org.jboss.mq.SpyJMSException: Cannot authenticate user; - nested throwable: (java.io.IOException: Client is not connected)"

I found nothing at: http://search.yahoo.com/search;_ylt=A0oGknCnQBpJqasA3OtXNyoA?p=%22org.jboss.mq.SpyJMSException%3A+Cannot+authenticate+user%22%2B%22java.io.IOException%3A+Client+is+not+connected%22&fr=yie7c&ei=UTF-8

[peterj]

The doc link you provided in your first post is for JBoss Message, but the location of the jms-ds.xml file you provided in your second post is for JBossMQ - two completely different messaging systems. If you want to make use of the recovery mechanisms, you need to first install JBoss Messaging.

[gan.gary]

"PeterJ" wrote:
The doc link you provided in your first post is for JBoss Message, but the location of the jms-ds.xml file you provided in your second post is for JBossMQ - two completely different messaging systems. If you want to make use of the recovery mechanisms, you need to first install JBoss Messaging.

Really? Then what's the correct way for recovery, for those who are using default JBoss setting( I am not sure what queue system is it, but it's JBoss version 4.2.2.GA)?

[peterj]

I am not aware of what recovery capabilities are present in JBossMQ (which is the messaging system in 4.2.x). This area was one of the major features of JBoss Messaging - coordination with JBoss Transactions to provide full XA-compliant recovery.

My recommendation is to install JBoss Messaging.

[gan.gary]

what if I stick with existing messaging? How can i get rid of that warning msg? It's because I could not even get back what I lost.

[gan.gary]

anyone?