IC82133: SECURE PROXY OUT-GOING CONNECTIONS FAILING

APAR status

• Closed as program error.

Error description

• 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.
  

Local fix

• Work-around (changed import file) and hot fix provided
  

Problem summary

• 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
  

Problem conclusion

• 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:
  3.3.1.20,3.4.0.2,3.4.1.2
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  STR SECURE PROX

• Fixed component ID

  5725D0300

Applicable component levels

• R320 PSY

     UP

• R331 PSY

     UP

• R340 PSY

     UP

• R341 PSY

     UP