snip...
>
> I have successfully created and tested stateless callback service with
> webapp with Tuscany-1.0.
> Now have a problem with Tuscnay-1.1-RC3......
> My stateless service was deployed in Tomcat as a war(Tomcat was running on
> 8080)....
> Now my problem is as below, i got following error on client side when i
> try
> to run my client(stateless callback)....
>
>
> -------------------------------------------------------------------------------------------------------------
>
Hi Nishant
Can you say something more about the composites you are running and how you
are running them, for example, from the text above it appears that you are
running a client and a server.
server = Tomcat on port 8080
composite
component - a component providing a service that will callback to the
caller
client = Java application?
composite
component - a component that will talk to the server service and also
provide a callback service
I assume you are running both of these on the same machine.
Assuming that all of this is true and looking at the error trace I would
guess that what is happening is that the SCA runtime is trying to bring the
client callback service up on Jetty on port 8080, The same port that Tomcat
is already running on.
You could confirm this by starting Tomcat on a different port to see what
happens.
If this is the case then you could switch to the Node implementation will
will choose a free port so that this clash doesn't happen. Having said this
I seem to remember seeing a post about callback binding configuration. I'll
see if I can find it as it might provide a more straightforward solution.
Regards
Simon
