Wednesday, August 1, 2001 06:57 AM
We set up a test to test our JMS implementation on Weblogic 5.1. We are creating multiple threads and then sending messages off to gather performance statistics. When we get to about 25 concurrent threads, we deadlock the server. If we set latency to 100 milliseconds or above then it will handle multiple threads. If you go below a 100 millisecond latency delay between requests or you are concurrent- it deadlocks. Are there any known issues? Any help is appreciated.