Wepshpere: order of loading of modules

We have irritating problem while deploying .war (which contains ejb components in jar inside) on two different PCs with same WAS v8.5.2.2

When we deploy our app on the first PC - everything looks good, while deploying on the second - it fails 'cause it is not able to find ejb bean in environment.

It's important to note that servers configs are quite the same. But order of loading of modules is different though: in first case it loads ejb module(jar) first and then web module, in second case - visa versa:

WebGroup SRVE0169I: Loading Web Module: UD-BACKGROUND-PROCESSES-SERVER. .....

WSVR0037I: Starting EJB jar: ud-background-processes-server-1.18.0_15914.war

And we think that it's the cause of failure.

How and where can it be configured?

Moreover - couple of times it was possible to make it load in the right order without changing server configuration! But we couldn't catch the rule of such behavior changing.

Also .war (and jars in it) contains neither of Websphere specific config files(like ibm-ejb-jar-bnd.xml) nor ejb specific files (ejb-jar.xml). It's configured using annotations @Stateless\@EJB\@LocalBean only.

Any thoughts on this issue?

Solution

Finally we've found out the reason of such behavior and we have changed order of loading by turning off checkbox values (see pictures) and restarting the server.

enter image description here

-----

enter image description here

-----

enter image description here

Actually we don't know yet which one made sence