Closed fmannhardt closed 4 years ago
Please note that also other Errors , like ExceptionInInitializerError might be thrown when JAR files are missing in the class path. Some error handling and printout to the log would be very helpful to diagnose these errors.
Fixed in latest update. All Throwables from data gateways now caught and logged.
If a Data Gateway throws a NoClassDefFoundError the case cannot be stopped anymore and there are no log messages to diagnose the issue. Since Data Gateways are quite likely to require 3rd party libraries, which might not be on the correct path NoClassDefFoundError are likely to be encountered.
the YAWL Engine stops working and can only be recovered by restarting the Tomcat sever. Here a test case Data Gateway that simply throws an Exception: TestDataGateway.zip
The respective calls to 'populateTaskParameter' and 'updateFromTaskCompletion' should also catch an Error. At least the YAWL Engine should not crash.
For completeness, the following exception is logged:
After a while the following message is logged