Datasource initialization error

Hi all,
Im using jBPM running in Domain mode. Both of my Slaves are NOT connected to internet. I have setup in my host.xml datasource relevant properties for the JVM running the jbpm-console.war

<property name="datasource.management.DataSourceProvider" value="WildflyDataSourceProvider" boot-time="false"/>
<property name="datasource.management.DriverProvider" value="WildflyDriverProvider" boot-time="false"/>
<property name="datasource.management.wildfly.host" value="..." boot-time="false"/>
<property name="datasource.management.wildfly.port" value="..." boot-time="false"/>
<property name="datasource.management.wildfly.admin" value="admin" boot-time="false"/>
<property name="datasource.management.wildfly.password" value="..." boot-time="false"/>
<property name="datasource.management.wildfly.realm" value="ManagementRealm" boot-time="false"/>
<property name="datasource.management.wildfly.profile" value="full" boot-time="false"/>
<property name="datasource.management.wildfly.serverGroup" value="jbpm-server-group" boot-time="false"/>
<property name="datasource.management.DefChangeHandler" value="DomainModeChangeHandler" boot-time="false"/>
<property name="datasource.management.disableDefaultDrivers" value="true" boot-time="false" />
<property name="jboss.as.management.blocking.timeout" value="1200"/>

Since I have set the datasource.management.disableDefaultDrivers property to "true" I would expect no initialization to happen. But when I start my JVM I see at some point in the server.log

2019-10-22 16:28:17,744 INFO [org.uberfire.ext.metadata.io.BatchIndex] (Thread-118) Completed indexing of system/datasets/master
2019-10-22 16:28:44,746 INFO [org.kie.workbench.common.screens.datasource.management.util.ServiceUtil] (pool-10-thread-1) Getting reference to managed bean: WildflyDataSourceProvider
2019-10-22 16:28:44,753 INFO [org.kie.workbench.common.screens.datasource.management.util.ServiceUtil] (pool-10-thread-1) Getting reference to managed bean: WildflyDriverProvider
2019-10-22 16:28:44,888 WARN *[org.kie.workbench.common.screens.datasource.management.backend.DataSourceManagementBootstrap] (pool-10-thread-1) Initialize deployments task finished with errors: *operation execution failed. :WFLYCTL0379: System boot is in process; execution of remote management operations is not currently available
2019-10-22 16:28:44,889 WARN [org.kie.workbench.common.screens.datasource.management.backend.DataSourceManagementBootstrap] (pool-10-thread-1) Startup drivers and datasources initialization will be retried again in: 30000 MILLISECONDS(19 attempts left)
...
up to
2019-10-22 16:36:45,389 WARN [org.kie.workbench.common.screens.datasource.management.backend.DataSourceManagementBootstrap] (pool-10-thread-1) Startup drivers and datasources initialization will be retried again in: 30000 MILLISECONDS(3 attempts left)
2019-10-22 16:37:12,380 WARN [org.kie.server.common.KeyStoreHelperUtil] (MSC service thread 1-6) Unable to load key store. Using password from configuration
2019-10-22 16:37:12,596 INFO [io.undertow.websockets.jsr] (ServerService Thread Pool – 181) UT026003: Adding annotated server endpoint class org.kie.server.controller.websocket.notification.WebSocketKieServerControllerNotification for path /websocket/controller/notification
...
Usually it makes 17 attempts of 30 seconds interval between them, meaning 510 seconds of delay in the startup procedure.
Before I set the property jboss.as.management.blocking.timeout to 1200, the jbpm-console deployment was failing to start due to these errors. After increasing blocking timeout jbpm-console deployment starts normally (after almost 9 minutes...), jBPM UI starts functioning normally and KIE servers that are configured to connect to it are successfully connected, get their container list, create them and start them. If I increase the log level I cannot see any errors, just INFO messages that are not so indicative to what is happening.
(there were connection errors with http-remoting to master before I set host, port, admin etc. properties, but no errors now, just the attempts message).

Does anyone know why is that happening and how we can eliminate it?