Layer7 API Management

Hi All,

Any one faced below error after reboot ssg. 

Log File Location opt/Securespan/Gateway/node/default/node/

90 org.jgroups.protocols.pbcast.NAKACK: sender ************(Ipaddresss) not found in xmit_table
2017-02-21T23:23:30.177-0600 SEVERE 190 org.jgroups.protocols.pbcast.NAKACK: range is null
2017-02-21T23:23:30.177-0600 SEVERE 190 org.jgroups.protocols.pbcast.NAKACK: sender ************(Ipaddresss2)  not found in xmit_table
2017-02-21T23:23:30.177-0600 SEVERE 190 org.jgroups.protocols.pbcast.NAKACK: range is null
2017-02-21T23:23:30.177-0600 SEVERE 190 org.jgroups.protocols.pbcast.NAKACK: sender ************(Ipaddresss2)  not found in xmit_table
2017-02-21T23:23:30.177-0600 SEVERE 190 org.jgroups.protocols.pbcast.NAKACK: range is null
2017-02-21T23:23:30.177-0600 SEVERE 190 org.jgroups.protocols.pbcast.NAKACK: sender ************(Ipaddresss3)  not found in xmit_table
2017-02-21T23:23:30.178-0600 SEVERE 190 org.jgroups.protocols.pbcast.NAKACK: range is null
2017-02-21T23:23:30.178-0600 SEVERE 190 org.jgroups.protocols.pbcast.NAKACK: sender ************(Ipaddresss4)  not found in xmit_table
2017-02-21T23:23:30.178-0600 SEVERE 190 org.jgroups.protocols.pbcast.NAKACK: range is null

Thanks!

Prashant Srivastava

Hi Prashant,

These types of errors are usually symptoms of other issues. Did you encounter issues after starting up Gateway? Is this something you see all the time?

Thank you Mohindra for replying!

Yes after restart gateway  status was wont_start, we found mention error under ssg log .We never faced such kind error hence posted over group . 

Resolution : Tried restart again and issue got resolved 

But need to understand Why this error came also how after restart issue got resolved ?

Prashant,
The WONT_START message can be due to a few reasons. I have included a list of those reasons with ways to fix them if you run into the problem in the future.

Gateway logs WONT_START message

Hi,

Any change had been done before reboot the gateway? Particularly, any change on the cluster?

Regards,

Mark

Thank you Mark for your time !!

We did not make any changes before restart the gateway. To maintain the performance we were doing recycle .

Is that the complete error or do you also see something like "Failed to determine whether a MessageId is a replay : Replication timeout for "

Thank you for you time!!Yes mention error was complete error . There was noting related to replication because This node is note database node .

Hi Prasanth,

This error message is from our multicast replay protection subsystem. This subsystem ensures that messages sent to one node in a cluster cannot be reused and retransmitted to another node in the cluster. Specifically, this error occurs when a Gateway tries to communicate with other Gateways in the cluster but the multicast replay protection subsystem does not have this node in its multicast group.

This is a known defect in a dependency used by the Layer 7 Gateway (specifically, JGroups) that provides reliable multicast messaging to multiple users. Traditionally, restarting the Gateway appliance indicated in the log message (IPaddress, in this case) will make the error go away by forcing the Gateway to rejoin the multicast cluster.

You can also disable multicast replay protection in its entirety by setting the following cluster-wide property: "cluster.replayProtection.multicast.enabled" to "false." This disables the process within the Gateway appliance that leverages JGroups and as such it will not log any errors. This subsystem is only actively used for policy enforcement when the Message Replay Protection assertion is used within a policy.

Thanks,

Gopinath

Thank you Gopinath!!

Yes  ,that moment only we restarted node and issue resolved .But wanted to know more about this error hence posted over here .