Yes, I am using 7.0.4. Will create a entry in the bugzila system
Thanks.
2010/10/28 Mark Thomas
> On 28/10/2010 02:20, Ivan wrote:
> > Thanks for clarifying it, so do the devs have plan for it ?
>
> Yes. What? Fix it. When? TBD.
>
> Creating a bugzilla entry will ensure it doesn't get forgotten.
On 28/10/2010 02:20, Ivan wrote:
> Thanks for clarifying it, so do the devs have plan for it ?
Yes. What? Fix it. When? TBD.
Creating a bugzilla entry will ensure it doesn't get forgotten.
I see you still haven't told us which version you are using. I assume
you've tested 7.0.4.
Mark
> Hope it
Thanks for clarifying it, so do the devs have plan for it ?
Hope it could be fixed soon.
2010/10/27 Mark Thomas
> On 27/10/2010 06:43, Ivan wrote:
> > Hi,
> > While calling the method destory() on the StandardContext directly,
> it
> > seems that the method destoryInternal() is called twice
Thanks for clarifying it, does the devs have plan for it ? Hope it could be
fixed soon.
2010/10/27 Mark Thomas
> On 27/10/2010 06:43, Ivan wrote:
> > Hi,
> > While calling the method destory() on the StandardContext directly,
> it
> > seems that the method destoryInternal() is called twice i
2010/10/28 Leon Rosenberg :
> Hello Konstantin,
>
> On Wed, Oct 27, 2010 at 11:53 PM, Konstantin Kolinko
> wrote:
>> 2010/10/28 Leon Rosenberg :
>>>
>>> Well, that would just move the problem from stopping Timer to calling
>>> shutdown on Executor, wouldn't it?
>>>
>>
>> The problem is with the T
> From: Leon Rosenberg [mailto:rosenberg.l...@gmail.com]
> Subject: Re: How to start a daemon without getting the warning?
> But I can't detect any obvious Thread.getContextClassLoader()
> calls in the code below:
The problem isn't associated with calling the above method, it's actually that
th
Hello Konstantin,
On Wed, Oct 27, 2010 at 11:53 PM, Konstantin Kolinko
wrote:
> 2010/10/28 Leon Rosenberg :
>>
>> Well, that would just move the problem from stopping Timer to calling
>> shutdown on Executor, wouldn't it?
>>
>
> The problem is with the Thread.getContextClassLoader() for your
> t
2010/10/28 Leon Rosenberg :
>
> Well, that would just move the problem from stopping Timer to calling
> shutdown on Executor, wouldn't it?
>
The problem is with the Thread.getContextClassLoader() for your
thread. It contains a reference to the webapp classloader, and thus
does not allow to GC it
On Wed, Oct 27, 2010 at 11:39 PM, Caldarale, Charles R
wrote:
>> From: Leon Rosenberg [mailto:rosenberg.l...@gmail.com]
>> Subject: Re: How to start a daemon without getting the warning?
>
>> Meaning that I have to implement own thread registry for
>> all started threads?
>
> Nobody's going to do
> From: Leon Rosenberg [mailto:rosenberg.l...@gmail.com]
> Subject: Re: How to start a daemon without getting the warning?
> Meaning that I have to implement own thread registry for
> all started threads?
Nobody's going to do it for you, since they're part of your webapp. (Might be
an interes
On Wed, Oct 27, 2010 at 10:43 PM, Caldarale, Charles R
wrote:
>> From: Leon Rosenberg [mailto:rosenberg.l...@gmail.com]
>> Subject: How to start a daemon without getting the warning?
>
>> to my knowledge this thread is a daemon.
>
> Which isn't really relevant in the situation where only the conte
> From: Leon Rosenberg [mailto:rosenberg.l...@gmail.com]
> Subject: How to start a daemon without getting the warning?
> to my knowledge this thread is a daemon.
Which isn't really relevant in the situation where only the context is being
stopped, not the entire JVM.
> how can I avoid this wa
Hello,
I'm getting following warning with 6.0.29,
after shutdown:
SEVERE: The web application [/moskitodemo] appears to have started a
thread named [MoskitoMemoryPoolReader] but has failed to stop it. This
is very likely to create a memory leak.
here's the snapshot of the code that starts the th
On 27/10/2010 17:56, laredotornado wrote:
>
> Hi,
>
> We're using Tomcat 6.0.24. We're noticing a high number of active Tomcat
> connections on one of our servers. We suspect that a lot of these
> connections are idle and waiting for a database call to return, but how can
> we nail down more co
> From: laredotornado [mailto:laredotorn...@gmail.com]
> Subject: How to troubleshoot what's causing so many connections?
> We're noticing a high number of active Tomcat
> connections on one of our servers.
First off, what do you mean by "Tomcat connections"? That's rather ambiguous
phrasing.
Hi Tomcat - Users,
I use Tomcat 6.0.29 on a Suse 11.1 Linux Server and I would like to start
my application without localhost, only with virtiual host.
On Windows it works already.
Here is the server.xml:
mmmtest.ch
Now I can reach the network with
Hi Mladen,
I 've understand the firt step.
The second step
< mod_jk supports only IPV4 >
How and where can I do this.
Thank' for your help
Regards
Michael Wendt
-Ursprüngliche Nachricht-
Von: Mladen Turk [mailto:mt...@apache.org]
Gesendet: Montag, 25. Oktober 2010 17:41
An: users@to
I did not say "concurrent users". Just active sessions. There are,
under normal circumstances, not more than 50 conccurent requests.
Original-Nachricht
Betreff: Re: ISAPI-Problem
Von: Mladen Turk
An: users@tomcat.apache.org
Datum: 27.10.2010 15:30
On 10/27/2010 03:24 PM, Jost
On 10/27/2010 03:24 PM, Jost Richstein wrote:
I am using the following small worker.properties:
worker.ajp13.connection_pool_size=500
...
My Tomcat site works fine in general, there are up to 1.400 users active and
the site
So how do you expect 500 connections will serve up to 1400 concu
Thank you. That's exactly what I was looking for.
-Original Message-
From: Caldarale, Charles R [mailto:chuck.caldar...@unisys.com]
And look here, for step-by-step instructions:
http://wiki.apache.org/tomcat/HowTo#How_do_I_make_my_web_application_be_
the_Tomcat_default_application_.3F
Hi,
I have the following problem on a Windows Server 2003 64Bit (AMD).
Configuration:
IIS 6, isapi_redirect.dll AMD64 Version 1.2.30, Tomcat 5.5.27, JDk 1.6.0_12
64Bit.
I am using the following small worker.properties:
ps=\
worker.list=ajp13
worker.ajp13.port=8010
worker.ajp13.host=localh
On 27/10/2010 11:16, Mark Thomas wrote:
> On 27/10/2010 11:08, Pid wrote:
>> On 26/10/2010 16:08, Marc Wilmots wrote:
>>> Hi again.
>>>
>>> I checked out the executor element, although, I can't find a lot of
>>> information about it.
>>> Would you mind explaining why using the executor element woul
> From: M.S.Eesh [mailto:freeos...@gmail.com]
> Subject: Access for restricted user to restart
> I have installed Apache tomcat 5.0.28
Over six years old and unsupported. Start again.
> Now I need to give access for restricted windows vista
> user to restart tomcat service as and when require
On 27/10/2010 11:08, Pid wrote:
> On 26/10/2010 16:08, Marc Wilmots wrote:
>> Hi again.
>>
>> I checked out the executor element, although, I can't find a lot of
>> information about it.
>> Would you mind explaining why using the executor element would fix the
>> problem I am having?
>
> The Execu
On 26/10/2010 16:08, Marc Wilmots wrote:
> Hi again.
>
> I checked out the executor element, although, I can't find a lot of
> information about it.
> Would you mind explaining why using the executor element would fix the
> problem I am having?
The Executor will reduce the size of the thread pool
On 27/10/2010 06:43, Ivan wrote:
> Hi,
> While calling the method destory() on the StandardContext directly, it
> seems that the method destoryInternal() is called twice in the
> LifecycleMBeanBase, the two stacktraces are below :
> a. LifecycleMBeanBase.unregister(ObjectName) line: 191
>
Thanks a lot Mladen, I really appreciate your help.
About the AJP leaving connections open; If you hadn't @apache.org in
your email address I wouldn't believe you ;)
2010/10/26, Mladen Turk :
> On 10/26/2010 08:36 PM, Marc Wilmots wrote:
>>
>> 1200> 1000, thus your theory is probably right.
>
> :
Hi,
I have installed Apache tomcat 5.0.28 in windows vista business
edition.I am using one application which is working only on this tomcat
version.Now I need to give access for restricted windows vista user to
restart tomcat service as and when require.Please guide me to do it.
28 matches
Mail list logo