Context-Free Validation Error

11 views
Skip to first unread message

Andrew Walsh

unread,
Apr 21, 2023, 4:45:32 PM4/21/23
to HL7v2 Syndromic Testing
We have a local installation of the tool, set up using the installation guide from the documentation section.

We have successfully posted A04 messages to the validation endpoint. /ss-r2/api/hl7v2/testcontext/2/validateMessage
Where is 2 has been confirmed as the appropriate testContextId

We can validate thousands of messages in succession with no issue.

However, we have encountered 2 issues, the first of which is a significant blocker.
Sometimes the API will return a response code of 400 with this message:

Sorry, cannot validate the message provided.
DEBUG:
gov.nist.hit.core.service.exception.MessageValidationException: Validation failed for classes [gov.nist.auth.hit.core.domain.ValidationLog] during persist time for groups [javax.validation.groups.Default, ]
List of constraint violations:[
ConstraintViolationImpl{interpolatedMessage='may not be null', propertyPath=userId, rootBeanClass=class gov.nist.auth.hit.core.domain.ValidationLog, messageTemplate='Unknown macro: {javax.validation.constraints.NotNull.message}'}
]

The stack trace points to this line:
at gov.nist.hit.core.api.TestContextController.validateMessage(TestContextController.java:110)

And further down points to these lines:

at gov.nist.hit.core.hl7v2.service.HL7V2MessageValidator.validate(HL7V2MessageValidator.java:69)
        at gov.nist.hit.core.hl7v2.service.impl.HL7V2MessageValidatorImpl.validate(HL7V2MessageValidatorImpl.java:14)
        at gov.nist.hit.core.api.TestContextController.validateMessage(TestContextController.java:101)

Once it sends that error, it continues to respond with that error, even for messages which have succeeded previously and for the sample message from the web UI. So far, nothing short of reinstalling the webapp has successfully resolved this issue.

Reviewing the code indicates that the generateReport() method is returning null, but we've been unable to trace farther back than that to understand why it is returning null.

The second issue is that periodically the API will return a response code of 400 with an error that traces back to a "java.net.SocketException: Connection reset" in the log. The logged stack trace does not contain any references to NIST code. Restarting the webapp resolves this issue, but if there is a known solution to prevent it, that would be helpful.

Thanks,
Andy Walsh

sheryl...@nist.gov

unread,
Apr 21, 2023, 4:56:52 PM4/21/23
to HL7v2 Syndromic Testing
Hi Andy,

Your inquiry has been received, and a response will be provided after the issue is evaluated by NIST analysts.

Thank you.


Reply all
Reply to author
Forward
0 new messages