My Oracle Support Banner

Attempting To Create A Connection Factory With A JNDI Name That Already Exists: "eis/Ftp/FtpAdapter" (Doc ID 2491430.1)

Last updated on DECEMBER 07, 2021

Applies to:

Oracle SOA Suite - Version and later
Information in this document applies to any platform.


When  received below error while Activate changes from console after updating FtpAdapter:

Attempting to create a connection factory with a JNDI name that already exists: "eis/Ftp/FtpAdapter".

#### <[STANDBY] ExecuteThread: '43' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <[severity-value: 16] [rid: 0] [partition-id: 0] [partition-name: DOMAIN] > weblogic.application.ModuleException: weblogic.connector.exception.RAOutboundException: Attempting to create a connection factory with a JNDI name that already exists: "eis/Ftp/FtpAdapter".
at weblogic.application.internal.ExtensibleModuleWrapper.activate(
at weblogic.application.internal.flow.ModuleListenerInvoker.activate(
at weblogic.application.internal.flow.ModuleStateDriver$
at weblogic.application.internal.flow.ModuleStateDriver$
at weblogic.application.utils.StateMachineDriver.nextState(
at weblogic.application.internal.flow.ModuleStateDriver.activate(
at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(
at weblogic.application.internal.BaseDeployment$
at weblogic.application.utils.StateMachineDriver.nextState(
at weblogic.application.internal.BaseDeployment.activate(
at weblogic.application.internal.SingleModuleDeployment.activate(
at weblogic.application.internal.DeploymentStateChecker.activate(
at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvok


To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

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