I have the following setup, via VMWare
OS: CentOS 5.1 Linux deki.nirving.local 2.6.18-53.el5 #1 SMP Mon Nov 12
02:22:48 EST 2007 i686 athlon i386 GNU/Linux
JRE:
java version "1.5.0_14"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_14-b03)
Java HotSpot(TM) Client VM (build 1.5.0_14-b03, mixed mode, sharing)
Glassfish: V2 UR1 Final Build
I have a domain created by issuing
lib/ant/bin/ant -f setup-cluster
Node Agent created by
/opt/glassfish/bin/asadmin create-node-agent nodeagent1
Instance created by
/opt/glassfish/bin/asadmin create-instance --user admin --passwordfile
/opt/glassfish/passwords --host localhost --port 4848 --nodeagent nodeagent1
--systemproperties
"JMX_SYSTEM_CONNECTOR_PORT=8687:IIOP_LISTENER_PORT=3330:IIOP_SSL_LISTENER_PORT=4440:IIOP_SSL_MUTUALAUTH_PORT=5550:HTTP_LISTENER_PORT=8080:HTTP_SSL_LISTENER_PORT=8180"
instance1
When I add a large Web Application (xwiki is what I am trying to deploy) I
cannot start my instance instance1 via the console, as it tries to
synchronise with the domain via the nodeagent and after a while the
following appears in the log of instance1
[#|2008-02-20T13:07:17.229+1100|INFO|sun-appserver9.1|javax.ee.enterprise.system.tools.synchronization|_ThreadID=11;_ThreadName=sync-1;|SYNC014:
Unable to update synchronization timestamp.
com.sun.enterprise.ee.synchronization.SynchronizationException: Error while
updating timestamp for synch request: ${com.sun.aas.instanceRoot
}/applications/
at com.sun.enterprise.ee.synchronization.TimestampCommand.execute(
TimestampCommand.java:153)
at com.sun.enterprise.ee.synchronization.BaseRequestMediator.commit(
BaseRequestMediator.java:151)
at com.sun.enterprise.ee.synchronization.BaseRequestMediator.run(
BaseRequestMediator.java:126)
at java.lang.Thread.run(Thread.java:595)
Caused by: java.lang.NullPointerException
at com.sun.enterprise.ee.synchronization.TimestampCommand.execute(
TimestampCommand.java:85)
... 3 more
|#]
if i stop the nodeagent via /opt/glassfish/bin/asadmin stop-node-agent
nodeagent1 the instance stops, but the node agent process is still there, so
something is not right.
Any ideas, as this is stopping me from deploying the application?
Thanks
Nicholas Irving