"genman" wrote :
| It looks the "wait" are for messages to arrive off the receive queue.
Perhaps the server isn't seeing the client response message? Do you know if
your client is active.
These are client stack traces. The client is hung in the main thread calling
start().
View the origina
"genman" wrote :
| Get a stack trace of your application and see what it's doing in JBoss
land. Also, upgrading and testing wouldn't hurt and might not be too hard to
try...
The main thread, which is stuck in start() looks like this:
- java.lang.Object.wait(long) (Compiled frame; informati
"nsayer" wrote : We have a client whose code looks somewhat like this:
|
| do {
| qc.start();
| runABunchOfThreadsThatProcess5000Messages();
| qc.stop();
| } while(shouldWeKeepGoing());
|
| (note that the method between start() and stop() waits for all t
We have a client whose code looks somewhat like this:
do {
qc.start();
makeABunchOfThreadsThatProcess5000Messages();
qc.stop();
} while(shouldWeKeepGoing());
The problem we're seeing is that very intermittently the client will get stuck
inside the call to start(). We registered an Exceptio
We're happily using a Jboss 4.0 application server to host a JMS queue we use.
Our actual use of the queue is straightforward, and is working very well.
As part of our monitoring strategy, we want to periodically (every minute or
so) examine the queue to look at the oldest message, the youngest
