You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by Deepa Kamalanathan <fl...@yahoo.co.in> on 2016/09/01 02:31:25 UTC

Re: REST API with .NET WCF - POST error

Hi,

 I'm facing the exact issue. 
Is the issue resolved? what changed to made to BizTalk or activeMQ?






--
View this message in context: http://activemq.2283324.n4.nabble.com/REST-API-with-NET-WCF-POST-error-tp4712511p4716049.html
Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.

Re: REST API with .NET WCF - POST error

Posted by Deepa Kamalanathan <fl...@yahoo.co.in>.
Hi,

We have tried couple options to solve this problem, 
We created a custom behavior to add this a Content type to the header of the
response but the WCF-WebHTTP adapter transmission failure occurs before the
message gets to that point. Next, we tried to configure the AMQ to add a
content type but could not find the correct “config” to edit.

Finally, we decided to choose BizTalk HTTP adapter instead of the
WCF-WebHTTP adapter to POST the message to the AMQ. The HTTP adapter is a
very old adapter and it doesn't  picky about what is in the header of the
response. It was pleasing to find that the HTTP adapter did  POST a message
to the AMQ without a transmission failure.

Here is the detail information.
https://connectedpawns.wordpress.com/2016/12/05/integrating-apache-activemq-with-biztalk-server-publishing-messages/

Regards,
Deepa Kamalanathan




--
View this message in context: http://activemq.2283324.n4.nabble.com/REST-API-with-NET-WCF-POST-error-tp4712511p4719745.html
Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.

Re: REST API with .NET WCF - POST error

Posted by Deepa Kamalanathan <fl...@yahoo.co.in>.
Hi,

The cause of this issue could be due to,

1. When the server receives a request without the content-type header
2. When the client receives a response without the content type header

In my case, the request message was successfully posted to ActiveMQ. I could
see the message in ActiveMQ.

So, the reason could be "When the client receives a response without the
content-type header".
With this, I started to debug through fiddler and got the response message
"Message sent" with HttpStatuscode 200.

The ActiveMQ is returning the response message as "Message sent" with
"Content-Length: 12" the header and there is no "Content-Type" header in the
response message and BizTalk couldn't understand the response message and
thus throws this error.

Now ActiveMQ has to fix the response message with the proper header in them.

Regards,
Deepa



--
View this message in context: http://activemq.2283324.n4.nabble.com/REST-API-with-NET-WCF-POST-error-tp4712511p4716433.html
Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.