WARNING [https-jsse-nio-443-exec-55]

Alibek Malikov July 24, 2019

25-Jul-2019 10:02:22.203 WARNING [https-jsse-nio-443-exec-55] com.sun.jersey.spi.container.servlet.WebComponent.filterFormParameters A servlet request, to the URI https://jira.**********.uz/rest/issueNav/latest/preferredSearchLayout, 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.

 

What could be the problem, please help people who have encountered problems of this type

1 comment

Steven F Behnke
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
July 24, 2019

This message is meaningless and is not meant for Server operators or administrators. Rather, this message is targeted toward Plugin Developers or Atlassian Developers, as it means something about the plugin is doing something strange. However, the 'strange thing' is quite literally harmless.

The issue is documented here and describes a clear workaround: https://jira.atlassian.com/browse/JRASERVER-59898

Alibek Malikov July 24, 2019

https://confluence.atlassian.com/display/JIRAKB/Jira+applications+stall+due+to+StackOverflowError+exception?utm_source=STP&utm_medium=logScan

 

There is also such a mistake, I understood how it seems to me what the problem was yesterday I added this script to the business process through the script runner:

import com.atlassian.jira.component.ComponentAccessor
import com.atlassian.jira.event.type.EventDispatchOption
import com.atlassian.jira.issue.fields.CustomField
import com.atlassian.jira.user.ApplicationUser

ApplicationUser currentUser = ComponentAccessor.getJiraAuthenticationContext().getLoggedInUser()
def cf = ComponentAccessor.customFieldManager.getCustomFieldObject(11100L); //Наблюдатели
def arrayOfComponents = issue.getComponents();
def userList = getCustomFieldValue(issue,11100L)?:[];

for(def comp in arrayOfComponents){
if(comp.getName()=="ТШТТ"){
userList += [getUser("sh.gaibnazarova")];
}
if(comp.getName()=="ТШТТ"){
userList += [getUser("s.hakimov")];
}
}

issue.setCustomFieldValue(cf, userList.collect{it})
ComponentAccessor.getIssueManager().updateIssue(currentUser, issue, EventDispatchOption.ISSUE_UPDATED, false)


ApplicationUser getUser(String userName){
return ComponentAccessor.getUserManager().getUserByName(userName)
}
def getCustomFieldValue(issue, Long fieldId) {
issue.getCustomFieldValue(ComponentAccessor.customFieldManager.getCustomFieldObject(fieldId))
}

Alibek Malikov July 24, 2019

QIP Shot - Screen 004.pngQIP Shot - Screen 003.pngQIP Shot - Screen 002.pngthis is scrins

Steven F Behnke
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
July 25, 2019

You should provide the actual error that is being printed in your log files -- You know there's a stackoverflow apparently, but you haven't provided your stacktrace for us to see...

Usually a stacktrace points right to the problem.

Alibek Malikov July 29, 2019

Where can I look stacktrace points to provide you with information?

Comment

Log in or Sign up to comment
TAGS
AUG Leaders

Atlassian Community Events