Dear Team,

we installed UM9.12 as windows service. when I start UM from the service it is showing service is “Running” but in the logs can see it is shutting down.is it a bug in UM in services it still running but in logs Realm going down.
I verified RAM and hard disk the system they are good enough. I have attached the logs here(also pasted). I can see memory related errors and some times ““StoreManagement:2” daemon prio=1 tid=0x1e waiting on com.pcbsys.foundation.collections.fCircularQueue@686155b3 WAITING”.

in the end

Logs:

INFO | jvm 1 | 2019/08/12 22:12:32 | Build Number: Build 121920 Build Date: June 25 2019
INFO | jvm 1 | 2019/08/12 22:12:32 | Autogenerated thread dump
INFO | jvm 1 | 2019/08/12 22:12:32 |
INFO | jvm 1 | 2019/08/12 22:12:32 |
INFO | jvm 1 | 2019/08/12 22:12:32 | “MemoryManagement” daemon prio=1 tid=0xb TIMED_WAITING
INFO | jvm 1 | 2019/08/12 22:12:32 | at java.lang.Thread.sleep(Native Method)
INFO | jvm 1 | 2019/08/12 22:12:32 | at com.pcbsys.foundation.memory.fMemoryManager.run(fMemoryManager.java:429)
INFO | jvm 1 | 2019/08/12 22:12:32 | at com.pcbsys.foundation.threads.fThread.localRun(fThread.java:106)
INFO | jvm 1 | 2019/08/12 22:12:32 | at com.pcbsys.foundation.threads.hThread.run(hThread.java:102)
INFO | jvm 1 | 2019/08/12 22:12:32 | at java.lang.Thread.run(Thread.java:748)
INFO | jvm 1 | 2019/08/12 22:12:32 |
INFO | jvm 1 | 2019/08/12 22:12:32 |
INFO | jvm 1 | 2019/08/12 22:12:32 | “UM Transport high accuracy tick timer” daemon prio=5 tid=0xc waiting on java.util.TaskQueue@6e93dcaf TIMED_WAITING
INFO | jvm 1 | 2019/08/12 22:12:32 | at java.lang.Object.wait(Native Method)
INFO | jvm 1 | 2019/08/12 22:12:32 | - TIMED_WAITING on java.util.TaskQueue@6e93dcaf
INFO | jvm 1 | 2019/08/12 22:12:32 | at java.util.TimerThread.mainLoop(Timer.java:552)
INFO | jvm 1 | 2019/08/12 22:12:32 | at java.util.TimerThread.run(Timer.java:505)
INFO | jvm 1 | 2019/08/12 22:12:32 |
INFO | jvm 1 | 2019/08/12 22:12:32 |
INFO | jvm 1 | 2019/08/12 22:12:32 | “Wrapper-Control-Event-Monitor” daemon prio=5 tid=0xe TIMED_WAITING
INFO | jvm 1 | 2019/08/12 22:12:32 | at java.lang.Thread.sleep(Native Method)
INFO | jvm 1 | 2019/08/12 22:12:32 | at org.tanukisoftware.wrapper.WrapperManager$3.run(WrapperManager.java:1040)
INFO | jvm 1 | 2019/08/12 22:12:32 |
INFO | jvm 1 | 2019/08/12 22:12:32 |
INFO | jvm 1 | 2019/08/12 22:12:32 | “Wrapper-Connection” daemon prio=10 tid=0x10 waiting on org.tanukisoftware.wrapper.WrapperManager$12@51c74081 WAITING
INFO | jvm 1 | 2019/08/12 22:12:32 | at java.lang.Object.wait(Native Method)
INFO | jvm 1 | 2019/08/12 22:12:32 | - WAITING on org.tanukisoftware.wrapper.WrapperManager$12@51c74081
INFO | jvm 1 | 2019/08/12 22:12:32 | at java.lang.Thread.join(Thread.java:1252)
INFO | jvm 1 | 2019/08/12 22:12:32 | at java.lang.Thread.join(Thread.java:1326)
INFO | jvm 1 | 2019/08/12 22:12:32 | at org.tanukisoftware.wrapper.WrapperManager.privilegedStopInner(WrapperManager.java:4616)
INFO | jvm 1 | 2019/08/12 22:12:32 | at org.tanukisoftware.wrapper.WrapperManager.handleBackend(WrapperManager.java:5600)
INFO | jvm 1 | 2019/08/12 22:12:32 | at org.tanukisoftware.wrapper.WrapperManager.run(WrapperManager.java:5889)
INFO | jvm 1 | 2019/08/12 22:12:32 | at java.lang.Thread.run(Thread.java:748)
INFO | jvm 1 | 2019/08/12 22:12:32 |
INFO | jvm 1 | 2019/08/12 22:12:32 |
INFO | jvm 1 | 2019/08/12 22:12:32 | “DestroyJavaVM” prio=5 tid=0x11 RUNNABLE
INFO | jvm 1 | 2019/08/12 22:12:32 |
INFO | jvm 1 | 2019/08/12 22:12:32 |
INFO | jvm 1 | 2019/08/12 22:12:32 | “ServerStarterThread” prio=5 tid=0x13 RUNNABLE
INFO | jvm 1 | 2019/08/12 22:12:32 | at sun.management.ThreadImpl.dumpThreads0(Native Method)
INFO | jvm 1 | 2019/08/12 22:12:32 | at sun.management.ThreadImpl.getThreadInfo(ThreadImpl.java:448)
INFO | jvm 1 | 2019/08/12 22:12:32 | at com.pcbsys.nirvana.server.jdk.v1_5.nThreadDumper.getJMXData(nThreadDumper.java:68)
INFO | jvm 1 | 2019/08/12 22:12:32 | at com.pcbsys.nirvana.server.jdk.v1_5.nThreadDumper.produceThreadDump(nThreadDumper.java:129)
INFO | jvm 1 | 2019/08/12 22:12:32 | at com.pcbsys.nirvana.server.jdk.nJDKHelper.produceThreadDump(nJDKHelper.java:82)
INFO | jvm 1 | 2019/08/12 22:12:32 | at com.pcbsys.nirvana.server.Server.stopServer(Server.java:213)
INFO | jvm 1 | 2019/08/12 22:12:32 | at com.pcbsys.nirvana.server.ServerService$ServerStarter.run(ServerService.java:179)
INFO | jvm 1 | 2019/08/12 22:12:32 |
INFO | jvm 1 | 2019/08/12 22:12:32 |
INFO | jvm 1 | 2019/08/12 22:12:32 | “WrapperActionServer_runner” daemon prio=5 tid=0x14 RUNNABLE
INFO | jvm 1 | 2019/08/12 22:12:32 | at java.net.DualStackPlainSocketImpl.accept0(Native Method)
INFO | jvm 1 | 2019/08/12 22:12:32 | at java.net.DualStackPlainSocketImpl.socketAccept(DualStackPlainSocketImpl.java:131)
INFO | jvm 1 | 2019/08/12 22:12:32 | at java.net.AbstractPlainSocketImpl.accept(AbstractPlainSocketImpl.java:409)
INFO | jvm 1 | 2019/08/12 22:12:32 | at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:199)
INFO | jvm 1 | 2019/08/12 22:12:32 | - LOCKED java.net.SocksSocketImpl@27b564ac
INFO | jvm 1 | 2019/08/12 22:12:32 | at java.net.ServerSocket.implAccept(ServerSocket.java:545)
INFO | jvm 1 | 2019/08/12 22:12:32 | at java.net.ServerSocket.accept(ServerSocket.java:513)
INFO | jvm 1 | 2019/08/12 22:12:32 | at org.tanukisoftware.wrapper.WrapperActionServer.run(WrapperActionServer.java:167)
INFO | jvm 1 | 2019/08/12 22:12:32 | at java.lang.Thread.run(Thread.java:748)
INFO | jvm 1 | 2019/08/12 22:12:32 |
INFO | jvm 1 | 2019/08/12 22:12:32 |
INFO | jvm 1 | 2019/08/12 22:12:32 | “Scheduler Worker Pool:0” daemon prio=5 tid=0x15 waiting on com.pcbsys.foundation.collections.fCircularQueue@459b7d61 WAITING
INFO | jvm 1 | 2019/08/12 22:12:32 | at java.lang.Object.wait(Native Method)
INFO | jvm 1 | 2019/08/12 22:12:32 | - WAITING on com.pcbsys.foundation.collections.fCircularQueue@459b7d61
.
.
.
INFO | jvm 1 | 2019/08/12 22:12:32 | “WrapperListener_stop_runner” prio=5 tid=0x999 waiting on com.pcbsys.nirvana.server.ServerService$ServerStarter@5ec96e2d TIMED_WAITING
INFO | jvm 1 | 2019/08/12 22:12:32 | at java.lang.Object.wait(Native Method)
INFO | jvm 1 | 2019/08/12 22:12:32 | - TIMED_WAITING on com.pcbsys.nirvana.server.ServerService$ServerStarter@5ec96e2d
INFO | jvm 1 | 2019/08/12 22:12:32 | at com.pcbsys.nirvana.server.ServerService.stop(ServerService.java:94)
INFO | jvm 1 | 2019/08/12 22:12:32 | at org.tanukisoftware.wrapper.WrapperManager$12.run(WrapperManager.java:4584)
STATUS | jvm 1 | 2019/08/12 22:12:32 | UM realm server - stop called
STATUS | jvm 1 | 2019/08/12 22:12:32 | Notifying server thread on stop
STATUS | jvm 1 | 2019/08/12 22:12:32 | Shutting down Nirvana Realm
INFO | jvm 1 | 2019/08/12 22:12:32 | Starting Realm Mon Aug 12 22:12:32 SGT 2019
INFO | jvm 1 | 2019/08/12 22:12:32 | Copyright (c) Software AG Limited. All rights reserved
INFO | jvm 1 | 2019/08/12 22:12:32 | Realm shutdown complete
INFO | jvm 1 | 2019/08/12 22:12:32 | Nirvana Realm has been shutdown
UM_Log.txt (13.6 KB)

Hey,

The StoreManagement thread is actually idle in that state so nothing to fear, it seems that UM is being issued a shutdown but from where I am not sure, could you provide the full nirvana.log and UMRealmService.log, might be ideal to compress them before uploading if possible.

Where did you note the memory issues?

Regards

Joshua

Thank you Joshua for prompt response. Sorry it was memory issue. Issue was resolved after increasing java heap size min and Max memory from 1024 to 2048 “Server_Common.conf”.