<vendor>
We have found this is a very interesting problem. In theory, you should be
able to change the connection pool (specifically the connection URL) at
runtime. However, there are a few issues. How do you close down the
connections that are currently in use? So, how does the transition occur?
There is no mention of this in the specification, so each vendor is left to
decide this on their own.
I would like to hear a discussion on the 'correct' way to change such a
property on the fly, but I think the issue comes down to two items:
- If the connection changes, do existing transaction die immediately,
or does the connection survive until it returns to the cache?
- If multiple connections are used in the course of an execution
chain (assuming transaction attributes like 'requires new' are
in the middle of the chain, which URL does the secondary
connection use?
</vendor>
Jonathan
Sriram Krovvidi wrote:
>
> Hi,
>
> Is it possible to change the connection pool for a CMP Bean at runtime (
> dynamically )???
>
> Please let me know your thoughts on this .
>
> Regards,
> - Sriram Krovvidi
>
> ===========================================================================
> To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
> of the message "signoff EJB-INTEREST". For general help, send email to
> [EMAIL PROTECTED] and include in the body of the message "help".
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
