I was just migrating my application to Payara 6.2022.1. But while starting, I face the following error message:
[2022-11-04T17:00:52.194+0100] [Payara 6.2022.1] [SCHWERWIEGEND]  [javax.enterprise.system.tools.deployment.common] [tid: _ThreadID=118 _ThreadName=payara-executor-service-task] [timeMillis: 1667577652194] [levelValue: 1000] [[
Exception while visiting de/.../MonitoringResultVO.class of size 1730
java.lang.UnsupportedOperationException: Record requires ASM8
I use records as data-objects for CDI-events, which work fine in Payara 5.2022.2 (on JDK temurin-17).
Ulrich, I wish I could help, but actually I’m having a similar problem using Springframework web mvc 6.0. In my case, I’ve opened a forum item but in my case I’ve reported it as “CDI is not available.” which occurs after a slew of these ASM8 and ASM9 required messages.
If you’re able to figure this our, be sure to reach out to me at email@example.com. Thanks, and I’ll do the same.
Thank you for reporting this bug. We are aware of the issue, and our Engineering team is working on a fix. I cannot provide a specific timeframe for the fix, as the problem is not prioritised at the moment, but I will post an update once it has been solved.
It should be a priority as should updating the CDI used. Both are stopping all application development using spring web mvc work on payara 6. My response from their team clearly stated that payara (and glassfish?) are not in synced with Jakarta 10.
I’d love to hear when a corrected version is being released.
Hi Felix, thanks for the response. For me, it should be of priority as well, because otherwise we cannot update to Payara6, but we are forced to because Payara5 get no updates anymore… and I would not transfer all Records to DTOs anymore… it would be very nice to get an update soon… many thanks
Thank you so much for your discovery! I have updated the internal issue with the GitHub issue linked here. We always encourage community members to submit a PR that the Engineering team would gladly verify.
The issue is sadly not prioritised at the moment, as the issues occur mostly on Spring applications, and our customer base mainly uses Jakarta EE. I apologise for all the trouble caused by this bug.
that’s not right, that this issue occurs mostly on Spring applications, it occurs in every Payara application using records with Java 17.
The bug blocks us from migrating to Payara 6… so it would be very nice, if this bug could be fixed shortly. Many thanks in advance!