Re: [VOTE] Release Apache Tomcat 7.0.18

[Martin Dubuc]

+1 Stable

On Thu, Jul 7, 2011 at 6:10 AM, Mark Thomas  wrote:

> The proposed Apache Tomcat 7.0.18 release is now available for voting.
>
> It can be obtained from:
> http://people.apache.org/~markt/dev/tomcat-7/v7.0.18/
> The svn tag is:
> http://svn.apache.org/repos/asf/tomcat/tc7.0.x/tags/TOMCAT_7_0_18/
>
> The proposed 7.0.18 release is:
>
> [ ] Broken - do not release
> [ ] Alpha  - go ahead and release as 7.0.18 Alpha
> [ ] Beta   - go ahead and release as 7.0.18 Beta
> [ X ] Stable - go ahead and release as 7.0.18 Stable
>
> Cheers,
>
> Mark
>
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: dev-h...@tomcat.apache.org
>
>

crlFile and SunX509 algorithm in Tomcat 7.0.11

[Martin Dubuc]

I posted a request for help regarding an issue with configuration of CRL for
HTTPS connector on the users list but haven't receive any insights on the
matter. I am re-posting the message with summary information in hope that
someone on the dev list can help.

* * *

Up to Tomcat 7.0.10, I used the crlFile configuration along with the SunX509
algorithm in SSL HTTP connector configuration in server.xml. However, when I
start Tomcat 7.0.11, 7.0.14 or 7.0.16 with the same configuration, I get the
following error:

Jun 16, 2011 12:22:22 PM org.apache.coyote.
AbstractProtocol init
SEVERE: Failed to initialize end point associated with ProtocolHandler
["http-bio-8443"]
java.io.IOException: CRLs not supported for type: SunX509
at
org.apache.tomcat.util.net.jsse.JSSESocketFactory.init(JSSESocketFactory.java:476)
...
Caused by: java.io.IOException: CRLs not supported for type: SunX509

at
org.apache.tomcat.util.net.jsse.JSSESocketFactory.init(JSSESocketFactory.java:476)
at org.apache.tomcat.util.net.
jsse.JSSESocketFactory.createSocket(JSSESocketFactory.java:158)
...

I am using JDK 6 update 26.

Has CRL support been recently removed for SunX509 algorithm? Anybody on the
dev list would know why this might have been introduced in 7.0.11?

I have seen that some code was committed in the JSSESocketFactory class in
7.0.11, but I can't see the correlation between this change and the
exception that started to be thrown in 7.0.11.

Martin

Re: [VOTE] Release Apache Tomcat 7.0.4

[Martin Dubuc]

+1 Beta

On Fri, Oct 15, 2010 at 4:47 AM, Mark Thomas  wrote:

> The proposed Apache Tomcat 7.0.4 release is now available for voting.
>
> It can be obtained from:
> http://people.apache.org/~markt/dev/tomcat-7/v7.0.4/
> The svn tag is:
> http://svn.apache.org/repos/asf/tomcat/tc7.0.x/tags/TOMCAT_7_0_4/
>
> As with previous votes, I have included a stable option below although
> my personal inclination is still to vote beta.
>
> The proposed 7.0.4 release is:
>
> [ ] Broken - do not release
> [ ] Alpha  - go ahead and release as 7.0.4 Alpha
> [X] Beta   - go ahead and release as 7.0.4 Beta
> [ ] Stable - go ahead and release as 7.0.4 Stable
>
> This vote will run until 10.00 UTC Wednesday 20th October (3 working days).
>
> Cheers,
>
> Mark
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: dev-h...@tomcat.apache.org
>
>

Re: [VOTE] Release Apache Tomcat 7.0.3

[Martin Dubuc]

+1 Beta

On Sat, Oct 2, 2010 at 7:47 PM, Mark Thomas  wrote:

> The proposed Apache Tomcat 7.0.3 release is now available for voting.
>
> It can be obtained from:
> http://people.apache.org/~markt/dev/tomcat-7/v7.0.3/
> The svn tag is:
> http://svn.apache.org/repos/asf/tomcat/tc7.0.x/tags/TOMCAT_7_0_3/
>
> As with previous votes, I have included a stable option below although
> my personal inclination is still to vote beta.
>
> The proposed 7.0.2 release is:
>
> [ ] Broken - do not release
> [ ] Alpha  - go ahead and release as 7.0.2 Alpha
> [X] Beta   - go ahead and release as 7.0.2 Beta
> [ ] Stable - go ahead and release as 7.0.2 Stable
>
> This vote will run for 72 hours.
>
> Cheers,
>
> Mark
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: dev-h...@tomcat.apache.org
>
>

Re: [VOTE] Release Apache Tomcat 7.0.2

[Martin Dubuc]

Looks fine on my side.

[X] Beta   - go ahead and release as 7.0.2 Beta

Martin

Re: [VOTE] Release Apache Tomcat 7.0.0 as beta

[Martin Dubuc]

+1 Beta

On Sun, Jun 13, 2010 at 6:15 PM, Mark Thomas  wrote:

> The proposed Apache Tomcat 7.0.0 release is now available for voting.
>
> It can be obtained from:
> http://people.apache.org/~markt/dev/tomcat-7/v7.0.0/
> The svn tag is:
> http://svn.apache.org/repos/asf/tomcat/tc7.0.x/tags/TOMCAT_7_0_0/
>
> Based on testing of RC4, feedback received on RC1-RC4, the currently
> open bugs against 7.0.x and the extensive refactoring that has taken
> place both of the connectors and the lifecycle componenets, I am
> proposing to release 7.0.0 as a beta release.
>
> And now for the important bit:
>
> The propsoed 7.0.0 release is
> [ ] Broken - do not release
> [ ] Alpha  - go ahead and release as 7.0.0 Alpha
> [X] Beta   - go ahead and release as 7.0.0 Beta
>
> Mark
>
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: dev-h...@tomcat.apache.org
>
>

Re: [VOTE] Release Apache Tomcat 7.0.0 as beta

[Martin Dubuc]

On Mon, Jun 14, 2010 at 5:30 PM, Mark Thomas  wrote:

> On 14/06/2010 14:27, Martin Dubuc wrote:
>
>> I have been running RC4 for a couple of days and it seems to be fairly
>> stable. I would recommend release it as 7.0.0 Beta.
>>
>> However, there is an issue with the el. It can't deal with literals, which
>> will be a problem for all applications using JSF converters. There was a
>> similar issue when Tomcat 6.0.2. came out. You can go back in the mailing
>> list archive read message in tomcat-dev Nov. 29, 2006 16:39:21 GMT and
>> titled "Problem with JSF 1.2 converters in Tomcat 6.0.2":
>>
>> http://marc.info/?l=tomcat-dev&m=116482838430229&w=2
>>
>
> Thanks for the report. The issue has been fixed.
>
>
This is great news. Thanks for addressing this issue. Looking forward to see
the next Tomcat load.


>
>  I sent a message to Rémy, who handled that issue back then, but haven't
>> got
>> news back from him.
>>
>
> I can't speak for Remy but private messages to developers tend to get
> ignored. The rule for Tomcat - as it is for all ASF projects - is if it
> didn't happen on the mailing list then it never happened. Issues should not
> be raised directly with individual committers but with the community as a
> whole either directly on the dev list or better still as a Bugzilla entry.
>
>
>
OK. Next time I'll send the message to the list directly.


>  I know we discussed el licensing a while back on the list. Hopefully it
>> will
>> not be a problem modifying that code.
>>
>
> Huh? I have no idea what you are referring to here. Tomcat's EL
> implementation is - and always has been - ALv2 licensed.
>
>
>
I confused the EL with the BCEL. Never mind.


> Mark
>
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: dev-h...@tomcat.apache.org
>
>

Re: [VOTE] Release Apache Tomcat 7.0.0 as beta

[Martin Dubuc]

I have been running RC4 for a couple of days and it seems to be fairly
stable. I would recommend release it as 7.0.0 Beta.

However, there is an issue with the el. It can't deal with literals, which
will be a problem for all applications using JSF converters. There was a
similar issue when Tomcat 6.0.2. came out. You can go back in the mailing
list archive read message in tomcat-dev Nov. 29, 2006 16:39:21 GMT and
titled "Problem with JSF 1.2 converters in Tomcat 6.0.2":

http://marc.info/?l=tomcat-dev&m=116482838430229&w=2

I sent a message to Rémy, who handled that issue back then, but haven't got
news back from him.

I know we discussed el licensing a while back on the list. Hopefully it will
not be a problem modifying that code.

Martin

On Sun, Jun 13, 2010 at 6:15 PM, Mark Thomas  wrote:

> The proposed Apache Tomcat 7.0.0 release is now available for voting.
>
> It can be obtained from:
> http://people.apache.org/~markt/dev/tomcat-7/v7.0.0/
> The svn tag is:
> http://svn.apache.org/repos/asf/tomcat/tc7.0.x/tags/TOMCAT_7_0_0/
>
> Based on testing of RC4, feedback received on RC1-RC4, the currently
> open bugs against 7.0.x and the extensive refactoring that has taken
> place both of the connectors and the lifecycle componenets, I am
> proposing to release 7.0.0 as a beta release.
>
> And now for the important bit:
>
> The propsoed 7.0.0 release is
> [ ] Broken - do not release
> [ ] Alpha  - go ahead and release as 7.0.0 Alpha
> [ ] Beta   - go ahead and release as 7.0.0 Beta
>
> Mark
>
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: dev-h...@tomcat.apache.org
>
>

Re: [VOTE] Release Tomcat 7.0.0 based on Tomcat 7.0.0-RC4

[Martin Dubuc]

I found out what the issue was. The commons-daemon-native.tar.gz file
contains archive library and object files in the unix directory that were
compiled on some other system. I would recommend that this tar file is
repackaged, doing a make clean in the unix directory before repackaging.

Martin

On Wed, Jun 9, 2010 at 12:55 PM, Mark Thomas  wrote:

> On 09/06/2010 17:49, Martin Dubuc wrote:
> > I can't get the jsvc binary to build with 7.0.0 RC4 under Fedora and
> CentOS.
>
> That would be best handled as a commons-daemon issue. I don't know
> enough about commons-daemon to comment if this is an issue for the users
> list or a JIRA issue.
>
> Mark
>
> >
> > Here is the output from make:
> >
> > (cd native; make  all)
> > make[1]: Entering directory
> >
> `/root/apache-tomcat-7.0.0-RC4/bin/commons-daemon-1.0.2-native-src/unix/native'
> > gcc -g -O2 -DOS_LINUX -DDSO_DLFCN -DCPU=\"i386\" -I/usr/java/include
> > -I/usr/java/include/linux -Wall -Wstrict-prototypes -c debug.c -o debug.o
> > gcc -g -O2 -DOS_LINUX -DDSO_DLFCN -DCPU=\"i386\" -I/usr/java/include
> > -I/usr/java/include/linux -Wall -Wstrict-prototypes -c home.c -o home.o
> > gcc -g -O2 -DOS_LINUX -DDSO_DLFCN -DCPU=\"i386\" -I/usr/java/include
> > -I/usr/java/include/linux -Wall -Wstrict-prototypes -c signals.c -o
> > signals.o
> > ar cr libservice.a arguments.o debug.o dso-dlfcn.o dso-dyld.o help.o
> home.o
> > java.o location.o replace.o locks.o signals.o
> > ar: libservice.a: Malformed archive
> > make[1]: *** [libservice.a] Error 1
> > make[1]: Leaving directory
> >
> `/root/apache-tomcat-7.0.0-RC4/bin/commons-daemon-1.0.2-native-src/unix/native'
> > make: *** [native/all] Error 2
> >
> > Martin
> >
> > On Mon, Jun 7, 2010 at 10:38 AM, Mark Thomas  wrote:
> >
> >> All,
> >>
> >> The next Tomcat 7.0.0 release candiate is ready for testing. 7.0.0-RC4
> >> can be obtained from:
> >> http://people.apache.org/~markt/dev/tomcat-7/v7.0.0-RC4/<http://people.apache.org/%7Emarkt/dev/tomcat-7/v7.0.0-RC4/>
> <http://people.apache.org/%7Emarkt/dev/tomcat-7/v7.0.0-RC4/>
> >> The svn tag is:
> >> http://svn.apache.org/repos/asf/tomcat/tc7.0.x/tags/TOMCAT_7_0_0_RC4/
> >>
> >> Please test this release candidate and provide feedback.
> >>
> >> The 7.0.0-RC4 tag is
> >> [ ] Broken - do not release
> >> [ ] Alpha  - go ahead and release 7.0.0 Alpha based on 7.0.0-RC4
> >> [ ] Beta   - go ahead and release 7.0.0 Beta based on 7.0.0-RC4
> >> [ ] Stable - go ahead and release 7.0.0 Stable based on 7.0.0-RC4
> >>
> >> The following issues were noted:
> >> -
> >>
> >> Thanks,
> >>
> >> Mark
> >>
> >>
> >>
> >> -
> >> To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
> >> For additional commands, e-mail: dev-h...@tomcat.apache.org
> >>
> >>
> >
>
>
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: dev-h...@tomcat.apache.org
>
>

Re: [VOTE] Release Tomcat 7.0.0 based on Tomcat 7.0.0-RC4

[Martin Dubuc]

I can't get the jsvc binary to build with 7.0.0 RC4 under Fedora and CentOS.

Here is the output from make:

(cd native; make  all)
make[1]: Entering directory
`/root/apache-tomcat-7.0.0-RC4/bin/commons-daemon-1.0.2-native-src/unix/native'
gcc -g -O2 -DOS_LINUX -DDSO_DLFCN -DCPU=\"i386\" -I/usr/java/include
-I/usr/java/include/linux -Wall -Wstrict-prototypes -c debug.c -o debug.o
gcc -g -O2 -DOS_LINUX -DDSO_DLFCN -DCPU=\"i386\" -I/usr/java/include
-I/usr/java/include/linux -Wall -Wstrict-prototypes -c home.c -o home.o
gcc -g -O2 -DOS_LINUX -DDSO_DLFCN -DCPU=\"i386\" -I/usr/java/include
-I/usr/java/include/linux -Wall -Wstrict-prototypes -c signals.c -o
signals.o
ar cr libservice.a arguments.o debug.o dso-dlfcn.o dso-dyld.o help.o home.o
java.o location.o replace.o locks.o signals.o
ar: libservice.a: Malformed archive
make[1]: *** [libservice.a] Error 1
make[1]: Leaving directory
`/root/apache-tomcat-7.0.0-RC4/bin/commons-daemon-1.0.2-native-src/unix/native'
make: *** [native/all] Error 2

Martin

On Mon, Jun 7, 2010 at 10:38 AM, Mark Thomas  wrote:

> All,
>
> The next Tomcat 7.0.0 release candiate is ready for testing. 7.0.0-RC4
> can be obtained from:
> http://people.apache.org/~markt/dev/tomcat-7/v7.0.0-RC4/
> The svn tag is:
> http://svn.apache.org/repos/asf/tomcat/tc7.0.x/tags/TOMCAT_7_0_0_RC4/
>
> Please test this release candidate and provide feedback.
>
> The 7.0.0-RC4 tag is
> [ ] Broken - do not release
> [ ] Alpha  - go ahead and release 7.0.0 Alpha based on 7.0.0-RC4
> [ ] Beta   - go ahead and release 7.0.0 Beta based on 7.0.0-RC4
> [ ] Stable - go ahead and release 7.0.0 Stable based on 7.0.0-RC4
>
> The following issues were noted:
> -
>
> Thanks,
>
> Mark
>
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: dev-h...@tomcat.apache.org
>
>

Re: [VOTE] Release build 6.0.20

[Martin Dubuc]

What is going to happen to the 6.0.20 load? Will it be officially released?
If it will, when and will it be identical to the load found at:
http://people.apache.org/~remm/tomcat-6/v6.0.20/?

Martin

On Wed, May 13, 2009 at 7:33 PM, Remy Maucherat  wrote:

> The candidates binaries are available here:
> http://people.apache.org/~remm/tomcat-6/v6.0.20/
>
> According to the release process, the 6.0.20 tag is:
> [ ] Broken
> [ ] Alpha
> [ ] Beta
> [ ] Stable
>
> Rémy
>
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: dev-h...@tomcat.apache.org
>
>

Re: [VOTE] Release build 6.0.13

[Martin Dubuc]

I have been using 6.0.13 for a few days. I was using 6.0.11 for some
time up to then. My app was running pretty smooth with 6.0.11. I do
not not if it is a coincidence or not, but since seitching to 6.0.13,
I have seen a few cases of Java exceptions, all seems to be related to
MySQL Connector/J connection timing out. I am wondering if anything
has changed in Tomcat since version 6.0.11 that could explain this
kind of issue.

Here is the stack trace of one such exception:

java.io.EOFException
   at com.mysql.jdbc.MysqlIO.readFully(MysqlIO.java:1963)
   at com.mysql.jdbc.MysqlIO.reuseAndReadPacket(MysqlIO.java:2375)
   at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:2874)
   at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:1623)
   at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:1715)
   at com.mysql.jdbc.Connection.execSQL(Connection.java:3243)
   at com.mysql.jdbc.Connection.execSQL(Connection.java:3172)
   at com.mysql.jdbc.Statement.executeQuery(Statement.java:1197)
   at 
org.apache.tomcat.dbcp.dbcp.DelegatingStatement.executeQuery(DelegatingStatement.java:208)
...
   at org.apache.jsp.login_jsp._jspService(login_jsp.java:77)
   at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
   at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
   at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper
.java:393)
   at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:3
20)
   at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:266)
   at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
   at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Appl
icationFilterChain.java:290)
   at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationF
ilterChain.java:206)
   at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDisp
atcher.java:654)
   at org.apache.catalina.core.ApplicationDispatcher.processRequest(Applica
tionDispatcher.java:445)
   at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationD
ispatcher.java:379)
   at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDis
patcher.java:292)
   at 
org.apache.catalina.authenticator.FormAuthenticator.forwardToLoginPage(FormAuthenticator.java:316)
   at 
org.apache.catalina.authenticator.FormAuthenticator.authenticate(FormAuthenticator.java:244)
   at 
org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:491)
   at 
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
   at 
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104)
   at 
org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:563)
   at 
org.apache.catalina.authenticator.SingleSignOn.invoke(SingleSignOn.java:393)
   at 
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
   at 
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:261)
   at 
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
   at 
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:581)
   at 
org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
   at java.lang.Thread.run(Thread.java:619)

Martin

On 5/8/07, Remy Maucherat <[EMAIL PROTECTED]> wrote:

The candidates binaries are available here:
http://people.apache.org/~remm/tomcat-6/v6.0.13/

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

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

[Martin Dubuc]

On 5/8/07, Remy Maucherat <[EMAIL PROTECTED]> wrote:

The candidates binaries are available here:
http://people.apache.org/~remm/tomcat-6/v6.0.13/

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

Rémy

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




Martin

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

Re: [VOTE] Release build 6.0.10

[Martin Dubuc]

On 2/16/07, Remy Maucherat <[EMAIL PROTECTED]> wrote:

Candidate binaries are available here:
http://people.apache.org/~remm/tomcat-6/v6.0.10/

According to the (slightly) updated release process, the 6.0.10 tag is:
[ ] Broken
[ ] Alpha
[ ] Beta
[X] Stable


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

Re: [VOTE] Release build 6.0.9

[Martin Dubuc]

On 2/5/07, Remy Maucherat <[EMAIL PROTECTED]> wrote:

Candidate binaries are available here:
http://people.apache.org/~remm/tomcat-6/v6.0.9/

According to the (slightly) updated release process, the 6.0.9 tag is:
[ ] Broken
[ ] Alpha
[X] Beta
[ ] Stable


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

Re: [VOTE] 6.0.x release process update

[Martin Dubuc]

+1

On 2/4/07, Remy Maucherat <[EMAIL PROTECTED]> wrote:

Hi,

I propose the following release process for Tomcat 6.0.x:

1. create tarball and unofficial binaries, put them on
people.apache.org/~remm/tomcat-6
2. announce candidate binaries are available for testing
3. wait 2-3 days for testing
4. call for alpha/beta/stable vote on build
5. 3 +1's later publish previously created tarball and binaries to
www.apache.org/dist/tomcat/tomcat-6
6. wait 2-3 days for voting to complete and/or for more testing
7. announce release after sync of the website

Votes ?

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: [VOTE] Release build 6.0.9 as alpha

[Martin Dubuc]

+1

On 2/1/07, Remy Maucherat <[EMAIL PROTECTED]> wrote:

Candidate binaries are available here:
http://people.apache.org/~remm/tomcat-6/v6.0.9/

Votes ?

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: New 6.0.x build

[Martin Dubuc]

+1

On 1/30/07, Remy Maucherat <[EMAIL PROTECTED]> wrote:

Remy Maucherat wrote:
> Hi,
>
> I think it would be a good idea early next week (possibly late monday)
> to do a new build and integrate the client cert fix I did a little bit
> earlier. I have seen a possible fix to do for NIO as well (41466).
>
> Comments ?

Ok, is it ok to create a new tag tomorrow evening ?

Thanks,
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: [VOTE] Release build 6.0.8 as alpha

[Martin Dubuc]

+1

On 1/18/07, Remy Maucherat <[EMAIL PROTECTED]> wrote:

http://people.apache.org/~remm/tomcat-6/v6.0.8/

Votes ?

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

[Martin Dubuc]

6.0.7 is:
[ ] Alpha
[X] Beta

Martin

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

Re: 6.0 status

[Martin Dubuc]

+1 to declare 6.0.6 beta. I am quite satisfied with its stability.

Martin

On 12/21/06, Remy Maucherat <[EMAIL PROTECTED]> wrote:

Hi,

I think it would be nice to proceed with a vote for 6.0.6 (no stable
this time either due to another batch of small glitches, but I think it
could be a beta if no further problems are found), as long as releasing
a new 6.0.7 alpha build.

Cluster: It seems some work remains on the cluster docs. What is the
plan for these ?

Admin: I didn't see anyone yet complain or ask for the admin webapp in
6.0, so I suppose it's really ok to not have it

Comments ?

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: [VOTE] Release build 6.0.6 as alpha

[Martin Dubuc]

+1

On 12/15/06, Remy Maucherat <[EMAIL PROTECTED]> wrote:

Hi,

The vote is to release Apache Tomcat 6.0.6 as alpha.
The build is located here: http://people.apache.org/~remm/tomcat-6/v6.0.6/

Votes ?

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]

Turning on logging of JSF 1.2 container inside Tomcat

[Martin Dubuc]

I have tried to turn on logging for the JSF 1.2 container inside
Tomcat 6, but haven't been successful. I followed the steps outlined
on Core JavaServer Faces book (p. 634), but the catalina.out file
doesn't contain more traces than when logging is not turned on.

I have copied the logging.properties files from jre/lib to Tomcat conf
directory. I have set java.util.logging.ConsoleHandler.level=FINEST
and I have added a line at end of file (com.sun.faces.level=FINEST) to
the logging.properties. I have also set CATALINA_OPTS in catalina.sh
to point to the updated logging.properties file in Tomcat conf
directory.

I know the logging.properties file gets loaded because when I changed
the global log level (.level) to FINEST, catalina.out contained not
just INFO level logs but also FINE level logs. However, this logging
is not valuable to me because there is way too much information
(FINEST for all modules). I would like to selectively turn on logging
for JSF.

Martin

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

Re: [VOTE] Tomcat 6.0.4 alpha build

[Martin Dubuc]

+1

On 12/6/06, Remy Maucherat <[EMAIL PROTECTED]> wrote:

Replacing the 6.0.3 tag, with fixes for the visible glitches:
http://people.apache.org/~remm/tomcat-6/v6.0.4/

Votes ?

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]

TomcatNative Libarry on Fedora Core 5

[Martin Dubuc]

Anybody been successful builidng Tomcat Native for Fedora Core 5? Is
there a place where I could retrieve the RPM?

I have tried to build. I had to modify the tcnative.spec file as
outlined by Jonas and repackage the sources of the
tomcat-native.tar.gz archive to be able to start the build process.
However, the build aborts toward the end with this error:

...
/bin/sh /usr/src/redhat/BUILD/apr-1.2.8/libtool --mode=install
/usr/bin/install -c -m 755 libtcnative-1.la
/var/tmp/tcnative-1.1.7-1-buildroot/usr/src/redhat/BUILD/apr-1.2.8/lib
libtool: install: error: cannot install `libtcnative-1.la' to a
directory not ending in /usr/local/apr/lib
make: *** [install] Error 1
error: Bad exit status from /var/tmp/rpm-tmp.13127 (%install)

Not sure why it expects directory to end with /usr/local/apr/lib. I
have built and installed APR 1.2.8 and it is installed in /usr/lib.

Martin

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

Re: DO NOT REPLY [Bug 41091] - Issue with JSF 1.2 validation when using subviews

[Martin Dubuc]

This bug is quite serious for developers that use JSF subviews in
their applications. This bug prevents the use of any validation code
in pages that use subviews.

On 11/30/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:

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=41091





--- Additional Comments From [EMAIL PROTECTED]  2006-11-30 13:44 ---
I don't think anyone will investigate this, so you should look into this 
further.

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




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

Re: Custom Faces servlet support in Tomcat 6.0.2 (JSF 1.2)

[Martin Dubuc]

I guess it would help to specify what kind of problem I am experiencing!!! ;-)

Here is the exception stack trace that gets thrown when the controller
tries to process the first JSF page:

Nov 30, 2006 10:08:31 PM org.apache.catalina.core.ApplicationContext log
SEVERE: StandardWrapper.Throwable
java.lang.IllegalStateException: Application was not properly
initialized at startup, could not find Factory:
javax.faces.context.FacesContextFactory
   at javax.faces.FactoryFinder.getFactory(FactoryFinder.java:263)
   at javax.faces.webapp.FacesServlet.init(FacesServlet.java:142)
   at myapp.CustomFacesServlet.init(CustomFacesServlet.java:36)
   at 
org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1161)
   at 
org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:981)
   at 
org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:4044)
   at 
org.apache.catalina.core.StandardContext.start(StandardContext.java:4350)
...

I don't know why the system can't find the FacesContextFactory. Any
configuration I should be doing or subclass I need to create?

Martin

On 11/30/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:

What's not working specifically?

>My Web application relies on a custom Faces servlet to handle server
>errors. This custom Faces servlet used to work well inside Tomcat
>5.5.16 but not anymore in Tomcat 6.0.2. I do not know if this problem
>is a limitation of Tomcat 6.0.2 or a change in the way JSF works.
>Could someone tell me? If this is a known problem, is there a
>workaround or are there any plans to fix it?
>
>Martin
>
>-
>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]

Custom Faces servlet support in Tomcat 6.0.2 (JSF 1.2)

[Martin Dubuc]

My Web application relies on a custom Faces servlet to handle server
errors. This custom Faces servlet used to work well inside Tomcat
5.5.16 but not anymore in Tomcat 6.0.2. I do not know if this problem
is a limitation of Tomcat 6.0.2 or a change in the way JSF works.
Could someone tell me? If this is a known problem, is there a
workaround or are there any plans to fix it?

Martin

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

Re: Problem with JSF 1.2 converters in Tomcat 6.0.2

[Martin Dubuc]

I downloaded a snapshot of the sources today and have verified that
the converter problem is solved. The page that uses a converter in
jsf-cardemo works fine now.

Thanks.

Martin

On 11/29/06, Remy Maucherat <[EMAIL PROTECTED]> wrote:

Martin Dubuc wrote:
> There seems to be a problem with Converter subclasses when running a
> JSF 1.2 Web app inside Tomcat 6.0.2. This problem can be reproduced by
> running the JSF car demo Web app that comes with the JSF 1.2
> distribution. To reproduce, in the car demo startup page, choose
> locale (click English for instance), then click More, then Buy, then
> Buy again in the choice confirmation page. The last Buy will cause a
> page submission and when invoking the converter on that page, the
> following exception will be raised:

I relaxed the check in the CVS, so you can try again.

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: Problem with JSF 1.2 converters in Tomcat 6.0.2

[Martin Dubuc]

I am running jsf-1.2_02-b03-FCS.

Martin

On 11/29/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:

What version of JSF 1.2 are you running exactly?


>There seems to be a problem with Converter subclasses when running a
>JSF 1.2 Web app inside Tomcat 6.0.2. This problem can be reproduced by
>running the JSF car demo Web app that comes with the JSF 1.2
>distribution. To reproduce, in the car demo startup page, choose
>locale (click English for instance), then click More, then Buy, then
>Buy again in the choice confirmation page. The last Buy will cause a
>page submission and when invoking the converter on that page, the
>following exception will be raised:
>
>org.apache.jasper.JasperException: /customerInfo.jsp(157,0) Cannot
>coerce value (creditCardConverter) to type
>(javax.faces.convert.Converter) for attribute converter.
>
>org.apache.jasper.compiler.DefaultErrorHandler.jspError(DefaultErrorHandler.jav
>a:40)
>
>org.apache.jasper.compiler.ErrorDispatcher.dispatch(ErrorDispatcher.java:406)
>
>org.apache.jasper.compiler.ErrorDispatcher.jspError(ErrorDispatcher.java:255)
>
>org.apache.jasper.compiler.Validator$ValidateVisitor.checkXmlAttributes(Validat
>or.java:1080)
>
>org.apache.jasper.compiler.Validator$ValidateVisitor.visit(Validator.java:818)
>
>   org.apache.jasper.compiler.Node$CustomTag.accept(Node.java:1507)
>   org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2336)
>   org.apache.jasper.compiler.Node$Visitor.visitBody(Node.java:2386)
>
>org.apache.jasper.compiler.Validator$ValidateVisitor.visit(Validator.java:837)
>
>   org.apache.jasper.compiler.Node$CustomTag.accept(Node.java:1507)
>   org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2336)
>   org.apache.jasper.compiler.Node$Visitor.visitBody(Node.java:2386)
>
>org.apache.jasper.compiler.Validator$ValidateVisitor.visit(Validator.java:837)
>
>   org.apache.jasper.compiler.Node$CustomTag.accept(Node.java:1507)
>   org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2336)
>   org.apache.jasper.compiler.Node$Visitor.visitBody(Node.java:2386)
>
>org.apache.jasper.compiler.Validator$ValidateVisitor.visit(Validator.java:837)
>
>   org.apache.jasper.compiler.Node$CustomTag.accept(Node.java:1507)
>   org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2336)
>   org.apache.jasper.compiler.Node$Visitor.visitBody(Node.java:2386)
>
>org.apache.jasper.compiler.Validator$ValidateVisitor.visit(Validator.java:837)
>
>   org.apache.jasper.compiler.Node$CustomTag.accept(Node.java:1507)
>   org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2336)
>   org.apache.jasper.compiler.Node$Visitor.visitBody(Node.java:2386)
>   org.apache.jasper.compiler.Node$Visitor.visit(Node.java:2392)
>   org.apache.jasper.compiler.Node$Root.accept(Node.java:489)
>   org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2336)
>   org.apache.jasper.compiler.Validator.validate(Validator.java:1679)
>   org.apache.jasper.compiler.Compiler.generateJava(Compiler.java:178)
>   org.apache.jasper.compiler.Compiler.compile(Compiler.java:306)
>   org.apache.jasper.compiler.Compiler.compile(Compiler.java:286)
>   org.apache.jasper.compiler.Compiler.compile(Compiler.java:273)
>
>org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:566)
>
>
>org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:314)
>
>   org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:320)
>   org.apache.jasper.servlet.JspServlet.service(JspServlet.java:266)
>   javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
>
>com.sun.faces.context.ExternalContextImpl.dispatch(ExternalContextImpl.java:413
>)
>
>com.sun.faces.application.ViewHandlerImpl.executePageToBuildView(ViewHandlerImp
>l.java:480)
>
>com.sun.faces.application.ViewHandlerImpl.renderView(ViewHandlerImpl.java:125)
>
>
>com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:13
>3)
>   com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:244)
>   com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:140)
>   javax.faces.webapp.FacesServlet.service(FacesServlet.java:245)
>
>-
>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]

Problem with JSF 1.2 converters in Tomcat 6.0.2

[Martin Dubuc]

There seems to be a problem with Converter subclasses when running a
JSF 1.2 Web app inside Tomcat 6.0.2. This problem can be reproduced by
running the JSF car demo Web app that comes with the JSF 1.2
distribution. To reproduce, in the car demo startup page, choose
locale (click English for instance), then click More, then Buy, then
Buy again in the choice confirmation page. The last Buy will cause a
page submission and when invoking the converter on that page, the
following exception will be raised:

org.apache.jasper.JasperException: /customerInfo.jsp(157,0) Cannot
coerce value (creditCardConverter) to type
(javax.faces.convert.Converter) for attribute converter.

org.apache.jasper.compiler.DefaultErrorHandler.jspError(DefaultErrorHandler.java:40)

org.apache.jasper.compiler.ErrorDispatcher.dispatch(ErrorDispatcher.java:406)

org.apache.jasper.compiler.ErrorDispatcher.jspError(ErrorDispatcher.java:255)

org.apache.jasper.compiler.Validator$ValidateVisitor.checkXmlAttributes(Validator.java:1080)

org.apache.jasper.compiler.Validator$ValidateVisitor.visit(Validator.java:818)
org.apache.jasper.compiler.Node$CustomTag.accept(Node.java:1507)
org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2336)
org.apache.jasper.compiler.Node$Visitor.visitBody(Node.java:2386)

org.apache.jasper.compiler.Validator$ValidateVisitor.visit(Validator.java:837)
org.apache.jasper.compiler.Node$CustomTag.accept(Node.java:1507)
org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2336)
org.apache.jasper.compiler.Node$Visitor.visitBody(Node.java:2386)

org.apache.jasper.compiler.Validator$ValidateVisitor.visit(Validator.java:837)
org.apache.jasper.compiler.Node$CustomTag.accept(Node.java:1507)
org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2336)
org.apache.jasper.compiler.Node$Visitor.visitBody(Node.java:2386)

org.apache.jasper.compiler.Validator$ValidateVisitor.visit(Validator.java:837)
org.apache.jasper.compiler.Node$CustomTag.accept(Node.java:1507)
org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2336)
org.apache.jasper.compiler.Node$Visitor.visitBody(Node.java:2386)

org.apache.jasper.compiler.Validator$ValidateVisitor.visit(Validator.java:837)
org.apache.jasper.compiler.Node$CustomTag.accept(Node.java:1507)
org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2336)
org.apache.jasper.compiler.Node$Visitor.visitBody(Node.java:2386)
org.apache.jasper.compiler.Node$Visitor.visit(Node.java:2392)
org.apache.jasper.compiler.Node$Root.accept(Node.java:489)
org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2336)
org.apache.jasper.compiler.Validator.validate(Validator.java:1679)
org.apache.jasper.compiler.Compiler.generateJava(Compiler.java:178)
org.apache.jasper.compiler.Compiler.compile(Compiler.java:306)
org.apache.jasper.compiler.Compiler.compile(Compiler.java:286)
org.apache.jasper.compiler.Compiler.compile(Compiler.java:273)

org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:566)

org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:314)
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:320)
org.apache.jasper.servlet.JspServlet.service(JspServlet.java:266)
javax.servlet.http.HttpServlet.service(HttpServlet.java:803)

com.sun.faces.context.ExternalContextImpl.dispatch(ExternalContextImpl.java:413)

com.sun.faces.application.ViewHandlerImpl.executePageToBuildView(ViewHandlerImpl.java:480)

com.sun.faces.application.ViewHandlerImpl.renderView(ViewHandlerImpl.java:125)

com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:133)
com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:244)
com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:140)
javax.faces.webapp.FacesServlet.service(FacesServlet.java:245)

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