Closed as program error.
discovered that it's not a missing timeout value that caused the NPE. It appears we were referencing a config object that was null when this socket factory was called.
Work-around (changed import file) and hot fix provided
Users Affected: Customers upgrading from Sterling Secure Proxy 2.x to SSP 3.4 Problem Description: Customer upgraded from SSP 2.x to SSP 3.4 and imported the configuration from SSP 2.x. When running Connect:Direct Secure+ sessions outbound through SSP, they get MSGCSP057E "Snode session could not start to intended route" and a NullPointerException in the ProxyServerCDImpl class. The import utility did not provide an empty property tag for the C:D adapters, and the engine got the NPE failure trying to access it. Platforms Affected: All
Resolution Summary: Now handle the case where no properties are defined in the C:D adapter config file and avoid the NullPointerException. Workaround is to save each C:D adapter configuration individually after the upgrade, as the empty property tags are generated correctly during the save operation. Delivered In: 22.214.171.124,126.96.36.199,188.8.131.52
Reported component name
STR SECURE PROX
Reported component ID
Last modified date
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fixed component name
STR SECURE PROX
Fixed component ID
Applicable component levels
Rate this page:
Copyright and trademark information
IBM, the IBM logo and ibm.com are trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the Web at "Copyright and trademark information" at www.ibm.com/legal/copytrade.shtml.