Jetty not starting anymore since gretty 1.1.0 about gretty

[akhikhl]

Sorry for problems with new version, I'll try to help you to fix everything quickly.

jettyEnvXmlFile -> contextConfigFile : yes, this is the right change. I thought I've added support also for an old property jettyEnvXml, but now I discover I renamed it to jettyEnvXmlFile. Sorry for inconvenience. Now we have the following: gretty extension supports contextConfigFile which is equivalent to jettyEnvXmlFile and serverConfigFile which is equivalent to jettyXmlFile. Equivalence is in a sense that you can use these properties interchangeably.

Problem with start: it is probably related to classloading. Could you, please, add managedClassReload=false to gretty and see whether it fixes the problem?

Other option: start "gradle run -i' or even "gradle run -d' to see more information on the context of the error.

[akhikhl]

Also I notice you unconditionally add jvmArgsDebug to jvmArgs. Is it intentional? Does the program start if you remove jvmArgsDebug?

[akhikhl]

Does it start, if you comment out jvmArgs at all? I'm asking because we need to isolate the problem.

[akhikhl]

I fixed breaking change with jettyEnvXmlFile and jettyXmlFile in Gretty 1.1.1: now things should work as before.
How does it look like with the other problem - application hang? Does disabling or reducing jvmArgs help?

[gregorko]

Sorry I have only little time this week.
I updated to 1.1.1 and removed all jvmArgs. Unfortunately it made no difference, it still hangs.

It might be unrelated but I have the impression the jettyEnvXmlFile or contextConfigFile is not loaded/used correctly. The file defines some EnvEntry's that also configure paths for logback. But logback now writes empty log files to the directory 'logDir_IS_UNDEFINED'. Therefore it looks like the EnvEntry's are not correctly registered.

Activating the -i option with gradle is not giving much more information. Activating -d dumping very much, but nothing looks suspicious. it finishes with:

22:52:54.045 [DEBUG] [org.akhikhl.gretty.LauncherBase] Got start status: {"status":"successfully started","host":"localhost","httpPort":8080,"contexts":[{"protocol":"http","host":"localhost","port":8080,"contextPath":"/","baseURI":"http://localhost:8080/"}]}

But my webapp has not started...

[akhikhl]

Do you start with appRun task? Does it work with appRunWar task?

[gregorko]

I used appRun but it behaves the same way when I use appRunWar. Sorry, I didn't have time to do more tests today.

[akhikhl]

Could you, please, publish a little project demonstrating how to reproduce a problem? Github or bitbucket will do.

[akhikhl]

I redesigned Gretty part dealing with start/stop. Hopefully it will fix your problem.

Could you, please, test it? The redesign is not released yet, it is available in snapshot version only. Please use the following script to configure gradle to use Gretty snapshot version:

buildscript {
  repositories {
    jcenter()
    maven { url 'http://oss.jfrog.org/artifactory/oss-snapshot-local' }
  }

  dependencies {
    classpath 'org.akhikhl.gretty:gretty:1.1.2-SNAPSHOT'
  }
}

apply plugin: 'war'
apply plugin: 'org.akhikhl.gretty'

I'm looking forward to your feedback.

[gregorko]

I'm currently on holidays, I will test it once I get back. And if there are still problems I will try to create a demonstration project.

[gregorko]

I finally had time to test and debug this against gretty 1.1.4. The problem appears to be the lookup location of contextConfigFile. I assumed it is relative from the project dir but that seems not to be the case as documented in http://akhikhl.github.io/gretty-doc/jetty-env.xml-support.html

I changed it to use an absolute path. But this is also causing troubles. I will open a new issue for that though.