>
> There is a very long timeout -- did you wait? I think it is 10
> minutes now.
> CLI is waiting for the response from a server command, "uptime". It
> is trying 4848. So you should always try 4848 in such situations --
> not 8080
Am waiting, but the behavior is different with a current build.
Asadmin start-domain returns successfully, but in the server log I see
this (the original prelude domain had the classloader/hellojsf
quicklook test deployed):
[...]
[#|2009-10-07T14:48:08.131-0400|INFO|glassfish|null|
_ThreadID=15;_ThreadName=Thread-3;|Grizzly Framework started in: 270ms
listening on port 4848|#]
[#|2009-10-07T14:48:08.131-0400|INFO|glassfish|null|
_ThreadID=16;_ThreadName=Thread-3;|Grizzly Framework started in: 435ms
listening on port 8080|#]
[#|2009-10-07T14:48:09.757-0400|WARNING|glassfish|
org.jvnet.hk2.osgimain|_ThreadID=11;_ThreadName=Thread-3;|Exception
while starting bundle com.sun.enterprise.osgi-adapter [131]
org.osgi.framework.BundleException: Activator start error in bundle
com.sun.enterprise.osgi-adapter [131].
at org.apache.felix.framework.Felix.activateBundle(Felix.java:1750)
at org.apache.felix.framework.Felix.startBundle(Felix.java:1621)
at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:890)
at org.jvnet.hk2.osgimain.Main.start(Main.java:124)
at
org
.apache
.felix.framework.util.SecureAction.startActivator(SecureAction.java:667)
at org.apache.felix.framework.Felix.activateBundle(Felix.java:1699)
at org.apache.felix.framework.Felix.startBundle(Felix.java:1621)
at org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:
1076)
at org.apache.felix.framework.StartLevelImpl.run(StartLevelImpl.java:
264)
at java.lang.Thread.run(Thread.java:637)
Caused by: com.sun.enterprise.module.ResolveError: Not able to locate
a unique module by name org.glassfish.jsftemplating
at
com
.sun
.enterprise
.v3
.server
.ClassLoaderHierarchyImpl
.createApplicationParentCL(ClassLoaderHierarchyImpl.java:166)
at
org
.glassfish
.deployment
.common
.DeploymentContextImpl.createClassLoader(DeploymentContextImpl.java:187)
at
org
.glassfish
.deployment
.common
.DeploymentContextImpl
.createDeploymentClassLoader(DeploymentContextImpl.java:172)
at
com
.sun
.enterprise
.v3.server.ApplicationLifecycle.deploy(ApplicationLifecycle.java:219)
at
com
.sun
.enterprise
.v3
.server
.ApplicationLoaderService
.processApplication(ApplicationLoaderService.java:340)
at
com
.sun
.enterprise
.v3
.server
.ApplicationLoaderService.postConstruct(ApplicationLoaderService.java:
163)
at
com.sun.hk2.component.AbstractWombImpl.inject(AbstractWombImpl.java:174)
at com.sun.hk2.component.ConstructorWomb$1.run(ConstructorWomb.java:91)
at java.security.AccessController.doPrivileged(Native Method)
at
com.sun.hk2.component.ConstructorWomb.initialize(ConstructorWomb.java:
88)
at com.sun.hk2.component.AbstractWombImpl.get(AbstractWombImpl.java:77)
at
com.sun.hk2.component.SingletonInhabitant.get(SingletonInhabitant.java:
58)
at com.sun.hk2.component.LazyInhabitant.get(LazyInhabitant.java:107)
at
com
.sun
.hk2.component.AbstractInhabitantImpl.get(AbstractInhabitantImpl.java:
60)
at
com
.sun.enterprise.v3.server.AppServerStartup.run(AppServerStartup.java:
233)
at
com
.sun.enterprise.v3.server.AppServerStartup.start(AppServerStartup.java:
129)
at com.sun.enterprise.module.bootstrap.Main.launch(Main.java:457)
at com.sun.enterprise.module.bootstrap.Main.launch(Main.java:401)
at org.jvnet.hk2.osgiadapter.HK2Main.start(HK2Main.java:121)
at
org
.apache
.felix.framework.util.SecureAction.startActivator(SecureAction.java:667)
at org.apache.felix.framework.Felix.activateBundle(Felix.java:1699)
... 9 more
And the last message in the log is:
[#|2009-10-07T14:48:09.892-0400|INFO|glassfish|org.glassfish.web.osgi|
_ThreadID=20;_ThreadName=Thread-3;|Waiting for Server to start|#]
After that I can hit localhost:8080 and 4848, but the latter doesn't
actually load the admin console. Am just watching the "loading in
progress screen" with this message over and over:
[#|2009-10-07T15:00:53.360-0400|INFO|glassfish|null|
_ThreadID=23;_ThreadName=Thread-3;|AdminConsoleAdapter's STATE IS: The
Admin Console is loading...|#]
And, finally, I can't stop the server normally:
hostname% ^start^stop
./bin/asadmin stop-domain domain1
CLI306 Warning - server is not running.
Command stop-domain executed successfully.