NSP - NFM-P Release 17.9 (Unable to connect)

lehio · Post by **lehio** » 31 May 2022 06:19

Dears ALL,

Hello, We need your help explaining why it's not working well. "GUI Interface" for NFM-P Application, This is the message that comes out when the browser is requested:-
--------------------------------------------------------------------------------------------------------------------------
1- https://nfmpmain1 -------> automatic change to ---------->
https://127.0.0.1/session-manager/login ... ogin%2Fcas
----------------------------------------------------------------------------------------------------------------------------
2022.05.30 19:51:32 652 +0200 INFO [stdout] membershipChanged: new Member - Standby reachable: /10.34.0.52
2022.05.30 19:51:32 837 +0200 INFO [stdout] RedundancyNmsService::ClusterNodes: node 1=10.34.0.20
2022.05.30 19:51:32 841 +0200 INFO [stdout] RedundancyNmsService::ClusterNodes: node 2=10.34.0.52
2022.05.30 19:51:32 870 +0200 INFO [stdout] RedundancyNmsService:: getPeerServerStatus(), The Peer server is a Standby Server
2022.05.30 19:51:32 870 +0200 INFO [stdout] RedundancyNmsService::ClusterNodes: I am master. Peer server is a Standby Server
2022.05.30 19:51:32 870 +0200 INFO [stdout] RedundancyNmsService::ClusterNodes: electing this nfmpmain1/NFM-P_Partition_NFMP_17_9_NFM-P
2022.05.30 19:51:32 879 +0200 INFO [stdout] clearStandbyAlarm: standby Server alarm is cleared [10.34.0.52] contextThread[RedundancyWorker[1]]
2022.05.30 19:51:37 886 +0200 INFO [stdout] RedundancyNmsService:: getPeerServerStatus(), The Peer server is a Standby Server
2022.05.30 19:51:37 888 +0200 INFO [stdout] RedundancyNmsService:: receiveOtherServerStatus(), The Peer server is initializing as a Standby Server
2022.05.30 19:54:37 564 +0200 INFO [stdout] RedundancyNmsService::ClusterNodes: node=10.34.0.20
2022.05.30 19:54:37 581 +0200 INFO [stdout] RedundancyNmsService::ClusterNodes: electing this nfmpmain1/NFM-P_Partition_NFMP_17_9_NFM-P
2022.05.30 19:54:37 585 +0200 INFO [stdout] membershipChanged: dead Member - Standby down: /10.34.0.52
2022.05.30 19:54:37 588 +0200 INFO [stdout] raiseStandbyAlarm: Standby Server alarm is raised [10.34.0.52] contextThread[RedundancyWorker[1]]
System log file has reached the maximum size. Saved as EmsThreadDump.2022-05-30_20-00-00.4.log
2022.05.30 20:02:16 321 +0200 INFO [stdout] membershipChanged: new Member - Standby reachable: /10.34.0.52
2022.05.30 20:02:16 530 +0200 INFO [stdout] RedundancyNmsService::ClusterNodes: node 1=10.34.0.20
2022.05.30 20:02:16 530 +0200 INFO [stdout] RedundancyNmsService::ClusterNodes: node 2=10.34.0.52
2022.05.30 20:02:16 569 +0200 INFO [stdout] RedundancyNmsService:: getPeerServerStatus(), The Peer server is a Standby Server
2022.05.30 20:02:16 571 +0200 INFO [stdout] RedundancyNmsService::ClusterNodes: I am master. Peer server is a Standby Server
2022.05.30 20:02:16 571 +0200 INFO [stdout] RedundancyNmsService::ClusterNodes: electing this nfmpmain1/NFM-P_Partition_NFMP_17_9_NFM-P
2022.05.30 20:02:16 579 +0200 INFO [stdout] clearStandbyAlarm: standby Server alarm is cleared [10.34.0.52] contextThread[RedundancyWorker[1]]
2022.05.30 20:02:21 585 +0200 INFO [stdout] RedundancyNmsService:: getPeerServerStatus(), The Peer server is a Standby Server
2022.05.30 20:02:21 587 +0200 INFO [stdout] RedundancyNmsService:: receiveOtherServerStatus(), The Peer server is initializing as a Standby Server
2022.05.30 20:04:15 528 +0200 INFO [stdout] RedundancyNmsService:: receiveOtherServerStatus(), The Peer server is a Standby Server
2022.05.30 20:04:15 582 +0200 INFO [stdout] RedundancyNmsService:: NSP Licenses are matched on both servers.
2022.05.30 20:04:15 602 +0200 INFO [stdout] RedundancyNmsService:: TestId Ranges are matched on both servers.
2022.05.30 20:04:15 614 +0200 INFO [stdout] RedundancyNmsService:: CPAM Licenses are matched on both servers.
2022.05.30 20:04:15 622 +0200 INFO [stdout] RedundancyNmsService::NFM-P Server Software patch level are matched on both servers
2022.05.30 20:04:15 622 +0200 INFO [stdout] RedundancyNmsService:: receiveOtherServerStatus(), The Peer server is a Standby Server
2022.05.30 20:04:15 635 +0200 INFO [stdout] RedundancyNmsService:: NSP Licenses are matched on both servers.
2022.05.30 20:04:15 639 +0200 INFO [stdout] RedundancyNmsService:: TestId Ranges are matched on both servers.
2022.05.30 20:04:15 647 +0200 INFO [stdout] RedundancyNmsService:: CPAM Licenses are matched on both servers.
2022.05.30 20:04:15 656 +0200 INFO [stdout] RedundancyNmsService::NFM-P Server Software patch level are matched on both servers
2022.05.30 20:05:15 539 +0200 INFO [stdout] RedundancyNmsService:: receiveOtherServerStatus(), The Peer server is a Standby Server
2022.05.30 20:05:15 564 +0200 INFO [stdout] RedundancyNmsService:: NSP Licenses are matched on both servers.
2022.05.30 20:05:15 568 +0200 INFO [stdout] RedundancyNmsService:: TestId Ranges are matched on both servers.
2022.05.30 20:05:15 579 +0200 INFO [stdout] RedundancyNmsService:: CPAM Licenses are matched on both servers.
2022.05.30 20:05:15 588 +0200 INFO [stdout] RedundancyNmsService::NFM-P Server Software patch level are matched on both servers
2022.05.30 20:10:00 219 +0200 INFO [stdout] RedundancyNmsService::ClusterNodes: node=10.34.0.20
2022.05.30 20:10:00 219 +0200 INFO [stdout] RedundancyNmsService::ClusterNodes: electing this nfmpmain1/NFM-P_Partition_NFMP_17_9_NFM-P
2022.05.30 20:10:00 220 +0200 INFO [stdout] membershipChanged: dead Member - Standby down: /10.34.0.52
2022.05.30 20:10:00 223 +0200 INFO [stdout] raiseStandbyAlarm: Standby Server alarm is raised [10.34.0.52] contextThread[RedundancyWorker[1]]
2022.05.30 20:13:45 509 +0200 INFO [stdout] membershipChanged: new Member - Standby reachable: /10.34.0.52
2022.05.30 20:13:45 729 +0200 INFO [stdout] RedundancyNmsService::ClusterNodes: node 1=10.34.0.20
2022.05.30 20:13:45 730 +0200 INFO [stdout] RedundancyNmsService::ClusterNodes: node 2=10.34.0.52
2022.05.30 20:13:45 733 +0200 INFO [stdout] RedundancyNmsService::getPeerServerStatus(), The Peer server is not responding..
2022.05.30 20:13:45 771 +0200 INFO [stdout] RedundancyNmsService:: getPeerServerStatus(), The Peer server is a Standby Server
2022.05.30 20:13:45 772 +0200 INFO [stdout] RedundancyNmsService::ClusterNodes: I am master. Peer server is a Standby Server
2022.05.30 20:13:45 772 +0200 INFO [stdout] RedundancyNmsService::ClusterNodes: electing this nfmpmain1/NFM-P_Partition_NFMP_17_9_NFM-P
2022.05.30 20:13:45 782 +0200 INFO [stdout] clearStandbyAlarm: standby Server alarm is cleared [10.34.0.52] contextThread[RedundancyWorker[1]]
2022.05.30 20:13:50 793 +0200 INFO [stdout] RedundancyNmsService:: getPeerServerStatus(), The Peer server is a Standby Server
2022.05.30 20:13:50 795 +0200 INFO [stdout] RedundancyNmsService:: receiveOtherServerStatus(), The Peer server is initializing as a Standby Server
2022.05.30 20:16:37 669 +0200 INFO [stdout] RedundancyNmsService:: receiveOtherServerStatus(), The Peer server is a Standby Server
2022.05.30 20:16:37 685 +0200 INFO [stdout] RedundancyNmsService:: NSP Licenses are matched on both servers.
2022.05.30 20:16:37 690 +0200 INFO [stdout] RedundancyNmsService:: TestId Ranges are matched on both servers.
2022.05.30 20:16:37 696 +0200 INFO [stdout] RedundancyNmsService:: CPAM Licenses are matched on both servers.
2022.05.30 20:16:37 702 +0200 INFO [stdout] RedundancyNmsService::NFM-P Server Software patch level are matched on both servers
System log file has reached the maximum size. Saved as EmsServer.2022-05-31_11-46-06.16.log
System log file has reached the maximum size. Saved as EmsThreadDump.2022-05-31_11-50-00.23.log
-------------------------------------------------------------------------------------------------------------------------------------------
----------------------------------------------------------------------------------------------------------------------------------------------

<2022.05.31 12:13:16 666 +0200><nfmpmain1><MemoryMonitorPrintTimer><> ***** TIMESTAMP : Tue May 31 12:13:16 EET 2022 *****
<2022.05.31 12:13:16 666 +0200><nfmpmain1><MemoryMonitorPrintTimer><> JVM MEMORY: Heap Memory Usage: init = 2097152K used = 201084K committed = 2027264K max = 2027264K - (9% used) Memory Threshold exceeded(#):0 - Pending finalization count:0
<2022.05.31 12:13:16 666 +0200><nfmpmain1><MemoryMonitorPrintTimer><> JVM MEMORY: Non-Heap Memory Usage: init = 2304K used = 53380K committed = 55992K max = 131072K - (40% used)
<2022.05.31 12:13:16 667 +0200><nfmpmain1><MemoryMonitorPrintTimer><> JVM MEMORY: Memory Pool Name: Code Cache Type: Non-heap memory Usage: init = 2304K used = 5464K committed = 5536K max = 49152K - (11% used) |Memory Manager Names: CodeCacheManager
<2022.05.31 12:13:16 667 +0200><nfmpmain1><MemoryMonitorPrintTimer><> JVM MEMORY: Memory Pool Name: Metaspace Type: Non-heap memory Usage: init = 0K used = 47916K committed = 50456K max = 81920K - (58% used) |Memory Manager Names: Metaspace Manager
<2022.05.31 12:13:16 667 +0200><nfmpmain1><MemoryMonitorPrintTimer><> JVM MEMORY: Memory Pool Name: Par Eden Space Type: Heap memory Usage: init = 559232K used = 159386K committed = 559232K max = 559232K - (28% used) |Memory Manager Names: ConcurrentMarkSweep,ParNew
<2022.05.31 12:13:16 667 +0200><nfmpmain1><MemoryMonitorPrintTimer><> JVM MEMORY: Memory Pool Name: Par Survivor Space Type: Heap memory Usage: init = 69888K used = 597K committed = 69888K max = 69888K - (0% used) |Memory Manager Names: ConcurrentMarkSweep,ParNew
<2022.05.31 12:13:16 667 +0200><nfmpmain1><MemoryMonitorPrintTimer><> JVM MEMORY: Memory Pool Name: CMS Old Gen Type: Heap memory Usage: init = 1398144K used = 41129K committed = 1398144K max = 1398144K - (2% used) |Memory Manager Names: ConcurrentMarkSweep
<2022.05.31 12:13:16 667 +0200><nfmpmain1><MemoryMonitorPrintTimer><> JVM MEMORY: Total Loaded Classes(#): 13541 Loaded Classes(#):13436 Unloaded Classes(#):105
<2022.05.31 12:13:17 010 +0200><nfmpmain1><JMSClientQueueCountLogger><server.j2ee.jms.JMSClientQueueCountLogger.logClientQueueCounts>
Durable Client Queue Counts: No clients exceeding queue count threshold found

<2022.05.31 12:13:17 015 +0200><nfmpmain1><JMSClientQueueCountLogger><server.j2ee.jms.JMSClientQueueCountLogger.logClientQueueCounts>
Non-Durable Client Queue Counts: No clients exceeding queue count threshold found