You are viewing a plain text version of this content. The canonical link for it is here.
Posted to sandesha-dev@ws.apache.org by Jerome Camilleri <je...@bull.net> on 2007/03/07 18:47:57 UTC
Error using IN-OUT asynchronous message with sandesha2
Hi,
After modify my client to call my IN-OUT service in asynchronous mode,
the precedent sandesha exception disappear.
The client with callback receive the response and terminate normally.
But on the server, an exception occur raised by sandesha code :
2007-03-07 18:20:44,588 DEBUG
org.apache.sandesha2.msgprocessors.TerminateSeqMsgProcessor - Enter:
TerminateSeqMsgProcessor::processInMessage
2007-03-07 18:20:44,588 DEBUG
org.apache.sandesha2.msgprocessors.TerminateSeqMsgProcessor - Enter:
TerminateSeqMsgProcessor::setUpHighestMsgNumbers,
urn:uuid:928A460DE91F3A15B41173288043861
2007-03-07 18:20:44,589 DEBUG
org.apache.sandesha2.msgprocessors.TerminateSeqMsgProcessor - Exit:
TerminateSeqMsgProcessor::setUpHighestMsgNumbers
2007-03-07 18:20:44,589 DEBUG
org.apache.sandesha2.msgprocessors.TerminateSeqMsgProcessor - Exit:
TerminateSeqMsgProcessor::processInMessage true
2007-03-07 18:20:48,277 ERROR org.apache.sandesha2.workers.SenderWorker
- Sandesha2 got an exception when sending a message:
org.apache.axis2.AxisFault: Connection refused; nested exception is:
java.net.ConnectException: Connection refused; nested exception is:
org.apache.axis2.AxisFault: Connection refused; nested exception is:
java.net.ConnectException: Connection refused
org.apache.axis2.AxisFault: Connection refused; nested exception is:
java.net.ConnectException: Connection refused; nested exception is:
org.apache.axis2.AxisFault: Connection refused; nested exception is:
java.net.ConnectException: Connection refused
at
org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java:227)
at
org.apache.axis2.engine.AxisEngine.resumeSend(AxisEngine.java:575)
at
org.apache.sandesha2.workers.SenderWorker.run(SenderWorker.java:185)
at
edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:665)
at
edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:690)
at java.lang.Thread.run(Thread.java:595)
I run sandesha and axis2 into Tomcat with http port number 8080.
I had modified the axis2.xml on my client repository to change the port
listener for the callback response.
<transportReceiver name="http"
class="org.apache.axis2.transport.http.SimpleHTTPServer">
<parameter name="port" locked="false">8087</parameter>
I don't understand why the exception "connection refused" occured. It
seems that the response on 8087 port is correclty send but the tcpmon
don't trace it...
Someone have an idea about this error pleased ?
Regards
Jérôme
---------------------------------------------------------------------
To unsubscribe, e-mail: sandesha-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: sandesha-dev-help@ws.apache.org
Re: Error using IN-OUT asynchronous message with sandesha2
Posted by Chamikara Jayalath <ch...@gmail.com>.
Hi Jerome,
Not yet. But a good point :-)
Currently we hv the SandeshaClient.waitUntilSequenceCompleted () method
which support outgoing seuqence, I'll update this to support incoming
sequences as well.
Chamikara
On 3/8/07, Jerome Camilleri <je...@bull.net> wrote:
>
> Chamikara Jayalath wrote:
> > Hi Jerome,
> >
> > This might be because u exit the client before the server send the
> > TerminateSequence message. Please give a little time interval before
> > you exit the client.
> >
> > Chamikara
> >
> Yes a Thread.sleep(5000); before the client finished let the server
> send the terminate sequence. Thanks.
> Does exist an elegant method (into the callback class for example) to
> wait just the necessary time ?
>
> Regards
>
> Jérôme
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: sandesha-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: sandesha-dev-help@ws.apache.org
>
>
Re: Error using IN-OUT asynchronous message with sandesha2
Posted by Chamikara Jayalath <ch...@gmail.com>.
Hi Jerome,
Not yet. But a good point :-)
Currently we hv the SandeshaClient.waitUntilSequenceCompleted () method
which support outgoing seuqence, I'll update this to support incoming
sequences as well.
Chamikara
On 3/8/07, Jerome Camilleri <je...@bull.net> wrote:
>
> Chamikara Jayalath wrote:
> > Hi Jerome,
> >
> > This might be because u exit the client before the server send the
> > TerminateSequence message. Please give a little time interval before
> > you exit the client.
> >
> > Chamikara
> >
> Yes a Thread.sleep(5000); before the client finished let the server
> send the terminate sequence. Thanks.
> Does exist an elegant method (into the callback class for example) to
> wait just the necessary time ?
>
> Regards
>
> Jérôme
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: sandesha-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: sandesha-dev-help@ws.apache.org
>
>
Re: Error using IN-OUT asynchronous message with sandesha2
Posted by Jerome Camilleri <je...@bull.net>.
Chamikara Jayalath wrote:
> Hi Jerome,
>
> This might be because u exit the client before the server send the
> TerminateSequence message. Please give a little time interval before
> you exit the client.
>
> Chamikara
>
Yes a Thread.sleep(5000); before the client finished let the server
send the terminate sequence. Thanks.
Does exist an elegant method (into the callback class for example) to
wait just the necessary time ?
Regards
Jérôme
---------------------------------------------------------------------
To unsubscribe, e-mail: sandesha-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: sandesha-dev-help@ws.apache.org
Re: Error using IN-OUT asynchronous message with sandesha2
Posted by Jerome Camilleri <je...@bull.net>.
Chamikara Jayalath wrote:
> Hi Jerome,
>
> This might be because u exit the client before the server send the
> TerminateSequence message. Please give a little time interval before
> you exit the client.
>
> Chamikara
>
Yes a Thread.sleep(5000); before the client finished let the server
send the terminate sequence. Thanks.
Does exist an elegant method (into the callback class for example) to
wait just the necessary time ?
Regards
Jérôme
---------------------------------------------------------------------
To unsubscribe, e-mail: sandesha-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: sandesha-dev-help@ws.apache.org
Re: Error using IN-OUT asynchronous message with sandesha2
Posted by Chamikara Jayalath <ch...@gmail.com>.
Hi Jerome,
This might be because u exit the client before the server send the
TerminateSequence message. Please give a little time interval before you
exit the client.
Chamikara
On 3/7/07, Jerome Camilleri <je...@bull.net> wrote:
>
> Hi,
>
> After modify my client to call my IN-OUT service in asynchronous mode,
> the precedent sandesha exception disappear.
> The client with callback receive the response and terminate normally.
> But on the server, an exception occur raised by sandesha code :
> 2007-03-07 18:20:44,588 DEBUG
> org.apache.sandesha2.msgprocessors.TerminateSeqMsgProcessor - Enter:
> TerminateSeqMsgProcessor::processInMessage
> 2007-03-07 18:20:44,588 DEBUG
> org.apache.sandesha2.msgprocessors.TerminateSeqMsgProcessor - Enter:
> TerminateSeqMsgProcessor::setUpHighestMsgNumbers,
> urn:uuid:928A460DE91F3A15B41173288043861
> 2007-03-07 18:20:44,589 DEBUG
> org.apache.sandesha2.msgprocessors.TerminateSeqMsgProcessor - Exit:
> TerminateSeqMsgProcessor::setUpHighestMsgNumbers
> 2007-03-07 18:20:44,589 DEBUG
> org.apache.sandesha2.msgprocessors.TerminateSeqMsgProcessor - Exit:
> TerminateSeqMsgProcessor::processInMessage true
> 2007-03-07 18:20:48,277 ERROR org.apache.sandesha2.workers.SenderWorker
> - Sandesha2 got an exception when sending a message:
> org.apache.axis2.AxisFault: Connection refused; nested exception is:
> java.net.ConnectException: Connection refused; nested exception
> is:
> org.apache.axis2.AxisFault: Connection refused; nested exception
> is:
> java.net.ConnectException: Connection refused
> org.apache.axis2.AxisFault: Connection refused; nested exception is:
> java.net.ConnectException: Connection refused; nested exception
> is:
> org.apache.axis2.AxisFault: Connection refused; nested exception
> is:
> java.net.ConnectException: Connection refused
> at
> org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(
> CommonsHTTPTransportSender.java:227)
> at
> org.apache.axis2.engine.AxisEngine.resumeSend(AxisEngine.java:575)
> at
> org.apache.sandesha2.workers.SenderWorker.run(SenderWorker.java:185)
> at
>
> edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.runTask
> (ThreadPoolExecutor.java:665)
> at
>
> edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run
> (ThreadPoolExecutor.java:690)
> at java.lang.Thread.run(Thread.java:595)
>
> I run sandesha and axis2 into Tomcat with http port number 8080.
> I had modified the axis2.xml on my client repository to change the port
> listener for the callback response.
> <transportReceiver name="http"
>
> class="org.apache.axis2.transport.http.SimpleHTTPServer">
> <parameter name="port" locked="false">8087</parameter>
>
> I don't understand why the exception "connection refused" occured. It
> seems that the response on 8087 port is correclty send but the tcpmon
> don't trace it...
> Someone have an idea about this error pleased ?
>
> Regards
> Jérôme
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: sandesha-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: sandesha-dev-help@ws.apache.org
>
>
Re: Error using IN-OUT asynchronous message with sandesha2
Posted by Chamikara Jayalath <ch...@gmail.com>.
Hi Jerome,
This might be because u exit the client before the server send the
TerminateSequence message. Please give a little time interval before you
exit the client.
Chamikara
On 3/7/07, Jerome Camilleri <je...@bull.net> wrote:
>
> Hi,
>
> After modify my client to call my IN-OUT service in asynchronous mode,
> the precedent sandesha exception disappear.
> The client with callback receive the response and terminate normally.
> But on the server, an exception occur raised by sandesha code :
> 2007-03-07 18:20:44,588 DEBUG
> org.apache.sandesha2.msgprocessors.TerminateSeqMsgProcessor - Enter:
> TerminateSeqMsgProcessor::processInMessage
> 2007-03-07 18:20:44,588 DEBUG
> org.apache.sandesha2.msgprocessors.TerminateSeqMsgProcessor - Enter:
> TerminateSeqMsgProcessor::setUpHighestMsgNumbers,
> urn:uuid:928A460DE91F3A15B41173288043861
> 2007-03-07 18:20:44,589 DEBUG
> org.apache.sandesha2.msgprocessors.TerminateSeqMsgProcessor - Exit:
> TerminateSeqMsgProcessor::setUpHighestMsgNumbers
> 2007-03-07 18:20:44,589 DEBUG
> org.apache.sandesha2.msgprocessors.TerminateSeqMsgProcessor - Exit:
> TerminateSeqMsgProcessor::processInMessage true
> 2007-03-07 18:20:48,277 ERROR org.apache.sandesha2.workers.SenderWorker
> - Sandesha2 got an exception when sending a message:
> org.apache.axis2.AxisFault: Connection refused; nested exception is:
> java.net.ConnectException: Connection refused; nested exception
> is:
> org.apache.axis2.AxisFault: Connection refused; nested exception
> is:
> java.net.ConnectException: Connection refused
> org.apache.axis2.AxisFault: Connection refused; nested exception is:
> java.net.ConnectException: Connection refused; nested exception
> is:
> org.apache.axis2.AxisFault: Connection refused; nested exception
> is:
> java.net.ConnectException: Connection refused
> at
> org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(
> CommonsHTTPTransportSender.java:227)
> at
> org.apache.axis2.engine.AxisEngine.resumeSend(AxisEngine.java:575)
> at
> org.apache.sandesha2.workers.SenderWorker.run(SenderWorker.java:185)
> at
>
> edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.runTask
> (ThreadPoolExecutor.java:665)
> at
>
> edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run
> (ThreadPoolExecutor.java:690)
> at java.lang.Thread.run(Thread.java:595)
>
> I run sandesha and axis2 into Tomcat with http port number 8080.
> I had modified the axis2.xml on my client repository to change the port
> listener for the callback response.
> <transportReceiver name="http"
>
> class="org.apache.axis2.transport.http.SimpleHTTPServer">
> <parameter name="port" locked="false">8087</parameter>
>
> I don't understand why the exception "connection refused" occured. It
> seems that the response on 8087 port is correclty send but the tcpmon
> don't trace it...
> Someone have an idea about this error pleased ?
>
> Regards
> Jérôme
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: sandesha-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: sandesha-dev-help@ws.apache.org
>
>