Jan,

I'm getting nuts! While the issue lasted for more than 2 month since first 
observation I can't reproduce it anymore since I posted to the mailing list. 
Not sure if I can blame Murphy for this or have to blame myself for doing 
something subtle different then the weeks before. Actually I would not have 
posted here without being sure to be able to reproduce. But sth changed 
obviously. I will try to isolate this factor and will reply ASAP.

Thanks,
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 <[email protected] 
<mailto:[email protected]>> 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 
<http://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
    [email protected] <mailto:[email protected]>
    To change your delivery options, retrieve your password, or unsubscribe 
from this list, visit
    https://dev.eclipse.org/mailman/listinfo/jetty-users




--
Jan Bartel <[email protected] <mailto:[email protected]>>
www.webtide.com <http://www.webtide.com>
/Expert assistance from the creators of Jetty and CometD/



_______________________________________________
jetty-users mailing list
[email protected]
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
[email protected]
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/jetty-users

Reply via email to