[JBoss JIRA] (DROOLS-3983) SAXParser error premature file on Change Set with Drools 5.3.1.Final
by Tibor Zimanyi (Jira)
[ https://issues.jboss.org/browse/DROOLS-3983?page=com.atlassian.jira.plugi... ]
Tibor Zimanyi commented on DROOLS-3983:
---------------------------------------
[~damian_roa], could you please change your XSD location so it uses https instead of http? We have a test that started to fail using this [1] XSD. When I use https instead of http there, it works. Looks like anonsvn.jboss.org was migrated to pure https (so no http available now).
[1] https://github.com/kiegroup/drools/blob/dc84a0abf017f15c12b270ace07efa7a5...
> SAXParser error premature file on Change Set with Drools 5.3.1.Final
> --------------------------------------------------------------------
>
> Key: DROOLS-3983
> URL: https://issues.jboss.org/browse/DROOLS-3983
> Project: Drools
> Issue Type: Bug
> Affects Versions: 5.6.0.Final
> Reporter: Sergio Roa
> Assignee: Mario Fusco
> Priority: Major
>
> The loading of the *change-set file is throwing a SaxParseException* since yesterday when starting our application, it didnt gave errors during the last 5 years and it remains untouched.
> We saw that this happened yesterday to the user Greg on this same forum, it suddenly started to happend to us yesterday too, so we were wondering what steps did you guys followed to fix the problem? We have a production system running OK, but our local machines are giving error when starting tomcat/websphere instances, we're scared that production machines will start to fail when restarting the services.. We're open to hearing suggestions or related fixes. Thanks in advance.
> UPDATE: 07/05/19: We found out that the JBPM service starts if we add this to our Tomcats/Websphere's For the people suffering the same problem that us *"-Ddrools.schema.validating=false"*. We believe that is a error in something related to the XMLParser library from the drools versión itself, maybe this can bring attention to the devs to this case.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (DROOLS-3985) [DMN Editor] No Build Error about missing inputs for imported node
by Michael Anstis (Jira)
[ https://issues.jboss.org/browse/DROOLS-3985?page=com.atlassian.jira.plugi... ]
Michael Anstis reassigned DROOLS-3985:
--------------------------------------
Assignee: Guilherme Gomes (was: Michael Anstis)
> [DMN Editor] No Build Error about missing inputs for imported node
> ------------------------------------------------------------------
>
> Key: DROOLS-3985
> URL: https://issues.jboss.org/browse/DROOLS-3985
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.22.0.Final
> Reporter: Jozef Marko
> Assignee: Guilherme Gomes
> Priority: Major
> Labels: drools-tools
> Attachments: MySpace_dmn.imports.zip
>
>
> This Iss was spotted during review of [PR|https://github.com/kiegroup/kie-wb-common/pull/2620] for DROOLS-3829 and DROOLS-3934.
> If user deploy a model with imported node, and this node miss inputs, no build error appears. However there is error if user tries to execute such model, for example via rest.
> h3. Steps To Reproduce
> # Deploy the attached project to kie server
> # Try to execute the model as:
> {code:sh}
> curl -u testadmin:'admin1234;' -H "accept: application/json" -H "content-type: application/json" -X POST "http://localhost:8080/kie-server/services/rest/server/containers/dmn.impo..." -d "{ \"model-namespace\" : \"https://github.com/kiegroup/drools/kie-dmn/_547C193C-0B52-45F5-877E-F74A7...", \"model-name\" : \"routes\", \"decision-name\" : [\"Traffic.Traffic\" ], \"decision-id\" : [ ], \"dmn-context\" : {\"Cars Per Hour\" : 10}}"
> {code}
> # You will get reuslt:
> {code:json}
> {
> "type" : "SUCCESS",
> "msg" : "OK from container 'dmn.imports'",
> "result" : {
> "dmn-evaluation-result" : {
> "messages" : [ {
> "dmn-message-severity" : "ERROR",
> "message" : "Required dependency 'Cars Per Hour' not found on node 'Traffic'",
> "message-type" : "REQ_NOT_FOUND",
> "source-id" : "_6BA74389-CBF7-4D6A-99B1-9F494DCC323A"
> } ],
> "model-namespace" : "https://github.com/kiegroup/drools/kie-dmn/_547C193C-0B52-45F5-877E-F74A7...",
> "model-name" : "routes",
> "decision-name" : "Traffic.Traffic",
> "dmn-context" : {
> "Cars Per Hour" : 10,
> "Traffic" : { }
> },
> "decision-results" : {
> "https://github.com/kiegroup/drools/kie-dmn/_1876D3A2-0972-4AE8-AF59-A56AD..." : {
> "messages" : [ {
> "dmn-message-severity" : "ERROR",
> "message" : "Required dependency 'Cars Per Hour' not found on node 'Traffic'",
> "message-type" : "REQ_NOT_FOUND",
> "source-id" : "_6BA74389-CBF7-4D6A-99B1-9F494DCC323A"
> } ],
> "decision-id" : "https://github.com/kiegroup/drools/kie-dmn/_1876D3A2-0972-4AE8-AF59-A56AD...",
> "decision-name" : "Traffic.Traffic",
> "result" : null,
> "status" : "SKIPPED"
> }
> }
> }
> }
> }{code}
> h3. Actual result
> There is response error message about missing dependency but no build error message
> h3. Expected result
> There is built error message
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (DROOLS-3983) SAXParser error premature file on Change Set with Drools 5.3.1.Final
by Sergio Roa (Jira)
[ https://issues.jboss.org/browse/DROOLS-3983?page=com.atlassian.jira.plugi... ]
Sergio Roa updated DROOLS-3983:
-------------------------------
Description:
The loading of the *change-set file is throwing a SaxParseException* since yesterday when starting our application, it didnt gave errors during the last 5 years and it remains untouched.
We saw that this happened yesterday to the user Greg on this same forum, it suddenly started to happend to us yesterday too, so we were wondering what steps did you guys followed to fix the problem? We have a production system running OK, but our local machines are giving error when starting tomcat/websphere instances, we're scared that production machines will start to fail when restarting the services.. We're open to hearing suggestions or related fixes. Thanks in advance.
UPDATE: 07/05/19: We found out that the JBPM service starts if we add this to our Tomcats/Websphere's For the people suffering the same problem that us *"-Ddrools.schema.validating=false"*. We believe that is a error in something related to the XMLParser library from the drools versión itself, maybe this can bring attention to the devs to this case.
was:
The loading of the change-set file is throwing a SaxParseException since yesterday when starting our application, when it didnt gave errors during the last 5 years.
We saw that this happened yesterday to the user Greg on this same forum, it suddenly started to happend to us yesterday too, so we were wondering what steps did you guys followed to fix the problem? We have a production system running OK, but our local machines are giving error when starting tomcat/websphere instances, we're scared that production machines will start to fail when restarting the services.. We're open to hearing suggestions or related fixes. Thanks in advance.
UPDATE: 07/05/19: We found out that the JBPM service starts if we add this to our Tomcats/Websphere's For the people suffering the same problem that us "-Ddrools.schema.validating=false". We believe that is a error in something related to the XMLParser library from the drools versión itself, maybe this can bring attention to the devs to this case.
> SAXParser error premature file on Change Set with Drools 5.3.1.Final
> --------------------------------------------------------------------
>
> Key: DROOLS-3983
> URL: https://issues.jboss.org/browse/DROOLS-3983
> Project: Drools
> Issue Type: Bug
> Affects Versions: 5.6.0.Final
> Reporter: Sergio Roa
> Assignee: Mario Fusco
> Priority: Major
>
> The loading of the *change-set file is throwing a SaxParseException* since yesterday when starting our application, it didnt gave errors during the last 5 years and it remains untouched.
> We saw that this happened yesterday to the user Greg on this same forum, it suddenly started to happend to us yesterday too, so we were wondering what steps did you guys followed to fix the problem? We have a production system running OK, but our local machines are giving error when starting tomcat/websphere instances, we're scared that production machines will start to fail when restarting the services.. We're open to hearing suggestions or related fixes. Thanks in advance.
> UPDATE: 07/05/19: We found out that the JBPM service starts if we add this to our Tomcats/Websphere's For the people suffering the same problem that us *"-Ddrools.schema.validating=false"*. We believe that is a error in something related to the XMLParser library from the drools versión itself, maybe this can bring attention to the devs to this case.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (DROOLS-3983) SAXParser error premature file on Change Set with Drools 5.3.1.Final
by Sergio Roa (Jira)
[ https://issues.jboss.org/browse/DROOLS-3983?page=com.atlassian.jira.plugi... ]
Sergio Roa updated DROOLS-3983:
-------------------------------
Description:
The loading of the change-set file is throwing a SaxParseException since yesterday when starting our application, when it didnt gave errors during the last 5 years.
We saw that this happened yesterday to the user Greg on this same forum, it suddenly started to happend to us yesterday too, so we were wondering what steps did you guys followed to fix the problem? We have a production system running OK, but our local machines are giving error when starting tomcat/websphere instances, we're scared that production machines will start to fail when restarting the services.. We're open to hearing suggestions or related fixes. Thanks in advance.
UPDATE: 07/05/19: We found out that the JBPM service starts if we add this to our Tomcats/Websphere's For the people suffering the same problem that us "-Ddrools.schema.validating=false". We believe that is a error in something related to the XMLParser library from the drools versión itself, maybe this can bring attention to the devs to this case.
was:
The loading of the change-set file is throwing a SaxParseException. I believe the problem is due to the fact that the following url is no longer available:
[http://drools.org/drools-5.0/change-set|http://drools.org/drools-5.0/chan...]
We saw that this happened yesterday to the user Greg on this same forum, it suddenly started to happend to us yesterday too, so we were wondering what steps did you guys followed to fix the problem? We have a production system running OK, but our local machines are giving error when starting tomcat/websphere instances, we're scared that production machines will start to fail when restarting the services.. We're open to hearing suggestions or related fixes. Thanks in advance.
Summary: SAXParser error premature file on Change Set with Drools 5.3.1.Final (was: Unavailable URL: http://drools.org/drools-5.0/change-set)
> SAXParser error premature file on Change Set with Drools 5.3.1.Final
> --------------------------------------------------------------------
>
> Key: DROOLS-3983
> URL: https://issues.jboss.org/browse/DROOLS-3983
> Project: Drools
> Issue Type: Bug
> Affects Versions: 5.6.0.Final
> Reporter: Sergio Roa
> Assignee: Mario Fusco
> Priority: Major
>
> The loading of the change-set file is throwing a SaxParseException since yesterday when starting our application, when it didnt gave errors during the last 5 years.
> We saw that this happened yesterday to the user Greg on this same forum, it suddenly started to happend to us yesterday too, so we were wondering what steps did you guys followed to fix the problem? We have a production system running OK, but our local machines are giving error when starting tomcat/websphere instances, we're scared that production machines will start to fail when restarting the services.. We're open to hearing suggestions or related fixes. Thanks in advance.
> UPDATE: 07/05/19: We found out that the JBPM service starts if we add this to our Tomcats/Websphere's For the people suffering the same problem that us "-Ddrools.schema.validating=false". We believe that is a error in something related to the XMLParser library from the drools versión itself, maybe this can bring attention to the devs to this case.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months