Wait for Receivers//Subscribers to Syncup at Tue Feb 08 17:48:00 PST 2011 No. of Messages yet to Receive from MDB1 83 No. of Messages yet to Subscribe from MDB1 96 No. of Messages yet to Receive from MDB2 305 No. of Messages yet to Subscribe from MDB2 309 Successful Sync Up... Total Number of Messages sent so far 12525 Total Number of Messages sent so far 12550 Total Number of Messages sent so far 12575 Total Number of Messages sent so far 12600 Total Number of Messages sent so far 12625 Total Number of Messages sent so far 12650 Total Number of Messages sent so far 12675 Total Number of Messages sent so far 12700 Total Number of Messages sent so far 12725 Total Number of Messages sent so far 12750 Total Number of Messages sent so far 12775 Total Number of Messages sent so far 12800 Total Number of Messages sent so far 12825 Total Number of Messages sent so far 12850 Total Number of Messages sent so far 12875 Total Number of Messages sent so far 12900 Total Number of Messages sent so far 12925 Total Number of Messages sent so far 12950 Total Number of Messages sent so far 12975 Total Number of Messages sent so far 13000 Wait for Receivers//Subscribers to Syncup at Tue Feb 08 17:48:11 PST 2011 No. of Messages yet to Receive from MDB1 40 No. of Messages yet to Subscribe from MDB1 40 No. of Messages yet to Receive from MDB2 126 No. of Messages yet to Subscribe from MDB2 118 Feb 8, 2011 5:48:15 PM com.sun.enterprise.resource.pool.ConnectionLeakDetector printConnectionLeakTrace WARNING: A potential connection leak detected for connection pool jms/MDBTopicFactory. The stack trace of the thread is provided below : com.sun.enterprise.resource.pool.ConnectionPool.setResourceStateToBusy(ConnectionPool.java:324) com.sun.enterprise.resource.pool.ConnectionPool.getResourceFromPool(ConnectionPool.java:754) com.sun.enterprise.resource.pool.ConnectionPool.getUnenlistedResource(ConnectionPool.java:632) com.sun.enterprise.resource.pool.ConnectionPool.internalGetResource(ConnectionPool.java:526) com.sun.enterprise.resource.pool.ConnectionPool.getResource(ConnectionPool.java:381) com.sun.enterprise.resource.pool.PoolManagerImpl.getResourceFromPool(PoolManagerImpl.java:242) com.sun.enterprise.resource.pool.PoolManagerImpl.getResource(PoolManagerImpl.java:167) com.sun.enterprise.connectors.ConnectionManagerImpl.getResource(ConnectionManagerImpl.java:335) com.sun.enterprise.connectors.ConnectionManagerImpl.internalGetConnection(ConnectionManagerImpl.java:304) com.sun.enterprise.connectors.ConnectionManagerImpl.allocateConnection(ConnectionManagerImpl.java:236) com.sun.enterprise.connectors.ConnectionManagerImpl.allocateConnection(ConnectionManagerImpl.java:165) com.sun.enterprise.connectors.ConnectionManagerImpl.allocateConnection(ConnectionManagerImpl.java:160) com.sun.messaging.jms.ra.ConnectionFactoryAdapter._allocateTopicConnection(ConnectionFactoryAdapter.java:297) com.sun.messaging.jms.ra.ConnectionFactoryAdapter.createTopicConnection(ConnectionFactoryAdapter.java:284) com.sun.messaging.jms.ra.ConnectionFactoryAdapter.createTopicConnection(ConnectionFactoryAdapter.java:266) SubscribeThread1.run(Unknown Source) Feb 8, 2011 5:48:15 PM com.sun.enterprise.resource.pool.ConnectionPool reclaimConnection INFO: Reclaiming the leaked connection of pool [ jms/MDBTopicFactory ] and destroying it so as to avoid both the application that leaked the connection and any other request that can potentially acquire the same connection from the pool end up using the connection at the same time Feb 8, 2011 5:48:16 PM com.sun.enterprise.resource.pool.ConnectionLeakDetector printConnectionLeakTrace WARNING: A potential connection leak detected for connection pool jms/MDBTopicFactory. The stack trace of the thread is provided below : com.sun.enterprise.resource.pool.ConnectionPool.setResourceStateToBusy(ConnectionPool.java:324) com.sun.enterprise.resource.pool.ConnectionPool.getMatchedResourceFromPool(ConnectionPool.java:812) com.sun.enterprise.resource.pool.ConnectionPool.resizePoolAndGetNewResource(ConnectionPool.java:789) com.sun.enterprise.resource.pool.ConnectionPool.getResourceFromPool(ConnectionPool.java:756) com.sun.enterprise.resource.pool.ConnectionPool.getUnenlistedResource(ConnectionPool.java:632) com.sun.enterprise.resource.pool.ConnectionPool.internalGetResource(ConnectionPool.java:526) com.sun.enterprise.resource.pool.ConnectionPool.getResource(ConnectionPool.java:381) com.sun.enterprise.resource.pool.PoolManagerImpl.getResourceFromPool(PoolManagerImpl.java:242) com.sun.enterprise.resource.pool.PoolManagerImpl.getResource(PoolManagerImpl.java:167) com.sun.enterprise.connectors.ConnectionManagerImpl.getResource(ConnectionManagerImpl.java:335) com.sun.enterprise.connectors.ConnectionManagerImpl.internalGetConnection(ConnectionManagerImpl.java:304) com.sun.enterprise.connectors.ConnectionManagerImpl.allocateConnection(ConnectionManagerImpl.java:236) com.sun.enterprise.connectors.ConnectionManagerImpl.allocateConnection(ConnectionManagerImpl.java:165) com.sun.enterprise.connectors.ConnectionManagerImpl.allocateConnection(ConnectionManagerImpl.java:160) com.sun.messaging.jms.ra.ConnectionFactoryAdapter._allocateTopicConnection(ConnectionFactoryAdapter.java:297) com.sun.messaging.jms.ra.ConnectionFactoryAdapter.createTopicConnection(ConnectionFactoryAdapter.java:284) com.sun.messaging.jms.ra.ConnectionFactoryAdapter.createTopicConnection(ConnectionFactoryAdapter.java:266) SubscribeThread2.run(Unknown Source) Feb 8, 2011 5:48:16 PM com.sun.enterprise.resource.pool.ConnectionPool reclaimConnection INFO: Reclaiming the leaked connection of pool [ jms/MDBTopicFactory ] and destroying it so as to avoid both the application that leaked the connection and any other request that can potentially acquire the same connection from the pool end up using the connection at the same time Successful Sync Up... Total Number of Messages sent so far 13025 Total Number of Messages sent so far 13050 Total Number of Messages sent so far 13075 Total Number of Messages sent so far 13100 Total Number of Messages sent so far 13125 Total Number of Messages sent so far 13150 Total Number of Messages sent so far 13175 Total Number of Messages sent so far 13200 Total Number of Messages sent so far 13225 Total Number of Messages sent so far 13250 Total Number of Messages sent so far 13275 Total Number of Messages sent so far 13300 Total Number of Messages sent so far 13325 Total Number of Messages sent so far 13350 Total Number of Messages sent so far 13375 Total Number of Messages sent so far 13400 Total Number of Messages sent so far 13425 Total Number of Messages sent so far 13450 Total Number of Messages sent so far 13475 Total Number of Messages sent so far 13500 Wait for Receivers//Subscribers to Syncup at Tue Feb 08 17:48:23 PST 2011 No. of Messages yet to Receive from MDB1 23 No. of Messages yet to Subscribe from MDB1 250 No. of Messages yet to Receive from MDB2 269 No. of Messages yet to Subscribe from MDB2 500 Feb 8, 2011 5:48:25 PM com.sun.enterprise.resource.pool.ConnectionLeakDetector printConnectionLeakTrace WARNING: A potential connection leak detected for connection pool jms/MDBTopicFactory. The stack trace of the thread is provided below : com.sun.enterprise.resource.pool.ConnectionPool.setResourceStateToBusy(ConnectionPool.java:324) com.sun.enterprise.resource.pool.ConnectionPool.getResourceFromPool(ConnectionPool.java:754) com.sun.enterprise.resource.pool.ConnectionPool.getUnenlistedResource(ConnectionPool.java:632) com.sun.enterprise.resource.pool.ConnectionPool.internalGetResource(ConnectionPool.java:526) com.sun.enterprise.resource.pool.ConnectionPool.getResource(ConnectionPool.java:381) com.sun.enterprise.resource.pool.PoolManagerImpl.getResourceFromPool(PoolManagerImpl.java:242) com.sun.enterprise.resource.pool.PoolManagerImpl.getResource(PoolManagerImpl.java:167) com.sun.enterprise.connectors.ConnectionManagerImpl.getResource(ConnectionManagerImpl.java:335) com.sun.enterprise.connectors.ConnectionManagerImpl.internalGetConnection(ConnectionManagerImpl.java:304) com.sun.enterprise.connectors.ConnectionManagerImpl.allocateConnection(ConnectionManagerImpl.java:236) com.sun.enterprise.connectors.ConnectionManagerImpl.allocateConnection(ConnectionManagerImpl.java:165) com.sun.enterprise.connectors.ConnectionManagerImpl.allocateConnection(ConnectionManagerImpl.java:160) com.sun.messaging.jms.ra.ConnectionFactoryAdapter._allocateTopicConnection(ConnectionFactoryAdapter.java:297) com.sun.messaging.jms.ra.ConnectionFactoryAdapter.createTopicConnection(ConnectionFactoryAdapter.java:284) com.sun.messaging.jms.ra.ConnectionFactoryAdapter.createTopicConnection(ConnectionFactoryAdapter.java:266) XATStressClient.doIT(Unknown Source) XATStressClient.main(Unknown Source) Feb 8, 2011 5:48:25 PM com.sun.enterprise.resource.pool.ConnectionPool reclaimConnection INFO: Reclaiming the leaked connection of pool [ jms/MDBTopicFactory ] and destroying it so as to avoid both the application that leaked the connection and any other request that can potentially acquire the same connection from the pool end up using the connection at the same time No. of Messages yet to Receive from MDB1 0 No. of Messages yet to Subscribe from MDB1 250 No. of Messages yet to Receive from MDB2 0 No. of Messages yet to Subscribe from MDB2 500 No. of Messages yet to Receive from MDB1 0 No. of Messages yet to Subscribe from MDB1 250 No. of Messages yet to Receive from MDB2 0 No. of Messages yet to Subscribe from MDB2 500 No. of Messages yet to Receive from MDB1 0 No. of Messages yet to Subscribe from MDB1 250 No. of Messages yet to Receive from MDB2 0 No. of Messages yet to Subscribe from MDB2 500 No. of Messages yet to Receive from MDB1 0 No. of Messages yet to Subscribe from MDB1 250 No. of Messages yet to Receive from MDB2 0 No. of Messages yet to Subscribe from MDB2 500 No. of Messages yet to Receive from MDB1 0 No. of Messages yet to Subscribe from MDB1 250 No. of Messages yet to Receive from MDB2 0 No. of Messages yet to Subscribe from MDB2 500 No. of Messages yet to Receive from MDB1 0 No. of Messages yet to Subscribe from MDB1 250 No. of Messages yet to Receive from MDB2 0 No. of Messages yet to Subscribe from MDB2 500 No. of Messages yet to Receive from MDB1 0 No. of Messages yet to Subscribe from MDB1 250 No. of Messages yet to Receive from MDB2 0 No. of Messages yet to Subscribe from MDB2 500 No. of Messages yet to Receive from MDB1 0 No. of Messages yet to Subscribe from MDB1 250 No. of Messages yet to Receive from MDB2 0 No. of Messages yet to Subscribe from MDB2 500 No. of Messages yet to Receive from MDB1 0 No. of Messages yet to Subscribe from MDB1 250 No. of Messages yet to Receive from MDB2 0 No. of Messages yet to Subscribe from MDB2 500 No. of Messages yet to Receive from MDB1 0 No. of Messages yet to Subscribe from MDB1 250 No. of Messages yet to Receive from MDB2 0 No. of Messages yet to Subscribe from MDB2 500 No. of Messages yet to Receive from MDB1 0 No. of Messages yet to Subscribe from MDB1 250 No. of Messages yet to Receive from MDB2 0 No. of Messages yet to Subscribe from MDB2 500 No. of Messages yet to Receive from MDB1 0 No. of Messages yet to Subscribe from MDB1 250 No. of Messages yet to Receive from MDB2 0 No. of Messages yet to Subscribe from MDB2 500 No. of Messages yet to Receive from MDB1 0 No. of Messages yet to Subscribe from MDB1 250 No. of Messages yet to Receive from MDB2 0 No. of Messages yet to Subscribe from MDB2 500 No. of Messages yet to Receive from MDB1 0 No. of Messages yet to Subscribe from MDB1 250 No. of Messages yet to Receive from MDB2 0 No. of Messages yet to Subscribe from MDB2 500 No. of Messages yet to Receive from MDB1 0 No. of Messages yet to Subscribe from MDB1 250