Deployed error for sar file: waitSaveStart: response not REM_SAVE_FILE_START
(Doc ID 2370320.1)
Last updated on DECEMBER 16, 2024
Applies to:
Oracle Communications ASAP - Version 7.3.0.0.0 and laterInformation in this document applies to any platform.
Symptoms
A custom cartridge sar has a different deployment behaviour as follows:
ASAP Release R7_3_0_P1 -> Successfully deployed.
ASAP Release R7_3_0_P2 -> Same deployment error.
ASAP Release R7_3_0_P3 -> Same deployment error.
The error thrown is as follows:
$ sadtClient deploy XXXXX.sar
You are working from the function func01 ...
An instance with the same ID as provided is found, attempting to replace existing ID.
Uploading sar file....
...................................................................................................................................................................................................................................
Upload sar file completed.
waitSaveStart: response not REM_SAVE_FILE_START.
Activation model < XXXXX.sar> is not deployed
DAEMAS9.diag
>> 112056.624:Thread-20:LOW :com.mslv.activation.daemon.utils.RemoteFile:
RemoteFile: REM_REQ_SAVE_FILE received.
>> 112056.624:Thread-20:LOW :com.mslv.activation.daemon.utils.RemoteFile:
RemoteFile: getFileName()= ojdbc6.jar
>> 112056.625:Thread-20:SANE:com.mslv.activation.daemon.server.ASAPDaemonHandler:
An exception in ASAPDaemonHandler: null
>> 112056.626:Thread-20:SANE:com.mslv.activation.daemon.server.ASAPDaemonHandler:
java.lang.NullPointerException
at java.io.File.<init>(File.java:277)
at com.mslv.activation.daemon.utils.RemoteFile.doSave(RemoteFile.java:876)
at com.mslv.activation.daemon.utils.RemoteFile.process(RemoteFile.java:544)
at com.mslv.activation.daemon.server.ASAPDaemonHandler.run(ASAPDaemonHandler.java:77)
WLS nohup.out
<file:/<domain_home>/oracle_communications/asap/ASAP_BASE/activationModels/.new/XXXXX.sar>>
<01-Mar-2018 11:20:56,635 GST AM> <ERROR> <services.ActivationModelBean> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <Can't get Connection to ASAP Daemon!!! Reason: waitSaveStart: response not REM_SAVE_FILE_START.>
java.io.IOException: Can't get Connection to ASAP Daemon!!! Reason: waitSaveStart: response not REM_SAVE_FILE_START.
at com.mslv.activation.daemon.utils.RemoteFile.put(RemoteFile.java:412)
at com.mslv.activation.daemon.utils.RemoteFile.put(RemoteFile.java:380)
at com.mslv.activation.services.ActivationModelBean.deployJ(ActivationModelBean.java:449)
at com.mslv.activation.services.ActivationModelBean.deploy(ActivationModelBean.java:180)
...
...
Caused by: java.io.IOException: waitSaveStart: response not REM_SAVE_FILE_START.
at com.mslv.activation.daemon.utils.RemoteFile.waitSaveStart(RemoteFile.java:730)
at com.mslv.activation.daemon.utils.RemoteFile.put(RemoteFile.java:404)
... 44 more
<01-Mar-2018 11:20:56,644 GST AM> <ERROR> <i18n.sadt_ejbLogger> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <Model XXXXX: Failed to deploy Java library lib/ojdbc6.jar>
Changes
Cause
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
Symptoms |
Changes |
Cause |
Solution |
References |