You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ode.apache.org by "Rosalin Pattnaik (JIRA)" <ji...@apache.org> on 2009/01/05 06:43:44 UTC
[jira] Created: (ODE-473) If ode crashes while waiting for an
response to an synchronous response and while thr has yet not been any
timeout , it does not resume on restarting the ode.
If ode crashes while waiting for an response to an synchronous response and while thr has yet not been any timeout , it does not resume on restarting the ode.
--------------------------------------------------------------------------------------------------------------------------------------------------------------
Key: ODE-473
URL: https://issues.apache.org/jira/browse/ODE-473
Project: ODE
Issue Type: Bug
Components: BPEL Runtime
Reporter: Rosalin Pattnaik
Priority: Critical
If we have bpel extension for retry on timeout with an invoke action , but the ode crashes before the timeout has occured .And thus there is neither a timeout exception nor has it received the response which might have been lost in the time it was down .When the ode restarts which of the following shd occur:
* The ode resumes from the invoke state ,waits for the response , timesout and retries, get the response and proceed normally.
* The process is not resumed.
In my case the process is not resumed in case timeout exception has not occured , but in case the timeout has occured and then the ode crashes then it retries gets the response and then completes succesfully.
[N.B It resumed in case there was an entry into the ode_activity_recovery table , or else it didnt]
Please find the BPEL and external service used as attachment with the query posted at ode user forum :
http://www.nabble.com/If-ode-crashes-while-waiting-for-an-response-to-an-synchronous-response-and-while-thr-has-yet-not-been-any-timeout-%2C-Does-it-on-restarting-resume-the-process-and-the-timesout-the-invoke-activity--td21248664.html
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Re: [jira] Commented: (ODE-473) If ode crashes while waiting for an
response to an synchronous response and while thr has yet not been any
timeout , it does not resume on restarting the ode.
Posted by Rosalin Pattnaik <ro...@gmail.com>.
Hi Alex,
I tried with the latest nightly build [build # 86 jan 7 , 2009]
http://hudson.zones.apache.org/hudson/view/ODE/job/ODE-trunk/lastStableBuild/
After the service was invoked and was waiting for a response, i killed the
ode.
After restarting the ode, this what i got on console:
Jan 7, 2009 11:57:17 AM org.apache.catalina.startup.Catalina start
INFO: Server startup in 54985 ms
DEBUG - GeronimoLog.debug(66) | handleWorkEvent: InvokeCheck event for mexid
hqejbhcnphr3w17uvkwuxl
11:58:06,843 DEBUG [BpelServerImpl] handleWorkEvent: InvokeCheck event for
mexid hqejbhcnphr3w17uvkwuxl
DEBUG - GeronimoLog.debug(66) | Dangling invocation
(mexId=hqejbhcnphr3w17uvkwuxl), forcing it into a failed state.
11:58:07,062 DEBUG [BpelServerImpl] Dangling invocation
(mexId=hqejbhcnphr3w17uvkwuxl), forcing it into a failed state.
DEBUG - GeronimoLog.debug(66) | replyWithFailure mex=hqejbhcnphr3w17uvkwuxl
11:58:07,062 DEBUG [PartnerRoleMessageExchangeImpl] replyWithFailure
mex=hqejbhcnphr3w17uvkwuxl
But the process was not resumed, while as per the flow , it shd retry in
case of failure.
Regards,
Rosalin
On Tue, Jan 6, 2009 at 11:34 PM, Alex Boisvert (JIRA) <ji...@apache.org>wrote:
>
> [
> https://issues.apache.org/jira/browse/ODE-473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12661233#action_12661233]
>
> Alex Boisvert commented on ODE-473:
> -----------------------------------
>
> On Tue, Jan 6, 2009 at 1:42 AM, Rosalin Pattnaik <
> rosalin.pattnaik@gmail.com
>
> <snip>
>
>
>
> Right, this is expected.
>
>
>
> <snip>
>
> The expected sequence of action should be the following,
> 1) process invokes service
> 2) server crashes before invoke is successful or timeouts
> 3) server is restarted
> 4) when the message exchange times-out (after 120 seconds, I believe) a
> scheduled job should mark the exchange as failed and then proceed according
> to your activity failure instruction
> 5) in your case, the invoke should be retried automatically.
>
> Can you test with the latest Ode 1.x branch as requested? If you're not
> getting this expected result then we'll look into it.
>
> alex
>
>
> > If ode crashes while waiting for an response to an synchronous response
> and while thr has yet not been any timeout , it does not resume on
> restarting the ode.
> >
> --------------------------------------------------------------------------------------------------------------------------------------------------------------
> >
> > Key: ODE-473
> > URL: https://issues.apache.org/jira/browse/ODE-473
> > Project: ODE
> > Issue Type: Bug
> > Components: BPEL Runtime
> > Reporter: Rosalin Pattnaik
> > Priority: Critical
> >
> > If we have bpel extension for retry on timeout with an invoke action ,
> but the ode crashes before the timeout has occured .And thus there is
> neither a timeout exception nor has it received the response which might
> have been lost in the time it was down .When the ode restarts which of the
> following shd occur:
> > * The ode resumes from the invoke state ,waits for the response ,
> timesout and retries, get the response and proceed normally.
> > * The process is not resumed.
> > In my case the process is not resumed in case timeout exception has not
> occured , but in case the timeout has occured and then the ode crashes then
> it retries gets the response and then completes succesfully.
> > [N.B It resumed in case there was an entry into the ode_activity_recovery
> table , or else it didnt]
> > Please find the BPEL and external service used as attachment with the
> query posted at ode user forum :
> >
> http://www.nabble.com/If-ode-crashes-while-waiting-for-an-response-to-an-synchronous-response-and-while-thr-has-yet-not-been-any-timeout-%2C-Does-it-on-restarting-resume-the-process-and-the-timesout-the-invoke-activity--td21248664.html
>
> --
> This message is automatically generated by JIRA.
> -
> You can reply to this email to add a comment to the issue online.
>
>
[jira] Resolved: (ODE-473) If ode crashes while waiting for an
response to an synchronous response and while thr has yet not been any
timeout , it does not resume on restarting the ode.
Posted by "Rafal Rusin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ODE-473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rafal Rusin resolved ODE-473.
-----------------------------
Resolution: Fixed
Fix Version/s: 1.3.4
It's already fixed
> If ode crashes while waiting for an response to an synchronous response and while thr has yet not been any timeout , it does not resume on restarting the ode.
> --------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: ODE-473
> URL: https://issues.apache.org/jira/browse/ODE-473
> Project: ODE
> Issue Type: Bug
> Components: BPEL Runtime
> Reporter: Rosalin Pattnaik
> Priority: Critical
> Fix For: 1.3.4
>
>
> If we have bpel extension for retry on timeout with an invoke action , but the ode crashes before the timeout has occured .And thus there is neither a timeout exception nor has it received the response which might have been lost in the time it was down .When the ode restarts which of the following shd occur:
> * The ode resumes from the invoke state ,waits for the response , timesout and retries, get the response and proceed normally.
> * The process is not resumed.
> In my case the process is not resumed in case timeout exception has not occured , but in case the timeout has occured and then the ode crashes then it retries gets the response and then completes succesfully.
> [N.B It resumed in case there was an entry into the ode_activity_recovery table , or else it didnt]
> Please find the BPEL and external service used as attachment with the query posted at ode user forum :
> http://www.nabble.com/If-ode-crashes-while-waiting-for-an-response-to-an-synchronous-response-and-while-thr-has-yet-not-been-any-timeout-%2C-Does-it-on-restarting-resume-the-process-and-the-timesout-the-invoke-activity--td21248664.html
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (ODE-473) If ode crashes while waiting for an
response to an synchronous response and while thr has yet not been any
timeout , it does not resume on restarting the ode.
Posted by "Rosalin Pattnaik (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ODE-473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12661470#action_12661470 ]
Rosalin Pattnaik commented on ODE-473:
--------------------------------------
Hi Alex,
I tried with the latest nightly build [build # 86 jan 7 , 2009]
http://hudson.zones.apache.org/hudson/view/ODE/job/ODE-trunk/lastStableBuild/
After the service was invoked and was waiting for a response, i killed the
ode.
After restarting the ode, this what i got on console:
Jan 7, 2009 11:57:17 AM org.apache.catalina.startup.Catalina start
INFO: Server startup in 54985 ms
DEBUG - GeronimoLog.debug(66) | handleWorkEvent: InvokeCheck event for mexid
hqejbhcnphr3w17uvkwuxl
11:58:06,843 DEBUG [BpelServerImpl] handleWorkEvent: InvokeCheck event for
mexid hqejbhcnphr3w17uvkwuxl
DEBUG - GeronimoLog.debug(66) | Dangling invocation
(mexId=hqejbhcnphr3w17uvkwuxl), forcing it into a failed state.
11:58:07,062 DEBUG [BpelServerImpl] Dangling invocation
(mexId=hqejbhcnphr3w17uvkwuxl), forcing it into a failed state.
DEBUG - GeronimoLog.debug(66) | replyWithFailure mex=hqejbhcnphr3w17uvkwuxl
11:58:07,062 DEBUG [PartnerRoleMessageExchangeImpl] replyWithFailure
mex=hqejbhcnphr3w17uvkwuxl
But the process was not resumed, while as per the flow , it shd retry in
case of failure.
Regards,
Rosalin
> If ode crashes while waiting for an response to an synchronous response and while thr has yet not been any timeout , it does not resume on restarting the ode.
> --------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: ODE-473
> URL: https://issues.apache.org/jira/browse/ODE-473
> Project: ODE
> Issue Type: Bug
> Components: BPEL Runtime
> Reporter: Rosalin Pattnaik
> Priority: Critical
>
> If we have bpel extension for retry on timeout with an invoke action , but the ode crashes before the timeout has occured .And thus there is neither a timeout exception nor has it received the response which might have been lost in the time it was down .When the ode restarts which of the following shd occur:
> * The ode resumes from the invoke state ,waits for the response , timesout and retries, get the response and proceed normally.
> * The process is not resumed.
> In my case the process is not resumed in case timeout exception has not occured , but in case the timeout has occured and then the ode crashes then it retries gets the response and then completes succesfully.
> [N.B It resumed in case there was an entry into the ode_activity_recovery table , or else it didnt]
> Please find the BPEL and external service used as attachment with the query posted at ode user forum :
> http://www.nabble.com/If-ode-crashes-while-waiting-for-an-response-to-an-synchronous-response-and-while-thr-has-yet-not-been-any-timeout-%2C-Does-it-on-restarting-resume-the-process-and-the-timesout-the-invoke-activity--td21248664.html
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (ODE-473) If ode crashes while waiting for an
response to an synchronous response and while thr has yet not been any
timeout , it does not resume on restarting the ode.
Posted by "Alex Boisvert (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ODE-473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12661233#action_12661233 ]
Alex Boisvert commented on ODE-473:
-----------------------------------
On Tue, Jan 6, 2009 at 1:42 AM, Rosalin Pattnaik <rosalin.pattnaik@gmail.com
<snip>
Right, this is expected.
<snip>
The expected sequence of action should be the following,
1) process invokes service
2) server crashes before invoke is successful or timeouts
3) server is restarted
4) when the message exchange times-out (after 120 seconds, I believe) a
scheduled job should mark the exchange as failed and then proceed according
to your activity failure instruction
5) in your case, the invoke should be retried automatically.
Can you test with the latest Ode 1.x branch as requested? If you're not
getting this expected result then we'll look into it.
alex
> If ode crashes while waiting for an response to an synchronous response and while thr has yet not been any timeout , it does not resume on restarting the ode.
> --------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: ODE-473
> URL: https://issues.apache.org/jira/browse/ODE-473
> Project: ODE
> Issue Type: Bug
> Components: BPEL Runtime
> Reporter: Rosalin Pattnaik
> Priority: Critical
>
> If we have bpel extension for retry on timeout with an invoke action , but the ode crashes before the timeout has occured .And thus there is neither a timeout exception nor has it received the response which might have been lost in the time it was down .When the ode restarts which of the following shd occur:
> * The ode resumes from the invoke state ,waits for the response , timesout and retries, get the response and proceed normally.
> * The process is not resumed.
> In my case the process is not resumed in case timeout exception has not occured , but in case the timeout has occured and then the ode crashes then it retries gets the response and then completes succesfully.
> [N.B It resumed in case there was an entry into the ode_activity_recovery table , or else it didnt]
> Please find the BPEL and external service used as attachment with the query posted at ode user forum :
> http://www.nabble.com/If-ode-crashes-while-waiting-for-an-response-to-an-synchronous-response-and-while-thr-has-yet-not-been-any-timeout-%2C-Does-it-on-restarting-resume-the-process-and-the-timesout-the-invoke-activity--td21248664.html
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (ODE-473) If ode crashes while waiting for an
response to an synchronous response and while thr has yet not been any
timeout , it does not resume on restarting the ode.
Posted by "Alex Boisvert (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ODE-473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12660860#action_12660860 ]
Alex Boisvert commented on ODE-473:
-----------------------------------
Can you reproduce this with the latest code on the Ode 1.x branch?
e.g. http://svn.apache.org/repos/asf/ode/branches/APACHE_ODE_1.X
> If ode crashes while waiting for an response to an synchronous response and while thr has yet not been any timeout , it does not resume on restarting the ode.
> --------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: ODE-473
> URL: https://issues.apache.org/jira/browse/ODE-473
> Project: ODE
> Issue Type: Bug
> Components: BPEL Runtime
> Reporter: Rosalin Pattnaik
> Priority: Critical
>
> If we have bpel extension for retry on timeout with an invoke action , but the ode crashes before the timeout has occured .And thus there is neither a timeout exception nor has it received the response which might have been lost in the time it was down .When the ode restarts which of the following shd occur:
> * The ode resumes from the invoke state ,waits for the response , timesout and retries, get the response and proceed normally.
> * The process is not resumed.
> In my case the process is not resumed in case timeout exception has not occured , but in case the timeout has occured and then the ode crashes then it retries gets the response and then completes succesfully.
> [N.B It resumed in case there was an entry into the ode_activity_recovery table , or else it didnt]
> Please find the BPEL and external service used as attachment with the query posted at ode user forum :
> http://www.nabble.com/If-ode-crashes-while-waiting-for-an-response-to-an-synchronous-response-and-while-thr-has-yet-not-been-any-timeout-%2C-Does-it-on-restarting-resume-the-process-and-the-timesout-the-invoke-activity--td21248664.html
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (ODE-473) If ode crashes while waiting for an
response to an synchronous response and while thr has yet not been any
timeout , it does not resume on restarting the ode.
Posted by "Rosalin Pattnaik (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ODE-473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12661091#action_12661091 ]
Rosalin Pattnaik commented on ODE-473:
--------------------------------------
Hi Alex,
I tested it with ode 1.2 and the prob remains the same.
*1st scenario:*
The bpel invoked the Globalweather service ,waited for response and then ode
timeout.Now the ode crashes.The console message just before the ode crashed
is as below:
........................
........................
14:56:10,218 DEBUG [SessionOutHandler] Sending a message containing wsa
endpoints in headers for session passing.
DEBUG - GeronimoLog.debug(66) | <?xml version='1.0'
encoding='utf-8'?><soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap
.org/soap/envelope/"><soapenv:Header><addr:To xmlns:addr="
http://www.w3.org/2005/08/addressing">http://192.168.1.150:8080/axi
s2/services/GlobalWeather</addr:To><addr:Action xmlns:addr="
http://www.w3.org/2005/08/addressing">http://www.webserviceX.NET/
GetWeather</addr:Action><addr:ReplyTo xmlns:addr="
http://www.w3.org/2005/08/addressing"><addr:Address>http://www.w3.org/2005/
08/addressing/anonymous</addr:Address></addr:ReplyTo><addr:MessageID
xmlns:addr="http://www.w3.org/2005/08/addressing">uuid:h
qejbhcnphr3vw7ivqgp9j</addr:MessageID></soapenv:Header><soapenv:Body><GetWeather
xmlns="http://www.webserviceX.NET">
<ns1:CityName xmlns:ns1="
http://www.webserviceX.NET">DELHI</ns1:CityName>
<ns1:CountryName xmlns:ns1="
http://www.webserviceX.NET">INDIA</ns1:CountryName>
</GetWeather></soapenv:Body></soapenv:Envelope>
14:56:10,234 DEBUG [SessionOutHandler] <?xml version='1.0'
encoding='utf-8'?><soapenv:Envelope xmlns:soapenv="http://schemas.
xmlsoap.org/soap/envelope/"><soapenv:Header><addr:To xmlns:addr="
http://www.w3.org/2005/08/addressing">http://192.168.1.150:8
080/axis2/services/GlobalWeather</addr:To><addr:Action xmlns:addr="
http://www.w3.org/2005/08/addressing">http://www.webservic
eX.NET/GetWeather</addr:Action><addr:ReplyTo xmlns:addr="
http://www.w3.org/2005/08/addressing"><addr:Address>http://www.w3.or
g/2005/08/addressing/anonymous</addr:Address></addr:ReplyTo><addr:MessageID
xmlns:addr="http://www.w3.org/2005/08/addressing"
xmlns="http://www.webserviceX.NET">
<ns1:CityName xmlns:ns1="
http://www.webserviceX.NET">DELHI</ns1:CityName>
<ns1:CountryName xmlns:ns1="
http://www.webserviceX.NET">INDIA</ns1:CountryName>
</GetWeather></soapenv:Body></soapenv:Envelope>
ERROR - GeronimoLog.error(108) | Error sending message
(mex={PartnerRoleMex#hqejbhcnphr3vw7ivqgp9i [PID {http://soa-matrix.co
m/example}Flow-4] calling
org.apache.ode.bpel.epr.WSAEndpoint@a3cf94.GetWeather(...)}): Read timed out
org.apache.axis2.AxisFault: Read timed out
at org.apache.axis2.AxisFault.makeFault(AxisFault.java:417)
at
org.apache.axis2.transport.http.HTTPSender.sendViaPost(HTTPSender.java:195)
at
org.apache.axis2.transport.http.HTTPSender.send(HTTPSender.java:77)
at
org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageWithCommons(CommonsHTTPTransportSender.java
:327)
at
org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java:206)
at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:396)
at
org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:374)
at
org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:211)
at
org.apache.axis2.client.OperationClient.execute(OperationClient.java:163)
at
org.apache.ode.axis2.SoapExternalService$1$1.call(SoapExternalService.java:162)
at
java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:269)
at java.util.concurrent.FutureTask.run(FutureTask.java:123)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
at java.lang.Thread.run(Thread.java:595)
Caused by: java.net.SocketTimeoutException: Read timed out
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.read(SocketInputStream.java:129)
at java.io.BufferedInputStream.fill(BufferedInputStream.java:218)
at java.io.BufferedInputStream.read(BufferedInputStream.java:235)
at
org.apache.commons.httpclient.HttpParser.readRawLine(HttpParser.java:77)
at
org.apache.commons.httpclient.HttpParser.readLine(HttpParser.java:105)
at
org.apache.commons.httpclient.HttpConnection.readLine(HttpConnection.java:1115)
at
org.apache.commons.httpclient.MultiThreadedHttpConnectionManager$HttpConnectionAdapter.readLine(MultiThreadedHttpC
onnectionManager.java:1373)
at
org.apache.commons.httpclient.HttpMethodBase.readStatusLine(HttpMethodBase.java:1832)
at
org.apache.commons.httpclient.HttpMethodBase.readResponse(HttpMethodBase.java:1590)
at
org.apache.commons.httpclient.HttpMethodBase.execute(HttpMethodBase.java:995)
at
org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java:397)
at
org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:170)
at
org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:396)
at
org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:346)
at
org.apache.axis2.transport.http.AbstractHTTPSender.executeMethod(AbstractHTTPSender.java:520)
at
org.apache.axis2.transport.http.HTTPSender.sendViaPost(HTTPSender.java:191)
... 13 more
14:57:10,812 ERROR [SoapExternalService] Error sending message
(mex={PartnerRoleMex#hqejbhcnphr3vw7ivqgp9i [PID {http://soa-m
atrix.com/example}Flow-4] calling
org.apache.ode.bpel.epr.WSAEndpoint@a3cf94.GetWeather(...)}): Read timed out
org.apache.axis2.AxisFault: Read timed out
at org.apache.axis2.AxisFault.makeFault(AxisFault.java:417)
at
org.apache.axis2.transport.http.HTTPSender.sendViaPost(HTTPSender.java:195)
at
org.apache.axis2.transport.http.HTTPSender.send(HTTPSender.java:77)
at
org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageWithCommons(CommonsHTTPTransportSender.java
:327)
at
org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java:206)
at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:396)
at
org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:374)
at
org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:211)
at
org.apache.axis2.client.OperationClient.execute(OperationClient.java:163)
at
org.apache.ode.axis2.SoapExternalService$1$1.call(SoapExternalService.java:162)
at
java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:269)
at java.util.concurrent.FutureTask.run(FutureTask.java:123)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
at java.lang.Thread.run(Thread.java:595)
Caused by: java.net.SocketTimeoutException: Read timed out
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.read(SocketInputStream.java:129)
at java.io.BufferedInputStream.fill(BufferedInputStream.java:218)
at java.io.BufferedInputStream.read(BufferedInputStream.java:235)
at
org.apache.commons.httpclient.HttpParser.readRawLine(HttpParser.java:77)
at
org.apache.commons.httpclient.HttpParser.readLine(HttpParser.java:105)
at
org.apache.commons.httpclient.HttpConnection.readLine(HttpConnection.java:1115)
at
org.apache.commons.httpclient.MultiThreadedHttpConnectionManager$HttpConnectionAdapter.readLine(MultiThreadedHttpC
onnectionManager.java:1373)
at
org.apache.commons.httpclient.HttpMethodBase.readStatusLine(HttpMethodBase.java:1832)
at
org.apache.commons.httpclient.HttpMethodBase.readResponse(HttpMethodBase.java:1590)
at
org.apache.commons.httpclient.HttpMethodBase.execute(HttpMethodBase.java:995)
at
org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java:397)
at
org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:170)
at
org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:396)
at
org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:346)
at
org.apache.axis2.transport.http.AbstractHTTPSender.executeMethod(AbstractHTTPSender.java:520)
at
org.apache.axis2.transport.http.HTTPSender.sendViaPost(HTTPSender.java:191)
... 13 more
DEBUG - GeronimoLog.trace(54) | Mex[hqejbhcnphr3vw7ivqgp9i].setPortOp(...)
14:57:11,031 DEBUG [MessageExchangeImpl]
Mex[hqejbhcnphr3vw7ivqgp9i].setPortOp(...)
DEBUG - GeronimoLog.debug(66) | replyWithFailure mex=hqejbhcnphr3vw7ivqgp9i
failureType=COMMUNICATION_ERROR description=Error
sending message (mex={PartnerRoleMex#hqejbhcnphr3vw7ivqgp9i [PID {
http://soa-matrix.com/example}Flow-4] calling org.apache.o
de.bpel.epr.WSAEndpoint@a3cf94.GetWeather(...)}): Read timed out
details=null
14:57:11,031 DEBUG [PartnerRoleMessageExchangeImpl] replyWithFailure
mex=hqejbhcnphr3vw7ivqgp9i failureType=COMMUNICATION_ERR
OR description=Error sending message
(mex={PartnerRoleMex#hqejbhcnphr3vw7ivqgp9i [PID {
http://soa-matrix.com/example}Flow-4]
calling org.apache.ode.bpel.epr.WSAEndpoint@a3cf94.GetWeather(...)}): Read
timed out details=null
DEBUG - GeronimoLog.debug(66) | create work event for
mex=hqejbhcnphr3vw7ivqgp9i
14:57:11,046 DEBUG [PartnerRoleMessageExchangeImpl] create work event for
mex=hqejbhcnphr3vw7ivqgp9i
DEBUG - GeronimoLog.debug(66) | Thread[ODEServer-19,5,main]: lock(iid=953,
time=1MICROSECONDS)
14:57:11,125 DEBUG [InstanceLockManager] Thread[ODEServer-19,5,main]:
lock(iid=953, time=1MICROSECONDS)
DEBUG - GeronimoLog.debug(66) | Thread[ODEServer-19,5,main]: lock(iid=953,
time=1MICROSECONDS)-->GRANTED
14:57:11,140 DEBUG [InstanceLockManager] Thread[ODEServer-19,5,main]:
lock(iid=953, time=1MICROSECONDS)-->GRANTED
DEBUG - GeronimoLog.debug(66) | >>
handleWorkEvent(jobData={type=INVOKE_RESPONSE, mexid=hqejbhcnphr3vw7ivqgp9i,
channel=26, i
id=953})
14:57:11,140 DEBUG [BpelProcess] >>
handleWorkEvent(jobData={type=INVOKE_RESPONSE, mexid=hqejbhcnphr3vw7ivqgp9i,
channel=26,
iid=953})
DEBUG - GeronimoLog.debug(66) | BpelRuntimeContextImpl created for instance
953. INDEXED STATE={{OScope '__PROCESS_SCOPE:Flow
' id=3}::0=[SCOPE(...)], {OScope '__PROCESS_SCOPE:Flow'
id=3}::0=[ACTIVE(...)], OSequence#36-main::1=[ACTIVITYGUARD(...)], {O
Scope 'Scope' id=60}::12=[ACTIVE(...)], {OScope 'Scope'
id=60}::11=[ACTIVITYGUARD(...)], {OScope 'Invoke' id=61}::14=[SCOPE(.
..)], {OScope 'Invoke' id=61}::14=[ACTIVE(...)], {OScope 'Scope'
id=60}::12=[SCOPE(...)], OInvoke#62-Invoke::15=[ACTIVITYGUAR
D(...)], OInvoke#62-Invoke::16=[INVOKE(...)], {OScope 'Invoke'
id=61}::13=[ACTIVITYGUARD(...)], OSequence#36-main::2=[SEQUENC
E(self=(OSequence#36-main,TerminationChannel#3,ParentScopeChannel#5),
linkframe=org.apache.ode.bpel.runtime.LinkFrame@102d823
, remaining=[{OScope 'Scope' id=60}, {OAssign : Assign, joinCondition=null},
{OScope 'InvokeConfirmation' id=88}, OReply#95-r
eplyOutput])]}
14:57:11,171 DEBUG [BpelRuntimeContextImpl] BpelRuntimeContextImpl created
for instance 953. INDEXED STATE={{OScope '__PROCES
S_SCOPE:Flow' id=3}::0=[SCOPE(...)], {OScope '__PROCESS_SCOPE:Flow'
id=3}::0=[ACTIVE(...)], OSequence#36-main::1=[ACTIVITYGUA
RD(...)], {OScope 'Scope' id=60}::12=[ACTIVE(...)], {OScope 'Scope'
id=60}::11=[ACTIVITYGUARD(...)], {OScope 'Invoke' id=61}:
:14=[SCOPE(...)], {OScope 'Invoke' id=61}::14=[ACTIVE(...)], {OScope 'Scope'
id=60}::12=[SCOPE(...)], OInvoke#62-Invoke::15=[
ACTIVITYGUARD(...)], OInvoke#62-Invoke::16=[INVOKE(...)], {OScope 'Invoke'
id=61}::13=[ACTIVITYGUARD(...)], OSequence#36-main
::2=[SEQUENCE(self=(OSequence#36-main,TerminationChannel#3,ParentScopeChannel#5),
linkframe=org.apache.ode.bpel.runtime.LinkF
rame@102d823, remaining=[{OScope 'Scope' id=60}, {OAssign : Assign,
joinCondition=null}, {OScope 'InvokeConfirmation' id=88},
OReply#95-replyOutput])]}
DEBUG - GeronimoLog.debug(66) | InvokeResponse event for iid 953
14:57:11,203 DEBUG [BpelProcess] InvokeResponse event for iid 953
DEBUG - GeronimoLog.debug(66) | Invoking message response for mexid
hqejbhcnphr3vw7ivqgp9i and channel 26
14:57:11,218 DEBUG [BpelRuntimeContextImpl] Invoking message response for
mexid hqejbhcnphr3vw7ivqgp9i and channel 26
DEBUG - GeronimoLog.debug(66) | Triggering response
14:57:11,218 DEBUG [BpelRuntimeContextImpl] Triggering response
ERROR - GeronimoLog.error(104) | Failure during invoke: Error sending
message (mex={PartnerRoleMex#hqejbhcnphr3vw7ivqgp9i [PI
D {http://soa-matrix.com/example}Flow-4] calling
org.apache.ode.bpel.epr.WSAEndpoint@a3cf94.GetWeather(...)}): Read timed out
14:57:11,234 ERROR [INVOKE] Failure during invoke: Error sending message
(mex={PartnerRoleMex#hqejbhcnphr3vw7ivqgp9i [PID {ht
tp://soa-matrix.com/example}Flow-4] calling
org.apache.ode.bpel.epr.WSAEndpoint@a3cf94.GetWeather(...)}): Read timed out
When restarted the ode, the external webservice was invoked again deu to the
following extension in the invoke activity.
<ext:failureHandling xmlns:ext="http://ode.apache.org/activityRecovery">
<ext:faultOnFailure>false</ext:faultOnFailure>
<ext:retryFor>2</ext:retryFor>
<ext:retryDelay>60</ext:retryDelay>
</ext:failureHandling>
and resumed normally.
*2nd Scenario*:
When the bpel had invoked the GlobalWeather service and was waiting for
response but not yet timedout , i shutdown the ode.
then on restarting it didnt resume the normal flow.The console message just
before the ode crashed is as below:
.......................
........................
DEBUG - GeronimoLog.debug(66) | My-Role EPR not specified, SEP will not be
used.
15:09:42,171 DEBUG [SoapExternalService] My-Role EPR not specified, SEP will
not be used.
DEBUG - GeronimoLog.debug(66) | Axis2 sending message to
http://192.168.1.150:8080/axis2/services/GlobalWeather using MEX {Pa
rtnerRoleMex#hqejbhcnphr3vwi5ao38wj [PID {
http://soa-matrix.com/example}Flow-4] calling
org.apache.ode.bpel.epr.WSAEndpoint@1
e31c3e.GetWeather(...)}
15:09:42,171 DEBUG [SoapExternalService] Axis2 sending message to
http://192.168.1.150:8080/axis2/services/GlobalWeather usin
g MEX {PartnerRoleMex#hqejbhcnphr3vwi5ao38wj [PID {
http://soa-matrix.com/example}Flow-4] calling org.apache.ode.bpel.epr.WSAE
ndpoint@1e31c3e.GetWeather(...)}
DEBUG - GeronimoLog.debug(66) | Message: <?xml version='1.0'
encoding='utf-8'?><soapenv:Envelope xmlns:soapenv="http://schema
s.xmlsoap.org/soap/envelope/"><soapenv:Body><GetWeather xmlns="
http://www.webserviceX.NET">
<ns1:CityName xmlns:ns1="
http://www.webserviceX.NET">DELHI</ns1:CityName>
<ns1:CountryName xmlns:ns1="
http://www.webserviceX.NET">INDIA</ns1:CountryName>
</GetWeather></soapenv:Body></soapenv:Envelope>
15:09:42,171 DEBUG [SoapExternalService] Message: <?xml version='1.0'
encoding='utf-8'?><soapenv:Envelope xmlns:soapenv="http
://schemas.xmlsoap.org/soap/envelope/"><soapenv:Body><GetWeather xmlns="
http://www.webserviceX.NET">
<ns1:CityName xmlns:ns1="
http://www.webserviceX.NET">DELHI</ns1:CityName>
<ns1:CountryName xmlns:ns1="
http://www.webserviceX.NET">INDIA</ns1:CountryName>
</GetWeather></soapenv:Body></soapenv:Envelope>
DEBUG - GeronimoLog.debug(66) |
org.apache.ode.axis2.SoapExternalService$CachedOptions$1@1535057 has been
modified
15:09:42,171 DEBUG [SoapExternalService$CachedOptions]
org.apache.ode.axis2.SoapExternalService$CachedOptions$1@1535057 has b
een modified
DEBUG - GeronimoLog.debug(66) | Translating IL Properties for Axis2
15:09:42,171 DEBUG [Properties] Translating IL Properties for Axis2
DEBUG - GeronimoLog.debug(66) | replyAsync mex=hqejbhcnphr3vwi5ao38wj
15:09:42,171 DEBUG [PartnerRoleMessageExchangeImpl] replyAsync
mex=hqejbhcnphr3vwi5ao38wj
DEBUG - GeronimoLog.debug(66) | Setting execution state on instance 1901
15:09:42,171 DEBUG [BpelRuntimeContextImpl] Setting execution state on
instance 1901
DEBUG - GeronimoLog.debug(66) | Sending stateful TO epr in message header
using session null
15:09:44,765 DEBUG [SessionOutHandler] Sending stateful TO epr in message
header using session null
DEBUG - GeronimoLog.debug(66) | Sending a message containing wsa endpoints
in headers for session passing.
15:09:44,765 DEBUG [SessionOutHandler] Sending a message containing wsa
endpoints in headers for session passing.
DEBUG - GeronimoLog.debug(66) | <?xml version='1.0'
encoding='utf-8'?><soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap
.org/soap/envelope/"><soapenv:Header><addr:To xmlns:addr="
http://www.w3.org/2005/08/addressing">http://192.168.1.150:8080/axi
s2/services/GlobalWeather</addr:To><addr:Action xmlns:addr="
http://www.w3.org/2005/08/addressing">http://www.webserviceX.NET/
GetWeather</addr:Action><addr:ReplyTo xmlns:addr="
http://www.w3.org/2005/08/addressing"><addr:Address>http://www.w3.org/2005/
08/addressing/anonymous</addr:Address></addr:ReplyTo><addr:MessageID
xmlns:addr="http://www.w3.org/2005/08/addressing">uuid:h
qejbhcnphr3vwi5ao38wk</addr:MessageID></soapenv:Header><soapenv:Body><GetWeather
xmlns="http://www.webserviceX.NET">
<ns1:CityName xmlns:ns1="
http://www.webserviceX.NET">DELHI</ns1:CityName>
<ns1:CountryName xmlns:ns1="
http://www.webserviceX.NET">INDIA</ns1:CountryName>
</GetWeather></soapenv:Body></soapenv:Envelope>
15:09:44,781 DEBUG [SessionOutHandler] <?xml version='1.0'
encoding='utf-8'?><soapenv:Envelope xmlns:soapenv="http://schemas.
xmlsoap.org/soap/envelope/"><soapenv:Header><addr:To xmlns:addr="
http://www.w3.org/2005/08/addressing">http://192.168.1.150:8
080/axis2/services/GlobalWeather</addr:To><addr:Action xmlns:addr="
http://www.w3.org/2005/08/addressing">http://www.webservic
eX.NET/GetWeather</addr:Action><addr:ReplyTo xmlns:addr="
http://www.w3.org/2005/08/addressing"><addr:Address>http://www.w3.or
g/2005/08/addressing/anonymous</addr:Address></addr:ReplyTo><addr:MessageID
xmlns:addr="http://www.w3.org/2005/08/addressing"
xmlns="http://www.webserviceX.NET">
<ns1:CityName xmlns:ns1="
http://www.webserviceX.NET">DELHI</ns1:CityName>
<ns1:CountryName xmlns:ns1="
http://www.webserviceX.NET">INDIA</ns1:CountryName>
</GetWeather></soapenv:Body></soapenv:Envelope>
Regards,
Rosalin
On Tue, Jan 6, 2009 at 12:41 AM, Alex Boisvert (JIRA) <ji...@apache.org>wrote:
> If ode crashes while waiting for an response to an synchronous response and while thr has yet not been any timeout , it does not resume on restarting the ode.
> --------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: ODE-473
> URL: https://issues.apache.org/jira/browse/ODE-473
> Project: ODE
> Issue Type: Bug
> Components: BPEL Runtime
> Reporter: Rosalin Pattnaik
> Priority: Critical
>
> If we have bpel extension for retry on timeout with an invoke action , but the ode crashes before the timeout has occured .And thus there is neither a timeout exception nor has it received the response which might have been lost in the time it was down .When the ode restarts which of the following shd occur:
> * The ode resumes from the invoke state ,waits for the response , timesout and retries, get the response and proceed normally.
> * The process is not resumed.
> In my case the process is not resumed in case timeout exception has not occured , but in case the timeout has occured and then the ode crashes then it retries gets the response and then completes succesfully.
> [N.B It resumed in case there was an entry into the ode_activity_recovery table , or else it didnt]
> Please find the BPEL and external service used as attachment with the query posted at ode user forum :
> http://www.nabble.com/If-ode-crashes-while-waiting-for-an-response-to-an-synchronous-response-and-while-thr-has-yet-not-been-any-timeout-%2C-Does-it-on-restarting-resume-the-process-and-the-timesout-the-invoke-activity--td21248664.html
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.