[
https://issues.apache.org/activemq/browse/AMQ-2902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=62268#action_62268
]
Bastian Krol commented on AMQ-2902:
-----------------------------------
I too see that issue in the current 5.4.1. This has nothing to do with JBoss.
It is reproducible in an ordinary Java application (see below). Claus, who told
you that is fixed in the trunk? From looking at the sources in the trunk I have
the impression that the related code has not changed (but I'm guessing a bit
here and could be wrong). The small test below reproduces the problem. Note
that the exception gets logged less frequently if you start and stop the
connection before closing it (enable the two commented lines). But it still
occurs. It occurs every time if you do not start and stop the connection.
{code:title=AMQ2902.java|borderStyle=solid}
import javax.jms.Connection;
import javax.jms.ConnectionFactory;
import javax.jms.JMSException;
import org.apache.activemq.ActiveMQConnectionFactory;
public class AMQ2902
{
public static void main(String[] arguments) throws JMSException
{
ConnectionFactory connectionFactory = new ActiveMQConnectionFactory(
"vm://localhost?broker.persistent=false");
Connection connection = connectionFactory.createConnection();
// connection.start();
// connection.stop();
connection.close();
}
}
{code}
> 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.
