-
15. Re: ejb failure on 64bit jdk ( solaris sparc )
wdfink Aug 20, 2015 6:55 AM (in response to basita)I suppose that this is a deployment order problem.
If you not specify any dependency the order might change if you run a 64bit vm.
If you have different app-deployments you might move the one with dependencies to deploy-last folder to start it at the end.
If it is the same application ear you need to set a dependency with an ejb-reference inside of the deployment descriptor, this should be handled by the container.
-
16. Re: ejb failure on 64bit jdk ( solaris sparc )
mayerw01 Aug 20, 2015 12:38 PM (in response to basita)Another idea. Is this a standard application or self developed?
The class fxratesservice does not appear to be an open source class. It does rather look like a financial thing.
Did you try to contact your application provider to get more info? Maybe there are some constraints programmed that prevent the application from running in a 64 bit JRE.
-
17. Re: ejb failure on 64bit jdk ( solaris sparc )
basita Aug 20, 2015 12:44 PM (in response to mayerw01)This is part of a product developed by our development team. They have not tested this on the sparc platform, as mentioned before, this is only happening in sparc. We do not release platform specific versions for our customers. So I guess this needs to be tested and the deployment order changed for sparc platform? What in particular should be changed in jboss?
-
18. Re: ejb failure on 64bit jdk ( solaris sparc )
mayerw01 Aug 21, 2015 7:51 AM (in response to basita)Just to understand you correctly. This issue occurs only on Solaris.
The application runs fine under some other operation system (Linux, Windows etc) even on the 64 bit jre?
-
19. Re: ejb failure on 64bit jdk ( solaris sparc )
basita Aug 21, 2015 8:53 AM (in response to mayerw01)Yes that is correct, the same application works on with JDK64bit on linux and windows.
-
20. Re: ejb failure on 64bit jdk ( solaris sparc )
mayerw01 Aug 21, 2015 11:27 AM (in response to basita)But then I do not understand why the 'deployment order problem' comes up on Solaris only.
And you are also saying that the JRE is properly installed on Solaris and testing on JRE 1.7 is not an option?