You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Tamilmaran (JIRA)" <ji...@apache.org> on 2013/02/26 07:50:15 UTC

[jira] [Comment Edited] (AMQ-4336) SocketException: Connection reset exception occurred in ActiveMQ for Bulk message producer

    [ https://issues.apache.org/jira/browse/AMQ-4336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13586869#comment-13586869 ] 

Tamilmaran edited comment on AMQ-4336 at 2/26/13 6:49 AM:
----------------------------------------------------------

Modified Bulk Message Producer
                
      was (Author: tamilmaran):
    Bulk Message Producer
                  
> SocketException: Connection reset exception occurred in ActiveMQ for Bulk message producer
> ------------------------------------------------------------------------------------------
>
>                 Key: AMQ-4336
>                 URL: https://issues.apache.org/jira/browse/AMQ-4336
>             Project: ActiveMQ
>          Issue Type: Bug
>         Environment: ActiveMQ 5.6,NMS,C#
>            Reporter: Tamilmaran
>            Priority: Blocker
>         Attachments: activemq.log, activemq.xml, SimulatorTC.rar
>
>
> I have a Bulk MSG producer which sends 1000 messages for every 4 seconds. And a durable subscriber in server side but not sure about its speed to consume all the messages in same rate as well as the producer.
> But after an hour, 'Connection is already closed' error is logged on producer side.
> On ActiveMQ side, Following error has been logged.
> 2013-02-18 21:45:45,149 | WARN  | Transport Connection to: tcp://10.2.44.73:59355 failed: java.net.SocketException: Connection reset | org.apache.activemq.broker.TransportConnection.Transport | ActiveMQ Transport: ssl:///10.2.44.73:59355
> 10.2.44.73-> Bulk MSG producer IP
> ActiveMQ is using File based cursor and producer control.
> Attached activeMQ config file and producer app(WAPSimulator)

--
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