Question
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
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
Hi Avinash,
what is the Backgroundprocessing data flow name that you stopped ?
Thanks
Sudheer.
Hi,
We are also facing the same issue. Did someone find any solution for this?
We are also facing the same issue after upgrading from 8.1.x to 8.3.2.
Could you please forward if you have any solution.
Sandeep999 and sravans4
Did either of you try the workaround that was suggested above?
Thanks!
Marissa | Senior Moderator | Pega Collaboration Center
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.
SUDHEER Nimmagadda
Still I can see this issue in 8.3.4 Version. I have upgraded to 8.3.4 yesterday but still issue exists in 8.3.4 version.
Hi Team,
As a workaround, we stopped the "Backgroundprocessing" data flow and in turn exceptions are also stopped in logs.
Thanks and Regards,
S Ch Avinash