Java.lang.IllegalArgumentException: Failed to properly unregister

(Doc ID 1158065.1)

Last updated on APRIL 04, 2018

Applies to:

Oracle Weblogic Server - Version 9.2 to 10.3.3
Information in this document applies to any platform.
***Checked for relevance on 9-Aug-2013***


When you have JDBC connection pool name same as application name in config.xml we are running into the issue.

Steps to reproduce:

1. Create JDBC connection pool named 'SLA'.
2. Deploy an application with same name 'SLA' as JDBC connection pool in admin console.

Deployment is successful but you can find error in server log and stdout.

And if you reboot WebLogic Server and the first time you login to AdminConsole, the Error appears to the Server log and Stdout.

<Jul 16, 2010 10:40:50 AM EDT> <Warning> <JMX> <BEA-149517> <An attempt was made to unregister an mbean that was already unregistered:>
<Jul 16, 2010 10:40:50 AM EDT> <Error> <Deployer> <BEA-149250> <Unable to unprepare application 'SLA'.
at weblogic.application.internal.flow.ApplicationRuntimeMBeanFlow.unprepare(
at weblogic.application.internal.BaseDeployment$1.previous(
at weblogic.application.utils.StateMachineDriver.previousState(
at weblogic.application.utils.StateMachineDriver.previousState(
at weblogic.application.internal.BaseDeployment.unprepare(
Truncated. see log file for complete stacktrace


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