[ https://issues.apache.org/activemq/browse/AMQ-2902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=62269#action_62269 ]
Bastian Krol commented on AMQ-2902: ----------------------------------- The obvious workaround to configure log4j to not show INFO level messages from the logger in question. A possible (very simplistic) fix would be to change {{TRANSPORTLOG.info("Transport failed: " + e, e);}} into {{TRANSPORTLOG.info("Transport failed: " + e);}} in {{org.apache.activemq.broker.TransportConnection}}. Since it is only a logging on info, the stack trace is probably not of interest anyway, right? > 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 > broker within JBoss 4.2.3 > Reporter: Jörg Henne > > After upgrading to 5.4.0 we see many exceptions of the following kind being > logged with level INFO: > {quote} > 2010-09-07 13:23:25,824 INFO > [org.apache.activemq.broker.TransportConnection.Transport] Transport failed: > org.apache.activemq.transport.TransportDisposedIOException: Peer > (vm://caa.embedded?waitForStart=300000&async=false#13) disposed. > org.apache.activemq.transport.TransportDisposedIOException: Peer > (vm://caa.embedded?waitForStart=300000&async=false#13) disposed. > at > org.apache.activemq.transport.vm.VMTransport.stop(VMTransport.java:159) > at > org.apache.activemq.transport.vm.VMTransportServer$1.stop(VMTransportServer.java:81) > at > org.apache.activemq.transport.TransportFilter.stop(TransportFilter.java:65) > at > org.apache.activemq.transport.TransportFilter.stop(TransportFilter.java:65) > at > org.apache.activemq.transport.ResponseCorrelator.stop(ResponseCorrelator.java:132) > at > org.apache.activemq.util.ServiceSupport.dispose(ServiceSupport.java:43) > at > org.apache.activemq.ActiveMQConnection.close(ActiveMQConnection.java:656) > at > org.apache.activemq.ra.ActiveMQManagedConnection.destroy(ActiveMQManagedConnection.java:207) > at > org.jboss.resource.connectionmanager.InternalManagedConnectionPool.doDestroy(InternalManagedConnectionPool.java:650) > at > org.jboss.resource.connectionmanager.InternalManagedConnectionPool.removeTimedOut(InternalManagedConnectionPool.java:481) > at > org.jboss.resource.connectionmanager.IdleRemover$IdleRemoverRunnable.run(IdleRemover.java:164) > at 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. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.