13 Replies Latest reply on Jun 5, 2013 3:10 PM by jpadula35

Cannot start portal if restart it without logging off - in GateIn-3.6.0.Beta02_jbossas7

jpadula35 May 30, 2013 10:06 PM

Environment: Windows Server 2008 Enterprise Virtual Machine. GateIn-3.6.0.Beta02_jbossas7, RichFaces 4.3.0.Final

I am updating this to more accurately reflect the problem I am seeing:

The portal times out when launching if I am logged into the portal as root, or as an LDAP user and have a portlet displayed in the browser.

Then I shut down the portal.

When I launch it again, it hangs after this logging:

21:53:04,398 INFO [org.picketlink.idm.impl.tree.IDMTreeCacheImpl] (http--0.0.0.0-8180-1) StaleNodesCleaner started successfully with delay 120000

If I wait long enough, eventually it fails with these errors:

20:34:56,698 INFO [org.picketlink.idm.impl.tree.IDMTreeCacheImpl] (http--0.0.0.0-8180-1) StaleNodesCleaner started successfully with delay 120000

20:34:56,699 INFO [org.picketlink.idm.impl.cache.InfinispanAPICacheProviderImpl] (http--0.0.0.0-8180-1) Infinispan cache for Picketlink IDM created successfuly. cache name: idm-portal-api

20:34:56,701 INFO [org.exoplatform.services.organization.idm.IntegrationCache] (http--0.0.0.0-8180-1) Infinispan cache for Picketlink IDM created successfuly. cache name: idm-portal-api

20:34:56,708 INFO [org.infinispan.jmx.CacheJmxRegistration] (http--0.0.0.0-8180-1) ISPN000031: MBeans were successfully registered to the platform mbean server.

20:34:56,712 INFO [org.picketlink.idm.impl.tree.IDMTreeCacheImpl] (http--0.0.0.0-8180-1) StaleNodesCleaner started successfully with delay 120000

20:34:56,713 INFO [org.picketlink.idm.impl.cache.InfinispanIdentityStoreCacheProviderImpl] (http--0.0.0.0-8180-1) Infinispan cache for Picketlink IDM created successfuly. cache name: idm-portal-store

20:39:37,590 ERROR [org.jboss.as.controller.management-operation] (DeploymentScanner-threads - 2) Operation ("add") failed - address: ([("deployment" => "dev-image-repository.war")]) - failure description: "Operation cancelled asynchronously"

20:39:37,592 ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015052: Did not receive a response to the deployment operation within the allowed timeout period [300 seconds]. Check the server configuration file and the server logs to find more about the status of the deployment.

20:39:37,596 ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015052: Did not receive a response to the deployment operation within the allowed timeout period [300 seconds]. Check the server configuration file and the server logs to find more about the status of the deployment.

20:39:37,600 ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015052: Did not receive a response to the deployment operation within the allowed timeout period [300 seconds]. Check the server configuration file and the server logs to find more about the status of the deployment.

20:39:37,604 ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015052: Did not receive a response to the deployment operation within the allowed timeout period [300 seconds]. Check the server configuration file and the server logs to find more about the status of the deployment.

20:39:37,607 ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015052: Did not receive a response to the deployment operation within the allowed timeout period [300 seconds]. Check the server configuration file and the server logs to find more about the status of the deployment.

20:39:37,611 ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015052: Did not receive a response to the deployment operation within the allowed timeout period [300 seconds]. Check the server configuration file and the server logs to find more about the status of the deployment.

20:39:37,615 ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015052: Did not receive a response to the deployment operation within the allowed timeout period [300 seconds]. Check the server configuration file and the server logs to find more about the status of the deployment.

20:39:37,618 ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015052: Did not receive a response to the deployment operation within the allowed timeout period [300 seconds]. Check the server configuration file and the server logs to find more about the status of the deployment.

20:39:37,622 ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015052: Did not receive a response to the deployment operation within the allowed timeout period [300 seconds]. Check the server configuration file and the server logs to find more about the status of the deployment.

20:39:37,625 ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015052: Did not receive a response to the deployment operation within the allowed timeout period [300 seconds]. Check the server configuration file and the server logs to find more about the status of the deployment.

20:39:37,628 ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015052: Did not receive a response to the deployment operation within the allowed timeout period [300 seconds]. Check the server configuration file and the server logs to find more about the status of the deployment.

20:39:37,631 ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015052: Did not receive a response to the deployment operation within the allowed timeout period [300 seconds]. Check the server configuration file and the server logs to find more about the status of the deployment.

20:39:37,635 ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015052: Did not receive a response to the deployment operation within the allowed timeout period [300 seconds]. Check the server configuration file and the server logs to find more about the status of the deployment.

20:39:37,638 ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015052: Did not receive a response to the deployment operation within the allowed timeout period [300 seconds]. Check the server configuration file and the server logs to find more about the status of the deployment.

20:39:37,641 ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015052: Did not receive a response to the deployment operation within the allowed timeout period [300 seconds]. Check the server configuration file and the server logs to find more about the status of the deployment.

20:39:37,652 ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015052: Did not receive a response to the deployment operation within the allowed timeout period [300 seconds]. Check the server configuration file and the server logs to find more about the status of the deployment.

Alternatively, if I do not wait for it to fully complete launching, this happens, but may be a side issue:

When trying to open the portal in IE10, I am asked to Set Root Password.

After I enter it and click Setup, the portal page goes white, and I get redirected here:

http://dev:8180/portal/setupaction

and I get this exception in the server.log:

20:17:16,113 WARN [org.exoplatform.web.CacheUserProfileFilter] (http--0.0.0.0-8180-2) An error occured while cache user profile: java.lang.RuntimeException: LocalizationFilter exception:

at org.exoplatform.portal.application.localization.LocalizationFilter.doFilter(LocalizationFilter.java:168) [exo.portal.webui.portal-3.6.0.Beta02.jar:3.6.0.Beta02]

at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.Patched.jar:]

at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.Patched.jar:]

at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:840) [jbossweb-7.0.13.Final.Patched.jar:]

at org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:622) [jbossweb-7.0.13.Final.Patched.jar:]

at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:560) [jbossweb-7.0.13.Final.Patched.jar:]

at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:488) [jbossweb-7.0.13.Final.Patched.jar:]

at org.gatein.portal.installer.PortalSetupServlet.doPost(PortalSetupServlet.java:105) [exo.portal.component.portal-3.6.0.Beta02.jar:3.6.0.Beta02]

at javax.servlet.http.HttpServlet.service(HttpServlet.java:754) [jboss-servlet-api_3.0_spec-1.0.0.Final.jar:1.0.0.Final]

at javax.servlet.http.HttpServlet.service(HttpServlet.java:847) [jboss-servlet-api_3.0_spec-1.0.0.Final.jar:1.0.0.Final]

at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329) [jbossweb-7.0.13.Final.Patched.jar:]

at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.Patched.jar:]

at org.exoplatform.web.filter.ExtensibleFilter$ExtensibleFilterChain.doFilter(ExtensibleFilter.java:96) [exo.portal.component.web.api-3.6.0.Beta02.jar:3.6.0.Beta02]

at org.exoplatform.web.filter.ExtensibleFilter.doFilter(ExtensibleFilter.java:71) [exo.portal.component.web.api-3.6.0.Beta02.jar:3.6.0.Beta02]

at org.exoplatform.web.filter.GenericFilter.doFilter(GenericFilter.java:70) [exo.portal.component.web.api-3.6.0.Beta02.jar:3.6.0.Beta02]

at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.Patched.jar:]

at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.Patched.jar:]

at org.exoplatform.web.CacheUserProfileFilter.doFilter(CacheUserProfileFilter.java:67) [exo.portal.component.web.security-3.6.0.Beta02.jar:3.6.0.Beta02]

at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.Patched.jar:]

at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.Patched.jar:]

at org.exoplatform.frameworks.jcr.web.ThreadLocalSessionProviderInitializedFilter.doFilter(ThreadLocalSessionProviderInitializedFilter.java:122) [exo.jcr.framework.web-1.15.3-GA.jar:1.15.3-GA]

at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.Patched.jar:]

at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.Patched.jar:]

at org.exoplatform.web.login.ConversationStateUpdateFilter.doFilter(ConversationStateUpdateFilter.java:66) [exo.portal.component.web.security-3.6.0.Beta02.jar:3.6.0.Beta02]

at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.Patched.jar:]

at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.Patched.jar:]

at org.exoplatform.services.security.web.SetCurrentIdentityFilter.doFilter(SetCurrentIdentityFilter.java:88) [exo.core.component.security.core-2.5.3-GA.jar:2.5.3-GA]

at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.Patched.jar:]

at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.Patched.jar:]

at org.exoplatform.web.login.RememberMeFilter.doFilter(RememberMeFilter.java:81) [exo.portal.component.web.security-3.6.0.Beta02.jar:3.6.0.Beta02]

at org.exoplatform.web.login.RememberMeFilter.doFilter(RememberMeFilter.java:49) [exo.portal.component.web.security-3.6.0.Beta02.jar:3.6.0.Beta02]

at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.Patched.jar:]

at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.Patched.jar:]

at org.gatein.security.oauth.webapi.OAuthDelegateFilter.doFilter(OAuthDelegateFilter.java:58) [exo.portal.component.web.oauth-web-3.6.0.Beta02.jar:3.6.0.Beta02]

at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.Patched.jar:]

at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.Patched.jar:]

at org.gatein.sso.integration.SSODelegateFilter.doFilter(SSODelegateFilter.java:60) [sso-integration-1.3.3.CR03.jar:1.3.3.CR03]

at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.Patched.jar:]

at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.Patched.jar:]

at org.exoplatform.container.web.PortalContainerFilter.doFilter(PortalContainerFilter.java:78) [exo.kernel.container-2.4.3-GA.jar:2.4.3-GA]

at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.Patched.jar:]

at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.Patched.jar:]

at org.gatein.portal.installer.PortalSetupFilter.doFilter(PortalSetupFilter.java:62) [exo.portal.component.portal-3.6.0.Beta02.jar:3.6.0.Beta02]

at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.Patched.jar:]

at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.Patched.jar:]

at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) [jbossweb-7.0.13.Final.Patched.jar:]

at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161) [jbossweb-7.0.13.Final.Patched.jar:]

at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:397) [jbossweb-7.0.13.Final.Patched.jar:]

at org.gatein.sso.integration.SSODelegateValve.invoke(SSODelegateValve.java:159) [sso-integration-1.3.3.CR03.jar:1.3.3.CR03]

at org.gatein.portal.security.jboss.PortalClusteredSSOSupportValve.invoke(PortalClusteredSSOSupportValve.java:88) [exo.portal.component.web.security-jboss-3.6.0.Beta02.jar:3.6.0.Beta02]

at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:153) [jboss-as-web-7.1.1.Final.jar:7.1.1.Final]

at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:155) [jbossweb-7.0.13.Final.Patched.jar:]

at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [jbossweb-7.0.13.Final.Patched.jar:]

at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [jbossweb-7.0.13.Final.Patched.jar:]

at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:368) [jbossweb-7.0.13.Final.Patched.jar:]

at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [jbossweb-7.0.13.Final.Patched.jar:]

at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:671) [jbossweb-7.0.13.Final.Patched.jar:]

at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:930) [jbossweb-7.0.13.Final.Patched.jar:]

at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_33]

Caused by: org.apache.jasper.JasperException: java.lang.ClassCastException: java.lang.Boolean cannot be cast to java.lang.String

at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:413) [jbossweb-7.0.13.Final.Patched.jar:]

at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:326) [jbossweb-7.0.13.Final.Patched.jar:]

at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:253) [jbossweb-7.0.13.Final.Patched.jar:]

at javax.servlet.http.HttpServlet.service(HttpServlet.java:847) [jboss-servlet-api_3.0_spec-1.0.0.Final.jar:1.0.0.Final]

at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329) [jbossweb-7.0.13.Final.Patched.jar:]

at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.Patched.jar:]

at org.exoplatform.portal.application.localization.LocalizationFilter.doFilter(LocalizationFilter.java:166) [exo.portal.webui.portal-3.6.0.Beta02.jar:3.6.0.Beta02]

... 58 more

Caused by: java.lang.ClassCastException: java.lang.Boolean cannot be cast to java.lang.String

at org.apache.jsp.setup.jsp.setup_jsp._jspService(setup_jsp.java:94)

at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70) [jbossweb-7.0.13.Final.Patched.jar:]

at javax.servlet.http.HttpServlet.service(HttpServlet.java:847) [jboss-servlet-api_3.0_spec-1.0.0.Final.jar:1.0.0.Final]

at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:369) [jbossweb-7.0.13.Final.Patched.jar:]

... 64 more

20:17:54,624 ERROR [org.jboss.as.controller.management-operation] (DeploymentScanner-threads - 2) Operation ("add") failed - address: ([("deployment" => "athena-image-repository.war")]) - failure description: "Operation cancelled asynchronously"

20:17:54,627 ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015052: Did not receive a response to the deployment operation within the allowed timeout period [300 seconds]. Check the server configuration file and the server logs to find more about the status of the deployment.

20:17:54,633 ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015052: Did not receive a response to the deployment operation within the allowed timeout period [300 seconds]. Check the server configuration file and the server logs to find more about the status of the deployment.

20:17:54,637 ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015052: Did not receive a response to the deployment operation within the allowed timeout period [300 seconds]. Check the server configuration file and the server logs to find more about the status of the deployment.

20:17:54,641 ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015052: Did not receive a response to the deployment operation within the allowed timeout period [300 seconds]. Check the server configuration file and the server logs to find more about the status of the deployment.

20:17:54,646 ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015052: Did not receive a response to the deployment operation within the allowed timeout period [300 seconds]. Check the server configuration file and the server logs to find more about the status of the deployment.

20:17:54,650 ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015052: Did not receive a response to the deployment operation within the allowed timeout period [300 seconds]. Check the server configuration file and the server logs to find more about the status of the deployment.

20:17:54,655 ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015052: Did not receive a response to the deployment operation within the allowed timeout period [300 seconds]. Check the server configuration file and the server logs to find more about the status of the deployment.

20:17:54,659 ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015052: Did not receive a response to the deployment operation within the allowed timeout period [300 seconds]. Check the server configuration file and the server logs to find more about the status of the deployment.

20:17:54,663 ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015052: Did not receive a response to the deployment operation within the allowed timeout period [300 seconds]. Check the server configuration file and the server logs to find more about the status of the deployment.

20:17:54,666 ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015052: Did not receive a response to the deployment operation within the allowed timeout period [300 seconds]. Check the server configuration file and the server logs to find more about the status of the deployment.

20:17:54,669 ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015052: Did not receive a response to the deployment operation within the allowed timeout period [300 seconds]. Check the server configuration file and the server logs to find more about the status of the deployment.

20:17:54,671 ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015052: Did not receive a response to the deployment operation within the allowed timeout period [300 seconds]. Check the server configuration file and the server logs to find more about the status of the deployment.

20:17:54,675 ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015052: Did not receive a response to the deployment operation within the allowed timeout period [300 seconds]. Check the server configuration file and the server logs to find more about the status of the deployment.

20:17:54,678 ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015052: Did not receive a response to the deployment operation within the allowed timeout period [300 seconds]. Check the server configuration file and the server logs to find more about the status of the deployment.

20:17:54,687 ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015052: Did not receive a response to the deployment operation within the allowed timeout period [300 seconds]. Check the server configuration file and the server logs to find more about the status of the deployment.

20:17:54,690 ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015052: Did not receive a response to the deployment operation within the allowed timeout period [300 seconds]. Check the server configuration file and the server logs to find more about the status of the deployment.

20:17:54,693 ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015052: Did not receive a response to the deployment operation within the allowed timeout period [300 seconds]. Check the server configuration file and the server logs to find more about the status of the deployment.

Here are the changes I made in standalone.xml:

<security-domain name="gatein-domain" cache-type="default">

<login-module code="org.exoplatform.web.security.InitSharedStateLoginModule" flag="required">

<module-option name="portalContainerName" value="portal"/>

<module-option name="realmName" value="gatein-domain"/>

</login-module>

<login-module code="org.exoplatform.services.security.jaas.SharedStateLoginModule" flag="required">

<module-option name="portalContainerName" value="portal"/>

<module-option name="realmName" value="gatein-domain"/>

</login-module>

<login-module code="org.exoplatform.services.organization.idm.CustomMembershipLoginModule" flag="required">

<module-option name="portalContainerName" value="portal"/>

<module-option name="realmName" value="gatein-domain"/>

<module-option name="membershipType" value="member" />

<module-option name="groupId" value="/platform/users" />

</login-module>

<login-module code="org.exoplatform.services.security.j2ee.JBossAS7LoginModule" flag="required">

<module-option name="portalContainerName" value="portal"/>

<module-option name="realmName" value="gatein-domain"/>

</login-module>

</authentication>

</security-domain>

Message was edited by: Joe Padula

Message was edited by: Joe Padula - changed title, and rearranged info.

1. Re: Cannot start portal if restart it without logging off - in GateIn-3.6.0.Beta02_jbossas7

rutlucas May 31, 2013 1:32 AM (in response to jpadula35)

Hello Joe,

I'm curious about your error.

Could you reproduce without LDAP, with the out-of-the-box module ?
This can help us if it's the LDAP pickelink module responsible of this.

If the dev-image-repository.war a simple app that we can take a look on it ?

Thanks,
Lucas
Actions
2. Re: Cannot start portal if restart it without logging off - in GateIn-3.6.0.Beta02_jbossas7

rutlucas May 31, 2013 2:39 AM (in response to jpadula35)

The ClassCastException is a bug in the PortalSetupServlet due is not possible to write the root password in the IDM.
I fixed this one and sent a Pull Request, thanks for your test !

The IDM error needs more investigation, there is some problem trying to writting in your user's repository.

Did you check if you have rights to write into your LDAP ?

Thanks !
Lucas
Actions
3. Re: Cannot start portal if restart it without logging off - in GateIn-3.6.0.Beta02_jbossas7

jpadula35 May 31, 2013 8:06 AM (in response to rutlucas)

Lucas,
Thanks for your replies.

I tried a couple of things based on your questoins.
1) Changed back idm-configuration.xml to the out-of-the-box version, so there is no connection to LDAP.
Was able to reproduce the problem by logging in as root.

I did notice however, that if I was on certain portlet pages, the problem does not occur.

I get the problem even if I remove the
dev-image-repository.war. Sometimes our homepage shows up in the error log.

Tomorrow when I get back to the office, I will put together a more complete set of configuration, I would have to remove a lot of stuff first to simplify it.

2) regarding the rights to LDAP. I am using the MSAD-readonly example, so I don't beleve we have rights to the LDAP.

Regards,
Joe
Actions
4. Re: Cannot start portal if restart it without logging off - in GateIn-3.6.0.Beta02_jbossas7

rutlucas May 31, 2013 8:17 AM (in response to jpadula35)

Thanks Joe.

I think that may be there is a couple of issues in the scenario.

Please, could you perform a quick test with a fresh install of GateIn-3.6.0.Beta02_jbossas7 ? and your dev-image-repository.war application ?.
(Just an unzip, no more configuration needed to this test).
This could give us more about how to reproduce the error.

If everything is running well with OOTB configuration, then try to set up the LDAP configuration.

Thx,
Lucas
Actions
5. Re: Cannot start portal if restart it without logging off - in GateIn-3.6.0.Beta02_jbossas7

jpadula35 Jun 2, 2013 3:19 PM (in response to rutlucas)

Lucas,
I took one of our portlets that is causing the failure and added it to a fresh install. I couldn't get it to launch unless I added our datasources to the standalone.xml, also oracle and postgresql to modules.

Logged in as root, I get the same problem, upon restarting the second time. Getting several of these exceptoins:
14:46:41,221 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/portal].[jsp]] (http--127.0.0.1-8080-1) Servlet.service() for servlet jsp threw exception: java.lang.RuntimeException: LocalizationFilter exception:
          at org.exoplatform.portal.application.localization.LocalizationFilter.doFilter(LocalizationFilter.java:168) [exo.portal.webui.portal-3.6.0.Beta02.jar:3.6.0.Beta02]
          at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:]
          at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:]
          at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:840) [jbossweb-7.0.13.Final.jar:]
          at org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:622) [jbossweb-7.0.13.Final.jar:]
          at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:560) [jbossweb-7.0.13.Final.jar:]
          at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:488) [jbossweb-7.0.13.Final.jar:]
          at org.gatein.portal.installer.PortalSetupFilter.doFilter(PortalSetupFilter.java:64) [exo.portal.component.portal-3.6.0.Beta02.jar:3.6.0.Beta02]
          at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:]
          at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:]
          at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) [jbossweb-7.0.13.Final.jar:]
          at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161) [jbossweb-7.0.13.Final.jar:]
          at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:397) [jbossweb-7.0.13.Final.jar:]
          at org.gatein.sso.integration.SSODelegateValve.invoke(SSODelegateValve.java:159) [sso-integration-1.3.3.CR03.jar:1.3.3.CR03]
          at org.gatein.portal.security.jboss.PortalClusteredSSOSupportValve.invoke(PortalClusteredSSOSupportValve.java:88) [exo.portal.component.web.security-jboss-3.6.0.Beta02.jar:3.6.0.Beta02]
          at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:153) [jboss-as-web-7.1.1.Final.jar:7.1.1.Final]
          at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:155) [jbossweb-7.0.13.Final.jar:]
          at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [jbossweb-7.0.13.Final.jar:]
          at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [jbossweb-7.0.13.Final.jar:]
          at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:368) [jbossweb-7.0.13.Final.jar:]
          at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [jbossweb-7.0.13.Final.jar:]
          at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:671) [jbossweb-7.0.13.Final.jar:]
          at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:930) [jbossweb-7.0.13.Final.jar:]
          at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_33]
Caused by: java.lang.NullPointerException
          at org.exoplatform.portal.application.localization.LocalizationFilter.doFilter(LocalizationFilter.java:140) [exo.portal.webui.portal-3.6.0.Beta02.jar:3.6.0.Beta02]
          ... 23 more

And then it hangs after this logging line:
14:46:54,279 INFO [org.picketlink.idm.impl.tree.IDMTreeCacheImpl] (http--127.0.0.1-8080-1) StaleNodesCleaner started successfully with delay 120000

It's odd though, I tried same thing with RichFaces 4 Simple Portlet from the PortletBridge, and does not give an issue.

Thanks for any help.
Joe
Actions
6. Re: Cannot start portal if restart it without logging off - in GateIn-3.6.0.Beta02_jbossas7

rutlucas Jun 3, 2013 3:56 AM (in response to jpadula35)

Hi Joe,

This error is strange. The NPE is happening retrieving the locale configuration in LocalizationFilter.
Taking a look into the code, this error shouldn't happen if you have a proper locale and all configuration files are placed as expected (so, it's strange that you can face it in a fresh install).

So, my guess is that is a side error where the root cause is hidden in the log for some reason.

Two points:
- Is it possible to attach an example of your portlet (simplified version) that we can run to reproduce error ?
- When you say that you need to add your datasources, I understand that are DS that your app needs, you are not overwritten the default datasource of portal (for a fresh install), am I right ?.

Thanks,
Lucas
Actions
7. Re: Cannot start portal if restart it without logging off - in GateIn-3.6.0.Beta02_jbossas7

jpadula35 Jun 3, 2013 2:40 PM (in response to rutlucas)

Hi Lucas,
I am working on trimming a portlet to send you that you can reproduce the problem.

Regarding the datasources, you are correct, I did not overright the existing data sources, just added ours.

Joe
Actions
8. Re: Cannot start portal if restart it without logging off - in GateIn-3.6.0.Beta02_jbossas7

jpadula35 Jun 4, 2013 10:52 PM (in response to jpadula35)
Hi Lucas,
I've attached a stripped down version of the portlet. It took a while because if I removed too much stuff I couldn't duplicate the problem. I've removed the database dependencies so no changes are necessary to standalone.xml.
The LocalizationFilter exception is repeatable each time you launch (if you are logged in as root, and have the portlet displayed already), but the hanging may not happen every single time, but it usually happens.

I've also attached the server.log file.

To reproduce the error, add the portlet to the application registry, leave the browser open with the portlet displayed. Then stop the portal,
then launch it again (standalone.bat).

If you can shed any light on this I would really appreciate it.
Regards,
Joe

boot.log.zip 2.0 KB

server.log.zip 16.6 KB

portlet-session-management.war 12.8 MB
Actions
9. Re: Cannot start portal if restart it without logging off - in GateIn-3.6.0.Beta02_jbossas7

rutlucas Jun 5, 2013 4:43 AM (in response to jpadula35)

Thanks Joe.

Can you please add the TestSessionBean.java file to take a look into this one without use a decompiler ?

Regards,
Lucas
Actions
10. Re: Cannot start portal if restart it without logging off - in GateIn-3.6.0.Beta02_jbossas7

rutlucas Jun 5, 2013 7:37 AM (in response to jpadula35)

Hello Joe,

I can play with your example and to delimit your issue.
The problematic component is the <a4j:poll> active in your browser when you shutdown and restart the server without refreshing session / browser.
Then ajax calls from <a4j:poll> is causing the strange behaviour, trying to get a portlet before the portal has been fully deployed.

I could experiment a similar behaviour using the showcase example app:
https://github.com/portletbridge/portletbridge/tree/master/examples/richfaces-showcase

Well, I'm not sure if this is can be a bug or not, I'm going to open a discussion with Ken about it.

In the mean while, I would recommend to add some control in your <a4j:poll> object.

Well, may be this can be an enhancement for richfaces project, in order to offer some kind of listener of a client object (like a4j:poll) when servers side is not accessible.

Hope this comments helps to debug your issue.

Regards,
Lucas
Actions
11. Re: Cannot start portal if restart it without logging off - in GateIn-3.6.0.Beta02_jbossas7

jpadula35 Jun 5, 2013 8:02 AM (in response to rutlucas)
Thanks for looking at this Lucas. I've added the source file for completeness (just stubs).

You know I had a felling the a4j:poll was causing the problem, because when I commented it out, no problem. But I thought it was the methods it was calling and then could not reproduce the problem any longer so started all over.

I'm wondering why this has become an issue now in 3.6 though as the portlet has used a4j:poll in GateIn 3.1, and 3.5.

The only other fhing I forgot to double check with Ken was if it was OK to use PortletBridge 3.2.0.Alpha1 (bundled in ur portlets) in Gatin3.6.0..Beta02. I noticed that is comes packaged with PB 3.2.0.Final.

Can you suggest any way to put some control in the a4j:poll element on the page? Is it possible to have it not poll if the portlet is not fully deployed yet?

Regards,
Joe

TestSessionBean.java.zip 440 bytes
Actions
12. Re: Cannot start portal if restart it without logging off - in GateIn-3.6.0.Beta02_jbossas7

rutlucas Jun 5, 2013 10:51 AM (in response to jpadula35)

Hi Joe,

We have been able to reproduce the issue.

It's part of a known JIRA reported before, I've uploaded a similar example like yours:

https://issues.jboss.org/browse/GTNPORTAL-2917

The main issue is to prevent JBossWeb to not receive calls until gatein is fully started.

In this JIRA team will track this issue.

Thanks for your tests.
Lucas
Actions
13. Re: Cannot start portal if restart it without logging off - in GateIn-3.6.0.Beta02_jbossas7

jpadula35 Jun 5, 2013 3:10 PM (in response to rutlucas)

Lucas,
Thanks so much for your help.
Joe
Actions

Go to original post