Submit and vote on feature ideas.

Welcome to the new Parasoft forums! We hope you will enjoy the site and try out some of the new features, like sharing an idea you may have for one of our products or following a category.

SOAP Message size it greater than allowed limit

Options
LegacyForum
LegacyForum Posts: 1,664 ✭✭
edited December 2016 in SOAtest
Where is this error coming from?
I'm trying to help a colleague run SOATest on a WCF web service operation, and for "big" responses, we are seeing this error in the SOATest client:

SOAP Message size it greater than allowed limit [SECURITY.MSGSIZE v 1.0]

This is perplexing, as the tool is actually able to get a response from the server that contains no SOAP faults. Furthermore, the response isn't very big at all - 22kb to be exact. I can't seem to Google this error message, and the the grammar/spelling mistake in it isn't working for my benefit either.

Is this a SOATest setting? Maybe a WCF setting? Or a WS-Security setting? It certainly isn't a restriction we are imposing at the server level.

Here's a screenshot for posterity.

Thanks in advance for any insight or ideas.
Tagged:

Comments

  • LegacyForum
    LegacyForum Posts: 1,664 ✭✭
    edited December 2016
    Options
    It seems that you are running a SOAP Policy enforcer on your test, and that message is coming from the policy enforcer. If you open up the configuration for those rules, you'll see that one of them is rule\SOAP\INTEROP.MGSIZE.rule. Right click > view help file will show for this rule: "This rule reports SOAP messages larger than 10240 bytes as violations to the message size restriction policy. Modify the rule with the value that fits your criteria."

    Uncheck the box next to this rule, or adjust the maximum file size, to correct this error message. As a general practice, you should review the rules you are enforcing and checking if they are applicable or if they make sense for your particular test case. Best regards,

    Orson

  • LegacyForum
    LegacyForum Posts: 1,664 ✭✭
    Options
    Thanks Orson, that is indeed the source of the error message!

Tagged