Hello guys, I've got an issue here and was wondering if any of you encounter similard problems in the past. I'am trying to run servicemix inside Jboss Here is what I have in my jboss server A web service (http://localhost:8080/MyWebService?WSDL) (war file) A servicemix-http component (zip file) A servicemix-shared component (zip file) A servicemix-jboss-deployer (sar file) A service assembly for my web service that exposes my web service trought the bus (zip file) : -http://localhost:8193/MyWebService?WSDL What my service assembly basically does is expose the web service and it's WSDL via the bus. Now When I start jboss the first time and only have the web service, servicemix-http, servicemix-shared and servicemix-jboss-deploy in my deploy directory, everything works fine. I then copy by the service assembly inside the jboss deploy directory (ONCE JBOSS HAS FINISH LOADING). Everything works fine when using this configuration. However I get a strange behaviour (a deadlock I think) when I have my service assembly as well in the deployment folder BEFORE starting Jboss. When it gets to loading the service assemblie, the whole server freezes when it's trying to access the WSDL for the web service (because jboss has not finished loading). This scenario freezes Jboss completly I have to manually kill the application. Is there any work around for this? Is it possible to force the loding of servicemix-jboss-deploy.sar file after Jboss has finished loading so as to ensure that the WSDL for the web service is avaible when loading the service assembly ? Any help would be greatly appreciated. -- View this message in context: http://www.nabble.com/Running-servicemix-in-jboss-tf2371732.html#a6607358 Sent from the ServiceMix - User mailing list archive at Nabble.com.
