IT14615: (SSPENG) ENGINE DOES NOT SHUTDOWN FROM COMMAND LINE

APAR status

• Closed as program error.

Error description

• User recently upgraded to 3.4.2.0 iFix 6+, then iFix 7 for
  Secure Proxy.  From the command line,  the user cannot shut
  down the SSP engine using .
  
  /stopEngine.sh mode=auto or just the regular ./stopEngine.sh.
  
  Error Message: '*** Could not connect to engine'.
  
  01 Apr 2016 16\:08\:02,637 64250468 [RequestHandler Pool Worker
  - 4] ERROR
  com.sterlingcommerce.component.accepter.csap.impl.AccepterImpl
  - ACPT042E SessionId: 2144 - Failed to secure connection.
  Address=/10.180.100.39:44258 : Client requested protocol TLSv1
  not enabled or not supported
  01 Apr 2016 16\:08\:02,646 3459 [main] ERROR
  com.sterlingcommerce.csp.client.Main - Could not connect to
  Engine. Either Engine is not running or the Engine connection
  parameters are incorrect.
  01 Apr 2016 16\:08\:02,647 3460 [main] ERROR
  com.sterlingcommerce.csp.client.Main -
  javax.net.ssl.SSLHandshakeException: Received fatal alert:
  handshake_failure
  

Local fix

• STRRTC - 497092
  RJ/RJ
  Circumvention:
  Update to latest SSP Build
  

Problem summary

• Customer could not shut down the SSP engine from the command
  line using either stopEngine.sh mode=auto or the regular
  ./stopEngine.sh.
  

Problem conclusion

• Added logic to SSP code base so that the TLS protocol is no
  longer hard-coded for SSP engine shutdown module.
  

Temporary fix

• Sent Customer SSP3420 iFix 7+ Build267.
  

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