Fixes are available
APAR status
Closed as program error.
Error description
When trying to cancel a task that was created recently this can lead to an NumberFormatException when the task creation is not yet complete: wle_ucaexcept E CWLLG0181E: An exception occurred during execution of task 7,855,824. Error: Not a valid char constructor input: in_creation com.lombardisoftware.core.TeamWorksException: Not a valid char constructor input: in_creation at com.lombardisoftware.core.TeamWorksException.asTeamWorksExceptio n(TeamWorksException.java:136) at com.lombardisoftware.bpd.runtime.engine.quartz.AbstractBpdTask.e xecute(AbstractBpdTask.java:130) at com.lombardisoftware.bpd.runtime.engine.quartz.AbstractBpdTask.e xecute(AbstractBpdTask.java:59) at com.lombardisoftware.server.scheduler.Engine.execute(Engine.java :787) at com.lombardisoftware.server.scheduler.Engine.access$300(Engine.j ava:78) at com.lombardisoftware.server.scheduler.Engine$1.run(Engine.java:5 00) at com.lombardisoftware.client.delegate.common.WebsphereDelegateHel per$2$1.run(WebsphereDelegateHelper.java:78) at java.security.AccessController.doPrivileged(AccessController.jav a:314) at javax.security.auth.Subject.doAs(Subject.java:573) at com.ibm.websphere.security.auth.WSSubject.doAs(WSSubject.java:19 5) at com.ibm.websphere.security.auth.WSSubject.doAs(WSSubject.java:15 2) at com.lombardisoftware.client.delegate.common.WebsphereDelegateHel per.doAs(WebsphereDelegateHelper.java:150) at com.lombardisoftware.client.delegate.common.WebsphereDelegateHel per$2.run(WebsphereDelegateHelper.java:74) at com.lombardisoftware.server.scheduler.Utils$EJBThreadRootRunnabl e.executeRunnable(Utils.java:113) at com.lombardisoftware.server.scheduler.ThreadPool$Worker.run(Thre adPool.java:194) at java.lang.Thread.run(Thread.java:772) Caused by: java.lang.NumberFormatException: Not a valid char constructor input: in_creation
Local fix
n/a
Problem summary
Problem Description: When during the creation of a task an exception occurs the system tries to cancel the task, which leads to an NumberFormatException like this: Caused by: java.lang.NumberFormatException: Not a valid char constructor input: in_creation at java.math.BigDecimal.bad(BigDecimal.java:1859) at java.math.BigDecimal.charParser(BigDecimal.java:1190) at java.math.BigDecimal.<init>(BigDecimal.java:922) at java.math.BigDecimal.<init>(BigDecimal.java:901) at com.lombardisoftware.bpd.component.flowcomponent.activity.worker .BPDActivityWorker.cancelWork(BPDActivityWorker.java:1941) at com.lombardisoftware.bpd.runtime.engine.FlowObjectExecutionTreeN ode.doCancelJobWithoutChildren(FlowObjectExecutionTreeNode.java: 1196) at com.lombardisoftware.bpd.runtime.engine.BPDExecutionTreeNode.can celJob(BPDExecutionTreeNode.java:403) at com.lombardisoftware.bpd.runtime.engine.BPDExecutionTreeNode.can celChildren(BPDExecutionTreeNode.java:427) at com.lombardisoftware.bpd.runtime.engine.BPDExecutionTreeNode.can celJob(BPDExecutionTreeNode.java:401) at com.lombardisoftware.bpd.runtime.engine.BPDExecutionTreeNode.can celChildren(BPDExecutionTreeNode.java:427) at com.lombardisoftware.bpd.runtime.engine.BPDExecutionTreeNode.can celJob(BPDExecutionTreeNode.java:401) at com.lombardisoftware.bpd.runtime.engine.BPDExecutionTreeNode.can celChildren(BPDExecutionTreeNode.java:427) at com.lombardisoftware.bpd.runtime.engine.BPDExecutionTreeNode.can celJob(BPDExecutionTreeNode.java:401) at com.lombardisoftware.bpd.runtime.engine.BPDExecutionTreeNode.can celChildren(BPDExecutionTreeNode.java:427) at com.lombardisoftware.bpd.runtime.engine.BPDExecutionTreeNode.can celJob(BPDExecutionTreeNode.java:401) at com.lombardisoftware.bpd.runtime.engine.workresult.AttachedEvent CompletedWorkResult.execute(AttachedEventCompletedWorkResult.jav a:64) at com.lombardisoftware.bpd.runtime.engine.util.BPDEngineUtils.exec uteException(BPDEngineUtils.java:674) at com.lombardisoftware.bpd.runtime.engine.util.BPDEngineUtils.tryT oDeliverExceptionToEvent(BPDEngineUtils.java:353) at com.lombardisoftware.bpd.runtime.engine.BPDEngine.canFindExcepti onEvent(BPDEngine.java:477) at com.lombardisoftware.bpd.runtime.engine.BPDEngine.canFindExcepti onEvent(BPDEngine.java:488) at com.lombardisoftware.bpd.runtime.engine.BPDEngine.canFindExcepti onEvent(BPDEngine.java:488) at com.lombardisoftware.bpd.runtime.engine.BPDEngine.canFindExcepti onEvent(BPDEngine.java:488) at com.lombardisoftware.bpd.runtime.engine.BPDEngine.executeTreeNod e(BPDEngine.java:336) at com.lombardisoftware.bpd.runtime.engine.BPDEngine.resume(BPDEngi ne.java:150) at com.lombardisoftware.bpd.runtime.engine.BPDEngine.processNotific ation(BPDEngine.java:569) at com.lombardisoftware.bpd.runtime.engine.BPDEngine.processNotific ation(BPDEngine.java:542) at com.lombardisoftware.bpd.runtime.engine.notification.BPDFlowObje ctNotification.applyToEngine(BPDFlowObjectNotification.java:15) at com.lombardisoftware.bpd.component.flowcomponent.activity.worker .notification.TaskActivityCompletedNotification.applyToEngine(Ta skActivityCompletedNotification.java:305) at com.lombardisoftware.bpd.runtime.engine.quartz.AbstractNotificat ionBpdTask.doWithLock(AbstractNotificationBpdTask.java:54) at com.lombardisoftware.bpd.runtime.engine.quartz.DbNotificationBpd Task.doWithLock(DbNotificationBpdTask.java:49) at com.lombardisoftware.bpd.runtime.engine.quartz.AbstractBpdTask$1 .doExecuteDuringLock(AbstractBpdTask.java:92) at com.lombardisoftware.bpd.runtime.engine.quartz.AbstractBpdTask$1 .doExecuteDuringLock(AbstractBpdTask.java:82) at com.lombardisoftware.bpd.runtime.engine.util.LockBPDInstanceComm and$1.doInTransaction(LockBPDInstanceCommand.java:62) at com.lombardisoftware.server.core.TXCommand$2.call(TXCommand.java :88) at com.lombardisoftware.utility.spring.ProgrammaticTransactionSuppo rt.executeInExistingTransaction(ProgrammaticTransactionSupport.j ava:566) at com.lombardisoftware.utility.spring.ProgrammaticTransactionSuppo rt.execute(ProgrammaticTransactionSupport.java:293) at com.lombardisoftware.server.core.TXCommand.executeInDeadlockRetr yLoop(TXCommand.java:86) at com.lombardisoftware.bpd.runtime.engine.util.LockBPDInstanceComm and.execute(LockBPDInstanceCommand.java:74) at com.lombardisoftware.bpd.runtime.engine.quartz.AbstractBpdTask$2 .doInTransaction(AbstractBpdTask.java:105) at com.lombardisoftware.bpd.runtime.engine.quartz.AbstractBpdTask$2 .doInTransaction(AbstractBpdTask.java:101) at com.lombardisoftware.server.core.TXCommand$2.call(TXCommand.java :88) at com.lombardisoftware.utility.spring.ProgrammaticTransactionSuppo rt$1.doInTransaction(ProgrammaticTransactionSupport.java:400) at org.springframework.transaction.jta.WebSphereUowTransactionManag er$UOWActionAdapter.run(WebSphereUowTransactionManager.java:306) at com.ibm.ws.uow.EmbeddableUOWManagerImpl.runUnderNewUOW(Embeddabl eUOWManagerImpl.java:786) at com.ibm.ws.uow.EmbeddableUOWManagerImpl.runUnderUOW(EmbeddableUO WManagerImpl.java:365) at org.springframework.transaction.jta.WebSphereUowTransactionManag er.execute(WebSphereUowTransactionManager.java:252) at com.lombardisoftware.utility.spring.ProgrammaticTransactionSuppo rt.executeInNewTransaction(ProgrammaticTransactionSupport.java:3 95) at com.lombardisoftware.utility.spring.ProgrammaticTransactionSuppo rt.execute(ProgrammaticTransactionSupport.java:264) at com.lombardisoftware.server.core.TXCommand.executeInDeadlockRetr yLoop(TXCommand.java:86) at com.lombardisoftware.server.core.TXCommand.execute(TXCommand.jav a:75) at com.lombardisoftware.bpd.runtime.engine.quartz.AbstractBpdTask.e xecute(AbstractBpdTask.java:101) ... 14 more Problem Summary: When cancel the task a list of created tasks is used. Unfortunately in case of an exception the list contains data that are not valid when cancel tasks.
Problem conclusion
With this interim fix the list of tasks, that is used to cancel tasks, is cleaned up in case of an exception, so that no NumberFormatException will be thrown in this a case anymore.
Temporary fix
iFix for 8.0.1.1 is available on Fix Central, search for APAR JR47444 at http://www.ibm.com/support/fixcentral/ Fix is also targetted for inclusion in next fixpack for BPM BPM 8.0.1, BPM 8.5.0
Comments
APAR Information
APAR number
JR47444
Reported component name
BPM ADVANCED
Reported component ID
5725C9400
Reported release
801
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2013-08-07
Closed date
2013-10-11
Last modified date
2013-10-11
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 STANDARD
Fixed component ID
5725C9500
Applicable component levels
R801 PSY
UP
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSFTDH","label":"IBM Business Process Manager Standard"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.0.1","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
07 January 2022