| Re: [jetty-users] Is there a limit on number of vhost.xml files? |
Ok, enabled dumpAfterStart but I can not find any dump file. I also enabled debug logging for jetty but still can not find any errors. The only thing I see, is the following lines at the end of the console log: 2017-03-31 09:40:54.033:INFO::main: Console stderr/stdout captured to /opt/jetty_default/logs/2017_03_31.jetty.log 2017-03-31 09:40:54.033:DBUG:oejx.XmlConfiguration:main: XML call setErr . . . . . . . . . . . . . . FAILED Fri Mar 31 09:41:49 CEST 2017 Not sure if that XML call setErr is some clue? BTJ On Wed, 2017-03-29 at 11:41 +1100, Jan Bartel wrote: > Try enabling dumpAfterStart on the server to see if that gives you more information. Make sure you have all jetty logging turned up to debug level. Then try hot deploying one at a time until you get an error. > > Jan > > On 24 March 2017 at 23:12, Bjørn T Johansen <btj@xxxxxxxxxx> wrote: > > Ok, just deployed a new version of one of the applicaions and now I got a FAILED again, the only change was a new war file. > > But I checked all the web applications and all is up and running, so not sure why Jetty writes FAILED when it starts? > > > > BTJ > > > > On Tue, 2017-03-21 at 14:07 +0100, Bjørn T Johansen wrote: > > > The problem is that the logfile does not really tell me anything, unless I am blind. > > > I guess there is no limit to the number of vhosts then, I only have 8-9. What's strange is that all the web applications are coming up, according the logs for the specific web applications.. I haven't tested yet, but will try to test all the web applications if they indeed respond as well, when I get that FAILED message.. > > > > > > BTJ > > > > > > On Mon, 2017-03-20 at 13:56 -0700, Joakim Erdfelt wrote: > > > > What do those logs tell you? > > > > /opt/jetty_default/logs/2017_03_18.jetty.log > > > > > > > > Just tried setting up a jetty.base with 4096 webapps, all on different vhosts. > > > > Takes a while to startup, but no FAILED message. > > > > How many do you have? > > > > > > > > > > > > > > > > > > > > Joakim Erdfelt / joakim@xxxxxxxxxxx > > > > > > > > > > > > On Sat, Mar 18, 2017 at 5:50 AM, Bjørn T Johansen <btj@xxxxxxxxxx> wrote: > > > > > When I start my jetty application, after adding one more vhost*.xml file, it says the following: > > > > > > > > > > Starting Jetty: StartLog to /var/run/jetty/jetty-start.log > > > > > 2017-03-18 13:40:47.844:INFO::main: Logging initialized @286ms to org.eclipse.jetty.util.log.StdErrLog > > > > > 2017-03-18 13:40:47.974:INFO::main: Console stderr/stdout captured to /opt/jetty_default/logs/2017_03_18.jetty.log > > > > > . . . . . . . . . . . . . . FAILED Sat Mar 18 13:41:43 CET 2017 > > > > > > > > > > If I remove one of the xml file, then Jetty will start successfully (does not matter which xml file). > > > > > What am I missing? > > > > > > > > > > btw, I am using Jetty 9.4.2.. > > > > > > > > > > > > > > > Regards, > > > > > > > > > > BTJ > > > > > > > > > > _______________________________________________ > > > > > jetty-users mailing list > > > > > jetty-users@xxxxxxxxxxx > > > > > To change your delivery options, retrieve your password, or unsubscribe from this list, visit > > > > > https://dev.eclipse.org/mailman/listinfo/jetty-users > > > > > > > > > > > _______________________________________________ > > > jetty-users mailing list > > > jetty-users@xxxxxxxxxxx > > > To change your delivery options, retrieve your password, or unsubscribe from this list, visit > > > https://dev.eclipse.org/mailman/listinfo/jetty-users > > > > > > > _______________________________________________ > > jetty-users mailing list > > jetty-users@xxxxxxxxxxx > > To change your delivery options, retrieve your password, or unsubscribe from this list, visit > > https://dev.eclipse.org/mailman/listinfo/jetty-users > > > > > > _______________________________________________ > jetty-users mailing list > jetty-users@xxxxxxxxxxx > To change your delivery options, retrieve your password, or unsubscribe from this list, visit > https://dev.eclipse.org/mailman/listinfo/jetty-users
Attachment:
signature.asc
Description: This is a digitally signed message part