Description of problem: I've recently tried to name a portal extension project which started with the lowercase letter 'u' and it failed to deploy the extension with the following exception: java.lang.IllegalStateException: No pre init tasks can be added to the portal container 'portal', because it has already been initialized. It turns out that reason failure was because the 'starter' webapp had already been initialized prior to the deployment of the portal extension. By renaming the project to start with an 'a' or 'U' the problem disappears and in the logs we can see that indeed the extension is deployed prior to the 'starter' webapp. We should ensure that starter webapp is always started last. Version-Release number of selected component (if applicable): EPP 5.2 How reproducible: always Steps to Reproduce: 1. rename docs/examples/portal/gatein-sample-extension.ear into for instance ugatein-sample-extension.ear; 2. deploy ugatein-sample-extension.ear, together with gatein-sample-portal-ds.xml and make sure that gatein-ds.xml is changed by adding '_portal' to the jndi names. 3. start the server Actual results: The following exception is logged: java.lang.IllegalStateException: No pre init tasks can be added to the portal container 'portal', because it has already been initialized. Expected results: No exception is logged and application is properly deployed. Additional info:
Need to mention in doc.
This issue was closed as CANTFIX. What do I need to mention? This should get its own docs bug if a change to documentation is required. What do you want to say in the release notes? Is this a work around?
Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: NEEDINFO: What needs to be mentioned in the doc specifically? CAUSE: CONSEQUENCE: FIX: RESULT:
Technical note updated. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. Diffed Contents: @@ -1,9 +1,9 @@ NEEDINFO: What needs to be mentioned in the doc specifically? -CAUSE: +CAUSE: If portal extension project is named with lowercase letter -CONSEQUENCE: +CONSEQUENCE: it is poossible that it starts later then necessary services, and throws java.lang.IllegalStateException -FIX: +FIX: Use uppercase first letter. -RESULT:+RESULT: We should ensure that starter webapp is always started last.
Technical note updated. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. Diffed Contents: @@ -1,5 +1,3 @@ -NEEDINFO: What needs to be mentioned in the doc specifically? - CAUSE: If portal extension project is named with lowercase letter CONSEQUENCE: it is poossible that it starts later then necessary services, and throws java.lang.IllegalStateException
Technical note updated. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. Diffed Contents: @@ -1,7 +1 @@ -CAUSE: If portal extension project is named with lowercase letter +If portal extension project is named with lowercase letter, it is possible that it starts later then necessary services, and throws java.lang.IllegalStateException. To workaround this issue, always use an uppercase first letter. This current functionality will be improved in a future release.- -CONSEQUENCE: it is poossible that it starts later then necessary services, and throws java.lang.IllegalStateException - -FIX: Use uppercase first letter. - -RESULT: We should ensure that starter webapp is always started last.