A few weeks ago, I wrote on this list about some issues I had with
SOAPConnection through an authenticated proxy (and basic auth and SSL).
I resolved those problems. I have a standalone app that can send my
message through this, and it works fine.
I then proceeded to develop this service call in WebLogic 8.1.4. My
first attempt used straight HTTP through the HTTPClient package. This
was able to get through the authorization, but I decided I'd prefer to
use a more standard framework for SOAP connections.
I first tried using Axis, because we already had a framework class to do
this. This was failing with the following error message:
"Unrecognized SSL message, plaintext connection?"
I found no useful information about this, so I decided to try to modify
the framework code to do exactly what my standalone app was doing, using
SOAPConnection. This is also failing, but with a different error
message:
<Aug 15, 2006 10:19:26 AM PDT> <Error> <Net> <BEA-000903> <Failed to
communicate with proxy: proxy/8080. Will try connection www.../443 now
(last hostname elided).
Note that I'm setting the same system properties and values in both the
standalone app and WLS. I've never seen really authoritative guidance
on which of those properties needs to be set, so I set all of them:
prop[http.proxyHost] value[proxy]
prop[http.proxyPort] value[8080]
prop[http.proxySet] value[true]
prop[https.proxyHost] value[proxy]
prop[https.proxyPort] value[8080]
prop[proxyHost] value[proxy]
prop[proxyPort] value[8080]
I've tried variations using the fully-qualified hostname for the proxy,
but that made no difference.
I would appreciate any useful guidance on this.