- #PROCESS AFFINITY NOT BEING SET MACHINE IS ALREADY LOADED. CODE#
- #PROCESS AFFINITY NOT BEING SET MACHINE IS ALREADY LOADED. ZIP#
Interval of sending of heartbeat requests in millisecondsįEP always uses M3UA connection between FEP and SMSC/USSD GW node.įEP initiates an SCTP connection, thus SMSC/USSD GW side(s) must configure SCTP server(s) and server association(s) (one association per FEP node).įEP prepares M3UA links with following options: functionality=IPSP, exchangeType=SE, ipspType=CLIENT, networkAppearance=102, RoutingContext=100. slee-ra-map-ra.LoadBalancerHeartBeatingServiceClassNameĪ class name of a LoadBalancer HeartBeatingService slee-ra-map-ra.BALANCERSĪ list of FEP side IP:port with a delimiter between FEP nodes. Port of SS7 M3UA association at SMSC/USSD GW side
#PROCESS AFFINITY NOT BEING SET MACHINE IS ALREADY LOADED. CODE#
Point Code of SMSC/USSD GW connected to FEP (must fit to a local MTP3/M3UA Point Code)
#PROCESS AFFINITY NOT BEING SET MACHINE IS ALREADY LOADED. ZIP#
Then, we need to zip restcomm-slee-ra-map-ra-7.4.1-30.jar and restcomm-slee-ra-map-du-7.4.1-30.jar files and deploy them into an original JBoss / WildFly folder. New unzipped folder contains META-INF/resource-adaptor-jar.xml file containing several config-property entries which we need to update. The latter is also a zip archive, then we need to unzip it too. This file is actually a zip archive, thus we need to unzip it.Īn unzipped folder contains a file named similarly to jars/restcomm-slee-ra-map-ra-7.4.1-30.jar. We can find this file within /server/default/deploy folder (for JBoss 5 case) or within /standalone/deployments folder (for WildFly case). MAP RA file is named similarly to restcomm-slee-ra-map-du-jboss-7.4.1-30.jar (for JBoss 5 server) or restcomm-slee-ra-map-du-7.4.1-30.jar (for WildFly server). UNBINDING - it can receive unbind response from server only, after which state changes to closed state ĬLOSED - it can’t receive any messages, this is the last state of the life cycle, which indicates that the connection is closed. If reconnect fails, connection is closed REBINDING - if connection drops to the server (SMSC), the client part changes ones state to rebinding until reconnect. OPEN - it can’t receive any messages, at this state the client part sends a bind request to the server (SMSC), and changes state to binding īINDING - it can receive only bind response from server, and if response does not have errors, the client part changes ones state to bound īOUND - it can receive all packets from server (SMSC), which can be sent according SMPP protocol, except unbind response INITIAL - it can’t receive any messages, this is first state of life cycle, at this state the client part is trying to connect to the server (SMSC) and if the connection is successful state changes to OPEN In case both maxResponseTime and maxRequestNumberWithoutResponseĪre exceeded, LB considers the server is dead and stops sending messages to the server. Stored and if the server response takes too long (the maxResponseTime value isĮxceeded) but the number of requests without response is small, then LB considers The timestamp of last packet sent by server is The maxResponseTime will allow to identify the server which fails to respond The “maxResponseTime” parameter also configurable. Server response does not take too long (it keeps within maxResponseTime limits), If maxRequestNumberWithoutResponse without response is exceeded but the The “maxRequestNumberWithoutResponse” is a configurable As soon as LB receives any packet from the server – When LB sends request to the server – theĬounter increments by one. Counter stores the number of requests which were sent to the server till the