[jira] [Created] (AMQ-4336) Connection reset exception occurred on Bulk msg producer

[Tamilmaran (JIRA)]

Tamilmaran created AMQ-4336:
-------------------------------

             Summary: Connection reset exception occurred on Bulk msg 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


I have a Bulk MSG producer which sends 1000 messages for every 4 seconds.
But after an hour, Connection reset exception occurred for Bulk MSG producer:-

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.

ActiveMQ configuration:

<beans xmlns="http://www.springframework.org/schema/beans"; 
xmlns:amq="http://activemq.apache.org/schema/core"; 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; 
xsi:schemaLocation="http://www.springframework.org/schema/beans 
http://www.springframework.org/schema/beans/spring-beans-2.0.xsd
  http://activemq.apache.org/schema/core 
http://activemq.apache.org/schema/core/activemq-core.xsd";>

      <bean 
class="org.springframework.beans.factory.config.PropertyPlaceholderConfigurer">
        <property name="locations">
            <value>file:${activemq.conf}/credentials.properties</value>
        </property>
    </bean>

    <broker xmlns="http://activemq.apache.org/schema/core";  
brokerName="localhost" dataDirectory="${activemq.data}" 
offlineDurableSubscriberTimeout="21600000" 
offlineDurableSubscriberTaskSchedule="1800000">

       
        <destinationPolicy>
            <policyMap>
              <policyEntries>
                <policyEntry topic="&gt;" producerFlowControl="false" 
memoryLimit="900mb">
                  <pendingSubscriberPolicy>
                    <vmCursor/>
                  </pendingSubscriberPolicy>
                  <pendingDurableSubscriberPolicy>
                    <fileDurableSubscriberCursor/>
                  </pendingDurableSubscriberPolicy>
                </policyEntry>
                <policyEntry queue="&gt;" producerFlowControl="false" 
memoryLimit="20mb">

                </policyEntry>
              </policyEntries>
            </policyMap>
        </destinationPolicy>


        <managementContext>
            <managementContext createConnector="false"/>
        </managementContext>

      
        <persistenceAdapter>
            <kahaDB ignoreMissingJournalfiles="true" 
directory="${activemq.data}/kahadb"/>
        </persistenceAdapter>

          <systemUsage>
            <systemUsage sendFailIfNoSpaceAfterTimeout="15000">
                <memoryUsage>
                    <memoryUsage limit="900 mb"/>
                </memoryUsage>
                <storeUsage>
                    <storeUsage limit="100 gb"/>
                </storeUsage>
                <tempUsage>
                    <tempUsage limit="50 gb"/>
                </tempUsage>
            </systemUsage>
        </systemUsage>
        
        <sslContext>
                <sslContext keyStore="file:${activemq.conf}\broker.ks" 
keyStorePassword="HVObfvBd@zDo" trustStore="file:${activemq.conf}\client.ks" 
trustStorePassword="HVObfvBd@zDo"/> 
         </sslContext>


        <transportConnectors>
            <transportConnector name="openwire" uri="tcp://0.0.0.0:61616"/>
            <transportConnector name="ssl" uri="ssl://0.0.0.0:61617"/>
            <transportConnector name="stomp" uri="stomp://0.0.0.0:61613"/>
            <transportConnector name="stompssl" 
uri="stomp+ssl://0.0.0.0:61614"/> 
        </transportConnectors>

    </broker>

  
    <import resource="jetty.xml"/>

</beans>

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