Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Date: Tue, 14 Jan 2014 15:15:55 +0000 (UTC)
From: "Timothy Bish (JIRA)" <jira@apache.org>
To: dev@activemq.apache.org
Message-ID: <JIRA.12630553.1359847962963.94264.1389712555966@arcas>
In-Reply-To: <JIRA.12630553.1359847962963@arcas>
References: <JIRA.12630553.1359847962963@arcas>
Subject: [jira] [Closed] (AMQ-4294) Client Hang on large payloads of size
 1-4MB
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/AMQ-4294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Timothy Bish closed AMQ-4294.
-----------------------------

    Resolution: Incomplete

No test case provided. 

> Client Hang on large payloads of size 1-4MB
> -------------------------------------------
>
>                 Key: AMQ-4294
>                 URL: https://issues.apache.org/jira/browse/AMQ-4294
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Transport
>    Affects Versions: 5.7.0
>         Environment: RHEL 6.3
>            Reporter: Mohit Anchlia
>            Priority: Critical
>         Attachments: client.log.gz, mq-conf-mule.txt, mq.log.tar.gz
>
>
> We have been debugging this issue for a while. It appears that activmq client just hangs on MQ and then eventually inactivity timer kicks off and kills the connection. We are using NIO but this behaviour is very wierd. When we have low load we don't see this issue but when our load increses we see that the client hangs waiting on MQ. We see lot of killed connections in MQ logs. I am attaching logs


--
This message was sent by Atlassian JIRA
(v6.1.5#6160)