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-to-broker networkConnectors, neither of which you've described so far as your situation. So although it's certainly possible that what you're seeing is the same thing that bug describes, it doesn't seem like a strong match to me. The bug I initially thought of when reading this (without the benefit of seeing the exception text and broker configuration) was https://issues.apache.org/jira/browse/AMQ-6262, but that's fixed in 5.13 and 5.14, so you shouldn't be seeing it in 5.15.3. Could this be caused by a firewall (allowing traffic in but not back out) or by your HTTP proxy itself? On which host did you do your Wireshark observation, broker or client? If you use it to observe on both hosts at once, do you see the same traffic on both, or do packets leave one host but never arrive at the other? Tim On Wed, Apr 18, 2018, 8:13 AM sue <samuel.uelts...@bsi-software.com> wrote: > Hi, > > I'm having troubles connecting to ActiveMQ using the HTTP connector. The > problem happenes on ActiveMQ 5.15.3 > > My activemq.xml defines to following connectors: > > > > My application creates several queues and subscribes to changes. > This works fine when using openwire, but the HTTP connector fails with the > following excpetion after 30 seconds: > > > > > Interestingly, the connection initially works. I see the packages going > over > the wire using wireshark. But after 30 seconds, one GET request times out > after 30 seconds. > > The following Jira Ticket looks somewhat similar: > https://issues.apache.org/jira/browse/AMQ-6557 > But this has been open and unassigned since January 2017. > > Does anyone have any suggestion on how to resolve this problem? I can > produce additional logfiles if needed. > Unfortunately I can't just use a binary protocol because the traffic has to > go through a HTTP proxy. > > Any help is greatly appreciated. > > Cheers > Samuel > > > > -- > Sent from: > http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html >
