Re: Tomcat 6.0.1 alpha

[William A. Rowe, Jr.]

Guys - something got broken again in your release process against ASF policy...

I don't see three +1's for any of the recent postings to your downloads page.

Please remedy this - even if it's a matter of 3 +1's for 'alpha'?

Remy Maucherat wrote:
> Hi,
> 
> Tomcat 6.0.1 alpha is now available for testing:
> http://tomcat.apache.org/download-60.cgi
> 
> A stability vote will be done next week.
> 
> Rémy
> 
> -
> 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: Tomcat 6.0.1 alpha

[Henri Gomez]

+1

2006/11/17, William A. Rowe, Jr. <[EMAIL PROTECTED]>:

Guys - something got broken again in your release process against ASF policy...

I don't see three +1's for any of the recent postings to your downloads page.

Please remedy this - even if it's a matter of 3 +1's for 'alpha'?

Remy Maucherat wrote:
> Hi,
>
> Tomcat 6.0.1 alpha is now available for testing:
> http://tomcat.apache.org/download-60.cgi
>
> A stability vote will be done next week.
>
> Rémy
>
> -
> 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]

[EMAIL PROTECTED]: Project jakarta-tomcat-dbcp (in module jakarta-tomcat-5) failed

[bobh]

To whom it may engage...

This is an automated request, but not an unsolicited one. For 
more information please visit http://gump.apache.org/nagged.html, 
and/or contact the folk at [EMAIL PROTECTED]

Project jakarta-tomcat-dbcp has an issue affecting its community integration.
This issue affects 3 projects,
 and has been outstanding for 23 runs.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- jakarta-tomcat-catalina :  Servlet 2.4 Reference Implementation
- jakarta-tomcat-dbcp :  Servlet 2.4 and JSP 2.0 Reference Implementation
- jakarta-tomcat-jk :  Connectors to various web servers


Full details are available at:

http://vmgump.apache.org/gump/public/jakarta-tomcat-5/jakarta-tomcat-dbcp/index.html

That said, some information snippets are provided here.

The following annotations (debug/informational/warning/error messages) were 
provided:
 -DEBUG- Sole output [naming-factory-dbcp.jar] identifier set to project name
 -INFO- Made directory 
[/usr/local/gump/public/workspace/jakarta-tomcat-5/tomcat-deps]
 -INFO- Failed with reason build failed
 -INFO- Failed to extract fallback artifacts from Gump Repository



The following work was performed:
http://vmgump.apache.org/gump/public/jakarta-tomcat-5/jakarta-tomcat-dbcp/gump_work/build_jakarta-tomcat-5_jakarta-tomcat-dbcp.html
Work Name: build_jakarta-tomcat-5_jakarta-tomcat-dbcp (Type: Build)
Work ended in a state of : Failed
Elapsed: 6 secs
Command Line: java -Djava.awt.headless=true org.apache.tools.ant.Main 
-Dgump.merge=/x1/gump/public/gump/work/merge.xml -Dbuild.sysclasspath=only 
-Dcommons-collections.home=/usr/local/gump/public/workspace/jakarta-commons/collections
 -Dcommons-dbcp.home=/usr/local/gump/public/workspace/jakarta-commons/dbcp 
-Dcommons-dbcp.version=17112006 
-Dtomcat-dbcp.home=/usr/local/gump/public/workspace/jakarta-tomcat-5/tomcat-deps
 -Dcommons-pool.home=/usr/local/gump/public/workspace/jakarta-commons/pool 
build-tomcat-dbcp 
[Working Directory: /usr/local/gump/public/workspace/jakarta-tomcat-5]
CLASSPATH: 
/opt/jdk1.5/lib/tools.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-swing.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-apache-resolver.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-trax.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-junit.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-nodeps.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant.jar:/usr/local/gump/packages/junit3.8.1/junit.jar:/usr/local/gump/public/workspace/xml-commons/java/build/resolver.jar
-
Buildfile: build.xml

build-tomcat-dbcp:

-build-tomcat-dbcp:
 [copy] Copying 104 files to 
/usr/local/gump/public/workspace/jakarta-tomcat-5/tomcat-deps
[mkdir] Created dir: 
/usr/local/gump/public/workspace/jakarta-tomcat-5/tomcat-deps/src/java/org/apache/tomcat/dbcp
 [move] Moving 92 files to 
/usr/local/gump/public/workspace/jakarta-tomcat-5/tomcat-deps/src/java/org/apache/tomcat/dbcp
[mkdir] Created dir: 
/usr/local/gump/public/workspace/jakarta-tomcat-5/tomcat-deps/classes
[javac] Compiling 92 source files to 
/usr/local/gump/public/workspace/jakarta-tomcat-5/tomcat-deps/classes
[javac] 
/usr/local/gump/public/workspace/jakarta-tomcat-5/tomcat-deps/src/java/org/apache/tomcat/dbcp/pool/PoolUtils.java:20:
 cannot find symbol
[javac] symbol  : class StackKeyedObjectPool
[javac] location: package org.apache.tomcat.dbcp.pool.impl
[javac] import org.apache.tomcat.dbcp.pool.impl.StackKeyedObjectPool;
[javac] ^
[javac] 
/usr/local/gump/public/workspace/jakarta-tomcat-5/tomcat-deps/src/java/org/apache/tomcat/dbcp/pool/PoolUtils.java:22:
 cannot find symbol
[javac] symbol  : class SoftReferenceObjectPool
[javac] location: package org.apache.tomcat.dbcp.pool.impl
[javac] import org.apache.tomcat.dbcp.pool.impl.SoftReferenceObjectPool;
[javac] ^
[javac] 
/usr/local/gump/public/workspace/jakarta-tomcat-5/tomcat-deps/src/java/org/apache/tomcat/dbcp/pool/PoolUtils.java:23:
 cannot find symbol
[javac] symbol  : class StackObjectPool
[javac] location: package org.apache.tomcat.dbcp.pool.impl
[javac] import org.apache.tomcat.dbcp.pool.impl.StackObjectPool;
[javac] ^
[javac] 
/usr/local/gump/public/workspace/jakarta-tomcat-5/tomcat-deps/src/java/org/apache/tomcat/dbcp/pool/PoolUtils.java:353:
 cannot find symbol
[javac] symbol  : class SoftReferenceObjectPool
[javac] location: class org.apache.tomcat.dbcp.pool.PoolUtils
[javac] assert !(pool instanceof SoftReferenceObjectPool)
[javac]  ^
[javac] 
/usr/loca

[EMAIL PROTECTED]: Project jakarta-tomcat-dbcp (in module jakarta-tomcat-5) failed

[bobh]

To whom it may engage...

This is an automated request, but not an unsolicited one. For 
more information please visit http://gump.apache.org/nagged.html, 
and/or contact the folk at [EMAIL PROTECTED]

Project jakarta-tomcat-dbcp has an issue affecting its community integration.
This issue affects 3 projects,
 and has been outstanding for 23 runs.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- jakarta-tomcat-catalina :  Servlet 2.4 Reference Implementation
- jakarta-tomcat-dbcp :  Servlet 2.4 and JSP 2.0 Reference Implementation
- jakarta-tomcat-jk :  Connectors to various web servers


Full details are available at:

http://vmgump.apache.org/gump/public/jakarta-tomcat-5/jakarta-tomcat-dbcp/index.html

That said, some information snippets are provided here.

The following annotations (debug/informational/warning/error messages) were 
provided:
 -DEBUG- Sole output [naming-factory-dbcp.jar] identifier set to project name
 -INFO- Made directory 
[/usr/local/gump/public/workspace/jakarta-tomcat-5/tomcat-deps]
 -INFO- Failed with reason build failed
 -INFO- Failed to extract fallback artifacts from Gump Repository



The following work was performed:
http://vmgump.apache.org/gump/public/jakarta-tomcat-5/jakarta-tomcat-dbcp/gump_work/build_jakarta-tomcat-5_jakarta-tomcat-dbcp.html
Work Name: build_jakarta-tomcat-5_jakarta-tomcat-dbcp (Type: Build)
Work ended in a state of : Failed
Elapsed: 6 secs
Command Line: java -Djava.awt.headless=true org.apache.tools.ant.Main 
-Dgump.merge=/x1/gump/public/gump/work/merge.xml -Dbuild.sysclasspath=only 
-Dcommons-collections.home=/usr/local/gump/public/workspace/jakarta-commons/collections
 -Dcommons-dbcp.home=/usr/local/gump/public/workspace/jakarta-commons/dbcp 
-Dcommons-dbcp.version=17112006 
-Dtomcat-dbcp.home=/usr/local/gump/public/workspace/jakarta-tomcat-5/tomcat-deps
 -Dcommons-pool.home=/usr/local/gump/public/workspace/jakarta-commons/pool 
build-tomcat-dbcp 
[Working Directory: /usr/local/gump/public/workspace/jakarta-tomcat-5]
CLASSPATH: 
/opt/jdk1.5/lib/tools.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-swing.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-apache-resolver.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-trax.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-junit.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-nodeps.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant.jar:/usr/local/gump/packages/junit3.8.1/junit.jar:/usr/local/gump/public/workspace/xml-commons/java/build/resolver.jar
-
Buildfile: build.xml

build-tomcat-dbcp:

-build-tomcat-dbcp:
 [copy] Copying 104 files to 
/usr/local/gump/public/workspace/jakarta-tomcat-5/tomcat-deps
[mkdir] Created dir: 
/usr/local/gump/public/workspace/jakarta-tomcat-5/tomcat-deps/src/java/org/apache/tomcat/dbcp
 [move] Moving 92 files to 
/usr/local/gump/public/workspace/jakarta-tomcat-5/tomcat-deps/src/java/org/apache/tomcat/dbcp
[mkdir] Created dir: 
/usr/local/gump/public/workspace/jakarta-tomcat-5/tomcat-deps/classes
[javac] Compiling 92 source files to 
/usr/local/gump/public/workspace/jakarta-tomcat-5/tomcat-deps/classes
[javac] 
/usr/local/gump/public/workspace/jakarta-tomcat-5/tomcat-deps/src/java/org/apache/tomcat/dbcp/pool/PoolUtils.java:20:
 cannot find symbol
[javac] symbol  : class StackKeyedObjectPool
[javac] location: package org.apache.tomcat.dbcp.pool.impl
[javac] import org.apache.tomcat.dbcp.pool.impl.StackKeyedObjectPool;
[javac] ^
[javac] 
/usr/local/gump/public/workspace/jakarta-tomcat-5/tomcat-deps/src/java/org/apache/tomcat/dbcp/pool/PoolUtils.java:22:
 cannot find symbol
[javac] symbol  : class SoftReferenceObjectPool
[javac] location: package org.apache.tomcat.dbcp.pool.impl
[javac] import org.apache.tomcat.dbcp.pool.impl.SoftReferenceObjectPool;
[javac] ^
[javac] 
/usr/local/gump/public/workspace/jakarta-tomcat-5/tomcat-deps/src/java/org/apache/tomcat/dbcp/pool/PoolUtils.java:23:
 cannot find symbol
[javac] symbol  : class StackObjectPool
[javac] location: package org.apache.tomcat.dbcp.pool.impl
[javac] import org.apache.tomcat.dbcp.pool.impl.StackObjectPool;
[javac] ^
[javac] 
/usr/local/gump/public/workspace/jakarta-tomcat-5/tomcat-deps/src/java/org/apache/tomcat/dbcp/pool/PoolUtils.java:353:
 cannot find symbol
[javac] symbol  : class SoftReferenceObjectPool
[javac] location: class org.apache.tomcat.dbcp.pool.PoolUtils
[javac] assert !(pool instanceof SoftReferenceObjectPool)
[javac]  ^
[javac] 
/usr/loca

[EMAIL PROTECTED]: Project tomcat-tc6-dbcp (in module tomcat-tc6) failed

[Bill Barker]

To whom it may engage...

This is an automated request, but not an unsolicited one. For 
more information please visit http://gump.apache.org/nagged.html, 
and/or contact the folk at [EMAIL PROTECTED]

Project tomcat-tc6-dbcp has an issue affecting its community integration.
This issue affects 2 projects,
 and has been outstanding for 23 runs.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- tomcat-tc6 :  Java Servlet 2.5 & Server Pages JSP 2.1 implementation (for 
...
- tomcat-tc6-dbcp :  Java Servlet 2.5 & Server Pages JSP 2.1 implementation 
(for ...


Full details are available at:
http://vmgump.apache.org/gump/public/tomcat-tc6/tomcat-tc6-dbcp/index.html

That said, some information snippets are provided here.

The following annotations (debug/informational/warning/error messages) were 
provided:
 -DEBUG- Sole output [tomcat-jdbc-17112006.jar] identifier set to project name
 -INFO- Made directory [/usr/local/gump/public/workspace/tomcat-tc6/tomcat-deps]
 -INFO- Failed with reason build failed
 -INFO- Failed to extract fallback artifacts from Gump Repository



The following work was performed:
http://vmgump.apache.org/gump/public/tomcat-tc6/tomcat-tc6-dbcp/gump_work/build_tomcat-tc6_tomcat-tc6-dbcp.html
Work Name: build_tomcat-tc6_tomcat-tc6-dbcp (Type: Build)
Work ended in a state of : Failed
Elapsed: 6 secs
Command Line: java -Djava.awt.headless=true org.apache.tools.ant.Main 
-Dgump.merge=/x1/gump/public/gump/work/merge.xml -Dbuild.sysclasspath=only 
-Dcommons-collections.home=/usr/local/gump/public/workspace/jakarta-commons/collections
 -Dcommons-dbcp.home=/usr/local/gump/public/workspace/jakarta-commons/dbcp 
-Dtomcat-dbcp.jar=/usr/local/gump/public/workspace/tomcat-tc6/tomcat-deps/tomcat-jdbc-17112006.jar
 -Dtomcat-dbcp.home=/usr/local/gump/public/workspace/tomcat-tc6/tomcat-deps 
-Dcommons-pool.home=/usr/local/gump/public/workspace/jakarta-commons/pool 
build-tomcat-dbcp 
[Working Directory: /usr/local/gump/public/workspace/tomcat-tc6]
CLASSPATH: 
/opt/jdk1.5/lib/tools.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-swing.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-apache-resolver.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-trax.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-junit.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-nodeps.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant.jar:/usr/local/gump/packages/junit3.8.1/junit.jar:/usr/local/gump/public/workspace/xml-commons/java/build/resolver.jar
-
Buildfile: build.xml

build-tomcat-dbcp:
 [copy] Copying 104 files to 
/usr/local/gump/public/workspace/tomcat-tc6/tomcat-deps
[mkdir] Created dir: 
/usr/local/gump/public/workspace/tomcat-tc6/tomcat-deps/src/java/org/apache/tomcat/dbcp
 [move] Moving 92 files to 
/usr/local/gump/public/workspace/tomcat-tc6/tomcat-deps/src/java/org/apache/tomcat/dbcp
[mkdir] Created dir: 
/usr/local/gump/public/workspace/tomcat-tc6/tomcat-deps/classes
[javac] Compiling 92 source files to 
/usr/local/gump/public/workspace/tomcat-tc6/tomcat-deps/classes
[javac] 
/usr/local/gump/public/workspace/tomcat-tc6/tomcat-deps/src/java/org/apache/tomcat/dbcp/pool/PoolUtils.java:20:
 cannot find symbol
[javac] symbol  : class StackKeyedObjectPool
[javac] location: package org.apache.tomcat.dbcp.pool.impl
[javac] import org.apache.tomcat.dbcp.pool.impl.StackKeyedObjectPool;
[javac] ^
[javac] 
/usr/local/gump/public/workspace/tomcat-tc6/tomcat-deps/src/java/org/apache/tomcat/dbcp/pool/PoolUtils.java:22:
 cannot find symbol
[javac] symbol  : class SoftReferenceObjectPool
[javac] location: package org.apache.tomcat.dbcp.pool.impl
[javac] import org.apache.tomcat.dbcp.pool.impl.SoftReferenceObjectPool;
[javac] ^
[javac] 
/usr/local/gump/public/workspace/tomcat-tc6/tomcat-deps/src/java/org/apache/tomcat/dbcp/pool/PoolUtils.java:23:
 cannot find symbol
[javac] symbol  : class StackObjectPool
[javac] location: package org.apache.tomcat.dbcp.pool.impl
[javac] import org.apache.tomcat.dbcp.pool.impl.StackObjectPool;
[javac] ^
[javac] 
/usr/local/gump/public/workspace/tomcat-tc6/tomcat-deps/src/java/org/apache/tomcat/dbcp/pool/PoolUtils.java:353:
 cannot find symbol
[javac] symbol  : class SoftReferenceObjectPool
[javac] location: class org.apache.tomcat.dbcp.pool.PoolUtils
[javac] assert !(pool instanceof SoftReferenceObjectPool)
[javac]  ^
[javac] 
/usr/local/gump/public/workspace/tomcat-tc6/tomcat-deps/src/java/org/apache/tomcat/dbcp/pool/PoolUtils.java:355:
 

[EMAIL PROTECTED]: Project tomcat-tc6-dbcp (in module tomcat-tc6) failed

[Bill Barker]

To whom it may engage...

This is an automated request, but not an unsolicited one. For 
more information please visit http://gump.apache.org/nagged.html, 
and/or contact the folk at [EMAIL PROTECTED]

Project tomcat-tc6-dbcp has an issue affecting its community integration.
This issue affects 2 projects,
 and has been outstanding for 23 runs.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- tomcat-tc6 :  Java Servlet 2.5 & Server Pages JSP 2.1 implementation (for 
...
- tomcat-tc6-dbcp :  Java Servlet 2.5 & Server Pages JSP 2.1 implementation 
(for ...


Full details are available at:
http://vmgump.apache.org/gump/public/tomcat-tc6/tomcat-tc6-dbcp/index.html

That said, some information snippets are provided here.

The following annotations (debug/informational/warning/error messages) were 
provided:
 -DEBUG- Sole output [tomcat-jdbc-17112006.jar] identifier set to project name
 -INFO- Made directory [/usr/local/gump/public/workspace/tomcat-tc6/tomcat-deps]
 -INFO- Failed with reason build failed
 -INFO- Failed to extract fallback artifacts from Gump Repository



The following work was performed:
http://vmgump.apache.org/gump/public/tomcat-tc6/tomcat-tc6-dbcp/gump_work/build_tomcat-tc6_tomcat-tc6-dbcp.html
Work Name: build_tomcat-tc6_tomcat-tc6-dbcp (Type: Build)
Work ended in a state of : Failed
Elapsed: 6 secs
Command Line: java -Djava.awt.headless=true org.apache.tools.ant.Main 
-Dgump.merge=/x1/gump/public/gump/work/merge.xml -Dbuild.sysclasspath=only 
-Dcommons-collections.home=/usr/local/gump/public/workspace/jakarta-commons/collections
 -Dcommons-dbcp.home=/usr/local/gump/public/workspace/jakarta-commons/dbcp 
-Dtomcat-dbcp.jar=/usr/local/gump/public/workspace/tomcat-tc6/tomcat-deps/tomcat-jdbc-17112006.jar
 -Dtomcat-dbcp.home=/usr/local/gump/public/workspace/tomcat-tc6/tomcat-deps 
-Dcommons-pool.home=/usr/local/gump/public/workspace/jakarta-commons/pool 
build-tomcat-dbcp 
[Working Directory: /usr/local/gump/public/workspace/tomcat-tc6]
CLASSPATH: 
/opt/jdk1.5/lib/tools.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-swing.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-apache-resolver.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-trax.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-junit.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-nodeps.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant.jar:/usr/local/gump/packages/junit3.8.1/junit.jar:/usr/local/gump/public/workspace/xml-commons/java/build/resolver.jar
-
Buildfile: build.xml

build-tomcat-dbcp:
 [copy] Copying 104 files to 
/usr/local/gump/public/workspace/tomcat-tc6/tomcat-deps
[mkdir] Created dir: 
/usr/local/gump/public/workspace/tomcat-tc6/tomcat-deps/src/java/org/apache/tomcat/dbcp
 [move] Moving 92 files to 
/usr/local/gump/public/workspace/tomcat-tc6/tomcat-deps/src/java/org/apache/tomcat/dbcp
[mkdir] Created dir: 
/usr/local/gump/public/workspace/tomcat-tc6/tomcat-deps/classes
[javac] Compiling 92 source files to 
/usr/local/gump/public/workspace/tomcat-tc6/tomcat-deps/classes
[javac] 
/usr/local/gump/public/workspace/tomcat-tc6/tomcat-deps/src/java/org/apache/tomcat/dbcp/pool/PoolUtils.java:20:
 cannot find symbol
[javac] symbol  : class StackKeyedObjectPool
[javac] location: package org.apache.tomcat.dbcp.pool.impl
[javac] import org.apache.tomcat.dbcp.pool.impl.StackKeyedObjectPool;
[javac] ^
[javac] 
/usr/local/gump/public/workspace/tomcat-tc6/tomcat-deps/src/java/org/apache/tomcat/dbcp/pool/PoolUtils.java:22:
 cannot find symbol
[javac] symbol  : class SoftReferenceObjectPool
[javac] location: package org.apache.tomcat.dbcp.pool.impl
[javac] import org.apache.tomcat.dbcp.pool.impl.SoftReferenceObjectPool;
[javac] ^
[javac] 
/usr/local/gump/public/workspace/tomcat-tc6/tomcat-deps/src/java/org/apache/tomcat/dbcp/pool/PoolUtils.java:23:
 cannot find symbol
[javac] symbol  : class StackObjectPool
[javac] location: package org.apache.tomcat.dbcp.pool.impl
[javac] import org.apache.tomcat.dbcp.pool.impl.StackObjectPool;
[javac] ^
[javac] 
/usr/local/gump/public/workspace/tomcat-tc6/tomcat-deps/src/java/org/apache/tomcat/dbcp/pool/PoolUtils.java:353:
 cannot find symbol
[javac] symbol  : class SoftReferenceObjectPool
[javac] location: class org.apache.tomcat.dbcp.pool.PoolUtils
[javac] assert !(pool instanceof SoftReferenceObjectPool)
[javac]  ^
[javac] 
/usr/local/gump/public/workspace/tomcat-tc6/tomcat-deps/src/java/org/apache/tomcat/dbcp/pool/PoolUtils.java:355:
 

Re: Tomcat 6.0.1 alpha

[Peter Rossbach]

+1 -- 6.0.2 is beta,

Am 17.11.2006 um 10:46 schrieb William A. Rowe, Jr.:

Guys - something got broken again in your release process against  
ASF policy...


I don't see three +1's for any of the recent postings to your  
downloads page.


Please remedy this - even if it's a matter of 3 +1's for 'alpha'?

Remy Maucherat wrote:

Hi,

Tomcat 6.0.1 alpha is now available for testing:
http://tomcat.apache.org/download-60.cgi

A stability vote will be done next week.

Rémy

-
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: Tomcat 6.0.1 alpha

[Yoav Shapira]

I could swear we had agreed before the release candidate was posted to
call the first couple of 6.0 builds alpha...

+1 for 6.0.1 as alpha.

Yoav

On 11/17/06, William A. Rowe, Jr. <[EMAIL PROTECTED]> wrote:

Guys - something got broken again in your release process against ASF policy...

I don't see three +1's for any of the recent postings to your downloads page.

Please remedy this - even if it's a matter of 3 +1's for 'alpha'?

Remy Maucherat wrote:
> Hi,
>
> Tomcat 6.0.1 alpha is now available for testing:
> http://tomcat.apache.org/download-60.cgi
>
> A stability vote will be done next week.
>
> Rémy
>
> -
> 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: Tomcat 6.0.1 alpha

[Mladen Turk]

William A. Rowe, Jr. wrote:

Guys - something got broken again in your release process against ASF policy...

I don't see three +1's for any of the recent postings to your downloads page.



+1

--
Mladen

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

Re: Tomcat 6.0.1 alpha

[Mladen Turk]

William A. Rowe, Jr. wrote:

Guys - something got broken again in your release process against ASF policy...
I don't see three +1's for any of the recent postings to your downloads page.



Nothing got broken.

Tomcat is probably one of the latest remaining projects
where the developers and PMC still works on the
original ASF presumptions (CTR).
The vote itself is a minor thing compared with all
the work and communication that happened a long time before
the email stating: "I'll make the release".

Anyone interested can monitor the developers list and
react promptly if he thinks there is a major outage.

One size doesn't fit all, and never will.

Regards,
Mladen.


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

DO NOT REPLY [Bug 40668] - MailSessionFactory is missing in Tomcat 5.5.20

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


[EMAIL PROTECTED] changed:

   What|Removed |Added

 CC||[EMAIL PROTECTED]




-- 
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 40993] New: - add session_cookie to lb worker to support customed SESSION_IDENTIFIER

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

   Summary: add session_cookie to lb worker to support customed
SESSION_IDENTIFIER
   Product: Tomcat 5
   Version: 5.5.20
  Platform: All
OS/Version: All
Status: NEW
  Severity: enhancement
  Priority: P3
 Component: Native:JK
AssignedTo: tomcat-dev@jakarta.apache.org
ReportedBy: [EMAIL PROTECTED]


"JSESSION" is a standard session identifier, but sometimes this may need to do
some change. For example, if two J2EE application in then same site domain, and
both of them use a "JSESSIONID" cookie... something wrong may be happened.

So I think this patch may be useful, at least for me.

-- 
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 40993] - add session_cookie to lb worker to support customed SESSION_IDENTIFIER

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





--- Additional Comments From [EMAIL PROTECTED]  2006-11-17 07:17 ---
Created an attachment (id=19134)
 --> (http://issues.apache.org/bugzilla/attachment.cgi?id=19134&action=view)
A patch use tomcat's connector/jk as base dir


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

Jasper: Using a non-File based environment

[Felix Meschberger]

Hi,

I am new to this list, so let me quickly introduce myself: I am Felix
Meschberger and am working on a Web Content Management Application
running on a Java Content Repository (Apache Jackrabbit) provding
amongst other things dynamic compilation of JSP scripts. I am also a
committer to the Jackrabbit project to which I contributed the JCR
ClassLoader and worked on the RMI layer library.

Integrating JSP support in the application is the reason for me be
here: To compile JSP, I took Jasper 5.5.20 and adapted it to my use
case, which I will explain quickly. As I said, the application will
run on Jackrabbit. Consequently, JSP source will be stored in the
repository not the OS Filesystem or the Web App Context. Also,
generated Java Source and Servlet classes will be stored in the
repository. The repository class loader will pick the servlets up for
execution.

To enable this functionality, I patched Jasper as follows:
 * Defined a new IOProvider interface, which abstracts the File
operations: getInputStream, getOutputStream, mkdirs, delete and some
more. Of course a default file based variant has also been implemented
 * Fixed all direct File uses to use the new IOProvider API
 * The IOProvider is set on JspRuntimeContext and defaults to the
File-based implementation
 * Modified JspCompilationContext.loader field to be a class loader,
as my environment has no URLClassLoader
 * To inject my custom class loader, I added API to the Options
interface to return a custom provided classloader to compile (in the
case of Eclipse Compiler) and load JspServlets instead of the
JspLoader.
 * Another change to the Options interface: the getScratchDir method
returns a File, which is not available in my environment. In fact the
scratchDir suffices it to be a String, which may be interpreted as a
Filesystem directory in the standartd use case. Hence, I modified the
method to return a String (Yes, I know, this is a "dangerous"
modification !)

I would like to to know, whether you would be interested to see these
patches and might consider them for addition to the Jasper code ?

Thanks for your replies
Felix

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

Re: svn commit: r452464 - /tomcat/connectors/trunk/jk/native/scripts/build/instdso.sh

[Rainer Jung]

Hello Jean-Frederic,

there is a problem with the instdso.sh you checked in. It removes a 
couple of files at the end, including the mod_jk.la file. When we run 
"make install" afterwards, apxs again tries to run instdso.sh from it's 
apache installation and complains about the missing mod_jk.la.


I compared the instdso.sh with the ones in Apache httpd 2.0 and 2.3 and 
they both do not have the 4 remove statements included in the mod_jk one.


Are they needed? Could we just remove those?

Regards,

Rainer

[EMAIL PROTECTED] wrote:

Author: jfclere
Date: Tue Oct  3 05:52:21 2006
New Revision: 452464

URL: http://svn.apache.org/viewvc?view=rev&rev=452464
Log:
libtool is not able to install on HP-UX, the Apache httpd script here does it.

Added:
tomcat/connectors/trunk/jk/native/scripts/build/instdso.sh   (with props)

Added: tomcat/connectors/trunk/jk/native/scripts/build/instdso.sh
URL: 
http://svn.apache.org/viewvc/tomcat/connectors/trunk/jk/native/scripts/build/instdso.sh?view=auto&rev=452464
==
--- tomcat/connectors/trunk/jk/native/scripts/build/instdso.sh (added)
+++ tomcat/connectors/trunk/jk/native/scripts/build/instdso.sh Tue Oct  3 
05:52:21 2006
@@ -0,0 +1,96 @@
+#!/bin/sh
+#
+# 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.
+#
+#
+# instdso.sh - install Apache DSO modules
+#
+# we use this instead of libtool --install because:
+# 1) on a few platforms libtool doesn't install DSOs exactly like we'd
+#want (weird names, doesn't remove DSO first)
+# 2) we never want the .la files copied, so we might as well copy
+#the .so files ourselves
+
+if test "$#" != "3"; then
+echo "wrong number of arguments to instdso.sh"
+echo "Usage: instdso.sh SH_LIBTOOL-value dso-name path-to-modules"
+exit 1
+fi
+
+SH_LIBTOOL=`echo $1 | sed -e 's/^SH_LIBTOOL=//'`
+DSOARCHIVE=$2
+DSOARCHIVE_BASENAME=`basename $2`
+TARGETDIR=$3
+DSOBASE=`echo $DSOARCHIVE_BASENAME | sed -e 's/\.la$//'`
+TARGET_NAME="$DSOBASE.so"
+
+SYS=`uname -s`
+
+if test "$SYS" = "AIX"
+then
+# on AIX, shared libraries remain in storage even when
+# all processes using them have exited; standard practice
+# prior to installing a shared library is to rm -f first
+CMD="rm -f $TARGETDIR/$TARGET_NAME"
+echo $CMD
+$CMD || exit $?
+fi
+
+CMD="$SH_LIBTOOL --mode=install cp $DSOARCHIVE $TARGETDIR/"
+echo $CMD
+$CMD || exit $?
+
+if test "$SYS" = "OS/2"
+then
+# on OS/2, aplibtool --install doesn't copy the .la files & we can't
+# rename DLLs to have a .so extension or they won't load so none of the 
+# steps below make sense.

+exit 0
+fi
+
+if test -s "$TARGETDIR/$DSOARCHIVE_BASENAME"
+then
+  DLNAME=`sed -n "/^dlname=/{s/.*='\([^']*\)'/\1/;p;}" 
$TARGETDIR/$DSOARCHIVE_BASENAME`
+  LIBRARY_NAMES=`sed -n "/^library_names/{s/library_names='\([^']*\)'/\1/;p;}" 
$TARGETDIR/$DSOARCHIVE_BASENAME`
+  LIBRARY_NAMES=`echo $LIBRARY_NAMES | sed -e "s/ *$DLNAME//g"`
+fi
+
+if test -z "$DLNAME"
+then
+  echo "Warning!  dlname not found in $TARGETDIR/$DSOARCHIVE_BASENAME."
+  echo "Assuming installing a .so rather than a libtool archive."
+  exit 0
+fi
+
+if test -n "$LIBRARY_NAMES"
+then
+for f in $LIBRARY_NAMES
+do
+rm -f $TARGETDIR/$f
+done
+fi
+
+if test "$DLNAME" != "$TARGET_NAME"
+then
+mv $TARGETDIR/$DLNAME $TARGETDIR/$TARGET_NAME
+fi
+
+rm -f $TARGETDIR/$DSOARCHIVE_BASENAME
+rm -f $TARGETDIR/$DSOBASE.a
+rm -f $TARGETDIR/lib$DSOBASE.a
+rm -f $TARGETDIR/lib$TARGET_NAME
+
+exit 0

Propchange: tomcat/connectors/trunk/jk/native/scripts/build/instdso.sh
--
svn:executable = *



-
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: Jasper: Using a non-File based environment

[Remy Maucherat]

Felix Meschberger wrote:

Hi,

I am new to this list, so let me quickly introduce myself: I am Felix
Meschberger and am working on a Web Content Management Application
running on a Java Content Repository (Apache Jackrabbit) provding
amongst other things dynamic compilation of JSP scripts. I am also a
committer to the Jackrabbit project to which I contributed the JCR
ClassLoader and worked on the RMI layer library.

Integrating JSP support in the application is the reason for me be
here: To compile JSP, I took Jasper 5.5.20 and adapted it to my use
case, which I will explain quickly. As I said, the application will
run on Jackrabbit. Consequently, JSP source will be stored in the
repository not the OS Filesystem or the Web App Context. Also,
generated Java Source and Servlet classes will be stored in the
repository. The repository class loader will pick the servlets up for
execution.

To enable this functionality, I patched Jasper as follows:
 * Defined a new IOProvider interface, which abstracts the File
operations: getInputStream, getOutputStream, mkdirs, delete and some
more. Of course a default file based variant has also been implemented
 * Fixed all direct File uses to use the new IOProvider API
 * The IOProvider is set on JspRuntimeContext and defaults to the
File-based implementation
 * Modified JspCompilationContext.loader field to be a class loader,
as my environment has no URLClassLoader
 * To inject my custom class loader, I added API to the Options
interface to return a custom provided classloader to compile (in the
case of Eclipse Compiler) and load JspServlets instead of the
JspLoader.
 * Another change to the Options interface: the getScratchDir method
returns a File, which is not available in my environment. In fact the
scratchDir suffices it to be a String, which may be interpreted as a
Filesystem directory in the standartd use case. Hence, I modified the
method to return a String (Yes, I know, this is a "dangerous"
modification !)

I would like to to know, whether you would be interested to see these
patches and might consider them for addition to the Jasper code ?


File abstraction is already present in Tomcat (for example, JSP used to 
run on top of Slide), so you can have all webapp resources loaded from a 
repository of your choice, rather than the filesystem.


If you want generated source and classes to be stored in the repository, 
then I really don't see the point. For starters, it's an implementation 
detail which could go away.


Rémy

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

DO NOT REPLY [Bug 39589] - $CATALINA_BASE/shared/lib and $CATALINA_BASE/shared/classes libraries not found in specific deployments

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





--- Additional Comments From [EMAIL PROTECTED]  2006-11-17 08:10 ---
Wondering why this issue is not being looked at?

-- 
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: [VOTE] Tomcat 6.0.2

[Remy Maucherat]

Remy Maucherat wrote:

6.0.2 is:
[ ] Alpha
[X] Beta


I like it :)

Rémy

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

Re: Tomcat 6.0.1 alpha

[William A. Rowe, Jr.]

Mladen Turk wrote:
> William A. Rowe, Jr. wrote:
>> Guys - something got broken again in your release process against ASF
>> policy...
>> I don't see three +1's for any of the recent postings to your
>> downloads page.
>>
> 
> Nothing got broken.

Actually it did, because I've followed the list for some 3 years although
I don't have the cycles to be active (too many fingers in other dikes within
and outside the ASF).  I brought this up almost a year ago now and watched
as the list started voting on all it's distribution packages (e.g. 'release'
in whichever form, alpha beta or general availability).  Things were following
the ASF procedure :)

> Tomcat is probably one of the latest remaining projects
> where the developers and PMC still works on the
> original ASF presumptions (CTR).

CTR/RTC has nothing to do with voting on the final distribution package.
It has to do with how the source code repository is handled, and I think
(from following the discussion on dev@) that the current policies suit the
project very well.

> The vote itself is a minor thing compared with all
> the work and communication that happened a long time before
> the email stating: "I'll make the release".

No, this is what the ASF is saying - yes all those micro decisions are great
so that everyone is on the same page when you get to a release, but...

the only vote that binds the board and the foundation to the package is your
project's release vote after the distribution package is rolled, and...

that's what makes this the ASF's release, and not Remy's personal liability.
Believe me, we aren't nitpicking, I don't want Remy or any other committer
to be hanging out there with liabilities for something distributed by any
given project.

> Anyone interested can monitor the developers list and
> react promptly if he thinks there is a major outage.

Trust, I do :)  Things are working great, and other than this issue with
6.0.1/6.0.2 I haven't seen any issues.  And belated congratulations on
the new 6.0 baby!

> One size doesn't fit all, and never will.

On this, policy for handling a distribution package, there is only one size
that ensures your collective work becomes the ASF's headache, should any
'bad thing' happen in the future with respect to intellectual property or
liability.

I'm just looking out for you guys, especially everyone with the gumption
to handle the RM's job ;)

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

Re: Tomcat 6.0.1 alpha

[Yoav Shapira]

Hi,
I understand what Bill is saying.  Let's talk specifics to see what we missed.

We had a poll on this public mailing list to decide on a time and date
to cut 6.0.1.  We agreed on a time/date, and cut the release then.  We
announced here that the release was available and said we'd have a
stability vote in one week.  The release was tentatively rated as
alpha by the release manager.  After a week, we had the stability
vote, and decided the release is indeed alpha and not more stable.  We
also decided to cut 6.0.2 next.

What did we miss?  Was it a formal announcement to [EMAIL PROTECTED]
about 6.0.1 stability?  Was it formally marking the 6.0.1 time/date
poll as a voting thread and posting its results?

Yoav


On 11/17/06, William A. Rowe, Jr. <[EMAIL PROTECTED]> wrote:

Mladen Turk wrote:
> William A. Rowe, Jr. wrote:
>> Guys - something got broken again in your release process against ASF
>> policy...
>> I don't see three +1's for any of the recent postings to your
>> downloads page.
>>
>
> Nothing got broken.

Actually it did, because I've followed the list for some 3 years although
I don't have the cycles to be active (too many fingers in other dikes within
and outside the ASF).  I brought this up almost a year ago now and watched
as the list started voting on all it's distribution packages (e.g. 'release'
in whichever form, alpha beta or general availability).  Things were following
the ASF procedure :)

> Tomcat is probably one of the latest remaining projects
> where the developers and PMC still works on the
> original ASF presumptions (CTR).

CTR/RTC has nothing to do with voting on the final distribution package.
It has to do with how the source code repository is handled, and I think
(from following the discussion on dev@) that the current policies suit the
project very well.

> The vote itself is a minor thing compared with all
> the work and communication that happened a long time before
> the email stating: "I'll make the release".

No, this is what the ASF is saying - yes all those micro decisions are great
so that everyone is on the same page when you get to a release, but...

the only vote that binds the board and the foundation to the package is your
project's release vote after the distribution package is rolled, and...

that's what makes this the ASF's release, and not Remy's personal liability.
Believe me, we aren't nitpicking, I don't want Remy or any other committer
to be hanging out there with liabilities for something distributed by any
given project.

> Anyone interested can monitor the developers list and
> react promptly if he thinks there is a major outage.

Trust, I do :)  Things are working great, and other than this issue with
6.0.1/6.0.2 I haven't seen any issues.  And belated congratulations on
the new 6.0 baby!

> One size doesn't fit all, and never will.

On this, policy for handling a distribution package, there is only one size
that ensures your collective work becomes the ASF's headache, should any
'bad thing' happen in the future with respect to intellectual property or
liability.

I'm just looking out for you guys, especially everyone with the gumption
to handle the RM's job ;)

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

[Jeanfrancois Arcand]

6.0.2 is:
[ ] Alpha
[X] Beta



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

Re: Tomcat 6.0.1 alpha

[William A. Rowe, Jr.]

Yoav Shapira wrote:
> 
> What did we miss?  Was it a formal announcement to [EMAIL PROTECTED]
> about 6.0.1 stability?  Was it formally marking the 6.0.1 time/date
> poll as a voting thread and posting its results?

What you are missing is pretty straightforward.  It's that you can't have
a release vote of a package that isn't in your hands.  Therefore any vote
on the "future state" of the repository isn't a "release vote", but it's
a decision to cut a release candidate.  And in all this the committers are
working really well and rowing in the same direction :)

Once you have a tarball/jar in-hand, you have something you can vote to
release (or not), and then post it on the general downloads page.  Until
there are 3 votes for somepackage-1.2.3.tar.gz, it still isn't an ASF
release and doesn't, yet, belong on the downloads page.  /dev/dist/ or
somewhere the RM wants to put it for signoff works.



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

DO NOT REPLY [Bug 40668] - MailSessionFactory is missing in Tomcat 5.5.20

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


[EMAIL PROTECTED] changed:

   What|Removed |Added

 CC||[EMAIL PROTECTED]




-- 
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 40996] New: - Tomcat Connectors 1.2.19 sticky sessions not sticky

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

   Summary: Tomcat Connectors 1.2.19 sticky sessions not sticky
   Product: Tomcat 5
   Version: Unknown
  Platform: Other
OS/Version: Linux
Status: NEW
  Severity: major
  Priority: P2
 Component: Connector:AJP
AssignedTo: tomcat-dev@jakarta.apache.org
ReportedBy: [EMAIL PROTECTED]


Since upgrading from Tomcat Connectors 1.2.15 to 1.2.19 we find that session
affinity between apache and a tomcat/jboss instance is lossed. It appears that
the connector will quite frequently direct traffic to the first worker in a LB
pool rather than the one with the correct JVMRoute for the session.

Rolling back to 1.2.15 has resolved this issue. No other conf changes were made
as part of this upgrade.

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