Weblogic 7.1 ..
Madhav Inamti <[email protected]> Fri, 21 Mar 2003 18:59:33 -0800
| Newsgroups | gmane.comp.java.sun.connector |
|---|---|
| Message-ID | <75C025AE395F374B81F6416B1D4BDEFBB088CC@mtv-corpmail.microfocus.com> |
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