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

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • 9.0.0.Final
    • None
    • Transactions
    • None
    • 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

      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

        1. 0001-patching-servicename-for-ds-dependency.patch
          1 kB

              smaestri@redhat.com Stefano Maestri
              thjenkin@redhat.com Tom Jenkinson
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: