I can see the following log entries very frequently in our confluence log:
2016-01-06 10:06:41,380 WARN [StreamsCompletionService::thread-54] [confluence.content.transform.ContentTransformationContext] getStack No request found. Need request to store the context stack.
-- url: /confluence/plugins/servlet/streams | userName: <user>
As far as I can tell it does not occur for all users on our Confluence instance, at least there are only a few usernames that appear in the latest log file.
I am unsure whether this has any effect on Confluence or usage - I haven't had any error reports from users, just trying to figure out what is going on.
Has anyone experienced this, or know what the cause is?
Our Confluence instance uses the JIRA user directory.
I found a couple of support tickets where the error, "No request found. Need request to store the context stack." was reported. Each instance had a different URL in the log as the URL that was being accessed. There were no cases with a clear explanation of the error and no cases with recent versions of Confluence. Plugins seemed to be the suspected culprits in the cases I reviewed.
If the URL in your error messages is similar to what was first posted in this thread, "/confluence/plugins/servlet/streams", then a good first step would be to clear the Confluence plugins cache as described in How to clear Confluence plugins cache
In the meantime, to help me narrow down the issue, please let me know:
I look forward to hearing more about the issue. If clearing the plugin cache fixes it please post back to this thread so people who search for the error can find the solution in the future.
thank you for the reply.
Clear the Plugins cache unfortanly don't work. The Warn message still appear. Here an example.
2017-11-29 10:00:40,886 WARN [StreamsCompletionService::thread-29280] [confluence.content.transform.ContentTransformationContext] getStack No request found. Need request to store the context stack. -- url: /plugins/servlet/streams | referer: https://##############/plugins/servlet/gadgets/ifr?container=atlassian&mid=2841145769984&country=DE&lang=de&view=default&view-params=%7B%22writable%22%3A%22false%22%7D&st=atlassian%3ARO6dWLFKwEDad6UwFmRCP577OQdZA7%2BsiD1VkLC7HTop3DJ6RbCIcsyD1IJ25cBx54BhTVhs0fEzmb2sr%2FMHGqPkBzryTfykwwddrqod3sqTFdWDD7Wh7bDrpl5W%2FmO8VXrrI8bRGaTusq8RIkgVQwcoMvIXKkp8tnTGvy12G2PAB6I872dJufcpvKwDYMlfm2x7lpZtn1fTW3J%2BO%2BGUzSmJntYRyHmorh9MEsfJsL%2FT1AwPJmRfO48hBedBxwRsrTmsdK%2BzH4T%2Bm6a%2FdlLhkeGqtSZNNEirn1zr70uEUDGuFG2pOe%2Buh7E9%2BL%2BipJtdGwDZjPLKBlB2uVqgfXvGDJSAtBEet7YfzJ9uKyTZsBo2ANlI&up_isConfigured=true&up_isReallyConfigured=false&up_title=Aktivit%C3%A4tsstrom&up_titleRequired=true&up_numofentries=10&up_refresh=false&up_maxProviderLabelCharacters=50&up_rules=&up_renderingContext=&up_keys=&up_itemKeys=&up_username=&url=https%3A%2F%2F#########%2Frest%2Fgadgets%2F1.0%2Fg%2Fcom.atlassian.streams.confluence%3Aactivitystream-gadget%2Fgadgets%2Fconf-activitystream-gadget.xml&libs=auth-refresh | traceId: e5c99eaa6c440aa7 | userName: ########
######## = URL or Username
Thanks and regards
I ran across this same issue in a case today and found that this appears to be log spam from the Scroll macro: https://k15t.jira.com/browse/VSN-3576
I would recommend trying the workaround listed at the link above from k15t:
Add new entry "com.k15t.scroll.runtime.confluence.content.transform.ContentTransformationContext" to "Logging and Profiling" with the log level "ERROR"
Please report back and let us know whether this helps.
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
Hi Community! Kesha (kay-sha) from the Confluence marketing team here! Can you share stories with us on how your non-technical (think Marketing, Sales, HR, legal, etc.) teams are using Confluen...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs