edge-ttp XDR simulators (H2 Tests 10/11/12/16) never notify ETT - cards stuck Pending since the Jul 22 rebuild (likely missing JAXB provider in xdstools)

7 views
Skip to first unread message

REDA ELAMRI

unread,
Sep 30, 2026, 6:56:25 PMSep 30
to Edge Test Tool (ETT)
Hi Sai / ETT team,

The XDR send cards (Test By Criteria > H2 > (i)(C) Send using Edge Protocol - XDR, Tests 10/11/12/16) never leave Pending: LOGS show only "ran tc 10", no captured request, no validation report. We have reproduced the mechanism, so this should be a quick fix on the toolkit host.

What happens (verified Sept 30):

1. ETT sends the Direct message, our HISP converts it and POSTs the ITI-41 to the simulator. We tried both endpoints the card gives out - the ett.healthit.gov:11084 TLS endpoint at 22:29:17Z and the 34.235.25.130:11080 endpoint at 22:34:46Z - from 66.6.125.16, Direct To Address xdr-s...@direct.isharemedicalrecords.com. The simulator returns HTTP 200 / RegistryResponse Success.
2. The sims are configured correctly (toolkit REST, /xdstools/rest/simulators/edge-ttp__10): Transaction_Notification_URI = ett.healthit.gov:8888/ett/api/xdrNotification, Transaction_Notification_Class = gov.nist.healthcare.ttt.xdr.api.XDRServlet, Creation Time Jul 22 2026. ETT's TkListener route api/xdrNotification/{id} is live (a GET to it returns 400, not 404).
3. So the missing piece is the toolkit's notification POST to <URI>/toolkitcallback. On a local copy of the same toolkit (xdstools 7.10.0 on Java 8) that POST fails silently every time with:

   INFO: Callback to http://.../toolkitcallback
   SEVERE: MessageBodyWriter not found for media type=application/xml, type=class gov.nist.toolkit.transactionNotificationService.TransactionLogBean
   groovy.lang.MissingMethodException: No signature of method: java.util.logging.Logger.error() ... [Error on notify for simulator edge-ttp__10 ...]

   i.e. the Jersey client has no JAXB provider to serialise TransactionLogBean, and the toolkit's own error handler then throws, so nothing is logged at the card level. Adding jaxb-api-2.3.1.jar, jaxb-runtime-2.3.3.jar and jersey-media-jaxb-2.33.jar to xdstools/WEB-INF/lib fixed it locally: the card then advances and the report is emailed.

Could you check the toolkit's catalina.out on the edge-ttp host for that SEVERE line around 22:29Z / 22:34Z on Sept 30, and add the JAXB jars (or run the toolkit on a JDK that still ships JAXB)? Once it is back we will re-run Tests 10/11/12/16 immediately and confirm.

Background and earlier attempts are in my Sept 26 thread "XDR 'Send using Edge Protocol - XDR' (h)(2) Test 10 - SUT's XDR reaches ETT but card stays Pending". We are working against an Oct 21 package freeze, so this is our last open ETT item.

Thank you,
Reda Elamri
iShare Medical
Reply all
Reply to author
Forward
0 new messages