dcsimg
WebLogic 7.0 halted because of more than 30 cuncurrent threads hit
0 posts in topic
Flat View  Flat View
TOPIC ACTIONS:
 

Posted By:   Matt_Jiang
Posted On:   Friday, October 18, 2002 02:15 AM

Here is the structure: 1. 30 concurrent threads request http request -> 2.. servlet in WLS -> 3.. servlet call a stateless session bean -> 3.1. session bean send a message to Q1 and return to servlet. session create an global object, put it in a synchronized global HashMap -> 3.2. servlet start to wait on an global object, according to a key -> 4.. in onMessage() of a MDB, send a message to Q2 -> 5.. servlet as a Q2 message listener -> 6.. servlet got message from Q2 -> 7.. notify the object to release wait. The    More>>

Here is the structure:


1. 30 concurrent threads request http request ->

2.. servlet in WLS ->

3.. servlet call a stateless session bean ->

3.1. session bean send a message to Q1 and return to servlet. session create an global object, put it in a synchronized global HashMap
->

3.2. servlet start to wait on an global object, according to a key ->

4.. in onMessage() of a MDB, send a message to Q2 ->

5.. servlet as a Q2 message listener ->

6.. servlet got message from Q2 ->

7.. notify the object to release wait.




The problem occurs in 3.2!

I think WebLogic couldnot handle so many concurrent users, too many threads are waiting. Cause the MDB didn't get any onMessage call from Q1. so the servlet won't never get notify. Then WLS halted.



I run the same structure in JBoss 3.0, it runs with no problem!


Does any body hit this problem,too? Please give me advises.
thank you very much

   <<Less
About | Sitemap | Contact