• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

Proxy settings being lost between two webservice calls

 
Greenhorn
Posts: 1
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Dear community,

I have a webservice client running under WebSphere 6.1 with the traffic going through our company proxy and SSL.
Our https.proxy settings are defined at the jvm level.

On the first call of the webservice, everything goes fine. At that time, we receive a http 302 redirect with a new URL (same domain with other parameters).
With the setting com.ibm.wsspi.webservices.Constants.HTTP_REDIRECT_ENABLED, Websphere is following the new link but gives the following error:

WebServicesFault
faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.generalException
faultString: WSWS3713E: La connexion à l'hôte éloigné *** a échoué. L'erreur suivante a été reçue java.nio.channels.UnresolvedAddressException.
faultActor: null
faultDetail:

WSWS3713E: La connexion à l'hôte éloigné *** a échoué. L'erreur suivante a été reçue java.nio.channels.UnresolvedAddressException.
at com.ibm.ws.webservices.engine.transport.http.HttpOutboundChannelConnection.connect(HttpOutboundChannelConnection.java:933)
at com.ibm.ws.webservices.engine.transport.http.HttpsOutboundChannelConnection.connect(HttpsOutboundChannelConnection.java:210)
at com.ibm.ws.webservices.engine.transport.http.HTTPSender.invoke(HTTPSender.java:578)

It's like that on the second call to the same destination, WebSphere is not using the proxy settings anymore.

Is that a normal behaviour, how could I force the proxy settings usage on a http 302 redirect ?

Thanks for your hints,

Regards,
François
 
Without deviation from the norm, progress is not possible - Zappa. Tiny ad:
a bit of art, as a gift, the permaculture playing cards
https://gardener-gift.com
reply
    Bookmark Topic Watch Topic
  • New Topic