CODEWITHSUNDEEP
javalinuxfilesystemsstartupeclipse-virgo
Philip Allgaier
Philip Allgaier

Reputation: 3669

Eclipse Virgo: Different startup order on Linux vs. Windows => How to fix?

The AProMoRe project is using an Eclipse Virgo server as the base. For the startup handling there are multiple ".plan" files to load the required artifacts. They are copied in the Virgo "pickup" folder and are named as follows:

Note: In the same folder there are also other JAR and WAR files.

Windows: Everything startups perfectly. The first file that the hot deployer picks up after Virgo starts ("KE0007I Virgo ready.") is the first plan file ("HD0001I Hot deployer processing 'INITIAL' event for file '100-manager.plan'."). And then next next, and so on. All good.

Linux: The behavior is completely different. The plan files are only picked up later on during the loading and the hot deployer starts for some reason by just picking some of the JAR/WAR files to load first, leading to all kinds of resolution/dependency errors.

The same Virgo version (3.6.2.RELEASE) is used on both platforms, so my assumption was that the startup order/behavior should be the same.

Is the filesystem look-up behavior of Virgo (or Java in general) different of those platforms? Is there a fix/workaround to get a matching behavior?

Upvotes: 0

Views: 86

Answers (1)

GianMaria Romanato
GianMaria Romanato

Reputation: 132

You should move the plans into the repository folder and create a top-level plan which lists them all in the right order, then drop only the top-level plan into the pickup folder.

Upvotes: 0

Related Questions