Thanks, that was in fact the issue, and setting those to true fixed it! The somewhen must be 7.3.0, because 7.2.2 will crash with said <set>s
Thanks again for your help, spent way too much time looking in the wrong place. Thank you, Daniel Winsor Associate, IT Architecture On 4/17/13 2:44 PM, "Thomas Becker" <[email protected]> wrote: >Hi Daniel, > >that output is triggered by the following server options: > > <Set name="dumpAfterStart">false</Set> > <Set name="dumpBeforeStop">false</Set> > >If they're false you won't get a dump on start/stop. Guess the default >might have changed somewhen. Check jetty.xml for these settings and >change them to your needs. > >Cheers, >Thomas > >Am 4/17/13 11:29 PM, schrieb Winsor, Daniel: >> Hi, >> >> Maybe the issue is not even logging related. Can you answer if this >> logging output represents an error? >> >> org.mortbay.jetty.plugin.JettyServer@2b6dd9c5 STOPPED >> [email protected]:8080 >> [email protected]:8443 >> +-qtp2066981544{8<=5<=8/254,0} >> +-HandlerCollection@413afcd0 started >> +-ContextHandlerCollection@7abdd25 started >> | >> >>+-JettyWebAppContext@6c99ea5d@6c99ea5d/nonexistent,[file:/Users/dwinsor/n >>eo >> Jetty >> >> Basically, I'm not sure why it would say JettyServer STOPPED, even >>though >> the webapp is running just fine and later prints out [INFO] Started >>Jetty >> Server. >> >> >> Thank you, >> Daniel Winsor >> Associate, IT Architecture >> >> >> >> >> On 4/17/13 2:10 PM, "Winsor, Daniel" <[email protected]> wrote: >> >>> Thanks, >>> >>> That has already been linked, but I am not using jetty 9. I am using >>> jetty 7, and I have been through the documentation already. >>> >>> Thank you, >>> Daniel Winsor >>> Associate, IT Architecture >>> >>> From: Joakim Erdfelt <[email protected]<mailto:[email protected]>> >>> Reply-To: JETTY user mailing list >>> <[email protected]<mailto:[email protected]>> >>> Date: Wed, 17 Apr 2013 14:05:05 -0700 >>> To: JETTY user mailing list >>> <[email protected]<mailto:[email protected]>> >>> Subject: Re: [jetty-users] Upgrading to Jetty 8 turns off debug output >>> >>> The logging documentation for Jetty 9 is at >>> >>>http://www.eclipse.org/jetty/documentation/current/configuring-logging.h >>>tm >>> l >>> >>> >>> >>> -- >>> Joakim Erdfelt <[email protected]<mailto:[email protected]>> >>> webtide.com<http://www.webtide.com/> >>> Developer advice, services and support >>>from the Jetty & CometD experts >>> eclipse.org/jetty<http://eclipse.org/jetty/> - >>> cometd.org<http://cometd.org/> >>> >>> >>> On Wed, Apr 17, 2013 at 1:48 PM, Winsor, Daniel >>> <[email protected]<mailto:[email protected]>> wrote: >>> Thank you, upgrading to jetty 9 may be a further step, but I have heard >>> it requires more configuration changes than just 7 -> 8. >>> The jetty 9 logging documentation looks a whole lot like the jetty 7 / >>>8 >>> docs, and jetty 8 logging is, as implied by >>> http://wiki.eclipse.org/Jetty/Feature/Jetty_Logging much more like >>>jetty >>> 7 than jetty 9. >>> However, the issue is really that jetty 7.2.2 works, 7.3.0 and above >>> fail. So I'd prefer to focus on jetty 7 or 8 right now, and perhaps 8 >>> shouldn't even be considered. >>> Jetty logging worked before without a jetty-logging.properties, but now >>> still fails to show said output when I add this: >>> >>> org.eclipse.jetty.util.log.class=org.eclipse.jetty.util.log.StdErrLog >>> >>> org.eclipse.jetty.LEVEL=DEBUG >>> >>> Thank you, >>> Daniel Winsor >>> Associate, IT Architecture >>> >>> From: Jesse McConnell >>> >>><[email protected]<mailto:[email protected]><mailto:jess >>>e. >>> [email protected]<mailto:[email protected]>>> >>> Reply-To: JETTY user mailing list >>> >>><[email protected]<mailto:[email protected]><mailto:jetty-us >>>er >>> [email protected]<mailto:[email protected]>>> >>> Date: Wed, 17 Apr 2013 15:30:44 -0500 >>> To: JETTY user mailing list >>> >>><[email protected]<mailto:[email protected]><mailto:jetty-us >>>er >>> [email protected]<mailto:[email protected]>>> >>> Subject: Re: [jetty-users] Upgrading to Jetty 8 turns off debug output >>> >>> Alternately just use the jetty 9 plugin >>> org.eclipse.jetty:jetty-maven-plugin:9.0.2.v20130417 >>> >>> cheers, >>> jesse >>> >>> -- >>> jesse mcconnell >>> >>>[email protected]<mailto:[email protected]><mailto:jesse >>>.m >>> [email protected]<mailto:[email protected]>> >>> >>> >>> On Wed, Apr 17, 2013 at 3:29 PM, Jesse McConnell >>> >>><[email protected]<mailto:[email protected]><mailto:jess >>>e. >>> [email protected]<mailto:[email protected]>>> wrote: >>> the logging in the latest jetty 8 releases is much like in 9 so I'll >>>link >>> that documentation >>> >>> >>>http://www.eclipse.org/jetty/documentation/current/configuring-logging.h >>>tm >>> l >>> >>> cheers, >>> jesse >>> >>> -- >>> jesse mcconnell >>> >>>[email protected]<mailto:[email protected]><mailto:jesse >>>.m >>> [email protected]<mailto:[email protected]>> >>> >>> >>> On Wed, Apr 17, 2013 at 2:41 PM, Winsor, Daniel >>> >>><[email protected]<mailto:[email protected]><mailto:daniel >>>.w >>> [email protected]<mailto:[email protected]>>> wrote: >>> Hi, >>> >>> I am currently on jetty 7.2.0.RC0, run through the jetty-maven-plugin. >>> I'd like to upgrade to jetty 8.latest to be able to use servlet 3.0. >>> However, what I'm noticing is that with 7.2.0.RC0 I get some nice >>> debugging shown on my terminal, and with other versions, even other 7.x >>> versions, I'm not getting it. >>> The kind of debug output I see with 7.2.0.RC0 is like so: >>> >>>org.mortbay.jetty.plugin.JettyServer@271bc503<mailto:org.mortbay.jetty.p >>>lu >>> >>>gin.JettyServer@271bc503<mailto:org.mortbay.jetty.plugin.JettyServer@271 >>>bc >>> >>>503><mailto:org.mortbay.jetty.plugin.JettyServer@271bc503<mailto:org.mor >>>tb >>> ay.jetty.plugin.JettyServer@271bc503>>> STOPPED >>> >>> >>>[email protected]<mailto:[email protected]>< >>>ma >>> >>>ilto:[email protected]<mailto:[email protected]. >>>0> >>>> >>>><mailto:[email protected]<mailto:SelectChannelConnector@0 >>>>.0 >>>> >>>>.0.0><mailto:[email protected]<mailto:SelectChannelConnect >>>>or >>>> @0.0.0.0>>>:8080 >>> >>> >>>[email protected]<mailto:[email protected]><mailto:S >>>sl >>> >>>[email protected]<mailto:[email protected]>><mailto:-SslS >>>oc >>> >>>[email protected]<mailto:[email protected]><mailto:SslSocket >>>Co >>> [email protected]<mailto:[email protected]>>>:8443 >>> +-qtp62871287{8<=5<=8/254,0} >>> +-HandlerCollection@c237b89<mailto:-HandlerCollection@c237b89> started >>> >>> >>>+-ContextHandlerCollection@6d836598<mailto:-ContextHandlerCollection@6d8 >>>36 >>> 598> started >>> | >>> >>>+-JettyWebAppContext@17043b2f<mailto:-JettyWebAppContext@17043b2f>@17043 >>>b2 >>> f/widgets,[file:/Users/dwinsor/previ >>> Š a whole bunch more >>> >>> It tells me everything about what's on the classpath for certain >>> contexts, etc etc, so it's really helpful and I'd like to keep it >>>around. >>> Strangely, these are the versions for which I get this kind of output >>> 8.1.10 no >>> 7.3.0.v20110203 no >>> 7.2.2 yes >>> 7.2.0.RC0 yes >>> 7.0.2.RC0 yes >>> 7.0.0.RC2 no >>> >>> I have seen https://bugs.eclipse.org/bugs/show_bug.cgi?id=333771 but I >>>am >>> not sure if it's related, because I do not set any logging properties >>> within the jetty-maven-plugin. In fact, I'm not even sure how the >>> logging properties are handled at all. >>> I am using slf4j 1.7.5, and jetty 7.2.0.RC0 works with both slf4j 1.7.5 >>> and 1.5.9.RC0. >>> Transitive dependencies for the jetty-maven-plugin are: >>> [INFO] +- org.slf4j:slf4j-api:jar:1.7.5:compile >>> [INFO] +- org.slf4j:slf4j-log4j12:jar:1.7.5:compile >>> [INFO] | \- log4j:log4j:jar:1.2.14:compile (version managed from >>>1.2.17) >>> >>> I added a log4j.properties to src/main/resources with this: >>> >>> log4j.rootLogger = TRACE, A1 >>> >>> log4j.appender.A1=org.apache.log4j.ConsoleAppender >>> >>> And it still didn't help >>> >>> So my question, how can I enable the logging shown above for jetty >>>8.1.10? >>> >>> Thank you, >>> Daniel Winsor >>> Associate, IT Architecture >>> _______________________________________________ >>> jetty-users mailing list >>> >>>[email protected]<mailto:[email protected]><mailto:jetty-use >>>rs >>> @eclipse.org<mailto:[email protected]>> >>> https://dev.eclipse.org/mailman/listinfo/jetty-users >>> >>> >>> _______________________________________________ jetty-users mailing >>>list >>> >>>[email protected]<mailto:[email protected]><mailto:jetty-use >>>rs >>> @eclipse.org<mailto:[email protected]>> >>> https://dev.eclipse.org/mailman/listinfo/jetty-users >>> _______________________________________________ >>> jetty-users mailing list >>> [email protected]<mailto:[email protected]> >>> https://dev.eclipse.org/mailman/listinfo/jetty-users >>> >>> _______________________________________________ jetty-users mailing >>>list >>> [email protected]<mailto:[email protected]> >>> https://dev.eclipse.org/mailman/listinfo/jetty-users >>> _______________________________________________ >>> jetty-users mailing list >>> [email protected] >>> https://dev.eclipse.org/mailman/listinfo/jetty-users >> >> _______________________________________________ >> jetty-users mailing list >> [email protected] >> https://dev.eclipse.org/mailman/listinfo/jetty-users >> > >_______________________________________________ >jetty-users mailing list >[email protected] >https://dev.eclipse.org/mailman/listinfo/jetty-users _______________________________________________ jetty-users mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/jetty-users
