[kconner]

This issue is due to different networking behaviour in the Mac JDK, and causes HttpClient to hang.

[kconner]

Correction, it doesn't hang but keep retrying.

[dward]

I know that's what the issue was originally triggered by, but I would like to address all hanging possibilities as part of the resolution.

[bradsdavis]

I do think failing is an issue in the sense that even if the remote service comes back online, this one never will.

Sounds like a Feature Request to me. 

Sure, call it whatever you would like.  This is a customer issue; it is discussed in Customer Support Portal issues: 832723 and 832723.

[bradsdavis]

If it happens in the Mac JDK, it also happens on the Windows JDK, as I am using Windows XP + Java 6.

[kconner]

But this is very different from what Brad is asking for.

Kev

[kconner]

No, it doesn't.  You are confusing two different issues.

Kev

[bradsdavis]

I am asking for 2 things in this post.

1) The server does not hang under any circumstance due to the fact that the JBoss bind address is the same as the underlying Soap Service.

2) The SoapProxy is more tolerant moving forward in how it handles a remote service not being available when the server restarts.

[bradsdavis]

Kevin Conner wrote:

No, it doesn't.  You are confusing two different issues.

Kev

No what doesn't?  Be more explicit.

[dward]

The quickstarts do show it.  However I will admit that the documentation is weak in this area.  I will create a JIRA for it.

https://jira.jboss.org/jira/browse/JBESB-3303

[dward]

David Ward wrote:

The quickstarts do show it.  However I will admit that the documentation is weak in this area.  I will create a JIRA for it.

https://jira.jboss.org/jira/browse/JBESB-3303 is for trunk feeding JBoss.org ESB 4.9 and is closed.

https://jira.jboss.org/jira/browse/JBESB-3304 is for the JBESB_4_7_CP branch feeding JBoss.com SOA-P 5.0.x and is closed.

https://jira.jboss.org/jira/browse/SOA-2072 is the dependent SOA-P issue for JBoss.com SOA-P 5.0.2 and is pending acceptance.