Robert Balent created SWITCHYARD-634: ---------------------------------------- Summary: Camel endpoint for reference binding is not destroyed after application undeployment Key: SWITCHYARD-634 URL: https://issues.jboss.org/browse/SWITCHYARD-634 Project: SwitchYard Issue Type: Bug Components: core Affects Versions: 0.3 Reporter: Robert Balent Fix For: 0.4 Attachments: reference_binding_server.log, switchyard.xml I've created simple application with camel file:// binding input, one bean injecting XML route, XML route and file:// reference binding output. The problem is that when application is undeployed the reference binding stays still active and is not destroyed. In log you can see: * Creating endpoint uri=\[file:///home/rbalent/temp/sw-input], path=[/home/rbalent/temp/sw-input], parameters=[{}] and when file is consumed * Creating endpoint uri=\[file:///home/rbalent/temp/sw-output], path=[/home/rbalent/temp/sw-output], parameters=[{}] But in undeployment process there is not even mention about the second endpoint. It stays still active. Of course file: endpoint can't consume any message but when I've tried it with camel-irc component it stays connected to irc server after application undeployment. My switchyard.xml and full AS7 server.log with notes when application deployment and undeployment started is attached. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira