Josef and Team
I ran into the same exact error earlier this year..when I ran curl --trace LOG
thru the proxy I could see that the proxy server was mangling the request
Headers
I was able to locate the Proxy documentation directives to disable Header
Mangling and did so
Once the headers transmitted unmangled our authentication worked correctly and
our web services operated within prescribed timeouts
*gruss*
Martin
______________________________________________
Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité
Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger
sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung
oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem
Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung.
Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung
fuer den Inhalt uebernehmen.
Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le
destinataire prévu, nous te demandons avec bonté que pour satisfaire informez
l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est
interdite. Ce message sert à l'information seulement et n'aura pas n'importe
quel effet légalement obligatoire. Étant donné que les email peuvent facilement
être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité
pour le contenu fourni.
Subject: AW: AW: Errnn238 after boot calling web services
Date: Tue, 13 Nov 2012 13:52:03 +0100
From: josef.stadelm...@axa-winterthur.ch
To: java-user@axis.apache.org
The VM of Tomcat must know about that; i.e. in Tomcat for Windowscatalina.sh
shows# CATALINA_OPTS (Optional) Java runtime options used when the
"start",# "run" or "debug" command is executed.#
Include here and not in JAVA_OPTS all options, that should#
only be used by Tomcat itself, not by the stop process,#
the version command etc.# Examples are heap size, GC logging,
JMX ports etc.So it is a Java switch when it comes to launch Tomcat which must
be set. It is (in our company) a hint for the ProxyServer to straight start
with Basic authentication, i.e. it shall not start with negotiating cycles,
i.e. it shall not using NTLM authentication first and if that fails use Basic
authentication (as they normally do). Also in your case, I would use WireShark,
a network protocol analyzer, to see what happens on the network level.You will
then see immediately if your proxy server allows you to reach out to the
intranet web server, or if already this fails due to missing or bad
authentication or due to entering into a lengthy negotiation cycles which might
be badly supported by your client (Tomcats JVM) Josef Von: Oscar Rugama
[mailto:oscas...@hotmail.com]
Gesendet: Dienstag, 13. November 2012 09:47
An: java-user@axis.apache.org
Betreff: RE: AW: Errnn238 after boot calling web services How can u use this '
-Dhttp.auth.preference=Basic'?
Thanks
OscarSubject: AW: Errnn238 after boot calling web services
Date: Tue, 13 Nov 2012 09:21:12 +0100
From: josef.stadelm...@axa-winterthur.ch
To: java-user@axis.apache.orgMaybe you need this as well
-Dhttp.auth.preference=Basicdepending on the negotiating schema your proxy is
using.Josef Von: Oscar Rugama [mailto:oscas...@hotmail.com]
Gesendet: Dienstag, 13. November 2012 08:12
An: java-user@axis.apache.org
Betreff: RE: Errnn238 after boot calling web services Hi,
I configure http connection like that:
http
System.setProperty("http.proxySet", "true");
System.setProperty("http.proxyHost",
ConfigurationManager.getProperty("ws.proxy.host"));
System.setProperty("http.proxyPort",
ConfigurationManager.getProperty("ws.proxy.port"));
System.setProperty("http.proxyType",ConfigurationManager.getProperty("ws.proxy.type"));
System.setProperty("http.proxyUser", proxyUser);
System.setProperty("http.proxyPassword", proxyPassword);
https
System.setProperty("https.proxySet",ConfigurationManager.getProperty("asnef.proxySet"));
System.setProperty("https.proxyHost",ConfigurationManager.getProperty("ws.proxy.host"));
System.setProperty("https.proxyPort",ConfigurationManager.getProperty("ws.proxy.port"));
System.setProperty("https.proxyType",ConfigurationManager.getProperty("ws.proxy.type"));
System.setProperty("https.proxyUser", proxyUser);
System.setProperty("https.proxyPassword", proxyPassword);
As i said in one mail before, all this code works until we re-start tomcat
(shutdown and startup) when it stars to fail and get errn238
Thank you very much
Kind regards,
Oscar
> From: andreas.veit...@gmail.com
> Date: Mon, 12 Nov 2012 19:35:13 +0100
> Subject: Re: Errnn238 after boot calling web services
> To: java-user@axis.apache.org
>
> The problem is that the following line in the stack trace is in the
> code path that is executed for direct connections:
>
> at
> org.apache.axis.components.net.DefaultSocketFactory.create(DefaultSocketFactory.java:120)
>
> How do you configure the HTTP proxy to be used by your Web application?
>
> Andreas
>
> On Mon, Nov 12, 2012 at 7:24 PM, Oscar Rugama <oscas...@hotmail.com> wrote:
> >
> > It goles through a Http Proxy, no direct connection
> >
> > Thanks
> > Oscar
> >
> > El 12/11/2012, a las 19:19, "Andreas Veithen" <andreas.veit...@gmail.com>
> > escribió:
> >
> >> Are these connections expected to go through an HTTP proxy or are they
> >> direct connections?
> >>
> >> Andreas
> >>
> >> On Mon, Nov 12, 2012 at 8:18 AM, Oscar Rugama <oscas...@hotmail.com> wrote:
> >>>
> >>> Hi Andreas,
> >>>
> >>> Please find attached stack trace of the ConnectException?
> >>>
> >>> Thanks in advance
> >>> Kind regards,
> >>> Oscar
> >>>
> >>>
> >>>
> >>>> From: andreas.veit...@gmail.com
> >>>> Date: Sun, 11 Nov 2012 20:09:56 +0100
> >>>
> >>>> Subject: Re: Errnn238 after boot calling web services
> >>>> To: java-user@axis.apache.org
> >>>
> >>>>
> >>>> Do you have the complete stack trace of the ConnectException?
> >>>>
> >>>> Andreas
> >>>>
> >>>> On Sun, Nov 11, 2012 at 9:28 AM, Oscar Rugama <oscas...@hotmail.com>
> >>>> wrote:
> >>>>> Hi
> >>>>>
> >>>>> I have been looking for a solution for the following during last two
> >>>>> weeks
> >>>>> and i´am becoming almost crazy, so any help will be welcomed
> >>>>>
> >>>>> I have a Web Service with Axis2 that publish several methods. One of
> >>>>> this
> >>>>> methods call two external (Internet) Web Services so for this web
> >>>>> services i
> >>>>> am a client. The client for this Web Services is made with Axis 1.4.
> >>>>>
> >>>>> I can say that all works fine but when we boot the web server (tomcat
> >>>>> and i
> >>>>> have also test in JBoss) the client for this web services don´t work it
> >>>>> raises
> >>>>>
> >>>>> AxisFault
> >>>>> faultCode:
> >>>>> {http://schemas.xmlsoap.org/soap/envelope/}Server.userException
> >>>>> faultSubcode:
> >>>>> faultString: java.net.ConnectException: Connection timed out (errno:238)
> >>>>> faultActor:
> >>>>> faultNode:
> >>>>> faultDetail:
> >>>>> {http://xml.apache.org/axis/}stackTrace:java.net.ConnectException:
> >>>>> Connection timed out (errno:238)
> >>>>>
> >>>>> When trying to connect to the external Web Services. The rest of the
> >>>>> methods
> >>>>> i publish in Axis2 if they don´t have to call these external web
> >>>>> services,
> >>>>> works fine.
> >>>>>
> >>>>> Tomcat server 6 and jdk 1.5 (also tested with 1.6)
> >>>>>
> >>>>> I´m becoming crazy because this source code works fine until a boot is
> >>>>> made
> >>>>> and after that calling external web services don´t work. To make it work
> >>>>> i
> >>>>> have to undeploy mi Web Service un Axis2 an redeploy and sometimes i
> >>>>> also
> >>>>> have to redeploy Axis2.
> >>>>>
> >>>>> Any idea please?
> >>>>>
> >>>>> Thanks in advance
> >>>>> Oscar
> >>>>
> >>>> ---------------------------------------------------------------------
> >>>> To unsubscribe, e-mail: java-user-unsubscr...@axis.apache.org
> >>>> For additional commands, e-mail: java-user-h...@axis.apache.org
> >>>>
> >>>
> >>>
> >>> ---------------------------------------------------------------------
> >>> To unsubscribe, e-mail: java-user-unsubscr...@axis.apache.org
> >>> For additional commands, e-mail: java-user-h...@axis.apache.org
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: java-user-unsubscr...@axis.apache.org
> >> For additional commands, e-mail: java-user-h...@axis.apache.org
> >>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-user-unsubscr...@axis.apache.org
> For additional commands, e-mail: java-user-h...@axis.apache.org
>
