RE: New Feature List

2006-06-28 Thread Yong Gou
Hi, Filip,

When I used full fledged Tomcat 5.5.15 (i.e. standard edition) in an OSGi 
environment, I found the thread pool of the ReplicationListener was not be 
destroyed when I stopped Tomcat. So after I stopped and restarted Tomcat for a 
few times, the accumulated number of undestroyed threads would increase 
accordingly. This resulted in serious memory leak in case of needing stopping 
and restarting Tomcat in succession in a JVM within its single lifecycle. 

So I read the code of ReplicationListener.java and tried to figure out what is 
the problem. I saw there is a start method which instantiates a ThreadPool 
instance but seems no matched stop method provided to destroy the created 
instance. I am wondering is this a negligence or by design for some reasons?

In addition, a few other threads such as "Cluster-MembershipReceiver", 
"http--Processor***" and "TP-Processor*" were also not able to be destroyed 
in my case.

I know with normal Tomcat usage, this might not be a problem since Tomcat 
stopping/restarting implies JVM stopping/restarting, all threads and memory 
will get recycled after JVM has stopped. But this is indeed a problem in my 
case.


Thanks,
Eric



-Original Message-
From: Filip Hanik - Dev Lists [mailto:[EMAIL PROTECTED] 
Sent: 2006年6月23日 22:02
To: Tomcat Developers List
Subject: Re: New Feature List

Look at the "Get Involved" section of Tomcat's home page

http://tomcat.apache.org/getinvolved.html

Yoav Shapira wrote:
> Riyaz,
> New contributors are always welcome.
>
> A decent place to start looking for work are the open issues for
> Tomcat in Bugzilla.  You will see a number marked as Enhancement
> Requests, and a number whose solution is not trivial at all.  Work on
> whatever interests you...
>
> Yoav
>
> On 6/23/06, Riyaz Mansoor <[EMAIL PROTECTED]> wrote:
>>
>> i'll keep it brief.
>>
>> i'm looking to spend time on working on the new features coming to
>> tomcat 5.5 or 6
>>
>> on the website, i could find no info on this. i was hoping there would
>> be a page listing the features being worked in 5.5 and the coming
>> features in 6
>>
>> riyaz
>>
>> -
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
>
>


-- 


Filip Hanik

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



___
Notice:  This email message, together with any attachments, may contain
information  of  BEA Systems,  Inc.,  its subsidiaries  and  affiliated
entities,  that may be confidential,  proprietary,  copyrighted  and/or
legally privileged, and is intended solely for the use of the individual
or entity named in this message. If you are not the intended recipient,
and have received this message in error, please immediately return this
by email and then delete it.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



RE: truncated server.xml got when storing config on condition that more than one vitual host with same application base directory "webapps" were defined.

2006-02-14 Thread Yong Gou
Hi George,

Has the issue you mentioned been fixed? If it has, how could I get this fix?

Thanks,
Eric

-Original Message-
From: George Sexton [mailto:[EMAIL PROTECTED] 
Sent: 2006年1月27日 0:29
To: 'Tomcat Developers List'
Subject: RE: truncated server.xml got when storing config on condition that 
more than one vitual host with same application base directory "webapps" were 
defined.

If you have the tomcat service running as LocalSystem, then there should be
no permission issues.

Looking through your post again, I think the issue is the same as mine,
you're just getting there differently. I think that its failing on the write
of the context.xml, as in my case because the other app didn't correctly
free the resource (close the file, whatever). The scenario I'm guessing at
is:

Host A Saves but doesn't close all files
Host B tries to save but can't because Host A's files were'nt correctly
closed.


George Sexton
MH Software, Inc.
http://www.mhsoftware.com/
Voice: 303 438 9585
  

> -Original Message-
> From: Yong Gou [mailto:[EMAIL PROTECTED] 
> Sent: Wednesday, January 25, 2006 9:41 PM
> To: Tomcat Developers List
> Subject: RE: truncated server.xml got when storing config on 
> condition that more than one vitual host with same 
> application base directory "webapps" were defined.
> 
> yes. I checked each webapps/app/META-INF directory, each of 
> these directory has a lot of backup files named like 
> context.xml.2005-11-28.19-02-56. These files were created 
> when Tomcat server was running. and also I think there should 
> be no write permission related issues since my Tomcat server 
> was running on Windows XP. so I am not sure if this is same 
> as your case.
> 
> Thanks,
> Eric
> 
> -Original Message-
> From: George Sexton [mailto:[EMAIL PROTECTED] 
> Sent: 2006年1月19日 0:27
> To: 'Tomcat Developers List'
> Subject: RE: truncated server.xml got when storing config on 
> condition that more than one vitual host with same 
> application base directory "webapps" were defined.
> 
> I didn't notice. Did you follow my advice to check write 
> permissions on all of the webapps directories.
> 
> As reported, if the tomcat user cannot write to each webapp 
> (or at least the webapp/META-INF directory), then creation of 
> the server.xml will fail in the manner you describe.
> 
> George Sexton
> MH Software, Inc.
> http://www.mhsoftware.com/
> Voice: 303 438 9585
>   
> 
> > -Original Message-
> > From: Yong Gou [mailto:[EMAIL PROTECTED]
> > Sent: Tuesday, January 17, 2006 8:47 PM
> > To: Tomcat Developers List
> > Subject: RE: truncated server.xml got when storing config 
> on condition 
> > that more than one vitual host with same application base directory 
> > "webapps" were defined.
> > 
> > Hi Peter,
> > 
> > I downloaded the 5.5.15 beta from Apache Tomcat downloads page and 
> > installed it on my desktop. But I found the same issue was 
> still there 
> > with this version when I used its admin console webapp to add a new 
> > host and store config to the server.xml. The following is the 
> > resultant server.xml.
> > 
> >   > port="6005">
> >> className="org.apache.catalina.core.AprLifecycleListener"/>
> >> className="org.apache.catalina.mbeans.GlobalResourcesLifecycle
> > Listener"/>
> >> className="org.apache.catalina.storeconfig.StoreConfigLifecycl
> > eListener"/>
> >> className="org.apache.catalina.mbeans.ServerLifecycleListener"/>
> >   
> >  >   name="simpleValue"
> >   type="java.lang.Integer"
> >   value="30"/>
> >  >   auth="Container"
> >   description="User database that can be updated and saved"
> >   name="UserDatabase"
> >   type="org.apache.catalina.UserDatabase"
> >   pathname="conf/tomcat-users.xml"
> >   
> factory="org.apache.catalina.users.MemoryUserDatabaseFactory"/>
> >   
> >>   name="Catalina">
> >  > port="6080"
> > redirectPort="6443"
> > minSpareThreads="25"
> > connectionTimeout="6"
> > connectionLinger="-1"
> > serverSoTimeout="0"
> > maxSpareThreads="75"
> > maxThreads="150"
> > tcpNoDelay="true"
> > maxHtt

RE: truncated server.xml got when storing config on condition that more than one vitual host with same application base directory "webapps" were defined.

2006-01-25 Thread Yong Gou
yes. I checked each webapps/app/META-INF directory, each of these directory has 
a lot of backup files named like context.xml.2005-11-28.19-02-56. These files 
were created when Tomcat server was running. and also I think there should be 
no write permission related issues since my Tomcat server was running on 
Windows XP. so I am not sure if this is same as your case.

Thanks,
Eric

-Original Message-
From: George Sexton [mailto:[EMAIL PROTECTED] 
Sent: 2006年1月19日 0:27
To: 'Tomcat Developers List'
Subject: RE: truncated server.xml got when storing config on condition that 
more than one vitual host with same application base directory "webapps" were 
defined.

I didn't notice. Did you follow my advice to check write permissions on all of 
the webapps directories.

As reported, if the tomcat user cannot write to each webapp (or at least the 
webapp/META-INF directory), then creation of the server.xml will fail in the 
manner you describe.

George Sexton
MH Software, Inc.
http://www.mhsoftware.com/
Voice: 303 438 9585
  

> -Original Message-
> From: Yong Gou [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, January 17, 2006 8:47 PM
> To: Tomcat Developers List
> Subject: RE: truncated server.xml got when storing config on condition 
> that more than one vitual host with same application base directory 
> "webapps" were defined.
> 
> Hi Peter,
> 
> I downloaded the 5.5.15 beta from Apache Tomcat downloads page and 
> installed it on my desktop. But I found the same issue was still there 
> with this version when I used its admin console webapp to add a new 
> host and store config to the server.xml. The following is the 
> resultant server.xml.
> 
>   port="6005">
>className="org.apache.catalina.core.AprLifecycleListener"/>
>className="org.apache.catalina.mbeans.GlobalResourcesLifecycle
> Listener"/>
>className="org.apache.catalina.storeconfig.StoreConfigLifecycl
> eListener"/>
>className="org.apache.catalina.mbeans.ServerLifecycleListener"/>
>   
>name="simpleValue"
>   type="java.lang.Integer"
>   value="30"/>
>auth="Container"
>   description="User database that can be updated and saved"
>   name="UserDatabase"
>   type="org.apache.catalina.UserDatabase"
>   pathname="conf/tomcat-users.xml"
>   factory="org.apache.catalina.users.MemoryUserDatabaseFactory"/>
>   
>  name="Catalina">
>  port="6080"
> redirectPort="6443"
> minSpareThreads="25"
> connectionTimeout="6"
> connectionLinger="-1"
> serverSoTimeout="0"
> maxSpareThreads="75"
> maxThreads="150"
> tcpNoDelay="true"
> maxHttpHeaderSize="8192">
> 
>  port="6009"
> redirectPort="6443"
> protocol="AJP/1.3">
> 
>  defaultHost="localhost"
> name="Catalina">
>   
>  appBase="webapps"
>   name="localhost">
>   
>  appBase="webapps"
>   name="gyvh">
> 
> 
> Thanks,
> Eric
> 
> 
> 
> -Original Message-
> From: Peter Rossbach [mailto:[EMAIL PROTECTED]
> Sent: 2006年1月16日 18:30
> To: Tomcat Developers List
> Subject: Re: truncated server.xml got when storing config on condition 
> that more than one vitual host with same application base directory 
> "webapps" were defined.
> 
> It storeconfig server.xml saving after add a new host works for me!
> 
> I have tested with current svn head.
> 
> create host with fixed MBean descriptor from MBeanFactory (Thanks for
> this)
> and store server.xml with mbean StoreConfig.storeConfig().
> 
> Regards
> Peter
> 
> My saved server.xml looks like this:
> 
>port="8010"
>  shutdown="8010">
> className="org.apache.catalina.mbeans.GlobalResourcesLifecycle
> Listener"/
>  >
> className="org.apache.catalina.storeconfig.StoreConfigLifecycl
> eListener" 
> />
> className="org.apache.catalina.mbeans.ServerLifecycleListener"/>
>
>  auth="Container"
>description="User database that can be updated and saved"
>name="UserDatabase"
>type="org.apache.

RE: truncated server.xml got when storing config on condition that more than one vitual host with same application base directory "webapps" were defined.

2006-01-17 Thread Yong Gou
Hi Peter,

I downloaded the 5.5.15 beta from Apache Tomcat downloads page and installed it 
on my desktop. But I found the same issue was still there with this version 
when I used its admin console webapp to add a new host and store config to the 
server.xml. The following is the resultant server.xml.



  
  
  
  
  


  
  





  
  
  
  


Thanks,
Eric



-Original Message-
From: Peter Rossbach [mailto:[EMAIL PROTECTED] 
Sent: 2006年1月16日 18:30
To: Tomcat Developers List
Subject: Re: truncated server.xml got when storing config on condition that 
more than one vitual host with same application base directory "webapps" were 
defined.

It storeconfig server.xml saving after add a new host works for me!

I have tested with current svn head.

create host with fixed MBean descriptor from MBeanFactory (Thanks for  
this)
and store server.xml with mbean StoreConfig.storeConfig().

Regards
Peter

My saved server.xml looks like this:



   
   
   
   
 
   
   
 
 
 
 
 
   
   
   
   
   
 
   


Am 16.01.2006 um 11:03 schrieb Yong Gou:

> Hi Peter,
>
> There were just some info, no severe exception was thrown. You can  
> try it in your environment.
>
> Thanks,
> Eric
>
>
> -Original Message-
> From: Peter Rossbach [mailto:[EMAIL PROTECTED]
> Sent: 2006年1月16日 17:39
> To: Tomcat Developers List
> Subject: Re: truncated server.xml got when storing config on  
> condition that more than one vitual host with same application base  
> directory "webapps" were defined.
>
> Hey,
>
> see you any exception inside your log?
>
> Regards
> peter
>
>
> Am 16.01.2006 um 09:29 schrieb Yong Gou:
>
>> The version of Tomcat server is 5.5.12
>>
>> -Original Message-
>> From: Yong Gou
>> Sent: 2006年1月16日 16:24
>> To: dev@tomcat.apache.org
>> Subject: truncated server.xml got when storing config on condition
>> that more than one vitual host with same application base directory
>> "webapps" were defined.
>>
>> Hi,
>>
>>
>>
>> I am not sure if the following is an issue of Tomcat JMX server or an
>> improper usage? Is there anyone who has experienced the same?
>>
>> In addition to the virtual host localhost which is predefined by
>> Tomcat
>> server as the default on a Tomcat server, I created another virtual
>> host
>> testvh on the server with its attribute appBase being specified as
>> webapps and other attributes having their default values via Tomcat
>> admin console webapp, and then clicked the "commit changes" button to
>> save all configurations to the server's server.xml file. The
>> operations
>> resulted in the following server.xml.
>>
>> NOTE that the Host, Engine, Service and Server elements are not
>> closed.
>> This is an incomplete server.xml. However if I specified another  
>> value
>> other than webapps for its attribute appBase when the virtual host
>> testvh was created, the issue would disappear and I could get a
>> correct
>> server.xml. You can try to define more virtual hosts with the same
>> appBase webapps if two cannot reproduce the issue.
>>
>>
>>
>> 
>>
>> >
>> port="9005">
>>
>>   > className="org.apache.catalina.core.AprLifecycleListener"/>
>>
>>   > className="org.apache.catalina.mbeans.GlobalResourcesLifecycleListene 
>> r
>> "/
>>>
>>
>>   > className="org.apache.catalina.storeconfig.StoreConfigLifecycleListen 
>> e
>> r"
>> />
>>
>>   > className="org.apache.catalina.mbeans.ServerLifecycleListener"/>
>>
>>   
>>
>> >
>>   name="simpleValue"
>>
>>   type="java.lang.Integer"
>>
>>   value="30"/>
>>
>> >
>>   auth="Container"
>>
>>   description="User database that can be updated and saved"
>>
>>   name="UserDatabase"
>>
>>   type="org.apache.catalina.UserDatabase"
>>
>>   pathname="conf/tomcat-users.xml"
>>
>>   factory="org.apache.catalina.users.MemoryUserDatabaseFactory"/>
>>
>>   
>>
>>   >
>>   name="Catalina">
>>
>> >
>> port="9080"
>>
>> redirectPort="9443"
>>
>> minSpareThreads="25"
>>
>>

RE: truncated server.xml got when storing config on condition that more than one vitual host with same application base directory "webapps" were defined.

2006-01-16 Thread Yong Gou
Hi Peter,

There were just some info, no severe exception was thrown. You can try it in 
your environment.

Thanks,
Eric


-Original Message-
From: Peter Rossbach [mailto:[EMAIL PROTECTED] 
Sent: 2006年1月16日 17:39
To: Tomcat Developers List
Subject: Re: truncated server.xml got when storing config on condition that 
more than one vitual host with same application base directory "webapps" were 
defined.

Hey,

see you any exception inside your log?

Regards
peter


Am 16.01.2006 um 09:29 schrieb Yong Gou:

> The version of Tomcat server is 5.5.12
>
> -Original Message-----
> From: Yong Gou
> Sent: 2006年1月16日 16:24
> To: dev@tomcat.apache.org
> Subject: truncated server.xml got when storing config on condition  
> that more than one vitual host with same application base directory  
> "webapps" were defined.
>
> Hi,
>
>
>
> I am not sure if the following is an issue of Tomcat JMX server or an
> improper usage? Is there anyone who has experienced the same?
>
> In addition to the virtual host localhost which is predefined by  
> Tomcat
> server as the default on a Tomcat server, I created another virtual  
> host
> testvh on the server with its attribute appBase being specified as
> webapps and other attributes having their default values via Tomcat
> admin console webapp, and then clicked the "commit changes" button to
> save all configurations to the server's server.xml file. The  
> operations
> resulted in the following server.xml.
>
> NOTE that the Host, Engine, Service and Server elements are not  
> closed.
> This is an incomplete server.xml. However if I specified another value
> other than webapps for its attribute appBase when the virtual host
> testvh was created, the issue would disappear and I could get a  
> correct
> server.xml. You can try to define more virtual hosts with the same
> appBase webapps if two cannot reproduce the issue.
>
>
>
> 
>
> 
> port="9005">
>
>className="org.apache.catalina.core.AprLifecycleListener"/>
>
>className="org.apache.catalina.mbeans.GlobalResourcesLifecycleListener 
> "/
>>
>
>className="org.apache.catalina.storeconfig.StoreConfigLifecycleListene 
> r"
> />
>
>className="org.apache.catalina.mbeans.ServerLifecycleListener"/>
>
>   
>
> 
>   name="simpleValue"
>
>   type="java.lang.Integer"
>
>   value="30"/>
>
> 
>   auth="Container"
>
>   description="User database that can be updated and saved"
>
>   name="UserDatabase"
>
>   type="org.apache.catalina.UserDatabase"
>
>   pathname="conf/tomcat-users.xml"
>
>   factory="org.apache.catalina.users.MemoryUserDatabaseFactory"/>
>
>   
>
>   
>   name="Catalina">
>
> 
> port="9080"
>
> redirectPort="9443"
>
> minSpareThreads="25"
>
> connectionTimeout="2"
>
> maxThreads="150"
>
> maxSpareThreads="75"
>
> maxHttpHeaderSize="8192">
>
> 
>
> 
> port="9009"
>
> redirectPort="9443"
>
> protocol="AJP/1.3">
>
> 
>
> 
> defaultHost="localhost"
>
> name="Catalina">
>
>   
>
>   
>   appBase="webapps"
>
>   name="testvh">
>
> 
> path="/TomcatLogHelper">
>
>
> d:\javadev\apache\tomcat2\conf\context.xml WatchedReso
> urce>
>
> 
>
>   
>
>   
>   appBase="webapps"
>
>   name="localhost">
>
> gy
>
> 
> path="/TomcatLogHelper">
>
>
> d:\javadev\apache\tomcat2\conf\context.xml WatchedReso
> urce>
>
> 
>
>
>
> Thanks,
>
> Eric
>
>
>
>
>
>
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



FW: truncated server.xml got when storing config on condition that more than one vitual host with same application base directory "webapps" were defined.

2006-01-16 Thread Yong Gou
The version of Tomcat server is 5.5.12

-Original Message-
From: Yong Gou 
Sent: 2006年1月16日 16:24
To: dev@tomcat.apache.org
Subject: truncated server.xml got when storing config on condition that more 
than one vitual host with same application base directory "webapps" were 
defined.

Hi,

 

I am not sure if the following is an issue of Tomcat JMX server or an
improper usage? Is there anyone who has experienced the same?

In addition to the virtual host localhost which is predefined by Tomcat
server as the default on a Tomcat server, I created another virtual host
testvh on the server with its attribute appBase being specified as
webapps and other attributes having their default values via Tomcat
admin console webapp, and then clicked the "commit changes" button to
save all configurations to the server's server.xml file. The operations
resulted in the following server.xml. 

NOTE that the Host, Engine, Service and Server elements are not closed.
This is an incomplete server.xml. However if I specified another value
other than webapps for its attribute appBase when the virtual host
testvh was created, the issue would disappear and I could get a correct
server.xml. You can try to define more virtual hosts with the same
appBase webapps if two cannot reproduce the issue.

 





  

  

  

  

  





  

  











  

  



 
d:\javadev\apache\tomcat2\conf\context.xml



  

  

gy



 
d:\javadev\apache\tomcat2\conf\context.xml



 

Thanks,

Eric

 

 




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



truncated server.xml got when storing config on condition that more than one vitual host with same application base directory "webapps" were defined.

2006-01-16 Thread Yong Gou
Hi,

 

I am not sure if the following is an issue of Tomcat JMX server or an
improper usage? Is there anyone who has experienced the same?

In addition to the virtual host localhost which is predefined by Tomcat
server as the default on a Tomcat server, I created another virtual host
testvh on the server with its attribute appBase being specified as
webapps and other attributes having their default values via Tomcat
admin console webapp, and then clicked the "commit changes" button to
save all configurations to the server's server.xml file. The operations
resulted in the following server.xml. 

NOTE that the Host, Engine, Service and Server elements are not closed.
This is an incomplete server.xml. However if I specified another value
other than webapps for its attribute appBase when the virtual host
testvh was created, the issue would disappear and I could get a correct
server.xml. You can try to define more virtual hosts with the same
appBase webapps if two cannot reproduce the issue.

 





  

  

  

  

  





  

  











  

  



 
d:\javadev\apache\tomcat2\conf\context.xml



  

  

gy



 
d:\javadev\apache\tomcat2\conf\context.xml



 

Thanks,

Eric

 

 



cannot get correct attributes and operations from the Data Source mbean created through jconsole GUI

2006-01-15 Thread Yong Gou
Hi,

 

Can anyone who has experienced the following problem tell me how to
solve it when creating DataSource mbean on the JMX server of Tomcat
server 5.5.12?

The problem I encountered can be described like this: I used JDK1.5's
jconsole utility to connect to my Tomcat server, after it was connected
I invoked the method void addResource("ds_123", "javax.sql.DataSource")
on the mbean "Catalina:type=NamingResources,resourcetype=Global" to add
a DataSource mbean to the JMX server. This operation should have created
a "Catalina:type=DataSource,class=javax.sql.DataSource,name="ds_123""
mbean with attributes such as username, password, url and with methods
like getConnection, close. But actually the created mbean which only has
attributes like factoryClassName, factoryClassLocation, className and
has methods like remove clear and clone was quite different than the
correct mbean I expected. But with Tomcat admin console webapp, I could
create the DataSource mbean I expected correctly. In my understanding,
these two methods should generate the same result but the truth was not.
I checked some related source code of tomcat admin console webapp such
as SaveDataSourceAction.java but didn't find any clue to get the correct
answer.

Acutally I got the same result like what I got using jconsole when I
invoked method void addResource("ds_123", "javax.sql.DataSource") on the
mbean "Catalina:type=NamingResources,resourcetype=Global" in a java
program. How can I create a DataSource mbean with the correct attributes
and methods like the mbean created using Tomcat admin console webapp.

 

Thank you in advance!

 

Eric