I'm having a problem deploying to Orion, which causes the deployment
time to increase over time, and eventually the jvm orion is in to run
out of memory. Basically, I'm using ANT to deploy, calling the Orion
admin tool (com.evermind.client.orion.OrionConsoleAdmin) and passing the
relevant parameters into it. The EAR file I'm deploying includes a lib
directory, with all of the required extra jar files in it (utilities,
etc). In order for orion to use these when loading a bean, I put the
line <library path="../lib"/> into orion-application.xml, between the
<persistence/> and <principals/> tag. Orion does indeed load up the jar
files as expected, so that works.
The problem is that each time I deploy, the number of <library
path="../lib"/> tags at least doubles, and at one stage I was left with
over 500 <library path="../lib"/> tags in the orion-application.xml
file. At this stage, the server slowed to a crawl, and either took
several minutes to load up the beans, or else crashed.
Has anybody come across this behaviour? And what can I do about it?
And does anybody know of a good source of documentation on the various
configuration options available for Orion, as I find it is poorly
documented in all areas. Maybe the people at IronFlare could get their
act together from counting all the money from Oracle, and produce a
decent, (even semi-)professional set of documentation.
Regds.,
Ois�n.
