KB Article #176060
[Question] Sequence of context numbers
Problem
In Gateway log there is a question about context numbersThe customer notice d some numbers in the logs and though Support explained that it concerns "just a product internal context number" and does by no means mean that his product is going to crash or "run out of contexts", they just want to know *why* this context is so different -->
For an incoming, normal functioning protocol connection, we see for instance (1801) (a low number, going up in sequence, starting from 1 each time Gateway is restarted).
But when the same incoming session ends in error, for instance with a "Reason 14, Invalid Remote Identifier", then the context becomes something like (33587410) rather than (1801).
We would like to explain why this number changes, why so high and do they risk to hit any kind of maximum of this context number (and if so, what will happen) ?
Problem was reproduced in many contexts at various customer
One example with steps to replicate is below:
Perform a normal transfer, using OFTPv2, without any errors and observe the context numbers in between brackets. The modify the OFTP identifier (so it will be wrong on purpose) and try again a transfer. After the "error" (invalid remote identifier) the original context number (still in between brackets) has been replaced by an enormous high number.
Example of log:
"
M1AwU0Bk9AA 20140324 163649 217 ODT I DISC_IND PROLD(133) disconnect indication received for NEW [reason="Normal sessio
n termination"]
20140324 163649 106 NET I DISC_IND (133) disconnection indication [reason="0"] [origin="0"] ß numéro de context qui démarre à 1 quand on démarre la Gateway
20140324 163649 105 NET I DISC_REQ (133) disconnection request [reason="0"]
20140324 163649 106 NET I DISC_IND (145) disconnection indication [reason="0"] [origin="0"]
ODMAAA SFAwU0hk9AA 20140324 163649 011 SUP W ABORT_ID PROLD(41943185) connection abort indication: reason="164, Protocol error ß numéro de context qui démarre très élevé et pas à « 1 »
" /prot.diag="116, Network disconnection detected" / error=99
20140324 163649 106 NET I DISC_IND (144) disconnection indication [reason="0"] [origin="0"]
QDMAAA R1AwU0dk9AA 20140324 163649 011 SUP W ABORT_ID PROLD(41943184) connection abort indication: reason="164, Protocol error
" /prot.diag="116, Network disconnection detected" / error=99
20140324 163649 532 SUP I SITE-RTRY Site 'PROLD': retry delay set to 20 seconds
"
Resolution
There are different modules that send messages to the log:- net -> context at FT level, low number, starts from 1.
- sup -> context at supervisor level, higher number -> it's a combination between the transfer tag and the session tag.
There is no risk to run out of contexts.