Hi Dan,
Thank you for info, in spite of the fact that it makes me upset:
it is so easy to forget to put conn.close() to the finally block.
Such bug hardly can be noticed during testing, and when at long last
you get "Login failed", it is hard to find the exact place of the bug.
Best regards,
Oleg
Dan OConnor wrote:
DO> Hi Oleg,
DO> The specification does not prohibit a component from saving a
DO> connection instance. In fact, although the preferred resource-
DO> usage pattern is acquire-use-release within a single business
DO> method, a number of notification callbacks in the EJB specification
DO> seem to exist primarily to enable acquiring and freeing resources
DO> across business method calls. We are required to support this
DO> behavior to be compliant.
DO> -Dan
DO> On 27 Sep 00, at 18:52, Oleg Nitz wrote:
>> If somebody knows for sure the answer to the following question,
>> please, tell me.
>> Can a bean get Connection instance during one method call and store in
>> a bean instance field for use in subsequent calls of this or other
>> methods?
>> I understand that in any case that would be a bad practice,
>> and I know why.
>> But if the specification strongly prohibits it, I think that jBoss
>> could collect such garbage Connections after the method ends and
>> return them to the pool.
>>
>> Best regards,
>> Oleg Nitz
>>
>>
>>
>>
>> --
>> --------------------------------------------------------------
>> To subscribe: [EMAIL PROTECTED]
>> To unsubscribe: [EMAIL PROTECTED]
>> Problems?: [EMAIL PROTECTED]
>>
DO> --
DO> --------------------------------------------------------------
DO> To subscribe: [EMAIL PROTECTED]
DO> To unsubscribe: [EMAIL PROTECTED]
DO> Problems?: [EMAIL PROTECTED]
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
