Phoenix dist/work directory question

[Andrei Ivanov <my...@surfeu.fi>]

Hi
Latest Phoenix, creates work directory where it stores all jars under
"myapp.sar-XYZ/SAR-INF/lib/" for every run of the phoenix application. What
is the idea behind this and where one can read about this new feature of
Phoenix?

Br. Andrei



--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>

location for keystore/truststore inside sar?

[Andrei Ivanov <my...@surfeu.fi>]

Hi
Where is the default location for keystore/truststore inside sar? Can these
files be included during build process using ant sar target and/or how whey
can be deployed to a phoenix application (any recommendations)?

Regards, Andrei

PS thanks for comments on my previous questions.


----- Original Message -----
From: "Peter Donald" <pe...@apache.org>
To: "Avalon-Phoenix Developers List" <av...@jakarta.apache.org>
Sent: Wednesday, May 15, 2002 12:08 AM
Subject: Re: Phoenix dist/work directory question


On Wed, 15 May 2002 06:40, Andrei Ivanov wrote:
> Latest Phoenix, creates work directory where it stores all jars under
> "myapp.sar-XYZ/SAR-INF/lib/" for every run of the phoenix application.
What
> is the idea behind this and where one can read about this new feature of
> Phoenix?

Previously when deploying an application it would extract the jars and
classes
into $PHOENIX_HOME/apps/myapp/SAR-INF/lib. Then these jars are loaded by
URLClassLoader and the application is run.

However a problem occurs when you try to redeploy the same application while
running. Once loaded via the URLClassLoader, the JVM caches the jars in
memory - thus even if you change the jars on the filesystem you will still
be
using the classes from the old jars.

Using a temporary "work" directory gets around this (and is similar to what
tomcat/jboss/other app servers do). Basically the jars are loaded from a new
directory every time they are deployed meaning that JVM will not cache them.

The bug entry for it is at

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=8648

But unfortunately it has not been extensively documented yet.

--
Cheers,

Peter Donald


--
To unsubscribe, e-mail:
<ma...@jakarta.apache.org>
For additional commands, e-mail:
<ma...@jakarta.apache.org>



--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>

Re: Phoenix dist/work directory question

[Peter Donald <pe...@apache.org>]

On Wed, 15 May 2002 06:40, Andrei Ivanov wrote:
> Latest Phoenix, creates work directory where it stores all jars under
> "myapp.sar-XYZ/SAR-INF/lib/" for every run of the phoenix application. What
> is the idea behind this and where one can read about this new feature of
> Phoenix?

Previously when deploying an application it would extract the jars and classes 
into $PHOENIX_HOME/apps/myapp/SAR-INF/lib. Then these jars are loaded by 
URLClassLoader and the application is run. 

However a problem occurs when you try to redeploy the same application while 
running. Once loaded via the URLClassLoader, the JVM caches the jars in 
memory - thus even if you change the jars on the filesystem you will still be 
using the classes from the old jars.

Using a temporary "work" directory gets around this (and is similar to what 
tomcat/jboss/other app servers do). Basically the jars are loaded from a new 
directory every time they are deployed meaning that JVM will not cache them.

The bug entry for it is at

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=8648

But unfortunately it has not been extensively documented yet.

-- 
Cheers,

Peter Donald


--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>