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

0 Ranno Soesilo over 8 years ago

With the logs.
server.log
application-server.log
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Mike Cichy
Appian Employee
over 8 years ago

Can you provide a screenshot of your model, please?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Stefan Helzle
A Score Level 3
over 8 years ago

It is not too complex. The script task is completely empty. No inputs or outputs.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Eduardo Fuentes
Appian Employee
over 8 years ago

There's something wrong with your environment. The error shows the failing node is: "MoveDiscussionContentActivity". That doesn't correspond to the script task code.

Can you attach all the files of type (make sure to include any file with these words in the name)

<APPIAN_HOME>\\ear\\suite.ear\\web.war\\WEB-INF\\conf\\process\\-activities.xml?
<APPIAN_HOME>\\ear\\suite.ear\\web.war\\WEB-INF\\conf\\process\\palette-config*.xml

Can you export the dummy model that is failing? I want to review its XML to make sure it's exporting the script task and not the wrong node.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Eduardo Fuentes
Appian Employee
over 8 years ago

Another question. Are you using a Web Server? (e.g. Apache, IIS, etc.)?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Ranno Soesilo over 8 years ago

Hi Eduardo,

Glad you're helping us out. Yes, we are using IIS 8.0 as the webserver. After running the process also locally, we produced the same error.

In the attachments I have included the requested files including the exported application of the process model.
Also included is an exported replica application of the same process model in an Appian Cloud environment, where it is not producing any errors.

Thanks !

With regards,

Ranno
activities xml files.zip
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
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
0 Ranno Soesilo over 8 years ago

Thanks for the help Eduardo. With your hypotheses we were able to find out what the problem was. It was due to a missing copied file of server/process/design/gw1/pd*.kdb, which was unfortunately left out in the migrating process. Everything is up and running again!
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel