Useless CORAL loops retrying to login if password is expired (ORA-28001).
This has been reported by Salvatore (thanks!), originally in
Date: Wed, 26 Jan 2011 17:47:42 +0100
From: Salvatore Di Guida <email@example.com>
To: Salvatore Di Guida <firstname.lastname@example.org>,
Andrea Valassi <Andrea.Valassi@cern.ch>,
Giacomo Govi <email@example.com>,
Vincenzo Innocente <firstname.lastname@example.org>,
Alexander Kalkhof <email@example.com>,
Alexander Loth <Alexander.Loth@cern.ch>,
Raffaello Trentadue <firstname.lastname@example.org>
Subject: [bug #76166 Review session exceptions and their use in connection
Follow-up Comment #2, bug #76166 (project pool):
I have just found another case where CORAL does not behave correctly. When trying to connect to an account with expired password, ORACLE throws an ORA-28001; this is catched by the ORACLE session, which throws a StartSessionException, so, after a given time, it retries to log in, and so on forever. I have realized that the only authentication error you catch and rethrow, then stopping to retry, is the ORA-01017 (wrong username/password), mapped through AuthenticationFailureException. In attachment, a test executable which I used for reproducing the error...