Using Java Studio Creator Shortfin, build an app using IBM DB2 drivers. At
design time they are used in Type 4 (pure Java), as are almost all other drivers.
However, when the same application is deployed to Glassfish, the container
attempts to load the drivers as Type 2 (requiring native libraries). That's a
holdover from an earlier time, and is almost never the right thing to do.
Among other things, different libraries are required for each platform, and do
not exist at all for certain platforms.
This is controlled by adding a property to the Connection Pool, driverType=4.
That should be set by default on any deployment that uses the DB2 drivers.
The appserver's documentation seems to indiacte it supports only Type2 drivers.
The plugin uses this as kind of a master list for its mappings.
So if this is the case, we cannot use type 4 as the default.
Being J2ee certified is a big process, and I guess type 4 either was not
certified or maybe introduced CTS failures...
Moving ot RFE. Please, escalate if needed for VWP.
Do we set the driverType in the CP property list or do we let the server select the default?
If we don't... maybe we should. I agree that we should set it to the value the server would use to pass CTS. By
setting it, we make it easier for a user to discover it and leverage driverType=4, if THEY decide that they want to do this?
Also... this issue is over two years old.... what is the CURRENT status for of this in a 9.1/DB2 environment?
Please be ready to discuss this issue on 2008/10/22
no bug should be assigned to issues. distributing the load.