if you are getting the above error after upgrading from one version of JBoss to another, and you are using Spring, check how you are setting your soapAction in your WebServiceTemplate.
After upgrading to WildFly, I found I was getting the above error accessing a SOAP web service that had not really changed. After much investigation and nashing of teeth, the issue was that the SOAPAction didnt match what was defined in the WSDL. Seems like previous versions of JBoss were not so strict on this, but that WildFly is.
Passing the required SOAPAction on the WebServiceTemplate when processing the request resolved this issue. Hope this helps someone out in the future!