Mailing-List: contact geronimo-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: geronimo-dev@incubator.apache.org
Date: Wed, 5 May 2004 16:36:20 -0700
Subject: Re: MultiPoolConnectionInterceptor.SubjectCRIKey fix
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v553)
From: David Jencks <david@coredevelopers.net>
To: geronimo-dev@incubator.apache.org
Content-Transfer-Encoding: 7bit
In-Reply-To: <07258F4244D6F649B1A78993D070B7CA0122D30E@ACSPMXE02>
Message-Id: <032CCEC6-9EED-11D8-844F-003065F4889C@coredevelopers.net>

?? SubjectCRIKey does implement hashCode().  Does your implementation 
of ConnectionRequestInfo implement it properly?  Please provide more 
details. In particular, are you using container managed security (i.e. 
a Subject) or application managed security (i.e ConnectionRequestInfo)?

BTW does the version of your patches I applied to the openejb jdbc 
wrapper work for you?

thanks
david jencks

On Wednesday, May 5, 2004, at 02:58 PM, Hamilton Verissimo de Oliveira 
(Engenharia - SPO) wrote:

>
> I'm experiencing some memory leaks with Geronimo JCA implementation. 
> While
> I'm trying to find out where is the problem I saw another minor 
> problem:
>
> SubjectCRIKey must overrides hashCode. If not the getConnection will 
> always
> create new pools:
>
>     public void getConnection(ConnectionInfo connectionInfo) throws
> ResourceException {
>
>         <...>
>
>         SinglePoolConnectionInterceptor poolInterceptor = null;
>         synchronized (pools) {
>             poolInterceptor = (SinglePoolConnectionInterceptor)
> pools.get(key);
>
>
> Maybe that is the reason of the memory leak. Anyway, still digging...
>
>
> Regards,
> hammett
>