[jboss-jira] [JBoss JIRA] (WFLY-4274) Add diagnostic logging to BaseComponent.waitForComponentStart()

[James Livingston (JIRA)]

     [ https://issues.jboss.org/browse/WFLY-4274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

James Livingston updated WFLY-4274:
-----------------------------------
    Description: When trying to diagnose the cause of issues like WFLY-2692 or WFLY-917, it would be useful to know which component is stalled in BaseComponent.waitForComponentStart(). Adding trace-level logging of the components starting and finishing waiting would be useful.  (was: When trying to diagnose the cause of issues like WFLT-2692 or WFLY-917, it would be useful to know which component is stalled in BaseComponent.waitForComponentStart(). Adding trace-level logging of the components starting and finishing waiting would be useful.)


> Add diagnostic logging to BaseComponent.waitForComponentStart()
> ---------------------------------------------------------------
>
>                 Key: WFLY-4274
>                 URL: https://issues.jboss.org/browse/WFLY-4274
>             Project: WildFly
>          Issue Type: Enhancement
>          Components: EE
>    Affects Versions: 9.0.0.Alpha1
>            Reporter: James Livingston
>            Assignee: David Lloyd
>
> When trying to diagnose the cause of issues like WFLY-2692 or WFLY-917, it would be useful to know which component is stalled in BaseComponent.waitForComponentStart(). Adding trace-level logging of the components starting and finishing waiting would be useful.



--
This message was sent by Atlassian JIRA
(v6.3.11#6341)