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: Session closed after a while(random)
Date Thu, 13 Jul 2006 19:05:10 GMT
Maybe try run your code in a debugger and set breakpoints in the
ActiveMQSession class to see where & why the session gets closed? (The
code's pretty easy to follow, its a relatively simple class).


On 7/13/06, Adrian Tarau <ady@daxtechnologies.com> wrote:
> James, do you want the sources or can you recommend me some actions? To
> create the session all the time, not to cache it?
>
> Adrian Tarau wrote:
> > Ok, so who close the session? :)
> >
> > James Strachan wrote:
> >> Sorry I forgot about that :)
> >>
> >> The only time a VM broker is shut down is explicitly via application
> >> code or a shutdown handler.
> >>
> >> On 7/13/06, Adrian Tarau <ady@daxtechnologies.com> wrote:
> >>> I use vm connector so no connection problems should be involved, right?
> >>>
> >>> James Strachan wrote:
> >>> > BTW are you using auto-reconnect? It could be that the socket is
> >>> > terminated due to some network issue?
> >>> >
> >>> >
> >>> http://incubator.apache.org/activemq/how-can-i-support-auto-reconnection.html
> >>>
> >>> >
> >>> >
> >>> > On 7/13/06, Adrian Tarau <ady@daxtechnologies.com> wrote:
> >>> >> I made a search for "close" in the source code and except from
> >>> produces,
> >>> >> consumers and inputstream and outputstream I don't close the
> >>> connection
> >>> >> or session, except on the JVM shutdown(Thread hook).
> >>> >>
> >>> >> I can provide you(private - not on the mailing list) the source
code
> >>> >> because this is very annoying.
> >>> >> Thanks.
> >>> >>
> >>> >> James Strachan wrote:
> >>> >> > Apart from inactivity timeouts on the transport layer, we
> >>> generally
> >>> >> > don't close sessions. Are you sure nothing in your application
> >>> code is
> >>> >> > trying to close the session?
> >>> >> >
> >>> >> > On 7/13/06, Adrian Tarau <ady@daxtechnologies.com> wrote:
> >>> >> >> I have this issue for some time with ActiveMQ 4.0 and
4.0.1.
> >>> >> >>
> >>> >> >> I use vm transport and create one session used to produce
and
> >>> consume
> >>> >> >> messages. Everything works fine, days in a row, until
it start to
> >>> >> throw
> >>> >> >> exception that "Session is closed". There are any watch
dogs that
> >>> >> close
> >>> >> >> sessions after a while, based on some criteria?
> >>> >> >>
> >>> >> >> I couldn't find any rule, when or why it happens.
> >>> >> >> Should I create the session all the time - I understood
 is time
> >>> >> >> consuming and it should be safe to cache it.
> >>> >> >>
> >>> >> >> Thanks.
> >>> >> >>
> >>> >> >> *javax.jms.IllegalStateException: The Session is closed
> >>> >> >>     at
> >>> >> >>
> >>> >>
> >>> org.apache.activemq.ActiveMQSession.checkClosed(ActiveMQSession.java:577)
> >>>
> >>> >>
> >>> >> >>
> >>> >> >>     at
> >>> >> >>
> >>> >>
> >>> org.apache.activemq.ActiveMQSession.createConsumer(ActiveMQSession.java:799)*
> >>>
> >>> >>
> >>> >> >>
> >>> >> >>
> >>> >> >>
> >>> >> >
> >>> >> >
> >>> >>
> >>> >>
> >>> >
> >>> >
> >>>
> >>>
> >>
> >>
> >
>
>


-- 

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

Mime
View raw message