Hi Sanjay,
That's strange. The way it works is, once configuration changes are done, your app-bits are
shuttled to the cluster instances (called cache repository). It seems to me that that process is
hanging (it is called Repository Synchronization).
I would like to understand the root cause here. So, I need your help.
- Start from a clean slate.
- Start the DAS (admin server) and create your cluster.
- Start the node-agents and clusters.
- Deploy the application. (In other words, redo deployment part). At this point asadmin appears
to hang.
- kill -3 <appserver-DAS-process-id> (this can be revealed from the jps command).
A file named jvm.log will be populated in <domain-dir>/logs folder.
Kindly attach that file.
BTW, how much memory DAS is configured with?
Thanks,
Kedar
[Message sent by forum member 'km' (km)]
http://forums.java.net/jive/thread.jspa?messageID=240493