Skip to main content

This content is closed to future replies and is no longer being maintained or updated.
Links may no longer function. If you have a similar request, please write a new post.

Question

 Chinna Avinash Samidi (ChinnaAvinash.Samidi)
Mercedes Benz Mobility
Solution Architect
Mercedes Benz Mobility
DE
ChinnaAvinash.Samidi Member since 2012 20 posts
Mercedes Benz Mobility
Posted: Mar 20, 2020
Last activity: Aug 30, 2021
Posted: 20 Mar 2020 8:01 EDT
Last activity: 30 Aug 2021 15:34 EDT
Closed

NumberFormatException in Logs - after Pega 8.3.2 upgrade

Hi Team,

We are performing upgrade of PRPC from V7.2.2 to V8.3.2 including Customer service and CRM FS V8.3

In this process, it is observed that NumberFormatException is getting printed in logs continuously. Can anyone of you guide on, "How to stop this exception from filling up PegaRules log file".

xxxx-xx-xx 19:18:43,692 [,19,2,3,4,5,6,7,8,9]] [  STANDARD] [                    ] [                    ] (.AtLeastOnceResilienceStrategy) ERROR   - Unable to acknowledge java.lang.NumberFormatException: For input string: ""     at java.lang.NumberFormatException.forInputString(NumberFormatException.java:76) ~[?:2.9 (11-22-2017)]     at java.lang.Long.parseLong(Long.java:613) ~[?:2.9 (11-22-2017)]     at java.lang.Long.parseLong(Long.java:643) ~[?:2.9 (11-22-2017)]     at com.pega.dsm.dnode.impl.dataset.kafka.KafkaAcknowledgmentService$KafkaAcknowledgmentTask.toAcknowledge(KafkaAcknowledgmentService.java:80) ~[d-node.jar:?]

Attached are the exception stack trace details for your reference.

- S Ch Avinash

To see attachments, please log in.
Pega Customer Service for Financial Services 8.3
Project Delivery
Financial Services
Senior System Architect

  • Sudheer Nimmagadda
Posted: 4 years ago
Posted: 3 Apr 2020 11:02 EDT
Pallavi Mandal (Pallavi_Mandal) Senior Technical Documentation Specialist
Pegasystems Inc.
IN

Hello Avinash,

Thank you for sharing your workaround.

Would you like to mark it as the Solution or would you still like input from the Pega Collaboration Center? Regards,

Pallavi M | Moderator | Pega Collaboration Center

To see attachments, please log in.
Posted: 4 years ago
Posted: 12 Aug 2020 8:03 EDT
Sudheer Nimmagadda (Sudheer Nimmagadda)
Highmark Health
Sr Application Developer
Highmark Health

This bug (BUG-559949) identified in Pega 8.3 version. The underlying problem in this issue is coming from Kafka Client https://issues.apache.org/jira/browse/KAFKA-7082 which was fixed in Pega 8.3.3 release. to fix this issue apply the latest Pega 8.3.4 patchset in your environment, meanwhile 

Temporary Workaround: 

1. Go to Dev Studio > Records > Sysadmin > Log Category and create a new log category rule instance.

2. Provide a short description and log category name such as "DataflowResilienceStrategy.default". Log category name is just ID of the rule instance. After clicking on create provide the default log level for the logger "com.pega.dsm.dnode.impl.dataflow.resilience.AtLeastOnceResilienceStrategy" and set it to OFF instead of current level "ERROR". This should eliminate the ERROR you are seeing.

 

To see attachments, please log in.
Posted: 3 years ago
Updated: 3 years ago
Posted: 26 Jul 2021 13:48 EDT
Updated: 26 Jul 2021 13:50 EDT
Omprakash Eleti (OmprakashE8365)
Radial Inc

Radial Inc
US

Hi Pega Team @

MarissaRogers,

 

We are also facing the same issue for our queue processors. We are on Pega 8.4.0. Below is the error in logs.

 

Did we have permanent fix for it? Could you pls recommend a permanent solution? Thank you.

 

Show More

Hi Pega Team @

MarissaRogers,

 

We are also facing the same issue for our queue processors. We are on Pega 8.4.0. Below is the error in logs.

 

Did we have permanent fix for it? Could you pls recommend a permanent solution? Thank you.

 

2021-07-26 17:29:38,157 [1,12,13,14,15,16,17]] [  STANDARD] [                    ] [                    ] (.AtLeastOnceResilienceStrategy) ERROR   - Unable to acknowledge data flow run [pzStandardProcessor] on thread [DataFlow-Service-PickingupRun-pzStandardProcessor:136, Access group: [PRPC:AsyncProcessor], Partitions=[0,1,10,11,12,13,14,15,16,17]] 
java.lang.NumberFormatException: For input string: "" 
	at java.lang.NumberFormatException.forInputString(NumberFormatException.java:65) ~[?:1.8.0_91] 
	at java.lang.Long.parseLong(Long.java:601) ~[?:1.8.0_91] 
	at java.lang.Long.parseLong(Long.java:631) ~[?:1.8.0_91] 
	at com.pega.dsm.dnode.impl.dataset.stream.StreamAcknowledgmentService$StreamAcknowledgmentTask.toAcknowledge(StreamAcknowledgmentService.java:91) ~[d-node.jar:?] 
	at com.pega.dsm.dnode.impl.dataset.stream.StreamAcknowledgmentService.toAcknowledge(StreamAcknowledgmentService.java:50) ~[d-node.jar:?] 
	at com.pega.dsm.dnode.impl.dataset.stream.StreamAcknowledgmentFeature.toAcknowledge(StreamAcknowledgmentFeature.java:37) ~[d-node.jar:?] 
	at com.pega.dsm.dnode.impl.dataflow.resilience.AtLeastOnceResilienceStrategy.acknowledge(AtLeastOnceResilienceStrategy.java:388) ~[d-node.jar:?] 
Show Less
To see attachments, please log in.

We'd prefer it if you saw us at our best.

Pega Collaboration Center has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice