On Wednesday 10 December 2008 4:39:35 am Alexey Zavizionov wrote:
> Any suggestions ?

No idea.    Maybe tomcat has a security manager or something that prevents it.  
 
Or maybe the tomcat server itself has some setting that if the servlet 
doesn't respond in 60 secs or something, it assumes the servlet is hung and 
closes the connection.   I don't really know.  

Dan


>
> On Thu, Dec 4, 2008 at 4:59 PM, Alexey Zavizionov
>
> <[email protected]> wrote:
> > I tested in a tomcat before, any setReceiveTimeout and
> > setConnectionTimeout didn't affect, after 60 seconds it fails.
> >
> > Dec 4, 2008 4:03:01 PM
> > org.apache.cxf.service.factory.ReflectionServiceFactoryBean
> > buildServiceFromWSDL
> > INFO: Creating Service {urn:oasis:names:tc:wsrp:v2:wsdl}WSRPService
> > from WSDL:
> > http://localhost:8080/wsrp/soap/services/WSRP_v2_Markup_Service?wsdl
> > Invoking getServiceDescription...
> > [INFO] WSRPV2ServiceDescriptionPortTypeImpl - Executing operation
> > getServiceDescription
> > null
> > [en]
> > []
> > null
> > Dec 4, 2008 4:04:01 PM org.apache.cxf.phase.PhaseInterceptorChain
> > doIntercept INFO: Interceptor has thrown exception, unwinding now
> > org.apache.cxf.interceptor.Fault: Could not send Message.
> >        at
> > org.apache.cxf.interceptor.MessageSenderInterceptor$MessageSenderEndingIn
> >terceptor.handleMessage(MessageSenderInterceptor.java:64) at
> > org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorCh
> >ain.java:220) at
> > org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:296) at
> > org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:242) at
> > org.apache.cxf.frontend.ClientProxy.invokeSync(ClientProxy.java:73) at
> > org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:178)
> > at $Proxy46.getServiceDescription(Unknown Source)
> >
> >
> > I have tested in a JUnit and it works! Junit publishing service within
> > jetty container.
> >
> > What It could be with tomcat?
> >
> > Apache Tomcat Version 6.0.16
> >
> > Thanks and regards,
> > Alexey.
> >
> > --
> >
> >
> > On Thu, Dec 4, 2008 at 1:11 PM, Alexey Zavizionov
> >
> > <[email protected]> wrote:
> >> For me it doesn't work
> >>
> >> Caused by: java.net.SocketTimeoutException: Read timed out
> >>        at java.net.SocketInputStream.socketRead0(Native Method)
> >>        at java.net.SocketInputStream.read(SocketInputStream.java:129)
> >>        at java.io.BufferedInputStream.fill(BufferedInputStream.java:218)
> >>        at
> >> java.io.BufferedInputStream.read1(BufferedInputStream.java:256) at
> >> java.io.BufferedInputStream.read(BufferedInputStream.java:313) at
> >> sun.net.www.http.HttpClient.parseHTTPHeader(HttpClient.java:659) at
> >> sun.net.www.http.HttpClient.parseHTTP(HttpClient.java:604) at
> >> sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnec
> >>tion.java:961) at
> >> java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:367)
> >> at
> >> org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResp
> >>onse(HTTPConduit.java:1937) at
> >> org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.close(HTTP
> >>Conduit.java:1865) at
> >> org.apache.cxf.transport.AbstractConduit.close(AbstractConduit.java:66)
> >> at org.apache.cxf.transport.http.HTTPConduit.close(HTTPConduit.java:593)
> >> at
> >> org.apache.cxf.interceptor.MessageSenderInterceptor$MessageSenderEndingI
> >>nterceptor.handleMessage(MessageSenderInterceptor.java:62) ... 31 more
> >>
> >>
> >> On Wed, Dec 3, 2008 at 6:36 PM, Alexey Zavizionov
> >>
> >> <[email protected]> wrote:
> >>> Okay, thanks
> >>>
> >>> Would you modify that code on wiki with
> >>>  Client client = ClientProxy.getClient(greeter);
> >>>
> >>> I will try setConnectionTimeout tomorrow.
> >>>
> >>> Regards,
> >>> Alexey
> >>>
> >>> On Wed, Dec 3, 2008 at 6:26 PM, Daniel Kulp <[email protected]> wrote:
> >>>> On Wednesday 03 December 2008 11:24:06 am Alexey Zavizionov wrote:
> >>>>> Hello, thanks for reply
> >>>>>
> >>>>> There is a line
> >>>>> Client client = ClientProxy.getClient(poltim);
> >>>>> what is it "poltim" ?
> >>>>
> >>>> It's your client proxy object that implements your service interface.
> >>>>
> >>>> Dan
> >>>>
> >>>>> Regards,
> >>>>> Alexey
> >>>>>
> >>>>> On Wed, Nov 26, 2008 at 7:21 PM, Andi Abes <[email protected]> wrote:
> >>>>> > To configure client side parameters in general, see
> >>>>> >
> >>>>> > http://cwiki.apache.org/CXF20DOC/client-http-transport-including-ss
> >>>>> >l-sup port.html
> >>>>> >
> >>>>> >
> >>>>> > The part you're looking for is the attribute ReceiveTimeout, which
> >>>>> > by default is 60 seconds- it is specified in millis. Based on the
> >>>>> > schema doc, a value of 0 should make the wait infinite.
> >>>>> >
> >>>>> >
> >>>>> > Should look something like this (but I havent't tried it yet)
> >>>>> >
> >>>>> > <http-conf:conduit name="*.http-conduit">
> >>>>> >  <http-conf:client  ReceiveTimeout ="0"/>
> >>>>> >
> >>>>> > </http-conf:conduit>
> >>>>> >
> >>>>> > A.
> >>>>> >
> >>>>> >> -----Original Message-----
> >>>>> >> From: Michael Ramnarine [mailto:[email protected]]
> >>>>> >> Sent: Wednesday, November 26, 2008 12:05 PM
> >>>>> >> To: [email protected]
> >>>>> >> Subject: RE: While debugging - SocketTimeoutException: Read timed
> >>>>> >> out
> >>>>> >>
> >>>>> >> Pausing the reader thread helps this situation (in eclipse debug
> >>>>> >> view
> >>>>> >
> >>>>> > /
> >>>>> >
> >>>>> >> call stack / right click on reader thread and pause it).
> >>>>> >>
> >>>>> >> If someone can explain how to configure the http connection to
> >>>>> >
> >>>>> > increase
> >>>>> >
> >>>>> >> the timeout, that would a bit more work, but would be even better.
> >>>>> >>
> >>>>> >> -Mike
> >>>>> >>
> >>>>> >> > -----Original Message-----
> >>>>> >> > From: Alexey Zavizionov [mailto:[email protected]]
> >>>>> >> > Sent: Wednesday, November 26, 2008 11:55 AM
> >>>>> >> > To: [email protected]
> >>>>> >> > Subject: While debugging - SocketTimeoutException: Read timed
> >>>>> >> > out
> >>>>> >> >
> >>>>> >> > Hello, list
> >>>>> >> >
> >>>>> >> > When I use debugger I see timed out exception.
> >>>>> >> > How can I fix it?
> >>>>> >> >
> >>>>> >> > Caused by: java.net.SocketTimeoutException: Read timed out
> >>>>> >> >         at java.net.SocketInputStream.socketRead0(Native Method)
> >>>>> >> >         at
> >>>>> >> > java.net.SocketInputStream.read(SocketInputStream.java:129)
> >>>>> >> >         at
> >>>>> >> > java.io.BufferedInputStream.fill(BufferedInputStream.java:218)
> >>>>> >> >         at
> >>>>> >> > java.io.BufferedInputStream.read1(BufferedInputStream.java:256)
> >>>>> >> >         at
> >>>>> >> > java.io.BufferedInputStream.read(BufferedInputStream.java:313)
> >>>>> >> >         at
> >>>>> >> > sun.net.www.http.HttpClient.parseHTTPHeader(HttpClient.java:659)
> >>>>> >> >         at
> >>>>> >
> >>>>> > sun.net.www.http.HttpClient.parseHTTP(HttpClient.java:604)
> >>>>> >
> >>>>> >> >         at
> >>>>> >
> >>>>> > sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLC
> >>>>> >on
> >>>>> >
> >>>>> >> > nection.java:961)
> >>>>> >> >         at
> >>>>> >
> >>>>> > java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:3
> >>>>> >67
> >>>>> >
> >>>>> >> > )
> >>>>> >> >         at
> >>>>> >
> >>>>> > org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handl
> >>>>> >eR
> >>>>> >
> >>>>> >> > esponse(HTTPConduit.java:1937)
> >>>>> >> >         at
> >>>>> >
> >>>>> > org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.close
> >>>>> >(H
> >>>>> >
> >>>>> >> > TTPConduit.java:1865)
> >>>>> >> >         at
> >>>>> >
> >>>>> > org.apache.cxf.transport.AbstractConduit.close(AbstractConduit.java
> >>>>> >:6
> >>>>> >
> >>>>> >> > 6)
> >>>>> >> >         at
> >>>>> >
> >>>>> > org.apache.cxf.transport.http.HTTPConduit.close(HTTPConduit.java:59
> >>>>> >3)
> >>>>> >
> >>>>> >> >         at
> >>>>> >
> >>>>> > org.apache.cxf.interceptor.MessageSenderInterceptor$MessageSenderEn
> >>>>> >di
> >>>>> >
> >>>>> >> > ngInterceptor.handleMessage(MessageSenderInterceptor.java:62)
> >>>>> >> >
> >>>>> >> >
> >>>>> >> >
> >>>>> >> >
> >>>>> >> > Regards,
> >>>>> >> > Alexey
> >>>>
> >>>> --
> >>>> Daniel Kulp
> >>>> [email protected]
> >>>> http://dankulp.com/blog



-- 
Daniel Kulp
[email protected]
http://dankulp.com/blog

Reply via email to