'Workflow could not be started' about alfresco-developer-series HOT 12 CLOSED

Can you check $ALFRESCO_HOME/tomcat/logs/catalina.out and see if there are
any exceptions in the log?

On Mon, Oct 12, 2015 at 2:07 PM, Nick Ferguson [email protected]
wrote:

I'm working through the workflow tutorial, and I'm having difficulty with
the publishWhitepaper workflow. The other share-configured workflow,
helloWorld UI works fine, but each time I try to start the
publishWhitepaper workflow, be it from the content edit page or from the
"My Tasks" applet, I receive an error "Workflow could not be started" with
the message "Failed to start workflow.. "

I've applied the amps to an existing 5.0.d server with the previous
tutorial's amps, using the -force parameter on apply_amps. I'm using the
code downloaded directly from here in case I made a mistake.

Any ideas?

—
Reply to this email directly or view it on GitHub
#9.

from alfresco-developer-series.

I don't see a catalina.out file, but I do see a catalina.2015-10-13. In it, the only non-"INFO" entry in the log says this: WARNING: [SetContextPropertiesRule]{Context} Setting property 'debug' to '0' did not find a matching property.

Full log here: Gist of entire log

I didn't included system info, which may be helpful.
Windows 10
Alfresco Community Edition 5.0.d (with all files configured for it)
Chrome

from alfresco-developer-series.

This is not the full log so it isn't much help, unfortunately. Can you find
an alfresco.log file?

On Tue, Oct 13, 2015 at 6:49 AM, Nick Ferguson [email protected]
wrote:

I don't see a catalina.out file, but I do see a catalina.2015-10-13. In
it, the only non-"INFO" entry in the log says this: WARNING:
[SetContextPropertiesRule]{Context} Setting property 'debug' to '0' did not
find a matching property.

Full log here: Gist of entire log
https://gist.github.com/fergusonna/61534a279c1dbecc6f06

—
Reply to this email directly or view it on GitHub
#9 (comment)
.

from alfresco-developer-series.

I reinstalled the Alfresco server, and reapplied the amps from before. THIS is the log from running it today with the same error.

Below is the error. Ignore the circle as I was asking someone else if the numbers were helpful in looking up the problem.

from alfresco-developer-series.

There should be a corresponding log entry that describes why the workflow
could not be started.

On Tue, Oct 13, 2015 at 8:59 AM, Nick Ferguson [email protected]
wrote:

I reinstalled the Alfresco server, and reapplied the amps from before.
THIS https://gist.github.com/fergusonna/e1b0b421317e67498bd9 is the log
from running it today with the same error.

Below is the error. Ignore the circle as I was asking someone else if the
numbers were helpful in looking up the problem.
[image: workflow_error]
https://cloud.githubusercontent.com/assets/6790737/10456757/f64c731a-7190-11e5-87e8-62cd8660af1d.png

—
Reply to this email directly or view it on GitHub
#9 (comment)
.

from alfresco-developer-series.

I linked the only alfresco.log that I found. https://gist.github.com/fergusonna/e1b0b421317e67498bd9

from alfresco-developer-series.

When I attempted to run the repo tier with 'mvn integration-test -Pamp-to-war', I noticed an error mentioning that "No bean named 'lucene' is defined".

from alfresco-developer-series.

There is no integration test for the workflow project. Let me see if I can re-create this and I'll get back to you.

from alfresco-developer-series.

This does appear to be a bug of some sort, but the question is why. All of this code has been tested with 5.0.d and 5.0 Enterprise and it hasn't changed. I'm wondering if something changed in the upstream SDK.

from alfresco-developer-series.

Sorry, I meant by launching the repo with the mvn integration-test
-Pamp-to-war command.
On Oct 14, 2015 7:00 PM, "Jeff Potts" [email protected] wrote:

There is no integration test for the workflow project. Let me see if I can
re-create this and I'll get back to you.

—
Reply to this email directly or view it on GitHub
#9 (comment)
.

from alfresco-developer-series.

May be related to this: https://forums.activiti.org/content/couldnt-find-variable-type-able-serialize-object-global-nashornglobal

Still investigating.

from alfresco-developer-series.

Fixed, see 1b09e8b. The move to nashorn caused the plain script task element to fail. I swapped it out for a service task instead.
Thanks for the report!

from alfresco-developer-series.