AAOP 6.x - ConfigurationException in scheduler debug logs
2 years ago
Originally Published: 2014-05-22
Article Number
000052344
Applies To
1.If your Environment EFN is not active and you do not have Firewall & credentials settings added
2.However this is enabled from your Backoffice >scheduled tasks> EFN -->"True", then you will see the above  below DEBUG exception(please note: its not an "ERROR")

Issue
AAOP 6.x - ConfigurationException in scheduler debug logs
In scheduler logs you will see:
===================================
org.apache.axis.i18n.resource::handleGetObject(noService10) 
2014-05-06 12:48:00,796 DEBUG [scheduler_Worker-6] ConfigurationException - Exception: 
org.apache.axis.ConfigurationException: No service named eFraudNetwork is available 
org.apache.axis.ConfigurationException: No service named eFraudNetwork is available 
at org.apache.axis.configuration.FileProvider.getService(FileProvider.java:233) 
at org.apache.axis.AxisEngine.getService(AxisEngine.java:311) 
at org.apache.axis.MessageContext.setTargetService(MessageContext.java:756) 
at org.apache.axis.client.Call.invoke(Call.java:2690) 
at org.apache.axis.client.Call.invoke(Call.java:2443) 
at org.apache.axis.client.Call.invoke(Call.java:2366) 
at org.apache.axis.client.Call.invoke(Call.java:1812) 
at com.passmarksecurity.efn.ws.client.EFraudNetworkStub.updateRiskData(EFraudNetworkStub.java:245) 
at com.passmarksecurity.efn.BasicEfnClient.updateRiskDataService(BasicEfnClient.java:216) 
at com.passmarksecurity.efn.BasicEfnClient.updateLocalRiskData(BasicEfnClient.java:256) 
at com.passmarksecurity.efn.scheduler.EfnScheduler.process(EfnScheduler.java:35) 
at com.rsa.csd.scheduler.BatchJobWrapper.process(BatchJobWrapper.java:94) 
at com.rsa.csd.scheduler.BatchJobWrapper.executeInternal(BatchJobWrapper.java:78) 
at org.springframework.scheduling.quartz.QuartzJobBean.execute(QuartzJobBean.java:86) 
at org.quartz.core.JobRunShell.run(JobRunShell.java:202) 
at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:525) 
===================================

Workaround
To resolve the issue:
-Disable the EFN from your scheduled task> efn> set to "False"
-Save and Publish the changes
 
Please note this is only applicable for scenarion where customers do not have EFN enabled and do not want to use EFN.