Great, thanks for the investigation, and for updating the bug.
Tim
On Mon, Apr 23, 2018, 12:51 AM sue wrote:
> Dear Tim,
>
> In the meantime, I found the cause for the problem which was introduced to
> the client in version 5.14.1 with the following commit:
>
> https://git-wip-us.apache.org/rep
Dear Tim,
In the meantime, I found the cause for the problem which was introduced to
the client in version 5.14.1 with the following commit:
https://git-wip-us.apache.org/repos/asf?p=activemq.git;h=06e929f
There, a default socket timesout of 30 seconds was added which conflicts
with the time it
Thanks for submitting the bug. Which versions before 5.15.3 did you test,
so we can update the Affects Version to reflect your findings?
Also, did you downgrade the broker as well, or just the client (leaving the
broker at 5.15.3)? What you wrote sounds like you only changed the client
but not the
A quick update for anyone having the same issue.
The cause was a bug in the activemq client that exists since version 5.14,
see https://issues.apache.org/jira/browse/AMQ-6949
I managed to get the HTTP connection working by downgrading to the 5.13.4
client
--
Sent from: http://activemq.2283324
Dear Tim,
Thank you for your reply.
My message indeed seems to have been corrupted somehow.
In the meantime I managed to narrow the problem down quite a bit and I can
provide more information.
For my setup I am running the ActiveMQ Message Broker 5.15.3 locally on my
Windows system. I took the
Samuel,
It appears that the relevant sections of your message were stripped out
somehow. Can you re-send the message with them included?
Also, there are elements of the JIRA bug you linked to that don't match the
scenario you described: that bug is occurring after a broker restart, and
on broker-
