Question
Bradesco Seguros
BR
Last activity: 13 Jan 2022 17:24 EST
Failed to start Kafka - Invalid decorator
Hey Everyone,
We are setting up environments for Pega version 8.6 and are having problems at the time we boot the environment where Kafka cannot start. Especially when it tries, as per the message below, to generate the log information:
2022-01-04 10:31:51,813 [StreamServer.Default] [ STANDARD] [ ] [ ] ( dsm.kafka.Kafka) ERROR - Failed to start Kafka on 1 attempt, kafka log [0.008s][error][logging] Invalid decorator '\Tomcat 9.0_Tomcat9-PEGA\kafka- Proprietary information hidden\logs\kafkaServer-gc.log'. Invalid -Xlog option '-Xlog:gc*:file=E:\Tomcat 9.0_Tomcat9-PEGA\kafka- Proprietary information hidden\logs\kafkaServer-gc.log:time,tags:filecount=10,filesize=102400', see error log for details. Error: Could not create the Java Virtual Machine. Error: A fatal exception has occurred. Program will exit.
We are using TomCat 9 with SQL Server database.
In the development environment, we have 1 node that is set to Universal.
Is there any procedure that should be performed in relation to Tomcat's default directory, so that it can identify the indicated folder? What are the most appropriate ways to assess and correct the problem?
Accepted Solution
Updated: 13 Jan 2022 17:24 EST
Pegasystems Inc.
US
I cannot give advice for 1.17, as I haven't even tried this version yet. Mostly using openjdk version "1.8.0_312", but openjdk 1.11 (I recommend the latest version jdk-11.0.13+8) is also supported for 8.6.
Pegasystems Inc.
US
Any chance that you are using an older jdk version here?
From the error, it looks like this could related to be a jdk bug: https://bugs.openjdk.java.net/browse/JDK-8215398
If so, try a newer/latest jdk version.
Also, it seems that this bug doesn't affect jdk 8, maybe you could try that as another option.
Bradesco Seguros
BR
Thanks for the feedback. We apply the new version of OpenJDK 1.17. We are using version 8.6.1. I verified that the problem was worked around, however, some OOTB rules, such as to validate the application, or, check platform performance information are not running.
Generating error like these:
Thanks for the feedback. We apply the new version of OpenJDK 1.17. We are using version 8.6.1. I verified that the problem was worked around, however, some OOTB rules, such as to validate the application, or, check platform performance information are not running.
Generating error like these:
There was a problem getting a list: code: 8120 SQLState: S0001 Message: Column 'PegaDATA.pr_perf_stats.pxRequestorID' is invalid in the select list because it is not contained in either an aggregate function or the GROUP BY clause. 2022-01-07 16:39:23,575 [ http-nio-80-exec-8] [ STANDARD] [ ] [Origination:01.01.01] ( pega.jsr199.Jsr199Bridge) ERROR pegamiddledev.br800.corpintra.net| Proprietary information hidden HHGBBASPX7EV863IMN8PSCUMELTF36TQYA Lucas.papa - Failed to compile rule: /com/pegarules/generated/expressions/ra_action__pystartingdate__pycontentsource_pyparameters___pytimeperiod_52bfc6c9b90d1b4cf6c8de0579ad7a12.java 2022-01-07 16:39:23,587 [ http-nio-80-exec-8] [ STANDARD] [ ] [Origination:01.01.01] (sm.VirtualTableAssemblyHandler) ERROR pegamiddledev.br800.corpintra.net| Proprietary information hidden HHGBBASPX7EV863IMN8PSCUMELTF36TQYA Lucas.papa - The rule which attempted to use a non-accessible jar during rule compilation is: "com.pegarules.generated.expressions.ra_action__pystartingdate__pycontentsource_pyparameters___pytimeperiod_52bfc6c9b90d1b4cf6c8de0579ad7a12". Please see error above for non-accessible jar information. 2022-01-07 16:39:23,587 [ http-nio-80-exec-8] [ STANDARD] [ ] [Origination:01.01.01] (sm.VirtualTableAssemblyHandler) ERROR pegamiddledev.br800.corpintra.net| Proprietary information hidden HHGBBASPX7EV863IMN8PSCUMELTF36TQYA Lucas.papa - Failed to compile com.pegarules.generated.expressions.ra_action__pystartingdate__pycontentsource_pyparameters___pytimeperiod_52bfc6c9b90d1b4cf6c8de0579ad7a12, pzInsKey = RULE-DECLARE-EXPRESSIONS RULE-OBJ-REPORT- .PYSTARTINGDATE!.PYCONTENTSOURCE.PYPARAMETERS().PYTIMEPERIOD #20180713T131517.205 GMT; see class's compile log file. 2022-01-07 16:39:23,590 [ http-nio-80-exec-8] [ STANDARD] [ ] [Origination:01.01.01] ( internal.mgmt.Executable) ERROR pegamiddledev.br800.corpintra.net| Proprietary information hidden HHGBBASPX7EV863IMN8PSCUMELTF36TQYA Lucas.papa - FirstUseAssemblerException
Are there any limitations due to this update? Any recommended procedure after this update?
Can the recommendation indicated in the link -
be effective?
Thanks a lot for the help.
Pegasystems Inc.
US
re: OpenJDK 1.17
According to the Platform Support Guide, your options for Pega 8.6 are OpenJDK 1.8 & OpenJDK 1.11
I would try the latest version of one of these instead of version 1.17
Bradesco Seguros
BR
@PhilipShannon We tried the latest version of 1.11 but it was not effective. That's why we opted for the most current version, which allowed the Kafka bug to be resolved. However, I brought these points that I mentioned. Therefore, I ask if we could use as a complement the procedure indicated in the link - https://docs-previous.pega.com/pega-services-troubleshooting/troubleshooting-fua-compiler-error-requires-16-compliant-jvm
Pegasystems Inc.
US
If jdk 1.11 didn't work then I would try openjdk version "1.8.0_312"
Since I did not see any “Requires a 1.6 compliant JVM” message in your posted log info, I didn't find the article to be relevant for your situation
Bradesco Seguros
BR
I will put in the action plan, this possibility of downloading the OpenJDK version. What we evaluated was that, for example, after updating to version 1.17, in addition to solving the Kafka problem, the application started to climb faster. Would it really make sense to put a version below 1.11?
Accepted Solution
Updated: 13 Jan 2022 17:24 EST
Pegasystems Inc.
US
I cannot give advice for 1.17, as I haven't even tried this version yet. Mostly using openjdk version "1.8.0_312", but openjdk 1.11 (I recommend the latest version jdk-11.0.13+8) is also supported for 8.6.
Bradesco Seguros
BR
Excellent point and that's exactly what we did just a little bit in the environment, apply version Proprietary information hidden+8. From what we've seen, it runs well and allows the error that it had identified to be resolved. it is an October 2021 update. Important that this is noted so others can apply the most up-to-date version of 1.11 and that the platform will not OOTB compile above version 1.11 unless it is updated to the next version.