Tim how can I provide with more detailed logs? I can try and adjust broker side
to have more debugs but client is unlikely to extend its messages
Thx
Marcin
Od: "Timothy Bish"
Do: "users"
Wysłane: środa, 26 kwiecień 2017 22:16:34
Temat: Re: Occasionally EOF on c
t connection level but I can't find how to do this
without global DEBUG/TRACE option ?
Thx
Marcin
Od: "Tim Bain"
Do: "users"
Wysłane: czwartek, 20 kwiecień 2017 7:04:07
Temat: Re: Occasionally EOF on connection
Nothing in your configuration looks obviously wrong to me
ls on transport connection level but I can't find how to do this
> without global DEBUG/TRACE option ?
>
> Thx
> Marcin
>
>
> Od: "Tim Bain"
> Do: "users"
> Wysłane: czwartek, 20 kwiecień 2017 7:04:07
> Temat: Re: Occasionally EOF on conne
can also change log4j in AMQ broker to log more details on transport
connection level but I can't find how to do this without global DEBUG/TRACE
option ?
Thx
Marcin
Od: "Tim Bain"
Do: "users"
Wysłane: czwartek, 20 kwiecień 2017 7:04:07
Temat: Re: Occasion
Nothing in your configuration looks obviously wrong to me.
Is the connection between your broker and the clients that are having
problems unstable during the period of time that these problems are
occurring? Simultaneous EOFs on both ends of a socket connection makes me
think of packet loss or net
Hello all,
in our framework we use AMQ 5.14.1 and CMS version 3.9.4. From time to time we
observe connection drops on client's side like the one below:
20170418 10:00:41.902 CRITICAL: void
CMSConnectionManager::sltConnectionError(CMSExceptionListener::errorType,
QString) "DataInputStream::re
