A java.lang.NumberFormatException is Generated in OAAM Log File When a Decimal Value is Used in a Numeric Data Type field in an Entity (Doc ID 1399440.1)

Last updated on SEPTEMBER 21, 2016

Applies to:

Oracle Adaptive Access Manager - Version 10.1.4.5 to 10.1.4.5 [Release 10g]
Information in this document applies to any platform.

Symptoms

A java.lang.NumberFormatException is generated in OAAM log file when a decimal value is used in a Numeric Data Type field in an entity.

STEPS REQUIRED TO REPRODUCE THE ISSUE
=====================================

  1. Create an entity of Numeric Data Type. The client's application declares the value java.math.BigDecimal.
  2. Create a transaction using the entity defined above.
  3. Fire a transaction through sample application with decimal value for the numeric data field of entity.
  4. Note the java.lang.NumberFormatException in the log file.


ACTUAL RESULTS RECEIVED FROM ABOVE STEPS
========================================
The following stack trace snippet appears in the log file:

2011-11-19 11:36:06,770 WARN [app=oaam_oarm] [[ACTIVE] ExecuteThread: '2'
for queue: 'weblogic.kernel.Default (self-tuning)']
com.bharosa.vcrypt.tracker.transaction.data.ValueData - Exception while
parsing long value from String [20.00]. Setting value as 0
java.lang.NumberFormatException: For input string: "20.00"
at
java.lang.NumberFormatException.forInputString(NumberFormatException.java:48)

at java.lang.Long.parseLong(Long.java:419)
at java.lang.Long.parseLong(Long.java:468)


Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms