-
1. Re: createTopicConnection with secured topic
adrian.brock Aug 13, 2003 8:42 AM (in response to uuu)A client is only allowed to signon to a server once.
It is in the spec. You should assign a different clientid
in jbossmq-state.xml for a second user.
Regards,
Adrian -
2. Re: createTopicConnection with secured topic
uuu Aug 14, 2003 3:43 AM (in response to uuu)Hi, Adrian!
Thanks for your reply.
I've already tried different users for MDB and Session bean and it works.
But I still get this error when I kill the second instance(with MDB) to model fatal system crach so it has no chance to logout from the 1st instance.
So when it restarts it gets "That client id is already connected to the server!".
And I've got to restart 1st instance to purge this stuck user.
Is there a way to do it without restarting?
Througth JMX or something like that? -
3. Re: createTopicConnection with secured topic
adrian.brock Aug 14, 2003 8:16 AM (in response to uuu)Which version of jboss are you using?
Did jboss detect the first mdb had gone away?
Regards,
Adrian -
4. Re: createTopicConnection with secured topic
uuu Aug 14, 2003 11:38 PM (in response to uuu)I'm using JBoss 3.2.1 with Tomcat 4.1.24 .
JBoss doesn't detect that MDB has gone away probably because I'm using HTTPServerILService -
5. Re: createTopicConnection with secured topic
adrian.brock Aug 15, 2003 8:26 AM (in response to uuu)You should report that as a bug at
http://www.sf.net/projects/jboss
It should be possible for the server to detect the
client vanished otherwise the client id would be locked
out unless you rebooted jboss.
Regards,
Adrian