[RHDM-403] ERRORs when running standalone decision central - JBoss Issue Tracker

XML

Word

Printable

Details

Type: Bug
Status: Closed (View Workflow)
Priority: Blocker
Resolution: Done
Affects Version/s: 7.0.0.GA
Fix Version/s: 7.0.1.GA
Component/s: Build and Assembly, Configuration, Decision Central
Labels:
- gss
- support

Environment:

Hide

Starting the Decision Central standalone package with the following command:

java -jar \

-Dorg.kie.server.user=controllerUser \

-Dorg.kie.server.pwd=controllerUser1234\; \

rhdm-7.0.0.GA-decision-central-standalone.jar \

-s rhdm7-config.yaml

and the following content in rhdm7-config.yaml:

swarm:

  logging:

    console-handlers:

      CONSOLE:

        level: INFO

        named-formatter: COLOR_PATTERN

    pattern-formatters:

      PATTERN:

        pattern: "%d{yyyy-MM-dd HH:mm:ss,SSS} %-5p [%c] (%t) %s%e%n"

      COLOR_PATTERN:

        pattern: "%K{level}%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%e%n"

    periodic-rotating-file-handlers:

      FILE:

        file:

          path: server.log

        suffix: .yyyy-MM-dd

        named-formatter: PATTERN

    root-logger:

      handlers:

      - CONSOLE

      - FILE

  management:

    security-realms:

      ApplicationRealm:

        local-authentication:

          default-user: local

          allowed-users: local

          skip-group-loading: true

        properties-authentication:

          path: /data/jboss/rhdm700/standalone/configuration/application-users.properties

          plain-text: false

        properties-authorization:

          path: /data/jboss/rhdm700/standalone/configuration/application-roles.properties

Show

Starting the Decision Central standalone package with the following command: java -jar \ -Dorg.kie.server.user=controllerUser \ -Dorg.kie.server.pwd=controllerUser1234\; \ rhdm-7.0.0.GA-decision-central-standalone.jar \ -s rhdm7-config.yaml and the following content in rhdm7-config.yaml : swarm: logging: console-handlers: CONSOLE: level: INFO named-formatter: COLOR_PATTERN pattern-formatters: PATTERN: pattern: "%d{yyyy-MM-dd HH:mm:ss,SSS} %-5p [%c] (%t) %s%e%n" COLOR_PATTERN: pattern: "%K{level}%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%e%n" periodic-rotating-file-handlers: FILE: file: path: server.log suffix: .yyyy-MM-dd named-formatter: PATTERN root-logger: handlers: - CONSOLE - FILE management: security-realms: ApplicationRealm: local-authentication: default-user: local allowed-users: local skip-group-loading: true properties-authentication: path: /data/jboss/rhdm700/standalone/configuration/application-users.properties plain-text: false properties-authorization: path: /data/jboss/rhdm700/standalone/configuration/application-roles.properties

Target Release:

7.1.0.GA

Description

This error is thrown during server startup:

11:57:49,319 ERROR [org.dashbuilder.dataset.DataSetDefRegistryImpl] (MSC service thread 1-5) Data set definition read error: jbpmExecutionErrorList.dset: java.lang.IllegalArgumentException: Provider not supported: REMOTE

	at org.dashbuilder.dataset.json.DataSetDefJSONMarshaller.readProviderType(DataSetDefJSONMarshaller.java:112)

	at org.dashbuilder.dataset.json.DataSetDefJSONMarshaller.fromJson(DataSetDefJSONMarshaller.java:84)

	at org.dashbuilder.dataset.DataSetDefRegistryCDI$2.visitFile(DataSetDefRegistryCDI.java:284)

	at org.dashbuilder.dataset.DataSetDefRegistryCDI$2.visitFile(DataSetDefRegistryCDI.java:272)

	at org.uberfire.java.nio.file.FileTreeWalker.walk(FileTreeWalker.java:71)

	at org.uberfire.java.nio.file.FileTreeWalker.walk(FileTreeWalker.java:96)

	at org.uberfire.java.nio.file.FileTreeWalker.walk(FileTreeWalker.java:96)

	at org.uberfire.java.nio.file.FileTreeWalker.walk(FileTreeWalker.java:48)

	at org.uberfire.java.nio.file.Files.walkFileTree(Files.java:1031)

	at org.uberfire.java.nio.file.Files.walkFileTree(Files.java:1052)

	at org.dashbuilder.dataset.DataSetDefRegistryCDI.listDataSetDefs(DataSetDefRegistryCDI.java:270)

	at org.dashbuilder.dataset.DataSetDefRegistryCDI.registerDataSetDefs(DataSetDefRegistryCDI.java:158)

	at org.dashbuilder.dataset.DataSetDefRegistryCDI.init(DataSetDefRegistryCDI.java:117)

and these WARN/ERROR messages show up every 30 seconds:

12:07:19,435 WARN  [org.kie.workbench.common.screens.datasource.management.backend.DataSourceManagementBootstrap] (pool-14-thread-1) Initialize deployments task finished with errors: It was not possible to open connection to server. java.net.ConnectException: WFLYPRT0053: Could not connect to http-remoting://127.0.0.1:9990. The connection failed

12:07:19,435 WARN  [org.kie.workbench.common.screens.datasource.management.backend.DataSourceManagementBootstrap] (pool-14-thread-1) Startup drivers and datasources initialization will be retried again in: 30000 MILLISECONDS(1 attempts left)

12:07:49,446 ERROR [org.kie.workbench.common.screens.datasource.management.backend.integration.wildfly.WildflyBaseClient] (pool-14-thread-1) It was not possible to open connection to Wildfly/EAP server.: java.io.IOException: java.net.ConnectException: WFLYPRT0053: Could not connect to http-remoting://127.0.0.1:9990. The connection failed

	at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:149)

	at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:80)

	at org.kie.workbench.common.screens.datasource.management.backend.integration.wildfly.WildflyBaseClient.testConnection(WildflyBaseClient.java:158)

	at org.kie.workbench.common.screens.datasource.management.backend.integration.wildfly.WildflyBaseClient.testConnection(WildflyBaseClient.java:147)

	at org.kie.workbench.common.screens.datasource.management.backend.core.wildfly.WildflyDriverProvider.hasStarted(WildflyDriverProvider.java:210)

	at org.kie.workbench.common.screens.datasource.management.backend.core.wildfly.WildflyDriverProvider$Proxy$_$$_WeldClientProxy.hasStarted(Unknown Source)

	at org.kie.workbench.common.screens.datasource.management.backend.core.impl.DataSourceRuntimeManagerImpl.hasStarted(DataSourceRuntimeManagerImpl.java:199)

	at org.kie.workbench.common.screens.datasource.management.backend.core.impl.DataSourceRuntimeManagerImpl$Proxy$_$$_WeldClientProxy.hasStarted(Unknown Source)

	at org.kie.workbench.common.screens.datasource.management.backend.DataSourceManagementBootstrap.lambda$getInitializeDeploymentsTask$0(DataSourceManagementBootstrap.java:172)

	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)

	at java.util.concurrent.FutureTask.run(FutureTask.java:266)

	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)

	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)

	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)

	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)

	at java.lang.Thread.run(Thread.java:748)

Caused by: java.net.ConnectException: WFLYPRT0053: Could not connect to http-remoting://127.0.0.1:9990. The connection failed

Gliffy Diagrams

Attachments

Activity

People

Assignee:

Marek Novotny

Reporter:

Martin Weiler

Votes:

0 Vote for this issue

Watchers:

4 Start watching this issue

Dates

Created:

20/Feb/18 6:07 AM

Updated:

10/Sep/18 11:53 AM

Resolved:

10/Sep/18 11:53 AM