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 » WMB: The given SOAPAction x does not match an operation

Post new topic  Reply to topic Goto page Previous  1, 2
 WMB: The given SOAPAction x does not match an operation « View previous topic :: View next topic » 
Author Message
Mhalaise
PostPosted: Mon Mar 07, 2016 7:07 am    Post subject: Reply with quote

Newbie

Joined: 02 Mar 2016
Posts: 9

I'm really clutching at straws now but: the SOAPAction in the wsdl file(s) is blank (""). However, by invoking a dummy webservice that simply dumps the content of the ${Root} and ${LocalEnvironment} I can see SOAPAction has been populated (with the very value that is then "rejected" with the error message I am seeing). Why is that being set when the wsdl sets that to blank? Is this some sort of default behaviour with our antique WMB?

I tried, just out of interest, really, setting HTTPRequestHeader.SOAPAction to "" but that opened up a whole new can of worms which I yet to make sense of (basically, the XML document prologue wasn't liked)...


Last edited by Mhalaise on Mon Mar 07, 2016 7:14 am; edited 1 time in total
Back to top
View user's profile Send private message
fjb_saper
PostPosted: Mon Mar 07, 2016 7:10 am    Post subject: Reply with quote

Grand High Poobah

Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY

Mhalaise wrote:
I'm really clutching at straws now but: the SOAPAction in the wsdl file(s) is blank (""). However, by invoking a dummy webservice that simply dumps the content of the ${Root} and ${LocalEnvironment} I can see SOAPAction has been populated (with the very value that is then "rejected" with the error message I am seeing. Why is that being set when the wsdl sets that to blank? Is this some sort of default behaviour with our antique WMB?

I tried, just out of interest, really, setting HTTPRequestHeader.SOAPAction to "" but that opened up a whole new can of worms which I yet to make sense of (basically, the XML document prologue wasn't liked)...

Have you tried setting the SOAP Action in the local environment override field?
_________________
MQ & Broker admin
Back to top
View user's profile Send private message Send e-mail
Mhalaise
PostPosted: Mon Mar 07, 2016 7:23 am    Post subject: Reply with quote

Newbie

Joined: 02 Mar 2016
Posts: 9

fjb_saper wrote:
Mhalaise wrote:
I'm really clutching at straws now but: the SOAPAction in the wsdl file(s) is blank (""). However, by invoking a dummy webservice that simply dumps the content of the ${Root} and ${LocalEnvironment} I can see SOAPAction has been populated (with the very value that is then "rejected" with the error message I am seeing. Why is that being set when the wsdl sets that to blank? Is this some sort of default behaviour with our antique WMB?

I tried, just out of interest, really, setting HTTPRequestHeader.SOAPAction to "" but that opened up a whole new can of worms which I yet to make sense of (basically, the XML document prologue wasn't liked)...

Have you tried setting the SOAP Action in the local environment override field?


That is actually what I wanted (or, rather, hoped) to do but all references I can find for WMB 6.1 LocalEnvironment do not mention SOAPAction. The only reference I could find was in the HTTPRequestHeader. Kind of clutching at straws with a blindfold on. It could be the searches I'm doing but a bit flummoxed at the moment...
Back to top
View user's profile Send private message
mqjeff
PostPosted: Mon Mar 07, 2016 7:40 am    Post subject: Reply with quote

Grand Master

Joined: 25 Jun 2008
Posts: 17447

Mhalaise wrote:
WMB 6.1


Well. There's your problem.

Insist on migrating to a supported version, or find another job.
_________________
chmod -R ugo-wx /
Back to top
View user's profile Send private message
Mhalaise
PostPosted: Mon Mar 07, 2016 7:59 am    Post subject: Reply with quote

Newbie

Joined: 02 Mar 2016
Posts: 9

Yep, I think I agree, mqjeff. This is a battle I cannot win. Too many odds stacked against me. Your "find another job" made me laugh

Ok, all, I'm going to drop this now, thanks so much for all your guidance, etc. but I think it's time to give up on WMB (6.1). Sadly, there's only a snowball in hell's chance of getting a supported version now (long story short, the company hosting WMB are being dropped, as is our long faithful mainframe, in favour of a Windows/Linux *hiss* hosted off-the-shelf *yuk* product). So, yep, maybe it really is time for a "look elsewhere" for interesting work
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Goto page Previous  1, 2 Page 2 of 2

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » WMB: The given SOAPAction x does not match an operation
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.