000030002 - IMG: java.lang.IllegalArgumentException: Value is not a boolean: no_markup

Document created by RSA Customer Support Employee on Jun 14, 2016Last modified by RSA Customer Support Employee on Apr 21, 2017
Version 2Show Document
  • View in full screen mode

Article Content

Article Number000030002
Applies ToRSA IMG 6.8.1
RSA IMG 6.8.1 all patch levels
IssueNavigating around IMG results in "Request could not be handled" errors in almost every screen and this error is in the AveksaServer.log:
java.lang.IllegalArgumentException: Value is not a boolean: `no_markup`.
CauseThe patch level of the IMG software is different from the patch level of the database. In this case, the IMG software is at version 6.8.1 GA, and the database has a patch.
6.8.1 GA expects boolean values (TRUE or FALSE) for the XSS/Scripting Security values for HTML/javascript. Starting with 6.8.1 patches, these values are no longer boolean values only. They contain more specific values such as 'NO_MARKUP."
To check whether your values are boolean or not:
Login to the IMG server as user 'oracle'
$ sqlplus avuser/secret@avdb
SQL> select * from t_system_settings where parameter like '%Html%';
Note the values for the different HTML parameters.
This is a rare occurrence because your database gets its patch level from installing the patch which you would do on the IMG system. However, if you had a 6.8.1 PXX system pointing to a remote database and you needed to replace the IMG system for whatever reason while keeping the remote database, that system would need both 6.8.1 installed and the patch to bring it to the same patch level as the database. If the patch is not applied, this error can happen.
Resolution1. Determine the patch level of your database 
Login to the IMG server as user 'oracle'

$ sqlplus avuser/secret@avdb
SQL> 
select parameter, value from t_system_settings where parameter like '%HotFixes%';
2. Determine the patch level of your IMG software:
Login to the IMG server as user 'oracle'
cd /home/oracle/Aveksa_jboss-4.2.2.GA/server/default/deploy/aveksa.ear/aveksa.war/WEB-INF/classes/patch-version.properties
3. Apply the same patch to IMG to bring your IMG software to the same patch level as your database.

NOTE: There is an engineering enhancement request to build in a patch-level check upon startup. If there is a patch-level mismatch, the startup should fail with a message informing you of the patch level discrepancy.

Attachments

    Outcomes