Nati,
a quote from the weblogic documentation....
http://e-docs.bea.com/wls/docs81/upgrade/upgrade70to81.html#1059093
hope this helps
Connection Proxy Wrapper
When a connection request is made, WebLogic Server returns to the client
(via the resource adapter) a Proxy object that wraps the connection
object. WebLogic Server uses this proxy to provide features that assist
applications using the WebLogic Server implementation of the J2EE
Connector Architecture. These features include (1) connection leak
detection capabilities and (2) late XAResource enlistment when a
connection request is made before starting a global transaction that
uses that connection.
If the connection object returned from a connection request is cast as a
Connection class, a ClassCastException can occur. This exception is
caused by either (1) the resource adapter doing the cast or (2) the
client doing the cast during a connection request.
In WebLogic Server 8.1, an attempt is made to detect the
ClassCastException caused by the resource adapter case (1) above. If the
server detects that this cast is failing, it turns off the proxy wrapper
feature and proceeds by returning the connection object during a
connection request (unwrapped). The server logs a warning message to
indicate that the proxy wrapper has been turned off. When this type of
cast failure occurs, connection leak detection and late XAResource
enlistment features are also turned off (but currently no indication of
this is given in the Console monitoring).
Note: WebLogic Server attempts to detect the ClassCastException by
acting as a client using container-managed security. Doing so requires
the resource adapter to be deployed with security credentials defined.
If the client is doing the cast and getting a ClassCastException, the
customer (client) code can be modified as follows:
Example: The client is casting the connection object to MyConnection.
Instead of MyConnection being a class that implements the resource
adapter's Connection interface, modify it to be an interface that
extends Connection.
Implement a MyConnectionImpl class that implements the MyConnection
interface.
Nati Shalom
<[EMAIL PROTECTED] To: [EMAIL PROTECTED]
.COM> cc:
Sent by: A Subject: JCA exception with web logic
mailing list for
Enterprise
JavaBeans
development
<[EMAIL PROTECTED]
A.SUN.COM>
24/07/2003 01:55
Please respond to
Nati Shalom
Hi All
I'm trying to deploy a JCA implementation into WL 8.1.0.0
>From some reason I got the following exception:
"<Jul 24, 2003 1:13:11 AM IDT> <Warning> <Connector> <BEA-190083> <Proxy
test failed. WLS will not use connection proxies for resource adapter
"eis/GigaSpacesCF"
.>"
WL Exception Description:
"The "jndiName" The resource adapter attempted to cast the WLS connection
proxy to a class or an interface not implemented by the proxy and got a
java.lang.ClassCastException (java.lang.ClassCastException). Late
transaction enlistement and leak and idle detection will be turned off for
this resource adapter"
The JCA that I'm trying to deploy support JCA1.1 version.
Have any one seen this exception before ?
Any help would be mostly appreciated.
Thanks
Nati S.
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
