Deployment API And "Automatically Acquire Locks And Activate Changes"
Last updated on NOVEMBER 05, 2016
Applies to:Oracle WebLogic Server - Version 10.3 and later
Information in this document applies to any platform.
When the "Automatically Acquire Lock and Activate Changes" flag is set on the Preferences page of the Admin Console, and an attempt is made to deploy or undeploy an application using the WebLogic APIs as described in Listing 4-2 of the "Oracle WebLogic Server: Programming WebLogic Deployment 10g Release 3 (10.3)" document, the ProgressObject continues to have a status of "running," and the handleProgressEvent() method of the ProgressListener never gets called. In other words, the code hangs.
The loss of functionality is that the user application is actually a console extension where a code hang would make the use case unworkable. The standalone API will work if the user does not log into the console. The expected result is that the application can be deployed from the API.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms