PHINMS outgoing problems
Emily Cheng
To all the PHINMS experts if you could help,
We're having problem with PHINMS's sending files (I.e., failed to have response to complete the sending). It seemed we were actually able to send out some files but failed to have response back to update the status for some reason, so as a result it showed failed and impaired all other routes/files. We could receive ELR files from facilities without any problems. Not sure why/what caused failure in having response for the sending. What could cause the response failed? Could it be causing from the response generated at receiver or the response returned at sender for whatever reasons? Any help you could offer is much appreciated.
BTW, I've cleaned up all the files and cleared the PHINMS cache and restarted the PHINMS server. But the sending problem remained.
Event log on the proxy server: several errors regarding Schannel if they're related to the problem? What/how to fix it?
PHINMS Logs below (on PHINMS server)
WorkerThread-1|12/18|11:45:46|POST to phinms.cdc.gov:443 done, reading response|
WorkerThread-1|12/18|11:45:46|Waiting for response...|
WorkerThread-1|12/18|11:45:46|Setting default data read timeout to: 600 seconds|
Thread-40|12/18|11:45:47|Got no content|
WorkerThread-1|12/18|11:55:46|Error: timeout reading response|
WorkerThread-1|12/18|11:55:46|Could not retrieve Envelope from HTTPMultiParser - HTTP Status: false
Message: null|
WorkerThread-1|12/18|11:55:46|Error uploading file|
WorkerThread-1|12/18|11:55:46||
WorkerThread-1|12/18|11:55:46|Preparing message|
WorkerThread-1|12/18|11:55:46|Downloading certificate from URL:file:///C:/certs/CDC_encryption.cer|
WorkerThread-1|12/18|11:55:46|Certificate downloaded from URL: file:///C:/certs/CDC_encryption.cer successfully|
WorkerThread-1|12/18|11:55:46|Warning: Record:payloadFile unspecified|
WorkerThread-1|12/18|11:55:46|Warning: Record:payloadContent unspecified|
WorkerThread-1|12/18|11:55:46|INFO:Byload has been copied|
WorkerThread-1|12/18|11:55:46|Composing message without SyncReply|
WorkerThread-1|12/18|11:55:46|Warning: Record:arguments unspecified|
WorkerThread-1|12/18|11:55:46|Encryption time=0 sec.|
WorkerThread-1|12/18|11:56:16|Trying connection to:phinms.cdc.gov:443|
WorkerThread-1|12/18|11:56:16|Initialized SSL context .... |
WorkerThread-1|12/18|11:56:16|Website up -->phinms.cdc.gov:443|
WorkerThread-1|12/18|11:56:16|Trying to connect to phinms.cdc.gov:443|
WorkerThread-1|12/18|11:56:16|Connection established to phinms.cdc.gov:443|
WorkerThread-1|12/18|11:56:16|Making SOAP request to phinms.cdc.gov to send record:258138|
WorkerThread-1|12/18|11:56:16|POST to phinms.cdc.gov:443 done, reading response|
WorkerThread-1|12/18|11:56:16|Waiting for response...|
WorkerThread-1|12/18|11:56:16|Setting default data read timeout to: 900 seconds|
Thread-41|12/18|11:56:18|Got no content|
Thanks,
Emily Cheng
Loyall, David
Emily,
Ok, I've heard that you're already engaged with CDC PHINMS support on this but the ticket remains open. So, I'll throw in my two cents.
Let's temporarily enable heavy debugging logs for SSL connections.
You'll want to add this:
-Djavax.net.debug=ssl
...to your command line options for Java that the PHINMS Tomcat service uses.
You'll do that by looking at the PHINMS Tomcat service properties to find the "service name"...
...And then going to c:\program files\phinms2.9.00\appserver\bin (or thereabouts) to find tomcat7w.exe... and then going to the command prompt and typing something like tomcat7w.exe //ES/<service name>...
Which should pull up something like this:
Which will allow you to add -Djavax.net.debug=ssl.
Then you'll restart PHINMS and you'll find a bunch of SSL debugging in the logs! That will tell us what is going wrong with the connection to PHINM.cdc.gov. OR, it's not an SSL problem.
Cheers and best wishes for the holidays,
--Dave from Nebraska
--
---
You received this message because you are subscribed to the Google Groups "PHINMS User Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
phinms+un...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Emily Cheng
Emily,
Ok, I've heard that you're already engaged with CDC PHINMS support on this but the ticket remains open. So, I'll throw in my two cents.
Let's temporarily enable heavy debugging logs for SSL connections.
You'll want to add this:
-Djavax.net.debug=ssl
...to your command line options for Java that the PHINMS Tomcat service uses.
You'll do that by looking at the PHINMS Tomcat service properties to find the "service name"...
<image001.png>
...And then going to c:\program files\phinms2.9.00\appserver\bin (or thereabouts) to find tomcat7w.exe... and then going to the command prompt and typing something like tomcat7w.exe //ES/<service name>...
Which should pull up something like this:
<image002.png>