Shital Khedkar created AMQ-6999:
-----------------------------------

             Summary: Getting error after some time in ActiveMQ
                 Key: AMQ-6999
                 URL: https://issues.apache.org/jira/browse/AMQ-6999
             Project: ActiveMQ
          Issue Type: Bug
          Components: Broker
    Affects Versions: 5.14.4
            Reporter: Shital Khedkar
         Attachments: activemq.xml, extracted_activemq_log.txt

Hi Team,

We are using Apache ActiveMQ version 5.14.4 in our one of application. We are 
getting below errors on one of our environment :



2018-06-01 00:34:04,664 | WARN | Transport Connection to: tcp://127.0.0.1:15253 
failed: java.io.EOFException | 
org.apache.activemq.broker.TransportConnection.Transport | ActiveMQ Transport: 
tcp:///127.0.0.1:15253@61616
2018-06-01 00:43:41,714 | WARN | Transport Connection to: tcp://127.0.0.1:15251 
failed: java.net.SocketException: Broken pipe (Write failed) | 
org.apache.activemq.broker.TransportConnection.Transport | ActiveMQ 
InactivityMonitor Worker
2018-06-01 00:41:50,372 | WARN | Transport Connection to: tcp://127.0.0.1:15257 
failed: java.net.SocketException: Broken pipe (Write failed) | 
org.apache.activemq.broker.TransportConnection.Transport | ActiveMQ 
InactivityMonitor Worker
2018-06-01 00:46:29,265 | INFO | Waited 2.384 seconds for ExecutorService: 
java.util.concurrent.ThreadPoolExecutor@ef3e7c[Shutting down, pool size = 3, 
active threads = 3, queued tasks = 0, completed tasks = 21821] to terminate... 
| org.apache.activemq.util.ThreadPoolUtils | ActiveMQ InactivityMonitor Worker
2018-06-01 01:07:18,895 | WARN | Forcing shutdown of ExecutorService: 
java.util.concurrent.ThreadPoolExecutor@ef3e7c[Shutting down, pool size 1, 
active threads = 1, queued tasks = 0, completed tasks = 21823] due first await 
termination elapsed. | org.apache.activemq.util.ThreadPoolUtils | ActiveMQ 
InactivityMonitor Worker
2018-06-01 01:20:32,847 | WARN | Forcing shutdown of ExecutorService: 
java.util.concurrent.ThreadPoolExecutor@ef3e7c[Shutting down, pool size = 1, 
active threads = 1, queued tasks = 0, completed tasks = 21823] due first await 
termination elapsed. | org.apache.activemq.util.ThreadPoolUtils | ActiveMQ 
InactivityMonitor Worker

2018-06-17 13:31:23,040 | WARN | Transport Connection to: tcp://127.0.0.1:47415 
failed: java.io.EOFException | 
org.apache.activemq.broker.TransportConnection.Transport | ActiveMQ Transport: 
tcp:///127.0.0.1:47415@61616
2018-06-17 13:31:23,510 | WARN | Transport Connection to: tcp://127.0.0.1:47417 
failed: java.io.EOFException | 
org.apache.activemq.broker.TransportConnection.Transport | ActiveMQ Transport: 
tcp:///127.0.0.1:47417@61616
2018-06-17 13:31:23,512 | WARN | Transport Connection to: tcp://127.0.0.1:47413 
failed: java.io.EOFException | 
org.apache.activemq.broker.TransportConnection.Transport | ActiveMQ Transport: 
tcp:///127.0.0.1:47413@61616
2018-06-18 09:23:23,841 | WARN | Transport Connection to: tcp://127.0.0.1:30049 
failed: java.net.SocketException: Connection reset | 
org.apache.activemq.broker.TransportConnection.Transport | ActiveMQ Transport: 
tcp:///127.0.0.1:30049@61616
2018-06-18 09:23:23,940 | WARN | Transport Connection to: tcp://127.0.0.1:30047 
failed: java.io.EOFException | 
org.apache.activemq.broker.TransportConnection.Transport | ActiveMQ Transport: 
tcp:///127.0.0.1:30047@61616
2018-06-18 13:43:58,188 | WARN | Transport Connection to: tcp://127.0.0.1:30247 
failed: java.io.EOFException | 
org.apache.activemq.broker.TransportConnection.Transport | ActiveMQ Transport: 
tcp:///127.0.0.1:30247@61616
2018-06-18 13:43:58,672 | WARN | Transport Connection to: tcp://127.0.0.1:30251 
failed: java.io.EOFException | 
org.apache.activemq.broker.TransportConnection.Transport | ActiveMQ Transport: 
tcp:///127.0.0.1:30251@61616
2018-06-18 13:43:58,672 | WARN | Transport Connection to: tcp://127.0.0.1:30249 
failed: java.io.EOFException | 
org.apache.activemq.broker.TransportConnection.Transport | ActiveMQ Transport: 
tcp:///127.0.0.1:30249@61616

 

Can you please help us on this, what we can do it to resolve above issue.

 

Thanks in adavance



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to