Red Hat Bugzilla – Bug 779552
SOAPProxy Service with unreachable proxy URL causes server to hang
Last modified: 2010-09-21 15:42:08 EDT
Date of First Response: 2010-02-04 14:47:44
Help Desk Ticket Reference: https://enterprise.redhat.com/issue-tracker/848373
As documented in JBESB-2947, if I use an http url for a local JBossWS hosted web services, the server hangs. I replace the url with the internal url and the server starts fine.
However, if the http url was for a service on another server, and that server was not reachable (e.g., I put it a bogus IP address for the servername), I found that it also causes the server to hang. In this case there is an error message at least:
12:16:16,896 INFO [EsbDeployment] Starting ESB Deployment 'UpdateStatusService.esb'
12:17:32,514 INFO [HttpMethodDirector] I/O exception (java.net.SocketException) caught when processing request: Network is unreachable
12:17:32,514 INFO [HttpMethodDirector] Retrying request
This server is still hung (e.g. jmx-console is not available). However it is not hung quite as bad, it will at least shut down without doing a kill -9.
This seems problematic to me, since a customer cannot guarantee that their real services are always running when they startup their ESB, and hanging the server is never acceptable.
Need to register HttpMethodParams.RETRY_HANDLER and extend it to other exceptions, default seems to be DefaultHttpMethodRetryHandler.
Link: Added: This issue depends JBESB-3172
FYI, the hanging only appears to happen on Mac OS, which SOA-P does not provide production support for, so we are putting this one aside for now.
Security: Removed: JBoss Internal Added: Public
Additional information about the environment from Brad Davis: "This is the case with Windows XP with Java 1.6.0_18-b07 as well."
Help Desk Ticket Reference: Added: https://enterprise.redhat.com/issue-tracker/848373
This has not been seen in a windows environment until now (we test on windows). Can we please have a log file attached to this case?
I have the fix completed locally (dead easy) that registers our own HttpMethodRetryHandler which (in addition to what DefaultHttpMethodRetryHandler checks for) also checks for a generic SocketException. This should account for the Mac JDK vs. Linux JDK behavioral difference. However, I am hesitating checking it in until I see a log file for the Windows JDK environment That Martin/Brad mentioned. I want to make sure we cover that as well. So, as Kevin requested, a log file would be much appreciated. Thanks!
Tom Cunningham verified my fix on his Mac, so I have committed the fix for JBESB-3172 on trunk. It will be included in .org ESB 4.9.
Now, since THIS issue (SOA-1928) is a platform issue, and we do not yet provide customer support for Mac OS, I don't know when there will be an associated JBESB issue that targets a platform CP release. But when there is, it will be an easy port.
MAC OS is not supported with SOA-P 5.x and there are no plans to do so.