Deployment of EJB_Timer_App fails with reference to an application class #618
Comments
|
Issue is not present in 4.1.1.154, is present with 4.1.1.161-SNAPSHOT with eclipselink downgraded to 2.6.1-p1. |
|
We'll package the source and get it into the Patched Projects Repo. |
|
Could you describe in more detail the applications you are deploying and the order. |
|
I'm deploying an EJB jar with persistence context and timer service. Based on my last comment this doesn't seem to be related to eclipselink upgrade, so I went through changes in 161. Reverting 82819f4, which seemed as a probable cause doesn't solve this. Instead it is likely caused by switching to using standard orm.xml file in ejb-timer-app, which was done in e14ece3. Eclipselink will then pickup not only timer's orm.xml, but also application's one. I'll know for sure in about 20 minutes, when I build embedded jar again. |
|
Eclipselink source should be here https://github.com/payara/Payara_PatchedProjects/tree/master/org/eclipse/persistence/source/2.6.2.payara-p1 |
|
Thank you, hopefully I won't be needing them. I was right in my last comment, it was standard name of orm.xml. PR follows. Concerning test case, do you have some standard way of providing them, like arquillian? I'm not sure I can extract the test from my project now, especially, since it's about same age as ARQ, and therefore uses embedded API directly. |
…orm.xml When application contains META-INF/orm.xml, then this file is also processed when EJB Timer Service is deployed. To prevent this ejb-timer-service-app was using non-standard name. This reverts parts of e14ece3, that switched back to standard
Fix for Payara #618 - Deployment of EJB_Timer_App fails when app has orm.xml
|
Fixed by #621 |
PAYARA-3665 PAYARA-3676 4.191.Maintenance Approved-by: Jonathan Coustick <jonathan.coustick@payara.fish>
…a#618)" This reverts pull request payara#618. > * Merge pull request payara#3870 from Pandrex247/PAYARA-3676-Asadmin-Prompt-Issues > > PAYARA-3676 PAYARA-3665 Fix More Asadmin Prompt Issues > > > * PAYARA-3665 Merge conflicts > > > > Notable changes are in the second commit: String vs. char
Revert "PAYARA-3665 PAYARA-3676 4.191.Maintenance (pull request payara#618)"
payara#618)"" This reverts commit 12e739b.
…rise Revert "FISH-5747 Upgrade Corba to version 4.2.4.payara-p1"
When deploying an ejb jar into embedded container on 4.1.161-SNAPSHOT following exception is thrown:
The core issue is, that we are deploying timer service here and its persistence context (the entity backing table EJB__TIMER__TBL), so in no way it should process any of the application classes at this point. Application's persistence context have been successfully loaded earlier, before EJB initialization started.
Tried to debug this, but with checked out eclipselink tag 2.6.2 I land at empty line on
MetadataProject.1877so I cannot proceed further without access to sources of 2.6.2-p1.The text was updated successfully, but these errors were encountered: