Not Able To Deploy The Cartridge Using SadtClient or sadtConsole: Can't get Connection to Daemon!!!
(Doc ID 2085116.1)
Last updated on NOVEMBER 11, 2023
Applies to:
Oracle Communications ASAP - Version 7.2.0 and laterInformation in this document applies to any platform.
Symptoms
On ASAP 7.2.0 version, with the Service Access Deployment Tool
Customer not able to deploy the cartridge using sadtClient.
$ sadtClient deploy <CustomerCartridge>.sar
You are working from the function func01 ...
Uploading sar file....
.....................
Upload sar file completed.
Cannot connect to Daemon server
Activation model <Customer Cartridge>
The following error was seen in the Weblogic logs
Not able to deploy the cartridge using sadtclient
$ sadtClient deploy <Customer Cartridge>
You are working from the function func01 ...
Uploading sar file....
.....................
Upload sar file completed.
Cannot connect to Daemon server
Activation model <Customer Cartridge>
ERROR
-----------------------
The following error was seen in the Weblogic logs
<[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> java.io.IOException: Can't get Connection to Daemon!!!
at com.mslv.activation.daemon.utils.RemoteFile.(RemoteFile.java:58)
at com.mslv.activation.management.services.CartridgeMBean.deploy(CartridgeMBean.java:519)
at com.mslv.activation.management.services.CartridgeMBean.deploy(CartridgeMBean.java:469)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
BUSINESS IMPACT
-----------------------
Deployment can not be done on non-prod environment.
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 |