Details
-
Fix
-
Status: Released (View Workflow)
-
Minor
-
Resolution: Fixed
-
1.12
-
None
Description
Current Situation
When the job JobSchedulerPLSQLJobJSAdapterClass runs on an agent and the connection string is wrong, the log contains
COM-80020009 com.sos.JSHelper.Exceptions.JobSchedulerException: Fatal Error (null), method=call
Here are two problems
- There should not be a null pointer exception
- The original error is not shown in the log
Desired Behavior
When the job JobSchedulerPLSQLJobJSAdapterClass runs on an agent and the connection string is wrong
- No null pointer exception should be raised
- The correct error should be shown like this
COM-80020009 com.sos.JSHelper.Exceptions.JobSchedulerException: Fatal Error (SQL Exception raised. Msg='The Network Adapter could not establish the connection', Status='61000' (The Network Adapter could not establish the connection)), method=call
or
COM-80020009 com.sos.JSHelper.Exceptions.JobSchedulerException: Fatal Error (SQL Exception raised. Msg='Listener refused the connection with the following error:
ORA-12514, TNS:listener does not currently know of service requested in connect descriptor
', Status='66000' (Listener refused the connection with the following error:
ORA-12514, TNS:listener does not currently know of service requested in connect descriptor
)), method=call
Patch
A patch is available here.