Skip to main content

[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

On 19 October 2015 at 15:12, Erik Dick <deved@xxxxxxxxxx> wrote:
I have a jetty standalone installation on a external drive which is connected to my mac book pro (or my mac pro), via firewire. When I try to trigger a hot deployment via 'touch <war>.xml' I run into the following exception:

2015-10-19 05:58:59.170:INFO:oejs.Server:main: jetty-9.3.3.v20150827
2015-10-19 05:58:59.187:INFO:oejdp.ScanningAppProvider:main: Deployment monitor [file:///Volumes/CRBS/test-server/webapps/] at interval 1
2015-10-19 05:58:59.734:INFO:oejsh.ContextHandler:main: Started o.e.j.w.WebAppContext@724af044{/JUnitRM,file:///private/var/folders/n_/6pdgm8s93m38nzvbwtw8m8ww0000gn/T/jetty-0.0.0.0-8080-JUnitRM.war-_JUnitRM-any-855703027366426152.dir/webapp/,AVAILABLE}{/JUnitRM.war}
2015-10-19 05:58:59.739:INFO:oejsh.ContextHandler:main: Started o.e.j.s.h.ContextHandler@32cf48b7{/jslearn,file:///Volumes/CRBS/test-server/webapps/jslearn/,AVAILABLE}
2015-10-19 05:58:59.753:INFO:oejs.ServerConnector:main: Started ServerConnector@25ad35e8{HTTP/1.1,[http/1.1]}{0.0.0.0:8080}
2015-10-19 05:58:59.753:INFO:oejs.Server:main: Started @1145ms
2015-10-19 06:00:29.931:INFO:oejsh.ContextHandler:Scanner-0: Stopped o.e.j.w.WebAppContext@724af044{/JUnitRM,null,UNAVAILABLE}{/JUnitRM.war}
2015-10-19 06:00:30.108:WARN:oejw.WebAppContext:Scanner-0: Failed startup of context o.e.j.w.WebAppContext@5c786d3c{/JUnitRM,file:///private/var/folders/n_/6pdgm8s93m38nzvbwtw8m8ww0000gn/T/jetty-0.0.0.0-8080-JUnitRM.war-_JUnitRM-any-7642976926383851049.dir/webapp/,STARTING}{/JUnitRM.war}
java.nio.file.NoSuchFileException: /private/var/folders/n_/6pdgm8s93m38nzvbwtw8m8ww0000gn/T/jetty-0.0.0.0-8080-JUnitRM.war-_JUnitRM-any-855703027366426152.dir/webapp/WEB-INF/lib/javax.servlet-api-3.1.0.jar
    at sun.nio.fs.UnixException.translateToIOException(UnixException.java:86)
    at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:102)
    at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:107)
    at sun.nio.fs.UnixFileSystemProvider.newByteChannel(UnixFileSystemProvider.java:214)
    at java.nio.file.Files.newByteChannel(Files.java:361)
    at java.nio.file.Files.newByteChannel(Files.java:407)
    at java.nio.file.spi.FileSystemProvider.newInputStream(FileSystemProvider.java:384)
    at java.nio.file.Files.newInputStream(Files.java:152)
    at org.eclipse.jetty.util.resource.PathResource.getInputStream(PathResource.java:331)
    at org.eclipse.jetty.annotations.AnnotationParser.parseJar(AnnotationParser.java:907)
    at org.eclipse.jetty.annotations.AnnotationParser.parse(AnnotationParser.java:842)
    at org.eclipse.jetty.annotations.AnnotationConfiguration$ParserTask.call(AnnotationConfiguration.java:163)
    at org.eclipse.jetty.annotations.AnnotationConfiguration$1.run(AnnotationConfiguration.java:545)
    at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:654)
    at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:572)
    at java.lang.Thread.run(Thread.java:745)

Afterwards the application can no longer be reached; 'HTTP ERROR: 503'; service unavailable'

This does not happen if I move the same installation over to the main drive of the mac book and apply same procedure.
(Mac OS 10.10; Jvm 1.8.0_60).

Not sure if that would be a bug at Jetty or on JVM level.

Regards, Erik
_______________________________________________
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



--
Jan Bartel <janb@xxxxxxxxxxx>
www.webtide.com
Expert assistance from the creators of Jetty and CometD



_______________________________________________
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

Back to the top