[
https://issues.apache.org/jira/browse/HDDS-3978?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
runzhiwang updated HDDS-3978:
-
Description:
We met dead lock related to log4j, the jstack information has been attached.
For the follow
[
https://issues.apache.org/jira/browse/HDDS-3978?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
runzhiwang updated HDDS-3978:
-
Description:
We met dead lock related to log4j, the jstack information has been attached.
For the follow
[
https://issues.apache.org/jira/browse/HDDS-3978?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
runzhiwang updated HDDS-3978:
-
Description: We met dead lock related to log4j, the jstack information has
been attached. (was: We met d
[
https://issues.apache.org/jira/browse/HDDS-3978?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
runzhiwang updated HDDS-3978:
-
Description: We met dead lock related to log4j, the jstack information has
been attached.
> Switch log4j
[
https://issues.apache.org/jira/browse/HDDS-3978?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
runzhiwang updated HDDS-3978:
-
Attachment: jstack-deadlock-log.txt
> Switch log4j to log4j2 to avoid deadlock
> -