Fixes are available
APAR status
Closed as program error.
Error description
During server restart, applications using Business Rules may fail to startup. There is a very small timing window during the initialization of an application that uses Business Rules artifacts. This window involves a call to the java.text.DateFormat.parse() method. Currently the same format instance is shared between all threads. If multiple threads (different applications starting up) happen to execute the code at the same time, it will result in an error. The chances of this error occuring are very low. This APAR will resolve the issue by using new instances of the format for each thread. An example of the error can be found in FFDC files similar to the following: FFDC Exception:java.lang.NumberFormatException SourceId:com.ibm.wbiservers.customization.runtime.xml.Customizat ionTimes tampContentHandler.endElement ProbeId:122 Reporter:com.ibm.wbiservers.customization.runtime.xml.Customizat ionTimes tampContentHandler@503c503c java.lang.NumberFormatException: For input string: ".2001133E.2001133E44" at sun.misc.FloatingDecimal.readJavaFormatString(FloatingDecimal.ja va:1266) at java.lang.Double.parseDouble(Double.java:510) at java.text.DigitList.getDouble(DigitList.java:151) at java.text.DecimalFormat.parse(DecimalFormat.java:1302) at java.text.SimpleDateFormat.subParse(SimpleDateFormat.java:1611) at java.text.SimpleDateFormat.parse(SimpleDateFormat.java:1332) at java.text.DateFormat.parse(DateFormat.java:335) at com.ibm.wbiservers.customization.runtime.xml.CustomizationTimest ampConte ntHandler.endElement(CustomizationTimestampContentHandler.java:1 37)
Local fix
Restart the server. The chances of this conflict are low, so a subsequent startup is likely to proceed without error.
Problem summary
Workaround: Restart the server. The chances of this conflict are low, so a subsequent startup is likely to proceed without error. Problem Summary: This window involves a call to the java.text.DateFormat.parse() method. Currently the same format instance is shared between all threads. If multiple threads (different applications starting up) happen to execute the code at the same time, it will result in an error. The chances of this error occuring are very low.
Problem conclusion
With this interim fix the Business Rules code is changed, so that an instance of java.text.DateFormat is not shared across multiple threads so that the exception will not be caused any longer. FIX AVAILABILITY: iFix for 7.5.1.1 is available on Fix Central, search for APAR JR46632 at http://www.ibm.com/support/fixcentral/ Fix is also included in BPM 7.5.1.2 Fix is also included in BPM 8.0.1.2 Fix is also included in BPM 8.5.0.1 When obtaining any of the above fixes, be sure to download the accompanying readme, for itself and any prerequisite fixes, and review them thorougly.
Temporary fix
Comments
APAR Information
APAR number
JR46632
Reported component name
BPM ADVANCED
Reported component ID
5725C9400
Reported release
751
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2013-05-09
Closed date
2013-08-12
Last modified date
2013-08-12
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
BPM ADVANCED
Fixed component ID
5725C9400
Applicable component levels
R751 PSY
UP
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSFTN5","label":"IBM Business Process Manager Advanced"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.5.1","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
08 January 2022