Christopher Schultz wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
André,
On 2/21/2010 10:21 AM, André Warnier wrote:
You can certainly do that on the base of symbolic links and NFS mounts
for instance. Each Tomcat would contain something like :
Just be sure that Tomcat doesn't delete
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
André,
On 2/21/2010 10:21 AM, André Warnier wrote:
> You can certainly do that on the base of symbolic links and NFS mounts
> for instance. Each Tomcat would contain something like :
Just be sure that Tomcat doesn't delete your entire document reposi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hassan,
On 2/21/2010 9:36 AM, Hassan Schroeder wrote:
> On Sun, Feb 21, 2010 at 3:23 AM, imrank wrote:
>
>> Can I use the approach of having all the files sitting on a single NFS file
>> server and have the different tomcat instances read/write the
On Sun, Feb 21, 2010 at 3:01 PM, imrank wrote:
> Hasan, the approach you described is one that I was also considering to keep
> things consistent across tomcat instances (btw, there is no modifications
> occurring to existing files). I was considering using an approach whereby
> after a file is u
f the static files is done at the Apache level,
> you may be able to use one of the caching modules available at the
> Apache level, to avoid even more network traffic.
> But again that depends on the application, and how often the same files
On Sun, Feb 21, 2010 at 8:54 AM, André Warnier wrote:
>> it's uploads that
>> add a file to the file system on the Tomcat that processed the request.
>> And that would be the source filesystem to rsync from.
>
> Yes, but how often ?
In the simplest case, once each time a file is uploaded :-)
Ho
Hassan Schroeder wrote:
On Sun, Feb 21, 2010 at 7:36 AM, André Warnier wrote:
Not to mention possible inconsistencies between the different copies..
;-)
Imagine you have 4 balanced Tomcats, each of which has its own file
repository, and each of which can potentially run the next upload request
On Sun, Feb 21, 2010 at 7:36 AM, André Warnier wrote:
> Not to mention possible inconsistencies between the different copies..
> ;-)
> Imagine you have 4 balanced Tomcats, each of which has its own file
> repository, and each of which can potentially run the next upload request or
> download requ
Hassan Schroeder wrote:
On Sun, Feb 21, 2010 at 3:23 AM, imrank wrote:
Can I use the approach of having all the files sitting on a single NFS file
server and have the different tomcat instances read/write the files to that
server's filesystem? I guess theres gonna be some cost in terms of netw
imrank wrote:
Hey,
Thanks for ur prompt reply.
Unfortunately, the approach you described wouldn't work in our case because
our app needs to do some custom authorization logic before a file can be
downloaded (sorry should've mentioned that). I dont think I can get httpd to
perform this authoriza
On Sun, Feb 21, 2010 at 3:23 AM, imrank wrote:
> Can I use the approach of having all the files sitting on a single NFS file
> server and have the different tomcat instances read/write the files to that
> server's filesystem? I guess theres gonna be some cost in terms of network
> latency...
Not
-
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: users-h...@tomcat.apache.org
>
>
>
--
View this message in context:
http://old.nabble.com/Serving-static-files-in-a-cluster-tp27672008p27674733.html
Sent from the Tomc
Imran Khan wrote:
Hey,
I am using tomcat 5.5.26 on Ubuntu, currently having a clustered
configuration, but having the entire cluster on a single box. I have the
tomcat instances sitting behind apache.
Eventually I'd like to move to cluster on different physical boxes. Part of
our application in
Hey,
I am using tomcat 5.5.26 on Ubuntu, currently having a clustered
configuration, but having the entire cluster on a single box. I have the
tomcat instances sitting behind apache.
Eventually I'd like to move to cluster on different physical boxes. Part of
our application involves serving files
14 matches
Mail list logo
