Return-Path: X-Original-To: apmail-activemq-dev-archive@www.apache.org Delivered-To: apmail-activemq-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 408A8EB01 for ; Sat, 2 Feb 2013 23:34:13 +0000 (UTC) Received: (qmail 97234 invoked by uid 500); 2 Feb 2013 23:34:13 -0000 Delivered-To: apmail-activemq-dev-archive@activemq.apache.org Received: (qmail 97130 invoked by uid 500); 2 Feb 2013 23:34:13 -0000 Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@activemq.apache.org Delivered-To: mailing list dev@activemq.apache.org Received: (qmail 97122 invoked by uid 99); 2 Feb 2013 23:34:13 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 02 Feb 2013 23:34:13 +0000 Date: Sat, 2 Feb 2013 23:34:12 +0000 (UTC) From: "Mohit Anchlia (JIRA)" To: dev@activemq.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (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 X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Mohit Anchlia created AMQ-4294: ---------------------------------- Summary: 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 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira