Return-Path: Delivered-To: apmail-activemq-dev-archive@www.apache.org Received: (qmail 29162 invoked from network); 1 Oct 2010 08:38:12 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 1 Oct 2010 08:38:12 -0000 Received: (qmail 37303 invoked by uid 500); 1 Oct 2010 08:38:12 -0000 Delivered-To: apmail-activemq-dev-archive@activemq.apache.org Received: (qmail 37240 invoked by uid 500); 1 Oct 2010 08:38:11 -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 37232 invoked by uid 99); 1 Oct 2010 08:38:10 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 01 Oct 2010 08:38:10 +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; Fri, 01 Oct 2010 08:38:07 +0000 Received: from thor (localhost [127.0.0.1]) by thor.apache.org (8.13.8+Sun/8.13.8) with ESMTP id o918bkbw016351 for ; Fri, 1 Oct 2010 08:37:46 GMT Message-ID: <12536502.39981285922266340.JavaMail.jira@thor> Date: Fri, 1 Oct 2010 04:37:46 -0400 (EDT) From: "Bastian Krol (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 X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/activemq/browse/AMQ-2902?page=3Dcom.atlassi= an.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D62= 269#action_62269 ]=20 Bastian Krol edited comment on AMQ-2902 at 10/1/10 4:36 AM: ------------------------------------------------------------ The obvious workaround is to configure log4j to not show INFO level message= s from the logger in question. {noformat}=20 {noformat}=20 However, a possible (very simplistic) fix would be to change {{TRANSPORTLOG= .info("Transport failed: " + e, e);}} into {{TRANSPORTLOG.info("Transport f= ailed: " + e);}} in {{org.apache.activemq.broker.TransportConnection}}. Si= nce it is only a logging on info, the stack trace is probably not of intere= st anyway, right? Patch: {noformat}=20 ### Eclipse Workspace Patch 1.0 #P activemq-core Index: src/main/java/org/apache/activemq/broker/TransportConnection.java =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- src/main/java/org/apache/activemq/broker/TransportConnection.java=09(re= vision 1003422) +++ src/main/java/org/apache/activemq/broker/TransportConnection.java=09(wo= rking copy) @@ -233,7 +233,7 @@ if (!stopping.get()) { transportException.set(e); if (TRANSPORTLOG.isInfoEnabled()) { - TRANSPORTLOG.info("Transport failed: " + e, e); + TRANSPORTLOG.info("Transport failed: " + e); } stopAsync(); } {noformat}=20 was (Author: basti1302): The obvious workaround to configure log4j to not show INFO level messag= es from the logger in question. {noformat}=20 {noformat}=20 However, a possible (very simplistic) fix would be to change {{TRANSPORTLOG= .info("Transport failed: " + e, e);}} into {{TRANSPORTLOG.info("Transport f= ailed: " + e);}} in {{org.apache.activemq.broker.TransportConnection}}. Si= nce it is only a logging on info, the stack trace is probably not of intere= st anyway, right? Patch: {noformat}=20 ### Eclipse Workspace Patch 1.0 #P activemq-core Index: src/main/java/org/apache/activemq/broker/TransportConnection.java =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- src/main/java/org/apache/activemq/broker/TransportConnection.java=09(re= vision 1003422) +++ src/main/java/org/apache/activemq/broker/TransportConnection.java=09(wo= rking copy) @@ -233,7 +233,7 @@ if (!stopping.get()) { transportException.set(e); if (TRANSPORTLOG.isInfoEnabled()) { - TRANSPORTLOG.info("Transport failed: " + e, e); + TRANSPORTLOG.info("Transport failed: " + e); } stopAsync(); } {noformat}=20 =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.