A null pointer exception occurs after you schedule a flow in SAS Job Flow Scheduler. Its thread stops responding in SAS^® Web Infrastructure Platform Services and also stops listening to port 1964. A similar null pointer exception occurs if the scheduling service has a log level of DEBUG.

When this exception occurs, SAS^® Management Console does not retrieve flows to expand or refresh the Schedule Manager plug-in, and further attempts to schedule fail.

Restarting SAS Web Infrastructure Platform Services on the middle-tier environment restarts the SAS Job Flow Scheduler thread until another exception occurs.

You can verify that this issue has occurred by taking these steps:

• Use the netstat command-line utility to verify that port 1964 is no longer listening on the middle-tier environment.
• Check the SASWIPServices9.4.log file in SAS-configuration-directory/Lev1/Web/Logs/SASServer1_1/ to see whether a null pointer exception has been recorded for scheduling. 

Click the Hot Fix tab in this note to access the hot fix for this issue.

Operating System and Release Information

A fix for this issue for SAS Middle Tier 9.4_M7 is available at:

A fix for this issue for SAS Management Console 9.4_M7 is available at:

A fix for this issue for SAS Middle Tier 9.4_M6 is available at: