felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "J.W. Janssen (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FELIX-4282) HTTP Bundle 2.2.1 has and incorrect embedded Jetty instance
Date Sat, 09 Nov 2013 16:38:17 GMT

    [ https://issues.apache.org/jira/browse/FELIX-4282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13818189#comment-13818189
] 

J.W. Janssen commented on FELIX-4282:
-------------------------------------

Performing a comparison using MD5 hashes on the differences between Jetty 7.6.12 & 7.6.13
reveals that the classes {{CookieCutter}} and {{QuotedStringTokenizer}} are *exactly* the
same in both releases (only 17 of the 564 classes are different between these two releases).
So, merely from a byte-code perspective this can not be the solution for the original problem.
Why an upgrade to Jetty 7.6.13 appears to solve your issue is beyond me. 
I therefore do not directly share your opinion that upgrading Jetty to 7.6.13 should be done
for "more robustness". Instead, I'd try to find out why it fails in your particular situation.
In addition, I would opt for upgrading directly to Jetty 9.x (as is already done in SVN) as
to benefit from the latest features provided by it, and to allow working on [RFC-189|https://github.com/osgi/design/raw/master/rfcs/rfc0189/rfc-0189-Http_Service_Updates.pdf].
The only downside of this would be that Jetty 9 requires Java 7 (but I do not think that is
that of a major issue for most people).



> HTTP Bundle 2.2.1 has and incorrect embedded Jetty instance
> -----------------------------------------------------------
>
>                 Key: FELIX-4282
>                 URL: https://issues.apache.org/jira/browse/FELIX-4282
>             Project: Felix
>          Issue Type: Bug
>          Components: HTTP Service
>            Reporter: Bruce Jackson
>
> I've recently downloaded the latest version of the http bundle 2.2.1 which
> contains the update to Jetty 7. This seems to have a problem, perhaps
> because the Jetty version is a snapshot.
> java.lang.NoSuchMethodError:
> org.eclipse.jetty.util.QuotedStringTokenizer.unquoteOnly(Ljava/lang/String;
> )Ljava/lang/String;
> 	at
> org.eclipse.jetty.server.CookieCutter.parseFields(CookieCutter.java:284)
> 	at org.eclipse.jetty.server.CookieCutter.getCookies(CookieCutter.java:64)
> 	at org.eclipse.jetty.server.Request.getCookies(Request.java:499)
> 	at
> org.eclipse.jetty.server.session.SessionHandler.checkRequestedSessionId(Ses
> sionHandler.java:260)
> 	at
> org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java
> :155)
> 	at
> org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java
> :978)
> 	at
> org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:13
> 5)
> 	at
> org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHan
> dlerCollection.java:255)
> 	at
> org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:
> 116)
> 	at org.eclipse.jetty.server.Server.handle(Server.java:369)
> 	at
> org.eclipse.jetty.server.AbstractHttpConnection.handleRequest(AbstractHttpC
> onnection.java:486)
> 	at
> org.eclipse.jetty.server.AbstractHttpConnection.headerComplete(AbstractHttp
> Connection.java:933)
> 	at
> org.eclipse.jetty.server.AbstractHttpConnection$RequestHandler.headerComple
> te(AbstractHttpConnection.java:995)
> 	at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:630)
> 	at org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:230)
> 	at
> org.eclipse.jetty.server.AsyncHttpConnection.handle(AsyncHttpConnection.jav
> a:82)
> 	at
> org.eclipse.jetty.io.nio.SelectChannelEndPoint.handle(SelectChannelEndPoint
> .java:606)
> 	at
> org.eclipse.jetty.io.nio.SelectChannelEndPoint$1.run(SelectChannelEndPoint.
> java:46)
> 	at
> org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java
> :603)
> 	at
> org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:
> 538)
> 	at java.lang.Thread.run(Thread.java:724)
> If I build the bundle manually with the 7.4.16 Jetty-all, I don't see this
> problem.
> I'm using the released HTTP Bundle from the felix download site. If I
> manually remove the classes from the exploded jar and replace them with
> the contents of the latest release Jetty all build (which is
> jetty-all-server-7.6.13.v20130916) then I no longer see this problem.
> I suspect that the reason that we see this is that we are using Jetty 7
> continuations (looking at the stack trace, this seems to be an async
> operation) and so if you're not using them, you may never have encountered
> this problem.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Mime
View raw message