mod-erm-usage crashes when manually uploading certain COUNTER reports
Description
A user can upload a statistics file, formatted as defined in the COUNTER CoP releases 4 & 5.
When uploading some COUNTER files mod-erm-usage crashes. After selecting a file in the UI and pressing the upload button a dialog will appear to inform about the success of the operation. After uploading problematic files the message will be like
proxyClient failure: mod-erm-usage-2.10.0-SNAPSHOT.104 http://10.36.1.55:9133:Connection was closed
Subsequentely, when interacting with the eUsage app in the UI errors like the following will be shown. SysOp told me that the module died.
ERROR: in module @folio/erm-usage, operation GET on resource 'counterReports' failed, saying: proxyClient failure: mod-erm-usage-2.10.0-SNAPSHOT.104 http://10.36.1.55:9133: finishConnect(..) failed: Connection refused: /10.36.1.55:9133
A problematic json file (CoP R5) is attached (zipped:
thanks reporting the error. It seems as if the container memory limit was set too low. I increased the limit and tested it on the folio-testing environment, where it is working now. The provided report file is fine. Fix is included in the latest build mod-erm-usage-2.10.0-SNAPSHOT.105
A user can upload a statistics file, formatted as defined in the COUNTER CoP releases 4 & 5.
When uploading some COUNTER files mod-erm-usage crashes. After selecting a file in the UI and pressing the upload button a dialog will appear to inform about the success of the operation. After uploading problematic files the message will be like
proxyClient failure: mod-erm-usage-2.10.0-SNAPSHOT.104 http://10.36.1.55:9133:Connection was closedSubsequentely, when interacting with the eUsage app in the UI errors like the following will be shown. SysOp told me that the module died.
ERROR: in module @folio/erm-usage, operation GET on resource 'counterReports' failed, saying: proxyClient failure: mod-erm-usage-2.10.0-SNAPSHOT.104 http://10.36.1.55:9133: finishConnect(..) failed: Connection refused: /10.36.1.55:9133A problematic json file (CoP R5) is attached (zipped:
). To my knowledge the file itself is okay.