gradle 4: jetty doesn't start war when compiled with gretty plugin

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

gradle 4: jetty doesn't start war when compiled with gretty plugin

Bill Ross-2

In case anyone is using gretty, hopefully the fix is obvious, else I'll downgrade gradle, since 4.0 only has gretty support.

Thanks,

Bill

https://github.com/akhikhl/gretty/issues/413

build.gradle:

apply plugin: 'war'
//apply plugin: 'jetty'
apply from: 'https://raw.github.com/akhikhl/gretty/master/pluginScripts/gretty.plugin'

war {
    archiveName = 'pr.war'  
    webXml = file('src/web.xml')
}
# added
gretty {
    servletContainer = 'jetty9'
    httpPort = 8080
}

_______________________________________________
jetty-users mailing list
[hidden email]
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/jetty-users
Reply | Threaded
Open this post in threaded view
|

Re: gradle 4: jetty doesn't start war when compiled with gretty plugin

Bill Ross-2

Same without gretty - the war isn't seen, it seems. I went back to the gradle 2 config, and still war doesn't load. I can't find any active log files in jetty.home or jetty.base, so presumably what I see on the console is all there is, including starting c3p0, so it's getting that config.

This code had no effect:

    @Override
    public void init(ServletConfig config) throws ServletException {
System.err.println("EEEE");
System.exit(1);

Other than trying gretty, I changed DAO's and database since the last time I started the server, but no config changes.

The log to stderr looks the same as usual:

WARN  : Deprecated [name] used in ${jetty.base}/modules/logging.mod

[ShutdownMonitor] Not enabled (port < 0): -1
Feb 12, 2018 10:36:56 PM com.mchange.v2.log.MLog <clinit>
INFO: MLog clients using java 1.4+ standard logging.
Feb 12, 2018 10:36:56 PM com.mchange.v2.c3p0.C3P0Registry banner
INFO: Initializing c3p0-0.9.1.2 [built 21-May-2007 15:04:56; debug? true; trace: 10]
SLF4J: Class path contains multiple SLF4J bindings.
SLF4J: Found binding in [jar:file:/tmp/jetty-0.0.0.0-8080-pr.war-_pr-any-3090547320525633267.dir/webapp/WEB-INF/lib/logback-classic-1.0.7.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in [jar:file:/hdd/reep/home/pr/jetty-base/lib/logging/logback-classic-1.0.7.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
SLF4J: Actual binding is of type [ch.qos.logback.classic.util.ContextSelectorStaticBinder]

Feb 12, 2018 10:36:56 PM com.mchange.v2.c3p0.impl.AbstractPoolBackedDataSource getPoolManager
INFO: Initializing c3p0 pool...  [lots]

and that's it.

$ java -jar ./jetty-distribution-9.4.6.v20170531/start.jar \

             jetty.home=./jetty-distribution-9.4.6.v20170531 \
             jetty.base=./jetty-base

On 2/12/18 4:44 PM, Bill Ross wrote:

In case anyone is using gretty, hopefully the fix is obvious, else I'll downgrade gradle, since 4.0 only has gretty support.

Thanks,

Bill

https://github.com/akhikhl/gretty/issues/413

build.gradle:

apply plugin: 'war'
//apply plugin: 'jetty'
apply from: 'https://raw.github.com/akhikhl/gretty/master/pluginScripts/gretty.plugin'

war {
    archiveName = 'pr.war'  
    webXml = file('src/web.xml')
}
# added
gretty {
    servletContainer = 'jetty9'
    httpPort = 8080
}


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

Re: gradle 4: jetty doesn't start war when compiled with gretty plugin

Bill Ross-2

Solved. Hints for others in the same situation:

  - look at jetty-base/resources/logback.xml for log location

  - a leftover print to stdout is what finally alerted me that the war is being started

Underlying causes: disk migration (log location) and missing resource causing startup hang.

Bill


On 2/12/18 10:57 PM, Bill Ross wrote:

Same without gretty - the war isn't seen, it seems. I went back to the gradle 2 config, and still war doesn't load. I can't find any active log files in jetty.home or jetty.base, so presumably what I see on the console is all there is, including starting c3p0, so it's getting that config.

This code had no effect:

    @Override
    public void init(ServletConfig config) throws ServletException {
System.err.println("EEEE");
System.exit(1);

Other than trying gretty, I changed DAO's and database since the last time I started the server, but no config changes.

The log to stderr looks the same as usual:

WARN  : Deprecated [name] used in ${jetty.base}/modules/logging.mod

[ShutdownMonitor] Not enabled (port < 0): -1
Feb 12, 2018 10:36:56 PM com.mchange.v2.log.MLog <clinit>
INFO: MLog clients using java 1.4+ standard logging.
Feb 12, 2018 10:36:56 PM com.mchange.v2.c3p0.C3P0Registry banner
INFO: Initializing c3p0-0.9.1.2 [built 21-May-2007 15:04:56; debug? true; trace: 10]
SLF4J: Class path contains multiple SLF4J bindings.
SLF4J: Found binding in [<a class="moz-txt-link-freetext" href="jar:file:/tmp/jetty-0.0.0.0-8080-pr.war-_pr-any-3090547320525633267.dir/webapp/WEB-INF/lib/logback-classic-1.0.7.jar%21/org/slf4j/impl/StaticLoggerBinder.class" moz-do-not-send="true">jar:file:/tmp/jetty-0.0.0.0-8080-pr.war-_pr-any-3090547320525633267.dir/webapp/WEB-INF/lib/logback-classic-1.0.7.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in [<a class="moz-txt-link-freetext" href="jar:file:/hdd/reep/home/pr/jetty-base/lib/logging/logback-classic-1.0.7.jar%21/org/slf4j/impl/StaticLoggerBinder.class" moz-do-not-send="true">jar:file:/hdd/reep/home/pr/jetty-base/lib/logging/logback-classic-1.0.7.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
SLF4J: Actual binding is of type [ch.qos.logback.classic.util.ContextSelectorStaticBinder]

Feb 12, 2018 10:36:56 PM com.mchange.v2.c3p0.impl.AbstractPoolBackedDataSource getPoolManager
INFO: Initializing c3p0 pool...  [lots]

and that's it.

$ java -jar ./jetty-distribution-9.4.6.v20170531/start.jar \

             jetty.home=./jetty-distribution-9.4.6.v20170531 \
             jetty.base=./jetty-base

On 2/12/18 4:44 PM, Bill Ross wrote:

In case anyone is using gretty, hopefully the fix is obvious, else I'll downgrade gradle, since 4.0 only has gretty support.

Thanks,

Bill

https://github.com/akhikhl/gretty/issues/413

build.gradle:

apply plugin: 'war'
//apply plugin: 'jetty'
apply from: 'https://raw.github.com/akhikhl/gretty/master/pluginScripts/gretty.plugin'

war {
    archiveName = 'pr.war'  
    webXml = file('src/web.xml')
}
# added
gretty {
    servletContainer = 'jetty9'
    httpPort = 8080
}


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