WLST Scripting Error - Must Activate Changes Bug

Question

I wrote a script to automate Weblogic deployments and during the undeploy and sometimes the deploy part of the script there is an error message that says, "The task cannot be processed further until the current edit session is activated. When this occurs, task processing will continue. The user can exit the deployer tool without affecting the task." When this happens I have to click the "Activate Changes" on the GUI of the admin console for the script to continue and do what I want it to do. Are there any WLST Jython programmers out there that know how to avoid this issue? I am trying to run the script without touching the GUI.

Also, sometimes the State of the managed server changes to 'deploy initializing'. When this happens I know that things are really messed up. I think this happens when I choose the other option "Undo All Changes".

score 1 · Answer 1 · answered Mar 22 '17 at 15:41

1

Its best to always do small bits, activate those changes and then proceed to the next task.

When doing an undeploy and deploy, its always better to undeploy, activate the change and then do a deploy and activate again, this way things remain clean else you may have conflicts when activating all changes in 1 go.

and no you dont have to activate from console, you can do from wlst using activate([timeout], [block])

answered Mar 22 '17 at 15:41

SridharS

893
4
8

1

@SridharS, can you provide an example code here ..? – Asanke Apr 03 '17 at 23:59
@SridharS, can you provide an example code here ..? I have the deploy(application, path, targets=servername) command executed from my python program.. which hangs up with the following log `[Deployer:149140]The task cannot be processed further until the current edit session is activated. When this occurs, task processing will continue. The user can exit the deployer tool without affecting the task..............................................................` – Asanke Apr 04 '17 at 00:05

score 1 · Answer 2 · edited Jun 23 '22 at 04:43

1

Ensure to commit one transaction per session. This way you would not miss your earlier undeploy/deploy status due to the issue incurred by current deploy/undeploy task. Please find sample code block below.

    app-list = [app1 app2 app3 ... app60]
    for app in app-list:
        edit()
        startEdit()
        app-path = "<path-to-your-apps>/" + app
        deploy(app, app-path, targets=<your-targets>)
        print 'deployed ' + app
        activate()

edited Jun 23 '22 at 04:43

abto

1,583
1
12
31

answered Mar 23 '17 at 15:38

Praveen Raj Kumar

198
1
7

@praveen-raj-kumar, can you provide an example code here ..? I have the deploy(application, path, targets=servername) command executed from my python program.. which hangs up with the following log `[Deployer:149140]The task cannot be processed further until the current edit session is activated. When this occurs, task processing will continue. The user can exit the deployer tool without affecting the task..............................................................` – Asanke Apr 04 '17 at 00:06
Added it to my original answer – Praveen Raj Kumar May 22 '17 at 10:40

Asanke · Accepted Answer · 2017-06-21T02:04:56.197

1

There is a good answer of code for this in this blog

edited Jun 21 '17 at 02:04

answered Apr 04 '17 at 16:21

Asanke

551
1
11
32

WLST Scripting Error - Must Activate Changes Bug

3 Answers3