topic Unable to view process definitions via probe: SAXParseExcept in Alfresco Archive

Unable to view process definitions via probe: SAXParseExcept

wolpert — Wed, 06 Jul 2011 17:59:20 GMT

Folks- I'm using activiti 5.6, via the grails activiti plugin, without a problem. Process definitions are deployed correctly, and can view them correctly via the activiti RepositoryService class. But I get into a problem when I start up the activiti-probe and activiti-explorer webapplication. Attem

Re: Unable to view process definitions via probe: SAXParseExcept

wolpert — Wed, 06 Jul 2011 21:56:32 GMT

I saw one reference that said if encoding is upper case it could cause this exception. I did change in the files that are generated by the eclipse tool from

<?xml version="1.0" encoding="UTF-8"?>

to

<?xml version="1.0" encoding="utf-8"?>

but the error still appears. Still at a loss on this one.

Re: Unable to view process definitions via probe: SAXParseExcept

wolpert — Fri, 29 Jul 2011 17:51:08 GMT

Does anyone have any insight into this problem?

Re: Unable to view process definitions via probe: SAXParseExcept

jbarrez — Fri, 05 Aug 2011 13:07:06 GMT

The exception happens when there is something wrong as first element.

Did you try with a very minimal process? Can you post your process?

Re: Unable to view process definitions via probe: SAXParseExcept

wolpert — Fri, 05 Aug 2011 17:36:18 GMT

The issues is independent of the complexity of the activiti xml file to import.

The process definition deployed using probe work fine. Meaning that once deployed, you can view the process definition without the error.

If the same XML is deployed using the grails-activiti plugin, reviewing the process fails with the exception show above when trying to review the process with activiti.

Correct me if I'm wrong, but probe is retrieving the XML from the core engine using an internal technique, and re-validating what was stored internally. If this is correct, then the part that is delivering the XML to probe is adding something to the XML to cause the error in probe validation of the XML. Remember that using this process defined by the XML does work fine…. so the core engine is working normally. I'm at a loss to explain what occurs during the deployment via grails-activiti that causes this error.

I'll come up with specific steps to reproduce this problem, but I'll do it with the next version of activiti (5.7) just in case that impacts the issue.

Re: Unable to view process definitions via probe: SAXParseExcept

jbarrez — Wed, 10 Aug 2011 12:34:58 GMT

Okay, 15 aug is the target date.
Keep us posted, as I'm curious to what could lead to the problem.

Re: Unable to view process definitions via probe: SAXParseExcept

wolpert — Tue, 16 Aug 2011 20:16:47 GMT

Turns out the problem was resolved at the database driver level. Specifically, the issue is in how the JDBC driver retrieves 'bytea' fields. With the application using 8.4-701 driver against the 9.0 database, the problem would manifest itself in retrieving the data 'in certain cases'. Upgraded to 9.0-801 and it worked fine. Also, the 9.0-801 driver was able to read from the 8.4 database without a problem. (Backwards compatible, not forward compatible, as one would reasonably expect.)

I cannot explain why some cases would work and others would not, but since upgrading the JDBC driver fixed all the problem cases, I'm calling it 'good'.

Re: Unable to view process definitions via probe: SAXParseExcept

ronald_van_kuij — Wed, 17 Aug 2011 07:21:49 GMT

thanks for reporting back. Appreciated. Can you just add which db it was?

Re: Unable to view process definitions via probe: SAXParseExcept

wolpert — Thu, 18 Aug 2011 16:08:26 GMT

PostgreSQL…

Re: Unable to view process definitions via probe: SAXParseExcept

jbarrez — Fri, 26 Aug 2011 08:09:03 GMT

djeez … that's a very deep bug … kudos that you were able to find it!