Bernd Zeitler [http://community.jboss.org/people/Frito] created the discussion
"Re: Non-daemon threads running when using Deploymentmanager in JBoss 6" To view the discussion, visit: http://community.jboss.org/message/619041#619041 -------------------------------------------------------------- I investigated a bit more this morning... Your are right: it only happens with copy contents is set to true. When the content has been copied, the remoting client, which is starting a {{StreamServer}} instance, is closed, but the {{StreamServer}} is still alive. It doesn't get the StreamHandler.CLOSE from the server side and the connector is not stopped explicitly on client side, even if client.close() is invoked after every action called on the {{StreamingDeploymentTarget}}. The {{StreamServer}} will be removed upon finalization... I don't know for now, if the client side (deployment) is responsible for closing the {{StreamServer}} or if this is something that came with jboss remoting 2.5.3 . Other remoting threads are daemon threads, but I think, making the {{AcceptThreab}} daemon would only heal the symptom... ;-) -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/619041#619041] Start a new discussion in JBoss Microcontainer at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&containerType=14&container=2114]
_______________________________________________ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
