HttpSession destroyed

[duely]

Does anyone have users that has a high login count value? I noticed from my server logs in atlassian-jira-security.log, that anonymous creates HttpSession, but the user destroy the sessions. This occurs frequently and has inflated the login count value for the user in JIRA User Management.

Here's an example:

2018-12-10 18:40:23,242 http-nio-8080-exec-10232 anonymous 1120x8418373x1 - 87.100.100.100,25.25.25.55 /rest/api/2/search HttpSession created [zgmwkp]

2018-12-10 18:40:23,964 http-nio-8080-exec-10232 johndoe 1120x8418373x1 zgmwkp 87.100.100.100,25.25.25.55 /rest/api/2/search HttpSession [zgmwkp] destroyed for 'johndoe'

Here's a log of session being destroyed:

2018-12-10 18:40:17,382 http-nio-8080-exec-10267 johndoe 1120x8418352x1 17bjr9e 87.100.100.100,25.25.25.55 /rest/api/2/field HttpSession [17bjr9e] destroyed for 'johndoe'
2018-12-10 18:40:18,478 http-nio-8080-exec-10216 johndoe 1120x8418353x1 1xquqic 87.100.100.100,25.25.25.55 /rest/api/2/search HttpSession [1xquqic] destroyed for 'johndoe'
2018-12-10 18:40:19,369 http-nio-8080-exec-10182 johndoe 1120x8418358x1 1xyug8o 87.100.100.100,25.25.25.55 /rest/api/2/search HttpSession [1xyug8o] destroyed for 'johndoe'
2018-12-10 18:40:20,283 http-nio-8080-exec-10263 johndoe 1120x8418360x1 13ire5g 87.100.100.100,25.25.25.55 /rest/api/2/search HttpSession [13ire5g] destroyed for 'johndoe'
2018-12-10 18:40:21,202 http-nio-8080-exec-10159 johndoe 1120x8418361x1 geraro 87.100.100.100,25.25.25.55 /rest/api/2/search HttpSession [geraro] destroyed for 'johndoe'
2018-12-10 18:40:22,140 http-nio-8080-exec-10284 johndoe 1120x8418363x1 p0bjiv 87.100.100.100,25.25.25.55 /rest/api/2/search HttpSession [p0bjiv] destroyed for 'johndoe'
2018-12-10 18:40:23,060 http-nio-8080-exec-10248 johndoe 1120x8418370x1 1ptk7ka 87.100.100.100,25.25.25.55 /rest/api/2/search HttpSession [1ptk7ka] destroyed for 'johndoe'
2018-12-10 18:40:23,964 http-nio-8080-exec-10232 johndoe 1120x8418373x1 zgmwkp 87.100.100.100,25.25.25.55 /rest/api/2/search HttpSession [zgmwkp] destroyed for 'johndoe'
2018-12-10 18:40:24,220 http-nio-8080-exec-10235 johndoe 1120x8418375x1 6rk2pg 87.100.100.100,25.25.25.55 /rest/api/2/search HttpSession [6rk2pg] destroyed for 'johndoe'

Notice that the session destroyed has multiple entries within a minute. These session destroy gets tallied into the user login count value.

[Richard]

Hi, we have the same behavior here with JIRA 8.5.1 and it seems to create performance issues. More investigation on the way.

[Richard]

We found out that a user had an RSS Feed configured with his uname / pwd. It was sending requests to JIRA constantly.

We changed the refresh delay.

[Josh Steckler]

Http Sessions without associated logins are usually in my experience related to monitoring tools.

Users that have very high session counts are usually in my experience using the REST API for something. I would suspect this is what is happening for you.

[PS]

Hi @josh , @duely 

Gone through an application outage for 2 hours and could not find the solution. we killed the process and the application started coming up. What is the issue can anyone help.  its an urgency

Error Message"

2020-04-29 16:54:18,339 http-nio-8080-exec-29 anonymous 1014x1214535x19 - 10.208.45.220,10.208.45.227 /plugins/servlet/streams HttpSession created [qdfo81]

2020-04-29 16:54:34,131 http-nio-8080-exec-29 jirasystem 1014x1214535x19 qdfo81 10.208.45.220,10.208.45.227 /plugins/servlet/streams HttpSession [qdfo81] destroyed for 'jirasystem'

2020-04-29 18:20:47,202 http-nio-8080-exec-2      HttpSession created [1mjseeg]

2020-04-29 18:20:49,378 http-nio-8080-exec-5      HttpSession created [1xqr8u4]

2020-04-29 18:20:52,093 http-nio-8080-exec-17      HttpSession created [xlxbdb]

2020-04-29 18:21:01,405 http-nio-8080-exec-22      HttpSession created [bhtfos]

2020-04-29 18:21:06,306 http-nio-8080-exec-19      HttpSession created [1ptbkh6]

[Rawan Aldosary]

hi, I'm new to this but could you please tell me what do you mean of "you've killed the process" and how did you do that? thanks

[richard.cazes]

Usually this is opening the "Task manager" on the machine that runs JIRA, choosing the "Atlassian JIRA" process, right click on it and choose "End task".

Preferred method would be to stop the service if JIRA is installed this way. That's a cleaner way because the Database can do its closing tasks... but sometimes you have no choice but using the "kill the process" method.

Best of luck!