XmlValueDisconnectedException when deleting a composite sensor in JDeveloper

(Doc ID 2312214.1)

Last updated on OCTOBER 05, 2017

Applies to:

Oracle SOA Suite - Version 12.2.1.0.0 to 12.2.1.2.0 [Release 12c]
Information in this document applies to any platform.

Symptoms

When using JDeveloper to delete a composite sensor in a SOA composite project, the following exception can occur :-

May 08, 2017 5:01:42 PM oracle.ideimpl.feedback2.client.FeedbackManagerImpluncaughtException
SEVERE: Uncaught Exception
org.apache.xmlbeans.impl.values.XmlValueDisconnectedException
at org.apache.xmlbeans.impl.values.XmlObjectBase.check_orphaned(XmlObjectBase.java:1258)
at com.oracle.xmlns.bpel.sensor.impl.TSensorImpl.getServiceConfig(Unknown Source)
at oracle.tip.tools.ide.fabric.sensors.ui.SensorsHandler.getSensorsListForNode(SensorsHandler.java:308)
at oracle.tip.tools.ide.fabric.sensors.ui.SensorsHandler.getSensorsList(SensorsHandler.java:134)

After this, until JDeveloper is restarted, sensors don't work quite as expected. eg.

- Deleting more sensors can cause more exceptions

- If all sensors are subsequently deleted from the Composite, the sensorAction.xml is not deleted (even though there are no longer any sensors configured). It needs to be deleted manually.



Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms