Bugzilla – Bug 5778
GRAM2 audting: no error message on db update failure
Last modified: 2009-03-19 09:48:57
You need to
before you can comment on or make changes to this bug.
Database: MySql 4.1.22
In GRAM4, when the database is not accessible, the audit logs never indicate
that a failure has occured. They look exactly the same as when successful.
I verified this under 2 conditions:
1. when the connection timeout occurred as described in
2. when I deliberately changed the password for the database in the
$GLOBUS_LOCATION//etc/gram-service/jndi-config.xml file to an invalid one.
An ERROR/SEVERE log message should be generated when this occurs.
I would like to note that this is also related to <a
*** This bug has been marked as a duplicate of bug 6400 ***