XMA: TMF is keeping active transactions open for SLSENDER after SLSENDER and XMA Pathway are stopped
The reason for this behavior because is the XMA TACL routines are shutting down the pathway with the Pathmon command ?SHUTDOWN2, MODE IM, UNTIL DONE?. The ?MODE IM? means that it stops the servers immediately but does not close them. This allows them to clean up resources. Depending on how much activity was in progress with SLSENDER at the time of the shutdown, it will take a short period of time for all the transactions to be backed out and terminated. This is normal behavior.
Workaround:
Shut down the XMA pathway as follows
1. Manually freeze and stop the all servers
a. PATHCOM $XMA
b. FREEZE SERVER *
c. STOP SERVER *
d. STOP SERVER *
2. Stop the pathmon using the PWSTOP or XMA_PWSTOP routines. This is because these two routines capture snapshot information on the XMA pathway environment and store it in file called PWSTATE prior to the shutdown. This is not done if the pathway is shutdown manually using the "PATHCOM $XMA; SHUTDOWN, WAIT" command.
a. RUN $<vol>.XYGATEMA.XMA INSTALL
b. XMA_PWSTOP
or:
RUN $<vol>.XYGATEMA.PWSTOP
Where $<vol> is the disk volume where XMA was installed.
If you are unable to locate the solution needed or if you need additional assistance please Click Here to open a case from our Customer Care Portal.
Related Articles
XMA: SLSENDER - Steps to follow for SLSENDER When Upgrading to XMA 2.65
The upgrade to XMA 2.65 makes changes to the SYSLOGQ table. Consequentially, this could cause fatal errors for SLSENDER when it it initially started following the upgrade. This is due to outstanding TMF transactions that remains until they are ...
XMA: How to uninstall SLSENDER.
As the SLSENDER is configured and added to the XMA pathway when the customer follows the installation process in the XMA manual. The following procedure can be used to manually stop the SLSENDER , remove any records that have been generated, and stop ...
XMA: SLSENDER is busy
Use the XMA_SQLCOMPALL macro to generate a new optimized query plan, which will then be used when compiling the objects. TACL> VOLUME $SYSTEM.XYGATEMA TACL> RUN XMA INSTALL TACL> XMA_PWSTOP TACL> XMA_SQLCOMPALL TACL> XMA_PWCOOL The XMA_SQLCOMPALL ...
XMA Critical TMF message #222 from SLSENDER - TMF AutoAbort timeout duration error messages remedy
We have two potential solutions: Upgrade to XMA 2.60 where the SYSLOGQ index has been updated. This is the preferred Implement the procedure below to update the current XMA SYSLOGI index in any XMA implementation prior to 2.60. SYSLOGQI index update ...
XMA: How to optimize SLSENDER to handle multiple SIEMs
SLSENDER must be optimized for the number of SIEMS and transactions 1. SLSENDER can be configured in XMA_MANAGER. >run xma install >XMA_MANAGER >2: Movers >18: Configure SysLog Send server) 2. In the SysLog Send server menu (SLSENDER), the Max Number ...