Details

    • Similar Issues:
      Show 5 results 

      Description

      The steps are simple:

      1. Extract the GlassFish 3.1.2.2 WAR.
      2. Extract the Liferay dependencies to the domains\domain1\lib folder.
      3. Update domains\domain1\config\domain.xml per attached.
      3.5. Start glassfish with asadmin start-domain domain1
      4. Deploy Liferay using "asadmin deploy --force=true --upload=true liferay-portal-6.1.1.war".
      5. Complete configuration once Liferay deployed.
      6. Redeploy Liferay using "asadmin deploy --force=true --upload=true liferay-portal-6.1.1.war".

      Deployment fails with:

      remote failure: Error occurred during deployment: Exception while loading the app : java.lang.IllegalStateException: ContainerBase.addChild: start: org.apache.c
      atalina.LifecycleException: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'com.liferay.portal.spring.aop.ServiceBeanAut
      oProxyCreator#0' defined in class path resource [META-INF/base-spring.xml]: Cannot resolve reference to bean 'serviceAdvice' while setting bean property 'method
      Interceptor'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'serviceAdvice' defined in class path r
      esource [META-INF/base-spring.xml]: Cannot resolve reference to bean 'asyncAdvice' while setting bean property 'nextMethodInterceptor'; nested exception is org.
      springframework.beans.factory.BeanCreationException: Error creating bean with name 'asyncAdvice' defined in class path resource [META-INF/base-spring.xml]: Cann
      ot resolve reference to bean 'threadLocalCacheAdvice' while setting bean property 'nextMethodInterceptor'; nested exception is org.springframework.beans.factory
      .BeanCreationException: Error creating bean with name 'threadLocalCacheAdvice' defined in class path resource [META-INF/base-spring.xml]: Cannot resolve referen
      ce to bean 'bufferedIncrementAdvice' while setting bean property 'nextMethodInterceptor'; nested exception is org.springframework.beans.factory.BeanCreationExce
      ption: Error creating bean with name 'bufferedIncrementAdvice' defined in class path resource [META-INF/base-spring.xml]: Cannot resolve reference to bean 'inde
      xableAdvice' while setting bean property 'nextMethodInterceptor'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating be
      an with name 'indexableAdvice' defined in class path resource [META-INF/base-spring.xml]: Cannot resolve reference to bean 'transactionAdvice' while setting bea
      n property 'nextMethodInterceptor'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'transactionAdvic
      e' defined in class path resource [META-INF/base-spring.xml]: Cannot resolve reference to bean 'liferayTransactionManager' while setting bean property 'platform
      TransactionManager'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'liferayTransactionManager' defi
      ned in class path resource [META-INF/hibernate-spring.xml]: Cannot resolve reference to bean 'liferayHibernateSessionFactory' while setting constructor argument
      ; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'liferayHibernateSessionFactory' defined in class p
      ath resource [META-INF/hibernate-spring.xml]: Invocation of init method failed; nested exception is java.lang.IllegalStateException: Unable to initialize portal
      . Please see server.log for more details.
      Command deploy failed.

      Attempts to access Liferay fail with error 500.

      (For some reason, the server.log file doesn't contain any error details.)

        Activity

        Hide
        Kevin Dean added a comment -

        Forgot one step, between 3 and 4:

        Start GlassFish with "asadmin start-domain domain1".

        Show
        Kevin Dean added a comment - Forgot one step, between 3 and 4: Start GlassFish with "asadmin start-domain domain1".
        Hide
        Sharry Shi added a comment -

        No Longer Reproducible on:
        Tomcat 7.0 + MySQL 5. Portal 6.2.x GIT ID: 5d1615af460142a39fdc9354c5190205939b015e.

        Redeployed successfully.

        Show
        Sharry Shi added a comment - No Longer Reproducible on: Tomcat 7.0 + MySQL 5. Portal 6.2.x GIT ID: 5d1615af460142a39fdc9354c5190205939b015e. Redeployed successfully.
        Hide
        Kevin Dean added a comment -

        I don't understand this resolution at all.

        The case specifically refers to GlassFish 3.1.2.2 with detailed steps to reproduce. Testing against Tomcat does not in any way address the problem.

        Show
        Kevin Dean added a comment - I don't understand this resolution at all. The case specifically refers to GlassFish 3.1.2.2 with detailed steps to reproduce. Testing against Tomcat does not in any way address the problem.
        Hide
        Andrew Betts added a comment -

        GlassFish 3.1.2 leaves stale files on the server even after liferay has been undeployed. In order to resolve the issue you need to delete these files.

        1. Undeploy the Liferay application from the admin console.
        2. Shut down the Glassfish application server.
        3. Go to the glassfish-3.1.2\domains[domain]\applications directory and delete the liferay-portal application.
        4. Go to the glassfish-3.1.2\domains[domain]\autodeploy folder and delete both Liferay deployments within the folder. They should be named: liferay-portal.war and liferay-portal.war_deployed
        5. Go to the Glassfish admin console and deploy liferay again.

        Show
        Andrew Betts added a comment - GlassFish 3.1.2 leaves stale files on the server even after liferay has been undeployed. In order to resolve the issue you need to delete these files. 1. Undeploy the Liferay application from the admin console. 2. Shut down the Glassfish application server. 3. Go to the glassfish-3.1.2\domains[domain]\applications directory and delete the liferay-portal application. 4. Go to the glassfish-3.1.2\domains[domain]\autodeploy folder and delete both Liferay deployments within the folder. They should be named: liferay-portal.war and liferay-portal.war_deployed 5. Go to the Glassfish admin console and deploy liferay again.
        Hide
        Kevin Dean added a comment -

        Then there is something about Liferay that is causing this problem with GlassFish. None of the applications I have ever developed have had this problem. I suggest you take this problem up with Oracle to determine where the fault lies.

        Show
        Kevin Dean added a comment - Then there is something about Liferay that is causing this problem with GlassFish. None of the applications I have ever developed have had this problem. I suggest you take this problem up with Oracle to determine where the fault lies.
        Hide
        Jane Kim (Inactive) added a comment -

        Reproduced on:
        Glassfish 3.1.2.2. Portal 6.1.x GIT ID: 17b7629d59a690c997434941ae33d40a952a4f1f
        Glassfish 3.1.2.2. Portal 6.2.x GIT ID: c8da79cfdc20e6932a0bc979d9c93fadb4947e30

        Show
        Jane Kim (Inactive) added a comment - Reproduced on: Glassfish 3.1.2.2. Portal 6.1.x GIT ID: 17b7629d59a690c997434941ae33d40a952a4f1f Glassfish 3.1.2.2. Portal 6.2.x GIT ID: c8da79cfdc20e6932a0bc979d9c93fadb4947e30
        Hide
        Arthur Hsiao (Inactive) added a comment -

        Hello Kevin,

        I am Arthur with the support department and I actually was the engineer that figured out that Glassfish left behind stale files that needed to be deleted prior to redeployment. Currently, the issue seems to be a known issue from here: https://java.net/jira/browse/GLASSFISH-19087 or at least a user had reported it. But due to a lack of response from the reporting user, Glassfish representatives went ahead and closed the ticket. From this ticket, however, it seems very likely that there are a handful of applications (Liferay included) that leave behind stale files and thus the server needs to be shut down and the stale files need to be deleted prior to redeployment or a bean error will arise due to the stale files thinking that Liferay still exists on the application server. Whether or not this issue is caused by the application or Glassfish is definitely intriguing, but if this occurs with other applications like the Glassfish jira ticket is insinuating, then this may be an issue with the application server itself. However, since there is a workaround to the issue and that we have offered, I'll go ahead and let Jane decide how we should approach the issue further.

        I hope that my clarification helped clear some of the confusion.

        All the best,
        Arthur

        Show
        Arthur Hsiao (Inactive) added a comment - Hello Kevin, I am Arthur with the support department and I actually was the engineer that figured out that Glassfish left behind stale files that needed to be deleted prior to redeployment. Currently, the issue seems to be a known issue from here: https://java.net/jira/browse/GLASSFISH-19087 or at least a user had reported it. But due to a lack of response from the reporting user, Glassfish representatives went ahead and closed the ticket. From this ticket, however, it seems very likely that there are a handful of applications (Liferay included) that leave behind stale files and thus the server needs to be shut down and the stale files need to be deleted prior to redeployment or a bean error will arise due to the stale files thinking that Liferay still exists on the application server. Whether or not this issue is caused by the application or Glassfish is definitely intriguing, but if this occurs with other applications like the Glassfish jira ticket is insinuating, then this may be an issue with the application server itself. However, since there is a workaround to the issue and that we have offered, I'll go ahead and let Jane decide how we should approach the issue further. I hope that my clarification helped clear some of the confusion. All the best, Arthur
        Hide
        Kevin Dean added a comment -

        That certainly sounds plausible. Is there any chance that you would be willing to take this up with the GlassFish team? While it may well be a GlassFish issue, it would be easier to have it between them and you in case Liferay is doing something (rightly or wrongly) to trigger it. It's not been an issue for any of my web apps so there's something in the interaction that is responsible.

        Show
        Kevin Dean added a comment - That certainly sounds plausible. Is there any chance that you would be willing to take this up with the GlassFish team? While it may well be a GlassFish issue, it would be easier to have it between them and you in case Liferay is doing something (rightly or wrongly) to trigger it. It's not been an issue for any of my web apps so there's something in the interaction that is responsible.

          People

          • Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:
              Days since last comment:
              1 year, 14 weeks, 5 days ago

              Development

                Structure Helper Panel