XCOM Gateway Directory Watcher stopped for two policies
Article ID: 242312
Updated On:
Products
Issue/Introduction
There are 2 policies configured for the Directory Watcher to take the files when they arrive which had been working correctly.
Today it was discovered that the Directory Watcher for policies named POLICY1 and POLICY2 had stopped. The Directory Watcher for both policies was restarted to resolve the problem but what caused them to stop in the first place?
Environment
Release : 12.0
Component : XCOM DATA TRANSPORT GATEWAY FOR WINDOWS
Cause
Problems caused by NTLM authentication failures as reported in the previous day's GatewayControlServer.log e.g. for policy POLICY1
===
[05-17-2022/16:06:34.292/ART][INFO ][com.ca.xcom.gateway.autoFileInsertion.PolicyDirectoryWatchersInvoker] Watch on Policy: [POLICY1 ] will not be watched in future.
[05-17-2022/16:06:34.331/ART][ERROR][com.ca.xcom.gateway.autoFileInsertion.PolicyWatcher] POLICY1
com.ca.xcom.logging.exception.SystemException: com.ca.xcom.logging.exception.SystemException: MSG33218
at com.ca.xcom.gateway.autoFileInsertion.PolicyWatcher.StartWatch(PolicyWatcher.java:271)
...
Caused by: com.ca.xcom.logging.exception.SystemException: MSG33218
at com.ca.xcom.samba.client.SMBProtocolUtil.testRealmPath(SMBProtocolUtil.java:231)
at com.ca.xcom.gateway.autoFileInsertion.PolicyWatcher.isFolderWellConfigured(PolicyWatcher.java:289)
at com.ca.xcom.gateway.autoFileInsertion.PolicyWatcher.StartWatch(PolicyWatcher.java:116)
... 9 more
Caused by: com.ca.xcom.logging.exception.SystemException: MSG33226
at com.ca.xcom.samba.client.SMBProtocolUtil.testRealmPath(SMBProtocolUtil.java:155)
... 11 more
Caused by: com.hierynomus.smbj.common.SMBApiException: STATUS_LOGON_FAILURE(3221225581/3221225581): Authentication failed for 'xcwatch' using com.hierynomus.smbj.auth.NtlmAuthenticator@58088d3a
at com.hierynomus.smbj.connection.Connection.authenticate(Connection.java:131)
at com.ca.xcom.samba.client.SMBProtocolUtil.testRealmPath(SMBProtocolUtil.java:143)
... 11 more
===
Similar authentication failure was also visible for policy POLICY2.
Resolution
The network administrators found an NTLM problem which needed to be fixed.
NOTE: The user XCWATCH was defined as the user for Directory Watcher service as per the xcom-globals.xml file:
<AUTOMATIC_FILE_INSERTION START_SERVICE="YES" LOCALE_LANGUAGE="US" USERNAME="XCWATCH"/>
To be informed of any future failures/errors that user XCWATCH needs to be configured to send email notifications under "Manage Users".
Additional Information
Currently the XCOM Gateway is designed to stop the watch after 3 authentication retries to save resources and avoid unwanted continuous traffic when the network is broken.
So, those 3 retries means that any momentary intermittent failure should not cause a problem.
For a real significant network/authentication issue, the watch will be stopped and if configured an email notification should be received.
XCOM™ Data Transport® Gateway > Administrating > Policies > Create and Manage Policies
XCOM™ Data Transport® Gateway > Administrating > Policies > Policy Configuration Wizard >Configure Directory Watching
XCOM™ Data Transport® Gateway > Administrating > Users
Feedback
