I'm seeing the same behavior when I restart after normal
deploy/undeploy. domain.xml is no longer found and domain.bak remains
in config.
Exception in thread "Thread-1" com.sun.enterprise.v3.server.BootError:
Failed to parse
C:\v3-2-6\v3\distributions\web\target\web\glassfish\config\..\domains\domain1\config\domain.xml
at
com.sun.enterprise.v3.server.DomainXml.parseDomainXml(DomainXml.java:96)
at com.sun.enterprise.v3.server.DomainXml.run(DomainXml.java:79)
Tim Quinn wrote:
> Hi.
>
> If I start the server successfully using java -jar <the-main-jar> and
> then I deploy a web app, and the domain.xml file is renamed to
> domain.bak. It is never renamed back to .xml nor is a new domain.xml
> created - at least not anywhere I have found and I've looked. The
> same thing happens if I restart the server with a web app deployed
> already (having renamed the domain.bak back to domain.xml or else the
> server will not start).
>
> Interestingly, using java -jar to start the server I do not see the
> class not found exceptions for
> com.sun.enterprise.admin.server.core.jmx.AppServerMBeanServerBuilder
> that I see when I run using mvn gf:run.
>
> Further, if I run with mvn gf:run then I see the exceptions I wrote
> about last night but I *do *get a new domain.xml in the domain's
> config directory!
>
> Odd. Any ideas?
>
> - Tim