-
1. Re: How to set mex.timeout?
jeff.yuchang Jan 27, 2010 12:10 AM (in response to steeqs4)This configuration is just for the ODE, which uses the axis2 to invoke the webservice, while Riftsaw is using JBossWS. I just checked the code, found currently we didn't have an option for the mex.timeout config, it is hard-coded as 2 mins. I've created a jira for it: https://jira.jboss.org/jira/browse/RIFTSAW-156.
-
2. Re: How to set mex.timeout?
steeqs4 Jan 27, 2010 9:37 AM (in response to jeff.yuchang)Thanks Jeff. -
3. Re: How to set mex.timeout?
objectiser Jan 29, 2010 7:03 AM (in response to steeqs4)Hi Martin
There is a snapshot available that may fix this problem, see https://jira.jboss.org/jira/browse/RIFTSAW-156 for more details.
Further testing required, but if you wanted something to try urgently, then you may want to give it a go.
Regards
Gary
-
4. Re: How to set mex.timeout?
clsimone Mar 25, 2011 9:16 AM (in response to objectiser)Hi,
I hope that I address my problem on the right topic. I have a process that is invoking a WS that responds only in within 3 minutes and 30 seconds. I have a file.endpoint where I have specified the mex.timeout=240000, but the process throws the "Read timeout error" after only 1 minute and 20 seconds. Do you have any idea why it's ignoring this parameter? Or if there is another way to do this?
Interceptor for {http://..._Service#{http://cxf.apache.org/jaxws/dispatch}Invoke has thrown exception, unwinding now
org.apache.cxf.interceptor.Fault: Could not send Message....
Caused by: java.net.SocketTimeoutException: SocketTimeoutException invoking http://127.0.0.1:8080/...: Read timed out
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
-
5. Re: How to set mex.timeout?
objectiser Mar 25, 2011 9:48 AM (in response to clsimone)Hi Laura
Yes this should be supported, as described here: http://docs.jboss.org/riftsaw/releases/2.2.0.Final/userguide/html/deploy.html#d0e717
If you could raise a jira with the relevant details about your environment and a testcase then we can take a look.
Regards
Gary
-
6. Re: How to set mex.timeout?
clsimone Mar 28, 2011 3:24 AM (in response to steeqs4)Hi Gary,
I tested the HelloWorld example in my environmeny and it works, my question is: this timeout is it considered when doing an invoke activity? I mean when waiting for an invoke response is it waiting that amount of time, before continuing with the rest of activities?
Thank you,
Laura
-
7. How to set mex.timeout?
objectiser Mar 28, 2011 5:31 AM (in response to clsimone)Hi Laura
Yes the same mechanism applies to the invocation of external services.
Regards
Gary
-
8. Re: How to set mex.timeout?
clsimone Apr 12, 2011 9:08 AM (in response to objectiser)Hi Gary,
Thank you for your response. My use case is very strange... my service invoke is still timing out. I have tried to invoke from my process the HelloWorld process (that is waiting 3 minutes before responding) and also this case is working. I think it should not be any difference between invoking a web service and a bpel service, but this is my case there is something that I just can't figure out. Do you have any ideas what else I could try?
Thank you,
Laura
-
9. Re: How to set mex.timeout?
objectiser Apr 12, 2011 9:29 AM (in response to clsimone)Hi Laura
The only other thing would be to put together a simple testcase that reproduces the problem and raise a bug in our jira with it attached, then we can see if we can reproduce it.
Regards
Gary
-
10. How to set mex.timeout?
objectiser Apr 21, 2011 12:17 PM (in response to objectiser)Hi Laura
Thanks for providing the example, this has helped to locate the issue.
The problem appears to be that when invoking another BPEL process, this is using the internal process to process communications and therefore subject to the timeout for the process being invoked.
When invoking a jaxws service, this is subject to the underlying http request timeout.
I have been experimenting with setting this timeout value through the jaxws API, but so far it is not working as documented here: http://community.jboss.org/wiki/JBossWS-UserGuide#Oneway_Invocations_117717.
The other issue is that the jaxws spec did not standardise how these properties should be defined, so implementations have selected their own approach - e.g. the sun reference impl uses a different set of properties.
Regards
Gary
-
11. How to set mex.timeout?
objectiser Apr 21, 2011 1:17 PM (in response to objectiser)Should be fixed, and available from http://hudson.jboss.org/hudson/job/RiftSaw/ job #366 shortly. However this will depend upon jbossws-native or cxf 3.4.0.GA.
Regards
Gary
-
12. Re: How to set mex.timeout?
clsimone Apr 22, 2011 1:47 AM (in response to objectiser)Hi Gary,
Thank you for your response. I understand that the problem is on the jaxws service side, but why is there a fix also on the Riftsaw?
http://hudson.jboss.org/hudson/job/RiftSaw/ job #366
What I don't understand is why in my environment is working .
Regards,
Laura
-
13. Re: How to set mex.timeout?
objectiser Apr 22, 2011 6:41 AM (in response to clsimone)The reason for the riftsaw change was to apply the timeout value to the jaxws implementation specific property name - and which is only available in jbossws 3.4.0.GA.
Regards
Gary
-
14. Re: How to set mex.timeout?
clsimone May 2, 2011 4:12 AM (in response to objectiser)What is your feeling about the "RIFTSAW-378 Testcase required for jaxws client timeout"? I would need to know if it's feasible to wait for this change or I should look for another solution.
Regards,
Laura