Talking about Connection Pooling, I wonder what really happens when a
Connection that has already been open, is passed as a parameter from an EJB
to another EJB's method. I guess that, even though the two beans run in the
same container, the call is handled as if it were a remote call: can anyone
confirm on this? If so, the Connection should be sent to the invoked method
as a serialized copy of the Connection object living in the calling method.
How does this affect the Connection Pooling? Is the number of connections
in use increased by one when the one passed as a parameter is used or are
they considered to be the same connection towards the database? What happens
to the first connection if the one in the invoked method is closed?
Thanks in advance,
MJ
> There are many examples on the web. and if you search this archive
> you will find some references to them.
>
> Also You can look at Poolman for an example and Java code to perform
> database pooling.
>
> Also You can also Look at our open source JSP kit at www.jspinsider.com.
>
> In the kit I have generic code which shows you how to modularize your
> approach so you can use any connection pooling software. The Kit is still
> beta software but it serves as an practical example of what you
> are looking for.
===========================================================================
To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff JSP-INTEREST".
For digest: mailto [EMAIL PROTECTED] with body: "set JSP-INTEREST DIGEST".
Some relevant FAQs on JSP/Servlets can be found at:
http://java.sun.com/products/jsp/faq.html
http://www.esperanto.org.nz/jsp/jspfaq.html
http://www.jguru.com/jguru/faq/faqpage.jsp?name=JSP
http://www.jguru.com/jguru/faq/faqpage.jsp?name=Servlets
