Hi,
I recently got this issue without our AES 6.1 when using DMCC Service Observer. The exception is
PM com.avaya.proxy.castor.CastorUnmarshaller unmarshal
WARNING: Could not unmarshal: <?xml version="1.0" encoding="UTF-8"?>
<ServiceLinkStatusEvent xmlns="http://www.avaya.com/csta"><ns1:monitorCrossRefID xmlns:ns1="http://www.ecma-international.org/standards/ecma-323/csta/ed3">221</ns1:monitorCrossRefID><device><ns2:deviceIdentifier xmlns:ns2="http://www.ecma-international.org/standards/ecma-323/csta/ed3" typeOfNumber="other" mediaClass="voice" bitRate="constant">9600:AvayaAcm:172.25.8.20:0</ns2:deviceIdentifier></device><serviceLinkUp>true</serviceLinkUp></ServiceLinkStatusEvent>
The class for the root element 'ServiceLinkStatusEvent' could not be found.{file: [not available]; line: 2; column: 59}
at org.exolab.castor.xml.Unmarshaller.unmarshal(Unknown Source)
at org.exolab.castor.xml.Unmarshaller.unmarshal(Unknown Source)
at com.avaya.proxy.castor.CastorUnmarshaller.unmarshal(CastorUnmarshaller.java:186)
at com.avaya.mvcs.proxy.CstaUnmarshallerNode$CstaUnmarshallerProcessorThread.run(CstaUnmarshallerNode.java:198)
at com.avaya.common.util.concurrent.impl.RunnableWrapper.run(RunnableWrapper.java:57)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Caused by: org.xml.sax.SAXException: The class for the root element 'ServiceLinkStatusEvent' could not be found.

I found this release note https://downloads.avaya.com/css/P8/documents/100176246 related to ServiceLinkStatusEvent issue, however, look like its only apply for AES6.2, while we are at 6.1

Please advise

That document lists the fixes in AE Services 6.2.0 Super Patch 4, so probably the problem existed in previous releases, including 6.1.

Unfortunately, the bug number is from an older reporting tool and I cannot find any mention of it in our current tool. Therefore, I do not know if the problem was fixed in the DMCC Client, AE Services or the sample application. I would suspect, that the fix was applied in the DMCC Client. In this case, you could download and use a newer version of the client - this may fix the problem.

Alternatively, if this warning is not causing you any problems, you could ignore it.

Martin

Hi,
We upgraded to 6.3 and the issue still persist? Do you have any other idea?

What did you upgrade - the AE Services or the Client library?

Martin

We upgraded AES
About the "client library", do you mean the SDK?

We upgrade the SDK to latest 7.1 and got the same exception. Any advise?
Thanks

Make sure you are using the 7.1 version of the mappings files when you run the application.

Now iam running our application which was built with sdk 7.1 and latest mapping files, still the same exceptions

2018-05-08 20:52:37,237 com.avaya.proxy.castor.CastorUnmarshaller WARNING - Could not unmarshal: <?xml version="1.0" encoding="UTF-8"?>
<ServiceLinkStatusEvent xmlns="http://www.avaya.com/csta"><ns1:monitorCrossRefID xmlns:ns1="http://www.ecma-international.org/standards/ecma-323/csta/ed3">335</ns1:monitorCrossRefID><device><ns2:deviceIdentifier xmlns:ns2="http://www.ecma-international.org/standards/ecma-323/csta/ed3" typeOfNumber="other" mediaClass="voice" bitRate="constant">9600:AvayaAcm:172.25.8.20:0</ns2:deviceIdentifier></device><serviceLinkUp>true</serviceLinkUp></ServiceLinkStatusEvent>
The class for the root element 'ServiceLinkStatusEvent' could not be found.{file: [not available]; line: 2; column: 59}
at org.exolab.castor.xml.Unmarshaller.unmarshal(Unknown Source)
at org.exolab.castor.xml.Unmarshaller.unmarshal(Unknown Source)
at com.avaya.proxy.castor.CastorUnmarshaller.unmarshal(CastorUnmarshaller.java:186)
at com.avaya.mvcs.proxy.CstaUnmarshallerNode$CstaUnmarshallerProcessorThread.run(CstaUnmarshallerNode.java:198)
at com.avaya.common.util.concurrent.impl.RunnableWrapper.run(RunnableWrapper.java:57)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Caused by: org.xml.sax.SAXException: The class for the root element 'ServiceLinkStatusEvent' could not be found.
at org.exolab.castor.xml.UnmarshalHandler.startElement(Unknown Source)
at org.exolab.castor.xml.UnmarshalHandler.startElement(Unknown Source)
at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source)
at org.apache.xerces.impl.dtd.XMLDTDValidator.startElement(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanStartElement(Unknown Source)
at org.apache.xerces.impl.XMLDocumentScannerImpl$ContentDispatcher.scanRootElementHook(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)

Hi Bruno,

An incompatibility was introduced in DMCC Java SDK 7.1.1. This means that you will not get ServiceLinkStatusEvents when using client 7.1.1 (or later) with an older version of AE Services.

However, all other versions of the SDK (7.1.0 and older) are compatible with older versions of AE Services. For example, I do get ServiceLinkStatusEvents with SDK 7.1.0 and my AE Services 6.3.3.

I think I have gone as far as I can in the forum on this issue. If you need further help, please open a Technical Support ticket. Please note, for non-paid members, there is a fee for this service.

Martin