"[EMAIL PROTECTED]" wrote : http://jira.jboss.com/jira/browse/JBAS-1337
| http://jira.jboss.com/jira/browse/JBAS-1338
|
Ok.
We are going to re-use the jms connections avoiding creating them.
Greetings
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=38947
http://jira.jboss.com/jira/browse/JBAS-1337
http://jira.jboss.com/jira/browse/JBAS-1338
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3894729#3894729
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3894729
I am having the same problem as you.
I have 3 schedulers which are creating about 2 jms connections per second and
close them 2 seconds later. The amount of threads (readtasks and writetasks)
created by JBoss grows rapidly to 4 hundred when it stops growing. If we
decrease the creation rate t
Hi,
I have solved the problem by using a singelton wrapper for the Connection class. This
will also enable all clients to be Exception listeners since the wrapper class
distributes the onException() call.
I am starting and stopping with, addMessageListener(...) and session.close().
Seems to wo
If you want to use Connection.start and Connection.stop per client, then I see why
you'd have a need for many of them.
As I said, feel free to make changes to the JBoss source and send the patch my way.
If it looks good, I'll make it available for 3.2.4.
http://www.jboss.org/index.html?module
anonymous wrote : Looks like what your code does is connect, the disconnect.
Yep, This is true. This code only demonstrates a problem I am experiencing in a lager
application.
anonymous wrote : Is there some way you can avoid connecting and disconnecting so
quickly?
I have been trying to find a
Looks like what your code does is connect, the disconnect. Is there some way you can
avoid connecting and disconnecting so quickly? You can have one connection per
application and create sessions per Thread even if multi-threaded.
Use UIL2ConnectionFactory (see the FAQ) not UILConnectionFacto
