Return-Path: Delivered-To: apmail-activemq-dev-archive@www.apache.org Received: (qmail 79439 invoked from network); 22 Sep 2010 09:42:08 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 22 Sep 2010 09:42:08 -0000 Received: (qmail 55250 invoked by uid 500); 22 Sep 2010 09:42:08 -0000 Delivered-To: apmail-activemq-dev-archive@activemq.apache.org Received: (qmail 55047 invoked by uid 500); 22 Sep 2010 09:42:06 -0000 Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@activemq.apache.org Delivered-To: mailing list dev@activemq.apache.org Received: (qmail 55039 invoked by uid 99); 22 Sep 2010 09:42:05 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 22 Sep 2010 09:42:05 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.22] (HELO thor.apache.org) (140.211.11.22) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 22 Sep 2010 09:42:04 +0000 Received: from thor (localhost [127.0.0.1]) by thor.apache.org (8.13.8+Sun/8.13.8) with ESMTP id o8M9fhlQ005477 for ; Wed, 22 Sep 2010 09:41:44 GMT Message-ID: <15137902.27641285148503817.JavaMail.jira@thor> Date: Wed, 22 Sep 2010 05:41:43 -0400 (EDT) From: "Colombo Marco (JIRA)" To: dev@activemq.apache.org Subject: [jira] Issue Comment Edited: (AMQ-2902) ResourceAdapter logs confusing Exception upon pool connection disposal In-Reply-To: <15500931.11521283859340355.JavaMail.jira@thor> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: ae95407df07c98740808b2ef9da0087c [ https://issues.apache.org/activemq/browse/AMQ-2902?page=3Dcom.atlassi= an.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D61= 989#action_61989 ]=20 Colombo Marco edited comment on AMQ-2902 at 9/22/10 5:39 AM: ------------------------------------------------------------- Also with 5.4.1 release (on JBoss 4.2.3.GA) this issue is present: 2010-09-22 11:29:31,458 INFO [org.apache.activemq.broker.TransportConnecti= on.Transport] Transport failed: org.apache.activemq.transport.TransportDisp= osedIOException: Peer (vm://localhost#37) disposed. org.apache.activemq.transport.TransportDisposedIOException: Peer (vm://loca= lhost#37) disposed. at org.apache.activemq.transport.vm.VMTransport.stop(VMTransport.ja= va:159) at org.apache.activemq.transport.vm.VMTransportServer$1.stop(VMTran= sportServer.java:81) at org.apache.activemq.transport.TransportFilter.stop(TransportFilt= er.java:65) at org.apache.activemq.transport.TransportFilter.stop(TransportFilt= er.java:65) at org.apache.activemq.transport.ResponseCorrelator.stop(ResponseCo= rrelator.java:132) at org.apache.activemq.util.ServiceSupport.dispose(ServiceSupport.j= ava:43) at org.apache.activemq.ActiveMQConnection.close(ActiveMQConnection.= java:656) at org.apache.activemq.ra.ActiveMQManagedConnection.destroy(ActiveM= QManagedConnection.java:207) at org.jboss.resource.connectionmanager.InternalManagedConnectionPo= ol.doDestroy(InternalManagedConnectionPool.java:650) at org.jboss.resource.connectionmanager.InternalManagedConnectionPo= ol.removeTimedOut(InternalManagedConnectionPool.java:481) at org.jboss.resource.connectionmanager.IdleRemover$IdleRemoverRunn= able.run(IdleRemover.java:164) at java.lang.Thread.run(Thread.java:619) But this affects the broker? This could bring to errors or broker faults? was (Author: rjtokenlanring): Also with 5.4.1 this issue is present: 2010-09-22 11:29:31,458 INFO [org.apache.activemq.broker.TransportConnecti= on.Transport] Transport failed: org.apache.activemq.transport.TransportDisp= osedIOException: Peer (vm://localhost#37) disposed. org.apache.activemq.transport.TransportDisposedIOException: Peer (vm://loca= lhost#37) disposed. at org.apache.activemq.transport.vm.VMTransport.stop(VMTransport.ja= va:159) at org.apache.activemq.transport.vm.VMTransportServer$1.stop(VMTran= sportServer.java:81) at org.apache.activemq.transport.TransportFilter.stop(TransportFilt= er.java:65) at org.apache.activemq.transport.TransportFilter.stop(TransportFilt= er.java:65) at org.apache.activemq.transport.ResponseCorrelator.stop(ResponseCo= rrelator.java:132) at org.apache.activemq.util.ServiceSupport.dispose(ServiceSupport.j= ava:43) at org.apache.activemq.ActiveMQConnection.close(ActiveMQConnection.= java:656) at org.apache.activemq.ra.ActiveMQManagedConnection.destroy(ActiveM= QManagedConnection.java:207) at org.jboss.resource.connectionmanager.InternalManagedConnectionPo= ol.doDestroy(InternalManagedConnectionPool.java:650) at org.jboss.resource.connectionmanager.InternalManagedConnectionPo= ol.removeTimedOut(InternalManagedConnectionPool.java:481) at org.jboss.resource.connectionmanager.IdleRemover$IdleRemoverRunn= able.run(IdleRemover.java:164) at java.lang.Thread.run(Thread.java:619) But this affects the broker? This could bring to errors or broker faults? =20 > ResourceAdapter logs confusing Exception upon pool connection disposal > ---------------------------------------------------------------------- > > Key: AMQ-2902 > URL: https://issues.apache.org/activemq/browse/AMQ-2902 > Project: ActiveMQ > Issue Type: Bug > Components: JCA Container > Affects Versions: 5.4.0 > Environment: AMQ 5.4.0 ResourceAdapter running with an embedded b= roker within JBoss 4.2.3 > Reporter: J=C3=B6rg Henne > > After upgrading to 5.4.0 we see many exceptions of the following kind bei= ng logged with level INFO: > {quote} > 2010-09-07 13:23:25,824 INFO [org.apache.activemq.broker.TransportConnec= tion.Transport] Transport failed: org.apache.activemq.transport.TransportDi= sposedIOException: Peer (vm://caa.embedded?waitForStart=3D300000&async=3Dfa= lse#13) disposed. > org.apache.activemq.transport.TransportDisposedIOException: Peer (vm://ca= a.embedded?waitForStart=3D300000&async=3Dfalse#13) disposed. > =09at org.apache.activemq.transport.vm.VMTransport.stop(VMTransport.java:= 159) > =09at org.apache.activemq.transport.vm.VMTransportServer$1.stop(VMTranspo= rtServer.java:81) > =09at org.apache.activemq.transport.TransportFilter.stop(TransportFilter.= java:65) > =09at org.apache.activemq.transport.TransportFilter.stop(TransportFilter.= java:65) > =09at org.apache.activemq.transport.ResponseCorrelator.stop(ResponseCorre= lator.java:132) > =09at org.apache.activemq.util.ServiceSupport.dispose(ServiceSupport.java= :43) > =09at org.apache.activemq.ActiveMQConnection.close(ActiveMQConnection.jav= a:656) > =09at org.apache.activemq.ra.ActiveMQManagedConnection.destroy(ActiveMQMa= nagedConnection.java:207) > =09at org.jboss.resource.connectionmanager.InternalManagedConnectionPool.= doDestroy(InternalManagedConnectionPool.java:650) > =09at org.jboss.resource.connectionmanager.InternalManagedConnectionPool.= removeTimedOut(InternalManagedConnectionPool.java:481) > =09at org.jboss.resource.connectionmanager.IdleRemover$IdleRemoverRunnabl= e.run(IdleRemover.java:164) > =09at java.lang.Thread.run(Thread.java:619) > {quote} > I suppose that the cause for the message is actually harmless - hence the= INFO level - but the messages are confusing and annoying nonetheless. --=20 This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.