OSB Batch Deployment Is Not Being Activated Due To 'weblogic.management.provider.EditNotEditorException' (Doc ID 3008463.1)

Last updated on MARCH 11, 2024

Applies to:

Symptoms

One of our non-prod environment is failing deploying huge number of OSB applications in a single session. I'm seeing below errors:

1. weblogic.management.mbeanservers.edit.NotEditorException: weblogic.management.provider.EditNotEditorException: Not edit lock owner

2. <Feb 29, 2024 6:39:36,069 PM MST> <Warning> <JMX> <BEA-149513> <JMX Connector Server stopped at service:jmx:iiop://<HOST_NAME>:<PORT>/jndi/weblogic.management.mbeanservers.editsession.DOMAIN.ServiceBus.>

3. com.bea.wli.sb.transports.TransportException: Deployment Failed: weblogic.management.ManagementException: [Deployer:149166]Deployments cannot be triggered through configuration updates and through the Deployment APIs simultaneously.
  at com.bea.wli.sb.transports.TransportException.newInstance(TransportException.java:214)
  at com.bea.wli.sb.transports.jms.JmsTransportProvider.makeWLSChangesOnCreate(JmsTransportProvider.java:256)

I have tried adding below argument to Admin server startup but did not help:

-Dcom.bea.wli.config.deployment.WlsEditSessionTimeout=3600

Changes

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.