My current method can hold about 3000 threads until memory collapses. I'm
looking to replace this method with something more efficient in terms of
RAM usage. Something like a buffer, where each item needs far less RAM than
the kind of threads I'm creating now. Then when it gets full I will use
Amaz
> From: Brian Braun [mailto:brianbr...@gmail.com]
> Subject: Re: Best way to log requests from a servlet and to a database?
(Marking this off-topic, since it has nothing to do with Tomcat.)
> My current method can hold about 3000 threads until memory collapses. I'm
> looking to replace this meth
>
> it's not. maybe it will make things clear if i change the names of the
> paths, say:
>
> * when user goes to http://app1.com/ -> {thesamewebapp}/app1 path is served
> as root path of the domain app1.com
> * when user goes to http://app2.com/ -> {thesamewebapp}/app2 path is served
> as root path
> From: cjder...@gmail.com [mailto:cjder...@gmail.com] On Behalf Of chris derham
> Subject: Re: Different webapp paths on different hosts
> To my mind if you deploy the app as ROOT.war, as long as DNS is
> configured correctly, that single context will serve responses to
> http://app1.com/ and htt
On 1/26/2013 9:23 PM, chris derham wrote:
it's not. maybe it will make things clear if i change the names of the
paths, say:
* when user goes to http://app1.com/ -> {thesamewebapp}/app1 path is served
as root path of the domain app1.com
* when user goes to http://app2.com/ -> {thesamewebapp}/
On 1/26/2013 9:36 PM, Caldarale, Charles R wrote:
From: cjder...@gmail.com [mailto:cjder...@gmail.com] On Behalf Of chris derham
Subject: Re: Different webapp paths on different hosts
To my mind if you deploy the app as ROOT.war, as long as DNS is
configured correctly, that single context wi
> From: bxqdev [mailto:bxq...@themailbay.com]
> Subject: Re: Different webapp paths on different hosts
> in this case http://app1.com/ and http://app2.com/ will serve the same
> content.
> i need different content on different domains.
First you state that you want the same webapp to serve both
Hi chuck,
I finally found this, implemented it and works great!
http://docs.oracle.com/javase/6/docs/api/java/util/concurrent/LinkedBlockingQueue.html
However, if I get significantly more requests, this may not be enough
because MySQL will get slower and the queue will get full. I think I could
s
> From: Brian Braun [mailto:brianbr...@gmail.com]
> Subject: Re: [OT] Best way to log requests from a servlet and to a database?
> However, if I get significantly more requests, this may not be enough
> because MySQL will get slower and the queue will get full. I think I could
> start using this
