Forum Discussion

holzbachw's avatar
holzbachw
Occasional Contributor
12 years ago

DEBUG in output.log

I installed loadUI 2.6.4 and after launching a successful load test I noticed that the output.log file grew rapidly to nearly 1GB with DEBUG level statements. As result, I continue to exit loadUI, delete the file, and then start loadUI. The output.log file is located under C:\Program Files\SmartBear\LoadUI-2.6.4
I examined log4j.xml and soapui-log4j.xml but, do not see any directive that mentions output.log.
How can I eliminate this unhelpful logging? Thanks

9 Replies

  • PM_r's avatar
    PM_r
    Icon for Staff rankStaff
    12 years ago
    Hmm... I'm not familiar with output.log, but I can see that this is a problem... could you post some rows from it to give us a clue on what this file is?

    Henrik
  • holzbachw's avatar
    holzbachw
    Occasional Contributor
    12 years ago
    Here is a sample. I can see that this is related to the test that I am running. I just don't know why this is being recorded. Thanks.
    08:02:58,381 DEBUG [HttpClientSupport$SoapUIHttpClient] Attempt 1 to execute request
    08:02:58,381 DEBUG [SoapUIMultiThreadedHttpConnectionManager$SoapUIDefaultClientConnection] Sending request: POST /scsms/executeservice HTTP/1.1
    08:02:58,381 DEBUG [HttpClientSupport$SoapUIHttpClient] Attempt 1 to execute request
    08:02:58,381 DEBUG [SoapUIMultiThreadedHttpConnectionManager$SoapUIDefaultClientConnection] Sending request: POST /scsms/dialogreport HTTP/1.1
    08:02:58,381 DEBUG [SoapUIMultiThreadedHttpConnectionManager$SoapUIDefaultClientConnection] Receiving response: HTTP/1.1 200 OK
    08:02:58,381 DEBUG [HttpClientSupport$SoapUIHttpClient] Connection can be kept alive for 3000000 MILLISECONDS
    08:02:58,381 DEBUG [HttpClientSupport$SoapUIHttpClient] Stale connection check
    08:02:58,381 DEBUG [TestCasePropertiesNode] 1setting property:
    08:02:58,381 DEBUG [TestCasePropertiesNode] setting property:_valueToOverride_Datetime, sent at Thu Sep 20 12:17:56 EDT 2012
  • holzbachw's avatar
    holzbachw
    Occasional Contributor
    12 years ago
    Here is the head of this output.log:
    Device "Mobile Intel(R) 4 Series Express Chipset Family" (\\.\DISPLAY1) initialization failed :
    WARNING: bad driver version detected, device disabled. Please update your driver to at least version 6.14.10.5303
    Device "Mobile Intel(R) 4 Series Express Chipset Family" (\\.\DISPLAY2) initialization failed :
    WARNING: bad driver version detected, device disabled. Please update your driver to at least version 6.14.10.5303

    .:::.
    .==:::::.
    .====:::::::.
    .======:::::::::.
    .========:::::::::::.
    .:=========:::::::::::::.
    .:::=========:::::::::::::::.
    :::::=========:::::::::::::::::
    :::::=========:::::::::::::::::
    ':::=========:::::::::::::::'
    ':======================'
    '==================='
    '==============='
    '==========='
    ':::::::'
    ':::'


    :: :: :: :: ::::
    :: :: :: :: ::
    :: :::: ::::: :::::: :: :: ::
    :: :: :: :: :: :: :: :: :: ::
    :::::: :::: ::: : :::::: ::::: ::::

    LoadUI 2.6.4


    LoadUI Home: C:\Documents and Settings\holzbachw\.loadui
    Launching LoadUI Build: INTERNAL 20131106-1445
    JavaFX2 bundle started!
    Configuring log4j from [C:\Program Files\SmartBear\LoadUI-2.6.4\soapui-log4j.xml]
    07:59:15,367 INFO [DefaultSoapUICore] initialized soapui-settings from [C:\Documents and Settings\holzbachw\soapui-settings.xml]
  • PM_r's avatar
    PM_r
    Icon for Staff rankStaff
    12 years ago
    Hmm... how do you launch LoadUI?

    It seems like you're launching it like this: loadui.exe > output.log.
  • holzbachw's avatar
    holzbachw
    Occasional Contributor
    12 years ago
    I launch loadUI by Start -> Programs -> SmartBear -> LoadUI 2.6.4 -> LoadUI
  • renatoathaydes's avatar
    renatoathaydes
    Contributor
    12 years ago
    If you're using a shortcut, check the shortcut's properties. LoadUI does not generate such file and you probably have some setting somewhere setting it. Try running LoadUI via the loadui.bat file and you'll probably confirm that this file will not be created.
  • holzbachw's avatar
    holzbachw
    Occasional Contributor
    12 years ago
    Still quite curious. The shortcut has no mention of output.log. I looked into Windows Environment variables but, did not see output.log.
    Finally, I launched as loadUI.bat >NUL. I no longer see output.log being created. I had been running loadUI 2.1.0 which did not produce that log. On Monday, I installed 2.6.4 and encountered the output.log. Next, I installed 2.6.3 which also produced the log. 2.1.0 still does not produce the log. I'll just make a mental note to run loadUI as shown.
  • holzbachw's avatar
    holzbachw
    Occasional Contributor
    12 years ago
    Still curious... Perhaps this is a clue?
    Found output.log in C:\Program Files\SmartBear\LoadUI-2.6.4\.install4j\i4jparams.conf
    Here is a snippet.

    <uninstallDelete>
    <entry name="jre/bin/server/classes.jsa" />
    <entry name="./error.log" />
    <entry name="./output.log" />
    <entry name="./error.log" />
    </uninstallDelete>
  • MSkog's avatar
    MSkog
    Icon for Staff rankStaff
    12 years ago
    Hi
    Thanks, you gave me just what i needed. And great news! i found the solution. It turned out that we had configured our launcher to output everything to output.log in the open source version. We didn't notice this when we looked for this problem in the PRO version. Thanks for reporting this. The next release of LoadUI will not have this problem!

    Regards,
    Max