TIBCO DataSynapse GridServer Service Session stuck after all task completed due to java.lang.NullPointerException
Article ID: KB0073196
Updated On:
| Products | Versions |
|---|---|
| TIBCO DataSynapse GridServer | 5.2.x, 6.3.x, 7.0.0 |
Description
If a GridServer Service Session is stuck in running state due to NullPointerException on the Driver side, you will see a message like:
06/23/21 09:14:54.251 FINE: [JakartaHttpSupport] t:[id:438] JHS: Check Response
JHS: Response Value:200
cannot deserialize object java.lang.NullPointerException
java.lang.NullPointerException
06/23/21 09:14:54.267 SEVERE: [TaskDispatcher$DispatcherJob] t:[id:438] while calling taskFailed java.lang.NullPointerException
JHS: Response Value:200
cannot deserialize object java.lang.NullPointerException
java.lang.NullPointerException
06/23/21 09:14:54.267 SEVERE: [TaskDispatcher$DispatcherJob] t:[id:438] while calling taskFailed java.lang.NullPointerException
From the above message, we can confirm that the Driver was able to download properly the task output from the Engine, as we can see the response for all the task outputs like:
06/23/21 09:14:54.251 FINE: [JakartaHttpSupport] t:[id:438] JHS: Check Response
JHS: Response Value:200
JHS: Response Value:200
However, the NPE can be seen after the Driver downloads the task output from the Engine. This happens when the application code is trying to do some operation that seems to be a NULL object.
Environment
All
Resolution
Customer will need to check for NULL object before doing decoding/serialize/deserialize (or any operation done in the client application code) that could be corrupting GridServer cache that is causing next Failed to recover corrupt cache entry error.
Issue/Introduction
If a GridServer Service Session is stuck in running state due to NullPointerException on the Driver side after successfully downloaded all task outputs. It is needed to control NPE from client code before making any further operation.
Feedback
Yes
No
Powered by
