axis-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Oscar Rugama <oscas...@hotmail.com>
Subject RE: Errnn238 after boot calling web services
Date Sun, 11 Nov 2012 10:18:09 GMT

Thanks for answering, but it´s sure the url works, because as i said just undeploy a redeploy
and all works fine. Also i made a standalone client to test connectivity and it works when
at axis1.4 fails



> Date: Sun, 11 Nov 2012 06:25:29 -0300
> Subject: Re: Errnn238 after boot calling web services
> From: robertlazarski@gmail.com
> To: java-user@axis.apache.org
> 
> On Sun, Nov 11, 2012 at 5:28 AM, Oscar Rugama <oscaster@hotmail.com> wrote:
> <snip>
> > 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.
> >
> <snip>
> > 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
> 
> At the time of the client calls, I would verify that the OS, ie
> outside Java, could connect to the url and port of whatever gives the
> error "Connection timed out" . In Linux I would do that in the client
> code via netcat and Runtime.exec() , but that's just one example.
> 
> If the problem is still in Java I'd try URLConnection and keep
> narrowing it down to perhaps considering another client besides Axis
> 1.4, or at least looking if its a fixed Jira issue.
> 
> - R
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-user-unsubscribe@axis.apache.org
> For additional commands, e-mail: java-user-help@axis.apache.org
> 
 		 	   		  
Mime
View raw message