java.lang.NumberFormatException: For input string: 'nu' when importing from 5.5 to 5.x Description:When using buildomatic to import from an earlier version of JRS to a newer version, a customer encountered this stacktrace within their buildomatic output: | [toc] |
java.lang.NumberFormatException: For input string: "nu" java.lang.NumberFormatException: For input string: "nu" at java.lang.NumberFormatException.forInputString(NumberFormatException.java:65) at java.lang.Integer.parseInt(Integer.java:492) at com.jaspersoft.jasperserver.api.metadata.common.service.impl.Cipherer.dehexify(Cipherer.java:215) at com.jaspersoft.jasperserver.api.metadata.common.service.impl.Cipherer.decode(Cipherer.java:154) at com.jaspersoft.jasperserver.export.modules.auth.beans.UserBean.copyTo(UserBean.java:128) .....
JasperReport Server v5.5 contained a defect, #35723, characterized by incorrectly encypted data in user password tags of js-exports. This can cause an exception upon import in circumstances where the user can an empty/blank/null password in the JIUSER table.
This empty/blank/null password circumstance is typically associated with externally authenticated users.
Resolution:
Two options exist for resolution:
Manually edit each individual user's .xml file, removing 'null' from the password element, then import. Find/replace tools (ReplaceText for win OS) can be executed against the export's directories of users.
find:
<password>ENC<null></password>
replace with:
<password>ENC<></password>
Example sed commands:
sed -i 's/null//g' *.xml
OR more robust
sed -i 's/ENC\<\;null\>\;/ENC\<\;\>\;/g'; *
Patch your JasperReport Server v5.5 instance with the cumulative hotfix patch & re-run the original export.
Ref. Case #00050467
Recommended Comments
There are no comments to display.