Policy assertion "{http://schemas.sun.com/2006/03/wss/server}DisableStreamingSecurity" was evaluated as "UNSUPPORTED".

This test s72 in wssecurity/functional SQE workspace is failing some times.Looks like a test issue.This test uses DisableStreamingSecurity assertion.Attaching the policy file for the service.

Tested with the following :

* GlassFish Server Open Source Edition 3.1-b38 (build 38) ,Metro/2.1-b25 (trunk-6664; 2010-12-31T11:31:15+0000) - Pass
* GlassFish Server Open Source Edition 3.1-b39 (build 39) , Metro/2.1-b27 (trunk-6695; 2011-01-25T10:02:57+0000) - Pass
* GlassFish Server Open Source Edition 3.1 (build 40) , Metro/2.1-b27 (trunk-6695; 2011-01-25T10:02:57+0000) - Pass

For all the 3 executions, I am using Metro/2.1-SNAPSHOT (trunk-6685; 2011-01-22T23:49:19+0000).may be if I change the metro build , that is used at client side makes the difference.

Filing the issue so as we can look into this later when we get some time.
#### Environment
Linux,gf3.1 build 39,40
#### Affected Versions
[2.1]

Source: [https://github.com/javaee/metro-wsit/issues/1528](https://github.com/javaee/metro-wsit/issues/1528)
Author: glassfishrobot

Start with functional wssecurity test s72 and the attached service policy file, then reproduce the intermittent DisableStreamingSecurity assertion failure. Compare the client Metro/2.1-SNAPSHOT build with the listed GlassFish and Metro versions. Done means identifying the version or test condition that causes UNSUPPORTED and confirming the test behaves consistently.

Written by the indexing model from the issue text.