PQ74400: ADD THE SUPPORT OF INFRASTRUCTURE TO MAKE VENDOR-SPECIFIC CALLS TO WAS 4.0 RELEASE SUCH AS ADDING NEW CLASS CALL WSCALLHELPER(). | |||||||||||||||||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||||||||||||||||
![]() APAR status Closed as program error. Error description Customer need to use the Oracle 9i defined type XMLType in connection pooling which is not supported in WAS 4.0 now.Local fix The current work around for the customer is to access Oracle directly and bypass connection pooling.Problem summary **************************************************************** * USERS AFFECTED: WebSphere Application Server users who need * * to invoke vendor specific methods (methods * * outside of the JDBC specification) on * * WebSphere managed JDBC objects, or pass * * vendor specific objects to methods. This * * includes Connections, Statements, * * PreparedStatements, CallableStatements, * * and ResultSets. * **************************************************************** * PROBLEM DESCRIPTION: The WebSphere managed JDBC objects * * comply to the JDBC 2.0 specification. * * * * Attempts to invoke methods outside of * * this specification will require casting * * a WebSphere managed object to a vendor * * specific object. This will result * * in a ClassCastException at runtime. * * * * Attempts to pass a WebSphere managed * * object to a method which expects a * * vendor * * method will also result in a * * ClassCastException. * **************************************************************** * RECOMMENDATION: * **************************************************************** Because WebSphere provides managed JDBC objects, and wrappers the objects provided by the JDBC provider, an application was previously unable to invoke methods not included in the JDBC specification on a WebSphere managed object. Due to requests by multiple customers for access to these vendor specific functions, it has been decided to add a mechanism within WebSphere to enable customers to invoke these methods.Problem conclusion A new static class has been added to the WebSphere runtime. com.ibm.ejs.cm.proxy.WSCallHelper contains a static jdbcCall method to allow an application to call a method on the underlying vendor object and static jdbcPass methods to allow an application to pass the underlying vendor object to another method. See the JavaDoc for the WSCallHelper class (packaged with the fix) for more information on calling these methods. These methods use reflection to invoke the method on the underlying vendor class. While every effort was made to make this perform in the best way possible, reflection is an expensive operation, and should only be used when there are no other alternatives to perform the required operation. These methods should only be used to invoke methods outside of the JDBC specification. Attempts to invoke JDBC methods through this mechanism will result in SQLExceptions. WARNING: Use of these methods causes the JDBC object to be used outside of WebSphere's protective mechanisms. Performing certain operations (such as setting autoCommit, or transaction isolation settings, etc.) outside of these protective mechanisms will cause problems with the future use of this pooled object. IBM does not guarantee stability of the object after invocation of these methods, it is the user's responsibility to ensure that invocation of these methods does not perform operations which harm the object. Use at your own risk.Temporary fix Comments
APAR is sysrouted FROM one or more of the following: PQ69520 APAR is sysrouted TO one or more of the following: Modules/Macros
Publications Referenced
|
Product categories: Software > Application Servers >
Distributed Application & Web Servers > WebSphere Application
Server > General
Operating system(s):
Software version: 00W
Software edition:
Reference #: PQ74400
IBM Group: Software Group
Modified date: May 21, 2003
(C) Copyright IBM Corporation 2000, 2008. All Rights Reserved.