Guillaume,
I'm not sure if this mail was meant for me. It seems like you started a new
thread (which was wise).
Anyway, no I think this is really strange. Like Richard pointed out, it
seems like it's a JRE problem. Looking at the stacktrace it seems to involve
calls from Jetty. I had been assuming that different versions of Jetty, by
accident, is more or less prone to be exposed to this bug. If then pax-web
uses different versions of Jetty then that could cause one version of
pax-web to work and the other one to fail.
Note that just because pax-web 0.7.2 seems to work for me, it doesn't mean
that the same problem can't happen with 0.7.2. It might just not be as
likely given my configuration.
Why Equinox doesn't show this problem is a mystery to me. But if everything
is about unlucky timing then I guess changing from Felix to Equinox probably
changes the timing and maybe, by luck, the bug won't appear.
Looking at the Karaf features file that comes from pax-web, the following
features are listed in version 0.7.3:
<feature name='jetty' version='6.1.19'>
<bundle>mvn:org.mortbay.jetty/jetty-util/6.1.19</bundle>
<bundle>mvn:org.mortbay.jetty/jetty/6.1.19</bundle>
</feature>
<feature name='jetty' version='6.1.22'>
<bundle>mvn:org.mortbay.jetty/jetty-util/6.1.22</bundle>
<bundle>mvn:org.mortbay.jetty/jetty/6.1.22</bundle>
</feature>
In version 0.7.2 only the 6.1.19 version is listed.
However, looking at Karaf's own feature file that comes bundled with Karaf
2.1.0, the http feature looks like this:
<feature name="http" version="2.1.0">
<config name="org.ops4j.pax.web">
org.osgi.service.http.port=8181
</config>
<bundle>mvn:org.apache.geronimo.specs/geronimo-servlet_2.5_spec/1.1.2</bundle>
<bundle>mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.jetty-bundle/6.1.22_2</bundle>
<bundle>mvn:org.ops4j.pax.web/pax-web-api/0.7.3</bundle>
<bundle>mvn:org.ops4j.pax.web/pax-web-spi/0.7.3</bundle>
<bundle>mvn:org.ops4j.pax.web/pax-web-runtime/0.7.3</bundle>
<bundle>mvn:org.ops4j.pax.web/pax-web-jetty/0.7.3</bundle>
</feature>
So, it seems like the ServiceMix OSGi wrapper of Jetty 6.1.22 is being used
regardless of what version of pax-web I use. Can't say this makes it any
clearer - but it's interesting...
Do you know why the ServiceMix wrapper is necessary. What about the one
provided by Jetty (via pax-web feature file)? Is it not fit for OSGi?
/Bengt
2010/11/12 Guillaume Nodet <[email protected]>
> If the pax-web 0.7.3 doesn't work and pax-web 0.7.2 seems to not have
> that problem, have you tried to see what in pax-web could actually
> cause the issue ?
>
> 2010/11/12 Łukasz Dywicki <[email protected]>:
> > +1 too :)
> >
> > -----Original Message-----
> > From: James Strachan [mailto:[email protected]]
> > Sent: Thursday, November 11, 2010 4:08 PM
> > To: [email protected]
> > Subject: Re: [VOTE] Release Karaf version 2.1.1
> >
> > +1
> >
> > On 10 November 2010 23:35, Jamie G. <[email protected]> wrote:
> >> Hi,
> >>
> >> We resolved 16 issues in this release (may take some time for cwiki to
> >> update with this page):
> >> https://cwiki.apache.org/confluence/display/KARAF/Karaf+2.1.1+Release
> >>
> >> Staging repository:
> >> https://repository.apache.org/content/repositories/orgapachekaraf-057/
> >>
> >> Release tags:
> >> http://svn.apache.org/repos/asf/karaf/tags/karaf-2.1.1/
> >>
> >> Please vote to approve this release:
> >>
> >> [ ] +1 Approve the release
> >> [ ] -1 Veto the release (please provide specific comments)
> >>
> >> This vote will be open for 72 hours.
> >>
> >
> >
> >
> > --
> > James
> > -------
> > FuseSource
> > Email: [email protected]
> > Web: http://fusesource.com
> > Twitter: jstrachan
> > Blog: http://macstrac.blogspot.com/
> >
> > Open Source Integration
> >
> >
>
>
>
> --
> Cheers,
> Guillaume Nodet
> ------------------------
> Blog: http://gnodet.blogspot.com/
> ------------------------
> Open Source SOA
> http://fusesource.com
>
