"java.lang.ClassCastException: org.hl7.v3.II cannot be cast to org.hl7.v3.INT" warnings in the logs during patient discovery

classic Classic list List threaded Threaded
8 messages Options
Reply | Threaded
Open this post in threaded view
|

"java.lang.ClassCastException: org.hl7.v3.II cannot be cast to org.hl7.v3.INT" warnings in the logs during patient discovery

Nick King
CONNECT version 4.4.1

When processing outbound patient discovery responses, we see the following in the Connect log:

[#|2016-03-03T14:21:02.892-0500|WARNING|glassfish3.1.2|org.apache.cxf.phase.PhaseInterceptorChain|_ThreadID=147;_ThreadName=Thread-2;|Interceptor for {urn:ihe:iti:xcpd:2009}RespondingGatewayPortTypeService#{urn:ihe:iti:xcpd:2009}RespondingGateway_PRPA_IN201305UV02 has thrown exception, unwinding now
java.lang.ClassCastException: org.hl7.v3.II cannot be cast to org.hl7.v3.INT
        at org.hl7.v3.PRPAMT201306UV02MinimumDegreeMatch$JaxbAccessorF_value.set(FieldAccessor_Ref.java:60)
        at com.sun.xml.bind.v2.runtime.reflect.Accessor.receive(Accessor.java:171)
        at com.sun.xml.bind.v2.runtime.unmarshaller.UnmarshallingContext.endElement(UnmarshallingContext.java:538)
        at com.sun.xml.bind.v2.runtime.unmarshaller.StAXStreamConnector.handleEndElement(StAXStreamConnector.java:221)
        at com.sun.xml.bind.v2.runtime.unmarshaller.StAXStreamConnector.bridge(StAXStreamConnector.java:185){code}

The patient discovery response appears to be valid as we can see in the CONNECT log prior to the exception. The relevant query snippet from the patient discovery response is as follows:

<matchCriterionList>
        <matchAlgorithm>
                <typeId/>
                <value xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="II"/>
                <semanticsText/>
        </matchAlgorithm>
        <matchWeight>
                <typeId/>
                <value xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="II"/>
                <semanticsText/>
        </matchWeight>
        <minimumDegreeMatch>
                <typeId/>
                <value xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="II"/>
                <semanticsText/>
        </minimumDegreeMatch>
</matchCriterionList>

Any help with solving this issue would be appreciated. Thanks
Reply | Threaded
Open this post in threaded view
|

Re: "java.lang.ClassCastException: org.hl7.v3.II cannot be cast to org.hl7.v3.INT" warnings in the logs during patient discovery

Sovann Huynh
Administrator
Hi Nick,

Is this happening on the initiating gateway after receiving the response or is it happening on the responding gateway as it's generating a response? It sounds like you're seeing this in the initiating log after receiving a response but I'd like to clarify.

Sovann
Sovann
CONNECT Product Team Member
Reply | Threaded
Open this post in threaded view
|

Re: "java.lang.ClassCastException: org.hl7.v3.II cannot be cast to org.hl7.v3.INT" warnings in the logs during patient discovery

Nick King
Hi Sovann,

This is happening on the initiating gateway after receiving the response. We're seeing this in the initiating log after receiving a response.

Thanks
Reply | Threaded
Open this post in threaded view
|

Re: "java.lang.ClassCastException: org.hl7.v3.II cannot be cast to org.hl7.v3.INT" warnings in the logs during patient discovery

Sovann Huynh
Administrator
Thanks, Nick. Is there correlated patient data in the response? Are you able to use the response to create patient correlations?
Sovann
CONNECT Product Team Member
Reply | Threaded
Open this post in threaded view
|

Re: "java.lang.ClassCastException: org.hl7.v3.II cannot be cast to org.hl7.v3.INT" warnings in the logs during patient discovery

Nick King
The request doesn't find a matching patient so no correlation could be created. The exception looks to be happening before that step though when the response is being unmarshalled.
Reply | Threaded
Open this post in threaded view
|

Re: "java.lang.ClassCastException: org.hl7.v3.II cannot be cast to org.hl7.v3.INT" warnings in the logs during patient discovery

Sovann Huynh
Administrator
In reply to this post by Nick King
Are you running SoapUI validation suite tests? I'll look into this more when I get a chance but for now, can you set the following property to "trust" in gateway.properties, restart your server and see if that error still occurs?

#response modes: verify|trust|passthrough
patientDiscoveryResponseMode=trust
Sovann
CONNECT Product Team Member
Reply | Threaded
Open this post in threaded view
|

Re: "java.lang.ClassCastException: org.hl7.v3.II cannot be cast to org.hl7.v3.INT" warnings in the logs during patient discovery

Sovann Huynh
Administrator
Nick, can you also provide us with your complete PD response message?
Sovann
CONNECT Product Team Member
Reply | Threaded
Open this post in threaded view
|

Re: "java.lang.ClassCastException: org.hl7.v3.II cannot be cast to org.hl7.v3.INT" warnings in the logs during patient discovery

Nick King
The responding gateway has made a change on their end which has stopped this error occurring. However, we are now seeing the following error,

http://forums.connectopensource.org/Unable-to-unmarshall-CONNECT-entity-PD-response-td7580161.html