Jetty
  1. Jetty
  2. JETTY-991

Starting Jetty in separate JVM

    Details

    • Type: New Feature New Feature
    • Status: Resolved Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 6.1.16
    • Fix Version/s: 7.6.6, 8.1.6
    • Component/s: Maven
    • Labels:
      None
    • Number of attachments :
      0

      Description

      Please support starting jetty (using jetty-maven-plugin) in separate JVM istance than one Maven build is running in. With jetty-maven-plugin running in separate JVM instance, stopping it should exit JVM instance Jetty was running in. This would enable maven code coverage plugins like maven cobertura plugin to get coverage data on time for maven report generation, as these data get stored on JVM exit event.

        Issue Links

          Activity

          Hide
          Edd grant added a comment -

          Tested this on 7.6.8-SNAPSHOT, can confirm that run-forked is now starting, waiting and stopping correctly - thanks for this. I have an issue where it hangs in a multi module project build however will raise this as a separate JIRA and will try to put together a sharable example.

          Show
          Edd grant added a comment - Tested this on 7.6.8-SNAPSHOT, can confirm that run-forked is now starting, waiting and stopping correctly - thanks for this. I have an issue where it hangs in a multi module project build however will raise this as a separate JIRA and will try to put together a sharable example.
          Hide
          Edd grant added a comment -

          r.e. my last comment about multi-module project builds hanging, ignore that it was an issue created within my particular project. My testing of this suggests that it is working perfectly now. Many thanks.

          Show
          Edd grant added a comment - r.e. my last comment about multi-module project builds hanging, ignore that it was an issue created within my particular project. My testing of this suggests that it is working perfectly now. Many thanks.
          Hide
          Eugen Paraschiv added a comment -

          One small improvement would be to log the jvmArgs when doing the fork. I had everything configured correctly, the new JVM was indeed getting the arguments I was passing - but had no idea that was the case by looking at the logs. I verified it via connecting the the new process with VisualVM and looking at the JVM arguments, but that's of course not optimal.
          Hope that makes sense.
          Thanks.

          Show
          Eugen Paraschiv added a comment - One small improvement would be to log the jvmArgs when doing the fork. I had everything configured correctly, the new JVM was indeed getting the arguments I was passing - but had no idea that was the case by looking at the logs. I verified it via connecting the the new process with VisualVM and looking at the JVM arguments, but that's of course not optimal. Hope that makes sense. Thanks.
          Hide
          Joakim Erdfelt added a comment -

          Eugen Paraschiv,

          This is not an active bug tracking system for Jetty.
          This jira system was for Jetty 6.x, back before the Jetty project joined the Eclipse Foundation.

          Jetty 6 was EOL (End of Life) back in 2010,
          No further work will be done on Jetty 6.

          If you have questions about Eclipse Jetty, use the bug tracker at Eclipse.
          http://bugs.eclipse.org/

          Also note, Jetty 7 and Jetty 8 are now also EOL (End of Life).
          Jetty 9 is the live, stable, mature, supported, and actively being developed version of Jetty.

          Show
          Joakim Erdfelt added a comment - Eugen Paraschiv, This is not an active bug tracking system for Jetty. This jira system was for Jetty 6.x, back before the Jetty project joined the Eclipse Foundation. Jetty 6 was EOL (End of Life) back in 2010, No further work will be done on Jetty 6. If you have questions about Eclipse Jetty, use the bug tracker at Eclipse. http://bugs.eclipse.org/ Also note, Jetty 7 and Jetty 8 are now also EOL (End of Life). Jetty 9 is the live, stable, mature, supported, and actively being developed version of Jetty.
          Hide
          Jan Bartel added a comment -

          Eugen,
          If you use one of the more recent jetty-9 versions, you can see the args to the fork by running maven with maven debug enabled (ie use mvn -X ....)
          Jan

          Show
          Jan Bartel added a comment - Eugen, If you use one of the more recent jetty-9 versions, you can see the args to the fork by running maven with maven debug enabled (ie use mvn -X ....) Jan

            People

            • Assignee:
              Jan Bartel
              Reporter:
              Stevo Slavic
            • Votes:
              13 Vote for this issue
              Watchers:
              18 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: