set the uncaught handler once in your client jvm, so that it has global effect:
>From your client main, or some startup code, use:
http://download.oracle.com/javase/1.5.0/docs/api/java/lang/Thread.html#setDefaultUncaughtExceptionHandler(java.lang.Thread.UncaughtExceptionHandler)
On 15 September 20
I'm hesitant to turn trace logging on as we get thousands of messages per
second, and this problem occurs maybe weeks apart, maybe days apart and so
trying to find anything in the log will be hard.
As for the default uncaught exception handler... I cant see how we can set
that from outside the Act
Dom,
this is unusual, some thoughts:
can you enable trace level logging for activemq on your clients to
see if there is anything suspicious in there.
If the dispatch thread is dying we should be able to see why.
As a catch all, can you specify a
java.lang.Thread#setDefaultUncaughtExceptionHandler
Our subscribers are not durable, however I have noticed that it does appear
to occur around our peaks (sometimes before, sometimes afterwards). Although
I have had it occur once at night, when our traffic was very load (1% of
peak).
I'm using the OpenWire protocol, not stomp. So I'm guessing that
Dom writes:
> Hi,
>
> I've starting having unusual problems with my ActiveMQ consumers, we send
> object messages via JMS 24 hours a day, peaking at around 10k per second to
> various different consumers. All these consumers are consuming from the same
> topic, however from different physical ser
When I processing a message something might fail that I want it to try again
and after it tries a specified number times, I want to push that message to
another queue for alternate processing. I have looked at JMS retries but
doesn't seem like the way I want to go.
With a valid Message, what is t
