Groovy log UI updates stop after some time, don't resume until after a restart

Hi!

thanks.. if you clear the groovy log via its right-click menu, does the logging pick up again in these situations?

regards,

/Ole
eviware.com

No, it just stays cleared, even if I run a different test case.

Hi Mr. McDonald,


Could you run soapUI by executing the soapUI run script from the command line?

That way you should be able to see standard output where additional logging messages and then you would be able to provide us with extra information when Groovy logging stops. I suspect this could be a bug in log4j, the underlying logging library.

Thank you in advance!


Cheers!
/Nenad Nikolic a.k.a. Shonzilla

I ran a long test (the output was nearly 29000 lines) from the command line like this:

    testrunner.bat -sTestSuite -cTestCase -r -j -f C:\test\ -o -i project.xml

and redirected the output to a file. All Groovy log statements were in the output, so this only seems to happen in the UI.

On thing to note, some of the log output is extremely long, say 2500 chars with embedded CRs. Could that adversely affect on the UI behavior?

- Michael

I've seen the same issue.  The Groovy log stops working at some point.  Requires restart of SoapUI.

Hi,

the upcoming nightly build of the 3.0 beta should fix this (we've had a hard time reproducing..), please let us know if this is (or is not) the case..

regards!

/Ole
eviware.com

I now see all entries in the Groovy logs in the UI.

Thanks.

This issue still occurs for us.  After two or three runs of a suite, the Groovy Log stops updating.

I have seen this too.

Hello,

I set up a loop in groovy but can not reproduce it. If you notice this happens can you provide us with more data?

robert