Is it possible to send messages to topic's/queues BEFORE the

[dbudworth]

Hello all,

I have added a JMS topic and queue to my jboss (CVS as of today)

I want to be able to send messages to either one (I don't care which), that will be stored by jboss until the MDBs that watch them are deployed.

The idea here, is I have some beans that are active on only one host (due to limited external resource), and remote machines send JMS messages to the resource host. But I also want to be able to upgrade the resource host on the fly, which would mean that while the beans are undeploying/re-deploying, they wont be listening on the message queues.

It seems from the log info, that both topic and queue see that there are no current listeners, and just drop the message on the floor.

Is there a way to make the container keep them until someone picks them up?

I don't mind RTFMing if someone wants to point out where this is descibed.

Thanks

[pra]

As far as I know the only (by the spec) guaranteed way of doing this is by making your MDB a durable topic subscriber (covered in the manual).

Depending on the (undocumented) retention policy for destinations in JBossMQ a queue may also make the jobb for you, but as said, without garantees - remember to set the time to live to a long enough period.

//Peter

[dbudworth]

But how does making the bean a durable subscriber help if I want to send messages to the queue BEFORE I deploy the bean?

What I am looking for is a way to declare a queue/topic in a way that a message will be held until someone picks it up.

What I see in Jboss logs is a message saying that there are no listeners, so I assume that it's dropping the message on the floor.

Isn't this the concept of durable/persistant queues? Or, is the idea that the message persists if the container holding the subscriber crashes?

[pra]

I would recomend you to ask on the old JBossMQ list, since thats where the JBossMQ guys still hangs out.

//Peter