Can be a missing config in tomee.xml like the broker Webapps shouldnt handle it
Le 14 sept. 2016 22:52, "vnalla" <[email protected]> a écrit : > Hi, > > I am using the javaee7 example jms-xa test and deploying it to the exiting > TomEE server. It works fine hen I run the test for the first time. If I run > the test again I see the following message in the log files, not sure why > and what it means. Appreciate your help. > > 14-Sep-2016 16:46:14.687 INFO [http-nio-0.0.0.0-8080-exec-13] > org.apache.openejb.assembler.classic.Assembler.destroyApplication > Undeploying app: > C:\Users\VN2158\AppData\Local\Temp\arquillian-tomee-app- > working-dir\0\31e8e0a2-f3b3-45dd-9f55-8d3ccaa5141e > 14-Sep-2016 16:46:14.703 WARNING [http-nio-0.0.0.0-8080-exec-13] > org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads > The > web application [31e8e0a2-f3b3-45dd-9f55-8d3ccaa5141e] appears to have > started a thread named [ActiveMQ VMTransport: vm://localhost#3-2] but has > failed to stop it. This is very likely to create a memory leak. Stack trace > of thread: > sun.misc.Unsafe.park(Native Method) > java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:215) > > java.util.concurrent.SynchronousQueue$TransferStack.awaitFulfill( > SynchronousQueue.java:460) > > java.util.concurrent.SynchronousQueue$TransferStack.transfer( > SynchronousQueue.java:362) > java.util.concurrent.SynchronousQueue.poll(SynchronousQueue.java:941) > > java.util.concurrent.ThreadPoolExecutor.getTask( > ThreadPoolExecutor.java:1066) > > java.util.concurrent.ThreadPoolExecutor.runWorker( > ThreadPoolExecutor.java:1127) > > java.util.concurrent.ThreadPoolExecutor$Worker.run( > ThreadPoolExecutor.java:617) > java.lang.Thread.run(Thread.java:745) > 14-Sep-2016 16:46:14.704 WARNING [http-nio-0.0.0.0-8080-exec-13] > org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads > The > web application [31e8e0a2-f3b3-45dd-9f55-8d3ccaa5141e] appears to have > started a thread named [ActiveMQ VMTransport: vm://localhost#2-2] but has > failed to stop it. This is very likely to create a memory leak. Stack trace > of thread: > sun.misc.Unsafe.park(Native Method) > java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:215) > > java.util.concurrent.SynchronousQueue$TransferStack.awaitFulfill( > SynchronousQueue.java:460) > > java.util.concurrent.SynchronousQueue$TransferStack.transfer( > SynchronousQueue.java:362) > java.util.concurrent.SynchronousQueue.poll(SynchronousQueue.java:941) > > java.util.concurrent.ThreadPoolExecutor.getTask( > ThreadPoolExecutor.java:1066) > > java.util.concurrent.ThreadPoolExecutor.runWorker( > ThreadPoolExecutor.java:1127) > > java.util.concurrent.ThreadPoolExecutor$Worker.run( > ThreadPoolExecutor.java:617) > java.lang.Thread.run(Thread.java:745) > > thanks, > Venkat > > > > > -- > View this message in context: http://tomee-openejb.979440. > n4.nabble.com/TomEE-7-0-1-ActiveMQ-errors-tp4680122.html > Sent from the TomEE Users mailing list archive at Nabble.com. >
