Using JBoss 3.0.4 and JBossMQ.
We have a problem if the durable subscriber client
attempts to reconnect after an abnormal connection
using the same Client ID, the exception is raised:
javax.jms.InvalidClientIDException: This
loggedOnClientIds is already registered !
at
org.jboss.mq.sm.AbstractStateManager.addLoggedOnClientId(AbstractStateManager.java:237)
How do we tell JBossMQ that the Client ID is no longer
connected?
In searching through the forums, I saw the suggestion
to use a different Client ID on reconnect, but that
does not make sense as the client will miss any
messages that published during the time it is down.
Thanks,
Ken Whitaker
__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com
-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user
