503 usually means your app is not started successfully. Since the process is forked you won't see your app's errors in the console. What I do in such setups is configure e.g. log4j for my app, to log to a file during integration tests, so that I can see what's going on serverside (for example, ServletContextListener init() crash, etc). HTH
On Thu, 2 Jun 2016 at 17:16 Tim Pizey <[email protected]> wrote: > Hi, > > I discovered that I was using an old version (9.2.2.v20140723) of the > jetty-maven-plugin, in my example recipe for web app integration > testing using jetty and jacoco > at http://github.com/timp/juice/ > > I upgraded to the latest version and discovered it does not work under > windows/java8/maven3.3. > > I then checked all intermediate versions so can say that the change > was introduced in v20160115 and has was present in 9.3.8.v20160314 or > v20160517. > > I have reviewed the change log at > https://github.com/eclipse/jetty.project/blob/jetty-9.3.x/VERSION.txt > but can see no clue as what the breaking change may have been. > > Jetty starts but responds with: > > HTTP ERROR: 503 > > Problemm accessing /. Reason: > Service Unavailable > > There are no clues in the log output that I can see. > It would be nice to be able to move up to the latest version. > > best regards > Tim > > > -- > Tim Pizey - http://tim.pizey.uk/ > _______________________________________________ > 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
