we have installed UM in our environment,some of the java application directly posting data through nsp URL.
they complained like some times they are able to post some times not. when i checked the UM logs
[Wed Sep 04 08:05:01 EDT 2019] UserManager: User wmroot@hostname Logged Out using nsp, Reason : unknown, session established for 9469 seconds, Session Id = 9d192cf00000000 ID: 10.72.16.173:59797 Session Name : IS Trigger: trigger name
[Tue Sep 10 00:25:27 EDT 2019] UserManager: User wmroot@hostnamel Logged Out using nsp, Reason : com.pcbsys.nirvana.base.nException Client session requested clean session close, session established for 470446 seconds, Session Id = 9d86f9300000000 ID: 10.72.16.220:32784 Session Name : IS Trigger: trigger name
not why why one session is sitting in UM memory this much time. is that suspected behavior?
when i checked the UM memory through free -m
total used free shared buffers cached
7855 7728 123 0 257 4248
-/+ buffers/cache: 2314 5541
Swap: 18363 100 18263
when i checked through top
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMM
83345 wmroot 20 0 11.7g 1.4g 16m S 1 4.3 18.3 802:58.49 java
any suggestions please