Jeremy Whiting [http://community.jboss.org/people/whitingjr] created the discussion "Broken pipe during high message load." To view the discussion, visit: http://community.jboss.org/message/563802#563802 -------------------------------------------------------------- Hi, I am running SPECjms2007 benchmark against JBoss Messaging. The benchmark is detecting an error during the benchmark run. This issue has been reported previously on the forum though the issue should be fixed in the current latest (as of Sept 2010) release. The client side reports the following problem. SM_Interaction4DR_17_EHID_2: Uncaught exception. org.jboss.jms.exception.MessagingTransactionRolledBackException: Failed to invoke     at org.jboss.jms.tx.ResourceManager.commitLocal(ResourceManager.java:225)     at org.jboss.jms.client.container.SessionAspect.handleCommit(SessionAspect.java:582)     at org.jboss.aop.advice.org.jboss.jms.client.container.SessionAspect_z_handleCommit_72769750.invoke(SessionAspect_z_handleCommit_72769750.java)     at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)     at org.jboss.jms.client.container.ClosedInterceptor.invoke(ClosedInterceptor.java:172)     at org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:86)     at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)     at org.jboss.jms.client.delegate.ClientSessionDelegate.commit(ClientSessionDelegate.java)     at org.jboss.jms.client.JBossSession.commit(JBossSession.java:164)     at org.spec.jms.eventhandler.sm.SM_Interaction4DR.oneIteration(SM_Interaction4DR.java:169)     at org.spec.perfharness.WorkerThread.pace(WorkerThread.java:339)     at org.spec.jms.agents.SPECWorkerThread.pace(SPECWorkerThread.java:979)     at org.spec.jms.agents.SPECWorkerThread.run(SPECWorkerThread.java:750)     at org.spec.jms.eventhandler.sm.SM_Interaction4DR.run(SM_Interaction4DR.java:135) Caused by: org.jboss.jms.exception.MessagingJMSException: Failed to invoke     at org.jboss.jms.client.delegate.DelegateSupport.handleThrowable(DelegateSupport.java:271)     at org.jboss.jms.client.delegate.DelegateSupport.doInvoke(DelegateSupport.java:205)     at org.jboss.jms.client.delegate.DelegateSupport.doInvoke(DelegateSupport.java:160)     at org.jboss.jms.client.delegate.ClientConnectionDelegate.org$jboss$jms$client$delegate$ClientConnectionDelegate$sendTransaction$aop(ClientConnectionDelegate.java:225)     at org.jboss.jms.client.delegate.ClientConnectionDelegate$sendTransaction_N3268650789275322226.invokeTarget(ClientConnectionDelegate$sendTransaction_N3268650789275322226.java)     at org.jboss.aop.joinpoint.MethodInvocati on.invokeNext(MethodInvocation.java:111)     at org.jboss.jms.client.container.FailoverValveInterceptor.invoke(FailoverValveInterceptor.java:92)     at org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:86)     at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)     at org.jboss.jms.client.container.ClosedInterceptor.invoke(ClosedInterceptor.java:172)     at org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:86)     at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)     at org.jboss.jms.client.delegate.ClientConnectionDelegate.sendTransaction(ClientConnectionDelegate.java)     at org.jboss.jms.tx.ResourceManager.commitLocal(ResourceManager.java:206)     ... 13 more Caused by: java.lang.IllegalStateException: Cannot find object in dispatcher with id za1-h9rkileg-1-eafiileg-hcwsz7-100j3     at org.jboss.jms.wireformat.ConnectionSendTransactionRequest.serverInvoke(ConnectionSendTransactionRequest.java:79)     at org.jboss.jms.server.remoting.JMSServerInvocationHandler.invoke(JMSServerInvocationHandler.java:157)     at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:930)     at org.jboss.remoting.transport.socket.ServerThread.completeInvocation(ServerThread.java:791)     at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:744)     at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:586)     at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:234)     at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:216)     at org.jboss.remoting.Client.invoke(Client.java:2034)     at org.jboss.remoting.Client.invoke(Client.java:877)     at org.jboss.remoting.Client.invoke(Client.java:865)     at org.jboss.jms.client.delegate.DelegateSupport.doInvoke(DelegateSupport.java:189)     ... 25 more SM_Interaction4DR_17_EHID_2: Closing producer JBossMessageProducer->ProducerDelegate[921505790, ID=NO_ID_SET] SM_Interaction4DR_17_EHID_2: Closing session JBossSession->SessionDelegate[1457428868, ID=0b1-i9rkileg-1-eafiileg-hcwsz7-100j3] SM_Interaction4DR_17_EHID_2: connection-pool: Removing JMS connection from pool JBossConnection->ConnectionDelegate[474307371, ID=za1-h9rkileg-1-eafiileg-hcwsz7-100j3, SID=0] SM_Interaction4DR_17_EHID_2: STOP The server log has many Broken Pipe error messages, here is one example 2010-09-27 12:01:25,746 WARN  [org.jboss.remoting.transport.bisocket.BisocketClientInvoker] (Timer-4) Unable to send ping: shutting down PingTimerTask java.net.SocketException: Broken pipe     at java.net.SocketOutputStream.socketWrite0(Native Method)     at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:109)     at java.net.SocketOutputStream.write(SocketOutputStream.java:132)     at org.jboss.remoting.transport.bisocket.BisocketClientInvoker$PingTimerTask.run(BisocketClientInvoker.java:723)     at java.util.TimerThread.mainLoop(Timer.java:534)     at java.util.TimerThread.run(Timer.java:484) JBM version:1.4.7.GA OS:RHEL 5.5 Java:java version "1.6.0_0" OpenJDK Runtime Environment (IcedTea6 1.6) (rhel-1.13.b16.el5-x86_64) OpenJDK 64-Bit Server VM (build 14.0-b16, mixed mode) Database: MySQL 5.1.50 community Jeremy -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/563802#563802] Start a new discussion in JBoss Messaging at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&...]