For every message that comes into the JMS Server via UIL2, the SocketManager
seems to be starting two threads: One ReadTask and another WriteTask. So, you
are seeing two threads for every message.
Your test is a good one. But for every run, you are creating the following:
1) Connection
2) Session
3) Sender
4) Receiver
This is causing in a proliferation of the number of threads that have to be
created by the JMS Server.
Try caching the above 4 objects (for a given queue) once you have created them
the first time. From the second time onwards, keep using the cached objects.
This might alleviate your problem.
For ex:
class ConnectionInfoHolder
| {
| private Connection conn = null;
| private Session session = null;
| ....
| }
|
| class Client
| {
| Map map = new Hashtable();
| public void test()
| {
| //create all of them
| map.put("queueName",connInfoHolder);
|
| if(map.contains("queueName"))
| //do your testing
| }
| }
HTH
Thanks,
Kalyan
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3855461#3855461
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3855461
-------------------------------------------------------
This SF.Net email is sponsored by: InterSystems CACHE
FREE OODBMS DOWNLOAD - A multidimensional database that combines
robust object and relational technologies, making it a perfect match
for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user
