I think Hong's issue is different from what you had ...she had rebuilt
one module and it was a known module-specific issue
For you, based on our previous mail conversations, I gather you had
installed using configure-runtime (that puts ina different profile -
'developer' into asenv.conf) instead of configure-cluster
When you run EEQL against this install, it creates new domains with this
setting instead of with 'cluster' fetching the settings from the asenv.conf
And hence DAS is accessible in non-secure mode at
http://localhost:4848
(similarly other port assignments change) whereas rest of EEQL assumes a
secure mode DAS.
Hence NA fails to contact DAS. ...Try flipping that env setting to
'cluster' or install cluster mode
That said I do agree this is a bit confusing ... (but I think I remember
seeing mails with plans to get that setting out of asenv.conf... )
Lloyd L Chambers wrote:
> I saw the same problem. I also added the following to the Quicklook
> Read Me last night:
>
>
> ____________________________________________________________________________________________________
>
> WARNING WARNING WARNING WARNING WARNING WARNING WARNING WARNING
> WARNING WARNING
> QuickLook has a bug which will hang early during the ee tests waiting
> for an http port that doesn't
> exist (it typically waits until it times out on port 38080 in
> sqe-domain, which is the http port
> found in eeconfig/ee-config.properties. But sqe-domain gets
> (incorrectly) created with port 8080.
>
> This can happen with a fresh checkout or a later run.
>
> --Lloyd Chambers, Dec 7, 2006
> ____________________________________________________________________________________________________
>
>
>
>
> On Dec 5, 2006, at 6:59 PM, 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.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>