KB Article #57111
JMS message sent' for transfer message '210-000000019098', transfer session '210:1-1', has expired" (Swift solution)
Customer is using the Synchrony suite with swift solution with the below architecture:-
Vantage>><< XMS >><< Integrator>><< Gateway>><< Transfers
During the message processing randomly few messages were getting error out with the below information in the logs:-
Integrator Logs:-
JMS message sent' for transfer message '210-000000019098', transfer session '210:1-1', has expired"
Vantage logs:-
20090408 122635 ERROR swiftUser_REM; 2009/04/08 12:26:35; Exchange Service failure : Queue is in use
20090408 122647 INFO swiftUser_REM; 2009/04/08 12:26:47; Logoff of a user
20090408 122657 WARN 09007395(0)282; FIN-2007-MT103; 2009/04/08 12:20:32; 12:20:32; elainehung; CorrelationID = 09007395(0)282 1239164756984 - Check result : Timeout expired
Resolution
Following steps were recommended to overcome this problem;-
For Vantage errors:-
1. 20090408 122657 WARN 09007395(0)282; FIN-2007-MT103; 2009/04/08 12:20:32; 12:20:32; elainehung; CorrelationID = 09007395(0)282 1239164756984 - Check result : Timeout expired
This is displayed in portal if a message has been sent by SWIFTNetPortal to the XMS queue to be processed by Integrator and no response has reached the portal during the timeout interval defined in its configuration file (by default it is 7 sec).
in case the Integrator takes more than 7 seconds to respond to a request from the portal then we need to increase this timeout in the below file (may to 60 sec from 7 sec)
<install-dir>\Vantage_V1.3.6.0\server\synchrony-vantage\webapps\portalforswiftnet\WEB-INF\web.xml.
Parameter:- check queue timeout = 7000
2. 20090408 122635 ERROR swiftUser_REM; 2009/04/08 12:26:35; Exchange Service failure : Queue is in use
This error can be reproduced systematically when launching 2 users simultaneously (and more users later on), having the queues in the XMS set to NOSHARE access mode.
So the solution is to set the queues in the XMS to the shared mode from the non shared mode.
Way to do it:-
xmsdsp queue -i <queue_name> {To display the status of the queue}
xmsupd queue -I <queue_name> -am share {To change the access mode to shared}
For Integrator:-
For the JMS transfer timeout issues:-
JMS TA separated for receive channels and send channels with the dedicated processing engines to have more connections with the XMS.
Another tip will be to try by increasing the timeout parameter in the JMS send channel (for eg: from 60sec to 300sec).