You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Mohit Anchlia (JIRA)" <ji...@apache.org> on 2013/02/03 00:38:12 UTC

[jira] [Updated] (AMQ-4294) Client Hang on large payloads of size 1-4MB

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

Mohit Anchlia updated AMQ-4294:
-------------------------------

    Attachment: client.log.gz
                mq.log.tar.gz
                mq-conf-mule.txt

Please find the stack traces, logs and conf files
                
> 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 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