Jira Service Desk: Error creating a ticket via service desk

Austin Cooper October 11, 2019

Moving from Jira Cloud to Jira Server 8.4.2 and Service Desk 4.2.2 on local host machine.

I have created a staging Jira server with service desk, software and core applications to support my current cloud setup.

Setup of docker container works as expected.

docker run --name jira-staging --detach --network host --mount source=jiraVolume,destination=/var/atlassian/application-data/jira -p 8080:80 atlassian/jira-software:8.4.2

And connecting to mysql database is functioning as expected.

Issues arise when I am trying to get the Jira Service Desk project to create a ticket

I receive a 

Error

Your request could not be created. Please check the fields have been correctly filled in.

The jira docker logs state

11-Oct-2019 12:44:30.383 WARNING [http-nio-8080-exec-4] com.sun.jersey.spi.container.servlet.WebComponent.filterFormParameters A servlet request, to the URI http://fgc-ubuntu02:8080/rest/servicedesk/1/customer/pages/portal/3/create/10, 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-Oct-2019 12:44:41.297 WARNING [http-nio-8080-exec-1] com.sun.jersey.spi.container.servlet.WebComponent.filterFormParameters A servlet request, to the URI http://fgc-ubuntu02:8080/rest/webResources/1.0/resources, 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-Oct-2019 12:44:41.511 WARNING [http-nio-8080-exec-10] com.sun.jersey.spi.container.servlet.WebComponent.filterFormParameters A servlet request, to the URI http://fgc-ubuntu02:8080/rest/activity-stream/1.0/preferences?_=1570797881235, 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.

0 answers

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events