I was able to get around this problem by changing the port to 8193 for my 2nd service, but I guess I'm not sure why they can't be deployed on the same? Webservers and application servers let you deploy several apps using the same ip address but different context. I read a little about this error from a search I did and it kind of makes sense. I guess I'm not sure why deployment on servicemix seems to go against what I'm used to with any application server I normally deploy on.
On 12/7/06, Ryan Moquin <[EMAIL PROTECTED]> wrote:
Hello, I managed to get a JSR181 web service exposed in Servicemix a couple weeks back. I'm now working on my second service that which is completely unrelated to the the first service other than being deployed side by side. In order to do this, I created these 4 modules: CommunicationServiceSU CommunicationServiceSU-jsr-181 CommunicationServiceSA CommunicationServiceSE I then had the CommunicationServiceSU module be dependant on the servicemix-jsr181 service engine. Inside of my xbean.xml, I used locationURI="http://0.0.0.0:8192/CommunicationService/";. So basically, I modeled this service and the previous service directly after the wsdl-first example. The problem is, when I deploy all the modules for both services (the other service has an identical set of modules, just named differently and obviously with different code.), I get this error: <exception-info> <nesting-level>1</nesting-level> <msg-loc-info> <loc-token/> <loc-message>Address already in use: bind</loc-message> <stack-trace><