|
Problem IC64787
|
Status: Closed |
IBM DATA SERVER DRIVER FOR JDBC 3 MAY NOT LOAD IN JRE 5.0+ WHEN USING SECURITY MANAGER. |
| product: |
DB2 FOR LUW / DB2FORLUW / 950 - DB2 |
| Problem description: |
All connectivity types: On IBM Data Server Driver for JDBC and
SQLJ driver version 3.53.95 (which was bundled with DB2 for
Linux, Unix, and Windows v9.5 Fixpack 4) and above, a
java.security.AccessControlException can occur when loading the
JDBC driver The application must use the Java SecurityManager,
and not allow reflection privileges to the application for the
error to occur.
When sending or receiving data as a DECFLOAT data type, a
java.security.AccessControlException may occur on all IBM Data
Server Driver for JDBC and SQLJ driver versions 3.0+ and
4.0-4.3. Like the problem above, this exception can only occur
when connecting to a database which supports the DECFLOAT data
type while running Java 5.0+ on the client, and the application
uses the Java SecurityManager and does not allow reflection
privileges to the application. This problem has now been
resolved.
This problem has already been resolved in driver versions
4.3.111 (which was bundled with DB2 for Linux, Unix, and Windows
v9.5 Fixpack 4) and above. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* N/A *
****************************************************************
* PROBLEM DESCRIPTION: *
* All connectivity types: On IBM Data Server Driver for JDBC *
* and SQLJ driver version 3.53.95 (which was bundled with DB2 *
* for Linux, Unix, and Windows v9.5 Fixpack 4) and above, a *
* java.security.AccessControlException can occur when loading *
* the JDBC driver The application must use the Java *
* SecurityManager, and not allow reflection privileges to the *
* application for the error to occur. *
* *
* When sending or receiving data as a DECFLOAT data type, a *
* java.security.AccessControlException may occur on all IBM *
* Data Server Driver for JDBC and SQLJ driver versions 3.0+ *
* and 4.0-4.3. Like the problem above, this exception can *
* only occur when connecting to a database which supports the *
* DECFLOAT data type while running Java 5.0+ on the client, *
* and the application uses the Java SecurityManager and does *
* not allow reflection privileges to the application. This *
* problem has now been resolved. *
* *
* This problem has already been resolved in driver versions *
* 4.3.111 (which was bundled with DB2 for Linux, Unix, and *
* Windows v9.5 Fixpack 4) and above. *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 Version 9.5 Fix Pack 5. *
**************************************************************** |
| Local Fix: |
n/a |
| available fix packs: |
DB2 Version 9.5 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
Problem was first fixed in Version 9.5 Fix Pack 5. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 25.11.2009
23.04.2010
23.04.2010 |
| Problem solved at the following versions (IBM BugInfos) |
9.5.FP5
|
| Problem solved according to the fixlist(s) of the following version(s) |
