Re: mod_jk release plan

[Jean-frederic Clere]

Rainer Jung wrote:


Hi,

I would like to start releasing mod_jk 1.2.16 this week.

Since our last release was done from CVS and there are several updates 
to the tool chain (autoconf/automake/m4/libtool), there is some risk 
of breaking the release (additionally to mod_jk code bugs).
For that reason I would propose to tag as 1.2.16-rc1, because we might 
need to have a second try on releasing it.


So I would propose, that I will

- take the role as RM for mod_jk 1.2.16
- tag mod_jk soon as 1.2.16-rc1
- roll a tarball and inform the dev- and user-list about availability 
of a release candidate and invite to test it.

- in case of negative testing: fix, retag as rc2, reroll etc.
- after positive testing start the vote
- after positive voting copy the final rc-tag to 1.2.16 and reroll the 
final release containing the right version numbers.

- finally announce the official release

Any comments?


Great +1

Cheers

Jean-Frederic



Rainer


-
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]

DO NOT REPLY [Bug 39909] - Tomcat as Windows service issues http error 404

[bugzilla]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=39909


[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|RESOLVED|REOPENED
 Resolution|DUPLICATE   |




--- Additional Comments From [EMAIL PROTECTED]  2006-06-28 07:56 ---
This defect report is flagged as RESOLVED.  Can someone please let me know what
the resolution is as I am stuck with the symptoms of this fault.


Regards
Alan Lewis

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.

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

svn commit: r417694 - /tomcat/connectors/trunk/jk/xdocs/config/workers.xml

[rjung]

Author: rjung
Date: Wed Jun 28 01:04:34 2006
New Revision: 417694

URL: http://svn.apache.org/viewvc?rev=417694&view=rev
Log:
Fix typo.

Modified:
tomcat/connectors/trunk/jk/xdocs/config/workers.xml

Modified: tomcat/connectors/trunk/jk/xdocs/config/workers.xml
URL: 
http://svn.apache.org/viewvc/tomcat/connectors/trunk/jk/xdocs/config/workers.xml?rev=417694&r1=417693&r2=417694&view=diff
==
--- tomcat/connectors/trunk/jk/xdocs/config/workers.xml (original)
+++ tomcat/connectors/trunk/jk/xdocs/config/workers.xml Wed Jun 28 01:04:34 2006
@@ -389,7 +389,7 @@
 between the webserver and tomcat will be closed if the client connection
 to the webserver is terminated during the request/response cycle. This allows
 to inform the servlet engine about broken client connections during lengthy 
operations.
-This features has been added in jk 1.2.16
+This feature has been added in jk 1.2.16
 
 
 



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

svn commit: r417697 - in /tomcat/connectors/trunk/jk/tools/reports: tomcat_reports.pl tomcat_trend.pl

[rjung]

Author: rjung
Date: Wed Jun 28 01:27:04 2006
New Revision: 417697

URL: http://svn.apache.org/viewvc?rev=417697&view=rev
Log:
Replace obsolete CVS keyword "Header" by "Id", drop redundant keywords.

Modified:
tomcat/connectors/trunk/jk/tools/reports/tomcat_reports.pl
tomcat/connectors/trunk/jk/tools/reports/tomcat_trend.pl

Modified: tomcat/connectors/trunk/jk/tools/reports/tomcat_reports.pl
URL: 
http://svn.apache.org/viewvc/tomcat/connectors/trunk/jk/tools/reports/tomcat_reports.pl?rev=417697&r1=417696&r2=417697&view=diff
==
--- tomcat/connectors/trunk/jk/tools/reports/tomcat_reports.pl (original)
+++ tomcat/connectors/trunk/jk/tools/reports/tomcat_reports.pl Wed Jun 28 
01:27:04 2006
@@ -16,9 +16,7 @@
 # limitations under the License.
 #
 
-# $Header$
-# $Revision$
-# $Date$
+# $Id$
 
 # Author: Glenn Nielsen
 

Modified: tomcat/connectors/trunk/jk/tools/reports/tomcat_trend.pl
URL: 
http://svn.apache.org/viewvc/tomcat/connectors/trunk/jk/tools/reports/tomcat_trend.pl?rev=417697&r1=417696&r2=417697&view=diff
==
--- tomcat/connectors/trunk/jk/tools/reports/tomcat_trend.pl (original)
+++ tomcat/connectors/trunk/jk/tools/reports/tomcat_trend.pl Wed Jun 28 
01:27:04 2006
@@ -16,9 +16,7 @@
 # limitations under the License.
 #
 
-# $Header$
-# $Revision$
-# $Date$
+# $Id$
 
 # Author:  Glenn Nielsen
 



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

Renaming jakarta-tomcat-connectors to tomcat-connectors?

[Rainer Jung]

I think it's time to rename jakarta-tomcat-connectors to 
tomcat-connectors. I'll try to handle the remaining jakarta-tomcat 
artefacts inside the connectors module and concerning the download.


Does anyone know about external references we might break?

Rainer

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

Re: Renaming jakarta-tomcat-connectors to tomcat-connectors?

[Henri Gomez]

It make sense.

+0

2006/6/28, Rainer Jung <[EMAIL PROTECTED]>:

I think it's time to rename jakarta-tomcat-connectors to
tomcat-connectors. I'll try to handle the remaining jakarta-tomcat
artefacts inside the connectors module and concerning the download.

Does anyone know about external references we might break?

Rainer

-
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]

RE: New Feature List

[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: Renaming jakarta-tomcat-connectors to tomcat-connectors?

[Jean-frederic Clere]

Rainer Jung wrote:

I think it's time to rename jakarta-tomcat-connectors to 
tomcat-connectors. I'll try to handle the remaining jakarta-tomcat 
artefacts inside the connectors module and concerning the download.


Does anyone know about external references we might break?


The web pages (connectors) are still telling "jakarta-bla..."  that also 
needs fixing.


Cheers

Jean-Frederic



Rainer

-
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]

DO NOT REPLY [Bug 36204] - Webapp unable to pick the Class by the shared classloader

[bugzilla]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=36204





--- Additional Comments From [EMAIL PROTECTED]  2006-06-28 10:36 ---
I just upgrade Tomcat to 5.5.17 and bug still exist
in previous my post I wrote was OS winXP, but real OS is Win2k

IMHO this bug exist because I'm using JRE, not JDK 


-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.

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

Re: Renaming jakarta-tomcat-connectors to tomcat-connectors?

[Rainer Jung]

That's part of what I'll be doing.

Jean-frederic Clere schrieb:

Rainer Jung wrote:

I think it's time to rename jakarta-tomcat-connectors to 
tomcat-connectors. I'll try to handle the remaining jakarta-tomcat 
artefacts inside the connectors module and concerning the download.


Does anyone know about external references we might break?


The web pages (connectors) are still telling "jakarta-bla..."  that also 
needs fixing.


Cheers

Jean-Frederic



Rainer


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

Re: Renaming jakarta-tomcat-connectors to tomcat-connectors?

[Yoav Shapira]

+1 to renaming.

Yoav

On 6/28/06, Rainer Jung <[EMAIL PROTECTED]> wrote:

That's part of what I'll be doing.

Jean-frederic Clere schrieb:
> Rainer Jung wrote:
>
>> I think it's time to rename jakarta-tomcat-connectors to
>> tomcat-connectors. I'll try to handle the remaining jakarta-tomcat
>> artefacts inside the connectors module and concerning the download.
>>
>> Does anyone know about external references we might break?
>
> The web pages (connectors) are still telling "jakarta-bla..."  that also
> needs fixing.
>
> Cheers
>
> Jean-Frederic
>
>>
>> Rainer

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





--
Yoav Shapira
Nimalex LLC
1 Mifflin Place, Suite 310
Cambridge, MA, USA
[EMAIL PROTECTED] / www.yoavshapira.com

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

Re: New Feature List

[Filip Hanik - Dev Lists]

Definitely not by design :)
I'll take a look at it

Filip

Yong Gou wrote:
> 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]

Re: New Feature List

[Remy Maucherat]

Filip Hanik - Dev Lists wrote:
> Definitely not by design :)

That's good to know :)

Rémy

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

DO NOT REPLY [Bug 39919] New: - Slow startup when replication enabled

[bugzilla]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=39919

   Summary: Slow startup when replication enabled
   Product: Tomcat 5
   Version: 5.5.17
  Platform: Other
OS/Version: other
Status: NEW
  Severity: normal
  Priority: P2
 Component: Catalina:Cluster
AssignedTo: tomcat-dev@jakarta.apache.org
ReportedBy: [EMAIL PROTECTED]


The current behaviour when I have two nodes (A and B) on a cluster and both
start up at the same time seems somewhat less than ideal.

As Node A deploys context X it asks B for session data, B ignores this message
because it doesn't yet have context X active, and also asks A for session data
for X, which in turn A ignores.

A and B then sit there for (default) 60s waiting for a reply, then give up and
carry with the next context.

The net result is that it can take around 60s per webappp for a "cold" start.

I suspect that the thing to do is to reply to a request for All Session Data
with some sort of "not available here" message, rather than just ignore it
because its not one of my contexts.

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.

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

Re: Renaming jakarta-tomcat-connectors to tomcat-connectors?

[Costin Manolache]

And why are you doing this ?

For tomcat5 - I don't see how much it helps. For tomcat6+ - I think the
main issue is figuring where to put the native code so the duplicated
java source trees don't confuse people. Given how much unused native
we have, it may be good to just move mod_jk and whatever else is still
used to tomcat6/ repo.

Costin

On 6/28/06, Rainer Jung <[EMAIL PROTECTED]> wrote:


I think it's time to rename jakarta-tomcat-connectors to
tomcat-connectors. I'll try to handle the remaining jakarta-tomcat
artefacts inside the connectors module and concerning the download.

Does anyone know about external references we might break?

Rainer

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

Re: Renaming jakarta-tomcat-connectors to tomcat-connectors?

[Yoav Shapira]

Hi,

On 6/28/06, Costin Manolache <[EMAIL PROTECTED]> wrote:

And why are you doing this ?


Why are we doing the renaming?  Because the relevant project is no
longer part of Jakarta, so to avoid confusion among users, be
consistent with other Tomcat code, discharge the Jakarta PMC from
responsibility, etc.  Ideally we would have done this right after we
became a TLP, but better late then never.

Or did you mean something else other than the renaming by "this" in
the above question?

Yoav



For tomcat5 - I don't see how much it helps. For tomcat6+ - I think the
main issue is figuring where to put the native code so the duplicated
java source trees don't confuse people. Given how much unused native
we have, it may be good to just move mod_jk and whatever else is still
used to tomcat6/ repo.

Costin

On 6/28/06, Rainer Jung <[EMAIL PROTECTED]> wrote:
>
> I think it's time to rename jakarta-tomcat-connectors to
> tomcat-connectors. I'll try to handle the remaining jakarta-tomcat
> artefacts inside the connectors module and concerning the download.
>
> Does anyone know about external references we might break?
>
> Rainer
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>





--
Yoav Shapira
Nimalex LLC
1 Mifflin Place, Suite 310
Cambridge, MA, USA
[EMAIL PROTECTED] / www.yoavshapira.com

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

Re: Renaming jakarta-tomcat-connectors to tomcat-connectors?

[Rainer Jung]

The reason to change names is the same, as it was during TC 5.5 
development, to reflect the TLP status of tomcat.


This will not be a change in java packages or svn directory names. The 
change will only be visible in documentation and it the name of the 
download file will change. In some parts of the documentation this 
already happened.


I think we should do it completely to keep names consistent with the 
tomcat naming.


I'm preparing a mod_jk release, which is independent of the TC version. 
It contains only the native parts (no change with that) so it's 
compatible with a wide range of tomcat versions.


After releasing I would also love to change repos structure to make 
deprecated code much more visible. More precisely: I would first like to 
build consensus on what parts are deprecated.


Rainer

Costin Manolache schrieb:

And why are you doing this ?

For tomcat5 - I don't see how much it helps. For tomcat6+ - I think the
main issue is figuring where to put the native code so the duplicated
java source trees don't confuse people. Given how much unused native
we have, it may be good to just move mod_jk and whatever else is still
used to tomcat6/ repo.

Costin

On 6/28/06, Rainer Jung <[EMAIL PROTECTED]> wrote:


I think it's time to rename jakarta-tomcat-connectors to
tomcat-connectors. I'll try to handle the remaining jakarta-tomcat
artefacts inside the connectors module and concerning the download.

Does anyone know about external references we might break?

Rainer

-
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]

Re: Renaming jakarta-tomcat-connectors to tomcat-connectors?

[Rainer Jung]

Rainer Jung schrieb:
After releasing I would also love to change repos structure to make 
deprecated code much more visible. More precisely: I would first like to 
build consensus on what parts are deprecated.


Sorry: I meant "to make the deprecation much more visible".

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

svn commit: r417883 - /tomcat/connectors/trunk/jni/native/BUILDING

[jfclere]

Author: jfclere
Date: Wed Jun 28 14:51:05 2006
New Revision: 417883

URL: http://svn.apache.org/viewvc?rev=417883&view=rev
Log:
Remove jakarta reference.

Modified:
tomcat/connectors/trunk/jni/native/BUILDING

Modified: tomcat/connectors/trunk/jni/native/BUILDING
URL: 
http://svn.apache.org/viewvc/tomcat/connectors/trunk/jni/native/BUILDING?rev=417883&r1=417882&r2=417883&view=diff
==
--- tomcat/connectors/trunk/jni/native/BUILDING (original)
+++ tomcat/connectors/trunk/jni/native/BUILDING Wed Jun 28 14:51:05 2006
@@ -17,7 +17,7 @@
   2 - In bin/setenv.sh add the following: 
 CATALINA_OPTS="$CATALINA_OPTS -Djava.library.path=tclib_location"
 In my machine I am using:
-/home/jfclere/jakarta-tomcat-connectors/jni/native/.libs for tclib_location
+/home/jfclere/tomcat-connectors/jni/native/.libs for tclib_location
 
 NOTES:
   - configure --without-ssl : Configure without ssl support.
@@ -28,4 +28,3 @@
   - For MAC OS X you must manually add a link
 cd ${tcnative installdir}
 ln -d libtcnative-1.dylib libtcnative-1.jnilib
-
\ No newline at end of file



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

DO NOT REPLY [Bug 39909] - Tomcat as Windows service issues http error 404

[bugzilla]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=39909


[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|REOPENED|RESOLVED
 Resolution||DUPLICATE




--- Additional Comments From [EMAIL PROTECTED]  2006-06-28 22:57 ---
Please read the comments on the duplicate bug report you filed for this issue.
It looks like a configuration issue rather than a bug and Bugzilla is not the
right forum to resolve configuration issues.

*** This bug has been marked as a duplicate of 39787 ***

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.

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

DO NOT REPLY [Bug 39787] - Tomcat 5.5.16 cannot serve pages (http status404) on Windows Server 2003

[bugzilla]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=39787





--- Additional Comments From [EMAIL PROTECTED]  2006-06-28 22:57 ---
*** Bug 39909 has been marked as a duplicate of this bug. ***

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.

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

svn commit: r417896 - /tomcat/connectors/trunk/jni/jnirelease.sh

[jfclere]

Author: jfclere
Date: Wed Jun 28 16:09:32 2006
New Revision: 417896

URL: http://svn.apache.org/viewvc?rev=417896&view=rev
Log:
Arrange it to update svn

Modified:
tomcat/connectors/trunk/jni/jnirelease.sh

Modified: tomcat/connectors/trunk/jni/jnirelease.sh
URL: 
http://svn.apache.org/viewvc/tomcat/connectors/trunk/jni/jnirelease.sh?rev=417896&r1=417895&r2=417896&view=diff
==
--- tomcat/connectors/trunk/jni/jnirelease.sh (original)
+++ tomcat/connectors/trunk/jni/jnirelease.sh Wed Jun 28 16:09:32 2006
@@ -14,28 +14,25 @@
 # See the License for the specific language governing permissions and
 # limitations under the License.
 #
-# Replace JKJNITAG with real tag, like TOMCAT_NATIVE_1_1_0
-JKJNITAG=HEAD
-# Replace JKJNIEXT with tagged version number, like 1.1.0
-JKJNIEXT="current"
-JKJNIVER="-${JKJNIEXT}"
-JKJNICVST=jakarta-tomcat-connectors
-export CVSROOT=:pserver:[EMAIL PROTECTED]:/home/cvspublic
-JKJNIDIST=tomcat-native${JKJNIVER}
+# Replace JKJNIEXT with branche/or tag
+#  and JKJNIVER by the version like -1.1.0
+JKJNIEXT="trunk"
+JKJNIVER="-dev"
+SVNBASE=https://svn.apache.org/repos/asf/tomcat/connectors/
+JKJNIDIST=tomcat-connectors${JKJNIVER}
 rm -rf ${JKJNIDIST}
-rm -f ${JKJNIDIST}.*
-cvs export -N -r $JKJNITAG jakarta-tomcat-connectors/KEYS
-cvs export -N -r $JKJNITAG jakarta-tomcat-connectors/LICENSE
-cvs export -N -r $JKJNITAG jakarta-tomcat-connectors/NOTICE
-cvs export -N -r $JKJNITAG jakarta-tomcat-connectors/jni/NOTICE.txt
-cvs export -N -r $JKJNITAG jakarta-tomcat-connectors/jni/README.txt
-cvs export -N -r $JKJNITAG jakarta-tomcat-connectors/jni/native
-mv ${JKJNICVST} ${JKJNIDIST}
+mkdir -p ${JKJNIDIST}/jni
+svn export $SVNBASE/${JKJNIEXT}/jni/native ${JKJNIDIST}/jni/native
+svn cat $SVNBASE/${JKJNIEXT}/KEYS > ${JKJNIDIST}/KEYS
+svn cat $SVNBASE/${JKJNIEXT}/LICENSE > ${JKJNIDIST}/LICENSE
+svn cat $SVNBASE/${JKJNIEXT}/NOTICE > ${JKJNIDIST}/NOTICE
+svn cat $SVNBASE/${JKJNIEXT}/jni/NOTICE.txt > ${JKJNIDIST}/NOTICE.txt
+svn cat $SVNBASE/${JKJNIEXT}/jni/README.txt > ${JKJNIDIST}/README.txt
 
 # Prebuild
 cd ${JKJNIDIST}/jni/native
 # Adjust the location of APR sources
-./buildconf --with-apr=../../../srclib/apr
+./buildconf --with-apr=$HOME/apr
 cd ../../../
 # Create distribution
 tar cvf ${JKJNIDIST}.tar ${JKJNIDIST}



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

svn commit: r417898 - /tomcat/connectors/trunk/jni/jnirelease.sh

[jfclere]

Author: jfclere
Date: Wed Jun 28 16:16:24 2006
New Revision: 417898

URL: http://svn.apache.org/viewvc?rev=417898&view=rev
Log:
Arrange apr location.

Modified:
tomcat/connectors/trunk/jni/jnirelease.sh

Modified: tomcat/connectors/trunk/jni/jnirelease.sh
URL: 
http://svn.apache.org/viewvc/tomcat/connectors/trunk/jni/jnirelease.sh?rev=417898&r1=417897&r2=417898&view=diff
==
--- tomcat/connectors/trunk/jni/jnirelease.sh (original)
+++ tomcat/connectors/trunk/jni/jnirelease.sh Wed Jun 28 16:16:24 2006
@@ -14,6 +14,9 @@
 # See the License for the specific language governing permissions and
 # limitations under the License.
 #
+# APRDIR have to be the location of the APR sources
+APRDIR=$HOME/apr
+#
 # Replace JKJNIEXT with branche/or tag
 #  and JKJNIVER by the version like -1.1.0
 JKJNIEXT="trunk"
@@ -32,11 +35,11 @@
 # Prebuild
 cd ${JKJNIDIST}/jni/native
 # Adjust the location of APR sources
-./buildconf --with-apr=$HOME/apr
+./buildconf --with-apr=$APRDIR
 cd ../../../
 # Create distribution
 tar cvf ${JKJNIDIST}.tar ${JKJNIDIST}
 gzip ${JKJNIDIST}.tar
 # Convert lineends to DOS
-perl srclib/apr/build/lineends.pl --cr ${JKJNIDIST}
+perl $APRDIR/build/lineends.pl --cr ${JKJNIDIST}
 zip -9 -r  ${JKJNIDIST}.zip ${JKJNIDIST}



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

Re: Renaming jakarta-tomcat-connectors to tomcat-connectors?

[Costin Manolache]

"Jakarta Tomcat" was used in many contexts, and I don't see why a user
would be confused - or care or know what a TLP is. That's internal
apache organization.

My point is - it would be better to stop using jakarta for future, and not
change the
past. Tomcat5 was released as 'jakarta tomcat', and it's more or less
history - we
make sort of maintainance releases.

For tomcat6 and other future releases - we can stop using jakarta.

Costin

On 6/28/06, Yoav Shapira <[EMAIL PROTECTED]> wrote:


Hi,

On 6/28/06, Costin Manolache <[EMAIL PROTECTED]> wrote:
> And why are you doing this ?

Why are we doing the renaming?  Because the relevant project is no
longer part of Jakarta, so to avoid confusion among users, be
consistent with other Tomcat code, discharge the Jakarta PMC from
responsibility, etc.  Ideally we would have done this right after we
became a TLP, but better late then never.

Or did you mean something else other than the renaming by "this" in
the above question?

Yoav

>
> For tomcat5 - I don't see how much it helps. For tomcat6+ - I think the
> main issue is figuring where to put the native code so the duplicated
> java source trees don't confuse people. Given how much unused native
> we have, it may be good to just move mod_jk and whatever else is still
> used to tomcat6/ repo.
>
> Costin
>
> On 6/28/06, Rainer Jung <[EMAIL PROTECTED]> wrote:
> >
> > I think it's time to rename jakarta-tomcat-connectors to
> > tomcat-connectors. I'll try to handle the remaining jakarta-tomcat
> > artefacts inside the connectors module and concerning the download.
> >
> > Does anyone know about external references we might break?
> >
> > Rainer
> >
> > -
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
>
>


--
Yoav Shapira
Nimalex LLC
1 Mifflin Place, Suite 310
Cambridge, MA, USA
[EMAIL PROTECTED] / www.yoavshapira.com