Hi Everyone,

We have a clustered environment with 2 node agents and 2 Servers. We are seeing the node agents are getting down frequently every day at the same time.In the Server Logs we didn't see anything but in the node agent Logs, The Following messages are getting logged at Windows OS.

DiscoveryTx   W   DCSV1115W: DCS Stack DefaultCoreGroup at Member Cell01\Webnode02\nodeagent: Member Cell01\Webnode01\RSrv connection  was closed. Member will  be removed from view. DCS connection status is Discovery|Ptp, transmitter closed. Removing closed connection.
TransportAdap W   DCSV1117W: DCS Stack DefaultCoreGroup at Member Cell01\Webnode02\nodeagent: The stream from Member Cell01\Webnode01\RSrv has closed. The channnel is View|Ptp. 
DiscoveryTx   W   DCSV1115W: DCS Stack DefaultCoreGroup at Member Cell01\Webnode02\nodeagent: Member Cell01\Webnode01\MXUI-1 connection  was closed. Member will  be removed from view. DCS connection status is Discovery|Ptp, transmitter closed. Removing closed connection.

TransportAdap W   DCSV1117W: DCS Stack DefaultCoreGroup at Member Cell01\Webnode02\nodeagent: The stream from Member Cell01\Webnode01\MXUI-1 has closed. The channnel is View|Ptp. 
DiscoveryTx   W   DCSV1115W: DCS Stack DefaultCoreGroup at Member Cell01\Webnode02\nodeagent: Member Cell01\Webnode01\nodeagent connection  was closed. Member will  be removed from view. DCS connection status is Discovery|Ptp, transmitter closed. Removing closed connection.
TransportAdap W   DCSV1117W: DCS Stack DefaultCoreGroup at Member Cell01\Webnode02\nodeagent: The stream from Member Cell01\Webnode01\nodeagent has closed. The channnel is Connected|Ptp. 
VSyncAlgo2    I   DCSV2004I: DCS Stack DefaultCoreGroup at Member Cell01\Webnode02\nodeagent: View synchronization completed successfully. The View Identifier is (9:0.Cell01\CellManager01\dmgr). The internal details are The leader equals Cell01\CellManager01\dmgr, ccv equals ((9:0.Cell01\CellManager01\dmgr).3.0).
 CoordinatorIm I   HMGR0228I: The Coordinator is not an Active Coordinator for core group DefaultCoreGroup. The active coordinator set is [Cell01\CellManager01\dmgr].

Help me how to fix this error.

Thank you in advance for the Response.

------------------------------
CKK
------------------------------

Normally related to Coregroups/HA manager...you may also need to look into buffer size of the Coregroup.

 - You should see warnings from the nodeagent JVM reporting that they can't talk to the DMGR for example. Check Nodegagents SystemErr.log too for info. I would look for High CPU usage errors or oddly enough OOM/HeapDumps as in Systhrow message.  

The message normally relates to Coregroup related issues - It looks for connections that closed because the underlying socket was closed. When a failed member is detected because of the socket closing mechanism, the following message is logged in the SystemOut.log file for the surviving members:

DCSV1115W: DCS Stack DefaultCoreGroup at Member anzioCell01\anzio\ServerD:
Member anzioCell01\anzio\ServerC connection  was closed. Member will  be removed from view.
DCS connection status is Discovery|Ptp, transmitter closed.

Got trigger happy...here some Info:

Hello Joe,

Thank you for the response.

As you mentioned, i have gone through the SystemErr Log Files of the Node Agent and Server. But i couldn't find any errors there.

I am not sure what to do next. Kindly advise.

Thank you 

Hi Everyone,

We have a clustered environment with 2 node agents and 4 Servers. We are seeing the node agents are getting down frequently every day at the same time.In the Server Logs we didn't see anything

DCSV1036W DCS stack defalutCore closing the connection because members did not manage connect please help this.

Hi Mohan, 

Does the servers and Nodes are registered as Services?

Hi Chaitanya,

When we have this issue, We observed that node agent processes are getting killed due to high memory usage. When we register the node agent as a service following the below URL It resolved the issue. Take a look at it.

https://www.ibm.com/docs/en/samfess/8.2.2?topic=cluster-creating-windows-service-node-agent
http://setgetweb.com/p/WAS855/ae/was1698.html

Hi,

  issue is resolve after increase pagging   size in Linux level.

Thanks,

Korlapati Mohan krishna