Thanks for your reply, Jagadish. I'll make a change to my code to work with
the new behavior.
> -----Original Message-----
> From: Jagadish.Ramu_at_Sun.COM [mailto:Jagadish.Ramu_at_Sun.COM]
> Sent: Monday, March 23, 2009 04:48
> To: dev_at_glassfish.dev.java.net
> Cc: Frank Kieviet
> Subject: Re: JCA question: when is ManagedConnection.cleanup() called?
>
> Hi Frank,
> Yes, this was done based on the following bug and the discussion.
>
> https://glassfish.dev.java.net/issues/show_bug.cgi?id=3682
>
> http://forums.java.net/jive/thread.jspa?messageID=235026
>
> Thanks,
> -Jagadish
>
>
>
> On Fri, 2009-03-20 at 13:14 -0700, Frank Kieviet wrote:
> > Hi,
> >
> >
> >
> > Migrating some JCA tests from v2 to v2.1, I noticed some differences
> > in behavior. It appears that in v2, ManagedConnection.cleanup() was
> > being called by GlassFish as soon as the adapter sends a
> > ConnectionEvent.CONNECTION_CLOSED event to GlassFish. In v2.1 it
> > appears that this call is being delayed until the transaction is
> > committed. Am I mistaken?
> >
> >
> >
> > TiA, Frank
> >
> >
> >
> >