[
https://issues.jboss.org/browse/WFLY-2338?page=com.atlassian.jira.plugin....
]
RH Bugzilla Integration commented on WFLY-2338:
-----------------------------------------------
Ondrej Chaloupka <ochaloup(a)redhat.com> made a comment on [bug
1020881|https://bugzilla.redhat.com/show_bug.cgi?id=1020881]
I found out that this happens not only with reload but as well when server is stopping.
Which means that when the JDBC object store is configured and you stopped the server the
server stucks and it has to be killed by 'kill -9' or similar way.
This problem seems to me quite urgent. I can see that the issue is already solved for
Wildfly then please check the process of the stopping the server as well.
When using a JDBC object store, the RecoveryManager service stop can
occur after the datasource is already stopped
------------------------------------------------------------------------------------------------------------------
Key: WFLY-2338
URL:
https://issues.jboss.org/browse/WFLY-2338
Project: WildFly
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Transactions
Reporter: Tom Jenkinson
Assignee: Stefano Maestri
Attachments: 0001-patching-servicename-for-ds-dependency.patch
It should be the cause of
https://bugzilla.redhat.com/show_bug.cgi?id=1020881
It has the effects described in the BZ, i.e. can cause warnings or can entirely block the
application server from stopping
--
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