what is the current state with this issue?
That's an old one... This was fixed ages ago.
I believe it was a combination of my bad API usage (had forgotten to cleanup Global object) with an inability of reproducing the bug locally which lead to the assumption that this was a bug in XmlBlaster code. I think there had never been a problem like this since then.
regards,
Balázs