[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [jetty-users] Jetty 9.3.x Hot Deployment on external drive fails
|
Hi Jan,
looks like it is reproducable again.
What I did.
- cd'ed to jetty installation directory
- tweaked the bin/jetty.sh to carry the debug property
- cd webapps
- ../bin/jetty.sh start
- checked the index page: localhost:8080/JUnitRM -> working
fine
- touch JUnitRM.xml
- checked the index page again -> HTTP ERROR: 503 ... Service
unavailable
- ../bin/jetty.sh stop
Please find attached the log file, the corresponding context file
and the conf. Rest of the Jetty setup is out of the shelf.
Havn't tried to reproduce on 9.3.5. but have seen it there as
well.
Best regard,
Erik
On 19/10/15 09:35, Jan Bartel wrote:
Erik,
Can you post a log with debug turned on (use
-Dorg.eclipse.jetty.LEVEL=DEBUG to turn on debugging) please?
Also include the contex xml file (if there is one) and any
changed config files.
thanks
Jan
_______________________________________________
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:
2015_10_26.stderrout.log.zip
Description: Zip archive
<?xml version="1.0" encoding="ISO-8859-1"?>
<!DOCTYPE Configure PUBLIC "-//Jetty//Configure//EN" "http://www.eclipse.org/jetty/configure.dtd">
<!-- ==================================================================
Configure and deploy the jenkins web application in $(jetty.home)/webapps/jenkins
Note. If this file did not exist or used a context path other that /test
then the default configuration of jetty.xml would discover the test
webapplication with a WebAppDeployer. By specifying a context in this
directory, additional configuration may be specified and hot deployments
detected.
===================================================================== -->
<Configure class="org.eclipse.jetty.webapp.WebAppContext">
<!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -->
<!-- Required minimal context configuration : -->
<!-- + contextPath -->
<!-- + war OR resourceBase -->
<!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -->
<Set name="contextPath">/JUnitRM</Set>
<Set name="war"><SystemProperty name="jetty.home" default="."/>/webapps/JUnitRM.war</Set>
<Get name="securityHandler">
<Set name="loginService">
<New class="org.eclipse.jetty.security.HashLoginService">
<Set name="name">Jenkins Realm</Set>
<Set name="config"><SystemProperty name="jetty.home" default="."/>/etc/realm.properties</Set>
<!-- To enable reload of realm when properties change, uncomment the following lines -->
<!-- changing refreshInterval (in seconds) as desired -->
<!--
<Set name="refreshInterval">5</Set>
<Call name="start"></Call>
-->
</New>
</Set>
<Set name="checkWelcomeFiles">true</Set>
</Get>
</Configure>
# ========================================================
# jetty.conf Configuration for jetty.sh script
# --------------------------------------------------------
# This file is used by the jetty.sh script to provide
# extra configuration arguments for the start.jar command
# created by that script.
#
# Each line in this file becomes an arguement to start.jar
# in addition to those found in the start.ini file
# =======================================================
jetty-logging.xml
jetty-started.xml
webapps/jslearn.xml