This KD covers the scenario of which all managed endpoints by this JCS server cannot be connected to. Simple actions like viewing the endpoint properties from provisioning manager produce the error above. If your case scenario only involve one or more but not ALL endpoints, this solution is not for you. If this does suite your scenario read on.
Note: This problem was observed on server running out of disk space.
Check the following JCS logs for these messages to see that indeed the same problem is qualified
ERROR - Unable to create application context for [com.ca.jcs.provisioning.adapter], unsatisfied dependencies: Dependency on [Additional information about depencies may vary)
ERROR - Application context refresh failed (OsgiBundleXmlApplicationContext(bundle=com.ca.jcs.provisioning.adapter, config=osgibundle:/META-INF/spring/*.xml))
Unable to create application context for [com.ca.jcs.provisioning.adapter]….
Exception in thread "Thread-##" java.lang.RuntimeException: JCS@<server_name>: Failed to initialise the standalone server manager
Caused by: javax.naming.NamingException: JCS@Iamappvprd1: Failed to create standalone configuration partition [Root exception is javax.naming.NamingException: JCS@<server_name>: Failed to create a JDBM partition: eTConfigContainerName=SA Configuration,dc=etasa [Root exception is javax.naming.NamingException [Root exception is java.io.StreamCorruptedException: invalid type code: 00]]]