Hi Rob I'll do that. It is desirable, actually: NIO support in Android is flakey before 2.2 (see http://code.google.com/p/android/issues/detail?id=3531) so not being able to turn this off is a major problem.
Thanks Bruce On 09/06/2010 10:53, "Rob Walker" <[email protected]> wrote: > Bruce > > Just grepping the source code, and I think this property was in the > original felix/http.jetty bundle but may not have made it across to the > new felix/http bundle. > > Would guess it could be retrofitted if found desirable - so maybe raise > a JIRA if there isn't one already > > -- Rob > > On 09/06/2010 11:42 AM, Jackson, Bruce wrote: >> Hi All >> >> I'm using Felix 2.0.5 with org.apache.felix.http.bundle-2.0.4.jar in an >> embedded Android application. In the docs ( >> http://felix.apache.org/site/apache-felix-http-service.html), I see that NIO >> support is optional but enabled by default. I don't want it, so I've passed >> the parameter: >> >> config.put("org.apache.felix.http.nio", "false"); >> >> into my startup config map. However, this doesn't seem to have disabled NIO >> support at all: exceptions clearly show that NIO is still being used as shown >> below (notice the last line bar one in the stack trace): >> >> at javax.servlet.http.HttpServlet.service(HttpServlet.java:820) >> at >> org.apache.felix.http.base.internal.handler.ServletHandler.doHandle(ServletHa >> ndler.java:92) >> at >> org.apache.felix.http.base.internal.handler.ServletHandler.handle(ServletHand >> ler.java:78) >> at >> org.apache.felix.http.base.internal.dispatch.ServletPipeline.handle(ServletPi >> peline.java:42) >> at >> org.apache.felix.http.base.internal.dispatch.InvocationFilterChain.doFilter(I >> nvocationFilterChain.java:49) >> at >> org.apache.felix.http.base.internal.dispatch.HttpFilterChain.doFilter(HttpFil >> terChain.java:33) >> at >> org.apache.felix.http.base.internal.dispatch.FilterPipeline.dispatch(FilterPi >> peline.java:48) >> at >> org.apache.felix.http.base.internal.dispatch.Dispatcher.dispatch(Dispatcher.j >> ava:39) >> at >> org.apache.felix.http.base.internal.DispatcherServlet.service(DispatcherServl >> et.java:55) >> at javax.servlet.http.HttpServlet.service(HttpServlet.java:820) >> at >> org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:511) >> at >> org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:390) >> at >> org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182) >> at >> org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:765) >> at >> org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152) >> at org.mortbay.jetty.Server.handle(Server.java:326) >> at >> org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:536) >> at >> org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection >> .java:915) >> at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:539) >> at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:212) >> at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:405) >> at >> org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:409) >> at >> org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:582) >> >> Am I doing something wrong, or is this config parameter just being ignored? >> >> Thanks >> >> Bruce >> >>
