1 Reply Latest reply on Oct 1, 2010 8:16 AM by hhcofcmds

    seam example failing during GlassFish deployment.

    javapool
    javapool Apr 29, 2010 5:46 PM

      I am trying to install seam example (Booking as well Registration) and it's failing during GlassFish deployment.


      The environment is
      GlassFish - Installed Version:GlassFish v3 (build 1)
      SEAM - jboss-seam-2.2.1.CR1
      JDK - jdk1.6.0 18
      Using Oracle 10g (transaction-type - JTA in persistence.xml)


      Pls let me know what am I missing here.


      Thanks in advance.


      The following details are captured during Registration deployment: (newly created domain with required lib. files)
      The server logs are


      Root cause Exception :-
      -2010-04-29T11:15:56.830-0400SEVEREglassfishv3.0javax.enterprise.system.core.org.glassfish.internal.data ThreadID-29; ThreadName-Thread-1;Exception while invoking class com.sun.enterprise.web.WebApplication start method
      java.lang.Exception: java.lang.IllegalStateException: ContainerBase.addChild: start: org.apache.catalina.LifecycleException: java.lang.LinkageError: loader constraint violation: when resolving method javassist.util.proxy.FactoryHelper.toClass(Ljavassist/bytecode/ClassFile;Ljava/lang/ClassLoader;Ljava/security/ProtectionDomain;)Ljava/lang/Class; the class loader (instance of org/glassfish/javaee/full/deployment/EarClassLoader) of the current class, org/jboss/seam/util/ProxyFactory, and the class loader (instance of org/apache/felix/framework/ModuleImpl$ModuleClassLoader) for resolved class, javassist/util/proxy/FactoryHelper, have different Class objects for the type javassist/bytecode/ClassFile used in the signature
              at com.sun.enterprise.web.WebApplication.start(WebApplication.java:117)
              at org.glassfish.internal.data.EngineRef.start(EngineRef.java:126)
              at org.glassfish.internal.data.ModuleInfo.start(ModuleInfo.java:241)
              at org.glassfish.internal.data.ApplicationInfo.start(ApplicationInfo.java:236)
             
              A little above I see the following logging
             
              -2010-04-29T11:15:50.958-0400INFOglassfishv3.0javax.enterprise.system.core.transaction.com.sun.jts.CosTransactions ThreadID-29; ThreadName-Thread-1;JTS5014: Recoverable JTS instance, serverId - 100-
             
              -      2010-04-29T11:15:51.192-0400INFOglassfishv3.0org.eclipse.persistence.session.file:/C:/glassfishv3/glassfish/domains/domain1/applications/ejb-timer-service-app/WEB-INF/classes/   EJB  Timer  App ThreadID-29; ThreadName-Thread-1;file:/C:/glassfishv3/glassfish/domains/domain1/applications/ejb-timer-service-app/WEB-INF/classes/   EJB  Timer  App login successful-
             
              -2010-04-29T11:15:51.989-0400INFOglassfishv3.0javax.enterprise.resource.webcontainer.jsf.config ThreadID-29; ThreadName-Thread-1;Initializing Mojarra 2.0.2 (FCS b10) for context '/seam-registration'-
             
              -      2010-04-29T11:15:56.815-0400SEVEREglassfishv3.0org.apache.catalina.core.StandardContext ThreadID-29; ThreadName-Thread-1;PWC1306: Startup of context /seam-registration failed due to previous errors-
             
              -2010-04-29T11:15:56.815-0400SEVEREglassfishv3.0org.apache.catalina.core.StandardContext ThreadID-29; ThreadName-Thread-1;PWC1305: Exception during cleanup after start failed
              org.apache.catalina.LifecycleException: PWC2769: Manager has not yet been started
              at org.apache.catalina.session.StandardManager.stop(StandardManager.java:892)

      • 695 Views
      • Tags: