Effective October 27, 2012, online and email support for FuseSource products will move to Red Hat support channels. For more information, please see the JIRA Migration to Red Hat FAQ.
As of October 27th, please open all new issues in the Red Hat Customer Portal .
Issue Details (XML | Word | Printable)

Key: MB-605
Type: Improvement Improvement
Status: Open Open
Priority: Major Major
Assignee: Hiram Chirino
Reporter: Hiram Chirino
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
FUSE Message Broker

Stacktrace showing in WARN level logging. Since it is diagnostic information, it should only be displayed at debug level.

Created: 25/Nov/09 12:22 PM   Updated: 25/Nov/09 12:23 PM
Component/s: broker
Affects Version/s: 5.3.0-psc-01-00M2
Fix Version/s: None


 Description  « Hide 
07:18:58 [REMOTE] BROKER1: 07:18:58 WARN  DemandForwardingBridge: Caught an exception processing local command 
07:18:58 [REMOTE] BROKER1: java.net.SocketException: Broken pipe 
07:18:58 [REMOTE] BROKER1: 	at java.net.SocketOutputStream.socketWrite0(Native Method) 
07:18:58 [REMOTE] BROKER1: 	at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92) 
07:18:58 [REMOTE] BROKER1: 	at java.net.SocketOutputStream.write(SocketOutputStream.java:136) 
07:18:58 [REMOTE] BROKER1: 	at org.apache.activemq.transport.tcp.TcpBufferedOutputStream.flush(TcpBufferedOutputStream.java:115) 
07:18:58 [REMOTE] BROKER1: 	at java.io.DataOutputStream.flush(DataOutputStream.java:106) 
07:18:58 [REMOTE] BROKER1: 	at org.apache.activemq.transport.tcp.TcpTransport.oneway(TcpTransport.java:167) 
07:18:58 [REMOTE] BROKER1: 	at org.apache.activemq.transport.InactivityMonitor.oneway(InactivityMonitor.java:237) 
07:18:58 [REMOTE] BROKER1: 	at org.apache.activemq.transport.TransportFilter.oneway(TransportFilter.java:83) 
07:18:58 [REMOTE] BROKER1: 	at org.apache.activemq.transport.WireFormatNegotiator.oneway(WireFormatNegotiator.java:104) 
07:18:58 [REMOTE] BROKER1: 	at org.apache.activemq.transport.MutexTransport.oneway(MutexTransport.java:40) 
07:18:58 [REMOTE] BROKER1: 	at org.apache.activemq.transport.ResponseCorrelator.oneway(ResponseCorrelator.java:60) 
07:18:58 [REMOTE] BROKER1: 	at org.apache.activemq.network.DemandForwardingBridgeSupport.serviceLocalCommand(DemandForwardingBridgeSupport.java:702) 
07:18:58 [REMOTE] BROKER1: 	at org.apache.activemq.network.DemandForwardingBridgeSupport$1.onCommand(DemandForwardingBridgeSupport.java:158) 
07:18:58 [REMOTE] BROKER1: 	at org.apache.activemq.transport.ResponseCorrelator.onCommand(ResponseCorrelator.java:116) 
07:18:58 [REMOTE] BROKER1: 	at org.apache.activemq.transport.TransportFilter.onCommand(TransportFilter.java:68) 
07:18:58 [REMOTE] BROKER1: 	at org.apache.activemq.transport.vm.VMTransport.oneway(VMTransport.java:113) 
07:18:58 [REMOTE] BROKER1: 	at org.apache.activemq.transport.MutexTransport.oneway(MutexTransport.java:40) 
07:18:58 [REMOTE] BROKER1: 	at org.apache.activemq.transport.ResponseCorrelator.oneway(ResponseCorrelator.java:60) 
07:18:58 [REMOTE] BROKER1: 	at org.apache.activemq.broker.TransportConnection.dispatch(TransportConnection.java:1195) 
07:18:58 [REMOTE] BROKER1: 	at org.apache.activemq.broker.TransportConnection.processDispatch(TransportConnection.java:779) 
07:18:58 [REMOTE] BROKER1: 	at org.apache.activemq.broker.TransportConnection.iterate(TransportConnection.java:815) 
07:18:58 [REMOTE] BROKER1: 	at org.apache.activemq.thread.PooledTaskRunner.runTask(PooledTaskRunner.java:122) 
07:18:58 [REMOTE] BROKER1: 	at org.apache.activemq.thread.PooledTaskRunner$1.run(PooledTaskRunner.java:43) 
07:18:58 [REMOTE] BROKER1: 	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) 
07:18:58 [REMOTE] BROKER1: 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) 
07:18:58 [REMOTE] BROKER1: 	at java.lang.Thread.run(Thread.java:637)

 All   Comments   Change History      Sort Order: Ascending order - Click to sort in descending order
[ Permlink | « Hide ]
Hiram Chirino added a comment - 25/Nov/09 12:23 PM
The above stack trace is a normal error condition when the network fails between two networked brokers. It should not be dumping the stack trace like that.


Powered by Atlassian JIRA the Professional Issue Tracker. (Enterprise Edition, Version: 3.13.2-#335) - Bug/feature request - Atlassian news - Contact Administrators