Yes, from the instance log, this seems like a synching up issue..but I
didn't do anything special in the steps..
[#|2006-12-05T22:18:23.407-0500|INFO|sun-appserver-ee9.1|javax.ee.enterprise.system.tools.synchronization|_ThreadID=10;_ThreadName=main;|IdentityManager
Data: User:adminuser|#]
[#|2006-12-05T22:18:24.415-0500|INFO|sun-appserver-ee9.1|javax.ee.enterprise.system.tools.synchronization|_ThreadID=10;_ThreadName=main;|SYNC001:
Unable to communicate with Domain Administration Server. Skipping
synchronization.|#]
[#|2006-12-05T22:18:24.417-0500|WARNING|sun-appserver-ee9.1|javax.ee.enterprise.system.tools.synchronization|_ThreadID=10;_ThreadName=main;|SYNC029:
There was an exception during synchronization. Please try again and a
full synchronization will be initiated. If the problem persists for a
server instance, you may backup and remove the cache repository (for
example, directories under nodeagents/na1/server1/) and restart the
node-agent (ex. asadmin stop-node-agent; start-node-agent
--startinstances=false) and the server instance (ex. asadmin
start-instance). All necessary configuration for the server instance
(server1 in example) will be downloaded from Domain Administration
Server by synchronization.
com.sun.enterprise.ee.synchronization.DASCommunicationException: Unable
to communicate with Domain Administration Server.
at
com.sun.enterprise.ee.synchronization.BaseSynchronizationDriver.synchronizeInternal(BaseSynchronizationDriver.java:254)
at
com.sun.enterprise.ee.synchronization.BaseSynchronizationDriver.synchronize(BaseSynchronizationDriver.java:116)
at
com.sun.enterprise.ee.synchronization.SynchronizationMain.main(SynchronizationMain.java:113)
|#]
Nandini Ektare wrote:
> Hi Hong,
>
> EE QLs seem to be runnign fine...Looks like instance sync-up failed
> for some reason on your setup...
> Do you see any logs in
> /home/hzhang/files/sun/appserver/nodeagents/sqe-agent/agent/logs/server.log
> or even DAS log?
>
> Nandini
>
>
>
> On Tue, 2006-12-05 at 18:59, Hong Zhang wrote:
>
>> How do we run the EE QuickLook tests these days? I first used the
>> command "maven bootstrap configure-cluster" to bootstrap the latest
>> nightly build and configure a cluster profile. Then I ran "maven -o
>> runtest-ee". The PE part ran fine, but when it's to the EE part, I
>> got something like this:
>>
>> Command create-node-agent executed successfully.
>> Command create-instance executed successfully.
>> start-node-agent --interactive=true --passwordfile
>> /home/hzhang/files/workspaces/sjsas91/glassfish/appserv-tests/config/adminpassword.txt
>> --terse=true --user adminuser --syncinstances=false
>> --startinstances=true --verbose=false --echo=true sqe-agent
>> Redirecting output to
>> /home/hzhang/files/sun/appserver/nodeagents/sqe-agent/agent/logs/server.log
>> Redirecting application output to
>> /home/hzhang/files/sun/appserver/nodeagents/sqe-agent/agent/logs/server.log
>> Enter Admin User:
>> Enter Admin Password:
>> Enter Master Password:
>> Enter Other Password Information (or ctrl-D or ctrl-Z):
>> com.sun.enterprise.config.ConfigException: Error refreshing
>> ConfigContext:/home/hzhang/files/sun/appserver/nodeagents/sqe-agent/sqe-server/config/domain.xml
>> cause:
>> /home/hzhang/files/sun/appserver/nodeagents/sqe-agent/sqe-server/config/domain.xml
>> (No such file or directory)
>> at
>> com.sun.enterprise.config.impl.ConfigContextImpl.refresh(ConfigContextImpl.java:386)
>> at
>> com.sun.enterprise.config.impl.ConfigContextImpl.refresh(ConfigContextImpl.java:468)
>>
>> So I checked, and there is indeed no
>> /home/hzhang/files/sun/appserver/nodeagents/sqe-agent/sqe-server/config/domain.xml
>> there. Anything wrong in my setup? Thanks.
>
>