Products | Versions |
---|---|
TIBCO Adapter for SWIFT | - |
Not Applicable | - |
Resolution:
Description:
============
When SWIFT Adapter connects to SWIFT Alliance through CASmf, the SWIFT Receiver starts, receive the first message but then shuts down. The current Window Size is 4, which means CASmf can receive 4 messages from SWIFT before returning the corresponding logical reply for the first message.
From the CASmf log, it appears the message sequence number is disordered, which makes the logical reply not associated to the message at some time. The session is then auto closed since the logical reply is invalid.
The following are the logs - CASMF (CUSLOG.LOG) and SWIFT RECEIVER LOG.
CASmf log:
11-20 06:33:32.31 -M- SHD IN OPEN_CF version 2 CASmfOutputSSR <-> AllianceMXSCASmfOutputSSR session # 1 sequence # 319 recovery 1 window 4 flow 1
11-20 06:33:32.31 -O- SHD MSG_APL_SES_OPEN The session for mapid CASmfOutputSSR is open
11-20 06:34:02.22 -M- SHD IN DATA version 2 CASmfOutputSSR <-> AllianceMXSCASmfOutputSSR session # 1 sequence # 319 duplicated 0
11-20 06:34:02.25 -M- SHD OUT LREP version 2 CASmfOutputSSR <-> AllianceMXSCASmfOutputSSR session # 1 sequence # 319
11-20 06:37:02.19 -M- SHD IN DATA version 2 CASmfOutputSSR <-> AllianceMXSCASmfOutputSSR session # 1 sequence # 320 duplicated 0
11-20 06:37:02.20 -M- SHD IN DATA version 2 CASmfOutputSSR <-> AllianceMXSCASmfOutputSSR session # 1 sequence # 321 duplicated 0
11-20 06:37:32.17 -M- SHD IN DATA version 2 CASmfOutputSSR <-> AllianceMXSCASmfOutputSSR session # 1 sequence # 322 duplicated 0
11-20 06:37:32.17 -M- SHD IN DATA version 2 CASmfOutputSSR <-> AllianceMXSCASmfOutputSSR session # 1 sequence # 323 duplicated 0
11-20 06:37:32.17 -W- SHD MSG_SHD_DATA_SEQ Invalid data seq # rcv 3 expected 325
11-20 06:37:32.17 -M- SHD IN DATA version 2 CASmfOutputSSR <-> AllianceMXSCASmfOutputSSR session # 1 sequence # 325 duplicated 0
Adapter log:
2010 Nov 20 09:28:28:660 GMT +4 SWIFTHUB-PHASE1-SwiftReceiver Info [Adapter] AESWIFT-000074 "CASmf using publisher MessagePublisherEndPoint sending UnparsedSWIFTMessage" tracking=#JFpNywZCNw34x-poMfNeEG-keDw#
2010 Nov 20 09:28:28:660 GMT +4 SWIFTHUB-PHASE1-SwiftReceiver Info [Adapter] AESWIFT-000112 "CASmf sending a logical reply to gateway"
2010 Nov 20 09:28:28:660 GMT +4 SWIFTHUB-PHASE1-SwiftReceiver Debug [Adapter] AESWIFT-000002 "Error sending logilcal reply to CASmf: [CASmf] CUSAPI_NOT_OPEN : 9004 : The session is not open."
2010 Nov 20 09:28:28:660 GMT +4 SWIFTHUB-PHASE1-SwiftReceiver Error [Adapter] AESWIFT-000113 "CASmf failed to send a logical reply to the gateway"
2010 Nov 20 09:28:28:676 GMT +4 SWIFTHUB-PHASE1-SwiftReceiver Error [Adapter] AESWIFT-000007 "The SWIFT adapter is stopping"
Environment:
===========
All 5.x versions
The component is TIBCO Adapter for SWIFTNet - FIN
Resolution:
=========
(1). Change the Window Size to 1 in the DMAPID.DAT and at the Message Partner in SWIFT Alliance.
(2). Restart SWIFT Alliance and CASmf, then start the adapter.
(3). If the preceeding two steps don'tt help then delete the .rvy files which are under <CASmf_Home>\dat . (It is suggested that the files be backed up before deleting them). Then restart CASmf and adapter.
To understand this issue more clearly, you may need to know the meaning of the following words.
(1). Window Size description:
The Window Size determines how many messages may be transmitted before a logical reply is required. This value is used for as long as the session is active.
Window Size 1 always ensures that after each message transmission to CASmf, logical reply is required.
During current settings (window size = 4), following method applies:
If a session is aborted when a window size of more than 1 is implemented, then the receiver must discard any messages that the sender sent but which the receiver has not processed. This applies directly to messages which have not yet received a logical reply.
(2). rvy file description:
The .rvy file is used to store the session number if some message is not received by adapter through CASmf when the session is auto closed. When adapter is restarted it will recover that session.