Required upgrade.
Source URL: svn http://anonsvn.jboss.org/repos/jbossweb?tags/JBOSSWEB_7_5_4_FINAL/#2581 Mead-Build: org.jboss.web-jbossweb-7.5.4.Final_redhat_1-1 Brew-Build: jbossweb-7.5.4-1.Final_redhat_1.1.ep6.el6
Source URL: svn http://anonsvn.jboss.org/repos/jbossweb?tags/JBOSSWEB_7_5_5_FINAL/#2585 Mead-Build: org.jboss.web-jbossweb-7.5.5.Final_redhat_1-1 Brew-Build: jbossweb-7.5.5-1.Final_redhat_1.1.ep6.el6
Source URL: svn http://anonsvn.jboss.org/repos/jbossweb?tags/JBOSSWEB_7_5_6_FINAL/#2593 Mead-Build: org.jboss.web-jbossweb-7.5.6.Final_redhat_1-1 Brew-Build: jbossweb-7.5.6-1.Final_redhat_1.1.ep6.el6
Source URL: svn http://anonsvn.jboss.org/repos/jbossweb?tags/JBOSSWEB_7_5_7_FINAL/#2596 Mead-Build: org.jboss.web-jbossweb-7.5.7.Final_redhat_1-1 Brew-Build: jbossweb-7.5.7-1.Final_redhat_1.1.ep6.el6
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHSA-2015-0847.html