[ 
https://issues.apache.org/jira/browse/HTTPCORE-243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Eric Hubert closed HTTPCORE-243.
--------------------------------


Verified change on trunk which now throws IllegalStateException at several 
places where a set connection is mandatory.

For the record: Oleg's analysis has been correct. Once Synapse does not remove 
the connection attribute from the context while releasing persistent 
connections the problem does not occur. Synapse trunk already correctly handles 
this situation.

> NPE in DefaultClientIOEventDispatch#inputReady
> ----------------------------------------------
>
>                 Key: HTTPCORE-243
>                 URL: https://issues.apache.org/jira/browse/HTTPCORE-243
>             Project: HttpComponents HttpCore
>          Issue Type: Bug
>          Components: HttpCore NIO
>    Affects Versions: 4.1
>         Environment: Linux 2.6.18-6-amd64,  Java 6 Update 21, 32bit
>            Reporter: Eric Hubert
>             Fix For: 4.1.1
>
>         Attachments: synapse_session_wire.log
>
>
> While using Synapse 1.2 with httpcore-nio 4.1 the following exceptions occurs
> WARN  2010-11-27 23:55:07,737 [http-Sender I/O dispatcher-1][][] 
> org.apache.synapse.transport.nhttp.HttpCoreNIOSender 'System may be unstable: 
> IOReactor encountered a runtime exception : null'
> java.lang.NullPointerException
>         at 
> org.apache.http.impl.nio.DefaultClientIOEventDispatch.inputReady(DefaultClientIOEventDispatch.java:148)
>         at 
> org.apache.http.impl.nio.reactor.BaseIOReactor.readable(BaseIOReactor.java:161)
>         at 
> org.apache.http.impl.nio.reactor.AbstractIOReactor.processEvent(AbstractIOReactor.java:335)
>         at 
> org.apache.http.impl.nio.reactor.AbstractIOReactor.processEvents(AbstractIOReactor.java:315)
>         at 
> org.apache.http.impl.nio.reactor.AbstractIOReactor.execute(AbstractIOReactor.java:275)
>         at 
> org.apache.http.impl.nio.reactor.BaseIOReactor.execute(BaseIOReactor.java:104)
>         at 
> org.apache.http.impl.nio.reactor.AbstractMultiworkerIOReactor$Worker.run(AbstractMultiworkerIOReactor.java:542)
>         at java.lang.Thread.run(Thread.java:619)
> FATAL 2010-11-27 23:55:08,678 [HttpCoreNIOSender][][] 
> org.apache.synapse.transport.nhttp.HttpCoreNIOSender 'Encountered an I/O 
> error: I/O dispatch worker terminated abnormally'
> org.apache.http.nio.reactor.IOReactorException: I/O dispatch worker 
> terminated abnormally
>         at 
> org.apache.http.impl.nio.reactor.AbstractMultiworkerIOReactor.execute(AbstractMultiworkerIOReactor.java:324)
>         at 
> org.apache.synapse.transport.nhttp.HttpCoreNIOSender.executeClientEngine(HttpCoreNIOSender.java:188)
>         at 
> org.apache.synapse.transport.nhttp.HttpCoreNIOSender.access$000(HttpCoreNIOSender.java:77)
>         at 
> org.apache.synapse.transport.nhttp.HttpCoreNIOSender$3.run(HttpCoreNIOSender.java:209)
>         at java.lang.Thread.run(Thread.java:619)
> Caused by: java.lang.NullPointerException
>         at 
> org.apache.http.impl.nio.DefaultClientIOEventDispatch.inputReady(DefaultClientIOEventDispatch.java:148)
>         at 
> org.apache.http.impl.nio.reactor.BaseIOReactor.readable(BaseIOReactor.java:161)
>         at 
> org.apache.http.impl.nio.reactor.AbstractIOReactor.processEvent(AbstractIOReactor.java:335)
>         at 
> org.apache.http.impl.nio.reactor.AbstractIOReactor.processEvents(AbstractIOReactor.java:315)
>         at 
> org.apache.http.impl.nio.reactor.AbstractIOReactor.execute(AbstractIOReactor.java:275)
>         at 
> org.apache.http.impl.nio.reactor.BaseIOReactor.execute(BaseIOReactor.java:104)
>         at 
> org.apache.http.impl.nio.reactor.AbstractMultiworkerIOReactor$Worker.run(AbstractMultiworkerIOReactor.java:542)
>         ... 1 more
> I will give my best to provide a wire log later on.

-- 
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]

Reply via email to