On Mon, Nov 23, 2009 at 8:46 PM, pwillemann <philwillem...@yahoo.com> wrote:

>
> Thank you for your answer, however it does not seem to work..  I get the
> same
> error as before:
> Here is a code snippet which implemented the suggested solution.
>
> public GetAOIResponse getAOI(GetAOI request) throws SSBException {
>                GetAOIResponse response = new GetAOIResponse();
>                try {
>                        response = cistub.getAOI(request);
>                        cistub._getServiceClient().cleanupTransport();   //
> Axis 2 V1.5.1
>                } catch (AxisFault af) {
>                        logger.error("Error with the local webservice", af);
>                        af.printStackTrace();
>                } catch (RemoteException re) {
>                        logger.error("Cannot connect to local webservice",
> re);
>                        re.printStackTrace();
>                } catch (SSBException e) {
>                        e.printStackTrace();
>                }
>                return response;
>        }
>
> This method will be called many times during its lifetime and I reuse
> cistub.  Is that a problem?   I would like to avoid instantiating a new
> stub
> everytime if possible.
>

Can you check with Axis2 1.5?

thanks,
Amila.

>
> Thanks for any help or suggestions
>
> Phil Willemann
>
>
> Amila Suriarachchi wrote:
> >
> > On Fri, Nov 13, 2009 at 11:02 PM, pwillemann
> > <philwillem...@yahoo.com>wrote:
> >
> >>
> >> I used WSDL2Java to create all my Web service classes.  I do not have
> any
> >> custom code.  Everything in my project is autogenerated.  My web service
> >> works fine in Axis 2 version 1.3 and Axis 2 version 1.4.1.  When I
> >> migrated
> >> to 1.5.1 I get timeouts.  Specifically the error says:
> >>
> >> HTTPSender.sendViaPost INFO - Unable to sendViaPost to
> >> url[http://127.0.0.1:8080/mywebservice/]
> >> org.apache.commons.httpclient.ConnectionPoolTimeoutException:  Timeout
> >> waiting for connection.
> >>
> >> I looked to see if there was a migration guide from 1.3/1.4 to 1.5 that
> >> addresses this issue, however I have been unable to find one.  This web
> >> service has worked for almost a year, but I am curious if the new
> version
> >> of
> >> Axis has revealed some sort of flaw or if there is an actual problem in
> >> 1.5.1.
> >>
> >> Has anyone had a similar problem or has anyone solved this problem? Any
> >> help
> >> would be appreciated very much.  Thanks!
> >>
> >
> > call stub._getServiceClient().cleanupTransport();
> > after service invocation.
> >
> > thanks,
> > Amila.
> >
> >>
> >> Sincerely yours
> >> Phil Willemann
> >>
> >> --
> >> View this message in context:
> >>
> http://old.nabble.com/WS-works-in-Axis-2-1.3-and-1.4.1-but-has-timeout-in-Axis-1.5.1--tp26340326p26340326.html
> >> Sent from the Axis - User mailing list archive at Nabble.com.
> >>
> >>
> >
> >
> > --
> > Amila Suriarachchi
> > WSO2 Inc.
> > blog: http://amilachinthaka.blogspot.com/
> >
> >
>
> --
> View this message in context:
> http://old.nabble.com/WS-works-in-Axis-2-1.3-and-1.4.1-but-has-timeout-in-Axis-1.5.1--tp26340326p26479852.html
> Sent from the Axis - User mailing list archive at Nabble.com.
>
>


-- 
Amila Suriarachchi
WSO2 Inc.
blog: http://amilachinthaka.blogspot.com/

Reply via email to