[
http://jira.nuxeo.org/browse/NXP-4618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=68101#action_68101
]
Bogdan Stefanescu commented on NXP-4618:
----------------------------------------
Can be fixed by dispatching the framework started event in a different thread.
This means nuxeo starting-up initialization will be done in parallel - and may
produce errors if you do request to nuxeo web application before the framework
started thread finish it's job (since nuxeo will not be fully initialized even
in you see the startup message on the console)
> Catalina should start and an error shown in the log if a framework event
> listener wait indefinitely
> ---------------------------------------------------------------------------------------------------
>
> Key: NXP-4618
> URL: http://jira.nuxeo.org/browse/NXP-4618
> Project: Nuxeo Enterprise Platform
> Issue Type: Bug
> Affects Versions: 5.3 GA
> Reporter: Alexandre Russel
> Attachments: twilddle_1.html
>
>
> If a framework listener freeze (ie: waiting for a DB connection), then
> neither Coyote nor Nuxeo is started even if there is the message:
> ======================================================================
> = Nuxeo EP Started
> ======================================================================
> = Component Loading Status: Pending: 0 / Unstarted: 0 / Total: 261
> ======================================================================
> in the log.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.nuxeo.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
ECM-tickets mailing list
[email protected]
http://lists.nuxeo.com/mailman/listinfo/ecm-tickets
