000036539 - Emails from workflow approval/fulfillment nodes are not generated and sent due to error "Illegal hex characters in escape (%) pattern" in RSA Identity Governance & Lifecycle 7.0.2 P05

Document created by RSA Customer Support Employee on Jul 20, 2018
Version 1Show Document
  • View in full screen mode

Article Content

Article Number000036539
Applies ToRSA Product Set: RSA Identity Governance and Lifecycle
RSA Version/Condition: 7.0.2 P05
 
IssueAfter upgrading to RSA Identity Governance and Lifecycle 7.0.2 P05, emails from the approval and fulfillment nodes do not get generated and sent for a few of the workflows due to the following error:

URLDecoder: Illegal hex characters in escape (%) pattern - For input string: "; " 


You will find the error below in the aveksaServer.log:

ERROR (Worker_actionq#Script Queue - Normal#WPDS_279) [com.aveksa.server.workflow.scripts.nodes.SendEmailThread] Couldn't Send Email to due to: 
java.lang.IllegalArgumentException: URLDecoder: Illegal hex characters in escape (%) pattern - For input string: "; "
at java.net.URLDecoder.decode(URLDecoder.java:192)
at com.aveksa.server.workflow.scripts.nodes.SendEmailThread.getBody(SendEmailThread.java:109)
at com.aveksa.server.workflow.scripts.nodes.SendEmailThread.sendEmail(SendEmailThread.java:146)
at com.aveksa.server.workflow.scripts.nodes.SendEmailThread.sendEmail(SendEmailThread.java:66)
at com.aveksa.server.workflow.scripts.nodes.SendEmailThread.run(SendEmailThread.java:62)


This error is similar to the error seen when the email node contains a percent (%) character as described in article 000036165 - After patching to RSA Identity Governance & Lifecycle 7.0.2 P03+, emails are not generated and sent due to the error 'Illegal hex characters in escape (%) pattern', but the cause is not similar. 

Here, the issue is seen even if the email body does not contain any % characters.
CauseThe emails are not sent because the body content is not being encoded and saved; hence, when plain text (without any encoding) is sent in an email, it gets decoded and the exception is thrown. 

Another cause for the email not being sent is due to a NullPointerException when either Workflow Variable or Object Attribute is added in the Send Email node.
ResolutionResolved in RSA Identity Governance & Lifecycle 7.0.2 P08.
WorkaroundThe workaround is to either:
  1. Save the workflow node which is not generating emails again, or
  2. Recreate the node after deleting the node which is having issue.

Attachments

    Outcomes