You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
http-nio-8032-exec-2 WARN admin 912x1017x1 g2ksfs 192.168.10.122 /rest/gadget/1.0/timeSince/generate [c.s.j.s.container.servlet.WebComponent] A servlet request, to the URI http://quicksilver:8032/luciano-GHS33058/rest/gadget/1.0/timeSince/generate?projectOrFilterId=project-10000&periodName=daily&daysprevious=30&dateField=created&isCumulative=true&width=782&height=521&inline=true&_=1455901927829, contains form parameters in the request body but the request body has been consumed by the servlet or a servlet filter accessing the request parameters. Only resource methods using @FormParam will work as expected. Resource methods consuming the request body by other means will not work as expected. 19-Feb-2016 15:12:12.286 WARNING [http-nio-8032-exec-14] com.sun.jersey.spi.container.servlet.WebComponent.filterFormParameters A servlet request, to the URI http://quicksilver:8032/luciano-GHS33058/rest/gadget/1.0/timeSince/generate?projectOrFilterId=project-10000&periodName=daily&daysprevious=30&dateField=created&isCumulative=true&width=782&height=521&inline=true&_=1455901932275, contains form parameters in the request body but the request body has been consumed by the servlet or a servlet filter accessing the request parameters. Only resource methods using @FormParam will work as expected. Resource methods consuming the request body by other means will not work as expected.
I saw a ticket with JIRA and it is solved in JRASERVER-59898 but I'm recently facing same kind logs in my confluence DC instances. Is anyone familiar with this or facing same kind of issue please let me know how to resolve it.