ElectronicInvoiceExtractJob - This is obsolete
Description:
This job retrieves invoices from the staging directory and processes them. The Invoices are transmitted from SciQuest. Either payment request or electronic invoice reject eDocs are created.
Error Found:
Stack trace with the following error:
Â
INFO edu.uconn.kuali.kfs.module.purap.service.impl.ElectronicInvoiceHelperServiceImpl :: Invoice Base Directory - /srv/uconn_configs/kfs-config/work/dev/kfs/staging/purap/electronicInvoiceÂ
INFO edu.uconn.kuali.kfs.module.purap.service.impl.ElectronicInvoiceHelperServiceImpl :: Invoice Accept Directory - /srv/uconn_configs/kfs-config/work/dev/kfs/staging/purap/electronicInvoice/accept/
INFO edu.uconn.kuali.kfs.module.purap.service.impl.ElectronicInvoiceHelperServiceImpl :: Invoice Reject Directory - /srv/uconn_configs/kfs-config/work/dev/kfs/staging/purap/electronicInvoice/reject/
INFO edu.uconn.kuali.kfs.module.purap.service.impl.ElectronicInvoiceHelperServiceImpl :: Is moving files allowed - true
INFO edu.uconn.kuali.kfs.module.purap.service.impl.ElectronicInvoiceHelperServiceImpl :: 1 file(s) available for processing
INFO edu.uconn.kuali.kfs.module.purap.service.impl.ElectronicInvoiceHelperServiceImpl :: Processing 12407692.xml....
INFO edu.uconn.kuali.kfs.module.purap.service.impl.ElectronicInvoiceHelperServiceImpl :: Adding namespace definition
INFO edu.uconn.kuali.kfs.module.purap.service.impl.ElectronicInvoiceHelperServiceImpl :: Namespace validation completedÂ
INFO edu.uconn.kuali.kfs.module.purap.service.impl.ElectronicInvoiceHelperServiceImpl :: Loading Invoice File Â
ERROR org.kuali.kfs.sys.batch.XmlBatchInputFileTypeBase :: error getting schema stream from url: Connection refused Â
ERROR edu.uconn.kuali.kfs.module.purap.service.impl.ElectronicInvoiceHelperServiceImpl :: 12407692.xml
ERROR edu.uconn.kuali.kfs.module.purap.service.impl.ElectronicInvoiceHelperServiceImpl :: java.lang.RuntimeException: error getting schema stream from url: Connection refused
Resolution:
Â
The electronic invoice batch process uses the ${externalizable.static.content.url} for defining the file paths. This variable points to a server node. If any of the server nodes are not up then this would resolve to null. This will cause null pointer exception where ever it is being used, which results is objects being initialized to null and leads to other errors. Below are some of the error messages we have encountered because of this:
Â
java.lang.RuntimeException: error getting schema stream from urlÂ
Â
null/null_20130430-22-40-01-576.null not found Â
Â
null/null_null.null (No such file or directory)Â
Â
 Â
Rerun the job when all nodes are active.