3 Replies Latest reply on Sep 23, 2013 7:40 AM by Wolf-Dieter Fink

    Deployment scanner ordering

    Maciej Swiderski Master



      I am experiencing a quite interesting (to not say weird) behavior with deployments on EAP6.1. So to give bit of a background, there are two web applications (wars) where one (AppA) has persistence.xml that is used to bootstrap data base. The second application (AppB) uses the same data base to read data from. So when application AppA bootstraps it will create persistence unit and build data base with hibernate auto ddl. Then AppB when bootstrapping it tries to connect to that db to prepare its internal components for execution. And now the "funny" part - AppB always fails when running on Java 6 but it always works on Java 7.


      So the main question is - is there anything that might be causing this behavior that depends on Java version?


      Another interesting part is that when renaming the deployments to be 1AppA and 2AppB it all works well on both Java 6 and Java 7... any idea?


      Here are the exact info about both Java:


      java version "1.6.0_51"

      Java(TM) SE Runtime Environment (build 1.6.0_51-b11-457-11M4509)

      Java HotSpot(TM) 64-Bit Server VM (build 20.51-b01-457, mixed mode)


      java version "1.7.0_25"

      Java(TM) SE Runtime Environment (build 1.7.0_25-b15)

      Java HotSpot(TM) 64-Bit Server VM (build 23.25-b01, mixed mode)


      testing that on OSX 10.8.4




      I know that the ordering in general is sort of non deterministic with such configuration (one app depends on another) but why it would work like this differently where the only difference is java version.


      Thanks a lot for any help