The last http.jetty we used would have been whatever is in SVN trunk.
We generally update to trunk, build from source and grab our framework
and bundles that way rather than from pre-built snapshots.
The transition to http wasn't for any specific functional reason, just
really to keep up with the more current/maintained bundle - the older
http.jetty bundle was still working fine for us.
- Rob
On 09/06/2010 12:08 PM, Jackson, Bruce wrote:
Which version of "http.jetty" were you using Rob?
On 09/06/2010 11:03, "Rob Walker"<[email protected]> wrote:
Bruce
I can see that - we've only recently moved across from the old
"http.jetty" to the "http" bundle ourselves for our main application,
but we generally run in an official JVM, so hadn't hit any issues with
NIO availability or stability
- R
On 09/06/2010 11:59 AM, Jackson, Bruce wrote:
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(Servlet
Ha
ndler.java:92)
at
org.apache.felix.http.base.internal.handler.ServletHandler.handle(ServletHa
nd
ler.java:78)
at
org.apache.felix.http.base.internal.dispatch.ServletPipeline.handle(Servlet
Pi
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(HttpF
il
terChain.java:33)
at
org.apache.felix.http.base.internal.dispatch.FilterPipeline.dispatch(Filter
Pi
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(DispatcherSer
vl
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(HttpConnecti
on
.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:58
2)
Am I doing something wrong, or is this config parameter just being ignored?
Thanks
Bruce
--
Ascert - Taking systems to the Edge
[email protected]
+44 (0)20 7488 3470
www.ascert.com
