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

Tamilmaran commented on AMQ-4336:
---------------------------------

System configuration (in which ActiveMQ runs):-

Processor:      Intel(R) Xeon(TM) CPU 2.80GHz, 2793 Mhz, 1 Core(s), 2 Logical 
Processor(s)
OS Name:        Microsoft Windows Server 2008 R2 Standard
RAM:            2GB
System Type:    x64-based PC
System Name:    INCHN-MCC01

                
> 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, 
> Test2-activemq.log
>
>
> 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

Reply via email to