Log Viewer not refreshing logs

Issue #481 resolved
Mukkamalla, Suryatej created an issue

When I go to my log viewer and click Refresh, the logs are not updated with the latest ones from my connection. Instead, it still shows the same logs from a few months back. Is there some cache I need to clear out before new logs will be displayed?

Update: The refresh functionality works when I open the developer console in my org. But then, that kind of defeats the purpose of the log viewer. Unless I am misunderstanding the purpose of the log viewer.

Comments (8)

  1. Scott Wells repo owner

    Suryatej, there shouldn't be any caching in Illuminated Cloud, and I agree that you shouldn't have to go into Developer Console to get the logs to be updated. Can you see if there was any kind of an error in idea.log from the refresh attempt?

  2. Mukkamalla, Suryatej Account Deactivated reporter

    I checked the idea.log file and it is not updated when I do the Log refresh. The log is the same before and after I try the refresh.

  3. Scott Wells repo owner

    Suryatej, sorry, but I wasn't expecting idea.log to be updated on a refresh...I'm just wondering what activity you see in the log when you perform a refresh, in particular looking for things like errors or stack traces. Do you see anything useful?

  4. Scott Wells repo owner

    Okay, let's try this...add this to Help>Debug Log Settings:

    #com.illuminatedcloud.client.ForceComApiClient
    

    then close and reopen your project (or restart the IDE), and then try to refresh the log viewer. You should get quite a bit of debug logging from the SOAP API calls that look like:

    -------------------------------------- 
    2016-12-01 14:08:04,552 [97459564]   INFO - rService.PartnerApi.PartnerApi - Outbound Message
    ---------------------------
    ID: 3
    Address: https://scw-zpf-dev-ed.my.salesforce.com/services/Soap/u/38.0/00DE0000000djw4
    Encoding: UTF-8
    Http-Method: POST
    Content-Type: text/xml
    Headers: {Accept=[*/*], SOAPAction=[""]}
    Payload: ...
    -------------------------------------- 
    2016-12-01 14:08:04,771 [97459783]   INFO - rService.PartnerApi.PartnerApi - Inbound Message
    ----------------------------
    ID: 3
    Response-Code: 200
    Encoding: UTF-8
    Content-Type: text/xml;charset=UTF-8
    Headers: {content-type=[text/xml;charset=UTF-8], Date=[Thu, 01 Dec 2016 20:08:04 GMT], Expires=[Thu, 01 Jan 1970 00:00:00 GMT], Set-Cookie=[BrowserId=w5-NtPjbTk2fyla5lRIXOw;Path=/;Domain=.salesforce.com;Expires=Mon, 30-Jan-2017 20:08:04 GMT], Strict-Transport-Security=[max-age=31536000; includeSubDomains], transfer-encoding=[chunked]}
    Payload: ...
    

    Please send those to me so I can see what calls are being made to the server and what the responses look like. Feel free to email them to me if you'd prefer since they may contain some information about the contents of your org.

  5. Scott Wells repo owner

    I'm going to resolve this for now since the issue seems to be how Salesforce is responding to a SOQL query for ApexLog which was reproduced in Developer Console.

  6. Log in to comment