[
https://issues.apache.org/jira/browse/AXIS2-3514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12677645#action_12677645
]
Asankha C. Perera commented on AXIS2-3514:
------------------------------------------
Michele
For 1
I would actually not recommend the NIO transport for vanilla Axis2. It was
built for a specific purpose - to enable Synapse to function as a high
performance ESB, and not wait on IO from backend services. This allows Synapse
to scale to supports thousands of concurrent users per JVM. But even Synapse
processes each request with a worker thread. Thus the actual concurrency you
could achieve is still limited to the number of threads/workload the JVM can
handle. For plain vanilla Axis2, you do not gain anything with NIO - since you
are anyway limited by the one-thread-per-request limitation. In this case, I
can point you to information which shows that traditional blocking IO performs
better.
For 2
Yes, this as well as quite a few others since the release of Synapse 1.2. So
get the latest from the trunk, until we release Synapse 1.3
Asankha
> HttpCoreNIOSender throws NullPointerException
> ---------------------------------------------
>
> Key: AXIS2-3514
> URL: https://issues.apache.org/jira/browse/AXIS2-3514
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: transports
> Affects Versions: 1.3
> Environment: java 1.5, linux, axis2 1.3
> Reporter: Michele Mazzucco
> Assignee: Asankha C. Perera
> Priority: Critical
>
> After a couple of minutes of use the system failed with the following error
> ERROR 10:04:09,557 (ClientHandler.java:348) - Received an internal server
> error : Internal Server Error
> ERROR 10:04:09,557 (ClientHandler.java:348) - Received an internal server
> error : Internal Server Error
> ERROR 10:04:09,557 (ClientHandler.java:348) - Received an internal server
> error : Internal Server Error
> Exception in thread "HttpCoreNIOSender" java.lang.NullPointerException
> at
> org.apache.axis2.transport.nhttp.ClientHandler.inputReady(ClientHandler.java:236)
> at
> org.apache.axis2.transport.nhttp.LoggingNHttpClientHandler.inputReady(LoggingNHttpClientHandler.java:113)
> at
> org.apache.http.impl.nio.DefaultNHttpClientConnection.consumeInput(DefaultNHttpClientConnection.java:111)
> at
> org.apache.axis2.transport.nhttp.PlainClientIOEventDispatch.inputReady(PlainClientIOEventDispatch.java:71)
> at
> org.apache.http.impl.nio.reactor.BaseIOReactor.readable(BaseIOReactor.java:68)
> at
> org.apache.http.impl.nio.reactor.AbstractIOReactor.processEvent(AbstractIOReactor.java:160)
> at
> org.apache.http.impl.nio.reactor.AbstractIOReactor.processEvents(AbstractIOReactor.java:145)
> at
> org.apache.http.impl.nio.reactor.AbstractIOReactor.execute(AbstractIOReactor.java:127)
> at
> org.apache.http.impl.nio.reactor.AbstractMultiworkerIOReactor$Worker.run(AbstractMultiworkerIOReactor.java:162)
> at java.lang.Thread.run(Thread.java:595)
> line 236 is
> sink.write(inbuf);
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
