If you specify query parameters in an XML page-sequence configuration that contain values that need to be URL encoded (like '=', '%') then the characters will be double-escaped inside the PageSequenceMonitor code before they are sent to the server.This will cause the page sequences to fail because the parameters will be malformed. For example:
<page virtual-host="localhost" path="/opennms/alarm/list.htm" port="8980" response-range="200">
<parameter key="filter" value="severity=1"/>
will cause the following GET to be issued to the server:
In this case, the '=' sign was escaped once to '%3D' (which is what we would expect) but then the '%' in that clause is escaped again resulting in the final string '%253D'.