[
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. 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.
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...]
Can that URL be made available again? Or can the information formerly available there be
provide so that we can host it?
We have several production systems that are non-functioning due to this issue. So, this is
a very high priority for us.
Unavailable URL:
http://drools.org/drools-5.0/change-set
--------------------------------------------------------
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. 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.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)