JMS Deployment
1 posts in topic
Flat View  Flat View
Older Post First |   Reply to Topic
TOPIC ACTIONS:
 

Posted By:   Jeff_Singer
Posted On:   Friday, February 22, 2002 01:34 AM

At the momment we have a number of different queues and topics.

What we are typically doing is running a JVM for each listener, so we have a very large number of JVM's and this result in a large number of threads (Linux). We currently have 1300 threads?????



Is this the best way to do this? I can obviously have one JVM for a number of listeners, but this has it's own drawbacks.



Also I am interested in the difference between receivers and listeners. Performance and load on system?


Any ideas or help will be appreciated, Jeff Singer
Report | Quote This | Send private message | Reply | Print

Re: JMS Deployment

Posted By:   Gregor_Kovac  
Posted On:   Saturday, February 23, 2002 12:21 AM

Hi!


As I can understand you, you have one SwiftMQ router with one JMS listener running in one JVM, right?

The thing is that you do not need this.

You can have multiple JMS listeners defined on one router, hence running only one JVM.

But each JMS listener must be running on a different port.

You would define something like:


swiftlet.sys$jms.listeners.names=plainsocket,sslsocket
swiftlet.sys$jms.listeners.plainsocket.port=4001
swiftlet.sys$jms.listeners.plainsocket.socketfactory.class=com.swiftmq.net.PlainSocketFactory
swiftlet.sys$jms.listeners.sslsocket.port=4002
swiftlet.sys$jms.listeners.sslsocket.socketfactory.class=com.swiftmq.net.JSSESocketFactory


So now you would have two JMS listeners(one is plainsocket running on port 4001 and the other is a SSL listener running on port 4002).


I hope this helps.

Best regards,

Kovi
Report | Quote This | Send private message | Reply | Print
About | Sitemap | Contact