Hi Michael,
ULCLoad collects all errors in the "Errors" node of the tree in the
left side of the GUI. If the error message is larger than 200k then
instead of the error message only a brief warning is displayed.
In order to see the full error message you can instruct ULCLoad to
write all error messages (including the ones that are larger than
200k) into its log file. To do so just add the following line to the
<LOAD_HOME>/ui/bin/jmeter.properties file:
log_level.com.ulcload.jmeter=DEBUG
By default ULCLoad stores all configured log messages in the
<LOAD_HOME>/ui/bin/jmeter.log file.
Moreover, before starting the test you can choose what kind of thread
behavior you want if an error occurs.
BTW, for guaranteed response time to your post kindly use
ulc-premium-support list. In my opinion you should have access to it as
your company must have purchased it.
Thanks and regards,
Janak
-----------------------------------------
Janak Mulani
email: [email protected]
url: http://www.canoo.com <http://www.canoo.com/>
Beyond AJAX - Java Rich Internet Applications
http://www.canoo.com/ulc
-----------------------------------------
________________________________
From: [email protected]
[mailto:[email protected]] On Behalf Of Meyer-Geerken
Michael (KSLD 621)
Sent: Wednesday, March 31, 2010 9:42 PM
To: [email protected]
Subject: [ULC-developer] Response too large to be displayed
In our current Test case we often get the following Error:
----
Response too large to be displayed (1749906 bytes).
----
(size in Bytes Value naturally does vary)
This happens at a place of a major but not very great Gui change.
Usually this action works if done in the Browser. Response time at this
action is generally low, but in other cases with longer response times we
don't have such Issues.
As this Error most of the times stops the executing thread and
seting it on 'continue' is not realy an option, we would like to have more
Information than this Error Message.
Is there any knowledge regarding such Errors in ULC Load?
Is there a known workaround to get such cases going again?
Is there a way to do further dumping of information (beanshell
listener maybe) ?
Any Idea would be welcome!
Thanks &
Best Regards
Michael MG
_______________________________________________
ULC-developer mailing list
[email protected]
http://lists.canoo.com/mailman/listinfo/ulc-developer
