Hi all,
There's a serious bug in the SQLTransformer: a query gets executed, and
after that the results are sucked out of it. Now, the moment the query is
executed, its Connection is given back to the Pool it belongs is (which is
good). But, if this Connection is reused before the results are sucked out
of it, serious problems arise (genre NullPointerException).
The problem does not arise ATM with the Excalibur that is in C2 now, because
that also has a serious bug in it (which I will report and patch tomorrow to
the Avalon people).
I'm working on a solution for the SQLTransformer, but I need one piece of
information: can I trust C2 to execute recycle() or dispose() as soon as the
pipeline has ended executing? This would allow me to allocate a Connection
in the setup(), and throw it back in the Pool in the recycle() resp.
dispose().
Once this is solved, I will of course send the patch to the list, but I need
this information to be able to patch it.
Thanks a lot,
tomK
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
