Fw: EJB and J2C Connector Problem

What made the difference here was that I had to mark the Resource Reference
for my resource adapter in the EJB Deployment Descriptor as "Unshareable".
When I did that the ManagedConnection.cleanup() method was no longer called
when the ejbCreate() method exited.

Thanks,
DW
----- Original Message -----
From: "John Pickler" <[email protected]>
To: <[email protected]>
Cc: "John Pickler" <[email protected]>
Sent: Wednesday, August 27, 2003 1:30 PM
Subject: EJB and J2C Connector Problem


> I have a written a J2EE Connector Architecture 1.0 Resource Adapter for
> my company along with some sample customer applications.  I have several
> applications in which I need a stateful session bean to create a
> connection through my resource adapter, and then have the client be able
to
> call the methods on that EJB instance with that same connection.  The
reason
> they need to be the same connection is so that the work done on my ERP
> server (which is what my resource adapter talks to) will be recognized as
> one single, related user session on the ERP side.  However, I've done
> significant debugging in WebSphere 5.0.2 (my company's platform of
choice),
> and I am finding that although the connection is being created
> (by me) in the ejbCreate() method, the container is calling my
> ManagedConnection.cleanup() method after the ejbCreate() method is
finished,
> which of course terminates the connection.  I need this connection to stay
> live across multiple Interaction.execute() calls on my resource adapter.
> Any ideas on how I accomplish this?  Am I doing something wrong?
>
> Thanks,
> DW

===========================================================================
To unsubscribe, send email to [email protected] and include in the body
of the message "signoff CONNECTOR-INTEREST".  For general help, send email to
[email protected] and include in the body of the message "help".