Syslog feature does not work on WFA 5.1.1P3 and datasource acquisition remains on Scheduled state
- Views:
- 194
- Visibility:
- Public
- Votes:
- 0
- Category:
- oncommand-workflow-automation-wfa
- Specialty:
- legacy
- Last Updated:
Applies to
- OnCommand Workflow Automation 5.1.1P3 (WFA) installed in Windows.
- Enabled Syslog feature of WFA
Issue
When Syslog is enabled from WFA settings and WFA service is restarted:
- Every Data source acquisition stays in "Scheduled" status
- No workflow runs. Workflows are all paused.
- Error below is found on
server.log
:
2022-03-07 09:41:28,705 ERROR [org.jboss.as.ejb3.invocation] (ServerService Thread Pool -- 79) WFLYEJB0034: EJB Invocation failed on component SyslogServiceImpl for method public abstract void com.netapp.wfa.common.service.WfaService.start(): javax.ejb.EJBTransactionRolledbackException: WFLYEJB0457: Unexpected Error
....
aused by: java.lang.NoClassDefFoundError: javax/naming/Context
at org.apache.logging.log4j.api@2.16.0//org.apache.logging.log4j.core.lookup.Interpolator.<init>(Interpolator.java:112)
....
Caused by: java.lang.ClassNotFoundException: javax.naming.Context from [Module "org.apache.logging.log4j.api" version 2.16.0 from local module loader @3dd1dc90 (finder: local module finder @abf688e (roots: D:\NetApp\WFA\jboss\modules,D:\NetApp\WFA\jboss\modules\system\layers\base))]
at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:255)