RESUME OPERATION FOR FILE EG FAILS IF WLS CONSOLE IS LOCKED (Doc ID 967478.1)

Last updated on JANUARY 04, 2016

Applies to:

Oracle WebLogic Integration - Version 10.2 to 10.3
Information in this document applies to any platform.

Symptoms

The WLI console doesn't have the lock and edit option. The resume operation for a File EG will implicitly deploy/redeploy the application jar associated with File EG.

The resume operation throws following exception if it is called while the WLS console is locked.
<Error> <Deployer> <BEA-149181> <Deployment Service encountered error while aborting the edit session before start. Initiator for this edit session is 'principals=[kernel identity = -1207246132]'. Error is
weblogic.management.provider.EditNotEditorException: Not edit lock owner
at weblogic.management.provider.internal.EditAccessImpl.checkEditLock(EditAccessImpl.java:120)
at weblogic.management.provider.internal.EditAccessImpl.undoUnactivatedChanges(EitAccessImp l.java:851)

 

<Warning> <Deployer> <BEA-149124> <Failures were detected while initiating deploy task for application 'WLIFileEG_cce111'. Error is: 'Waited 0 @ milliseconds'>
<Error> <WLI-Core> <BEA-489003> <Caught Exception: javax.management.InstanceNotFoundException: WLIFileEG_cce111
at weblogic.deploy.api.internal.utils.JMXDeployerHelper.getAppDeployment(JMXDeployerHelper.java:491)
at com.bea.wli.mbconnector.util.EGDeployerUtils.resumeGenerator(EGDeployerUtils.java:653)
at com.bea.wli.eventgenerators.file.FileEventGenerators.execAction(FileEventGenerators.java:560)
at com.bea.wli.eventgenerators.EventGenerators.resumeGenerators(EventGenerators.java:307)
at com.bea.wli.eventgenerators.EventGenerators.handleSuspendResumeResetEvent(EventGenerators.java:155)
Truncated. see log file for complete stacktrace


Releasing the lock from the WLS console and the subsequent attempt to resume the EG from the WLI console results in the associated thread going into stuck state.

<Error> <WebLogicServer> <BEA-000337> <[STUCK] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)' has been busy for "615" seconds working on the request "Http Request: /wliconsole/wliconsole.portal", which is more than the configured time (StuckThreadMaxTime) of "600" seconds. Stack trace:
java.lang.Object.wait(Native Method)
java.lang.Thread.join(Thread.java:1095)
java.lang.Thread.join(Thread.java:1148)
com.bea.wli.mbconnector.util.DeploymentProgressHelper.wait(DeploymentProgressHelper.java:30)
com.bea.wli.mbconnector.util.EGDeployerUtils.resumeGenerator(EGDeployerUtils.java:650)
com.bea.wli.eventgenerators.file.FileEventGenerators.execAction(FileEventGenerators.java:560)

Cause

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