Synapse sample 0 on Windows throws : java.io.IOException: An existing
connection was forcibly closed by the remote host
------------------------------------------------------------------------------------------------------------------------
Key: SYNAPSE-136
URL: https://issues.apache.org/jira/browse/SYNAPSE-136
Project: Synapse
Issue Type: Bug
Components: Core
Environment: Windows Vista Business
Reporter: Eric
Priority: Minor
I checked out the latest Synapse sources from the SVN trunk of 8th Oct '07.
When running synapse sample 0 : with configuration :
<definitions xmlns="http://ws.apache.org/ns/synapse ">
<!-- log all attributes of messages passing through -->
<log level="full"/>
<send/>
</definitions>
Although the sample client got back the response, I got the following at the
server logs :
Sending To: http://www.w3.org/2005/08/addressing/anonymous
SOAPAction: null
2007-10-08 12:20:05,354 [xxxxx] [HttpClientWorker-1] DEBUG SendMediator End :
Send mediator
2007-10-08 12:20:05,355 [xxxxx] [HttpClientWorker-1] DEBUG SequenceMediator End
: Sequence <main>
2007-10-08 12:20:05,686 [xxxxx] [I/O dispatcher 6] ERROR ServerHandler HTTP
connection [/127.0.0.1:
59777]: An existing connection was forcibly closed by the remote host
java.io.IOException: An existing connection was forcibly closed by the remote
host
at sun.nio.ch.SocketDispatcher.read0(Native Method)
at sun.nio.ch.SocketDispatcher.read(SocketDispatcher.java:25)
at sun.nio.ch.IOUtil.readIntoNativeBuffer(IOUtil.java:233)
at sun.nio.ch.IOUtil.read(IOUtil.java:206)
at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:207)
at
org.apache.axis2.transport.nhttp.LoggingIOSession$LoggingByteChannel.read
(LoggingIOSession.java:184)
at
org.apache.http.impl.nio.reactor.SessionInputBufferImpl.fill(SessionInputBufferImpl.java:84)
at
org.apache.http.impl.nio.codecs.AbstractMessageParser.fillBuffer(AbstractMessageParser.java
:97)
at
org.apache.http.impl.nio.DefaultNHttpServerConnection.consumeInput(DefaultNHttpServerConnection.java:110)
at
org.apache.axis2.transport.nhttp.PlainServerIOEventDispatch.inputReady(PlainServerIOEventDispatch.java
:69)
at
org.apache.http.impl.nio.reactor.BaseIOReactor.readable(BaseIOReactor.java:94)
at
org.apache.http.impl.nio.reactor.AbstractIOReactor.processEvent(AbstractIOReactor.java:189)
at org.apache.http.impl.nio.reactor.AbstractIOReactor.processEvents
(AbstractIOReactor.java:174)
at
org.apache.http.impl.nio.reactor.AbstractIOReactor.execute(AbstractIOReactor.java:137)
at
org.apache.http.impl.nio.reactor.BaseIOReactor.execute(BaseIOReactor.java:69)
at
org.apache.http.impl.nio.reactor.AbstractMultiworkerIOReactor$Worker.run(AbstractMultiworkerIOReactor.java:28
1)
at java.lang.Thread.run(Thread.java:595)
Synopsis from the Asankha :
----------------------------------------
" Are you using windows? Also whats your client application written in?
Most probably what happens is that your client sends the request stating
HTTP 1.1 which implies the use of keepalives unless a "Connection:
close" header is specified along with the request. But as soon as it
gets the response back - the client closes the connection and possibly
terminates itself. One way to find out if this is the cause is to send
the request to Synpase through TCPMon etc and check if what I am saying
is taking place - note that the sample stockquote client etc that uses
Axis2 in our samples also suffers from this - but this is not a defect
with Synapse. We could update Synapse to just do a WARN on this.. your
thoughts are welcome "
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
