You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Erik Drolshammer (JIRA)" <ji...@apache.org> on 2009/02/17 11:25:00 UTC
[jira] Created: (AMQ-2119) SocketException: Broken pipe should be
logged as warning not debug
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.
[jira] Resolved: (AMQ-2119) SocketException: Broken pipe should be
logged as warning not debug
Posted by "Gary Tully (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-2119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gary Tully resolved AMQ-2119.
-----------------------------
Assignee: Gary Tully
Resolution: Fixed
resolved in r983584 - now at INFO level
> 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
> Assignee: Gary Tully
> Fix For: 5.4.0
>
>
> 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.
[jira] Updated: (AMQ-2119) SocketException: Broken pipe should be
logged as warning not debug
Posted by "Rob Davies (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-2119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rob Davies updated AMQ-2119:
----------------------------
Fix Version/s: 5.4.0
> 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
> Fix For: 5.4.0
>
>
> 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.