topic Re: Error execute script document-workflows.get.js in Alfresco Archive

Error execute script document-workflows.get.js

user21 — Fri, 29 Jun 2012 15:31:26 GMT

Hello, after upgrading my alfresco from 3.4.c to 4.0.c, i get this error, when open document in Repository:Exception: org.mozilla.javascript.JavaScriptException - [object Error] (file:/usr/local/alfresco/tomcat/webapps/share/WEB-INF/classes/alfresco/site-webscripts/org/alfresco/components/document-d

Re: Error execute script document-workflows.get.js

jpotts — Fri, 29 Jun 2012 22:22:21 GMT

You're going to have to debug it. It looks like Share is getting a bad response from the repository tier web script it is invoking to find the workflows for a given document.

As you can see in the Share tier controller, the repository tier web script being invoked is:
http://localhost:8080/alfresco/s/api/node/{some node ref}/workflow-instances

You can put this into your browser and see what comes back. It might have some useful error message.

The documentation for the repository tier web script being invoked is:
http://localhost:8080/alfresco/s/script/org/alfresco/repository/workflow/workflow-instances-for-node.get

Look at that and you can see the freemarker library where this logic lives, which is:
$TOMCAT_HOME/webapps/alfresco/WEB-INF/classes/alfresco/templates/webscripts/org/alfresco/repository/workflow/workflow.lib.ftl

Everything in there eventually calls Java code and you have that source. So if you don't find anything helpful in the repository tier error message, set a breakpoint in the workflow API Java classes and then hit the web script again so you can step through it.

The scripts all work fine for me on 4.0.c so this is highly likely due to some sort of funky data condition caused by your upgrade.

Jeff

Re: Error execute script document-workflows.get.js

user21 — Tue, 03 Jul 2012 04:51:21 GMT

Dear Jeff, thank you for your reply.
Actually I can't execute the repository tier web script, so it says 404 HTTP error or empty json data. I think the URL is incorrect.
I've tried:
http://172.172.174.111:8080/alfresco/s/api/node/{workspace://SpacesStore/5c2ac44c-1657-495d-a4d0-9a1eaec0697e}/workflow-instances
http://172.172.174.111:8080/alfresco/s/api/node/{5c2ac44c-1657-495d-a4d0-9a1eaec0697e}/workflow-instances
http://172.172.174.111:8080/alfresco/s/api/node/5c2ac44c-1657-495d-a4d0-9a1eaec0697e/workflow-instances
there're no any results.

Could you tell me how to run this properly?

Re: Error execute script document-workflows.get.js

jpotts — Tue, 03 Jul 2012 13:37:15 GMT

1. Take the curly braces out.
2. Convert the "://" to "/"

Your URL should be:
http://172.172.174.111:8080/alfresco/s/api/node/workspace/SpacesStore/5c2ac44c-1657-495d-a4d0-9a1eaec0697e/workflow-instances

Jeff

Re: Error execute script document-workflows.get.js

user21 — Wed, 04 Jul 2012 04:50:06 GMT

Thank you for so quick reply. Now I've understood the root cause of my error.
The error was:
{
    "code" : 500,
    "name" : "Internal Error",
    "description" : "An error inside the HTTP server which prevented it from fulfilling the request."
},

"message" : "060413059 Wrapped Exception (with status template): 060453144 Workflow Component for engine id 'jbpm' is not registered",
"exception" : "org.springframework.extensions.webscripts.WebScriptException - 060413059 Wrapped Exception (with status template): 060453144 Workflow Component for engine id 'jbpm' is not registered",

So this error happens on any document that was involved in business processes in my previous version of Alfresco 3.4. (In 3.4 it was bpmn but version 4 uses activiti)
Jeff, could you tell me how to fix this issue on all my documents? Thanks in advance!

Re: Error execute script document-workflows.get.js

jpotts — Thu, 05 Jul 2012 14:33:03 GMT

Can you set:
system.workflow.engine.jbpm.enabled=true

In your alfresco-global.properties file and restart to see if that clears it up?

Jeff

Re: Error execute script document-workflows.get.js

user21 — Fri, 06 Jul 2012 12:53:00 GMT

Thank you Jeff, i put that property to my alfresco-global.properties and restart alfresco, but error is still showing