Hl7 posting error

Community
1

I send an hl7 message over /OpenELIS-Global/OrderRequest but getting following error
MSH|^!&|MedWeb|MedWeb_RIS|Mirth|Mirth_Facility|20231123121922.777+0300||ACK^O01^ACK|1331|D|2.5.1
MSA|AE|2018042015005600001
ERR|||207^Application internal error^HL70357^^^^^^Bean named ‘DBOrderPersister’ is expected to be of type ‘org.openelisglobal.dataexchange.order.action.DBOrderPersister’ but was actually of type ‘com.sun.proxy.$Proxy519’|E

HL7 message
MSH|^!&|Mirth|Mirth_Facility|MedWeb|MedWeb_RIS|20231123100000||ORM^O01|2018042015005600001|D|2.5.1
PID|||100001||Smith^John^M||19901001|M|||Street1|||||^CivilStatus|^Religion||||||NY
ORC|NW|20231122110114|
OBR|1|||94500-6^COVIDPCR(Respiratory Swab)||20231122110114

2

which version of OpenELIS are you running ??

3

I am also getting the same error.
I am running 2.7.3.4.

Here is the request I am executing:
(ORM message is generated from OpenEMR 7.0.1)

POST https://localhost:8443/OpenELIS-Global/OrderRequest HTTP/1.1

Content-Type: application/hl7-v2; charset=utf-8
Authorization: Basic YWRtaW46YWRtaW5BRE1JTiE=

MSH|^~&|AppOne|FacilityOne|AppTwo|FacilityTwo|20231201092356||ORM^O01|OpenEMR_Facility-0004|D|2.3
PID|1|1|1||Peter^Parker||20010810|M|||^^^^|||||||2|234-56-7890|||
NTE|1|L|medications NONE
PV1|1||||||^Norman^Osborn||||||||||||2|||||||||||||
IN1|1||||||||||||||||||||||||||||||||||||||||||||||P
GT1|1||Peter^Parker||^^^^|||20010810|M||self|234-56-7890
ORC|NW|OpenEMR_Facility-0004|||||||20231201092356|||^Norman^Osborn||||||||2
OBR|1|OpenEMR_Facility-0004||4548-4^Hemoglobin A1C|R||20231202145000|||||||||^Norman^Osborn||P|||||||||0
DG1|1||U07.1^^I10|

Error Response:
MSH|^~&|AppTwo|FacilityTwo|AppOne|FacilityOne|20231201220638.537+0300||ACK^O01^ACK|1|D|2.3
MSA|AE|OpenEMR_Facility-0004
ERR|||207^Application internal error^HL70357^^^^^^Bean named ‘DBOrderPersister’ is expected to be of type ‘org.openelisglobal.dataexchange.order.action.DBOrderPersister’ but was actually of type ‘com.sun.proxy.$Proxy527’|E

4

I am using 2.7.3.4 version

5

here is the attempted fix .
Can you try running with the latest version and test out??

6

Thank you @Moses_Mutesasira
Will test this.