>> I have this exception when :
>> - i undeploy the bean
>> - i send a message to the bean
>> - i deploy the bean (nothing appends)
>As described below: if you send messages here, the one's sent during
>undeploy will also be delivered. If no messages are sent before you
>undeploy, no messages w
ployed
are defintivly lost!!
We can call it a bug, no??
Cécile Saint-Martin
[EMAIL PROTECTED]
On 4 Maj, Till: [EMAIL PROTECTED] wrote:
> On 4 Maj, Saint-Martin Cécile wrote:
>> In fact, i had already problem when un deploying MDB :
>>
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 co
>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
>> I'm testing MDB with Jboss, i wrote a MDB wich destination is a durable
>> topic. When i stop ContainerFactoy service, Jboss clear all instances of
the
>> MDB and it's OK.
>> But when i restart this service, it doesn't re-create the pool of MDB
>> instances. Is it a bug?
>Hi, It is possible
Hello,
I'm testing MDB with Jboss, i wrote a MDB wich destination is a durable
topic. When i stop ContainerFactoy service, Jboss clear all instances of the
MDB and it's OK.
But when i restart this service, it doesn't re-create the pool of MDB
instances. Is it a bug?
Cécile Saint-Martin
[EMAIL P
