Could you please do some 'kill -3' (Unix) or 'Ctrl-Break' (Windows) when it happens and send me the thread dumps?release notes says version 1.1 2005-12-22
after some time of running ok, xmlBlaster starts to use 100% cpu time, but it's logging output seems to be doing nothing significant.
restarting xmlBlaster resolves the problem.
Has anyone else seen this kind of problem?
thanks Marcel