[JBoss JIRA] (GTNPORTAL-2675) Error during shutdown: "No pre init tasks can be added to the portal container"
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-2675?page=com.atlassian.jira.pl... ]
RH Bugzilla Integration commented on GTNPORTAL-2675:
----------------------------------------------------
theute(a)redhat.com changed the Status of [bug 878036|https://bugzilla.redhat.com/show_bug.cgi?id=878036] from VERIFIED to CLOSED
> Error during shutdown: "No pre init tasks can be added to the portal container"
> -------------------------------------------------------------------------------
>
> Key: GTNPORTAL-2675
> URL: https://issues.jboss.org/browse/GTNPORTAL-2675
> Project: GateIn Portal
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: WSRP integration
> Reporter: Matt Wringe
> Assignee: Matt Wringe
> Fix For: 3.5.0.Final
>
>
> When shutting down the portal, the following error message is thrown:
> 15:17:15,431 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/gatein-wsrp-integration]] Exception sending context destroyed event to listener instance of class org.exoplatform.container.web.PortalContainerConfigOwner: java.lang.IllegalStateException: No pre init tasks can be added to the portal container 'portal', because it has already been initialized. Check the webapp 'gatein-wsrp-integration'
> at org.exoplatform.container.RootContainer$PortalContainerPreInitTask.onAlreadyExists(RootContainer.java:1317) [exo.kernel.container-2.4.0-CR1.jar:2.4.0-CR1]
> at org.exoplatform.container.RootContainer.addInitTask(RootContainer.java:1108) [exo.kernel.container-2.4.0-CR1.jar:2.4.0-CR1]
> at org.exoplatform.container.PortalContainer.addInitTask(PortalContainer.java:464) [exo.kernel.container-2.4.0-CR1.jar:2.4.0-CR1]
> at org.exoplatform.container.PortalContainer.addInitTask(PortalContainer.java:438) [exo.kernel.container-2.4.0-CR1.jar:2.4.0-CR1]
> at org.exoplatform.container.web.PortalContainerConfigOwner.contextDestroyed(PortalContainerConfigOwner.java:56) [exo.kernel.container-2.4.0-CR1.jar:2.4.0-CR1]
> at org.apache.catalina.core.StandardContext.listenerStop(StandardContext.java:3489) [jbossweb-7.0.13.Final.jar:]
> at org.apache.catalina.core.StandardContext.stop(StandardContext.java:3999) [jbossweb-7.0.13.Final.jar:]
> at org.jboss.as.web.deployment.WebDeploymentService.stop(WebDeploymentService.java:108) [jboss-as-web-7.1.1.Final.jar:7.1.1.Final]
> at org.jboss.msc.service.ServiceControllerImpl$StopTask.stopService(ServiceControllerImpl.java:1911)
> at org.jboss.msc.service.ServiceControllerImpl$StopTask.run(ServiceControllerImpl.java:1874)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.7.0_06-icedtea]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.7.0_06-icedtea]
> at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_06-icedtea]
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 11 months
[JBoss JIRA] (GTNPORTAL-2771) Ensure that generated rememberme token is really unique
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-2771?page=com.atlassian.jira.pl... ]
RH Bugzilla Integration commented on GTNPORTAL-2771:
----------------------------------------------------
theute(a)redhat.com changed the Status of [bug 887972|https://bugzilla.redhat.com/show_bug.cgi?id=887972] from VERIFIED to CLOSED
> Ensure that generated rememberme token is really unique
> -------------------------------------------------------
>
> Key: GTNPORTAL-2771
> URL: https://issues.jboss.org/browse/GTNPORTAL-2771
> Project: GateIn Portal
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Reporter: Marek Posolda
> Assignee: Marek Posolda
> Labels: EPP6.0-Test-Dev
> Fix For: 3.6.0.Beta01
>
>
> Currently we are generating random rememberme tokens based on random int number (random.nextInt()). In systems with millions or many thousands login, this discriminator is not enough.
> We should improve it and fix it either by:
> 1) Ensure that generated token is really unique. In system with many logins the random number may not be unique enough, so we need to add other info (like System.currentTimeMillis() or counter or both...)
> 2) In case that token already exists, we should generate other one instead of refresh the current one.
> Maybe combination of both approaches would be best :-)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 11 months