PI78849: MANAGESDK GIVES ERROR DEPLOYMENT MANAGER NOT RUNNING WHEN RUNNING ON NODE WITH SECURITY ENABLED

Fixes are available

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

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.5","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
03 May 2022

Tips

PI78849: MANAGESDK GIVES ERROR DEPLOYMENT MANAGER NOT RUNNING WHEN RUNNING ON NODE WITH SECURITY ENABLED

Fixes are available

Subscribe

APAR status

Closed as program error.

Error description

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

APAR number

Reported component name

Reported component ID

Reported release

Status

PE

HIPER

Special Attention

Submitted date

Closed date

Last modified date

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

Fixed component ID

Applicable component levels

R850 PSY

R900 PSY

Document Information

Share your feedback

Need support?