ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Invalid Content-Type HTTP Header. Content-Type was missing

Post new topic  Reply to topic
 Invalid Content-Type HTTP Header. Content-Type was missing « View previous topic :: View next topic » 
Author Message
sankritya
PostPosted: Tue Dec 23, 2014 6:03 am    Post subject: Invalid Content-Type HTTP Header. Content-Type was missing Reply with quote

Centurion

Joined: 14 Feb 2008
Posts: 100

Hi All,

We are working on a requirement of migrating the WICS Services to WMB Platform. 1 of the exposed service is a web service and is accessed by a VB Application. During testing we found that VB Application is always getting SOAP fault when connecting to WMB Web Service. WMB Web Service has been implemented using SOAP Input and Reply node on WMB 7.0.0.6.
We asked the VB Application team to provide the WSDL their app is using to call. But they replied that they are just creating the message and sending it to our service url. They have not set any properties or WSDL in the application. Has any one faced similar issue and if yes what was the resolution. When we tried to run the service in debug mode by connecting all 4 terminals of SOAP Input node to compute node , it shows that request is not reaching WMB service, but Application is getting following error

Quote:
<?xml version="1.0" encoding="utf-8"?><soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"><soapenv:Body><soapenv:Fault><faultcode>soapenv:Server</faultcode><faultstring>Invalid Content-Type HTTP Header. Content-Type was missing, malformed or null.</faultstring><detail><Exception>org.apache.axis2.AxisFault: Invalid Content-Type HTTP Header. Content-Type was missing, malformed or null.
at com.ibm.broker.axis2.SoapUtilities.createSOAPMessage(SoapUtilities.java:1951)
at com.ibm.broker.axis2.SoapUtilities.createSOAPMessage(SoapUtilities.java:1920)
at com.ibm.broker.axis2.Axis2Invoker.processInboundRequest(Axis2Invoker.java:3159)
at com.ibm.broker.axis2.Axis2Invoker.invokeAxis2(Axis2Invoker.java:2865)
at com.ibm.broker.axis2.TomcatNodeRegistrationUtil.invokeAXIS2(TomcatNodeRegistrationUtil.java:474)
</Exception></detail></soapenv:Fault></soapenv:Body></soapenv:Envelope>
Back to top
View user's profile Send private message
Vitor
PostPosted: Tue Dec 23, 2014 6:22 am    Post subject: Re: Invalid Content-Type HTTP Header. Content-Type was missi Reply with quote

Grand High Poobah

Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA

sankritya wrote:
During testing we found that VB Application is always getting SOAP fault when connecting to WMB Web Service. WMB Web Service has been implemented using SOAP Input and Reply node on WMB 7.0.0.6.


VB? Real, honest, obsolete for years VB?

sankritya wrote:
We asked the VB Application team to provide the WSDL their app is using to call. But they replied that they are just creating the message and sending it to our service url.


There's your problem right there. They're making no provision for any of the artifacts that a "proper" web service has, probably because VB lacks the faciltities.

(For the record, calling a SOAP Input node from VB.NET has caused me some interesting problems....)

If the application is not using a web service with a WSDL, you're on a hiding to nothing trying to use a SOAP Input node. Replace it with an HTTP Input node and interpret the input by hand.

Also consider getting these people to move into the 21st Century and use VB.NET. When you move from v7.0.0.6 (which is out of support next September) you can put in a .NET Input node, at which point the communication can use .NET at both the application & flow end points and all the complexity goes away.

(Which is how I fixed my problem)
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
sankritya
PostPosted: Thu Feb 05, 2015 3:44 am    Post subject: Reply with quote

Centurion

Joined: 14 Feb 2008
Posts: 100

Quote:
Replace it with an HTTP Input node

It worked... Thanks Vitor javascript:emoticon('')
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Invalid Content-Type HTTP Header. Content-Type was missing
Jump to:  



You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.