Whoops, sorry about previous reply-all, this thread shouldn't be here.
2009/6/30 Andrew Clegg :
> 2009/6/30 Naresh Tallapelli :
>
>> More information about this error may be available
>> in the server error log.
>
> Are you writing the server, the client or both? Have
2009/6/30 Naresh Tallapelli :
> More information about this error may be available
> in the server error log.
Are you writing the server, the client or both? Have you looked in the
server's error log (or asked the server admin to do so)?
There's no way to help without seeing the details of the e
re in order to reproduce it. Possibly
do-able with a debugger -- dig down to find the Socket object and call
setLinger() and close() on it -- hard to say if it's a realistic
reproduction though :-(
Andrew.
2009/6/25 Andrew Clegg :
> 2009/6/24 Daniel Kulp :
>
>> Any chance you could
2009/6/24 Daniel Kulp :
> Any chance you could try with Jetty? Maybe Jetty does something different.
Sure, I'll need to install a few things on the server first -- I'll
set it up today hopefully and let you know what happens.
Andrew.
--
:: http://biotext.org.uk/ ::
PS I should have mentioned:
JDK 1.6.0_06-b02, Tomcat/6.0.16, Centos 5.3, CXF 2.2.2
--
View this message in context:
http://www.nabble.com/HTTP-transportno-exception-on-server-side-when-client-has-reset-TCP-connection-tp24182294p24183358.html
Sent from the cxf-dev mailing list archive at Nab
I'm posting this here rather than on the users list as it's a bit technical,
and I suspect it might indicate a bug in either CXF or at a lower level.
However, I'm really not sure how to simulate it in a way that would make a
convenient JIRA entry. I'm happy to bundle up some example code, if some
ostnames for it, but rather URI's that
>>> represent the logical purpose of the operation.
>>>
>>> The soap:address is obviously used to connect to the service, hence it
>>> must be updated.
>>>
>>>
>>>
>>>> -Origi
t
> represent the logical purpose of the operation.
>
> The soap:address is obviously used to connect to the service, hence it
> must be updated.
>
>
>
>> -Original Message-
>> From: Andrew Clegg [mailto:[EMAIL PROTECTED]
>> Sent: Thursday, Novemb
Hey folks,
I have a WSDL-first project which contains several service definitions, each
with a separate binding to a separate port type.
When I go to the 'services' page for the WAR in Tomcat, I get a bunch of
links like:
http://myserver:8080/MyWar/services/ServiceOne?wsdl
http://myserver:8080
