Interminent TransformerException: Could not determine the last modified timestamp
(Doc ID 2448272.1)
Last updated on FEBRUARY 19, 2019
Applies to:Oracle Communications Order and Service Management - Version 188.8.131.52.0 and later
Information in this document applies to any platform.
Customer developing an OSM COM solution using OSM version 184.108.40.206.1.B13
They observed the following issue in the logs when they tried to manually close a task from the OSM worklist.
javax.xml.transform.TransformerException: Could not determine the last modified timestamp of "zip:file:<DIR>/servers/XOSM_01/tmp/_WL_user/oms/oj4wat/APP-INF/
lib/osm-xml-rule.jar!/oracle/communications/ordermanagement/execution/orderComponentOrderItem.xquery" because it does not exist.. File[cp:oracle/communications/ordermanagement/execution/orderComponentOrderItem.xquery (actual location resolved to [cp:oracle/communications/ordermanagement/execution/orderComponentOrderItem.xquery]
The problem was resolved by performing a refresh cache in the server, therefore it seems for some reason the osm-xml-rule.jar could not be found in the tmp directory.
Please note also that the tmp parameter has been modified using startup parameter for the managed server : -Djava.io.tmpdir=<DIR>
After researching in the past logs , we found one more occurrence of this issue again for the same jar (osm-xml-rule.jar) , but the error is not reproduceable.
The system was behaving correctly during SIT testing for more than a week.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document