users@glassfish.java.net

Re: glassfish starting problem?

From: <glassfish_at_javadesktop.org>
Date: Fri, 22 May 2009 01:25:53 PDT

[AutoDeploy] Selecting file D:\j2ee_proj\Sun\SDK\domains\domain1\autodeploy\async-http-server.war for autodeployment.
Autoundeploying application :async-http-server
Servlet Context Name: Async Server, Server Info: Sun GlassFish Enterprise Server v2.1
classLoader = WebappClassLoader
  delegate: true
  repositories:
----------> Parent Classloader:
EJBClassLoader :
urlSet = []
doneCalled = false
 Parent -> java.net.URLClassLoader_at_164b9b6
SharedSecrets.getJavaNetAccess()=java.net.URLClassLoader$7_at_c489a0
[AutoDeploy] Successfully autoundeployed : D:\j2ee_proj\Sun\SDK\domains\domain1\autodeploy\async-http-server.war.
deployed with moduleid = async-http-server
Asynchronous HTTP Service available: true
JMS API available: true
Messaging Properties (web.xml): glassfish.properties
Failed JMS Environment: ConnectionFactory not found
Failed to subscribe to topic: icefacesContextEventTopic
    Exception message: javax.naming.NameNotFoundException: ConnectionFactory not found
    Exception cause: javax.naming.NameNotFoundException: ConnectionFactory not found
The icefaces-ahs.jar is included in the deployment, but the JMS topics are not
configured correctly on the application server. If you intended to use the
Asynchronous HTTP Server (AHS), please refer to the ICEfaces Developer's Guide
for instructions on how to configure the JMS topics on the application server.
If you did not intend to use AHS, please remove the icefaces-ahs.jar from your
deployment and try again.
Messaging Properties (web.xml): glassfish.properties
Failed JMS Environment: ConnectionFactory not found
Failed to subscribe to topic: icefacesContextEventTopic
    Exception message: javax.naming.NameNotFoundException: ConnectionFactory not found
    Exception cause: javax.naming.NameNotFoundException: ConnectionFactory not found
The icefaces-ahs.jar is included in the deployment, but the JMS topics are not
configured correctly on the application server. If you intended to use the
Asynchronous HTTP Server (AHS), please refer to the ICEfaces Developer's Guide
for instructions on how to configure the JMS topics on the application server.
If you did not intend to use AHS, please remove the icefaces-ahs.jar from your
deployment and try again.
Failed JMS Environment: ConnectionFactory not found
Failed to subscribe to topic: icefacesResponseTopic
    Exception message: javax.naming.NameNotFoundException: ConnectionFactory not found
    Exception cause: javax.naming.NameNotFoundException: ConnectionFactory not found
The icefaces-ahs.jar is included in the deployment, but the JMS topics are not
configured correctly on the application server. If you intended to use the
Asynchronous HTTP Server (AHS), please refer to the ICEfaces Developer's Guide
for instructions on how to configure the JMS topics on the application server.
If you did not intend to use AHS, please remove the icefaces-ahs.jar from your
deployment and try again.
Starting the Asynchronous HTTP Server in servlet-mode...
GlassFish ARP available: true
Jetty ARP available: false
Adapting to GlassFish ARP environment
[AutoDeploy] Successfully autodeployed : D:\j2ee_proj\Sun\SDK\domains\domain1\autodeploy\async-http-server.war.
[Message sent by forum member 'csayantan' (csayantan)]

http://forums.java.net/jive/thread.jspa?messageID=347268