Posted: Tue Jul 30, 2019 11:05 pm Post subject: Deploying same name jar files in 2 separate BARs on same EG
Newbie
Joined: 17 May 2019 Posts: 4
I have 2 applications A and B, for which 2 BARS A.bar and B.bar. Both of the BARs have a jar file with same name i.e. J1.jar. This jar is a packaged JCN and dependent classes. The jars in both the BARs are almost same except some changes in the java code in B.bar. Now I deploy application A, i.e. A.bar on EG1 and test, it works fine. Then I deploy application B, i.e. B.bar on the same EG1. The code in A.bar breaks. When I remove the changes in java code in the jar packaged in B.bar and deploy in EG1, code in A.bar works fine. This means the jar file is conflicting. I couldn't understand why it is conflicting if the jars are packaged in 2 different bars and are showing under different applications after deployment. How does broker treat it internally or if the jar in B.bar override the jar in A.bar because of same name? any pointers would be appreciated.
hi...what version of IIB are you using? what you've observed was the default behavior till v9 as it is relying either on the shared Integration level classloader or the Broker level one but in v10 it looks like java isolation is enabled by default for applications,
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum