Troubleshooting
Problem
We successfully applied the fix pack WAS 8.5.5.13, Switched JDK1.7 to 1.8 (8.0.5.6) and then upgrade BPM 8.6.
After dmgr / nodeagent, JVM restarted, but we are unable to access any bpm consoles.
Symptom
Problem Description and Scenario as follows
We are performing IBM Business Process Manager Version 8.6 upgrade, and the Installing V8.6 requires WebSphere Application Server V8.5.5, Fix Pack 13 or a later version and IBM WebSphere SDK Java Technology Edition Version 8.0 (Java 8).
Hence we performed given below upgrades.
1) Installed IBM WebSphere SDK Java Technology Edition Version 8.0 (Java 8.0.5.6 ) and switched from Java 1.7
2) Upgraded WebSphere Application Server V8.5.5, Fix Pack 13.
3) Upgraded BPM 8.6
We successfully applied the fix pack WAS 8.5.5.13, Switched JDK1.7 to 1.8 (8.0.5.6) and then upgrade BPM 8.6.
After dmgr / nodeagent, JVM restarted, but we are unable to access any bpm consoles.
We see the following error in systemout.log and also unable to start the JMS Messaging Engine.
===========================================================================
[3/14/19 10:56:58:451 ] 0000008d exception E com.ibm.ws.wim.adapter.ldap.LdapConnection getDirContext
com.ibm.websphere.wim.exception.WIMSystemException: CWWIM4520E The 'javax.naming.CommunicationException: myldapserver.ibm.com:636 [Root exception is java.net.SocketException: Socket is not connected]' naming exception occurred during processing.
at com.ibm.ws.wim.adapter.ldap.LdapConnection.getDirContext(LdapConnection.java:1880)
at com.ibm.ws.wim.adapter.ldap.LdapConnection.search(LdapConnection.java:3136)
at com.ibm.ws.wim.adapter.ldap.LdapConnection.checkSearchCache(LdapConnection.java:3104)
at com.ibm.ws.wim.adapter.ldap.LdapConnection.search(LdapConnection.java:3294)
at com.ibm.ws.wim.adapter.ldap.LdapConnection.searchEntities(LdapConnection.java:3515)
[3/14/19 10:56:58:451 ] 0000008d exception E com.ibm.ws.wim.adapter.ldap.LdapConnection getDirContext
com.ibm.websphere.wim.exception.WIMSystemException: CWWIM4520E The 'javax.naming.CommunicationException: myldapserver.ibm.com:636 [Root exception is java.net.SocketException: Socket is not connected]' naming exception occurred during processing.
at com.ibm.ws.wim.adapter.ldap.LdapConnection.getDirContext(LdapConnection.java:1880)
at com.ibm.ws.wim.adapter.ldap.LdapConnection.search(LdapConnection.java:3136)
at com.ibm.ws.wim.adapter.ldap.LdapConnection.checkSearchCache(LdapConnection.java:3104)
at com.ibm.ws.wim.adapter.ldap.LdapConnection.search(LdapConnection.java:3294)
at com.ibm.ws.wim.adapter.ldap.LdapConnection.searchEntities(LdapConnection.java:3515)
[3/14/19 10:56:59:597 ] 0000008d SibMessage E [BPM.BPMsampleT05.Bus:BPMmessageT01.000-BPM.BPMsample05.Bus] CWSIP0002E: An internal messaging error occurred in com.ibm.ws.sib.processor.impl.MessageProcessor, 1:123:1.233.3.2, com.ibm.ws.sib.security.users.UncheckedUserRepositoryException: USER_REPOSITORY_GET_USER_INFO_FAILED_CWSII0260E at com.ibm.ws.sib.security.impl.UserImpl.loadUniqueName(UserImpl.java:340) at com.ibm.ws.sib.security.impl.EntityImpl.getUniqueName(EntityImpl.java:112) at com.ibm.ws.sib.security.auth.policy.BusAuthorizationPolicyFactory$UserAuthorisationLoader.lookupUniqueName(BusAuthorizationPolicyFactory.java:1127) at com.ibm.ws.sib.security.auth.policy.BusAuthorizationPolicyFactory$AuthorisationLoader.getNames(BusAuthorizationPolicyFactory.java:1055)
===========================================================================
Cause
Issue is caused by 3rd party tool appdynamics
Resolving The Problem
Removed the 3rd party jar & configuration from Generic JVM arguments
For example:
In the Administration Console select Servers
Expand Server Type and select WebSphere application servers
Click on the name of your server
Expand Java and Process Management and select Process Definition.
Under the Additional Properties section, click Java Virtual Machine.
Scroll down and locate the textbox for Generic JVM arguments
Expand Server Type and select WebSphere application servers
Click on the name of your server
Expand Java and Process Management and select Process Definition.
Under the Additional Properties section, click Java Virtual Machine.
Scroll down and locate the textbox for Generic JVM arguments
-javaagent:/opt/IBM/WAS/AppDynamics/javaagent.jar -Dappdynamics.agent.applicationName=IBM_BPM -Dappdynamics.agent.nodeName=MYNode -Dappdynamics.agent.tierName=BPMSERVER01 -Dappdynamics.agent.uniqueHostId=Myserver
Removed the above properties and restart the websphere.
Document Location
Worldwide
[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Component":"Security, JMS Message engine","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF016","label":"Linux"},{"code":"PF033","label":"Windows"}],"Version":"V8.5, V9.0","Edition":"Websphere Application Server ND & Standalone.","Line of Business":{"code":"LOB45","label":"Automation"}}]
Was this topic helpful?
Document Information
Modified date:
26 March 2019
UID
ibm10875680