[
https://issues.apache.org/jira/browse/AMQ-6262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15256073#comment-15256073
]
ASF GitHub Bot commented on AMQ-6262:
-------------------------------------
GitHub user pbruski opened a pull request:
https://github.com/apache/activemq/pull/181
AMQ-6262 - HTTP transport broken in 5.12
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/atlassian/activemq
AMQ-6262-fix-inactivity-monitor-for-http
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/activemq/pull/181.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #181
----
commit c7f46503305b06abc1ddff49e1e2de467bb72d49
Author: Przemek Bruski <[email protected]>
Date: 2016-04-25T08:32:54Z
AMQ-6262 - HTTP transport broken in 5.12
----
> HTTP transport broken in 5.12
> -----------------------------
>
> Key: AMQ-6262
> URL: https://issues.apache.org/jira/browse/AMQ-6262
> Project: ActiveMQ
> Issue Type: Bug
> Affects Versions: 5.12.0, 5.12.1, 5.13.0, 5.12.2, 5.13.1, 5.12.3, 5.13.2
> Reporter: Przemek Bruski
> Priority: Critical
>
> A regression from https://issues.apache.org/jira/browse/AMQ-5794 .
> Connection watchdog is started for every initiated connection and stopped on
> WireFormatInfo command. HTTP transport doesn't send WireFormatInfo so the
> watchdog never realises that the connection has been successfully established.
> The connection gets terminated every 30seconds by the watchdog.
> At the beginning, everything looks fine, but then you start getting
> exceptions and start losing packets. I haven't seen that myself, but I had
> people reporting that if HTTP transports are in use, it eventually
> destabilises the broker and affects non-HTTP transports too.
> {noformat}
> 2016-04-22 10:32:46.029244500 2016-04-22 10:32:46,029 WARN [ActiveMQ
> InactivityMonitor Worker] [Transport] Transport Connection to:
> blockingQueue_28120594 failed:
> org.apache.activemq.transport.InactivityIOException: Channel was inactive
> 2016-04-22 10:33:30.988313500
> org.apache.activemq.transport.InactivityIOException: Channel was inactive (no
> connection attempt made) for too (>30000) long: blockingQueue_21644517
> 2016-04-22 10:33:30.988637500 at
> org.apache.activemq.transport.AbstractInactivityMonitor$1$1.run(AbstractInactivityMonitor.java:91)
> 2016-04-22 10:33:30.988667500 at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> 2016-04-22 10:33:30.988689500 at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> 2016-04-22 10:33:30.988717500 at java.lang.Thread.run(Thread.java:745)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
