]
Sergio Roa resolved DROOLS-3983.
--------------------------------
Resolution: Done
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.