Hello, 

I am getting the above warning with timeout of 500 msec when I stress my application. 
It is hard to reproduce the failure (i.e. it does not seem to happen if I have traces 
on and it does not happen every time I run a test) but I have seen it pop up every 
once in a while. 

My application has the following high-level architecture:
SessionBean -> MDB -> EntityBean -> MDB.

The client uses the session bean to queue up about 500 messages which load 500 entity 
beans. Then a perodic timer comes along to talk to the entity beans which queue up 
messages to another queue which runs some computation.  

My MDBs are configured with the default (i.e. 15) number of concurrent jms sessions 
and the default (ie. 100) number of MDB instances.

I appreciate any help in letting me know the conditions in which this happens. Thanks 
in advance for any help. 

Regards,
aboudank
 

View the original post : 
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3833918#3833918

Reply to the post : 
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3833918


-------------------------------------------------------
This SF.Net email is sponsored by Sleepycat Software
Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to 
deliver higher performing products faster, at low TCO.
http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user

Reply via email to