RE: TCP Clients hang

(ignore last post - hit send too soon)
 
Without seeing a server stack trace, its hard to say.
There have been reports of the tcp connector in 0.7.6 deadlocking.
Another possibility is that the server is unable to allocate a database
connection,
and is blocking until one  becomes free. To avoid this, increase the no.
of connections in the pool to be greater than the no. of threads allocated
to the scheduler
e.g:
 
  <SchedulerConfiguration maxThreads="10" />

  <DatabaseConfiguration>
    <RdbmsDatabaseConfiguration driver="...." maxActive="20" ....

 
-Tim

  _____  

From: openjms-user-admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
[mailto:openjms-user-admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org] On Behalf Of Tom Kline
Sent: Saturday, 29 April 2006 5:41 AM
To: [email protected]
Subject: [openjms-user] TCP Clients hang



We have been noticing that our TCP clients seem to get randomly "stuck"
they just hang after they connect.  We are using 0.7.6 version of OpenJMS.
Below you will see a message from our clients log file:

 

DEBUG 2006-04-28 15:23:22,070
com.metrosplash.jms.JMSListener.<init>(JMSListener.java:159) - Message
Listener running with a message selector: STORE =
'29399930-af35-468c-ab25-e8db410bc839'

 

 

Just sits and doesn't continue on.

 

Any ideas???

 

 

 

 

 



FuelLinks <http://www.fuellinks.com/> 

Tom Kline

(214)908-6640

MetroSplash Systems Group, Inc.

2300 Highland Village Road

Suite 700

Highland Village, TX 75077

 <http://www.fuellinks.com>