Fixes are available
9.0.0.4: WebSphere Application Server traditional V9.0 Fix Pack 4
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
9.0.0.5: WebSphere Application Server traditional V9.0 Fix Pack 5
9.0.0.6: WebSphere Application Server traditional V9.0 Fix Pack 6
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
9.0.0.7: WebSphere Application Server traditional V9.0 Fix Pack 7
9.0.0.8: WebSphere Application Server traditional V9.0 Fix Pack 8
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
9.0.0.9: WebSphere Application Server traditional V9.0 Fix Pack 9
9.0.0.10: WebSphere Application Server traditional V9.0 Fix Pack 10
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
9.0.0.11: WebSphere Application Server traditional V9.0 Fix Pack 11
9.0.5.0: WebSphere Application Server traditional Version 9.0.5 Refresh Pack
9.0.5.1: WebSphere Application Server traditional Version 9.0.5 Fix Pack 1
9.0.5.2: WebSphere Application Server traditional Version 9.0.5 Fix Pack 2
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
9.0.5.3: WebSphere Application Server traditional Version 9.0.5 Fix Pack 3
9.0.5.4: WebSphere Application Server traditional Version 9.0.5 Fix Pack 4
9.0.5.5: WebSphere Application Server traditional Version 9.0.5 Fix Pack 5
WebSphere Application Server traditional 9.0.5.6
9.0.5.7: WebSphere Application Server traditional Version 9.0.5 Fix Pack 7
9.0.5.8: WebSphere Application Server traditional Version 9.0.5.8
8.5.5.20: WebSphere Application Server V8.5.5.20
8.5.5.18: WebSphere Application Server V8.5.5 Fix Pack 18
8.5.5.19: WebSphere Application Server V8.5.5 Fix Pack 19
9.0.5.9: WebSphere Application Server traditional Version 9.0.5.9
9.0.5.10: WebSphere Application Server traditional Version 9.0.5.10
8.5.5.16: WebSphere Application Server V8.5.5 Fix Pack 16
8.5.5.21: WebSphere Application Server V8.5.5.21
9.0.5.11: WebSphere Application Server traditional Version 9.0.5.11
APAR status
Closed as program error.
Error description
managesdk is not able to run with security enabled, It is not connecting to Deployment Manager (dmgr). Dmgr is running fine, syncNode works fine. But managesdk fails to connect and complains dmgr is not running [ManageSDK] : updateNodeSdk() : Exception caught : ConectorException CWSDK0020E: Failed to connect to the deployment manager. Ensure that the deployment manager is running. [ManageSDK] : updateNodeSdk() : < exit failure [ManageSDK] : updateProfile() : < exit : failure CWSDK1018I: Profile XXXX could not be enabled to use SDK 1.8_64. [ManageSDK] : enableProfile() profileSingle : < exit : failure [ManageSDK] : performRequestedOperation() enableProfile : < exit : failure managesdk trace shows the following error : 2/6/17 17:40:09:530 EST] 00000001 SOAPConnector < reconnect Exit [SOAPException: faultCode=SOAP-ENV:Client; msg=Error opening socket: java.io.IOException: Exception during sslSocket.startHandshake: java.lang.RuntimeException: Unexpected error: java.security.InvalidAlgorithmParameterException: the trustAnchors parameter must be non-empty; targetException=java.lang.IllegalArgumentException: Error opening socket: java.io.IOException: Exception during sslSocket.startHandshake: java.lang.RuntimeException: Unexpected error: java.security.InvalidAlgorithmParameterException: the trustAnchors parameter must be non-empty] at org.apache.soap.transport.http.SOAPHTTPConnection.send(SOAPHTTPC onnectio n.java:475) at org.apache.soap.rpc.Call.WASinvoke(Call.java:510) at com.ibm.ws.management.connector.soap.SOAPConnectorClient$4.run(S OAPConne ctorClient.java:387) at com.ibm.ws.security.util.AccessController.doPrivileged(AccessCon troller. java:118) The reason why this happens is that the managesdk tool doesn't set proper jvm system property for composing CONFIG_ROOT, thus the code cannot expand the variable. Since CONFIG_ROOT contains cell name.
Local fix
n.a
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server, Network Deployment edition with * * admin security, using the managesdk * * command * **************************************************************** * PROBLEM DESCRIPTION: managesdk.bat[sh] command fails to * * connect to the dmgr and does not update * * the Java SDK as intended * **************************************************************** * RECOMMENDATION: * **************************************************************** The user.install.root parameter, which is used later by security components, was not being passed into the JVM that runs the managesdk command. You may receive messages such as: CWSDK1017I: Profile Dmgr01 now enabled to use SDK 1.8_64. CWSDK0020E: Failed to connect to the deployment manager. Ensure that the deployment manager is running. CWSDK1018I: Profile AppSrv01 could not be enabled to use SDK 1.8_64. CWSDK1016I: Errors occured processing request -enableProfile - profileName AppSrv01 -sdkName 1.8_64. CWSDK1020I: Processing of one or more profiles did not complete successfully. See previous messages.
Problem conclusion
The -Duser.install.root parameter was added to the java invocation in the managesdk.bat[sh] scripts. The fix for this APAR is currently targeted for inclusion in fix pack 9.0.0.4 and 8.5.5.12. Please refer to the Recommended Updates page for delivery information: http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
Temporary fix
Add the -Duser.install.root=%USER_INSTALL_ROOT% to the script manually.
Comments
APAR Information
APAR number
PI78849
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
850
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2017-03-27
Closed date
2017-05-08
Last modified date
2017-05-08
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
WEBS APP SERV N
Fixed component ID
5724H8800
Applicable component levels
R850 PSY
UP
R900 PSY
UP
Document Information
Modified date:
03 May 2022