Re: tomcat native documentation

[jean-frederic clere]

Costin Manolache wrote:

Yes, JVM is not so good because it changes, I agree /usr/local/lib ( and the
JVM dir ) are only good for people with root access.

What about having 2 options:
- 'system' installation - /usr/local/lib
- 'local' - TOMCAT_HOME/lib/native ( or TOMCAT_HOME/lib/`arch` if same
install is shared on multiple machine types )

We can include both in catalina.sh ( is /usr/lib, /usr/local/lib enabled by
default for finding .so ?),


/usr/lib yes, /usr/local/lib not (at least not in all OS).

 so user can save one step and

we can have more consistent instructions. Also a binary package that install
on top of TOMCAT_HOME would be easier.


So you would add the LD_LIBRARY_PATH to the TOMCAT_HOME/lib/native ( or 
better TOMCAT_HOME/lib/`arch`) in the catalina.sh (PATH for the .bat).




The fewer steps and variations - the easier will it be to build and support.



Costin

On 2/12/08, Henri Gomez <[EMAIL PROTECTED]> wrote:

In this case, should it be installed in the directory of the JVM
installation? I think MINA uses it too.

JVM directory may be problematic for those of us who switch between
JVM, ie IBM or Sun.

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

svn commit: r627689 - /tomcat/trunk/java/org/apache/catalina/session/ManagerBase.java

[fhanik]

Author: fhanik
Date: Thu Feb 14 01:55:23 2008
New Revision: 627689

URL: http://svn.apache.org/viewvc?rev=627689&view=rev
Log:
fix NPE
java.lang.NullPointerException at 
org.apache.catalina.session.ManagerBase.processExpires(ManagerBase.java:682)
at 
org.apache.catalina.session.ManagerBase.backgroundProcess(ManagerBase.java:667)
at 
org.apache.catalina.core.ContainerBase.backgroundProcess(ContainerBase.java:1316)
at 
org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(ContainerBase.java:1601)
at 
org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(ContainerBase.java:1610)
at 
org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(ContainerBase.java:1610)
at 
org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.run(ContainerBase.java:1590)
at java.lang.Thread.run(Thread.java:619)

Modified:
tomcat/trunk/java/org/apache/catalina/session/ManagerBase.java

Modified: tomcat/trunk/java/org/apache/catalina/session/ManagerBase.java
URL: 
http://svn.apache.org/viewvc/tomcat/trunk/java/org/apache/catalina/session/ManagerBase.java?rev=627689&r1=627688&r2=627689&view=diff
==
--- tomcat/trunk/java/org/apache/catalina/session/ManagerBase.java (original)
+++ tomcat/trunk/java/org/apache/catalina/session/ManagerBase.java Thu Feb 14 
01:55:23 2008
@@ -679,7 +679,7 @@
 if(log.isDebugEnabled())
 log.debug("Start expire sessions " + getName() + " at " + timeNow 
+ " sessioncount " + sessions.length);
 for (int i = 0; i < sessions.length; i++) {
-if (!sessions[i].isValid()) {
+if (sessions[i]!=null && !sessions[i].isValid()) {
 expireHere++;
 }
 }



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

svn commit: r627693 - /tomcat/tc6.0.x/trunk/STATUS.txt

[fhanik]

Author: fhanik
Date: Thu Feb 14 02:01:48 2008
New Revision: 627693

URL: http://svn.apache.org/viewvc?rev=627693&view=rev
Log:
new proposal and vote

Modified:
tomcat/tc6.0.x/trunk/STATUS.txt

Modified: tomcat/tc6.0.x/trunk/STATUS.txt
URL: 
http://svn.apache.org/viewvc/tomcat/tc6.0.x/trunk/STATUS.txt?rev=627693&r1=627692&r2=627693&view=diff
==
--- tomcat/tc6.0.x/trunk/STATUS.txt (original)
+++ tomcat/tc6.0.x/trunk/STATUS.txt Thu Feb 14 02:01:48 2008
@@ -97,4 +97,10 @@
 * lib is relative to catalina home, not base
   http://svn.apache.org/viewvc?rev=627602&view=rev
   +1: markt
+  -1: fhanik - lib should be relative to catalina.home
+
+* Fix NPE when iterating through sessions for expiration
+  http://svn.apache.org/viewvc?view=rev&revision=627689
+  +1: fhanik
   -1:
+  



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

svn commit: r627695 - /tomcat/tc6.0.x/trunk/STATUS.txt

[fhanik]

Author: fhanik
Date: Thu Feb 14 02:04:18 2008
New Revision: 627695

URL: http://svn.apache.org/viewvc?rev=627695&view=rev
Log:
I'm an idiot, put on my head backwards this morning :)

Modified:
tomcat/tc6.0.x/trunk/STATUS.txt

Modified: tomcat/tc6.0.x/trunk/STATUS.txt
URL: 
http://svn.apache.org/viewvc/tomcat/tc6.0.x/trunk/STATUS.txt?rev=627695&r1=627694&r2=627695&view=diff
==
--- tomcat/tc6.0.x/trunk/STATUS.txt (original)
+++ tomcat/tc6.0.x/trunk/STATUS.txt Thu Feb 14 02:04:18 2008
@@ -96,8 +96,8 @@
 
 * lib is relative to catalina home, not base
   http://svn.apache.org/viewvc?rev=627602&view=rev
-  +1: markt
-  -1: fhanik - lib should be relative to catalina.home
+  +1: markt, fhanik
+  -1: 
 
 * Fix NPE when iterating through sessions for expiration
   http://svn.apache.org/viewvc?view=rev&revision=627689



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

DO NOT REPLY [Bug 44405] - regression with tomcat 6.0.16, NullPointerException on getServletContext().getResourceAsStream()

[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=44405





--- Additional Comments From [EMAIL PROTECTED]  2008-02-14 05:10 ---
I know it doesn't work, I am just saying the check for / should have been added
only in strict compliance mode to avoid this "regression".

-- 
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 43925] - org.apache.jasper.runtime.BodyContentImpl causing huge memory allocations

[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=43925





--- Additional Comments From [EMAIL PROTECTED]  2008-02-14 05:35 ---
About the upper memory bound, I had missed the clear method. I thought the
original purpose was to keep the list of buffers around, now it looks to me the
memory usage is equivalent to the LIMIT_BUFFER mode.

-- 
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: r627743 - in /tomcat/trunk: java/org/apache/catalina/core/ApplicationContext.java java/org/apache/tomcat/util/http/ServerCookie.java webapps/docs/config/systemprops.xml

[fhanik]

Author: fhanik
Date: Thu Feb 14 05:59:00 2008
New Revision: 627743

URL: http://svn.apache.org/viewvc?rev=627743&view=rev
Log:
Add STRICT compliance flag to impact cookie value handling to provide backwards 
compatibility
Add STRICT complanice flag to impact ServletContext.getResource(AsStream) to be 
backwards compatible

Modified:
tomcat/trunk/java/org/apache/catalina/core/ApplicationContext.java
tomcat/trunk/java/org/apache/tomcat/util/http/ServerCookie.java
tomcat/trunk/webapps/docs/config/systemprops.xml

Modified: tomcat/trunk/java/org/apache/catalina/core/ApplicationContext.java
URL: 
http://svn.apache.org/viewvc/tomcat/trunk/java/org/apache/catalina/core/ApplicationContext.java?rev=627743&r1=627742&r2=627743&view=diff
==
--- tomcat/trunk/java/org/apache/catalina/core/ApplicationContext.java 
(original)
+++ tomcat/trunk/java/org/apache/catalina/core/ApplicationContext.java Thu Feb 
14 05:59:00 2008
@@ -52,6 +52,7 @@
 import org.apache.tomcat.util.buf.CharChunk;
 import org.apache.tomcat.util.buf.MessageBytes;
 import org.apache.tomcat.util.http.mapper.MappingData;
+import org.apache.catalina.Globals;
 
 
 /**
@@ -453,9 +454,12 @@
 public URL getResource(String path)
 throws MalformedURLException {
 
-if (path == null || !path.startsWith("/")) {
+if (path == null)
 throw new 
MalformedURLException(sm.getString("applicationContext.requestDispatcher.iae", 
path));
-}
+
+if (!path.startsWith("/") && Globals.STRICT_SERVLET_COMPLIANCE)
+throw new 
MalformedURLException(sm.getString("applicationContext.requestDispatcher.iae", 
path));
+
 
 path = normalize(path);
 if (path == null)
@@ -507,9 +511,12 @@
 public InputStream getResourceAsStream(String path) {
 
 path = normalize(path);
-if (path == null || !path.startsWith("/"))
+if (path == null)
 return (null);
 
+if (!path.startsWith("/") && Globals.STRICT_SERVLET_COMPLIANCE)
+return null;
+
 DirContext resources = context.getResources();
 if (resources != null) {
 try {

Modified: tomcat/trunk/java/org/apache/tomcat/util/http/ServerCookie.java
URL: 
http://svn.apache.org/viewvc/tomcat/trunk/java/org/apache/tomcat/util/http/ServerCookie.java?rev=627743&r1=627742&r2=627743&view=diff
==
--- tomcat/trunk/java/org/apache/tomcat/util/http/ServerCookie.java (original)
+++ tomcat/trunk/java/org/apache/tomcat/util/http/ServerCookie.java Thu Feb 14 
05:59:00 2008
@@ -51,6 +51,8 @@
 private int maxAge = -1;
 private int version = 0;
 
+protected static boolean switchToV1Cookies = 
!Boolean.valueOf(System.getProperty("org.apache.catalina.STRICT_SERVLET_COMPLIANCE",
 "false")).booleanValue();
+
 // Note: Servlet Spec =< 2.5 only refers to Netscape and RFC2109,
 // not RFC2965
 
@@ -248,7 +250,7 @@
 buf.append("=");
 // Servlet implementation does not check anything else
 
-maybeQuote2(version, buf, value);
+version = maybeQuote2(version, buf, value);
 
 // Add version 1 specific information
 if (version == 1) {
@@ -329,7 +331,7 @@
  * @param buf
  * @param value
  */
-public static void maybeQuote2 (int version, StringBuffer buf, String 
value) {
+public static int maybeQuote2 (int version, StringBuffer buf, String 
value) {
 if (value==null || value.length()==0) {
 buf.append("\"\"");
 }else if (containsCTL(value,version)) 
@@ -338,6 +340,11 @@
 buf.append('"');
 buf.append(escapeDoubleQuotes(value,1,value.length()-1));
 buf.append('"');
+} else if (switchToV1Cookies && version==0 && !isToken2(value)) {
+buf.append('"');
+buf.append(escapeDoubleQuotes(value,0,value.length()));
+buf.append('"');
+version = 1;
 } else if (version==0 && !isToken(value)) {
 buf.append('"');
 buf.append(escapeDoubleQuotes(value,0,value.length()));
@@ -349,6 +356,7 @@
 }else {
 buf.append(value);
 }
+return version;
 }
 
 

Modified: tomcat/trunk/webapps/docs/config/systemprops.xml
URL: 
http://svn.apache.org/viewvc/tomcat/trunk/webapps/docs/config/systemprops.xml?rev=627743&r1=627742&r2=627743&view=diff
==
--- tomcat/trunk/webapps/docs/config/systemprops.xml (original)
+++ tomcat/trunk/webapps/docs/config/systemprops.xml Thu Feb 14 05:59:00 2008
@@ -34,6 +34,7 @@
 
 
 
+
 
   
 
@@ -194,6 +195,15 @@
   every request that is associated with a session will cause the
   session's last accessed time to be updated regardless of whether or not
   the request explicity accesses the

svn commit: r627744 - /tomcat/tc6.0.x/trunk/STATUS.txt

[fhanik]

Author: fhanik
Date: Thu Feb 14 06:01:15 2008
New Revision: 627744

URL: http://svn.apache.org/viewvc?rev=627744&view=rev
Log:
regression proposals

Modified:
tomcat/tc6.0.x/trunk/STATUS.txt

Modified: tomcat/tc6.0.x/trunk/STATUS.txt
URL: 
http://svn.apache.org/viewvc/tomcat/tc6.0.x/trunk/STATUS.txt?rev=627744&r1=627743&r2=627744&view=diff
==
--- tomcat/tc6.0.x/trunk/STATUS.txt (original)
+++ tomcat/tc6.0.x/trunk/STATUS.txt Thu Feb 14 06:01:15 2008
@@ -104,3 +104,13 @@
   +1: fhanik
   -1:
   
+* Allow old style cookie values to work(auto switch to v1) (regression)
+  http://svn.apache.org/viewvc?view=rev&revision=627743 (ServerCookie.java)
+  +1: fhanik
+  -1: 
+  
+* Allow ServletContext.getResource("noslash/resource") (regression)
+  http://svn.apache.org/viewvc?view=rev&revision=627743 
(ApplicationContext.java)
+  +1: fhanik
+  -1: 
+



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

svn commit: r627745 - in /tomcat/tc6.0.x/trunk: STATUS.txt java/org/apache/coyote/http11/InternalNioOutputBuffer.java

[fhanik]

Author: fhanik
Date: Thu Feb 14 06:03:10 2008
New Revision: 627745

URL: http://svn.apache.org/viewvc?rev=627745&view=rev
Log:
implement fix

Modified:
tomcat/tc6.0.x/trunk/STATUS.txt

tomcat/tc6.0.x/trunk/java/org/apache/coyote/http11/InternalNioOutputBuffer.java

Modified: tomcat/tc6.0.x/trunk/STATUS.txt
URL: 
http://svn.apache.org/viewvc/tomcat/tc6.0.x/trunk/STATUS.txt?rev=627745&r1=627744&r2=627745&view=diff
==
--- tomcat/tc6.0.x/trunk/STATUS.txt (original)
+++ tomcat/tc6.0.x/trunk/STATUS.txt Thu Feb 14 06:03:10 2008
@@ -76,11 +76,6 @@
   +1: markt
   -1:
 
-* Handle case of NIO/SSL when transferring bytes to a disconnected socket
-  http://svn.apache.org/viewvc?rev=618420&view=rev
-  +1: fhanik, markt, pero
-  -1: 
-  
 * Use a single lock for synchronized session manipulation
   http://svn.apache.org/viewvc?rev=618823&view=rev
   +1: fhanik, markt, pero

Modified: 
tomcat/tc6.0.x/trunk/java/org/apache/coyote/http11/InternalNioOutputBuffer.java
URL: 
http://svn.apache.org/viewvc/tomcat/tc6.0.x/trunk/java/org/apache/coyote/http11/InternalNioOutputBuffer.java?rev=627745&r1=627744&r2=627745&view=diff
==
--- 
tomcat/tc6.0.x/trunk/java/org/apache/coyote/http11/InternalNioOutputBuffer.java 
(original)
+++ 
tomcat/tc6.0.x/trunk/java/org/apache/coyote/http11/InternalNioOutputBuffer.java 
Thu Feb 14 06:03:10 2008
@@ -794,7 +794,7 @@
 byte[] b = chunk.getBuffer();
 while (len > 0) {
 int thisTime = len;
-if (socket.getBufHandler().getWriteBuffer().position() == 
socket.getBufHandler().getWriteBuffer().capacity()) {
+if (socket.getBufHandler().getWriteBuffer().position() == 
socket.getBufHandler().getWriteBuffer().capacity() 
||socket.getBufHandler().getWriteBuffer().remaining()==0) {
 flushBuffer();
 }
 if (thisTime > 
socket.getBufHandler().getWriteBuffer().remaining()) {



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

svn commit: r627747 - in /tomcat/tc6.0.x/trunk: STATUS.txt java/org/apache/catalina/ha/session/DeltaManager.java java/org/apache/catalina/ha/session/DeltaRequest.java java/org/apache/catalina/ha/sessi

[fhanik]

Author: fhanik
Date: Thu Feb 14 06:04:10 2008
New Revision: 627747

URL: http://svn.apache.org/viewvc?rev=627747&view=rev
Log:
Fix dead lock during round robin non sticky lb

Modified:
tomcat/tc6.0.x/trunk/STATUS.txt
tomcat/tc6.0.x/trunk/java/org/apache/catalina/ha/session/DeltaManager.java
tomcat/tc6.0.x/trunk/java/org/apache/catalina/ha/session/DeltaRequest.java
tomcat/tc6.0.x/trunk/java/org/apache/catalina/ha/session/DeltaSession.java

Modified: tomcat/tc6.0.x/trunk/STATUS.txt
URL: 
http://svn.apache.org/viewvc/tomcat/tc6.0.x/trunk/STATUS.txt?rev=627747&r1=627746&r2=627747&view=diff
==
--- tomcat/tc6.0.x/trunk/STATUS.txt (original)
+++ tomcat/tc6.0.x/trunk/STATUS.txt Thu Feb 14 06:04:10 2008
@@ -76,11 +76,6 @@
   +1: markt
   -1:
 
-* Use a single lock for synchronized session manipulation
-  http://svn.apache.org/viewvc?rev=618823&view=rev
-  +1: fhanik, markt, pero
-  -1: 
-
 * ExtendedAccessLogValve cs-uri not print empty querystring
   http://svn.apache.org/viewvc?rev=620778&view=rev
   +1: pero,funkman,markt

Modified: 
tomcat/tc6.0.x/trunk/java/org/apache/catalina/ha/session/DeltaManager.java
URL: 
http://svn.apache.org/viewvc/tomcat/tc6.0.x/trunk/java/org/apache/catalina/ha/session/DeltaManager.java?rev=627747&r1=627746&r2=627747&view=diff
==
--- tomcat/tc6.0.x/trunk/java/org/apache/catalina/ha/session/DeltaManager.java 
(original)
+++ tomcat/tc6.0.x/trunk/java/org/apache/catalina/ha/session/DeltaManager.java 
Thu Feb 14 06:04:10 2008
@@ -615,10 +615,15 @@
  * @throws IOException
  */
 protected DeltaRequest deserializeDeltaRequest(DeltaSession session, 
byte[] data) throws ClassNotFoundException, IOException {
-ReplicationStream ois = getReplicationStream(data);
-session.getDeltaRequest().readExternal(ois);
-ois.close();
-return session.getDeltaRequest();
+try {
+session.lock();
+ReplicationStream ois = getReplicationStream(data);
+session.getDeltaRequest().readExternal(ois);
+ois.close();
+return session.getDeltaRequest();
+}finally {
+session.unlock();
+}
 }
 
 /**
@@ -629,8 +634,13 @@
  * @return serialized delta request
  * @throws IOException
  */
-protected byte[] serializeDeltaRequest(DeltaRequest deltaRequest) throws 
IOException {
-return deltaRequest.serialize();
+protected byte[] serializeDeltaRequest(DeltaSession session, DeltaRequest 
deltaRequest) throws IOException {
+try {
+session.lock();
+return deltaRequest.serialize();
+}finally {
+session.unlock();
+}
 }
 
 /**
@@ -1096,16 +1106,18 @@
  * @return a SessionMessage to be sent,
  */
 public ClusterMessage requestCompleted(String sessionId) {
+DeltaSession session = null;
 try {
-DeltaSession session = (DeltaSession) findSession(sessionId);
+session = (DeltaSession) findSession(sessionId);
 DeltaRequest deltaRequest = session.getDeltaRequest();
+session.lock();
 SessionMessage msg = null;
 boolean isDeltaRequest = false ;
 synchronized(deltaRequest) {
 isDeltaRequest = deltaRequest.getSize() > 0 ;
 if (isDeltaRequest) {
 counterSend_EVT_SESSION_DELTA++;
-byte[] data = serializeDeltaRequest(deltaRequest);
+byte[] data = serializeDeltaRequest(session,deltaRequest);
 msg = new SessionMessageImpl(getName(),
  
SessionMessage.EVT_SESSION_DELTA, 
  data, 
@@ -1155,6 +1167,8 @@
 } catch (IOException x) {
 
log.error(sm.getString("deltaManager.createMessage.unableCreateDeltaRequest",sessionId),
 x);
 return null;
+}finally {
+if (session!=null) session.unlock();
 }
 
 }
@@ -1360,9 +1374,14 @@
 DeltaSession session = (DeltaSession) findSession(msg.getSessionID());
 if (session != null) {
 if (log.isDebugEnabled()) 
log.debug(sm.getString("deltaManager.receiveMessage.delta",getName(), 
msg.getSessionID()));
-DeltaRequest dreq = deserializeDeltaRequest(session, delta);
-dreq.execute(session, notifyListenersOnReplication);
-session.setPrimarySession(false);
+try {
+session.lock();
+DeltaRequest dreq = deserializeDeltaRequest(session, delta);
+dreq.execute(session, notifyListenersOnReplication);
+session.setPrimarySession(false);
+}finally {
+session.unlock();
+}
 }
 }

DO NOT REPLY [Bug 30624] - unable to load tiles-definition.war when running embedded tomcat

[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=30624





--- Additional Comments From [EMAIL PROTECTED]  2008-02-14 06:08 ---
We have seen this bug on 5.5.23

java.lang.NullPointerException
at 
org.apache.catalina.realm.RealmBase.findSecurityConstraints(RealmBase.java:501)
at
org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:426)

Please assert the necessity to reopen, or spin off a bug for the 5.5.x branch.
Thanks.


-- 
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: r627751 - /tomcat/tc6.0.x/trunk/webapps/docs/changelog.xml

[fhanik]

Author: fhanik
Date: Thu Feb 14 06:09:52 2008
New Revision: 627751

URL: http://svn.apache.org/viewvc?rev=627751&view=rev
Log:
changelog for last two commits

Modified:
tomcat/tc6.0.x/trunk/webapps/docs/changelog.xml

Modified: tomcat/tc6.0.x/trunk/webapps/docs/changelog.xml
URL: 
http://svn.apache.org/viewvc/tomcat/tc6.0.x/trunk/webapps/docs/changelog.xml?rev=627751&r1=627750&r2=627751&view=diff
==
--- tomcat/tc6.0.x/trunk/webapps/docs/changelog.xml (original)
+++ tomcat/tc6.0.x/trunk/webapps/docs/changelog.xml Thu Feb 14 06:09:52 2008
@@ -35,7 +35,23 @@
 
   
 
+  
 44337:   Dir listing crashes if no readme-file present 
(funkman)
+  
+
+  
+  
+
+ 
+Fix NIO/SSL live lock during client disconnect (fhanik)
+  
+
+  
+  
+
+ 
+Fix session replication dead lock during non sticky load balancing 
(fhanik)
+  
 
   
 



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

embedded tomcat 6

[Mark Webb]

I have written a program that embeds tomcat 6.0.14 into it.  The problem is
that once I call Embedded.start(), the program does not keep running and
just terminates normally.  I have placed the program in the eclipse debugger
and all looks fine, but the program just exits.

What can I do to ensure that the program stays running after the call to
Embedded.start()?  After the call, I place a Thread.sleep(Integer.MAX_VALUE)
and things are fine, but that just does not seem to be good practice.

Thanks in advance

-- 

Talent hits a target no one else can hit; Genius hits a target no one else
can see.

embedded tomcat 6

[Mark Webb]

I have written a program that embeds tomcat 6.0.14 into it.  The
problem is that once I call Embedded.start(), the program does not
keep running and just terminates normally.  I have placed the program
in the eclipse debugger and all looks fine, but the program just
exits.

What can I do to ensure that the program stays running after the call
to Embedded.start()?  After the call, I place a
Thread.sleep(Integer.MAX_VALUE) and things are fine, but that just
does not seem to be good practice.

Thanks in advance
Mark

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

Re: embedded tomcat 6

[Johnny Kewl]

---
HARBOR: http://coolharbor.100free.com/index.htm
The most powerful application server on earth.
The only real POJO Application Server.
Making the Java dream come true.
---
- Original Message - 
From: "Mark Webb" <[EMAIL PROTECTED]>

To: "dev" 
Sent: Thursday, February 14, 2008 4:59 PM
Subject: embedded tomcat 6



I have written a program that embeds tomcat 6.0.14 into it.  The
problem is that once I call Embedded.start(), the program does not
keep running and just terminates normally.  I have placed the program
in the eclipse debugger and all looks fine, but the program just
exits.

What can I do to ensure that the program stays running after the call
to Embedded.start()?  After the call, I place a
Thread.sleep(Integer.MAX_VALUE) and things are fine, but that just
does not seem to be good practice.


Mark, it a long long time since I did this stuff... but I vaguely remember 
the concept,

and more importantly how to figure it out...

Embedded has a function called
   public void setAwait(boolean b) {
   await = b;
   }


From your program... you start a thread, and in that thread you

call this function, and then load up your web-apps and stuff.

Tomcat will hold the deamon, until you release that flag then the thread 
falls thru.


It was something like that and you right, sleeping threads are not the way 
to go.


Then the way I figured this stuff out
Go get all the source code for the WHOLE tomcat...

and start at BOOTSTRAP... study that because all it really does is use
the digester to read all the XML config, and then it calls down into the 
same
embedded functions that you using... so if you follow that code you actually 
have

guru examples... and then you may even end up doing what we did...

We left the digester stuff in so when we develop an embedded app, we do 
it
in normal tomcat, then just copy the config files and the webapp to the 
app... done!


Hope that helps... have fun
I remember log files driving us mad... but I cant remember the details, I 
think we just removed that.




Thanks in advance
Mark

-
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: embedded tomcat 6

[Mark Webb]

Thanks for the information.  Looking at the code, it does not look
like the setAwait(boolean) does anything.  I ended up writing a test
GUI tool that will start/stop my embedded Tomcat.  From what I can
tell, the embedded tomcat API relies on the calling thread(s) to keep
things going b/c with the test GUI, the process stays running without
the use of a call to Thread.sleep( large value ).


On Thu, Feb 14, 2008 at 10:24 AM, Johnny Kewl <[EMAIL PROTECTED]> wrote:
>
>  ---
>  HARBOR: http://coolharbor.100free.com/index.htm
>  The most powerful application server on earth.
>  The only real POJO Application Server.
>  Making the Java dream come true.
>  ---
>
>
> - Original Message -
>  From: "Mark Webb" <[EMAIL PROTECTED]>
>  To: "dev" 
>  Sent: Thursday, February 14, 2008 4:59 PM
>  Subject: embedded tomcat 6
>
>
>  >I have written a program that embeds tomcat 6.0.14 into it.  The
>  > problem is that once I call Embedded.start(), the program does not
>  > keep running and just terminates normally.  I have placed the program
>  > in the eclipse debugger and all looks fine, but the program just
>  > exits.
>  >
>  > What can I do to ensure that the program stays running after the call
>  > to Embedded.start()?  After the call, I place a
>  > Thread.sleep(Integer.MAX_VALUE) and things are fine, but that just
>  > does not seem to be good practice.
>  
>  Mark, it a long long time since I did this stuff... but I vaguely remember
>  the concept,
>  and more importantly how to figure it out...
>
>  Embedded has a function called
> public void setAwait(boolean b) {
> await = b;
> }
>
>  From your program... you start a thread, and in that thread you
>  call this function, and then load up your web-apps and stuff.
>
>  Tomcat will hold the deamon, until you release that flag then the thread
>  falls thru.
>
>  It was something like that and you right, sleeping threads are not the way
>  to go.
>
>  Then the way I figured this stuff out
>  Go get all the source code for the WHOLE tomcat...
>
>  and start at BOOTSTRAP... study that because all it really does is use
>  the digester to read all the XML config, and then it calls down into the
>  same
>  embedded functions that you using... so if you follow that code you actually
>  have
>  guru examples... and then you may even end up doing what we did...
>
>  We left the digester stuff in so when we develop an embedded app, we do
>  it
>  in normal tomcat, then just copy the config files and the webapp to the
>  app... done!
>
>  Hope that helps... have fun
>  I remember log files driving us mad... but I cant remember the details, I
>  think we just removed that.
>
>  
>  > Thanks in advance
>  > Mark
>  >
>  > -
>  > 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]
>
>



-- 

Talent hits a target no one else can hit; Genius hits a target no one
else can see.

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

svn commit: r627884 - /tomcat/tc6.0.x/trunk/STATUS.txt

[markt]

Author: markt
Date: Thu Feb 14 14:05:32 2008
New Revision: 627884

URL: http://svn.apache.org/viewvc?rev=627884&view=rev
Log:
Propose fix

Modified:
tomcat/tc6.0.x/trunk/STATUS.txt

Modified: tomcat/tc6.0.x/trunk/STATUS.txt
URL: 
http://svn.apache.org/viewvc/tomcat/tc6.0.x/trunk/STATUS.txt?rev=627884&r1=627883&r2=627884&view=diff
==
--- tomcat/tc6.0.x/trunk/STATUS.txt (original)
+++ tomcat/tc6.0.x/trunk/STATUS.txt Thu Feb 14 14:05:32 2008
@@ -104,3 +104,7 @@
   +1: fhanik
   -1: 
 
+* Fix ArrayIndexOutOfBoundsException when empty URL is requested
+  http://svn.apache.org/viewvc?rev=627883&view=rev
+  +1: markt
+  -1:



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

svn commit: r627885 - /tomcat/current/tc5.5.x/STATUS.txt

[markt]

Author: markt
Date: Thu Feb 14 14:05:40 2008
New Revision: 627885

URL: http://svn.apache.org/viewvc?rev=627885&view=rev
Log:
Propose fix

Modified:
tomcat/current/tc5.5.x/STATUS.txt

Modified: tomcat/current/tc5.5.x/STATUS.txt
URL: 
http://svn.apache.org/viewvc/tomcat/current/tc5.5.x/STATUS.txt?rev=627885&r1=627884&r2=627885&view=diff
==
--- tomcat/current/tc5.5.x/STATUS.txt (original)
+++ tomcat/current/tc5.5.x/STATUS.txt Thu Feb 14 14:05:40 2008
@@ -36,3 +36,7 @@
   +1: pero
   -1: 
 
+* Fix ArrayIndexOutOfBoundsException when empty URL is requested
+  http://svn.apache.org/viewvc?rev=627883&view=rev
+  +1: markt
+  -1:



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

svn commit: r627883 - /tomcat/trunk/java/org/apache/catalina/connector/CoyoteAdapter.java

[markt]

Author: markt
Date: Thu Feb 14 14:02:41 2008
New Revision: 627883

URL: http://svn.apache.org/viewvc?rev=627883&view=rev
Log:
Fix ArrayIndexOutOfBoundsException reported on users list. Patch provided by 
Charles R Caldarale.

Modified:
tomcat/trunk/java/org/apache/catalina/connector/CoyoteAdapter.java

Modified: tomcat/trunk/java/org/apache/catalina/connector/CoyoteAdapter.java
URL: 
http://svn.apache.org/viewvc/tomcat/trunk/java/org/apache/catalina/connector/CoyoteAdapter.java?rev=627883&r1=627882&r2=627883&view=diff
==
--- tomcat/trunk/java/org/apache/catalina/connector/CoyoteAdapter.java 
(original)
+++ tomcat/trunk/java/org/apache/catalina/connector/CoyoteAdapter.java Thu Feb 
14 14:02:41 2008
@@ -682,6 +682,10 @@
 int start = uriBC.getStart();
 int end = uriBC.getEnd();
 
+// An empty URL is not acceptable
+if (start == end)
+return false;
+
 // URL * is acceptable
 if ((end - start == 1) && b[start] == (byte) '*')
   return true;



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

DO NOT REPLY [Bug 44423] New: - invalid duplicate listeners warning

[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=44423

   Summary: invalid duplicate listeners warning
   Product: Tomcat 6
   Version: unspecified
  Platform: Other
OS/Version: other
Status: NEW
  Severity: normal
  Priority: P2
 Component: Catalina
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]


Using a default tomcat 6.0.16, a new warning appeared in the logs:
INFO: The APR based Apache Tomcat Native library which allows optimal
performance in production environments was not found on the java.library.path:
/opt/sun-jdk-1.6.0.04/jre/lib/i386/client:/opt/sun-jdk-1.6.0.04/jre/lib/i386:/opt/sun-jdk-1.6.0.04/jre/../lib/i386:/usr/java/packages/lib/i386:/lib:/usr/lib
Feb 14, 2008 11:44:59 PM org.apache.coyote.http11.Http11Protocol init
INFO: Initializing Coyote HTTP/1.1 on http-8080
Feb 14, 2008 11:44:59 PM org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 1192 ms
Feb 14, 2008 11:44:59 PM org.apache.catalina.core.StandardService start
INFO: Starting service Catalina
Feb 14, 2008 11:44:59 PM org.apache.catalina.core.StandardEngine start
INFO: Starting Servlet Engine: Apache Tomcat/6.0.16
Feb 14, 2008 11:45:00 PM org.apache.catalina.core.StandardContext
addApplicationListener
INFO: The listener "listeners.ContextListener" is already configured for this
context. The duplicate definition has been ignored.
Feb 14, 2008 11:45:00 PM org.apache.catalina.core.StandardContext
addApplicationListener
INFO: The listener "listeners.SessionListener" is already configured for this
context. The duplicate definition has been ignored.
Feb 14, 2008 11:45:00 PM org.apache.coyote.http11.Http11Protocol start
INFO: Starting Coyote HTTP/1.1 on http-8080
Feb 14, 2008 11:45:00 PM org.apache.jk.common.ChannelSocket init
INFO: JK: ajp13 listening on /0.0.0.0:8009
Feb 14, 2008 11:45:00 PM org.apache.jk.server.JkMain start
INFO: Jk running ID=0 time=0/52  config=null
Feb 14, 2008 11:45:00 PM org.apache.catalina.startup.Catalina start
INFO: Server startup in 1208 ms

The application containing the listeners is the examples that are bundled with
tomcat.
As far as I can see, the listeners are not duplicated...

-- 
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 44423] - invalid duplicate listeners warning

[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=44423





--- Additional Comments From [EMAIL PROTECTED]  2008-02-14 13:55 ---
Trunk has already been patched and the patch proposed for 6.0.x. It will be
fixed in the next release.

-- 
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: r627887 - /tomcat/current/tc5.5.x/STATUS.txt

[markt]

Author: markt
Date: Thu Feb 14 14:12:38 2008
New Revision: 627887

URL: http://svn.apache.org/viewvc?rev=627887&view=rev
Log:
Vote

Modified:
tomcat/current/tc5.5.x/STATUS.txt

Modified: tomcat/current/tc5.5.x/STATUS.txt
URL: 
http://svn.apache.org/viewvc/tomcat/current/tc5.5.x/STATUS.txt?rev=627887&r1=627886&r2=627887&view=diff
==
--- tomcat/current/tc5.5.x/STATUS.txt (original)
+++ tomcat/current/tc5.5.x/STATUS.txt Thu Feb 14 14:12:38 2008
@@ -33,7 +33,7 @@
 
 * Remove duplicate listner additions (backport from 6.0 trunk)
   http://svn.apache.org/viewvc?rev=620844&view=rev
-  +1: pero
+  +1: pero, markt
   -1: 
 
 * Fix ArrayIndexOutOfBoundsException when empty URL is requested



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

svn commit: r627886 - /tomcat/tc6.0.x/trunk/STATUS.txt

[markt]

Author: markt
Date: Thu Feb 14 14:12:05 2008
New Revision: 627886

URL: http://svn.apache.org/viewvc?rev=627886&view=rev
Log:
votes

Modified:
tomcat/tc6.0.x/trunk/STATUS.txt

Modified: tomcat/tc6.0.x/trunk/STATUS.txt
URL: 
http://svn.apache.org/viewvc/tomcat/tc6.0.x/trunk/STATUS.txt?rev=627886&r1=627885&r2=627886&view=diff
==
--- tomcat/tc6.0.x/trunk/STATUS.txt (original)
+++ tomcat/tc6.0.x/trunk/STATUS.txt Thu Feb 14 14:12:05 2008
@@ -91,17 +91,17 @@
 
 * Fix NPE when iterating through sessions for expiration
   http://svn.apache.org/viewvc?view=rev&revision=627689
-  +1: fhanik
+  +1: fhanik, markt
   -1:
   
 * Allow old style cookie values to work(auto switch to v1) (regression)
   http://svn.apache.org/viewvc?view=rev&revision=627743 (ServerCookie.java)
-  +1: fhanik
+  +1: fhanik, markt
   -1: 
   
 * Allow ServletContext.getResource("noslash/resource") (regression)
   http://svn.apache.org/viewvc?view=rev&revision=627743 
(ApplicationContext.java)
-  +1: fhanik
+  +1: fhanik, markt
   -1: 
 
 * Fix ArrayIndexOutOfBoundsException when empty URL is requested



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

[Proposal] Remove status page from the docs

[Mark Thomas]

All,

Whilst working through a general update of the docs webapp (CATALINA_BASE 
vs. CATALINA_HOME, Tomcat 5 -> Tomcat 6, common/lib -> lib etc) I cam 
across this page.


http://tomcat.apache.org/tomcat-6.0-doc/status.html

It is horribly out of date and duplicates information that is elsewhere. My 
suggestion is that it is removed for the next 6.0.x release. I am leaning 
towards not replacing it with anything but if we wanted to we could point 
towards http://wiki.apache.org/tomcat/TomcatVersions - which needs some 
tidying up but does give a better idea of where we are.


Thoughts?

Mark

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

Re: [Proposal] Remove status page from the docs

[Yoav Shapira]

+1.

On Thu, Feb 14, 2008 at 6:43 PM, Mark Thomas <[EMAIL PROTECTED]> wrote:
> All,
>
>  Whilst working through a general update of the docs webapp (CATALINA_BASE
>  vs. CATALINA_HOME, Tomcat 5 -> Tomcat 6, common/lib -> lib etc) I cam
>  across this page.
>
>  http://tomcat.apache.org/tomcat-6.0-doc/status.html
>
>  It is horribly out of date and duplicates information that is elsewhere. My
>  suggestion is that it is removed for the next 6.0.x release. I am leaning
>  towards not replacing it with anything but if we wanted to we could point
>  towards http://wiki.apache.org/tomcat/TomcatVersions - which needs some
>  tidying up but does give a better idea of where we are.
>
>  Thoughts?
>
>  Mark
>
>  -
>  To unsubscribe, e-mail: [EMAIL PROTECTED]
>  For additional commands, e-mail: [EMAIL PROTECTED]
>
>



-- 
Thanks,

Yoav

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

svn commit: r627911 - in /tomcat/trunk: NOTES-FOR-TOMCAT-6.2.txt NOTES-FOR-TOMCAT-7.txt

[markt]

Author: markt
Date: Thu Feb 14 15:54:39 2008
New Revision: 627911

URL: http://svn.apache.org/viewvc?rev=627911&view=rev
Log:
Add a file to track possible 6.2 features so I can refer to it from the wiki.

Added:
tomcat/trunk/NOTES-FOR-TOMCAT-6.2.txt   (with props)
Modified:
tomcat/trunk/NOTES-FOR-TOMCAT-7.txt

Added: tomcat/trunk/NOTES-FOR-TOMCAT-6.2.txt
URL: 
http://svn.apache.org/viewvc/tomcat/trunk/NOTES-FOR-TOMCAT-6.2.txt?rev=627911&view=auto
==
--- tomcat/trunk/NOTES-FOR-TOMCAT-6.2.txt (added)
+++ tomcat/trunk/NOTES-FOR-TOMCAT-6.2.txt Thu Feb 14 15:54:39 2008
@@ -0,0 +1,24 @@
+
+  Licensed to the Apache Software Foundation (ASF) under one or more
+  contributor license agreements.  See the NOTICE file distributed with
+  this work for additional information regarding copyright ownership.
+  The ASF licenses this file to You under the Apache License, Version 2.0
+  (the "License"); you may not use this file except in compliance with
+  the License.  You may obtain a copy of the License at
+
+  http://www.apache.org/licenses/LICENSE-2.0
+
+  Unless required by applicable law or agreed to in writing, software
+  distributed under the License is distributed on an "AS IS" BASIS,
+  WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+  See the License for the specific language governing permissions and
+  limitations under the License.
+
+
+$Id: NOTES-FOR-TOMCAT-7.txt 607604 2007-12-30 22:41:20Z markt $
+
+==
+ Things to consider for inclusion in Tomcat 6.2.0
+==
+
+1. AnnotationProcessor -> InstanceManager replacement (used by Geronimo)

Propchange: tomcat/trunk/NOTES-FOR-TOMCAT-6.2.txt
--
svn:eol-style = native

Modified: tomcat/trunk/NOTES-FOR-TOMCAT-7.txt
URL: 
http://svn.apache.org/viewvc/tomcat/trunk/NOTES-FOR-TOMCAT-7.txt?rev=627911&r1=627910&r2=627911&view=diff
==
--- tomcat/trunk/NOTES-FOR-TOMCAT-7.txt (original)
+++ tomcat/trunk/NOTES-FOR-TOMCAT-7.txt Thu Feb 14 15:54:39 2008
@@ -21,5 +21,7 @@
 Things to refer to when planning / writing Tomcat 7
 ===
 
-1. Support for standalone EL
-   http://issues.apache.org/bugzilla/show_bug.cgi?id=43819
\ No newline at end of file
+1. Anything in NOTES-FOR-TOMCAT-6.2.txt that didn't make it into 6.2.x
+
+2. Support for standalone EL
+   http://issues.apache.org/bugzilla/show_bug.cgi?id=43819



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

[Tomcat Wiki] Update of "TomcatVersions" by markt

[Apache Wiki]

Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Tomcat Wiki" for change 
notification.

The following page has been changed by markt:
http://wiki.apache.org/tomcat/TomcatVersions

--
 * markt: Yes, if it is agreed to drop support for it
   * What level of support do we want to provide for 5.5.x?
 * markt: Bug fixes and security fixes, no enhancements
+ 
+ = Overview =
+ This page provides a high-level view of each of the past, current and planned 
major Tomcat versions.
-  * Once we have a stable release of 6.2.x, what support do we want to provide 
for 6.0.x?
-* markt: None. The API change is likely to be minor and impact zero to 
very few users. If it is an issue then we can change our minds and limit it to 
just security fixes.
-  * What features/API changes do we want to include in 6.2.x
-* remm: It could be limited to the AnnotationProcessor -> InstanceManager 
replacement, and have the branch simply take over for 6.0.x immediately. This 
also allows placing 6.0.x in security fixes mode since 6.2 is a trivial upgrade 
path.
-* markt: I'd go further and not do any updates for 6.0.x
-  * What features/API changes do we want to put in 6.3.x for future inclusion 
in 6.4.x and/or 7.0.x?
-* markt: That is what the STATUS file and voting is for ;)
  
  = Tomcat 3.3.x =
  ||Spec versions:||Servlet 2.2, JSP 1.1||
@@ -59, +55 @@

  
  = Tomcat 6.2.x =
  ||Spec versions:||Servlet 2.5, JSP 2.1||
- ||Stable:||Yes||
- ||Enhancements:||Yes||
- ||Bug Fixes:||Yes||
- ||Security Fixes:||Yes||
- ||Process:||RTC||
- ||Listed on download pages||Yes||
- ||Release Manager:||TBD||
  Features:
   * 6.0.x plus
-  * Geronimo API changes
-  * TBD
+  * http://svn.apache.org/repos/asf/tomcat/trunk/NOTES-FOR-TOMCAT-6.2.txt
+  * TBD - additional features will be added to the above file
  
- = Tomcat 6.3.x =
+ = Tomcat 7.0.x =
- ||Spec versions:||Servlet 2.5, JSP 2.1||
+ ||Spec versions:||Servlet 2.6?, JSP 2.2?||
- ||Stable:||No||
- ||Enhancements:||Yes||
- ||Bug Fixes:||Yes||
- ||Security Fixes:||Yes||
- ||Process:||CTR||
- ||Listed on download pages||Yes||
- ||Release Manager:||TBD||
- Features:
+ Features
-  * 6.2.x plus
+  * 6.x plus
-  * TBD
+  * http://svn.apache.org/repos/asf/tomcat/trunk/NOTES-FOR-TOMCAT-7.txt
+  * TBD - additional features will be added to the above file
  
  = Unsupported versions =
  The following versions are no longer supported. The source is still available 
from SVN and both source and binary downloads are available from the archives.

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

[PROPOSAL] Announce 3.x is no longer supported

[Mark Thomas]

All,

The last 3.x release was almost 4 years ago. Since then there has been one 
security patch made available in source form and that was more an 
application issue than a Tomcat one.


There is still the odd support question on the users list but I think it is 
time to draw a line under 3.x. In practice, this would mean:

- removing the download links for 3.x from tomcat.a.o
- removing 3.x from dist (it would remain in the archives)
- removing the 3.x docs from tomcat.a.o
- closing any open 3.x bugs as WONTFIX

Adding a note that 3.x is no longer supported / removing much of the 3.x 
info from:

/index.html
/security-3.html
/whichversion.html
/bugreport.html

Thoughts?

Mark

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

[PROPOSAL / POLL] Issue a de-support notice for Tomcat 4

[Mark Thomas]

All,

Tomcat 4 has been in maintenance mode for some time now with nearly all 
changes either updating libraries or fixing security bugs. I am happy to 
continue acting as release manager for as long as there are three +1s when 
there is a release.


However, there will come a time when it makes sense to cease supporting 
Tomcat 4.1.x. Rather than just announce it, as we did for 5.0.x, I think we 
should try and give our users some notice to encourage them to move off 
4.1.x and to give them time to plan the move.


Therefore, my proposal is that we issue a de-support notice for Tomcat 4.

The poll is what date we announce for the end of Tomcat 4 support. Around 
12 months notice seems reasonable to me so I am going to suggest 30 June 
2009. Do people think this is enough notice? Alternative suggestions welcome.


The web pages would also need the appropriate updates.

Thoughts?

Mark

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

Re: [PROPOSAL] Announce 3.x is no longer supported

[Filip Hanik - Dev Lists]

+1

Filip

Mark Thomas wrote:

All,

The last 3.x release was almost 4 years ago. Since then there has been 
one security patch made available in source form and that was more an 
application issue than a Tomcat one.


There is still the odd support question on the users list but I think 
it is time to draw a line under 3.x. In practice, this would mean:

- removing the download links for 3.x from tomcat.a.o
- removing 3.x from dist (it would remain in the archives)
- removing the 3.x docs from tomcat.a.o
- closing any open 3.x bugs as WONTFIX

Adding a note that 3.x is no longer supported / removing much of the 
3.x info from:

/index.html
/security-3.html
/whichversion.html
/bugreport.html

Thoughts?

Mark

-
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: svn commit: r627911 - in /tomcat/trunk: NOTES-FOR-TOMCAT-6.2.txt NOTES-FOR-TOMCAT-7.txt

[Filip Hanik - Dev Lists]

+1. AnnotationProcessor -> InstanceManager replacement (used by Geronimo)

  


this is already in trunk, is that what you meant?

Filip

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

Re: [PROPOSAL / POLL] Issue a de-support notice for Tomcat 4

[Filip Hanik - Dev Lists]

yes, a the timeframe of 16 months heads up sounds like a good plan. 
still many instances of 4 running,
another way to look at it, is to have no more than 3 versions active at 
any point, so when TC 7 comes out, TC 4 goes to bed. I think it's too 
hard for us to try to maintain more releases than that.


Filip

Mark Thomas wrote:

All,

Tomcat 4 has been in maintenance mode for some time now with nearly 
all changes either updating libraries or fixing security bugs. I am 
happy to continue acting as release manager for as long as there are 
three +1s when there is a release.


However, there will come a time when it makes sense to cease 
supporting Tomcat 4.1.x. Rather than just announce it, as we did for 
5.0.x, I think we should try and give our users some notice to 
encourage them to move off 4.1.x and to give them time to plan the move.


Therefore, my proposal is that we issue a de-support notice for Tomcat 4.

The poll is what date we announce for the end of Tomcat 4 support. 
Around 12 months notice seems reasonable to me so I am going to 
suggest 30 June 2009. Do people think this is enough notice? 
Alternative suggestions welcome.


The web pages would also need the appropriate updates.

Thoughts?

Mark

-
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: [VOTE] Release build 4.1.37

[Filip Hanik - Dev Lists]

According to the release process, the 4.1.37 tag is:
[ ] Broken
[ ] Alpha
[ ] Beta
[X] Stable



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

svn commit: r627921 - /tomcat/trunk/PROPOSALS.txt

[fhanik]

Author: fhanik
Date: Thu Feb 14 16:36:29 2008
New Revision: 627921

URL: http://svn.apache.org/viewvc?rev=627921&view=rev
Log:
one more feature

Modified:
tomcat/trunk/PROPOSALS.txt

Modified: tomcat/trunk/PROPOSALS.txt
URL: 
http://svn.apache.org/viewvc/tomcat/trunk/PROPOSALS.txt?rev=627921&r1=627920&r2=627921&view=diff
==
--- tomcat/trunk/PROPOSALS.txt (original)
+++ tomcat/trunk/PROPOSALS.txt Thu Feb 14 16:36:29 2008
@@ -45,7 +45,7 @@
  - support multicast fire and forget
  - autoswitch TCP/UDP based on size, number of recipients, or on message flag
  - add in versioning to the message structure
-
+ - Add in a delay between bind failures, to give the JVM a chance to recover
 Priority Messaging
  - Being able to send through high priority messages through a channel
pause existing messages



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

Re: [PROPOSAL] Announce 3.x is no longer supported

[Yoav Shapira]

On Thu, Feb 14, 2008 at 7:05 PM, Mark Thomas <[EMAIL PROTECTED]> wrote:
>  Adding a note that 3.x is no longer supported / removing much of the 3.x
>  info from:
>  /index.html
>  /security-3.html
>  /whichversion.html
>  /bugreport.html
>
>  Thoughts?

+1.

Yoav

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

Re: [Proposal] Remove status page from the docs

[Rainer Jung]

+1

Mark Thomas schrieb:

All,

Whilst working through a general update of the docs webapp 
(CATALINA_BASE vs. CATALINA_HOME, Tomcat 5 -> Tomcat 6, common/lib -> 
lib etc) I cam across this page.


http://tomcat.apache.org/tomcat-6.0-doc/status.html

It is horribly out of date and duplicates information that is elsewhere. 
My suggestion is that it is removed for the next 6.0.x release. I am 
leaning towards not replacing it with anything but if we wanted to we 
could point towards http://wiki.apache.org/tomcat/TomcatVersions - which 
needs some tidying up but does give a better idea of where we are.


Thoughts?

Mark


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

Re: [PROPOSAL / POLL] Issue a de-support notice for Tomcat 4

[Rainer Jung]

I agree with both of you.

Forgive me that I didn't check myself: I run into a 4.0.x release every 
now and then, especially bundled with some apps. Has 4.0 ever been put 
into end of live? I think EOL for 4.0 should be announced like for 3.x 
if this didn't happen anytime in the past.


Regards,

Rainer

Filip Hanik - Dev Lists schrieb:
yes, a the timeframe of 16 months heads up sounds like a good plan. 
still many instances of 4 running,
another way to look at it, is to have no more than 3 versions active at 
any point, so when TC 7 comes out, TC 4 goes to bed. I think it's too 
hard for us to try to maintain more releases than that.


Filip

Mark Thomas wrote:

All,

Tomcat 4 has been in maintenance mode for some time now with nearly 
all changes either updating libraries or fixing security bugs. I am 
happy to continue acting as release manager for as long as there are 
three +1s when there is a release.


However, there will come a time when it makes sense to cease 
supporting Tomcat 4.1.x. Rather than just announce it, as we did for 
5.0.x, I think we should try and give our users some notice to 
encourage them to move off 4.1.x and to give them time to plan the move.


Therefore, my proposal is that we issue a de-support notice for Tomcat 4.

The poll is what date we announce for the end of Tomcat 4 support. 
Around 12 months notice seems reasonable to me so I am going to 
suggest 30 June 2009. Do people think this is enough notice? 
Alternative suggestions welcome.


The web pages would also need the appropriate updates.

Thoughts?

Mark

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

Re: [PROPOSAL] Announce 3.x is no longer supported

[Rainer Jung]

+1

We could include the info about "no release for almost 4 years" in the 
official message, so that users understand that this is not a message of 
bad support in general.


Regards,

Rainer

Mark Thomas schrieb:

All,

The last 3.x release was almost 4 years ago. Since then there has been 
one security patch made available in source form and that was more an 
application issue than a Tomcat one.


There is still the odd support question on the users list but I think it 
is time to draw a line under 3.x. In practice, this would mean:

- removing the download links for 3.x from tomcat.a.o
- removing 3.x from dist (it would remain in the archives)
- removing the 3.x docs from tomcat.a.o
- closing any open 3.x bugs as WONTFIX

Adding a note that 3.x is no longer supported / removing much of the 3.x 
info from:

/index.html
/security-3.html
/whichversion.html
/bugreport.html

Thoughts?

Mark

-
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: [PROPOSAL] Announce 3.x is no longer supported

[Bill Barker]

"Mark Thomas" <[EMAIL PROTECTED]> wrote in message 
news:[EMAIL PROTECTED]
> All,
>
> The last 3.x release was almost 4 years ago. Since then there has been one 
> security patch made available in source form and that was more an 
> application issue than a Tomcat one.
>
> There is still the odd support question on the users list but I think it 
> is time to draw a line under 3.x. In practice, this would mean:
> - removing the download links for 3.x from tomcat.a.o
> - removing 3.x from dist (it would remain in the archives)
> - removing the 3.x docs from tomcat.a.o
> - closing any open 3.x bugs as WONTFIX
>
> Adding a note that 3.x is no longer supported / removing much of the 3.x 
> info from:
> /index.html
> /security-3.html
> /whichversion.html
> /bugreport.html
>
> Thoughts?
>

Well, the way Apache is structured, it is impossible to say that 3.x is no 
longer supported.  If three PMC members were to show an interest in 
expanding it in the future (say myself, Costin, Henri), then the rest would 
have a hard time blocking commits to that branch ;).  I would go for 
something like "The 3.x.x line is unlikely to have another release", instead 
of "not supported" as a result.  Especially since I plan to answer the 
occational 3.3 question on [EMAIL PROTECTED]

I think (but haven't checked) that I've closed all of the 3.3.x issues in 
bugzilla.  The remaining issues are against 3.2.x, which was dead five years 
ago.  Otherwise, I seriously doubt that I could get 3 PMC members to vote +1 
on any commit I might want to make to the 3.3.x branch, much less find 3 for 
a release.  So I'm going to give this [PROPOSAL] my +1.

> Mark 




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

Re: [PROPOSAL / POLL] Issue a de-support notice for Tomcat 4

[Bill Barker]

Since you are the only one maintaining this branch, I really can't vote 
against the [PROPOSAL] if you no longer want to continue supporting it.  +1

"Mark Thomas" <[EMAIL PROTECTED]> wrote in message 
news:[EMAIL PROTECTED]
> All,
>
> Tomcat 4 has been in maintenance mode for some time now with nearly all 
> changes either updating libraries or fixing security bugs. I am happy to 
> continue acting as release manager for as long as there are three +1s when 
> there is a release.
>
> However, there will come a time when it makes sense to cease supporting 
> Tomcat 4.1.x. Rather than just announce it, as we did for 5.0.x, I think 
> we should try and give our users some notice to encourage them to move off 
> 4.1.x and to give them time to plan the move.
>
> Therefore, my proposal is that we issue a de-support notice for Tomcat 4.
>
> The poll is what date we announce for the end of Tomcat 4 support. Around 
> 12 months notice seems reasonable to me so I am going to suggest 30 June 
> 2009. Do people think this is enough notice? Alternative suggestions 
> welcome.
>
> The web pages would also need the appropriate updates.
>
> Thoughts?
>
> Mark 




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

Re: [PROPOSAL] Announce 3.x is no longer supported

[Costin Manolache]

+1

4 years ago the last version, about 8 years ago the first (or 3.0)
release...
I wish we also had a '6.x-minimal' release for people wanting something very
small ( and not using jetty ).

Costin

On Thu, Feb 14, 2008 at 4:05 PM, Mark Thomas <[EMAIL PROTECTED]> wrote:

> All,
>
> The last 3.x release was almost 4 years ago. Since then there has been one
> security patch made available in source form and that was more an
> application issue than a Tomcat one.
>
> There is still the odd support question on the users list but I think it
> is
> time to draw a line under 3.x. In practice, this would mean:
> - removing the download links for 3.x from tomcat.a.o
> - removing 3.x from dist (it would remain in the archives)
> - removing the 3.x docs from tomcat.a.o
> - closing any open 3.x bugs as WONTFIX
>
> Adding a note that 3.x is no longer supported / removing much of the 3.x
> info from:
> /index.html
> /security-3.html
> /whichversion.html
> /bugreport.html
>
> Thoughts?
>
> Mark
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

Re: [PROPOSAL / POLL] Issue a de-support notice for Tomcat 4

[Costin Manolache]

+1

Are you going to make any difference between 4.0.x and 4.1.x ? I think we
should drop 4.0.x sooner.

Costin

On Thu, Feb 14, 2008 at 4:12 PM, Mark Thomas <[EMAIL PROTECTED]> wrote:

> All,
>
> Tomcat 4 has been in maintenance mode for some time now with nearly all
> changes either updating libraries or fixing security bugs. I am happy to
> continue acting as release manager for as long as there are three +1s when
> there is a release.
>
> However, there will come a time when it makes sense to cease supporting
> Tomcat 4.1.x. Rather than just announce it, as we did for 5.0.x, I think
> we
> should try and give our users some notice to encourage them to move off
> 4.1.x and to give them time to plan the move.
>
> Therefore, my proposal is that we issue a de-support notice for Tomcat 4.
>
> The poll is what date we announce for the end of Tomcat 4 support. Around
> 12 months notice seems reasonable to me so I am going to suggest 30 June
> 2009. Do people think this is enough notice? Alternative suggestions
> welcome.
>
> The web pages would also need the appropriate updates.
>
> Thoughts?
>
> Mark
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

Re: [Proposal] Remove status page from the docs

[jean-frederic clere]

Mark Thomas wrote:

All,

Whilst working through a general update of the docs webapp 
(CATALINA_BASE vs. CATALINA_HOME, Tomcat 5 -> Tomcat 6, common/lib -> 
lib etc) I cam across this page.


http://tomcat.apache.org/tomcat-6.0-doc/status.html

It is horribly out of date and duplicates information that is elsewhere. 
My suggestion is that it is removed for the next 6.0.x release. I am 
leaning towards not replacing it with anything but if we wanted to we 
could point towards http://wiki.apache.org/tomcat/TomcatVersions - which 
needs some tidying up but does give a better idea of where we are.


Thoughts?


+1

Cheers

Jean-Frederic



Mark

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