Forum Discussion
SmartBear_Suppo
Alumni
15 years agoHi Nate(?)
There's a bug in the Java Console that limit's the output length of thread dumps. If you could please do the following two things, it would help us troubleshoot the problem:
1. Edit a part of eviware/loadUI 1.5.0/log4j.xml from this:
to this:
2. Run eviware/loadUI 1.5.0/loadUItest.bat from a command line (e.g. cmd.exe) and press CTRL+Break when nothing has happened for a while.
We would appreciate it very much to get the output of this (what's printed to the command line).
Best Regards
Henrik
SmartBear Sweden
There's a bug in the Java Console that limit's the output length of thread dumps. If you could please do the following two things, it would help us troubleshoot the problem:
1. Edit a part of eviware/loadUI 1.5.0/log4j.xml from this:
<!-- =============== -->
<!-- Loggers -->
<!-- =============== -->
<logger name="com.eviware.loadui" additivity="false">
<level value="INFO" />
<appender-ref ref="CONSOLE" />
</logger>
to this:
<!-- =============== -->
<!-- Loggers -->
<!-- =============== -->
<logger name="com.eviware.loadui" additivity="false">
<level value="DEBUG" />
<appender-ref ref="CONSOLE" />
</logger>
2. Run eviware/loadUI 1.5.0/loadUItest.bat from a command line (e.g. cmd.exe) and press CTRL+Break when nothing has happened for a while.
We would appreciate it very much to get the output of this (what's printed to the command line).
Best Regards
Henrik
SmartBear Sweden