[JBoss JIRA] (WFLY-13382) Wildfly-19.0.0.Final unable to run services
by Paul Ferraro (Jira)
[ https://issues.redhat.com/browse/WFLY-13382?page=com.atlassian.jira.plugi... ]
Paul Ferraro commented on WFLY-13382:
-------------------------------------
[~sachinsinghai1008] There is not a bug.
This is a support question, for which you should create a forum entry:
https://groups.google.com/forum/#!forum/wildfly
{quote}I have done the version upgrade for sub-systems in standalone-full and other jar version which is upgraded.{quote}
Make sure to elaborate on what exactly you mean by "... and other jar version which is upgrade", as I suspect that is where things went wrong.
> Wildfly-19.0.0.Final unable to run services
> -------------------------------------------
>
> Key: WFLY-13382
> URL: https://issues.redhat.com/browse/WFLY-13382
> Project: WildFly
> Issue Type: Bug
> Affects Versions: 19.0.0.Final
> Reporter: sachin singhai
> Assignee: Paul Ferraro
> Priority: Major
>
> I am updating my application to wildfly-19.0.0.Final from Wildfly-18.0.1.Final version.
> And this update is unable to run services of my application.
> I have done the version upgrade for sub-systems in standalone-full and other jar version which is upgraded. Due to security concerns I am unable to attach complete server.log file
> I have checked the server.log file and found that it is failing for below:
> 1) 2020-04-14 12:34:28,648 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 51) WFLYCTL0013: Operation ("add") failed - address: ([("subsystem" => "pojo")]): javax.xml.stream.FactoryConfigurationError: Provider com.ctc.wstx.stax.WstxInputFactory not found
> 2) 2020-04-14 12:34:28,658 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 55) WFLYCTL0013: Operation ("add") failed - address: ([("subsystem" => "sar")]): javax.xml.stream.FactoryConfigurationError: Provider com.ctc.wstx.stax.WstxInputFactory not found
> at java.xml/javax.xml.stream.FactoryFinder.newInstance(FactoryFinder.java:196)
> 3) 2020-04-14 12:34:29,052 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 37) WFLYCTL0013: Operation ("add") failed - address: ([("subsystem" => "ee")]): javax.xml.stream.FactoryConfigurationError: Provider com.ctc.wstx.stax.WstxInputFactory not found
> at java.xml/javax.xml.stream.FactoryFinder.newInstance(FactoryFinder.java:196)
>
> 4) 2020-04-14 12:34:29,504 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 49) WFLYCTL0013: Operation ("add") failed - address: ([("subsystem" => "messaging-activemq")]): javax.xml.stream.FactoryConfigurationError: Provider com.ctc.wstx.stax.WstxInputFactory not found
> 5) 2020-04-14 12:34:31,354 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 59) WFLYCTL0013: Operation ("add") failed - address: ([("subsystem" => "webservices")]): javax.xml.stream.FactoryConfigurationError: Provider com.ctc.wstx.stax.WstxInputFactory not found
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years
[JBoss JIRA] (WFLY-13382) Wildfly-19.0.0.Final unable to run services
by Paul Ferraro (Jira)
[ https://issues.redhat.com/browse/WFLY-13382?page=com.atlassian.jira.plugi... ]
Paul Ferraro closed WFLY-13382.
-------------------------------
Resolution: Rejected
> Wildfly-19.0.0.Final unable to run services
> -------------------------------------------
>
> Key: WFLY-13382
> URL: https://issues.redhat.com/browse/WFLY-13382
> Project: WildFly
> Issue Type: Bug
> Affects Versions: 19.0.0.Final
> Reporter: sachin singhai
> Assignee: Paul Ferraro
> Priority: Major
>
> I am updating my application to wildfly-19.0.0.Final from Wildfly-18.0.1.Final version.
> And this update is unable to run services of my application.
> I have done the version upgrade for sub-systems in standalone-full and other jar version which is upgraded. Due to security concerns I am unable to attach complete server.log file
> I have checked the server.log file and found that it is failing for below:
> 1) 2020-04-14 12:34:28,648 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 51) WFLYCTL0013: Operation ("add") failed - address: ([("subsystem" => "pojo")]): javax.xml.stream.FactoryConfigurationError: Provider com.ctc.wstx.stax.WstxInputFactory not found
> 2) 2020-04-14 12:34:28,658 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 55) WFLYCTL0013: Operation ("add") failed - address: ([("subsystem" => "sar")]): javax.xml.stream.FactoryConfigurationError: Provider com.ctc.wstx.stax.WstxInputFactory not found
> at java.xml/javax.xml.stream.FactoryFinder.newInstance(FactoryFinder.java:196)
> 3) 2020-04-14 12:34:29,052 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 37) WFLYCTL0013: Operation ("add") failed - address: ([("subsystem" => "ee")]): javax.xml.stream.FactoryConfigurationError: Provider com.ctc.wstx.stax.WstxInputFactory not found
> at java.xml/javax.xml.stream.FactoryFinder.newInstance(FactoryFinder.java:196)
>
> 4) 2020-04-14 12:34:29,504 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 49) WFLYCTL0013: Operation ("add") failed - address: ([("subsystem" => "messaging-activemq")]): javax.xml.stream.FactoryConfigurationError: Provider com.ctc.wstx.stax.WstxInputFactory not found
> 5) 2020-04-14 12:34:31,354 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 59) WFLYCTL0013: Operation ("add") failed - address: ([("subsystem" => "webservices")]): javax.xml.stream.FactoryConfigurationError: Provider com.ctc.wstx.stax.WstxInputFactory not found
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years
[JBoss JIRA] (WFLY-13382) Wildfly-19.0.0.Final unable to run services
by Paul Ferraro (Jira)
[ https://issues.redhat.com/browse/WFLY-13382?page=com.atlassian.jira.plugi... ]
Paul Ferraro updated WFLY-13382:
--------------------------------
Component/s: (was: Clustering)
> Wildfly-19.0.0.Final unable to run services
> -------------------------------------------
>
> Key: WFLY-13382
> URL: https://issues.redhat.com/browse/WFLY-13382
> Project: WildFly
> Issue Type: Bug
> Affects Versions: 19.0.0.Final
> Reporter: sachin singhai
> Assignee: Paul Ferraro
> Priority: Major
>
> I am updating my application to wildfly-19.0.0.Final from Wildfly-18.0.1.Final version.
> And this update is unable to run services of my application.
> I have done the version upgrade for sub-systems in standalone-full and other jar version which is upgraded. Due to security concerns I am unable to attach complete server.log file
> I have checked the server.log file and found that it is failing for below:
> 1) 2020-04-14 12:34:28,648 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 51) WFLYCTL0013: Operation ("add") failed - address: ([("subsystem" => "pojo")]): javax.xml.stream.FactoryConfigurationError: Provider com.ctc.wstx.stax.WstxInputFactory not found
> 2) 2020-04-14 12:34:28,658 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 55) WFLYCTL0013: Operation ("add") failed - address: ([("subsystem" => "sar")]): javax.xml.stream.FactoryConfigurationError: Provider com.ctc.wstx.stax.WstxInputFactory not found
> at java.xml/javax.xml.stream.FactoryFinder.newInstance(FactoryFinder.java:196)
> 3) 2020-04-14 12:34:29,052 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 37) WFLYCTL0013: Operation ("add") failed - address: ([("subsystem" => "ee")]): javax.xml.stream.FactoryConfigurationError: Provider com.ctc.wstx.stax.WstxInputFactory not found
> at java.xml/javax.xml.stream.FactoryFinder.newInstance(FactoryFinder.java:196)
>
> 4) 2020-04-14 12:34:29,504 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 49) WFLYCTL0013: Operation ("add") failed - address: ([("subsystem" => "messaging-activemq")]): javax.xml.stream.FactoryConfigurationError: Provider com.ctc.wstx.stax.WstxInputFactory not found
> 5) 2020-04-14 12:34:31,354 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 59) WFLYCTL0013: Operation ("add") failed - address: ([("subsystem" => "webservices")]): javax.xml.stream.FactoryConfigurationError: Provider com.ctc.wstx.stax.WstxInputFactory not found
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years
[JBoss JIRA] (DROOLS-5061) DMN strongly typed codegen DMNContext and DMNResult
by Matteo Mortari (Jira)
[ https://issues.redhat.com/browse/DROOLS-5061?page=com.atlassian.jira.plug... ]
Matteo Mortari updated DROOLS-5061:
-----------------------------------
Summary: DMN strongly typed codegen DMNContext and DMNResult (was: DMN codegen DMNContext and DMNResult)
> DMN strongly typed codegen DMNContext and DMNResult
> ---------------------------------------------------
>
> Key: DROOLS-5061
> URL: https://issues.redhat.com/browse/DROOLS-5061
> Project: Drools
> Issue Type: Epic
> Components: dmn engine
> Reporter: Matteo Mortari
> Assignee: Luca Molteni
> Priority: Major
>
> A codegen facility is required to generate statically code strongly typed for the input/output of a DMN model, considering also the data types defined inside the DMN model as ItemDefinition.
> Surface and interface common to:
> * BPMN integration: when invoking DMN from BPMN, the return of the evaluation is a Map and not the domain model
> * Kogito/OpenAPI/Swagger: when using the codegenerated version, annotation shall explain the swagger API the expected input/output type of the REST request for DMN
> ** for Quarkus based, use RegisterForReflection annotation
> ** use MP validation for allowedvalues
> * DMN Editor: when importing a Java Class in the editor, it shall use the user-supplied Java Class
> Documentation:
> * the programmatic use of the generated classes, directly, is DISCOURAGED
> * if anything, a programmatic use will eventually be stable by making use of the available interfaces in kie-dmn-core
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years
[JBoss JIRA] (DROOLS-5061) DMN strongly typed codegen DMNContext and DMNResult
by Matteo Mortari (Jira)
[ https://issues.redhat.com/browse/DROOLS-5061?page=com.atlassian.jira.plug... ]
Matteo Mortari updated DROOLS-5061:
-----------------------------------
Epic Name: DMN strongly typed codegen DMNContext and DMNResult (was: DMN codegen DMNContext and DMNResult)
> DMN strongly typed codegen DMNContext and DMNResult
> ---------------------------------------------------
>
> Key: DROOLS-5061
> URL: https://issues.redhat.com/browse/DROOLS-5061
> Project: Drools
> Issue Type: Epic
> Components: dmn engine
> Reporter: Matteo Mortari
> Assignee: Luca Molteni
> Priority: Major
>
> A codegen facility is required to generate statically code strongly typed for the input/output of a DMN model, considering also the data types defined inside the DMN model as ItemDefinition.
> Surface and interface common to:
> * BPMN integration: when invoking DMN from BPMN, the return of the evaluation is a Map and not the domain model
> * Kogito/OpenAPI/Swagger: when using the codegenerated version, annotation shall explain the swagger API the expected input/output type of the REST request for DMN
> ** for Quarkus based, use RegisterForReflection annotation
> ** use MP validation for allowedvalues
> * DMN Editor: when importing a Java Class in the editor, it shall use the user-supplied Java Class
> Documentation:
> * the programmatic use of the generated classes, directly, is DISCOURAGED
> * if anything, a programmatic use will eventually be stable by making use of the available interfaces in kie-dmn-core
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years
[JBoss JIRA] (DROOLS-4431) DMN REST endpoint requires stateful kie session
by Matteo Mortari (Jira)
[ https://issues.redhat.com/browse/DROOLS-4431?page=com.atlassian.jira.plug... ]
Matteo Mortari commented on DROOLS-4431:
----------------------------------------
BEFORE:
A BC project containing DMN assets required that IF any KieSession was manually specified as default, that had to be a stateful one.
Justin already specified the +drawbacks+ and the +workaround+ of this when occurring on a mixed-asset type of project in this jira.
NOW:
This is no longer the case.
Moreover, now, DMN Model and DMNRuntime is resolved directly over the default KieBase, including the case where any is manually specified as a default KieBase.
> DMN REST endpoint requires stateful kie session
> -----------------------------------------------
>
> Key: DROOLS-4431
> URL: https://issues.redhat.com/browse/DROOLS-4431
> Project: Drools
> Issue Type: Bug
> Components: dmn engine
> Environment: Noticed this is RHDM 7.3. Still exists in 7.4. Don't know which versions of Drools that coincides with.
> Reporter: Justin Jarae
> Assignee: Matteo Mortari
> Priority: Major
> Labels: field
> Attachments: DMN-Test.zip
>
>
> When trying to run DMN via the rest endpoint, if the default KIE session is stateless, an error is returned stating that "Cannot find a default KieSession". If the stateful session is specified as default, the DMN execution works as expected. This forces you to specify stateless for all other requests.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years
[JBoss JIRA] (DROOLS-4431) DMN REST endpoint requires stateful kie session
by Matteo Mortari (Jira)
[ https://issues.redhat.com/browse/DROOLS-4431?page=com.atlassian.jira.plug... ]
Matteo Mortari commented on DROOLS-4431:
----------------------------------------
Noting stacktrace and reported messages, which are now fixed.
{code:java}
14:29:23,958 ERROR [org.kie.server.services.dmn.ModelEvaluatorServiceBase] (default task-5) Error from container 'traffic-violation_1.0.0-SNAPSHOT': java.lang.RuntimeException: Cannot find a default KieSession
at org.drools.compiler.kie.builder.impl.KieContainerImpl.findKieSessionModel(KieContainerImpl.java:486)
at org.drools.compiler.kie.builder.impl.KieContainerImpl.newKieSession(KieContainerImpl.java:529)
at org.drools.compiler.kie.builder.impl.KieContainerImpl.newKieSession(KieContainerImpl.java:459)
at org.drools.compiler.kie.builder.impl.KieContainerImpl.newKieSession(KieContainerImpl.java:442)
at org.kie.server.services.dmn.ModelEvaluatorServiceBase.evaluateDecisions(ModelEvaluatorServiceBase.java:162)
at org.kie.server.remote.rest.dmn.ModelEvaluatorResource.evaluateDecisions(ModelEvaluatorResource.java:108)
{code}
while using:
{code:xml}
<kmodule xmlns="http://www.drools.org/xsd/kmodule" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<kbase name="KB1" default="true" eventProcessingMode="stream" equalsBehavior="identity">
<ksession name="KS1" type="stateless" default="true" clockType="realtime"/>
</kbase>
</kmodule>
{code}
reproducer messages (now fixed):
{code:java}
[ERROR] Tests run: 3, Failures: 0, Errors: 3, Skipped: 0, Time elapsed: 25.927 s <<< FAILURE! - in org.kie.server.integrationtests.dmn.DMNHelloWorldStatelessKBIntegrationTest
[ERROR] test_evaluateAll[0: JAXB KieServicesConfiguration{transport=REST, serverUrl='http://localhost:54143/kie-server-services/services/rest/server'}](org.kie.server.integrationtests.dmn.DMNHelloWorldStatelessKBIntegrationTest) Time elapsed: 0.381 s <<< ERROR!
org.kie.server.api.exception.KieServicesHttpException:
Unexpected HTTP response code when requesting URI 'http://localhost:54143/kie-server-services/services/rest/server/container...'! Error code: 404, message: <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<response type="FAILURE" msg="Error from container 'hello-world-statelesskb'Cannot find a default KieSession"/>
at org.kie.server.integrationtests.dmn.DMNHelloWorldStatelessKBIntegrationTest.test_evaluateAll(DMNHelloWorldStatelessKBIntegrationTest.java:58)
[ERROR] test_evaluateAll[1: JSON KieServicesConfiguration{transport=REST, serverUrl='http://localhost:54143/kie-server-services/services/rest/server'}](org.kie.server.integrationtests.dmn.DMNHelloWorldStatelessKBIntegrationTest) Time elapsed: 0.345 s <<< ERROR!
org.kie.server.api.exception.KieServicesHttpException:
Unexpected HTTP response code when requesting URI 'http://localhost:54143/kie-server-services/services/rest/server/container...'! Error code: 404, message: {
"type" : "FAILURE",
"msg" : "Error from container 'hello-world-statelesskb'Cannot find a default KieSession",
"result" : null
}
at org.kie.server.integrationtests.dmn.DMNHelloWorldStatelessKBIntegrationTest.test_evaluateAll(DMNHelloWorldStatelessKBIntegrationTest.java:58)
[ERROR] test_evaluateAll[2: XSTREAM KieServicesConfiguration{transport=REST, serverUrl='http://localhost:54143/kie-server-services/services/rest/server'}](org.kie.server.integrationtests.dmn.DMNHelloWorldStatelessKBIntegrationTest) Time elapsed: 0.132 s <<< ERROR!
org.kie.server.api.exception.KieServicesHttpException: Unexpected HTTP response code when requesting URI 'http://localhost:54143/kie-server-services/services/rest/server/container...'! Error code: 404, message: <response type="FAILURE" msg="Error from container 'hello-world-statelesskb'Cannot find a default KieSession"/>
at org.kie.server.integrationtests.dmn.DMNHelloWorldStatelessKBIntegrationTest.test_evaluateAll(DMNHelloWorldStatelessKBIntegrationTest.java:58)
{code}
> DMN REST endpoint requires stateful kie session
> -----------------------------------------------
>
> Key: DROOLS-4431
> URL: https://issues.redhat.com/browse/DROOLS-4431
> Project: Drools
> Issue Type: Bug
> Components: dmn engine
> Environment: Noticed this is RHDM 7.3. Still exists in 7.4. Don't know which versions of Drools that coincides with.
> Reporter: Justin Jarae
> Assignee: Matteo Mortari
> Priority: Major
> Labels: field
> Attachments: DMN-Test.zip
>
>
> When trying to run DMN via the rest endpoint, if the default KIE session is stateless, an error is returned stating that "Cannot find a default KieSession". If the stateful session is specified as default, the DMN execution works as expected. This forces you to specify stateless for all other requests.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years
[JBoss JIRA] (DROOLS-4431) DMN REST endpoint requires stateful kie session
by Matteo Mortari (Jira)
[ https://issues.redhat.com/browse/DROOLS-4431?page=com.atlassian.jira.plug... ]
Matteo Mortari updated DROOLS-4431:
-----------------------------------
Component/s: dmn engine
Tester: Daniel Rosa
Story Points: 3
Sprint: 2020 Week 16-18 (from Apr 13)
> DMN REST endpoint requires stateful kie session
> -----------------------------------------------
>
> Key: DROOLS-4431
> URL: https://issues.redhat.com/browse/DROOLS-4431
> Project: Drools
> Issue Type: Bug
> Components: dmn engine
> Environment: Noticed this is RHDM 7.3. Still exists in 7.4. Don't know which versions of Drools that coincides with.
> Reporter: Justin Jarae
> Assignee: Matteo Mortari
> Priority: Major
> Labels: field
> Attachments: DMN-Test.zip
>
>
> When trying to run DMN via the rest endpoint, if the default KIE session is stateless, an error is returned stating that "Cannot find a default KieSession". If the stateful session is specified as default, the DMN execution works as expected. This forces you to specify stateless for all other requests.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years