BPM, Workflow, and Case

BPM, Workflow, and Case

Come for answers. Stay for best practices. All we’re missing is you.

 View Only
  • 1.  BAW 20.0.0.1 - Cannot calculate next primary key issue

    Posted Fri November 24, 2023 06:28 PM
    Edited by Kwangho Kim Sun November 26, 2023 08:36 PM

    Hi Team

    When we manual deploy, I have met a below errors.

    000001ca BPMInstallPac I   BPMInstallPackage failed due to: CWLLG0433E: Tracking definitions were not sent successfully. Details: Cannot calculate next primary key
                                     java.lang.Exception: CWLLG0433E: Tracking definitions were not sent successfully. Details: Cannot calculate next primary key

    ...

    ...

    Caused by: com.lombardisoftware.core.TeamWorksRuntimeException: Cannot calculate next primary key
            at com.lombardisoftware.server.ejb.pk.PerfPKGeneratorCore.getNextHigh(PerfPKGeneratorCore.java:104)

    Do I need to increase timeout or refresh etc?

    Can you please help and guide?

    Thanks.



    ------------------------------
    Kwangho Kim
    ------------------------------



  • 2.  RE: BAW 20.0.0.1 - Cannot calculate next primary key issue

    Posted 14 hours ago

    Hi Kwangho Kim,

    I don't know how you resolved it. But in my case, the error was CWLLG0433E: Tracking definitions were not sent successfully. And when I checked the SystemOut.log file for the stacktrace, I found that a NoClassDefFoundError was also present, along with the error mentioned above, CWLLG0433E. Then I figured out that there is a log4j version 1 dependency was added by me in {InstallationPath}/BPM/Lombardi/lib/log4j, which was causing this error of NoClassDefFoundError. Once I removed it and replaced it with Log4j version 2 dependency in the same folder {InstallationPath}/BPM/Lombardi/lib/, then the error got resolved.

    I posted the above information on this thread because this kind of error was not discussed in too many forums, except the IBM Documentation (which was not enough to resolve the error) and which says we should contact IBM Support to get it resolved.



    ------------------------------
    Muhammad Haris Khan
    ------------------------------