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

Resource methods consuming the request body by other means will not work as expected

Hi, I am getting this error.

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.

11 answers

I would open a bug with Atlassian - this looks similar to this one for Confluence. I wouldn't worry too much though - this looks like a wrong logging level and not a real problem with the system. If you don't experience any loss of functionality you can just live with it. If it's bothering you too much and Atlassian confirm that it's not really a problem, you can also permanently change the logging level for that particular package to ERROR - see here for instructions.

I am running JIRA (server) and recently setup, But in log file i am getting this error.

WARNING [http-nio-8080-exec-24] com.sun.jersey.spi.container.servlet.WebComponent.filterFormParameters A servlet request, to the URI http://test.example.com/rest/issueNav/1/issueTable/stable, 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.

If you just want to get rid of this warning-message see this issue: https://jira.atlassian.com/browse/JRASERVER-59898

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

After changing the file you must restart the application:

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.

Give us more details - where do you see this error and under what circumstances.

Hello, I am on Jira 7.3.3 and I am having the same issue. Are there any suggestions for fix?

Any solution of this issue, I'm on 7.3.3 and facing same issue 

30-May-2018 12:30:10.649 WARNING [http-nio-80-exec-24] com.sun.jersey.spi.container.servlet.WebComponent.filterFormParameters A servlet request, to the URI https://myweb.com/rest/issueNav/1/issueTable/stable, 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.
30-May-2018 12:30:17.623 WARNING [http-nio-80-exec-16] com.sun.jersey.spi.container.servlet.WebComponent.filterFormParameters A servlet request, to the URI https://myweb.com/rest/issueNav/1/issueTable/stable, 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.
30-May-2018 12:30:17.657 WARNING [http-nio-80-exec-4] com.sun.jersey.spi.container.servlet.WebComponent.filterFormParameters A servlet request, to the URI https://myweb.com/rest/issueNav/1/issueTable/stable, 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.

We're on 7.3.7 and we're getting this error right before the system crash. Not sure if it's related to the crash.

Found this page while investigating the cause of frequent JIRA crashes today. I'm testing some REST API calls, but cannot say yet if they are the cause. I do notice that the mentioned error message is the last entry before the JIRA process dies.

Any chance you were also working on REST API calls?

(On v7.5.1)

Like Noni Khutane likes this

We are having the same issue in logs . Any updates from Atlassian to fix the problem? 

Atlassian JIRA Project Management Software (v7.3.8#73019-sha1:94e8771) 

Same problem here

 

23-Jul-2018 15:05:21.870 WARNING [http-nio-8080-exec-25] com.sun.jersey.spi.container.servlet.WebComponent.filterFormParameters A servlet request, to the URI http://172.16.17.62:8080/rest/project-templates/1.0/templates, 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.

 

Cannot create new project using a template.

I have the same error and also can't create new project. Have you solved this question?

@viveksrai@All   I also had this  problem, but fixed it,  it is not an error,  this  is problem  with your network connect, i was using  Wifi for the network which my JIRA service desk running on my  local host,   after i start using cable connection  this problem  disappears

So  it means that you have a poor network connection,  you  need to  switch to a right network in which your instance is running.

Best!

Our instance is running on Azure , so I dont think it could be a network issue. We also get these  errors before Jira crashes or perfomance gets terribly slow.

@Noni KhutaneRunning your instance  on Azure cloud  does  not guarantee that you  cannot have network issues. In  my case  after i did run my instance in  a  good network(internet ) this problem  disappeared  completely. in  case  of performance the could  be lots  of reason see trouble shooting  here  https://confluence.atlassian.com/jirakb/troubleshooting-performance-problems-336169888.html

Like Noni Khutane likes this

@Noni Khutane Running mine on a datacenter. Same problem. Did you found a solution?
@Moses Thomas Running an instance in a cloud environment should give us peace. And why should we handle connection issues for jira? It just shouldn't crash.

@Sascha_Becker  Unfortunately we have not found a solution for this specific error. However, whenever we get this in our logs we usually monitor Jira closely and check if performance degrades or server resources get used up. Then we troubleshoot.

@Sascha_Becker  So  may be it is  time you  create a support ticket to Atlassian if you could  as @petrov  suggested

I just explain my own experience from  the server side and what i did for it to  disappeared.

@Moses Thomas  Thanks for the response. This worked for me.

Like Moses Thomas likes this

We are on Jira 8.2.1 self host. Our office closed for a few days, and hit this error in catalina.out when office re-opens. Crowd is running, and no one can log in as a result of this error.

Basically whenever our Jira users try to log in, this error will occur after clicking on Log In button.

Network shouldn't be an issue, as all other applications running on the same host is working fine.

 

Edit: found out it's other issue on our end. Ignore what we wrote.

So what did you find out? May be we have the same issue in our confluence install?

Suggest an answer

Log in or Sign up to answer
TAGS

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