[
https://issues.apache.org/jira/browse/AMQ-3281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13113227#comment-13113227
]
Erkan commented on AMQ-3281:
----------------------------
I tested it with the 5.6-SNAPSHOT and it is the same effect. I get the
following warnings:
| WARN | Transport failed: java.io.EOFException
WARN | Transport failed: java.net.SocketException: Connection reset |
org.apache.activemq.broker.TransportConnection.Transport
WARN | Transport failed: java.net.SocketException: Software caused connection
abort: socket write error |
org.apache.activemq.broker.TransportConnection.Transport | Async Exception
Handler
WARN | Duplicate message add attempt rejected. Destination:
Can be the duplicate messages the reason so that the duplicate messages can not
be consume?
> Messages stuck
> --------------
>
> Key: AMQ-3281
> URL: https://issues.apache.org/jira/browse/AMQ-3281
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
> Affects Versions: 5.5.0
> Environment: Linux and Windows
> Reporter: Erkan
> Priority: Critical
> Fix For: 5.6.0
>
>
> Sometimes the messages stuck in queue and after restart of activemq then this
> messages redeliver to consumer. There are a lot of of topics:
> http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
> and this some of them:
> http://activemq.2283324.n4.nabble.com/Stuck-messages-Dispatch-issues-td2367852.html
> http://activemq.2283324.n4.nabble.com/Messages-stuck-in-queue-td3244342.html
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
