Custom OIM Client Fail to Communicate With OIM Weblogic Servers. IllegalStateException: Can't Find partitionName (Doc ID 2619742.1)

Last updated on DECEMBER 16, 2023

Applies to:

Symptoms

Application uses a custom OIM Client code which makes a call oracle.iam.platform.OIMClient.login() to connect to OIM.
URL used to connect to OIM Servers is of the form: URL= t3s://host1:port1, host2:port2

This issue started after upgrading OIM and Weblogic from 11g to 12c upgrade of OIM. 

The installation was then patched with <Patch:29146184> UNABLE TO CONNECT BY T3 PROTOCOL TO FEW BACKEND WEBLOGIC SERVERS
on top of weblogic 12.2.1.3.0 but it didn’t fix the issue.

Error reported as :

javax.security.auth.login.LoginException: java.lang.IllegalStateException: Can't find partitionName for URL: t3s://Host:Port
at weblogic.rjvm.RJVMImpl.setUser(RJVMImpl.java:576)
at weblogic.security.auth.Authenticate.authenticate(Authenticate.java:174)
at weblogic.security.auth.login.UsernamePasswordLoginModule.login(UsernamePasswordLoginModule.java:188)
at sun.reflect.GeneratedMethodAccessor82.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at javax.security.auth.login.LoginContext.invoke(LoginContext.java:755)
at javax.security.auth.login.LoginContext.access$000(LoginContext.java:195)
at javax.security.auth.login.LoginContext$4.run(LoginContext.java:682)
at javax.security.auth.login.LoginContext$4.run(LoginContext.java:680)

Cause

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