Apologies, I made the (incorrect) assumption they were broker logs... :-)

It's possible that these Detach/Ends are not actually being sent then, but
are just a response to the TCP connection dropping (the SEND is logged not
as things go on the wire, but at the point where the intent is to send, a
TCP connection detach will be treated as an abrupt remote connect close
which will trigger the sessions/links to be asked to detach/end
themselves).  Do you have the broker side log at all - does that say
anything?

In terms of configuring heartbeats, there is currently no way of
configuring the client to require heartbeats... the client will honour
requests from the server to sent heartbeats... so if you can configure
ActiveMQ to request heartbeats then the client will send them.

-- Rob

On 18 February 2015 at 15:59, Erik Aschenbrenner <easch...@icubic.de> wrote:

> Hi Rob,
>
> thanks for the answer.
>
> But the problem is that im trying to send a message at 2015-02-18
> 12:36:18.925 and after that, the detaches are logged. So the detaches are
> triggered by the client and not the broker? Why?
>
> Here are the last to lines from the RAW log:
>
> 2015-02-18 11:50:43.696: somthing cryptic sent and I leaved for lunch ;-)
> 2015-02-18 12:36:18.925: I send a messag to the broker got the session
> ended
> error.
>
>
>
> Maybe heartbeats could help to avoid the session loss? How can they be
> turned on for the QPID AMQP 1.0 JMS client (Java) by the way?
>
> Regards,
> Erik
>
>
>
>
>
> --
> View this message in context:
> http://qpid.2158936.n2.nabble.com/QPID-JMS-Java-Client-no-exception-when-session-is-remotely-ended-tp7620473p7620496.html
> Sent from the Apache Qpid users mailing list archive at Nabble.com.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
> For additional commands, e-mail: users-h...@qpid.apache.org
>
>

Reply via email to