The [action] cannot be processed at the receiver

If you are writing a web service and come across the following message in a SOAP Fault or a stack trace then don’t go digging around trying to find the code that caused the fault, take heed of the following information:

“The [action] cannot be processed at the receiver” is the [reason] string for a WS-Addressing specification defined fault which a compliant WS-Addressing implementation may throw if the value of the wsa:Action header is not recognised. The most likely problem is therefore that the web services client put the ‘wrong’ value in the wsa:Action header.

Suggested course of action: Check the documentation of your web services server to determine what action value it is expecting for a given operation and set that explicitly in your web service client.


1 Response to “The [action] cannot be processed at the receiver”



  1. 1 A Thing or Two About Apache Rampart – Part II « Source Open Trackback on March 5, 2010 at 9:39 am

Leave a Reply




About

I’m David Illsley, I work in Web Services development at IBM Hursley, which involves work on the Apache WS Project, where I am a committer and PMC member. When not working with technology, I spend a lot of time on the backstage aspects of theatre, and a sadly decreasing amount of time reading.

Archives

c

Disclaimer

The postings on this site solely reflect the personal views of the author and do not necessarily represent the views, positions, strategies or opinions of IBM or IBM management.

Twitter Updates

  • @katshann methinks someone's playing referrer games... (not me)... I'm barely in the top 30 search terms for my blog in the last 30 days 2 hours ago
  • @goodgravy Good luck! Sounds hopeful... 14 hours ago
  • Struggling to 'Open Link in New Tab' in recent Firefox nightlies. Muscle memory is just too strong 3 days ago
  • Dice games... what's the worst that can happen... #fb 5 days ago
  • Apparently one of my colleagues is 'prepared for DELETION'. That's a little more Logan's Run than I think he's expecting. 6 days ago