Appian engine in FATAL status

RE: Appian engine in FATAL status

Jim Schweitzer — Fri, 24 Mar 2017 20:21:23 GMT

This is not a common occurance. Any time you roll back to previous versions of KDBs, especially exec KDBs, you're basically reverting back part of the system to a previous snapshot in time.

Also, when starting up engines after a failure, sometimes you just need to allow time (hours) for the transactions to replay. Rolling back KDBs should be a last resort and done with help of Appian Support.

RE: Appian engine in FATAL status

octavianp — Fri, 24 Mar 2017 14:34:53 GMT

From what I have detailed, is there something different form the standard procedure? Also this kind of events can happen also in other environments, different than the production one and is definitely not nice, so it would be useful to do whatever it takes to avoid it.

RE: Appian engine in FATAL status

AppianCTO — Wed, 22 Mar 2017 21:11:07 GMT

Troubleshooting a production system should be done with our support team. Please open a case.

RE: Appian engine in FATAL status

octavianp — Wed, 22 Mar 2017 21:08:54 GMT

...ing about the production environment.
2. Now the application is up, but somehow some tasks that have been submitted appear to be in a previous state - why did this happen since we did not used an elder KDB file but just repaired the last one?
3. We noticed the following error in the application-server.log after successfully starting Appian:
“ERROR com.appiancorp.process.runtime.monitoring.GetTaskDetailsAction - Task request info: null
java.lang.IllegalArgumentException: Activity must be attended”
Can this have anything to do with the issue we faced? Should we be worried?
Thanks in advance,
Octav