Hi all, We've encountered an error while simply starting an empty

Ranno Soesilo over 8 years ago

Hi all,

We've encountered an error while simply starting an empty script task in a newly created process model.

We have Appian 7.10 installed on JBoss EAP-6.4.0 and MySQL with mysql-connector-java-5.1.35-bin.jar.

Ran checkengine.bat and every engine is running properly.

Small portion of the error is:

2015-09-24 15:30:12,500 [Appian Work Item - 0 - ProcessExec00 : UnattendedJavaActivityRequest] ERROR com.appiancorp.process.engine.UnattendedJavaActivityRequest - An error occurred while executing activity: id=38, classname=com.appiancorp.process.runtime.activities.MoveDiscussionContentActivity

And just a general error as an e-mail (included a screenshot of the body).

I've included the server.log and application-server.log files and it logs from the point Appian and JBoss are started until the execution of the process model with just an empty script task.

Any help is appreciated! Thanks in advance!

With regards,

Ranno

Discussion posts and replies are publicly visible

Parents

0 Eduardo Fuentes
Appian Employee
over 8 years ago

I can confirm both models have the reference to the right local id: "internal.16" which is what I expected to see in the XML for a script task. This is not an issue with the model itself apparently.

Your XMLs all look fine

Here are my hypotheses:

1. The web server is pointing to an old-date web.war folder (static content) and needs to be updated

2. This environment runs in two boxes, one box with APP Server and the other one ENGINE server and they are running two different hotfixes of Appian

3. The appian-topology.xml file in the APP_SERVER is not correctly configured and is making the APP_SERVER send the request to the wrong environment, possibly with an older version of Appian

4. This environment has network connectivity with other servers where APPIAN is running and the standalone.xml is allowing them to interact (e.g. clustering) by mistake.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Reply

0 Eduardo Fuentes
Appian Employee
over 8 years ago

I can confirm both models have the reference to the right local id: "internal.16" which is what I expected to see in the XML for a script task. This is not an issue with the model itself apparently.

Your XMLs all look fine

Here are my hypotheses:

1. The web server is pointing to an old-date web.war folder (static content) and needs to be updated

2. This environment runs in two boxes, one box with APP Server and the other one ENGINE server and they are running two different hotfixes of Appian

3. The appian-topology.xml file in the APP_SERVER is not correctly configured and is making the APP_SERVER send the request to the wrong environment, possibly with an older version of Appian

4. This environment has network connectivity with other servers where APPIAN is running and the standalone.xml is allowing them to interact (e.g. clustering) by mistake.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Children

No Data