Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-2338

When using a JDBC object store, the RecoveryManager service stop can occur after the datasource is already stopped

    Details

    • Steps to Reproduce:
      Hide

      Put a breakpoint in ArjunaRecoveryManagerService::stop
      Stop the server with a :reload
      Observe: 12:42:42,745 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-1) JBAS010409: Unbound data source [java:jboss/datasources/jdbc-store]

      This shows the datasource is being undeployed before the recovery manager

      Show
      Put a breakpoint in ArjunaRecoveryManagerService::stop Stop the server with a :reload Observe: 12:42:42,745 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-1) JBAS010409: Unbound data source [java:jboss/datasources/jdbc-store] This shows the datasource is being undeployed before the recovery manager

      Description

      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

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  maeste Stefano Maestri
                  Reporter:
                  tomjenkinson Thomas Jenkinson
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  2 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: