DatabaseLogin Authentication Cache Problem

[talgolan]

Greetings:

After what seemed like an eternity, I finally got DatabaseLogin working for my web applications!

However, I have noticed that making a change to the database, say, to a user's password, does not seem to be being "picked-up" by the DatabaseLogin mechanism unless, of course, the JBoss server is restarted, and/or the web application is restarted.

It appears as though the login information is being cached somewhere.

Does anyone have any guidance for me?

Also, how do I tell JBoss to provide me with some logging for my database connections and the login mechanism.

Thanks to whomever might be able to help.

Regards,

Tal

[petertje]

> It appears as though the login information is being
> cached somewhere.

That is correct.
You can flush the cache using a JMX call on the jboss jaas security manager.
If you search this forum, you'll easily find a few code examples of how to achieve that.

Hth
Peter.

[talgolan]

Thank Peter.

I have found the following code snippet in the JBoss Admin Manual (pg. 297)...

MBeanServer server = ...;
String jaasMgrName = "jboss.security:service=JaasSecurityManager";
ObjectName jaasMgr = new ObjectName(jaasMgrName);
Object[] params = {domainName};
String[] signature = {"java.lang.String"};
server.invoke(jaasMgr, "flushAuthenticationCache", params, signature);

However, for the life of me, I cannot figure out...

a) What imports I need to make this work, and
b) What completes line 1 "MBeanServer server = ...;"

Any suggestions?

[shafei]

Try

MBeanServer server = (MBeanServer)
MBeanServerFactory.findMBeanServer(null).get(0);

hth

[talgolan]

Thank you, that did the trick.

Much appreciated.

Tal