Closed garychan21 closed 2 months ago
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, Elif
Greetings, It's been more than 5 days since we requested more information or an update from you on the details of this issue. Could you provide an update soon, please? We're afraid that if we do not receive an update, we'll have to close this issue due to inactivity.
Greetings, It's been more than 5 days since this issue was identified as abandoned. We have closed this issue due to inactivity, please feel free to re-open it if you have more information to share.
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