Ah. Think I got it :)
Careful examination of server.log suggests the following:
[code]
[#|2007-10-31T15:03:06.796-0400|WARNING|sun-appserver-pe9.0|javax.enterprise.system.stream.err|_ThreadID=14;_ThreadName=httpWorkerThread-4848-0;_RequestID=2ccfeca3-f1ba-4673-b6de-55808fe97b7e;|[31/Oct/2007:15:03:06 EDT] ERROR [B3087]: The broker has detected an active lock file:
C:\Sun\AppServerNew 9\domains\domain1\imq\instances\imqbroker\lock
This file indicates that there is another copy of the broker running
on localhost:2621 that is also using the instance name "imqbroker".
Please use a different instance name or terminate the broker on localhost:2621.
|#]
[/code]
Does it mean that you have another broker running on the same port?
If yes, then when start this domain, it won't be able to listen on same port 2621. You have
two options:
1- change this broker's (which is EMBEDDED) port to something else that's available.
2- change this broker's type to REMOTE and assuming the other one (that runs on 2621)
allows remote connections and has user name and password that you know and have
configured.
I prefer 1, if you don't have to connect to an existing broker.
Regards,
Kedar
[Message sent by forum member 'km' (km)]
http://forums.java.net/jive/thread.jspa?messageID=243627