It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

com.sun.jersey.spi.container.servlet.WebComponent.filterFormParameters filling my log file

26-Feb-2019 16:00:18.053 WARNING [http-nio-127.0.0.1-8080-exec-7] com.sun.jersey.spi.container.servlet.WebComponent.filterFormParameters A servlet request, to the URI https://jira-tds.ourdomain.ch/rest/gadget/1.0/project/filters?projectId=10301&_=1551192997312, 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.
26-Feb-2019 16:00:20.478 WARNING [http-nio-127.0.0.1-8080-exec-14] com.sun.jersey.spi.container.servlet.WebComponent.filterFormParameters A servlet request, to the URI https://jira-tds.ourdomain.ch/rest/gadget/1.0/project/reports?projectId=10301&_=1551192997313, 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.
26-Feb-2019 16:00:21.770 WARNING [http-nio-127.0.0.1-8080-exec-19] com.sun.jersey.spi.container.servlet.WebComponent.filterFormParameters A servlet request, to the URI https://jira-tds.ourdomain.ch/rest/gadget/1.0/project/reports?projectId=10100&_=1551192997314, 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 keep seeing these warnings in the catalina.out log, and they are filling it in big numbers.

Strangely I can't find much about it online about it - so I am worried to have dome something wrong. Does anybody know why they appear and/or how to solve the issue?

For your information, I use the "Projects" gadget in the System Dashboard.

 

Thank you

 

 

1 answer

2 votes
Andy Heinzer Atlassian Team Feb 28, 2019

You haven't done anything wrong.  It is a very common warning message to see in regards to many Jira versions.  There is a suggestion ticket about this issue over in JRASERVER-59898.  

There is a workaround on that ticket that explains how you can adjust the logging level in order to avoid seeing these:

Workaround

Change the logging level for the com.sun.jersey.spi.container.servlet.WebComponent class in the conf/logging.properties file by adding this line:

com.sun.jersey.spi.container.servlet.WebComponent.level = SEVERE

This will prevent the Warnings from being logged.

I would expect that you would then need to save that logging.properties file AND restart Jira for these settings to take effect.

I hope this helps.

Andy

nice info thx.

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted in Jira

Demo Den Ep. 7: New Jira Cloud Reports

Learn how to use two new reports for next-gen projects in Jira Cloud:  Cumulative flow diagram and Sprint burndown chart. Ivan Teong, Product Manager, Jira Software, demos the Cumulative ...

365 views 1 3
Join discussion

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you