Problem accessing DB from Custom RoleMapper

Question

I've built a custom implementation of the RoleMapper class, and everything works
fine except for one thing... when the server is booted, I must first access the
WL console in order for the RoleMapper to be called, else the WL server crashes
back to a command prompt with no error log messages ... complete WL failure.
A little history on how it works - basically, the code is taken from the WL8 RoleMapper
example posted on dev2dev. However, in my RoleMapperDatabase class, I have code
to connect to an oracle database to retrieve the roles. Whenever a lookup is
done, I try to grab a DataSource object from the JNDI tree, and as soon as I get
a valid one I cache it in the class for future use. This gets around the problem
of failure when the server is first coming up, because the rolemapper initialize
gets called before the db datasource is bound to the jndi tree. the lookup is
pretty standard, something like:
ic.lookup("dsROLESDB")
This call works fine, as long as the first time its hit is from the WL console.
If I start WL server, then hit another webapp which causes a role lookup to happen,
the ic.lookup line fails to the point of crashing the server. Im assuming the
problem fix has something to do with being logged in as admin when the call happens,
but Im not sure... either way it shouldnt bring down the whole server...
Does anyone have any suggestions on implementing database access from within a
rolemapper?
Thanks in advance...
Chris

Answer 1

"Chris" <[email protected]> wrote in message
news:3f97f9fb$[email protected]..
>
>
I've built a custom implementation of the RoleMapper class, and everythingworks
fine except for one thing... when the server is booted, I must firstaccess the
WL console in order for the RoleMapper to be called, else the WL servercrashes
back to a command prompt with no error log messages ... complete WLfailure.
>
A little history on how it works - basically, the code is taken from theWL8 RoleMapper
example posted on dev2dev. However, in my RoleMapperDatabase class, Ihave code
to connect to an oracle database to retrieve the roles. Whenever a lookupis
done, I try to grab a DataSource object from the JNDI tree, and as soon asI get
a valid one I cache it in the class for future use. This gets around theproblem
of failure when the server is first coming up, because the rolemapperinitialize
gets called before the db datasource is bound to the jndi tree. thelookup is
pretty standard, something like:
ic.lookup("dsROLESDB")
This call works fine, as long as the first time its hit is from the WLconsole.
If I start WL server, then hit another webapp which causes a role lookupto happen,
the ic.lookup line fails to the point of crashing the server. Im assumingthe
problem fix has something to do with being logged in as admin when thecall happens,
but Im not sure... either way it shouldnt bring down the whole server...
By calling ic.lookup, you are most likely creating a recursive situation as
ic.lookup is going
to require security to be evaluated which is going to come back to your role
mapper.
You may be able to utilize the identity from initialization and then do a
runAs before
invoking the ic.lookup. We are thinking about having the security provider
code always invoked
with kernel identity.