Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Date: Mon, 25 Feb 2013 06:46:17 +0000 (UTC)
From: "Tamilmaran (JIRA)" <jira@apache.org>
To: dev@activemq.apache.org
Message-ID: <JIRA.12633203.1361371059821.331557.1361774777061@arcas>
In-Reply-To: <JIRA.12633203.1361371059821@arcas>
References: <JIRA.12633203.1361371059821@arcas>
Subject: [jira] [Updated] (AMQ-4336) SocketException: Connection reset
 exception occurred in ActiveMQ for Bulk message producer
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Tamilmaran updated AMQ-4336:
----------------------------

    Priority: Blocker  (was: Major)
    
> 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.xml, WAPSimulator.rar
>
>
> I have a Bulk MSG producer which sends 1000 messages for every 4 seconds.
> 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