I had a similar problem while client calling. In my scenario there were many methods which reuses complex types and I used "" as soap action. On the client side axis throws exception of EPR and WSA conflict. So, I simply changed every operations action :) to unique name. Now its working fine.
I dont know what are the consequences of not specifying soap action header. Kensky -- View this message in context: http://www.nabble.com/Can-you-default-the-SOAPAction-as-being-%22%22--t1475972.html#a4007793 Sent from the Axis - User forum at Nabble.com.
