Queue Connection management

divine_comedy Jul 10, 2003 2:36 PM

Hi, I am a new bie to JMS so please bear with me.
I am currently working to abstract the lower level details of JMS. And I am thinking of the following :
1. Using only one QueueConnection object per application. Is this a good idea ? ( seems to me that some books recommend this approach ). When clients want to send a message, they will work only with a Session.

A question :
- Is is ok if I do not close the connection upon shutdown ? I am thinking of using a static initializer to open the connection, but I am not quite sure whether to use a finalizer to shut down the connection. Any suggestions ??? I am trying not to use an MBean to manage the lifecycle.

1. Re: Queue Connection management

divine_comedy Jul 10, 2003 3:08 PM (in response to divine_comedy)

Forgot to ask the following question :
- Is a Queue object thread safe ?

Thanks.
Actions
2. Re: Queue Connection management

nphelps Jul 10, 2003 6:34 PM (in response to divine_comedy)

On you first question, it is a good design pattern to use a single connection, yes. You can use multiple Sessions which will provide for concurrent message delivery etc.

As to your second question... I'd recommend you close the connection.
Actions
3. Re: Queue Connection management

nphelps Jul 10, 2003 6:35 PM (in response to divine_comedy)

> - Is a Queue object thread safe ?

A Queue object is inherently thread safe because it is read only.
Actions

Go to original post