Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Cookie issue

Has anyone seen the following error? Any feedback is helpful:


at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$ Source)
at org.apache.tomcat.util.threads.TaskThread$
at Source)

10-Jan-2018 10:05:49.230 INFO [http-nio-8090-exec-2] org.apache.tomcat.util.http.LegacyCookieProcessor.processCookieHeader Cookies: Invalid cookie. Value not a token or quoted value
Note: further occurrences of Cookie errors will be logged at DEBUG level.


I don't know if it has something to do with cookie settting.  I don't want to change the setting and then this impact user logins. 

1 comment

Will Masters
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
May 09, 2018

Hi Nik, this issue is commonly caused by a client that is sending invalid cookie data. This means that either the cookie is incorrect or that the clients browser has a fault in the way it is setting the cookie.

It will continue sending it until the cookie expires or the cookies are cleared by the user, or the server sends a set-cookie header that clears that cookie.

The log information you have shown is at the level of INFO so unless you have a specific issue that connects it to an error in Confluence it’s merely informative of the first scenario.

It’s possible to change Tomcat’s CookieProcessor settings, to relax or adjust the interpretation of the cookie specifications, in this case however I would first try to track or log which user or client is causing this message, identify if there is an issue with the cookie or with Confluence to avoid disrupting existing users by making any server-side changes.

Kind regards,



Log in or Sign up to comment
AUG Leaders

Atlassian Community Events