problem creating user in RDBMS realm Using com.bea.wlpi.rdbmsrealm.RDBMSRealm
Girish Gupte
Girish Gupte
Girish Gupte
Hi,
I turned on the caching realm through the WLS Console, (Security).
After this I get a very unusual error, which seems to be comming
from the RDBMS implementation class (from WLI 2.0 SP2 distribution).
Here is the msg that I get while WLS server boots (the WLS server boots ok, but
WLPI does not initialize) ....
Unable to initialize WebLogic Process Integrator:
SQL Exception: ResultSet not open, operation 'next' not permitted. Verify that
autocommit is OFF.
at c8e.k.j.l_(Unknown Source)
at c8e.k.j.l_(Unknown Source)
at c8e.k.j.j_(Unknown Source)
at c8e.k.n.checkIfClosed(Unknown Source)
at c8e.k.n.movePosition(Unknown Source)
at c8e.k.n.movePosition(Unknown Source)
at c8e.k.n.next(Unknown Source)
at com.bea.wlpi.rdbmsrealm.RDBMSDelegate.getGroup(RDBMSDelegate.java:425)
at com.bea.wlpi.rdbmsrealm.RDBMSRealm.getGroup(RDBMSRealm.java:235)
at weblogic.security.acl.CachingRealm.getGroup(CachingRealm.java:1120)
at weblogic.ejb20.deployer.SecurityRoleMapping.lookupPrincipal(SecurityRoleMapping.java:243)
at weblogic.ejb20.deployer.SecurityRoleMapping.getSecurityRolePrincipals(SecurityRoleMapping.java:96)
at weblogic.ejb20.deployer.SecurityRoleMapping.getSecurityRolePrincipals(SecurityRoleMapping.java:128)
at weblogic.ejb20.deployer.SecurityRoleMapping.isPrincipalInAnyRole(SecurityRoleMapping.java:174)
at weblogic.ejb20.deployer.MethodInfoImpl.checkAccess(MethodInfoImpl.java:214)
at weblogic.ejb20.internal.MethodDescriptor.checkAccess(MethodDescriptor.java:285)
at weblogic.ejb20.internal.BaseEJBObject.preInvoke(BaseEJBObject.java:90)
at weblogic.ejb20.internal.StatelessEJBObject.preInvoke(StatelessEJBObject.java:55)
at com.bea.wlpi.server.plugin.PluginManagerCfgBeanEOImpl.init(PluginManagerCfgBeanEOImpl.java:1301)
at com.bea.wlpi.server.initlistener.InitListenerBean.onMessage(InitListenerBean.java:151)
at weblogic.ejb20.internal.MDListener.execute(MDListener.java:221)
at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:175)
at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:1933)
at weblogic.jms.client.JMSSession.execute(JMSSession.java:1892)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
at weblogic.kernel.Kernel.execute(Kernel.java:250)
at weblogic.jms.client.JMSSession.pushEnvelope(JMSSession.java:1779)
at weblogic.jms.client.JMSCallback.pushEnvelope(JMSCallback.java:69)
at weblogic.jms.frontend.FESession.execute(FESession.java:1972)
<Aug 22, 2001 11:56:01 AM MDT> <Notice> <WebLogicServer> <WebLogic Server started>
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
--------------- nested within: ------------------
com.bea.wlpi.rdbmsrealm.RDBMSException: caught SQL exception - with nested exception:
[SQL Exception: ResultSet not open, operation 'next' not permitted. Verify that
autocommit is OFF.]
at com.bea.wlpi.rdbmsrealm.RDBMSRealm.getGroup(RDBMSRealm.java:242)
<Aug 22, 2001 11:56:01 AM MDT> <Notice> <WebLogicServer> <ListenThread listening
on port 7101>
at weblogic.security.acl.CachingRealm.getGroup(CachingRealm.java:1120)
at weblogic.ejb20.deployer.SecurityRoleMapping.lookupPrincipal(SecurityRoleMapping.java:243)
at weblogic.ejb20.deployer.SecurityRoleMapping.getSecurityRolePrincipals(SecurityRoleMapping.java:96)
at weblogic.ejb20.deployer.SecurityRoleMapping.getSecurityRolePrincipals(SecurityRoleMapping.java:128)
at weblogic.ejb20.deployer.SecurityRoleMapping.isPrincipalInAnyRole(SecurityRoleMapping.java:174)
at weblogic.ejb20.deployer.MethodInfoImpl.checkAccess(MethodInfoImpl.java:214)
at weblogic.ejb20.internal.MethodDescriptor.checkAccess(MethodDescriptor.java:285)
at weblogic.ejb20.internal.BaseEJBObject.preInvoke(BaseEJBObject.java:90)
at weblogic.ejb20.internal.StatelessEJBObject.preInvoke(StatelessEJBObject.java:55)
at com.bea.wlpi.server.plugin.PluginManagerCfgBeanEOImpl.init(PluginManagerCfgBeanEOImpl.java:1301)
at com.bea.wlpi.server.initlistener.InitListenerBean.onMessage(InitListenerBean.java:151)
at weblogic.ejb20.internal.MDListener.execute(MDListener.java:221)
at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:175)
at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:1933)
at weblogic.jms.client.JMSSession.execute(JMSSession.java:1892)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
at weblogic.kernel.Kernel.execute(Kernel.java:250)
at weblogic.jms.client.JMSSession.pushEnvelope(JMSSession.java:1779)
at weblogic.jms.client.JMSCallback.pushEnvelope(JMSCallback.java:69)
at weblogic.jms.frontend.FESession.execute(FESession.java:1972)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
"Girish Gupte" <grg...@yahoo.com> wrote:
>
>
>
>Hi,
>I am currently using WLI 2.0 SP2 installation. Here is a very unusual
>thing I
>noticed. Can somebody tell me what is going on ???
>##########
>
>1 : I have set up the security realm as indicated in the config.xml file.
>As far
>as I understand, the caching realm entry has attribute pointing to the
>wlpiRDBMSRealm,
>which is a RDBMS implementation from the WLI 2.0 SP2 distribution.
>2: I start the server, open the WLS console, and create a new user through
>the
>console. I get no error message and it seems to work fine. ( I also click
>on the
>save it to database link, and it returns with msg that cache is refreshed
>).
>3: I see an entry in the fileRealm.properties file, but no record is
>inserted
>in the WLSUSER table in the database.
>
>Since the RDBMS realm (from WLI distribution) is defined as basic
>realm implementation, should it not insert entry into the database, instead
>of
>the file realm.
>Is this a general problem ( any RDBMS realm ) or is it specific to the
>WLI ?
>Is there anything that I have not configured here that is causing this
>behavior
>?
>Is it just refreshing the cache instead of inserting record in DB ?
>Why should it insert entry into fileRealm.properties ?
>
>Thanks,
>Girish
>