I'm seeing the same problem, with some simple test code.  It does not occur in 
2.7.13, but does in 2.7.14.  I've build gSOAP the same way both times 
(--enable-ssl --enable-debug).  I've traced it down the the select call in the 
new tcp_select routine, where is appears to wait for the default 10 seconds.  I 
haven't changed any of the timeout values.  Still working on it....

System: CentOS5.2, i386, gcc 4.1.2
  C++ client/server, built with pthreads 
  linked with "-lgsoapssl++ -lssl -lz -lpthread "


-Rob


--- In [email protected], "Robert" <enge...@...> wrote:
>
> 
> Our tests do not show the problem, though I have not tested on Fedora 11, 
> Ubuntu 9.04 and Ubuntu 8.04 LTS.
> 
> You can also try the samples/webserver. Compile and run with:
> 
> ./webserver 8081
> 
> open your browser to https://127.0.0.1:8081/test.html and try the links. By 
> default, the server does not use keep-alive so you would immediately notice a 
> slowdown if the problem occurs on the server side.
> 
> Maybe ssldump can help.
> 
> - Robert
> 
> --- In [email protected], Andrea Tassi <andrea.tassi@> wrote:
> >
> > Am I really alone with these problems?
> > 
> > Regards
> > Andrea
> > 
> > On Sun, Sep 20, 2009 at 9:10 AM, Andrea Tassi <andrea.tassi@>wrote:
> > 
> > > Only a little update: the problem is present also in the gSOAP 2.7.14 of
> > > September 20.
> > >
> > > Andrea
> > >
> > >
> > > On Fri, Sep 18, 2009 at 7:38 PM, Andrea Tassi <andrea.tassi@>wrote:
> > >
> > >> Hi,
> > >>
> > >> I'm testing the new gSOAP 2.7.14 but I'm experiencing a strange behavior.
> > >> The problem can be reproduced with the sslserver/sslclient in the
> > >> gsoap/sample folder:
> > >>
> > >>    1.
> > >>
> > >>    start the sslserver
> > >>    2.
> > >>
> > >>    perform a request with the sslclient
> > >>
> > >> you can see that the server response is very very slow respect to the
> > >> gSOAP 2.7.13 version. This problem is present in Fedora 11, Ubuntu 9.04 
> > >> and
> > >> Ubuntu 8.04 LTS.
> > >> Any ideas?
> > >>
> > >> Thanks
> > >> Andrea
> > >>
> > >
> >
>


Reply via email to