Well bad news,
I begin working with 4.2.1-GA, and it works as bad as 4.0.5
I'm pretty sure I'm making a mistake somewhere, can anybody give
me a clue where to look for.
Really I can't believe there is no error-message in logs or clients.
Stick a profiler on your code to figure out where the memory is being used, but my guess is it's the application rather than the transaction engine. 4.0.5 and 4.2.1 have different default transaction implementations and the chances of both of them leaking memory in the same way are slim.
Well YOU WERE RIGHT,
I worked wonderfully well in 4.2.1, I simply started de 4.0.5 instance and
supposed was the 4.2.1 one, so that was the reason of the same behaviour.
Everything is working just fine,
Thank you for make me test again,