In fact, i had already problem when un deploying MDB :
04/05/2001 15:25:35 ERROR
org.jboss.logging.Log4jService.handleNotification -
java.lang.NullPointerException
04/05/2001 15:25:35 INFO
org.jboss.logging.Log4jService.handleNotification - Could not close
JMSContainerInvoker connection:javax.jms.JMSEx
ception: Cannot close properly the connection
----- Original Message -----
From: "Saint-Martin Cécile" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, May 04, 2001 3:04 PM
Subject: Re: [JBoss-dev] Message driven bean
>The only way to take down a container is by undeploying the bean.
>
>To check if durable work, create your bean. Deploy it by copying it to
>deploy/. Send some messages. Remove it from deploy. Send some messages.
>Copy it in again. If it recives the messages sent when it was undeployed
>durable work.
I did that and i had a problem when i re-deployed the MDB :
04/05/2001 14:51:59 ERROR
org.jboss.logging.Log4jService.handleNotification -
java.rmi.RemoteException: ; nested exception is:
javax.jms.JMSException: The login id has an assigned client id.
That client id is already connected to the server!
(I used the subscriber example)
In fact, i dont' really understand how durable subscription works on JBoss
:(
Why do we need to create a user??
Cécile Saint-Martin
[EMAIL PROTECTED]
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
