IBM Support

How to check pending changes in the WebLogic admin server while doing the DC configuration.

Technical Blog Post


Abstract

How to check pending changes in the WebLogic admin server while doing the DC configuration.

Body

When configuring the WebLogic server with ITCAM for J2EE v7.1.1.0.5 agent/DC, you may encounter wait/timeout errors in the itm_config.log logfiles.  This happens because there are some open lock sessions still in the open/pending state.  This typically happens when you have multiple sessions open or you may have other teams accessing the WebLogic admin console and making changes, and these pending changes have not been activated yet.  Thus, if the lock has not been cleared, the configuration is failing when accessing the WLS admin server to add the ITCAM parameters as it times out to initiate the configuration.   You will see errors in the logs that look like this:

  weblogic.management.mbeanservers.edit.EditTimedOutException: weblogic.management.provider.EditWaitTimedOutException: Waited 300000 milliseconds

        at weblogic.utils.StackTraceDisabled.unknownMethod()

Caused by: weblogic.management.provider.EditWaitTimedOutException: Waited 300000 milliseconds

        ... 1 more

 

So, there are several ways to rectify this. 
1. From WebLogic Admin console, select "View changes and restarts" at the top left corner of the page in the "Change Center" box. See if there is anything listed under "Change List" and "Restart Checklist" tabs.
2. Try running wlst with the following commands on the Admin Server machine.  For example,
> wlst
wlst:/offline > connect ('Weblogic', 'xxxxx(password')
Connecting to t3://localhost:7001 with userid weblogic ...
Successfully connected to Admin Server "AdminServer" that belongs to domain "PT_Recover_domain".
wlst:/PT_Recover_domain/serverConfig > cmgr=getConfigManager()
wlst:/PT_Recover_domain/serverConfig > edit()
wlst:/PT_Recover_domain/edit > startEdit()
wlst:/PT_Recover_domain/edit > showChanges()

Check if this allows the edit session to be opened without creating any errors.

The best thing would be to save the changes in the Admin Console, and then restart the server.  Then redo the DC configuration again and it should work now.

 

 

Good luck. Smile

Noel Lewis

ITCAM / APM / ICAM L2 Support team

 

Tutorials Point

 

Subscribe and follow us for all the latest information directly on your social feeds:

 

 

image

 

image

 

image

 

 

  

Check out all our other posts and updates:

Academy Blogs:https://goo.gl/U7cYYY
Academy Videos:https://goo.gl/FE7F59
Academy Google+:https://goo.gl/Kj2mvZ
Academy Twitter :https://goo.gl/GsVecH


image

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"","label":""},"Component":"","Platform":[{"code":"","label":""}],"Version":"","Edition":"","Line of Business":{"code":"","label":""}}]

UID

ibm11084473