Re: Weblogic 7.1 ..

Madhav,

We usually call matchManagedConnection with each connection request to give
the RAR an opportunity to validate that we are using an appropriate MC to
satisfy the connection request.

If you could send me a log, I can take a closer look.

Feel free to contact me offline about this.
Deb



>I have a question on the way Weblogic works with regard to connector and
>stateful session beans.
>
>
>
>I would appreciate any answer/s to this.
>
>
>
>I have the connection pool size set to 10. Weblogic obtains 10 managed
>connections initially. When the EJB method is invoked which invokes the
>connector to perform a method call on the EIS, Weblogic invokes
>ManagedConnectionFactory::matchManagedConnection and goes through the list
>of 10 Managed Connections and does not find anything.
>
>
>
>Weblogic then destroys the first ManagedConnection in the pool and
>allocates a new one, say MC1. So, the connection handle instance in the
>EJB is linked to ManagedConnection MC1 by a call to
>ManagedConnection::getConnection.
>
>
>
>After the EJB method call is over, Weblogic calls
>ManagedConnection::cleanup to return the ManagedConnection to the pool.
>
>
>
>The next time an EJB method is called, it does not seem to call
>ManagedConnectionFactory::matchManagedConnection to find the matches in
>the pool.
>
>
>
>Websphere does call ManagedConnectionFactory::matchManagedConnection and
>ManagedConnection::associateConnection
>
>to associate the ManagedConnection with the connection handle
>
>
>
>Is Weblogic performing some optimization here ? Should it not call
>ManagedConnectionFactory::matchManagedConnection and
>ManagedConnection::associateConnection ?
>
>
>
>Thanks in advance,
>
>Madhav
>
>
>
>
>
>
>
>