XDR Test 11 Never Finishes

[Michael Mall]

When we run XDR Test 11 from our test server, the process is able to complete and the logs show the request and response.  But, when we do so from our live server, the logs never get generated and the button never moves beyond "Refresh Pending" no matter how many times I click it.  Is there something in the logs on your end that can provide some clues?

The last test to dir...@isharemedicalrecords.com was done at about 10:05 PM CT (11:05 PM ET).

Thanks

[Sandeep]

I don't see any log records for the direct address you posted for 7/10. Can you run again today? Make sure all the ports are accessible on the live server and no firewall is blocking external communication.

[Michael Mall]

Our firewall has a rule allowing inbound access to the ports for SMTP, IMAP, and POP3 from ttpedge.sitenv.org (52.26.237.9).  Do we need something else?

[Sandeep]

XDR does not require SMTP/IMAP/POP. As this test works fine on your test server map the same configuration to your live server and try again.

[Michael Mall]

For what it's worth, I ran the test again at 10:16 AM CT today (11:15 AM ET).  The Tomcat log entries show it "SENDING TO ENDPOINT http://ttpedge.sitenv.org:11080/xdstools/sim/edge-ttp__11/rep/xdrpr" and no errors are logged there.

In the Direct To Address field, I have entered dir...@isharemedicalrecords.com.

I haven't yet changed our firewall config.  Do I need to add some ports for access from ttpedge.sitenv.org?

[Sandeep]

2019-07-11 15:16:37 INFO  ListenerProcessor:? - Processing message from dir...@isharemedicalrecords.com

2019-07-11 15:16:37 INFO  ListenerProcessor:? - To testc...@ttpedge.sitenv.org

2019-07-11 15:16:37 INFO  ListenerProcessor:? - Mime Message parsing successful

2019-07-11 15:16:37 ERROR ListenerProcessor:? - Throw away message from dir...@isharemedicalrecords.com not a registered Direct (From) email account name

[Fatal Error] :19:3: An invalid XML character (Unicode: 0x3) was found in the element content of the document.

org.xml.sax.SAXParseException; lineNumber: 19; columnNumber: 3; An invalid XML character (Unicode: 0x3) was found in the element content of the document.

at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)

at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)

at groovy.util.XmlSlurper.parse(XmlSlurper.java:207)

There seems to be an invalid character in your XML. Is there a difference in XML between your test and live versions? 

[Michael Mall]

I notice your log includes "2019-07-11 15:16:37 ERROR ListenerProcessor:? - Throw away message from dir...@isharemedicalrecords.com not a registered Direct (From) email account name".

Earlier, we did run the test before adding dir...@isharemedicalrecords.com to our registered list of Direct Addresses.  I thought we had added it before running the last test; but, for good measure, I ran the test again at 3:36 PM CT (4:36 PM ET).  It still behaved the same way with "Pending Refresh" never going away.  Can you check to see if this error is still included in the logs?

Thanks.

[Sandeep]

2019-07-11 20:36:16 INFO  ListenerProcessor:? - Processing message from dir...@isharemedicalrecords.com

2019-07-11 20:36:16 INFO  ListenerProcessor:? - To testc...@ttpedge.sitenv.org

2019-07-11 20:36:16 INFO  ListenerProcessor:? - Mime Message parsing successful

2019-07-11 20:36:16 ERROR ListenerProcessor:? - No contact address listed for Direct (From) address dir...@isharemedicalrecords.com

2019-07-11 20:36:16 INFO  ListenerProcessor:? - Getting signing certificates /sites/ttp/certificates/good/ttpedge.sitenv.org.p12

2019-07-11 20:36:16 INFO  ListenerProcessor:? - Message Validation Begins

2019-07-11 20:36:16 INFO  ListenerProcessor:? - Logging message validation in database: <358812453.909.1562877374622.JavaMail.root@43309-SR22745>

[Fatal Error] :19:3: An invalid XML character (Unicode: 0x3) was found in the element content of the document.

org.xml.sax.SAXParseException; lineNumber: 19; columnNumber: 3; An invalid XML character (Unicode: 0x3) was found in the element content of the document.

at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)

at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)

at groovy.util.XmlSlurper.parse(XmlSlurper.java:207)

at groovy.util.XmlSlurper.parse(XmlSlurper.java:260)