activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Erik Drolshammer (JIRA)" <j...@apache.org>
Subject [jira] Created: (AMQ-2119) SocketException: Broken pipe should be logged as warning not debug
Date Tue, 17 Feb 2009 10:25:00 GMT
SocketException: Broken pipe should be logged as warning not debug
------------------------------------------------------------------

                 Key: AMQ-2119
                 URL: https://issues.apache.org/activemq/browse/AMQ-2119
             Project: ActiveMQ
          Issue Type: Bug
          Components: Broker
    Affects Versions: 5.2.0
         Environment: red hat 
            Reporter: Erik Drolshammer


Network problems are imho important. Can they be logged at WARN instead of debug? 

2009-02-17 08:57:43,241 DEBUG [broker.TransportConnection.Transport] Transport failed: java.net.SocketException:
Broken pipe
java.net.SocketException: Broken pipe
        at java.net.SocketOutputStream.socketWrite0(Native Method)
        at java.net.SocketOutputStream.socketWrite(Unknown Source)
        at java.net.SocketOutputStream.write(Unknown Source)
        at org.apache.activemq.transport.tcp.TcpBufferedOutputStream.flush(TcpBufferedOutputStream.java:115)
        at java.io.DataOutputStream.flush(Unknown Source)
        at org.apache.activemq.transport.tcp.TcpTransport.oneway(TcpTransport.java:167)
        at org.apache.activemq.transport.InactivityMonitor.oneway(InactivityMonitor.java:233)
        at org.apache.activemq.transport.InactivityMonitor$3.run(InactivityMonitor.java:135)
        at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
        at java.lang.Thread.run(Unknown Source) 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message