Hello:

We have a CFHTTP call that is failing and I cannot figure out why:

<cftry>
<cfhttp url="http://qaapp01:8080/payment-gateway/ws/"; method="post" 
throwonerror="true">
<cfhttpparam type="header" name="content-length" value="#len(soap)#">
<cfhttpparam type="header" name="charset" value="utf-8">
<cfhttpparam type="XML" value="#trim(soap)#">
</cfhttp>

<cfdump var="#cfhttp#" />

<cfcatch type="Any">
<cfset attributes.msg_error="#cfcatch.detail#-#cfcatch.message#">
</cfcatch>
</cftry> 

It doesn't matter what I adjust as far as the URL, protocol or port, I 
always seem to end up with this exception:

throwonerror=true : General Runtime Error; Unrecognized error code: Cannot 
locate: Connection Failed
throwonerror=false : Failed due to invalid Protocol: null

It seems to bubble up into Apache's HTTPClient libs, but I've reached a 
dead end trying to find out why.  Looking at the conversation in wireshark, 
I can seem some chatter back and forth between client and server, but a 
HTTP conversation never seems to take place and I don't see anything hit 
the fat end's access logs.  This is NOT an HTTPS call (although capable). 
 I've tried using HTTPS and HTTP, on standard and non-standard ports and 
nothing seems to get me past this error.

I've also verified that connectivity is good between the two hosts---I can 
get a response from the far end on the requesting host using wget/CURL.

This is OpenBD 3.1 Ready2Run running on Linux (I've tried both Linux Mint 
17.3 and Amazon Linux 2015.09) running under Java 8 64-bit, trying to make 
a SOAP post to a Jetty 9.3.2 / JDK 1.8 64-bit application server running on 
Amazon Linux 2015.09 .

If any of you have ever seen anything like this or have any ideas, input 
would be appreciated!

Thanks,
Bryan

-- 
-- 
online documentation: http://openbd.org/manual/
 http://groups.google.com/group/openbd?hl=en

--- 
You received this message because you are subscribed to the Google Groups "Open 
BlueDragon" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to