Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Archived » OHF » XCA error codes not recognized
XCA error codes not recognized [message #47644] Wed, 10 September 2008 18:36 Go to next message
Jesse Pangburn is currently offline Jesse Pangburn
Messages: 166
Registered: July 2009
Senior Member
Hi,
So, I'm doing some XCA error testing on the bridge and I sent back the
following "Partial Success" stuff:
[DEBUG][11:29:19][hf.ihe.xds.consumer.B_Consumer] Got response :
<ns5:AdhocQuery
Response

status=" urn:oasis:names:tc:ebxml-regrep:ResponseStatusType:PartialSu ccess "
xmlns:ns2="urn:oasis:names:tc:ebxml-regrep:xsd:rim:3.0"
xmlns:ns3="urn:oasis:names:tc:ebxml-regrep:xsd:rs:3.0"
xmlns:ns4="urn:oasis:names:tc:ebxml-regrep:xsd:lcm:3.0"
xmlns:ns5="urn:oasis:names:tc:ebxml-regrep:xsd:query:3.0"
xmlns:ns6="urn:ihe
:iti:xds-b:2007">
<ns3:RegistryErrorList>
<ns3:RegistryError
codeContext="Initiating Gateway Error: caught exception trying
to call receiving gateway 'NIST Public Receiving Gateway'"
errorCode="XDSUnavailableCommunity"

location=" com.healthvision.initiatinggateway.webservice.InitiatingGate wayService.sendQueryToReceivingGateway(InitiatingGatewayServ ice.java:304) "
severity="urn:oasis:names:tc:ebxml-regrep:ErrorSeverityType:Error "/>
</ns3:RegistryErrorList>
<ns2:RegistryObjectList>
<ns2:ExtrinsicObject home="urn:oid:1.19.6.24.109.42.1.3"
...

There are two objects from another gateway that are returned successfully,
and you can see the status is PartialSuccess. There are two problems I
see after that. First, when the error is displayed in the log, the new
XCA error "XDSUnavailableCommunity" seems to be replaced with
"UNKNOWNERROR" indicating the Bridge is not aware of the XCA codes:
[DEBUG][11:29:19][.ohf.ihe.xds.XDSResponseParser] Loading response in EMF.
[DEBUG][11:29:19][.ohf.ihe.xds.XDSResponseParser] Partial Success.
[DEBUG][11:29:19][.ohf.ihe.xds.XDSResponseParser] RegistryResponse error 0
code
is unrecognized.
[INFO ][11:29:19][.ohf.ihe.xds.XDSResponseParser] Error #0
Severity=Error
Code=UNKNOWNERROR
Code Context=Initiating Gateway Error: caught exception trying to
call r
eceiving gateway 'NIST Public Receiving Gateway'
Location=
com.healthvision.initiatinggateway.webservice.InitiatingGate wa
yService.sendQueryToReceivingGateway(InitiatingGatewayServic e.java:304)


- Error #0
Severity=Error
Code=UNKNOWNERROR
Code Context=Initiating Gateway Error: caught exception trying to
call r
eceiving gateway 'NIST Public Receiving Gateway'
Location=
com.healthvision.initiatinggateway.webservice.InitiatingGate wa
yService.sendQueryToReceivingGateway(InitiatingGatewayServic e.java:304)


The second problem is that the bridge says it got 0 documents, when the
log showed that it received two. Additionally, the response shows as [0]
which I believe is your success status:
[DEBUG][11:29:19][se.ohf.bridge.ihe.IheXdsBridge] got 0 documents by
QueryDocumentsByPatientId(PatientIdType ( idNumber=[01bfd2ebbd3743d]
assigningAuthority=[AssigningAuthority ( namespaceId=[]
universalId=[1.3.6.1.4.1.21367.2005.3.7] universalIdType=[ISO]
useDefaultAssigningAuthority=[false] universalIdTypeCode=[] )]
))
[DEBUG][11:29:19][clipse.ohf.bridge.ws.OHFBridge] returning response:
ResponseType ( response=[0] ) QueryDocumentsResponseType (
documentTypeArray=[] )
[DEBUG][11:29:19][clipse.ohf.bridge.ws.OHFBridge] got 0
documents:ResponseType ( response=[0] ) QueryDocumentsResponseType (
documentTypeArray=[] )

thanks,
Jesse
Re: XCA error codes not recognized [message #47734 is a reply to message #47644] Wed, 10 September 2008 19:17 Go to previous messageGo to next message
No real name is currently offline No real name
Messages: 292
Registered: July 2009
Senior Member
Hi Jesse -- these are new error codes introduced via CP for 2009. I have
these implemented, just not dropped into the repository as there are few
more CPs for 2009 that we'd like to knock off. Hopefully something by
next week to attack this issue.

- Sarah

Jesse Pangburn wrote:
> Hi,
> So, I'm doing some XCA error testing on the bridge and I sent back the
> following "Partial Success" stuff:
> [DEBUG][11:29:19][hf.ihe.xds.consumer.B_Consumer] Got response :
> <ns5:AdhocQuery
> Response
>
> status=" urn:oasis:names:tc:ebxml-regrep:ResponseStatusType:PartialSu ccess "
> xmlns:ns2="urn:oasis:names:tc:ebxml-regrep:xsd:rim:3.0"
> xmlns:ns3="urn:oasis:names:tc:ebxml-regrep:xsd:rs:3.0"
> xmlns:ns4="urn:oasis:names:tc:ebxml-regrep:xsd:lcm:3.0"
> xmlns:ns5="urn:oasis:names:tc:ebxml-regrep:xsd:query:3.0"
> xmlns:ns6="urn:ihe
> :iti:xds-b:2007">
> <ns3:RegistryErrorList>
> <ns3:RegistryError
> codeContext="Initiating Gateway Error: caught exception
> trying to call receiving gateway 'NIST Public Receiving Gateway'"
> errorCode="XDSUnavailableCommunity"
>
> location=" com.healthvision.initiatinggateway.webservice.InitiatingGate wayService.sendQueryToReceivingGateway(InitiatingGatewayServ ice.java:304) "
> severity="urn:oasis:names:tc:ebxml-regrep:ErrorSeverityType:Error "/>
> </ns3:RegistryErrorList>
> <ns2:RegistryObjectList>
> <ns2:ExtrinsicObject home="urn:oid:1.19.6.24.109.42.1.3"
> ...
>
> There are two objects from another gateway that are returned
> successfully, and you can see the status is PartialSuccess. There are
> two problems I see after that. First, when the error is displayed in
> the log, the new XCA error "XDSUnavailableCommunity" seems to be
> replaced with "UNKNOWNERROR" indicating the Bridge is not aware of the
> XCA codes:
> [DEBUG][11:29:19][.ohf.ihe.xds.XDSResponseParser] Loading response in EMF.
> [DEBUG][11:29:19][.ohf.ihe.xds.XDSResponseParser] Partial Success.
> [DEBUG][11:29:19][.ohf.ihe.xds.XDSResponseParser] RegistryResponse error
> 0 code
> is unrecognized.
> [INFO ][11:29:19][.ohf.ihe.xds.XDSResponseParser] Error #0
> Severity=Error
> Code=UNKNOWNERROR
> Code Context=Initiating Gateway Error: caught exception trying to
> call r
> eceiving gateway 'NIST Public Receiving Gateway'
> Location=
> com.healthvision.initiatinggateway.webservice.InitiatingGate wa
> yService.sendQueryToReceivingGateway(InitiatingGatewayServic e.java:304)
>
>
> - Error #0
> Severity=Error
> Code=UNKNOWNERROR
> Code Context=Initiating Gateway Error: caught exception trying to
> call r
> eceiving gateway 'NIST Public Receiving Gateway'
> Location=
> com.healthvision.initiatinggateway.webservice.InitiatingGate wa
> yService.sendQueryToReceivingGateway(InitiatingGatewayServic e.java:304)
>
>
> The second problem is that the bridge says it got 0 documents, when the
> log showed that it received two. Additionally, the response shows as
> [0] which I believe is your success status:
> [DEBUG][11:29:19][se.ohf.bridge.ihe.IheXdsBridge] got 0 documents by
> QueryDocumentsByPatientId(PatientIdType ( idNumber=[01bfd2ebbd3743d]
> assigningAuthority=[AssigningAuthority ( namespaceId=[]
> universalId=[1.3.6.1.4.1.21367.2005.3.7] universalIdType=[ISO]
> useDefaultAssigningAuthority=[false] universalIdTypeCode=[]
> )] ))
> [DEBUG][11:29:19][clipse.ohf.bridge.ws.OHFBridge] returning response:
> ResponseType ( response=[0] ) QueryDocumentsResponseType (
> documentTypeArray=[] )
> [DEBUG][11:29:19][clipse.ohf.bridge.ws.OHFBridge] got 0
> documents:ResponseType ( response=[0] ) QueryDocumentsResponseType (
> documentTypeArray=[] )
>
> thanks,
> Jesse
>
Re: XCA error codes not recognized [message #47765 is a reply to message #47734] Wed, 10 September 2008 23:27 Go to previous message
Jesse Pangburn is currently offline Jesse Pangburn
Messages: 166
Registered: July 2009
Senior Member
Hi Sarah,
OK cool, no rush, just wanted to make sure these were on "the list" :-)

thanks,
Jesse

Sarah Knoop wrote:

> Hi Jesse -- these are new error codes introduced via CP for 2009. I have
> these implemented, just not dropped into the repository as there are few
> more CPs for 2009 that we'd like to knock off. Hopefully something by
> next week to attack this issue.

> - Sarah

> Jesse Pangburn wrote:
>> Hi,
>> So, I'm doing some XCA error testing on the bridge and I sent back the
>> following "Partial Success" stuff:
>> [DEBUG][11:29:19][hf.ihe.xds.consumer.B_Consumer] Got response :
>> <ns5:AdhocQuery
>> Response
>>
>> status=" urn:oasis:names:tc:ebxml-regrep:ResponseStatusType:PartialSu ccess "
>> xmlns:ns2="urn:oasis:names:tc:ebxml-regrep:xsd:rim:3.0"
>> xmlns:ns3="urn:oasis:names:tc:ebxml-regrep:xsd:rs:3.0"
>> xmlns:ns4="urn:oasis:names:tc:ebxml-regrep:xsd:lcm:3.0"
>> xmlns:ns5="urn:oasis:names:tc:ebxml-regrep:xsd:query:3.0"
>> xmlns:ns6="urn:ihe
>> :iti:xds-b:2007">
>> <ns3:RegistryErrorList>
>> <ns3:RegistryError
>> codeContext="Initiating Gateway Error: caught exception
>> trying to call receiving gateway 'NIST Public Receiving Gateway'"
>> errorCode="XDSUnavailableCommunity"
>>
>>
location=" com.healthvision.initiatinggateway.webservice.InitiatingGate wayService.sendQueryToReceivingGateway(InitiatingGatewayServ ice.java:304) "
>> severity="urn:oasis:names:tc:ebxml-regrep:ErrorSeverityType:Error "/>
>> </ns3:RegistryErrorList>
>> <ns2:RegistryObjectList>
>> <ns2:ExtrinsicObject home="urn:oid:1.19.6.24.109.42.1.3"
>> ...
>>
>> There are two objects from another gateway that are returned
>> successfully, and you can see the status is PartialSuccess. There are
>> two problems I see after that. First, when the error is displayed in
>> the log, the new XCA error "XDSUnavailableCommunity" seems to be
>> replaced with "UNKNOWNERROR" indicating the Bridge is not aware of the
>> XCA codes:
>> [DEBUG][11:29:19][.ohf.ihe.xds.XDSResponseParser] Loading response in EMF.
>> [DEBUG][11:29:19][.ohf.ihe.xds.XDSResponseParser] Partial Success.
>> [DEBUG][11:29:19][.ohf.ihe.xds.XDSResponseParser] RegistryResponse error
>> 0 code
>> is unrecognized.
>> [INFO ][11:29:19][.ohf.ihe.xds.XDSResponseParser] Error #0
>> Severity=Error
>> Code=UNKNOWNERROR
>> Code Context=Initiating Gateway Error: caught exception trying to
>> call r
>> eceiving gateway 'NIST Public Receiving Gateway'
>> Location=
>> com.healthvision.initiatinggateway.webservice.InitiatingGate wa
>> yService.sendQueryToReceivingGateway(InitiatingGatewayServic e.java:304)
>>
>>
>> - Error #0
>> Severity=Error
>> Code=UNKNOWNERROR
>> Code Context=Initiating Gateway Error: caught exception trying to
>> call r
>> eceiving gateway 'NIST Public Receiving Gateway'
>> Location=
>> com.healthvision.initiatinggateway.webservice.InitiatingGate wa
>> yService.sendQueryToReceivingGateway(InitiatingGatewayServic e.java:304)
>>
>>
>> The second problem is that the bridge says it got 0 documents, when the
>> log showed that it received two. Additionally, the response shows as
>> [0] which I believe is your success status:
>> [DEBUG][11:29:19][se.ohf.bridge.ihe.IheXdsBridge] got 0 documents by
>> QueryDocumentsByPatientId(PatientIdType ( idNumber=[01bfd2ebbd3743d]
>> assigningAuthority=[AssigningAuthority ( namespaceId=[]
>> universalId=[1.3.6.1.4.1.21367.2005.3.7] universalIdType=[ISO]
>> useDefaultAssigningAuthority=[false] universalIdTypeCode=[]
>> )] ))
>> [DEBUG][11:29:19][clipse.ohf.bridge.ws.OHFBridge] returning response:
>> ResponseType ( response=[0] ) QueryDocumentsResponseType (
>> documentTypeArray=[] )
>> [DEBUG][11:29:19][clipse.ohf.bridge.ws.OHFBridge] got 0
>> documents:ResponseType ( response=[0] ) QueryDocumentsResponseType (
>> documentTypeArray=[] )
>>
>> thanks,
>> Jesse
>>
Re: XCA error codes not recognized [message #587557 is a reply to message #47644] Wed, 10 September 2008 19:17 Go to previous message
No real name is currently offline No real name
Messages: 292
Registered: July 2009
Senior Member
Hi Jesse -- these are new error codes introduced via CP for 2009. I have
these implemented, just not dropped into the repository as there are few
more CPs for 2009 that we'd like to knock off. Hopefully something by
next week to attack this issue.

- Sarah

Jesse Pangburn wrote:
> Hi,
> So, I'm doing some XCA error testing on the bridge and I sent back the
> following "Partial Success" stuff:
> [DEBUG][11:29:19][hf.ihe.xds.consumer.B_Consumer] Got response :
> <ns5:AdhocQuery
> Response
>
> status=" urn:oasis:names:tc:ebxml-regrep:ResponseStatusType:PartialSu ccess "
> xmlns:ns2="urn:oasis:names:tc:ebxml-regrep:xsd:rim:3.0"
> xmlns:ns3="urn:oasis:names:tc:ebxml-regrep:xsd:rs:3.0"
> xmlns:ns4="urn:oasis:names:tc:ebxml-regrep:xsd:lcm:3.0"
> xmlns:ns5="urn:oasis:names:tc:ebxml-regrep:xsd:query:3.0"
> xmlns:ns6="urn:ihe
> :iti:xds-b:2007">
> <ns3:RegistryErrorList>
> <ns3:RegistryError
> codeContext="Initiating Gateway Error: caught exception
> trying to call receiving gateway 'NIST Public Receiving Gateway'"
> errorCode="XDSUnavailableCommunity"
>
> location=" com.healthvision.initiatinggateway.webservice.InitiatingGate wayService.sendQueryToReceivingGateway(InitiatingGatewayServ ice.java:304) "
> severity="urn:oasis:names:tc:ebxml-regrep:ErrorSeverityType:Error "/>
> </ns3:RegistryErrorList>
> <ns2:RegistryObjectList>
> <ns2:ExtrinsicObject home="urn:oid:1.19.6.24.109.42.1.3"
> ...
>
> There are two objects from another gateway that are returned
> successfully, and you can see the status is PartialSuccess. There are
> two problems I see after that. First, when the error is displayed in
> the log, the new XCA error "XDSUnavailableCommunity" seems to be
> replaced with "UNKNOWNERROR" indicating the Bridge is not aware of the
> XCA codes:
> [DEBUG][11:29:19][.ohf.ihe.xds.XDSResponseParser] Loading response in EMF.
> [DEBUG][11:29:19][.ohf.ihe.xds.XDSResponseParser] Partial Success.
> [DEBUG][11:29:19][.ohf.ihe.xds.XDSResponseParser] RegistryResponse error
> 0 code
> is unrecognized.
> [INFO ][11:29:19][.ohf.ihe.xds.XDSResponseParser] Error #0
> Severity=Error
> Code=UNKNOWNERROR
> Code Context=Initiating Gateway Error: caught exception trying to
> call r
> eceiving gateway 'NIST Public Receiving Gateway'
> Location=
> com.healthvision.initiatinggateway.webservice.InitiatingGate wa
> yService.sendQueryToReceivingGateway(InitiatingGatewayServic e.java:304)
>
>
> - Error #0
> Severity=Error
> Code=UNKNOWNERROR
> Code Context=Initiating Gateway Error: caught exception trying to
> call r
> eceiving gateway 'NIST Public Receiving Gateway'
> Location=
> com.healthvision.initiatinggateway.webservice.InitiatingGate wa
> yService.sendQueryToReceivingGateway(InitiatingGatewayServic e.java:304)
>
>
> The second problem is that the bridge says it got 0 documents, when the
> log showed that it received two. Additionally, the response shows as
> [0] which I believe is your success status:
> [DEBUG][11:29:19][se.ohf.bridge.ihe.IheXdsBridge] got 0 documents by
> QueryDocumentsByPatientId(PatientIdType ( idNumber=[01bfd2ebbd3743d]
> assigningAuthority=[AssigningAuthority ( namespaceId=[]
> universalId=[1.3.6.1.4.1.21367.2005.3.7] universalIdType=[ISO]
> useDefaultAssigningAuthority=[false] universalIdTypeCode=[]
> )] ))
> [DEBUG][11:29:19][clipse.ohf.bridge.ws.OHFBridge] returning response:
> ResponseType ( response=[0] ) QueryDocumentsResponseType (
> documentTypeArray=[] )
> [DEBUG][11:29:19][clipse.ohf.bridge.ws.OHFBridge] got 0
> documents:ResponseType ( response=[0] ) QueryDocumentsResponseType (
> documentTypeArray=[] )
>
> thanks,
> Jesse
>
Re: XCA error codes not recognized [message #587571 is a reply to message #47734] Wed, 10 September 2008 23:27 Go to previous message
Jesse Pangburn is currently offline Jesse Pangburn
Messages: 166
Registered: July 2009
Senior Member
Hi Sarah,
OK cool, no rush, just wanted to make sure these were on "the list" :-)

thanks,
Jesse

Sarah Knoop wrote:

> Hi Jesse -- these are new error codes introduced via CP for 2009. I have
> these implemented, just not dropped into the repository as there are few
> more CPs for 2009 that we'd like to knock off. Hopefully something by
> next week to attack this issue.

> - Sarah

> Jesse Pangburn wrote:
>> Hi,
>> So, I'm doing some XCA error testing on the bridge and I sent back the
>> following "Partial Success" stuff:
>> [DEBUG][11:29:19][hf.ihe.xds.consumer.B_Consumer] Got response :
>> <ns5:AdhocQuery
>> Response
>>
>> status=" urn:oasis:names:tc:ebxml-regrep:ResponseStatusType:PartialSu ccess "
>> xmlns:ns2="urn:oasis:names:tc:ebxml-regrep:xsd:rim:3.0"
>> xmlns:ns3="urn:oasis:names:tc:ebxml-regrep:xsd:rs:3.0"
>> xmlns:ns4="urn:oasis:names:tc:ebxml-regrep:xsd:lcm:3.0"
>> xmlns:ns5="urn:oasis:names:tc:ebxml-regrep:xsd:query:3.0"
>> xmlns:ns6="urn:ihe
>> :iti:xds-b:2007">
>> <ns3:RegistryErrorList>
>> <ns3:RegistryError
>> codeContext="Initiating Gateway Error: caught exception
>> trying to call receiving gateway 'NIST Public Receiving Gateway'"
>> errorCode="XDSUnavailableCommunity"
>>
>>
location=" com.healthvision.initiatinggateway.webservice.InitiatingGate wayService.sendQueryToReceivingGateway(InitiatingGatewayServ ice.java:304) "
>> severity="urn:oasis:names:tc:ebxml-regrep:ErrorSeverityType:Error "/>
>> </ns3:RegistryErrorList>
>> <ns2:RegistryObjectList>
>> <ns2:ExtrinsicObject home="urn:oid:1.19.6.24.109.42.1.3"
>> ...
>>
>> There are two objects from another gateway that are returned
>> successfully, and you can see the status is PartialSuccess. There are
>> two problems I see after that. First, when the error is displayed in
>> the log, the new XCA error "XDSUnavailableCommunity" seems to be
>> replaced with "UNKNOWNERROR" indicating the Bridge is not aware of the
>> XCA codes:
>> [DEBUG][11:29:19][.ohf.ihe.xds.XDSResponseParser] Loading response in EMF.
>> [DEBUG][11:29:19][.ohf.ihe.xds.XDSResponseParser] Partial Success.
>> [DEBUG][11:29:19][.ohf.ihe.xds.XDSResponseParser] RegistryResponse error
>> 0 code
>> is unrecognized.
>> [INFO ][11:29:19][.ohf.ihe.xds.XDSResponseParser] Error #0
>> Severity=Error
>> Code=UNKNOWNERROR
>> Code Context=Initiating Gateway Error: caught exception trying to
>> call r
>> eceiving gateway 'NIST Public Receiving Gateway'
>> Location=
>> com.healthvision.initiatinggateway.webservice.InitiatingGate wa
>> yService.sendQueryToReceivingGateway(InitiatingGatewayServic e.java:304)
>>
>>
>> - Error #0
>> Severity=Error
>> Code=UNKNOWNERROR
>> Code Context=Initiating Gateway Error: caught exception trying to
>> call r
>> eceiving gateway 'NIST Public Receiving Gateway'
>> Location=
>> com.healthvision.initiatinggateway.webservice.InitiatingGate wa
>> yService.sendQueryToReceivingGateway(InitiatingGatewayServic e.java:304)
>>
>>
>> The second problem is that the bridge says it got 0 documents, when the
>> log showed that it received two. Additionally, the response shows as
>> [0] which I believe is your success status:
>> [DEBUG][11:29:19][se.ohf.bridge.ihe.IheXdsBridge] got 0 documents by
>> QueryDocumentsByPatientId(PatientIdType ( idNumber=[01bfd2ebbd3743d]
>> assigningAuthority=[AssigningAuthority ( namespaceId=[]
>> universalId=[1.3.6.1.4.1.21367.2005.3.7] universalIdType=[ISO]
>> useDefaultAssigningAuthority=[false] universalIdTypeCode=[]
>> )] ))
>> [DEBUG][11:29:19][clipse.ohf.bridge.ws.OHFBridge] returning response:
>> ResponseType ( response=[0] ) QueryDocumentsResponseType (
>> documentTypeArray=[] )
>> [DEBUG][11:29:19][clipse.ohf.bridge.ws.OHFBridge] got 0
>> documents:ResponseType ( response=[0] ) QueryDocumentsResponseType (
>> documentTypeArray=[] )
>>
>> thanks,
>> Jesse
>>
Previous Topic:How to use HL7 communication?
Next Topic:bridge success status not working
Goto Forum:
  


Current Time: Mon Sep 22 06:27:45 GMT 2014

Powered by FUDForum. Page generated in 0.02451 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software