-
Notifications
You must be signed in to change notification settings - Fork 304
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bug Report: SecurityException with signed jars after upgrading from Payara 5 to Payara 6.2024.5 #6776
Comments
Hi @garychan21, Could you please provide a simple-to-follow scenario on how to reproduce this on the latest version? A reproducer should ideally follow the SSCCE rules: http://www.sscce.org/.. It will greatly help us to find the cause and fix it. Thank you, |
Greetings, |
Greetings, |
Brief Summary
We recently migrated our application from the
javax
tojakarta
namespace along with upgrading the server from Payara 5 to Payara 6.2024.5. We are using thepayara-embedded-all-6.2024.5.jar
as the main dependency. We usejarsigner
to sign our jar files which are deployed to the glassfish domain specific lib folder. I.e.<glassfish_home>/domains/<our_domain>/lib
. When trying to deploy an .ear file which contains a remote EJB 2.x interface, we get this EJB Container initialization error:Caused by: java.lang.SecurityException: class "com.mmsi.util.config.ejb._ConfigurationPropagatorHome_DynamicStub"'s signer information does not match signer information of other classes in the same package
Expected Outcome
The migrated application with the remote EJB 2.x interfaces will be deployable in Payara 6.2024.x as they were in Payara 5.
Current Outcome
The .ear deployment containing the remote EJB 2.x interface results in a EJB Container initialization error:
Reproducer
Example of our EJB classes:
Operating System
Window Server 2019 Standard
JDK Version
Zulu JDK 11.0.22
Payara Distribution
Payara Server Full Profile
The text was updated successfully, but these errors were encountered: