activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "James Strachan" <james.strac...@gmail.com>
Subject Re: StackOveflowError in slow message consumer, why?
Date Mon, 10 Jul 2006 10:14:26 GMT
Until we see a stack trace there's not much for us to go on - e.g. it
could be in your consumer code for all we know. StackOverflowError can
happen if you have excessive recursion in your code.

On 7/10/06, Fredrik Jonson <fredrik@myrealbox.com> wrote:
> I wrote:
>
> > The strange thing is that sometimes, say every two minutes or so, I saw
> > a warning from the message listener, that it could not process a message
> > due to a StackOverflowError.
> >
> > 2006-07-07 15:51:12,336  WARN [JmsSessionDispatcher: 1]
> > (ActiveMQMessageConsumer.java:464) org.activemq.ActiveMQMessageConsumer -
> > could not process message: ACTIVEMQ_OBJECT_MESSAGE: [...]
> > Reason: java.lang.StackOverflowError java.lang.StackOverflowError
>
> Just a small followup on myself here.
>
> I was a bit surprised that the StackOverflowError didn't produce an stack
> trace. After a bit of research I suspect that it is an bug in the Sun 1.4.2
> library. I haven't had time to try it out myself, but a work around should be
> to upgrade to Java 1.5 or to run the jvm in interpreted mode, ie with the
> argument -Xint. Both should produce a stack trace.
>
> --
> Fredrik Jonson
>
>


-- 

James
-------
http://radio.weblogs.com/0112098/

Mime
View raw message