Yes, all these bugs explain my issues but I use jetty-distribution-7.4.2.v20110526.
So the issue is not fiexed, at least in version 7.4.2.v20110526. I can't find a newer 7.x version. Thanks. Guillaume. On Fri, Jun 24, 2011 at 5:02 PM, Thomas Becker <[email protected]> wrote: > Hi Guillaume, > > have a look at these issues: > > https://bugs.eclipse.org/bugs/**show_bug.cgi?id=347429<https://bugs.eclipse.org/bugs/show_bug.cgi?id=347429> > https://bugs.eclipse.org/bugs/**show_bug.cgi?id=348652<https://bugs.eclipse.org/bugs/show_bug.cgi?id=348652> > https://bugs.eclipse.org/bugs/**show_bug.cgi?id=347717<https://bugs.eclipse.org/bugs/show_bug.cgi?id=347717> > > One of these will explain your issue and both are fixed in 7.4.2. > > Cheers, > Thomas > > > > On 24/06/2011 16:48, Jesse McConnell wrote: > >> do you have --exec in your start.ini file? >> >> jesse >> >> -- >> jesse mcconnell >> [email protected] >> >> >> >> On Fri, Jun 24, 2011 at 09:45, Guillaume<[email protected]> wrote: >> >>> Hi, >>> I want to start jetty (7.x) on a solaris server, for that I use the >>> jetty.sh >>> startup script (jetty.sh). I made some small modifications on this script >>> to >>> make it works (maily replace += command). >>> Jetty is running, but the script starts 2 process (start.jar >>> and XmlConfiguration) . Example : >>> 20734 XmlConfiguration -XX:+UseParNewGC -XX:+UseConcMarkSweepGC >>> -XX:ParallelGCThreads=10 -XX:ParallelCMSThreads=4 -Xmx1024M -Xms1024M >>> -XX:SurvivorRatio=4 -XX:TargetSurvivorRatio=80 -XX:MaxTenuringThreshold=5 >>> -XX:+CMSClassUnloadingEnabled -XX:+**AlwaysActAsServerClassMachine >>> -XX:+UseLargePages -XX:LargePageSizeInBytes=256m -XX:+EliminateLocks >>> -XX:+UseBiasedLocking -XX:+DoEscapeAnalysis -XX:+UseNiagaraInstrs >>> -XX:+AdjustConcurrency -XX:+AlwaysPreTouch -XX:+UseNUMA -XX:+UseMembar >>> -XX:+UseCompressedOops -XX:+UseFastAccessorMethods >>> -XX:PerfDataSamplingInterval=**100 -XX:+PrintTenuringDistribution >>> -XX:PrintCMSStatistics=2 -XX:+PrintCommandLineFlags >>> -XX:InitialCodeCacheSize=32M -XX:ReservedCodeCacheSize=32M >>> -XX:+ParallelRefProcEnabled -XX:+CMSConcurrentMTEnabled >>> -XX:+CMSScavengeBeforeRemark -XX:+CMSParallelRemarkEnabled >>> -XX:+**CMSParallelSurvivorRemarkEnabl**ed -XX:CMSMarkStackSize=8M >>> -XX:CMSMarkStackSizeMax=8M -XX:**CMSInitiatingPermOccupancyFrac**tion=85 >>> -XX:**CMSInitiatingOccupancyFraction**=60 -XX:+** >>> UseCMSInitiatingOccupancyOnly >>> -XX:CMSTriggerRatio=65 >>> 20725 start.jar -Djetty.home=/opt/jettyuser/**jetty >>> -Djava.io.tmpdir=/tmp/**jettyuser >>> I don't know if it is normal but the stop command kills only the >>> process 20725, not the other one. >>> Does anyone already seen this kind of behavior ? >>> Thanks. >>> Guillaume. >>> ______________________________**_________________ >>> jetty-users mailing list >>> [email protected] >>> https://dev.eclipse.org/**mailman/listinfo/jetty-users<https://dev.eclipse.org/mailman/listinfo/jetty-users> >>> >>> >>> ______________________________**_________________ >> jetty-users mailing list >> [email protected] >> https://dev.eclipse.org/**mailman/listinfo/jetty-users<https://dev.eclipse.org/mailman/listinfo/jetty-users> >> > ______________________________**_________________ > jetty-users mailing list > [email protected] > https://dev.eclipse.org/**mailman/listinfo/jetty-users<https://dev.eclipse.org/mailman/listinfo/jetty-users> > >
_______________________________________________ jetty-users mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/jetty-users
