[
https://issues.apache.org/jira/browse/AMQ-6262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15257101#comment-15257101
]
ASF subversion and git services commented on AMQ-6262:
------------------------------------------------------
Commit 0c3d05f2eac40902fc252cb6cff4997f00b1b053 in activemq's branch
refs/heads/activemq-5.13.x from [~tabish121]
[ https://git-wip-us.apache.org/repos/asf?p=activemq.git;h=0c3d05f ]
https://issues.apache.org/jira/browse/AMQ-6262
Ensure that the connection check task is stopped once commands pass
through the inactivity monitor to prevent the transport from being
closed for no reason.
(cherry picked from commit e47edd7a282e1391f480c1278555f4a86e9a8ea9)
> 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
> Fix For: 5.14.0, 5.13.3
>
>
> 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)
