[JBoss-user] [Messaging, JMS JBossMQ] - Re: JBossMQ Thread Count grows until Linux Too Many Files Op

2005-09-11 Thread THancock
Unfortunately we received no help with this problem. We checked all connections 
and objects were being closed and destroyed and still the sockets on each MDB 
remained. 

The only solution for us was to move these tasks away from the MDB to a servlet 
which received the object, fired off a new Thread and processed the object in 
the Thread destroying the Thread when it was finished.

It works well for us but what would have worked better would have been a 
solution in an existing framework (rant, rant, rant - lol).



View the original post : 
http://www.jboss.com/index.html?module=bbop=viewtopicp=3894113#3894113

Reply to the post : 
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3894113


---
SF.Net email is Sponsored by the Better Software Conference  EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile  Plan-Driven Development * Managing Projects  Teams * Testing  QA
Security * Process Improvement  Measurement * http://www.sqe.com/bsce5sf
___
JBoss-user mailing list
JBoss-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-user


[JBoss-user] [Messaging, JMS JBossMQ] - JBossMQ Thread Count grows until Linux Too Many Files Open e

2005-05-10 Thread THancock
We are using JBoss 3.2.6 on JVM 1.4.2-06. 

We have 2 web servers that publish messages onto one of 3 JBoss Message Queue 
servers. 

The Thread List shows lots and lots of the following entries in the JBossMQ 
Thread Group:


  | Thread: UIL2.SocketManager.ReadTask#5 client=10.2.11.3:38834 : priority:5, 
demon:true
  | Thread: UIL2.SocketManager.WriteTask#6 client=10.2.11.3:38834 : priority:5, 
demon:true
  | 

interspersed with a few:

Thread: Thread-63 : priority:5, demon:true

The IP address relates to one of the servers publishing on the queue. The 
publishing of the message onto the queue is successful and no errors are 
thrown. 

Does anyone know why the socket is never treated as disconnected, thus freeing 
the Thread for re-use? Or is there a configuration setting for Thread timeouts?

We have to restart the servers about once every 2 hours to avoid the open files 
limit on the Linux boxes we are running and it would be great if we could avoid 
this problem altogether.


View the original post : 
http://www.jboss.org/index.html?module=bbop=viewtopicp=3877164#3877164

Reply to the post : 
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3877164


---
This SF.Net email is sponsored by Oracle Space Sweepstakes
Want to be the first software developer in space?
Enter now for the Oracle Space Sweepstakes!
http://ads.osdn.com/?ad_id=7393alloc_id=16281op=click
___
JBoss-user mailing list
JBoss-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-user