Details

    • Type: Dependency upgrade Dependency upgrade
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 2.2.4
    • Fix Version/s: 2.2.5
    • Component/s: karaf-webcontainer
    • Labels:
      None

      Description

      In order to fully upgrade to Jetty 7.5.4.v20101024 (which fix high CPU usage), we have to upgrade to Pax Web 1.0.8.

        Issue Links

          Activity

          Hide
          Jean-Baptiste Onofré added a comment -

          Upgraded in karaf-2.2.x: revision 1211020.

          Show
          Jean-Baptiste Onofré added a comment - Upgraded in karaf-2.2.x: revision 1211020.
          Hide
          Jean-Baptiste Onofré added a comment -

          I released Pax Web 1.0.8:

          http://team.ops4j.org/wiki/display/paxweb/Pax+Web+-+1.0.8

          I'm upgrading in karaf-2.2.x.

          Show
          Jean-Baptiste Onofré added a comment - I released Pax Web 1.0.8: http://team.ops4j.org/wiki/display/paxweb/Pax+Web+-+1.0.8 I'm upgrading in karaf-2.2.x.
          Hide
          Jean-Baptiste Onofré added a comment -

          I'm gonna test now and release Pax Web 1.0.8 tonight, to be included in Karaf 2.2.5.

          Show
          Jean-Baptiste Onofré added a comment - I'm gonna test now and release Pax Web 1.0.8 tonight, to be included in Karaf 2.2.5.
          Hide
          Freeman Fang added a comment -

          Hi Achim,

          Just FYI
          pax-web 1.0.7 use jetty 7.4.x, if we upgrade karaf container to jetty 7.5.x, there's some api change between jetty 7.4.x and jetty 7.5.x which could cause pax-web 1.0.7 doesn't work in karaf. I've run into this issue before, so we have to upgrade to pax-web 1.0.8 in this case

          Regards
          Freeman

          Show
          Freeman Fang added a comment - Hi Achim, Just FYI pax-web 1.0.7 use jetty 7.4.x, if we upgrade karaf container to jetty 7.5.x, there's some api change between jetty 7.4.x and jetty 7.5.x which could cause pax-web 1.0.7 doesn't work in karaf. I've run into this issue before, so we have to upgrade to pax-web 1.0.8 in this case Regards Freeman
          Hide
          Jean-Baptiste Onofré added a comment -

          Yes, but as discussed on IRC, Pax Web 1.0.8 will include others bug fixes, so it makes sense to upgrade to this version in Karaf 2.2.5.

          Show
          Jean-Baptiste Onofré added a comment - Yes, but as discussed on IRC, Pax Web 1.0.8 will include others bug fixes, so it makes sense to upgrade to this version in Karaf 2.2.5.
          Hide
          Achim Nierbeck added a comment -

          actually for upgrading jetty you don't need a newer version of pax-web.
          We only had once an issue that needed an upgrade of pax-web because of an incompatible change within jetty.
          Besides that upgrading jetty without Pax web and staying within the same major Version should work

          Show
          Achim Nierbeck added a comment - actually for upgrading jetty you don't need a newer version of pax-web. We only had once an issue that needed an upgrade of pax-web because of an incompatible change within jetty. Besides that upgrading jetty without Pax web and staying within the same major Version should work
          Hide
          Jean-Baptiste Onofré added a comment -

          Waiting for the Pax Web 1.0.8 release, I upgraded to 1.0.8-SNAPSHOT

          Show
          Jean-Baptiste Onofré added a comment - Waiting for the Pax Web 1.0.8 release, I upgraded to 1.0.8-SNAPSHOT
          Hide
          Freeman Fang added a comment -

          Hi JB,

          Just noticed you change this issue summary.
          FYI I already upgrade jetty to 7.5.4.v20111024, tracked by KARAF-998[1].
          You just need upgrade paw-web version when the snapshot get deployed.

          [1]https://issues.apache.org/jira/browse/KARAF-998

          Regards
          Freeman

          Show
          Freeman Fang added a comment - Hi JB, Just noticed you change this issue summary. FYI I already upgrade jetty to 7.5.4.v20111024, tracked by KARAF-998 [1] . You just need upgrade paw-web version when the snapshot get deployed. [1] https://issues.apache.org/jira/browse/KARAF-998 Regards Freeman
          Hide
          Jean-Baptiste Onofré added a comment -

          I fixed PAXWEB-320 and deployed a Pax Web 1.0.8-SNAPSHOT on the sonatype repos.

          I'm updating Karaf to use this Pax Web version.

          Show
          Jean-Baptiste Onofré added a comment - I fixed PAXWEB-320 and deployed a Pax Web 1.0.8-SNAPSHOT on the sonatype repos. I'm updating Karaf to use this Pax Web version.
          Hide
          Jean-Baptiste Onofré added a comment -

          This issue is blocked by:

          http://team.ops4j.org/browse/PAXWEB-320

          Show
          Jean-Baptiste Onofré added a comment - This issue is blocked by: http://team.ops4j.org/browse/PAXWEB-320

            People

            • Assignee:
              Jean-Baptiste Onofré
              Reporter:
              Jean-Baptiste Onofré
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development