Weird behavior with multiple Service Engines/Service Units

[Ryan Moquin]

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><![CDATA[java.net.BindException: Address
already in use: bind
... and so on

Then whichever service I tried to start second will shut itself down.  If I
stop the server and only deploy the module I want deployed, then bring the
server back up, it will start the single service then immediately shut it
down.

Is this behaviour a problem with the locationURI="
http://0.0.0.0:8192/CommunicationService/ have the same ip address and
port?  If so, why can't they be the same if the servicename is different?

Am I making a mistake with how I'm packaging everything?  Should I be
deploying both modules to the same two service engines?  servicemix-jsr181
and one that I create?

Thanks!
Ryan