nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Log error http-nio-8080-exec- ERROR /rest/service/1.0/project/listByIssueId.json [c.o.r.plugin.util

P_0jen30

I keep seeing this error message in atlassian-jira.log with the number at the end of http-nia-8080-exec- ranging from 2 all the way to 30. But the overall message is still the same.

I would like to know what exactly the cause of this error is and how can I resolve it.

I know (well, i think..) it is not related to actual application login attempts because my username shows up as well in the logs while I'm logged in trying to investigate the issue.

Excerpt of the logs, with usernames removed:

2019-10-07 10:57:06,201 http-nio-8080-exec-17 ERROR <username> 657x31445x1 1qvia7a 192.168.3.6 /rest/service/1.0/project/listByIssueId.json [c.o.r.plugin.util.RestClient] Login Failed

2019-10-07 10:57:06,898 http-nio-8080-exec-7 ERROR <username> 657x31461x2 12zrv7u 172.28.4.81 /rest/service/1.0/project/listByIssueId.json [c.o.r.plugin.util.RestClient] Login Failed

2019-10-07 10:57:08,561 http-nio-8080-exec-5 ERROR <username> 657x31469x1 1qvia7a 192.168.3.6 /rest/service/1.0/project/listByIssueId.json [c.o.r.plugin.util.RestClient] Login Failed

2019-10-07 10:57:13,891 http-nio-8080-exec-28 ERROR <username> 657x31485x2 1qvia7a 192.168.3.6 /rest/service/1.0/project/listByIssueId.json [c.o.r.plugin.util.RestClient] Login Failed

2019-10-07 10:57:25,412 http-nio-8080-exec-10 ERROR <username> 657x31662x2 12zrv7u 172.28.4.81 /rest/service/1.0/project/listByIssueId.json [c.o.r.plugin.util.RestClient] Login Failed

2019-10-07 10:57:25,658 http-nio-8080-exec-13 ERROR <username> 657x31694x1 12zrv7u 172.28.4.81 /rest/service/1.0/project/listByIssueId.json [c.o.r.plugin.util.RestClient] Login Failed

2019-10-07 10:58:10,334 http-nio-8080-exec-8 ERROR <username> 658x31775x1 1ynzcfc 172.28.4.123 /rest/service/1.0/project/listByIssueId.json [c.o.r.plugin.util.RestClient] Login Failed

2019-10-07 10:58:25,961 http-nio-8080-exec-18 ERROR <username> 658x31787x2 1qvia7a 192.168.3.6 /rest/service/1.0/project/listByIssueId.json [c.o.r.plugin.util.RestClient] Login Failed

2019-10-07 10:58:59,293 http-nio-8080-exec-6 ERROR <username> 658x31821x1 1ynzcfc 172.28.4.123 /rest/service/1.0/project/listByIssueId.json [c.o.r.plugin.util.Res

Accepted answers

Tinker Fadoua

Are you able to access Jira?
What is the most recent change you made in the instance that triggered this error?
You can also check catalina.out to get more information about the error.
Are the users appearing on the log unable to access Jira?

Any details will help.

Best,

Fadoua

All comments

Tinker Fadoua

Are you able to access Jira?
What is the most recent change you made in the instance that triggered this error?
You can also check catalina.out to get more information about the error.
Are the users appearing on the log unable to access Jira?

Any details will help.

Best,

Fadoua

P_0jen30

@Tinker Fadoua

I have access, so do most of the users.

The most recent change was i upgraded from 7.5.0 to 7.13.8 last week, but i think i saw these messages already in the logs prior to me upgrading.

Also im wondering if it could be tied to some plugins that are currently incompatible?

Catalina.out:

08-Oct-2019 11:37:11.978 WARNING [http-nio-8080-exec-53] com.sun.jersey.spi.container.servlet.WebComponent.filterFormParameters A servlet request, to the URI http://jira.XXXXXX.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.
com.optimizory.rmsis.plugin.exception.JiraSyncException: Login Failed
at com.optimizory.rmsis.plugin.util.RestClient.getResponse(RestClient.java:105)
at com.optimizory.rmsis.plugin.util.RestClient.getRMsisResponse(RestClient.java:48)
at com.optimizory.rmsis.plugin.service.RequirementManagerImpl.getResponse(RequirementManagerImpl.java:215)
at com.optimizory.rmsis.plugin.service.RequirementManagerImpl.getLinkedEntitiesByIssueId(RequirementManagerImpl.java:192)
at com.optimizory.rmsis.plugin.service.RequirementManagerImpl.getLinkedEntitiesByIssueIdAPI(RequirementManagerImpl.java:233)
at sun.reflect.GeneratedMethodAccessor1331.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at com.atlassian.plugins.rest.common.interceptor.impl.DispatchProviderHelper$ResponseOutInvoker$1.invoke(DispatchProviderHelper.java:192)
at com.atlassian.plugins.rest.common.interceptor.impl.DispatchProviderHelper$1.intercept(DispatchProviderHelper.java:83)
at com.atlassian.plugins.rest.common.interceptor.impl.DefaultMethodInvocation.invoke(DefaultMethodInvocation.java:53)
at com.atlassian.plugins.rest.common.expand.interceptor.ExpandInterceptor.intercept(ExpandInterceptor.java:34)
at com.atlassian.plugins.rest.common.interceptor.impl.DefaultMethodInvocation.invoke(DefaultMethodInvocation.java:53)
at com.atlassian.plugins.rest.common.interceptor.impl.DispatchProviderHelper.invokeMethodWithInterceptors(DispatchProviderHelper.java:110)
at com.atlassian.plugins.rest.common.interceptor.impl.DispatchProviderHelper$ResponseOutInvoker._dispatch(DispatchProviderHelper.java:190)
at com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
at com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)
at com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
at com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
at com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
at com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)
at com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542)
at com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473)
at com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419)
at com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1409)
at com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:409)

I am seeing this error message a lot in there.

Tinker Fadoua

Did you test make the same upgrade in a test environment before doing it in Production ?
Disable all incompatible plugins even though when it is a plugin issue the application won't start
Also when reading the logs you should mainly be concerned by SEVERE or ERROR. Warnings are usually not bad.

Please take a look at the logs again and check for errors.

Best,

Fadoua

P_0jen30

@Tinker Fadoua

I did test this upgrade in a test environment prior to performing it in PROD.

Here are the most Recent SEVER errors in catalina.out:

06-Oct-2019 17:27:50.851 SEVERE [localhost-startStop-2] org.apache.catalina.loader.WebappClassLoaderBase.checkThreadLocalMapForLeaks The web application [ROOT] created a ThreadLocal with key of type [org.picocontainer.DefaultPicoContainer.IntoThreadLocal] (value [org.picocontainer.DefaultPicoContainer$IntoThreadLocal@4b94faf8]) and a value of type [java.lang.Class] (value [class org.picocontainer.ComponentAdapter$NOTHING]) but failed to remove it when the web application was stopped. Threads are going to be renewed over time to try and avoid a probable memory leak.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

server

jira

jira-software

jira-software-server

atl-gruland

access

log

error