[jboss-user] [JBoss Messaging] - Re: Messaging 1.4.0 SP3 with JBoss AS 4.2.3

[sahanal]

Thank you for the response. 

JBM version: jboss-messaging-1.4.0.SP3

We have a pure app server which connects to JBM. we use durable subscribers. 
Only JBoss restart is solving the problem. client(my appserver) restart is not 
helping, which means creating new Connection and Session. Also when client is 
restarted we are able to see the following error: 
javax.jms.IllegalStateException: Cannot create a subscriber on the durable 
subscription since it already has subscriber(s)
. Here is the Jboss log


2009-07-14 17:57:51,925 DEBUG 
[org.jboss.remoting.transport.socket.ServerThread] 
WorkerThread#0[127.0.0.1:3979] closing socketWrapper: 
ServerSocketWrapper[Socket[addr=/127.0.0.1,port=3979,localport=4457].117459c]
2009-07-14 17:57:51,925 DEBUG 
[org.jboss.jms.server.remoting.ServerSocketWrapper] wrote CLOSING byte
2009-07-14 17:57:51,925 DEBUG 
[org.jboss.remoting.transport.socket.SocketWrapper] 
ServerSocketWrapper[Socket[addr=/127.0.0.1,port=3979,localport=4457].117459c] 
closing
2009-07-14 17:57:51,925 DEBUG 
[org.jboss.remoting.transport.socket.ServerThread] 
WorkerThread#1[127.0.0.1:3978] closing socketWrapper: 
ServerSocketWrapper[Socket[addr=/127.0.0.1,port=3978,localport=4457].db1df1]
2009-07-14 17:57:51,925 DEBUG 
[org.jboss.jms.server.remoting.ServerSocketWrapper] wrote CLOSING byte
2009-07-14 17:57:51,925 DEBUG 
[org.jboss.remoting.transport.socket.SocketWrapper] 
ServerSocketWrapper[Socket[addr=/127.0.0.1,port=3978,localport=4457].db1df1] 
closing
2009-07-14 17:57:51,925 DEBUG [org.jboss.remoting.InvokerRegistry] removed 
SocketClientInvoker[25724e, bisocket://10.11.151.170:2050639998] from registry
2009-07-14 17:57:51,925 DEBUG 
[org.jboss.remoting.transport.socket.MicroSocketClientInvoker] 
SocketClientInvoker[25724e, bisocket://10.11.151.170:2050639998] disconnecting 
...2009-07-14 17:57:51,925 DEBUG 
[org.jboss.remoting.transport.socket.SocketWrapper] 
ClientSocketWrapper[Socket[addr=/127.0.0.1,port=4235,localport=56656].1440636] 
closing
2009-07-14 17:57:51,925 DEBUG 
[org.jboss.remoting.callback.ServerInvokerCallbackHandler] 
ServerInvokerCallbackHandler[ab474q-8irr1u-fx4e2z0n-1-fx4e2ze3-4+ab474q-8irr1u-fx4e2z0n-1-fx4e2zg9-9]
 shut down
2009-07-14 17:57:56,035 DEBUG [com.arjuna.ats.arjuna.logging.arjLogger] 
Periodic recovery - first pass Tue, 14 Jul 2009 17:57:56
2009-07-14 17:57:56,035 DEBUG [com.arjuna.ats.arjuna.logging.arjLogger] 
StatusModule: first pass 
2009-07-14 17:57:56,035 DEBUG [com.arjuna.ats.txoj.logging.txojLoggerI18N] 
[com.arjuna.ats.internal.txoj.recovery.TORecoveryModule_3] - TORecoveryModule - 
first pass
2009-07-14 17:57:56,035 DEBUG [com.arjuna.ats.jta.logging.loggerI18N] 
[com.arjuna.ats.internal.jta.recovery.info.firstpass] Local XARecoveryModule - 
first pass
2009-07-14 17:58:06,035 DEBUG [com.arjuna.ats.arjuna.logging.arjLogger] 
Periodic recovery - second pass Tue, 14 Jul 2009 17:58:06
2009-07-14 17:58:06,035 DEBUG [com.arjuna.ats.arjuna.logging.arjLogger] 
AtomicActionRecoveryModule: Second pass 
2009-07-14 17:58:06,035 DEBUG [com.arjuna.ats.txoj.logging.txojLoggerI18N] 
[com.arjuna.ats.internal.txoj.recovery.TORecoveryModule_6] - TORecoveryModule - 
second pass
2009-07-14 17:58:06,035 DEBUG [com.arjuna.ats.jta.logging.loggerI18N] 
[com.arjuna.ats.internal.jta.recovery.info.secondpass] Local XARecoveryModule - 
second pass
2009-07-14 17:58:07,222 DEBUG 
[org.jboss.jms.server.security.SecurityMetadataStore] No SecurityMetadadata was 
available for SDSCMPCAMESSAGES1, using default security config
2009-07-14 17:58:37,176 DEBUG 
[org.jboss.jms.server.security.SecurityMetadataStore] No SecurityMetadadata was 
available for SDSCMPCAMESSAGES1, using default security config
2009-07-14 17:59:07,209 DEBUG 
[org.jboss.jms.server.security.SecurityMetadataStore] No SecurityMetadadata was 
available for SDSCMPCAMESSAGES1, using default security config
2009-07-14 17:59:37,163 DEBUG 
[org.jboss.jms.server.security.SecurityMetadataStore] No SecurityMetadadata was 
available for SDSCMPCAMESSAGES1, using default security config
2009-07-14 18:00:06,039 DEBUG [com.arjuna.ats.arjuna.logging.arjLogger] 
Periodic recovery - first pass Tue, 14 Jul 2009 18:00:06
2009-07-14 18:00:06,039 DEBUG [com.arjuna.ats.arjuna.logging.arjLogger] 
StatusModule: first pass 
2009-07-14 18:00:06,039 DEBUG [com.arjuna.ats.txoj.logging.txojLoggerI18N] 
[com.arjuna.ats.internal.txoj.recovery.TORecoveryModule_3] - TORecoveryModule - 
first pass
2009-07-14 18:00:06,039 DEBUG [com.arjuna.ats.jta.logging.loggerI18N] 
[com.arjuna.ats.internal.jta.recovery.info.firstpass] Local XARecoveryModule - 
first pass
2009-07-14 18:00:07,258 DEBUG 
[org.jboss.jms.server.security.SecurityMetadataStore] No SecurityMetadadata was 
available for SDSCMPCAMESSAGES1, using default security config
2009-07-14 18:00:16,039 DEBUG [com.arjuna.ats.arjuna.logging.arjLogger] 
Periodic recovery - second pass Tue, 14 Jul 2009 18:00:16
2009-07-14 18:00:16,039 DEBUG [com.arjuna.ats.arjuna.logging.arjLogger] 
AtomicActionRecoveryModule: 

[jboss-user] [JBoss Messaging] - Re: Messaging 1.4.0 SP3 with JBoss AS 4.2.3

[gaohoward]

Hi,

Please give the cp version of JBM, like 1.4.0.sp3-cp07.

The problem seems your client has crached before you close any 
subscribers/session/connections.



View the original post : 
http://www.jboss.org/index.html?module=bbop=viewtopicp=4243661#4243661

Reply to the post : 
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4243661
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user

[jboss-user] [JBoss Messaging] - Re: Messaging 1.4.0 SP3 with JBoss AS 4.2.3

[sahanal]

Not sure how to get the CP version. in the Manifest file, i have this info

Manifest-Version: 1.0
Ant-Version: Apache Ant 1.7.0
Created-By: 1.5.0_13-b05 (Sun Microsystems Inc.)
Specification-Title: JBoss Messaging
Specification-Version: 1.4.0.SP3
Specification-Vendor: JBoss Inc. (http://www.jboss.org/)
Implementation-Title: JBoss Messaging
Implementation-URL: http://www.jboss.org/
Implementation-Version: 1.4.0.SP3 (build: CVSTag=JBossMessaging_1_4_0_
 SP3 date=200712131418)
Implementation-Vendor: JBoss Inc. (http://www.jboss.org/)
Implementation-Vendor-Id: http://www.jboss.org/


View the original post : 
http://www.jboss.org/index.html?module=bbop=viewtopicp=4243670#4243670

Reply to the post : 
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4243670
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user

[jboss-user] [JBoss Messaging] - Re: Messaging 1.4.0 SP3 with JBoss AS 4.2.3

[gaohoward]

OK you already have the version right. You are using the 1.4.0.sp3. Current 
release is 1.4.0.sp3-cp08 for EAP and 1.4.4.GA for JBoss 4.2.3.GA. 
Can you try the latest version? They have a lot bug fixes.


View the original post : 
http://www.jboss.org/index.html?module=bbop=viewtopicp=4243674#4243674

Reply to the post : 
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4243674
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user

[jboss-user] [JBoss Messaging] - Re: Messaging 1.4.0 SP3 with JBoss AS 4.2.3

[sahanal]

facing exactly the same problem. we are using JBoss 4.2.3 GA with JBM 1.4. Do 
any one have solution for this?

Assuming this could be because of network issue, we changed the JBoss server 
bind address to loop back address, but still got the same error, showing,

2009-07-14 17:57:51,925 DEBUG 
[org.jboss.remoting.transport.socket.MicroSocketClientInvoker] 
SocketClientInvoker[25724e, bisocket://10.1.150.170:2050639998] disconnecting 
...

2009-07-14 17:57:51,925 DEBUG 
[org.jboss.remoting.transport.socket.SocketWrapper] 
ClientSocketWrapper[Socket[addr=/127.0.0.1,port=4235,localport=56656].1440636] 
closing

2009-07-14 17:57:51,925 DEBUG 
[org.jboss.remoting.callback.ServerInvokerCallbackHandler] 
ServerInvokerCallbackHandler[ab474q-8irr1u-fx4e2z0n-1-fx4e2ze3-4+ab474q-8irr1u-fx4e2z0n-1-fx4e2zg9-9]
 shut down

Its quite urgent, can any one pls help?


View the original post : 
http://www.jboss.org/index.html?module=bbop=viewtopicp=4243604#4243604

Reply to the post : 
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4243604
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user

[jboss-user] [JBoss Messaging] - Re: Messaging 1.4.0 SP3 with JBoss AS 4.2.3

[gaohoward]

Please give exact version of JBM. also the full stack trace may help better 
understanding your issue. Thanks!

View the original post : 
http://www.jboss.org/index.html?module=bbop=viewtopicp=4243624#4243624

Reply to the post : 
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4243624
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user

[jboss-user] [JBoss Messaging] - Re: Messaging 1.4.0 SP3 with JBoss AS 4.2.3

[dbarkats]

The problem is back we have already this kind of deconnection

View the original post : 
http://www.jboss.com/index.html?module=bbop=viewtopicp=4177873#4177873

Reply to the post : 
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4177873
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user

[jboss-user] [JBoss Messaging] - Re: Messaging 1.4.0 SP3 with JBoss AS 4.2.3

[dbarkats]

Does anyone can help me on this problem

THANK U

View the original post : 
http://www.jboss.com/index.html?module=bbop=viewtopicp=4174812#4174812

Reply to the post : 
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4174812
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user