RE: cvs commit: jakarta-tomcat-connectors/jk/native2/common jk_wo rker_ajp13.c

[Mladen Turk]

> -Original Message-
> From: news [mailto:[EMAIL PROTECTED]] On Behalf Of Costin Manolache
> Sent: Friday, October 04, 2002 11:13 PM
> To: [EMAIL PROTECTED]
> Subject: RE: cvs commit: 
> jakarta-tomcat-connectors/jk/native2/common jk_wo rker_ajp13.c
> 
> 
> Mladen - time for a jk2.0.2 :-) ?
> 

Why 2.0.2, did I miss the 2.0.1 ?

> I think this was a serious bug - if Nacho confirms the other 
> tests are passing, we need to push it into a milestone.
> 

I'll do the tests on my side.


> As a note: breaking the ajp connection on error is IMO the 
> best solution for now. If we start doing strong 
> authentication ( i.e. the 
> ajp extensions that Henri proposed ) - then it may be 
> expensive, and we should explore sending an error packet and 
> ignoring all further incoming messages from tomcat. The java 
> side should also check available() before sending any 
> message. That will still avoid the roundtrips. 
>

That convince me even more that we need a constant service channel
between the TC and a connector, to be able to deal with the asnyc events
on both sides.
I would like to see something like that in 2.1
 

As for the release, I was trying to push one even before your ajp
bugfix, so lets go for it.

Can we make some STATUS file explaining bug fixes since 2.0.0?

MT.



--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

staus code (-1) problem

[sunita desai]

Hi,

I have observed one peculiar problem with tomcat 4.0.3 version.
I searched the Bug Database too, to see whether this kind of problem is
detected earlier.
So I request you to kindly, go through my problem given below, and let me
know whether something similar has been observed before by any one.

To explain my problem, I have a plain Applet-Servlet communication.
The servlet just reads an backend socket connection contents and keeps
sending every 50 lines of information to the Applet.
And the applet after receiving every 50 lines, displays it in TextArea
without interpreting the data.And invokes the Servlet again as a URL.

After every invocation of Servlet when I check the
HttpConnection.getResponseCode
in the Applet, it gives me status code 200 and message "OK". And everything
is O.k, in the sense the Applet displays only the actual data or the content
being sent from Servlet.But sometimes, eventhough it is the same URL that is
being invoked and Servlet is sent the next 50 lines as ususal, I get the
Status code as "-1" and the HttpConnection.getResponseMessage returns me
"null". And when this happens the actual HTTP header content(along with some
HEX codes) is being displayed as data in the Applet display area, which
distorts the actual data coming from the Socket connection.
And then the next invocation of Servlet works fine as usual with status code
200. And the whole logic is working within a loop, so there can't be problem
with that specific invocation of Servlet.
If so then what could be the
problem. Is it that the header is not being recognised as header and it gets
interpreted as Data due to some reason? and also I have observed that when
the
header is not recognised properly,(when status code is -1) the header
"Content-length:" is missing. Because I don't see that being printed on the
Aplet display area.

But that header is present when the status code returned is 200.(I am
printing all the
headers in the java console and I see all the header being recognised).But
when the status code is -1, the headers are not recognised and not printed
on the jave console, but is being printed as data or content in Applet
display area.

But this behaviour is observed only sometimes,It happends randomly,Please
give any pointers or suggestions as to how I can avoid this problem?Please
advice.
Is this some kind of known problem with Apache tomcat version 4.0.3?

The Applet display output before and after the error looks like this:


h323-ivr-out=reroute-count:0
h323-ivr out=route:INCCARRIER|Z1_SP_NTKG|11011|0|2|Z1_HK_OP|Z1_HK_
OP1_TG2|11009|0|
Acct_in_octets:742
Acct_out_octets:806
Acct_in_packets:39


HTTP/1.1 200 OK
Content-Type: text/html
Date: Wed, 18 Sep 2002 20:07:08 GMT
Transfer-Encoding: chunked
Server: Apache Tomcat/4.0.3 (HTTP/1.1 Connector)

5c
Acct_out_packets:46
1


62
Acct_session_time:20 secs
1


7d
h323-disconnect-time=10:54:56.709 EST Sun May 5 2002
1


63
h323-disconnect-cause=10
1


69
h323-remote-address=10.15.89.150
1


5d
h323-voice-quality=0
1


78
alert-timepoint=10:54:34.559 EST Sun May 5 2002
1


70
gw-rxd-cdn=ton:1,npi:1,#:0016141756
1


76
gw-final-xlated-cdn=ton:1,npi:1,#:6141756
1


73
gw-rxd-cgn=ton:4,npi:1,pi:0,si:1,#:8381756
1


59
info-type=speech
1

I appreciate any help in this regard,
Thanks in advance,
Sunita



--
To unsubscribe, e-mail:

For additional commands, e-mail:




--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

Re: cvs commit: jakarta-tomcat-5 gump.xml

[Costin Manolache]

It's still broken - at least on my machine, the servetapi-5/examples are 
failing ( and gump uses the dist target ).

Costin

Bob Herrmann wrote:

> Oops.  Sorry.  Thanks.
> 
> On Fri, 2002-10-04 at 18:11, [EMAIL PROTECTED] wrote:
>> costin  2002/10/04 15:11:21
>> 
>>   Modified:.gump.xml
>>   Log:
>>   I think this is the correct syntax.
>>   
>>   Revision  ChangesPath
>>   1.11  +1 -1  jakarta-tomcat-5/gump.xml
>>   
>>   Index: gump.xml
>>   ===
>>   RCS file: /home/cvs/jakarta-tomcat-5/gump.xml,v
>>   retrieving revision 1.10
>>   retrieving revision 1.11
>>   diff -u -r1.10 -r1.11
>>   --- gump.xml   4 Oct 2002 18:36:54 -   1.10
>>   +++ gump.xml   4 Oct 2002 22:11:20 -   1.11
>>   @@ -12,7 +12,7 @@
>>
>>
>>
>>   -
>>   +
>>  
>>  >  project="jakarta-ant"/> >  reference="home" project="jsse"/>
>>   
>>   
>>   
>> 
>> --
>> To unsubscribe, e-mail:  
>>  For additional
>> commands, e-mail: 

-- 
Costin



--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

Re: cvs commit: jakarta-tomcat-connectors/jk/java/org/apache/jk/common ChannelSocket.java

[Costin Manolache]

Han Ming Ong wrote:

> Thanks for at least hooking up the setter correctly.
> 
> I know you folks are busy but if you can spend sometime thinking about
> the default value (which you have currently set to false) when you have
> a chance, we would truly appreciate it.

If you can give some good arguments why this value should be true and
how it won't affect anything that works now - I'm sure we can change it.


Costin


> 
> Thanks again Costin.
> 
> On Friday, October 4, 2002, at 04:33  PM, [EMAIL PROTECTED] wrote:
> 
>> costin  2002/10/04 16:33:14
>>
>>   Modified:jk/java/org/apache/jk/common ChannelSocket.java
>>   Log:
>>   Fix 13270. tcpNoDelay wasn't implemented.
>>
>>   Revision  ChangesPath
>>   1.22  +4 -2
>> jakarta-tomcat-connectors/jk/java/org/apache/jk/common/
>> ChannelSocket.java
>>
>>   Index: ChannelSocket.java
>>   ===
>>   RCS file:
>> /home/cvs/jakarta-tomcat-connectors/jk/java/org/apache/jk/common/
>> ChannelSocket.java,v
>>   retrieving revision 1.21
>>   retrieving revision 1.22
>>   diff -u -r1.21 -r1.22
>>   --- ChannelSocket.java 9 Aug 2002 20:52:37 -   1.21
>>   +++ ChannelSocket.java 4 Oct 2002 23:33:14 -   1.22
>>   @@ -105,7 +105,7 @@
>>int port=startPort;
>>InetAddress inet;
>>int serverTimeout;
>>   -boolean tcpNoDelay;
>>   +boolean tcpNoDelay=false;
>>int linger=100;
>>int socketTimeout;
>>
>>   @@ -259,7 +259,9 @@
>>s.setSoLinger( true, linger);
>>if( socketTimeout > 0 )
>>s.setSoTimeout( socketTimeout );
>>   -
>>   +if( tcpNoDelay )
>>   +s.setTcpNoDelay( true );
>>   +
>>requestCount++;
>>
>>InputStream is=new BufferedInputStream(s.getInputStream());
>>
>>
>>
>>
>> --
>> To unsubscribe, e-mail:
>> 
>> For additional commands, e-mail:
>> 
>>

-- 
Costin



--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

DO NOT REPLY [Bug 13060] - org.apache.jasper.JasperException: Unable to compile class for JSP

[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://nagoya.apache.org/bugzilla/show_bug.cgi?id=13060

org.apache.jasper.JasperException: Unable to compile class for JSP

[EMAIL PROTECTED] changed:

   What|Removed |Added

 OS/Version|Windows NT/2K   |All



--- Additional Comments From [EMAIL PROTECTED]  2002-10-05 00:56 
---
It is the same error that I see in my Linux installation. 
 
I am using Red Hat Linux 7.3 (Lastest patch to 3-Oct-2002)  
Java 1.4.1

--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

DO NOT REPLY [Bug 12783] - Coyote Connector and HTTP 1.0 Keep-Alive

[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://nagoya.apache.org/bugzilla/show_bug.cgi?id=12783

Coyote  Connector and HTTP 1.0 Keep-Alive





--- Additional Comments From [EMAIL PROTECTED]  2002-10-05 00:50 
---
When will be avaliable 4.1.13? I need it to monday :-)

--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

Re: cvs commit: jakarta-tomcat-5 gump.xml

[Bob Herrmann]

Oops.  Sorry.  Thanks. 

On Fri, 2002-10-04 at 18:11, [EMAIL PROTECTED] wrote:
> costin  2002/10/04 15:11:21
> 
>   Modified:.gump.xml
>   Log:
>   I think this is the correct syntax.
>   
>   Revision  ChangesPath
>   1.11  +1 -1  jakarta-tomcat-5/gump.xml
>   
>   Index: gump.xml
>   ===
>   RCS file: /home/cvs/jakarta-tomcat-5/gump.xml,v
>   retrieving revision 1.10
>   retrieving revision 1.11
>   diff -u -r1.10 -r1.11
>   --- gump.xml4 Oct 2002 18:36:54 -   1.10
>   +++ gump.xml4 Oct 2002 22:11:20 -   1.11
>   @@ -12,7 +12,7 @@
>
>
>  
>   -
>   +
>  
>  
>  
>   
>   
>   
> 
> --
> To unsubscribe, e-mail:   
> For additional commands, e-mail: 
-- 
Bob Herrmann <[EMAIL PROTECTED]>


--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

Re: Apache 2.0.43 is out

[Bojan Smojver]

Just ignore... I should read my e-mail from the most recent :-(

Bojan

On Sat, 2002-10-05 at 10:39, Bojan Smojver wrote:
> So, there was an MMN bump in Apache 2.0.43? From what I can tell, that's
> not the case...
> 
> Bojan
> 
> On Fri, 2002-10-04 at 18:13, Henri Gomez wrote:
> > We should provide new binaries for JK and JK2.
> > 
> > I'll do JK/JK2 for Linux boxes (and FreeBSD)
> > 
> > Who could do the same for Windows, Netware and Solaris ?
> > 
> > BTW, I'm still waiting an account on moof to build a MacOSX
> > version.
> > 
> > 
> > 
> > --
> > To unsubscribe, e-mail:   
> > For additional commands, e-mail: 
> > 
> 
> 
> 
> --
> To unsubscribe, e-mail:   
> For additional commands, e-mail: 
> 



--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

Re: Apache 2.0.43 is out

[Bojan Smojver]

So, there was an MMN bump in Apache 2.0.43? From what I can tell, that's
not the case...

Bojan

On Fri, 2002-10-04 at 18:13, Henri Gomez wrote:
> We should provide new binaries for JK and JK2.
> 
> I'll do JK/JK2 for Linux boxes (and FreeBSD)
> 
> Who could do the same for Windows, Netware and Solaris ?
> 
> BTW, I'm still waiting an account on moof to build a MacOSX
> version.
> 
> 
> 
> --
> To unsubscribe, e-mail:   
> For additional commands, e-mail: 
> 



--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

JSP 2.0's J2SE 1.4 Requirement

[Mark Roth]

It has been brought to my attention that some members of the Tomcat 
community have expressed a desire to see a requirement lower than J2SE 
1.4 in JSP 2.0.

First, let me reassure you that the JSP 2.0 specification is not final. 
  Actually, we are in Proposed Final Draft phase, and we are explicitly 
soliciting feedback!  Early feedback is always much appreciated.  As per 
the cover of the specification, the appropriate forum for feedback is 
[EMAIL PROTECTED]

Regarding the J2SE 1.4 requirement, the expert group discussed the topic 
in early August (as issue "[OTH-17] J2SE Version Requirement") and there 
was concensus from the different experts, but the EG is open to 
additional comments.  You can send mail directly to 
[EMAIL PROTECTED], or, maybe better in this case, talk 
directly to the Apache representatives to the Expert Group: Ricardo 
Rocha ([EMAIL PROTECTED]) and Geir Magnusson Jr. ([EMAIL PROTECTED]). 
In general the more feedback the rep has from his community the better 
for the Expert Group.

For what it's worth, the only technical reasons we require J2SE 1.4 are:

 1. We require support for JSR-45 (Debugging Support for Other
Languages)
 2. We declare support for Unicode 3.0 in our I18N chapter.

Actually, JSR-45 is quite important for the platform as a whole.  For 
example, it was recently pointed out to me that there's a bug report 
against Tomcat 5 because we didn't re-implement the pseudo-debug 
comments that Jasper 1 used to create, and that some tools relied on. 
Standard debugging annotations is an important enabler, and it would be 
a shame to have to wait even longer for it.

 From my perspective, the most significant reason to require J2SE 1.4 is 
that it would be best if people can write portable tag handlers that 
utilize J2SE 1.4 libraries, and be able to use them in any JSP 2.0 
application.  Do we really want to stagnate on J2SE 1.2 APIs forever?

I've compiled a list of new features in J2SE 1.3 and J2SE 1.4 that I 
believe would be of use to page authors and tag library developers that 
would decide to use JSP 2.0.  It would be awesome, IMHO, if page authors 
and tag library developers could rely on these features being present in 
any JSP 2.0 compliant container.  This list was also discussed in the 
Expert Group.

J2SE 1.3 adds (among other features):

 * Built-in JNDI
 * RMI/IIOP
 * CORBA ORB
 * PNG support (for image taglibs)
 * Various Security enhancements
 * Improved socket support
 * HTTP 1.1 client-side support
 * DynamicProxy
 * Serialization enhancements
 * Collections enhancements
 * BigDecimal and BigInteger enhancements
 * StrictMath
 * Timer API
 * Delete-on-close mode for opening zip and jar files
 * JPDA tool support

J2SE 1.4 adds (among other features):

 * XML Processing
 * New I/O APIs
 * Security: Java Cryptography integrated
 * Security: GSS-API, Certification Path API
 * Pluggable Image I/O framework
 * Print Service API
 * Standard Logging APIs
 * Long-term Persistence of JavaBeans
 * JDBC 3.0
 * Assertions
 * Preferences API
 * Chained Exception Facility
 * IPv6 Networking Support
 * JNDI enhancements
 * CORBA ORB with POA
 * *** JSR-45 (Debugging Support for Other Languages) ***
 * *** Unicode 3.0 ***
 * Currency class
 * Collections Framework enhancements
 * Built-in support for Regular Expressions

Regards,
-- 
Mark Roth, Java Software
JSP 2.0 Specification Co-Lead
Sun Microsystems, Inc.


--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

Re: cvs commit: jakarta-tomcat-connectors/jk/java/org/apache/jk/common ChannelSocket.java

[Han Ming Ong]

Thanks for at least hooking up the setter correctly.

I know you folks are busy but if you can spend sometime thinking about  
the default value (which you have currently set to false) when you have  
a chance, we would truly appreciate it.

Thanks again Costin.

On Friday, October 4, 2002, at 04:33  PM, [EMAIL PROTECTED] wrote:

> costin  2002/10/04 16:33:14
>
>   Modified:jk/java/org/apache/jk/common ChannelSocket.java
>   Log:
>   Fix 13270. tcpNoDelay wasn't implemented.
>
>   Revision  ChangesPath
>   1.22  +4 -2   
> jakarta-tomcat-connectors/jk/java/org/apache/jk/common/ 
> ChannelSocket.java
>
>   Index: ChannelSocket.java
>   ===
>   RCS file:  
> /home/cvs/jakarta-tomcat-connectors/jk/java/org/apache/jk/common/ 
> ChannelSocket.java,v
>   retrieving revision 1.21
>   retrieving revision 1.22
>   diff -u -r1.21 -r1.22
>   --- ChannelSocket.java  9 Aug 2002 20:52:37 -   1.21
>   +++ ChannelSocket.java  4 Oct 2002 23:33:14 -   1.22
>   @@ -105,7 +105,7 @@
>int port=startPort;
>InetAddress inet;
>int serverTimeout;
>   -boolean tcpNoDelay;
>   +boolean tcpNoDelay=false;
>int linger=100;
>int socketTimeout;
>
>   @@ -259,7 +259,9 @@
>s.setSoLinger( true, linger);
>if( socketTimeout > 0 )
>s.setSoTimeout( socketTimeout );
>   -
>   +if( tcpNoDelay )
>   +s.setTcpNoDelay( true );
>   +
>requestCount++;
>
>InputStream is=new BufferedInputStream(s.getInputStream());
>
>
>
>
> --
> To unsubscribe, e-mail:
> 
> For additional commands, e-mail:  
> 
>


--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

cvs commit: jakarta-tomcat-connectors/jk/java/org/apache/jk/common ChannelSocket.java

[costin]

costin  2002/10/04 16:33:14

  Modified:jk/java/org/apache/jk/common ChannelSocket.java
  Log:
  Fix 13270. tcpNoDelay wasn't implemented.
  
  Revision  ChangesPath
  1.22  +4 -2  
jakarta-tomcat-connectors/jk/java/org/apache/jk/common/ChannelSocket.java
  
  Index: ChannelSocket.java
  ===
  RCS file: 
/home/cvs/jakarta-tomcat-connectors/jk/java/org/apache/jk/common/ChannelSocket.java,v
  retrieving revision 1.21
  retrieving revision 1.22
  diff -u -r1.21 -r1.22
  --- ChannelSocket.java9 Aug 2002 20:52:37 -   1.21
  +++ ChannelSocket.java4 Oct 2002 23:33:14 -   1.22
  @@ -105,7 +105,7 @@
   int port=startPort;
   InetAddress inet;
   int serverTimeout;
  -boolean tcpNoDelay;
  +boolean tcpNoDelay=false;
   int linger=100;
   int socketTimeout;
   
  @@ -259,7 +259,9 @@
   s.setSoLinger( true, linger);
   if( socketTimeout > 0 ) 
   s.setSoTimeout( socketTimeout );
  -
  +if( tcpNoDelay )
  +s.setTcpNoDelay( true );
  +
   requestCount++;
   
   InputStream is=new BufferedInputStream(s.getInputStream());
  
  
  

--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

DO NOT REPLY [Bug 13270] - Container's AJP13 handler does not setTcpNoDelay on accept

[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://nagoya.apache.org/bugzilla/show_bug.cgi?id=13270

Container's AJP13 handler does not setTcpNoDelay on accept

[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution||FIXED



--- Additional Comments From [EMAIL PROTECTED]  2002-10-04 23:33 ---
For coyote - it's in jk2.properties ( where all jk properties are set ).
Just set channelSocket.XXX -> if you look at org.apache.jk.common.ChannelSocket
you'll find all supported properties and how they are implemented.
( each property in jk2.properties is turned into a setter ).

I fixed the code to actually do something with this setting :-)
Not sure about the default - yet.

--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

DO NOT REPLY [Bug 13263] - javax.servlet.request.key_size not following servlet spec

[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://nagoya.apache.org/bugzilla/show_bug.cgi?id=13263

javax.servlet.request.key_size not following servlet spec

[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution||FIXED



--- Additional Comments From [EMAIL PROTECTED]  2002-10-04 23:27 ---
done

--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

cvs commit: jakarta-tomcat-connectors/jk/java/org/apache/jk/common HandlerRequest.java

[costin]

costin  2002/10/04 16:26:25

  Modified:jk/java/org/apache/jk/common HandlerRequest.java
  Log:
  Fix 13263.
  
  Revision  ChangesPath
  1.17  +3 -2  
jakarta-tomcat-connectors/jk/java/org/apache/jk/common/HandlerRequest.java
  
  Index: HandlerRequest.java
  ===
  RCS file: 
/home/cvs/jakarta-tomcat-connectors/jk/java/org/apache/jk/common/HandlerRequest.java,v
  retrieving revision 1.16
  retrieving revision 1.17
  diff -u -r1.16 -r1.17
  --- HandlerRequest.java   1 Oct 2002 23:14:13 -   1.16
  +++ HandlerRequest.java   4 Oct 2002 23:26:25 -   1.17
  @@ -481,9 +481,10 @@
   /* Special case ( XXX in future API make it separate type !)
*/
   if( attributeCode == SC_A_SSL_KEY_SIZE ) {
  -// int ???... 
  +// Bug 1326: it's an Integer.
req.setAttribute("javax.servlet.request.key_size",
  -  Integer.toString(msg.getInt()));
  + new Integer( msg.getInt()));
  +//Integer.toString(msg.getInt()));
   }
   
   if( attributeCode == SC_A_REQ_ATTRIBUTE ) {
  
  
  

--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

DO NOT REPLY [Bug 12346] - Constant Refreshes crash "Framed" Web Applications in 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://nagoya.apache.org/bugzilla/show_bug.cgi?id=12346

Constant Refreshes crash "Framed"  Web Applications in TOMCAT

[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution||FIXED



--- Additional Comments From [EMAIL PROTECTED]  2002-10-04 23:22 ---
Mark as fixed. Latest CVS should have the fix.

--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

DO NOT REPLY [Bug 13320] New: - Can't get initialized static variables from servlet

[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://nagoya.apache.org/bugzilla/show_bug.cgi?id=13320

Can't get initialized static variables from servlet

   Summary: Can't get initialized static variables from servlet
   Product: Tomcat 4
   Version: 4.1.12
  Platform: PC
OS/Version: Linux
Status: NEW
  Severity: Normal
  Priority: Other
 Component: Unknown
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]


In my web application I have several static variables and try to initialize 
them using ServletContextListener defined in web.xml.
In log file I see that variables were properly initialized.
But when I send requests to servlet or JSP I get NPE, becase that variables is 
null.
Then I stop TomCat and see in files that variables were correctly finilized! 
So, they lived somewhere, but I could not get them. Tomcat server is one JVM.
I checked classloader in several cases and got the same class 
org.apache.catalina.loader.WebappClassLoader.

I got the same problem using init() method in servlet together with
load-on-startup.

It looks like for one web application defined in one context I got two 
different ServletContexts when try to initialize application using 
ServletContextListener or init()+load-on-startup. First contains init. 
parameters from both server.xml & web.xml, second only from web.xml. 
In this case I can't pass initialized variales to servlet using
ServletContext arguments.

First I got the problem in 4.0.2.

--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

cvs commit: jakarta-tomcat-connectors/http11/src/java/org/apache/coyote/http11 Http11Processor.java

[keith]

keith   2002/10/04 16:07:23

  Modified:http11/src/java/org/apache/coyote/http11
Http11Processor.java
  Log:
  Don't dup the work if it has already been done
  
  Revision  ChangesPath
  1.39  +2 -1  
jakarta-tomcat-connectors/http11/src/java/org/apache/coyote/http11/Http11Processor.java
  
  Index: Http11Processor.java
  ===
  RCS file: 
/home/cvs/jakarta-tomcat-connectors/http11/src/java/org/apache/coyote/http11/Http11Processor.java,v
  retrieving revision 1.38
  retrieving revision 1.39
  diff -u -r1.38 -r1.39
  --- Http11Processor.java  3 Oct 2002 05:24:06 -   1.38
  +++ Http11Processor.java  4 Oct 2002 23:07:23 -   1.39
  @@ -879,7 +879,8 @@
   }
   
   // Add date header
  -response.addHeader("Date", FastHttpDateFormat.getCurrentDate());
  +if (! response.containsHeader("Date"))
  +  response.addHeader("Date", FastHttpDateFormat.getCurrentDate());
   
   // Add server header
   response.addHeader("Server", Constants.SERVER);
  
  
  

--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

DO NOT REPLY [Bug 13264] - JspWriter.clear()/clearBuffer() doesn't reset the remaining buffer size as returned by JspWriter.getRemaining().

[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://nagoya.apache.org/bugzilla/show_bug.cgi?id=13264

JspWriter.clear()/clearBuffer() doesn't reset the remaining buffer size as returned by 
JspWriter.getRemaining().

[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution||INVALID



--- Additional Comments From [EMAIL PROTECTED]  2002-10-04 22:27 ---
User error.

--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

cvs commit: jakarta-tomcat-5 gump.xml

[costin]

costin  2002/10/04 15:11:21

  Modified:.gump.xml
  Log:
  I think this is the correct syntax.
  
  Revision  ChangesPath
  1.11  +1 -1  jakarta-tomcat-5/gump.xml
  
  Index: gump.xml
  ===
  RCS file: /home/cvs/jakarta-tomcat-5/gump.xml,v
  retrieving revision 1.10
  retrieving revision 1.11
  diff -u -r1.10 -r1.11
  --- gump.xml  4 Oct 2002 18:36:54 -   1.10
  +++ gump.xml  4 Oct 2002 22:11:20 -   1.11
  @@ -12,7 +12,7 @@
   
   
 
  -
  +
 
 
 
  
  
  

--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

DO NOT REPLY [Bug 13309] - Catalina calls System.exit()

[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://nagoya.apache.org/bugzilla/show_bug.cgi?id=13309

Catalina calls System.exit()





--- Additional Comments From [EMAIL PROTECTED]  2002-10-04 22:11 ---

core/StandardServer.java also calls System.exit() from it's await() method, if
it gets an IOException trying to create the ServerSocket.

--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

DO NOT REPLY [Bug 13309] - Catalina calls System.exit()

[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://nagoya.apache.org/bugzilla/show_bug.cgi?id=13309

Catalina calls System.exit()

[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|RESOLVED|REOPENED
 Resolution|INVALID |



--- Additional Comments From [EMAIL PROTECTED]  2002-10-04 22:06 ---

Using BootstrapService does not avoid the problem. BootstrapService simply wraps
around CatalinaService and Catalina itself. 

Since Catalina.java contains calls to System.exit(), it can still happen even if
you use BootstrapService. Calling System.exit() in response to an exception, no
matter how unlikely the exception, makes it dangerous to embedd Catalina into a
larger system. 

Instead of calling System.exit() in response to an exception, Catalina.java (and
other locations) should propagate an exception to the calling class, deferring
the decision to terminate the JVM as much as possible.

Ideally you should only call System.exit() from a main() method, as a means of
ensuring that all threads terminate--and it would still be nice to interrupt all
the running threads, and invoke any shutdown hooks, prior to killing the JVM.

--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

RE: cvs commit: jakarta-tomcat-connectors/jk/native2/common jk_wo rker_ajp13.c

[Costin Manolache]

Mladen - time for a jk2.0.2 :-) ?

I think this was a serious bug - if Nacho confirms the other tests
are passing, we need to push it into a milestone.

As a note: breaking the ajp connection on error is IMO the 
best solution for now. If we start doing strong authentication ( i.e. the 
ajp extensions that Henri proposed ) - then it may be expensive,
and we should explore sending an error packet and ignoring all
further incoming messages from tomcat. The java side should also
check available() before sending any message. That will still avoid
the roundtrips. 

Costin
 


Ignacio J. Ortega wrote:

> Bingo !! for me it's working now..
> 
> Need to some formal tests but seems to be working nice now.. Thanks
> 
> Saludos ,
> Ignacio J. Ortega
> 
> 
>> -Mensaje original-
>> De: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
>> Enviado el: 4 de octubre de 2002 22:29
>> Para: [EMAIL PROTECTED]
>> Asunto: cvs commit: jakarta-tomcat-connectors/jk/native2/common
>> jk_worker_ajp13.c
>> 
>> 
>> costin  2002/10/04 13:29:19
>> 
>>   Modified:jk/native2/common jk_worker_ajp13.c
>>   Log:
>>   Tentative fix for 12346.
>>   
>>   If an unrecoverable error happens ( for example when the client
>>   hits stop - the server can't send more data since the
>> connection is lost )
>>   we need to forcefully break the ajp13 connection, since tomcat can't
>>   know this and will continue to send data.
>>   
>>   This behavior is a result of the optimizations made for the
>> 'normal' case,
>>   i.e. the fact that tomcat doesn't wait for confirmation when sending
>>   chunks of data. Adding the roundtrip will have big negative
>> performance hit -
>>   and it's better to deal with the error cases.
>>   
>>   Note that the alternative ( and what seems to happen for
>> apache ) is to
>>   ignore the server errors and continue to receive chunks and
>> ignore them.
>>   That can save the ajp connection - with the price of having
>> tomcat send
>>   useless data. For a large file that may be a bad solution,
>> and tomcat will
>>   not be notified that the client had problems ( which may be
>> a usefull info ).
>>   
>>   If this doesn't fix the problem - please send me logs with ajp debug
>>   enabled. I can't reproduce it ( or run IIS ), but this is
>> clearly a bug..
>>   
>>   Revision  ChangesPath
>>   1.39  +7 -3
>> jakarta-tomcat-connectors/jk/native2/common/jk_worker_ajp13.c
>>   
>>   Index: jk_worker_ajp13.c
>>   ===
>>   RCS file:
>> /home/cvs/jakarta-tomcat-connectors/jk/native2/common/jk_worke
>> r_ajp13.c,v
>>   retrieving revision 1.38
>>   retrieving revision 1.39
>>   diff -u -r1.38 -r1.39
>>   --- jk_worker_ajp13.c  8 Jul 2002 13:34:26 -   1.38
>>   +++ jk_worker_ajp13.c  4 Oct 2002 20:29:19 -   1.39
>>   @@ -398,6 +398,8 @@
>>env->l->jkLog(env, env->l, JK_LOG_ERROR,
>>  "ajp13.service() ajpGetReply
>> unrecoverable error %d\n",
>>  err);
>>   +/* The connection is compromised, need to close it ! */
>>   +e->worker->in_error_state = 1;
>>return JK_ERR;
>>}
>>
>>   @@ -431,7 +433,8 @@
>>env->l->jkLog(env, env->l, JK_LOG_DEBUG,
>>  "ajp13.forwardST() After %d\n",err);
>>
>>   -
>>   +/* I assume no unrecoverable error can happen here -
>> we're in a single thread,
>>   +   so things are simpler ( at least in this area ) */
>>return err;
>>}
>> 
>>   @@ -498,7 +501,8 @@
>>}
>>if (err != JK_OK){
>>env->l->jkLog(env, env->l, JK_LOG_ERROR,
>>   -  "ajp13.service() Error  forwarding %s\n",
>> e->worker->mbean->name);
>>   +  "ajp13.service() Error  forwarding %s %d
>> %d\n", e->worker->mbean->name,
>>   +  e->recoverable, e->worker->in_error_state);
>>}
>>
>>if( w->mbean->debug > 0 )
>>   @@ -533,7 +537,7 @@
>>return JK_ERR;
>>}
>>
>>   -if( w->in_error_state ) {
>>   +if(  w->in_error_state ) {
>>jk2_close_endpoint(env, e);
>>/* if( w->mbean->debug > 0 )  */
>>env->l->jkLog(env, env->l, JK_LOG_INFO,
>>   
>>   
>>   
>> 
>> --
>> To unsubscribe, e-mail:
>> 
>> For additional commands, e-mail:
>> 
>> 
>>

-- 
Costin



--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

RE: cvs commit: jakarta-tomcat-connectors/jk/native2/common jk_worker_ajp13.c

[Ignacio J. Ortega]

Bingo !! for me it's working now..

Need to some formal tests but seems to be working nice now.. Thanks

Saludos ,
Ignacio J. Ortega


> -Mensaje original-
> De: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> Enviado el: 4 de octubre de 2002 22:29
> Para: [EMAIL PROTECTED]
> Asunto: cvs commit: jakarta-tomcat-connectors/jk/native2/common
> jk_worker_ajp13.c
> 
> 
> costin  2002/10/04 13:29:19
> 
>   Modified:jk/native2/common jk_worker_ajp13.c
>   Log:
>   Tentative fix for 12346.
>   
>   If an unrecoverable error happens ( for example when the client
>   hits stop - the server can't send more data since the 
> connection is lost )
>   we need to forcefully break the ajp13 connection, since tomcat can't
>   know this and will continue to send data.
>   
>   This behavior is a result of the optimizations made for the 
> 'normal' case,
>   i.e. the fact that tomcat doesn't wait for confirmation when sending
>   chunks of data. Adding the roundtrip will have big negative 
> performance hit -
>   and it's better to deal with the error cases.
>   
>   Note that the alternative ( and what seems to happen for 
> apache ) is to
>   ignore the server errors and continue to receive chunks and 
> ignore them.
>   That can save the ajp connection - with the price of having 
> tomcat send
>   useless data. For a large file that may be a bad solution, 
> and tomcat will
>   not be notified that the client had problems ( which may be 
> a usefull info ).
>   
>   If this doesn't fix the problem - please send me logs with ajp debug
>   enabled. I can't reproduce it ( or run IIS ), but this is 
> clearly a bug..
>   
>   Revision  ChangesPath
>   1.39  +7 -3  
> jakarta-tomcat-connectors/jk/native2/common/jk_worker_ajp13.c
>   
>   Index: jk_worker_ajp13.c
>   ===
>   RCS file: 
> /home/cvs/jakarta-tomcat-connectors/jk/native2/common/jk_worke
> r_ajp13.c,v
>   retrieving revision 1.38
>   retrieving revision 1.39
>   diff -u -r1.38 -r1.39
>   --- jk_worker_ajp13.c   8 Jul 2002 13:34:26 -   1.38
>   +++ jk_worker_ajp13.c   4 Oct 2002 20:29:19 -   1.39
>   @@ -398,6 +398,8 @@
>env->l->jkLog(env, env->l, JK_LOG_ERROR,
>  "ajp13.service() ajpGetReply 
> unrecoverable error %d\n",
>  err);
>   +/* The connection is compromised, need to close it ! */
>   +e->worker->in_error_state = 1;
>return JK_ERR;
>}
>
>   @@ -431,7 +433,8 @@
>env->l->jkLog(env, env->l, JK_LOG_DEBUG,
>  "ajp13.forwardST() After %d\n",err);
>
>   -
>   +/* I assume no unrecoverable error can happen here - 
> we're in a single thread,
>   +   so things are simpler ( at least in this area ) */
>return err;
>}
> 
>   @@ -498,7 +501,8 @@
>}
>if (err != JK_OK){
>env->l->jkLog(env, env->l, JK_LOG_ERROR,
>   -  "ajp13.service() Error  forwarding %s\n", 
> e->worker->mbean->name);
>   +  "ajp13.service() Error  forwarding %s %d 
> %d\n", e->worker->mbean->name,
>   +  e->recoverable, e->worker->in_error_state);
>}
>
>if( w->mbean->debug > 0 ) 
>   @@ -533,7 +537,7 @@
>return JK_ERR;
>}
>
>   -if( w->in_error_state ) {
>   +if(  w->in_error_state ) {
>jk2_close_endpoint(env, e);
>/* if( w->mbean->debug > 0 )  */
>env->l->jkLog(env, env->l, JK_LOG_INFO,
>   
>   
>   
> 
> --
> To unsubscribe, e-mail:   
> 
> For additional commands, e-mail: 
> 
> 
> 

--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

cvs commit: jakarta-tomcat-connectors/jk/native2/common jk_worker_ajp13.c

[costin]

costin  2002/10/04 13:29:19

  Modified:jk/native2/common jk_worker_ajp13.c
  Log:
  Tentative fix for 12346.
  
  If an unrecoverable error happens ( for example when the client
  hits stop - the server can't send more data since the connection is lost )
  we need to forcefully break the ajp13 connection, since tomcat can't
  know this and will continue to send data.
  
  This behavior is a result of the optimizations made for the 'normal' case,
  i.e. the fact that tomcat doesn't wait for confirmation when sending
  chunks of data. Adding the roundtrip will have big negative performance hit -
  and it's better to deal with the error cases.
  
  Note that the alternative ( and what seems to happen for apache ) is to
  ignore the server errors and continue to receive chunks and ignore them.
  That can save the ajp connection - with the price of having tomcat send
  useless data. For a large file that may be a bad solution, and tomcat will
  not be notified that the client had problems ( which may be a usefull info ).
  
  If this doesn't fix the problem - please send me logs with ajp debug
  enabled. I can't reproduce it ( or run IIS ), but this is clearly a bug..
  
  Revision  ChangesPath
  1.39  +7 -3  jakarta-tomcat-connectors/jk/native2/common/jk_worker_ajp13.c
  
  Index: jk_worker_ajp13.c
  ===
  RCS file: /home/cvs/jakarta-tomcat-connectors/jk/native2/common/jk_worker_ajp13.c,v
  retrieving revision 1.38
  retrieving revision 1.39
  diff -u -r1.38 -r1.39
  --- jk_worker_ajp13.c 8 Jul 2002 13:34:26 -   1.38
  +++ jk_worker_ajp13.c 4 Oct 2002 20:29:19 -   1.39
  @@ -398,6 +398,8 @@
   env->l->jkLog(env, env->l, JK_LOG_ERROR,
 "ajp13.service() ajpGetReply unrecoverable error %d\n",
 err);
  +/* The connection is compromised, need to close it ! */
  +e->worker->in_error_state = 1;
   return JK_ERR;
   }
   
  @@ -431,7 +433,8 @@
   env->l->jkLog(env, env->l, JK_LOG_DEBUG,
 "ajp13.forwardST() After %d\n",err);
   
  -
  +/* I assume no unrecoverable error can happen here - we're in a single thread,
  +   so things are simpler ( at least in this area ) */
   return err;
   }

  @@ -498,7 +501,8 @@
   }
   if (err != JK_OK){
   env->l->jkLog(env, env->l, JK_LOG_ERROR,
  -  "ajp13.service() Error  forwarding %s\n", e->worker->mbean->name);
  +  "ajp13.service() Error  forwarding %s %d %d\n", 
e->worker->mbean->name,
  +  e->recoverable, e->worker->in_error_state);
   }
   
   if( w->mbean->debug > 0 ) 
  @@ -533,7 +537,7 @@
   return JK_ERR;
   }
   
  -if( w->in_error_state ) {
  +if(  w->in_error_state ) {
   jk2_close_endpoint(env, e);
   /* if( w->mbean->debug > 0 )  */
   env->l->jkLog(env, env->l, JK_LOG_INFO,
  
  
  

--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

DO NOT REPLY [Bug 13309] - Catalina calls System.exit()

[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://nagoya.apache.org/bugzilla/show_bug.cgi?id=13309

Catalina calls System.exit()

[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution||INVALID



--- Additional Comments From [EMAIL PROTECTED]  2002-10-04 20:26 ---
Use the BootstrapService class (instead of Bootstrap), and the offending code
will never be called.

--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

cvs commit: jakarta-tomcat-connectors/util/java/org/apache/tomcat/util/net/puretls PureTLSImplementation.java PureTLSSocket.java PureTLSSocketFactory.java PureTLSSupport.java

[nacho]

nacho   2002/10/04 13:03:11

  Modified:util/java/org/apache/tomcat/util/net SSLImplementation.java
SSLSupport.java
  Added:   util/java/org/apache/tomcat/util/net/jsse
JSSEImplementation.java JSSESocketFactory.java
JSSESupport.java
   util/java/org/apache/tomcat/util/net/puretls
PureTLSImplementation.java PureTLSSocket.java
PureTLSSocketFactory.java PureTLSSupport.java
  Removed: util/java/org/apache/tomcat/util/net JSSEImplementation.java
JSSESocketFactory.java JSSESupport.java
PureTLSImplementation.java PureTLSSocket.java
PureTLSSocketFactory.java PureTLSSupport.java
  Log:
  Refactoring the SSL classes to his own packages, this should not harm anything and 
makes easy for tools to manage the depencies..
  
  Revision  ChangesPath
  1.1  
jakarta-tomcat-connectors/util/java/org/apache/tomcat/util/net/jsse/JSSEImplementation.java
  
  Index: JSSEImplementation.java
  ===
  /*
   * 
   *
   * The Apache Software License, Version 1.1
   *
   * Copyright (c) 1999 The Apache Software Foundation.  All rights 
   * reserved.
   *
   * Redistribution and use in source and binary forms, with or without
   * modification, are permitted provided that the following conditions
   * are met:
   *
   * 1. Redistributions of source code must retain the above copyright
   *notice, this list of conditions and the following disclaimer. 
   *
   * 2. Redistributions in binary form must reproduce the above copyright
   *notice, this list of conditions and the following disclaimer in
   *the documentation and/or other materials provided with the
   *distribution.
   *
   * 3. The end-user documentation included with the redistribution, if
   *any, must include the following acknowlegement:  
   *   "This product includes software developed by the 
   *Apache Software Foundation (http://www.apache.org/)."
   *Alternately, this acknowlegement may appear in the software itself,
   *if and wherever such third-party acknowlegements normally appear.
   *
   * 4. The names "The Jakarta Project", "Tomcat", and "Apache Software
   *Foundation" must not be used to endorse or promote products derived
   *from this software without prior written permission. For written 
   *permission, please contact [EMAIL PROTECTED]
   *
   * 5. Products derived from this software may not be called "Apache"
   *nor may "Apache" appear in their names without prior written
   *permission of the Apache Group.
   *
   * THIS SOFTWARE IS PROVIDED ``AS IS'' AND ANY EXPRESSED OR IMPLIED
   * WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
   * OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
   * DISCLAIMED.  IN NO EVENT SHALL THE APACHE SOFTWARE FOUNDATION OR
   * ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
   * SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
   * LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF
   * USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
   * ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
   * OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT
   * OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
   * SUCH DAMAGE.
   * 
   *
   * This software consists of voluntary contributions made by many
   * individuals on behalf of the Apache Software Foundation.  For more
   * information on the Apache Software Foundation, please see
   * .
   *
   * [Additional notices, if required by prior licensing conditions]
   *
   */ 
  
  package org.apache.tomcat.util.net.jsse;
  
  import org.apache.tomcat.util.net.SSLImplementation;
  import org.apache.tomcat.util.net.SSLSupport;
  import org.apache.tomcat.util.net.ServerSocketFactory;
  import java.io.*;
  import java.net.*;
  import javax.net.ssl.SSLSocket;
  
  /* JSSEImplementation:
  
 Concrete implementation class for JSSE
  
 @author EKR
  */

  public class JSSEImplementation extends SSLImplementation
  {
  public JSSEImplementation() throws ClassNotFoundException {
// Check to see if JSSE is floating around somewhere
Class.forName("javax.net.ssl.SSLServerSocketFactory");
  }
  
  
  public String getImplementationName(){
return "JSSE";
  }

  public ServerSocketFactory getServerSocketFactory()
  {
return new JSSESocketFactory();
  } 
  
  public SSLSupport getSSLSupport(Socket s)
  {
return new JSSESupport((SSLSocket)s);

cvs commit: jakarta-tomcat-connectors/util/java/org/apache/tomcat/util/net/puretls - New directory

[nacho]

nacho   2002/10/04 12:59:59

  jakarta-tomcat-connectors/util/java/org/apache/tomcat/util/net/puretls - New 
directory

--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

cvs commit: jakarta-tomcat-connectors/util/java/org/apache/tomcat/util/net/jsse - New directory

[nacho]

nacho   2002/10/04 12:59:41

  jakarta-tomcat-connectors/util/java/org/apache/tomcat/util/net/jsse - New directory

--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

DO NOT REPLY [Bug 13270] - Container's AJP13 handler does not setTcpNoDelay on accept

[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://nagoya.apache.org/bugzilla/show_bug.cgi?id=13270

Container's AJP13 handler does not setTcpNoDelay on accept





--- Additional Comments From [EMAIL PROTECTED]  2002-10-04 19:44 ---
Thanks Henri.

Certainly, Mac OS X's IP stack can be further optimized so that the
interaction between Nagle and delayed ack can be minimized (Linux, which I have 
tested, didn't suffer as much).
But I hope it doesn't take away the fact that ajp13 protocol lends itself
to be a good candidate for turning on TCP_NODELAY, by default.

Anyway, I took your advice and tried to add tcpnoDelay to true.
Unfortunately, it didn't work. I tried both with 
CoyoteConnector+JKCoyoteHandler and simply Ajp13Connector. Looking at the 
source codes, there is nowhere in either ChannelSocket.java nor Ajp13.java
that turns TCP_NODELAY on/off. As well, the docs didn't mention that
"tcpnoDelay" is a valid attribute in the XML element .

Here's part of the server.xml








--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

cvs commit: jakarta-tomcat-connectors/coyote/src/java/org/apache/coyote/tomcat5 CoyoteAdapter.java

[nacho]

nacho   2002/10/04 12:27:09

  Modified:coyote/src/java/org/apache/coyote/tomcat5 CoyoteAdapter.java
  Log:
  Porting Fixes done for Tomcat 4
  
  Revision  ChangesPath
  1.3   +9 -14 
jakarta-tomcat-connectors/coyote/src/java/org/apache/coyote/tomcat5/CoyoteAdapter.java
  
  Index: CoyoteAdapter.java
  ===
  RCS file: 
/home/cvs/jakarta-tomcat-connectors/coyote/src/java/org/apache/coyote/tomcat5/CoyoteAdapter.java,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -r1.2 -r1.3
  --- CoyoteAdapter.java2 Oct 2002 05:30:50 -   1.2
  +++ CoyoteAdapter.java4 Oct 2002 19:27:09 -   1.3
  @@ -246,19 +246,14 @@
   protected void postParseRequest(Request req, CoyoteRequest request,
   Response res, CoyoteResponse response)
   throws IOException {
  -
  -request.setSecure(connector.getSecure());
  -req.scheme().setString(connector.getScheme());
  +// XXX the processor needs to set a correct scheme and port prior to this 
point, 
  +// in ajp13 protocols dont make sense to get the port from the connector..
  +request.setSecure(req.scheme().equals("https"));
   
   request.setAuthorization
   (req.getHeader(Constants.AUTHORIZATION_HEADER));
  -
  -// Replace the default port if we are in secure mode
  -if (req.getServerPort() == 80 
  -&& connector.getScheme().equals("https")) {
  -req.setServerPort(443);
  -}
  -
  +// FIXME: the code below doesnt belongs to here, this is only  have sense 
  +// in Http11, not in ajp13..
   // At this point the Host header has been processed.
   // Override if the proxyPort/proxyHost are set 
   String proxyName = connector.getProxyName();
  
  
  

--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

cvs commit: jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/runtime PageContextImpl.java

[luehe]

luehe   2002/10/04 12:21:44

  Modified:jasper2/src/share/org/apache/jasper/compiler Generator.java
   jasper2/src/share/org/apache/jasper/runtime
PageContextImpl.java
  Log:
  Fixed regression (caused by fix for 12638), which prevented error pages in HTML
  format from being displayed properly.
  
  Revision  ChangesPath
  1.107 +6 -4  
jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/compiler/Generator.java
  
  Index: Generator.java
  ===
  RCS file: 
/home/cvs/jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/compiler/Generator.java,v
  retrieving revision 1.106
  retrieving revision 1.107
  diff -u -r1.106 -r1.107
  --- Generator.java3 Oct 2002 23:50:11 -   1.106
  +++ Generator.java4 Oct 2002 19:21:44 -   1.107
  @@ -492,8 +492,10 @@
if (pageInfo.isSession())
out.printil("HttpSession session = null;");
   
  - if (pageInfo.isIsErrorPage())
  + if (pageInfo.isIsErrorPage()) {
   out.printil("Throwable exception = (Throwable) 
request.getAttribute(\"javax.servlet.jsp.jspException\");");
  + out.printil("request.setAttribute(\"javax.servlet.error.exception\", 
exception);");
  + }
   
out.printil("ServletContext application = null;");
out.printil("ServletConfig config = null;");
  
  
  
  1.26  +10 -5 
jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/runtime/PageContextImpl.java
  
  Index: PageContextImpl.java
  ===
  RCS file: 
/home/cvs/jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/runtime/PageContextImpl.java,v
  retrieving revision 1.25
  retrieving revision 1.26
  diff -u -r1.25 -r1.26
  --- PageContextImpl.java  4 Oct 2002 00:30:48 -   1.25
  +++ PageContextImpl.java  4 Oct 2002 19:21:44 -   1.26
  @@ -554,9 +554,14 @@
   
if (errorPageURL != null && !errorPageURL.equals("")) {
   
  - // Set request attributes
  + // Set request attributes.
  + // Do not set the javax.servlet.error.exception attribute here
  + // (instead, set in the generated servlet code for the error page)
  + // in order to prevent the ErrorReportValve, which is invoked as
  + // part of forwarding the request to the error page, from 
  + // throwing it if the response has not been committed (the response
  + // will have been committed if the error page is a JSP page).
request.setAttribute("javax.servlet.jsp.jspException", t);
  - request.setAttribute("javax.servlet.error.exception", t);
request.setAttribute("javax.servlet.error.status_code",
new Integer(HttpServletResponse.SC_INTERNAL_SERVER_ERROR));
request.setAttribute("javax.servlet.error.request_uri",
  
  
  

--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

RE: Startup problem

[Ignacio J. Ortega]

This is a user question go ask in [EMAIL PROTECTED]

Saludos ,
Ignacio J. Ortega


> -Mensaje original-
> De: [EMAIL PROTECTED] 
> [mailto:[EMAIL PROTECTED]]
> Enviado el: 15 de octubre de 2002 17:22
> Para: [EMAIL PROTECTED]
> Asunto: Startup problem
> 
> 
> Hi,
> 
>   I installed Tomcat4.0 on Wint Nt .I have done all the path 
> and classpath
> settigs. While starting  i had problem ,Tomcat window appears 
> and after a
> while it disappears.i could't able to start the Tomcat.Could 
> u please help
> me ?
> 
> 
> -subba
> 
> 

--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

DO NOT REPLY [Bug 13309] New: - Catalina calls System.exit()

[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://nagoya.apache.org/bugzilla/show_bug.cgi?id=13309

Catalina calls System.exit()

   Summary: Catalina calls System.exit()
   Product: Tomcat 4
   Version: 4.1.10
  Platform: All
OS/Version: All
Status: NEW
  Severity: Major
  Priority: Other
 Component: Catalina
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]


Catalina calls System.exit()from several locations:
  -- core/StandardServer calls it
  -- several classes in startup call it

This makes life difficult for application developers who wish to embedd Tomcat
into their application, such as to attach a web interface to an application
which is otherwise not a web application.

In particular it may not be a critical failure if tomcat fails to start up
successfully, except that Catalina calls System.exit. It may also be a
recoverable error, as the containing system could try re-starting it with
different arguments. 

Please note that the documentation for CatalinaService at least in part implies
that it is expected to be used in this fashion: "designed to allow easier
wrapping by system level components".

So, I think Catalina should not call System.exit(), or should only call
System.exit() from a loader which is not intended to be wrapped by a system
level component.

--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

cvs commit: jakarta-tomcat-5 gump.xml

[bobh]

bobh2002/10/04 11:36:54

  Modified:.gump.xml
  Log:
  This should get gump builds working again.  Thanks to Stefan Bodewig!
  
  Revision  ChangesPath
  1.10  +3 -1  jakarta-tomcat-5/gump.xml
  
  Index: gump.xml
  ===
  RCS file: /home/cvs/jakarta-tomcat-5/gump.xml,v
  retrieving revision 1.9
  retrieving revision 1.10
  diff -u -r1.9 -r1.10
  --- gump.xml  23 Sep 2002 19:33:08 -  1.9
  +++ gump.xml  4 Oct 2002 18:36:54 -   1.10
  @@ -10,7 +10,9 @@
 
   org.apache.catalina
   
  -
  +
  +  
  +
 
 
 
  
  
  

--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

cvs commit: jakarta-tomcat/src/share/org/apache/tomcat/modules/loggers AccessLogInterceptor.java

[keith]

keith   2002/10/04 11:33:11

  Modified:src/share/org/apache/tomcat/modules/loggers
AccessLogInterceptor.java
  Log:
  Use CRLF on Win32 for access log
  
  Revision  ChangesPath
  1.8   +2 -1  
jakarta-tomcat/src/share/org/apache/tomcat/modules/loggers/AccessLogInterceptor.java
  
  Index: AccessLogInterceptor.java
  ===
  RCS file: 
/home/cvs/jakarta-tomcat/src/share/org/apache/tomcat/modules/loggers/AccessLogInterceptor.java,v
  retrieving revision 1.7
  retrieving revision 1.8
  diff -u -r1.7 -r1.8
  --- AccessLogInterceptor.java 15 Oct 2001 01:58:21 -  1.7
  +++ AccessLogInterceptor.java 4 Oct 2002 18:33:11 -   1.8
  @@ -125,6 +125,7 @@
   private static boolean useFlush = false;
   private static String logformat = LOGFORMAT_COMBINED;
   private static DateFormat df = new SimpleDateFormat("dd/MMM/:HH:mm:ss");
  +private static String crlf = System.getProperty("line.separator");
   
   /** Creates a new AccessLogInterceptor */
   public AccessLogInterceptor() {}
  @@ -277,7 +278,7 @@
fw.write(c);
}
}
  - fw.write('\n');
  + fw.write(crlf);
if (useFlush) {
fw.flush();
}
  
  
  

--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

DO NOT REPLY [Bug 13307] New: - Need to specify classLoader when loading resources...

[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://nagoya.apache.org/bugzilla/show_bug.cgi?id=13307

Need to specify classLoader when loading resources...

   Summary: Need to specify classLoader when loading resources...
   Product: Tomcat 4
   Version: 4.1.12
  Platform: PC
OS/Version: Windows NT/2K
Status: NEW
  Severity: Normal
  Priority: Other
 Component: Catalina
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]


In StringManager.java(line 115), ResourceBundle is used to load in a resource 
file.  No classloader is specified on this call, this causes the ClassLoader 
that ResourceBundle.class was loaded with to be used.

I'm trying to embed Tomcat into my application by using my own ClassLoader.  
Things work fine, except when Tomcat uses system classes to load resources.  
Since the system classes, like ResourceBundle, were loaded prior to my 
ClassLoader...Tomcat can't find the resource specified in its own jar files.

A more flexable approach would be to call ResourceBundle.getBundle
("bundlename", defaultLocale, getClass().getClassLoader()).

This would enable folks to more easily embed the catalina code in their systems.

Thanks,
Ray

--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

Re: [5.0] [VOTE] Removal of the LE distribution

[Bill Barker]

- Original Message -
From: "Jean-Francois Arcand" <[EMAIL PROTECTED]>
To: "Tomcat Developers List" <[EMAIL PROTECTED]>
Sent: Friday, October 04, 2002 6:39 AM
Subject: Re: [5.0] [VOTE] Removal of the LE distribution


>
>
> Bill Barker wrote:
>
> >- Original Message -
> >From: "Remy Maucherat" <[EMAIL PROTECTED]>
> >To: "Tomcat Developers List" <[EMAIL PROTECTED]>
> >Sent: Thursday, October 03, 2002 7:50 PM
> >Subject: Re: [5.0] [VOTE] Removal of the LE distribution
> >
> >
> >
> >
> >>Costin Manolache wrote:
> >>
> >>
> >>>Remy Maucherat wrote:
> >>>
> >>>
> >>>
> >>>
> Hi all,
> 
> Before starting to release 5.0.x milestones, I would like to propose
> having only one distribution for Tomcat 5.0.x, and standardize on what
> the LE distribution contains (so well, it's more the other
distribution
> which gets removed).
> 
> It has some advantages:
> - it is slightly smaller (less these days now that the XML parser has
to
> be shipped again with Tomcat)
> - runs as-is on JDK 1.3 (because of the Xerces inclusion)
> - 99% Apache or Apache-style licence (the JDBC 2 standard extension is
> needed for JDK 1.3 DataSource support :-()
> - less user confusion
> 
> The main "problem" is that the user will need additional downloads for
> some of the more advanced features, and the package will also not run
on
> JDK 1.2 as is (but from what I've seen, JDK 1.2 compatibility may not
be
> a priority for developers).
> 
> 
> +1 [X] Yes, remove the LE distribution
> -1 [ ] No, keep both distributions
> 
> 
> 
> >>>What would it take to be 100% Apache-style licence ? Can we do some
> >>>introspection tricks or conditional compilation to solve this ?
> >>>
> >>>
> >>I can remove the JDBC SE JAR, but then the JDBC connection pooling
> >>features won't work right out of the box on JDK 1.3 (assuming it is
> >>possible to run JDK 1.3 with TC 5).
> >>
> >>A great blinking warning should be added to the download page and the
> >>release notes if we do that.
> >>
> >>If somehow the Catalina (with JSP 2 support) adapter requires JDK 1.4,
> >>then JDBC SE can be removed.
> >>
> >>
> >
> >Well, it seems that this has already been done without a [VOTE].  After a
> >long time away from 5.0, I attempted to build it, only to discover that
it
> >can't be built any more.  As a result, I'm now (belatedly) posting my -1
to
> >R1.2 of o.a.c.core.StandardWrapper.java. and R1.1 of
o.a.c.u.SecurityUtil.
> >Please change to a version that compiles under 1.2 at least until there
is a
> >[VOTE] to change the target version.  AFAIK, the target version is still
the
> >same as 4.x (e.g. 1.2).
> >
> I'm confuse. The Tomcat 4.0-4.1 documentatopm requires JDK 1.3 for
> compilling the source code:
>
> " This subproject contains the source code Tomcat 4.0, a server that
implements
> the Servlet 2.3 and JSP 1.2 Specifications from Java Software.  In order
to
> build a binary distribution version of the container from a source
> distribution, you must have a Java Development Kit (JDK) for version 1.3
(or
> later) downloaded and installed (version 1.3.1 recommended), and do the
> following:"
>
> Tomcat should run on 1.2, but should it compile?

Sorry, I missed that one. -1 withdrawn.

>
> -- Jeanfrancois
>
>
>
>
> >
> >
> >
> >>Remy
> >>
> >>
> >>--
> >>To unsubscribe, e-mail:
> >>
> >>
> >
> >
> >
> >>For additional commands, e-mail:
> >>
> >>
> >
> >
> >
> >
> >
> >--
> >To unsubscribe, e-mail:

> >For additional commands, e-mail:

> >
> >
> >
> >
>


--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

Re: Apache 2.0.43 is out

[Han Ming Ong]

Jean-Frederic,

Just wondering if the module was compiled with '-g -O2' flag (default)  
or with '-Os' flag? Apple's doc seems to prefer that '-Os' flag is  
used. But if size is not a problem, '-O2' is fine as well.

http://developer.apple.com/techpubs/macosx/DeveloperTools/ 
ProjectBuilder/ProjectBuilder.help/Contents/Resources/English.lproj/C/ 
Optimizing.html


Thank, Han Ming

On Friday, October 4, 2002, at 09:48  AM, jean-frederic clere wrote:

> Clere, Jean-Frederic wrote:
>> Henri Gomez wrote:
>>> We should provide new binaries for JK and JK2.
>>>
>>> I'll do JK/JK2 for Linux boxes (and FreeBSD)
>>>
>>> Who could do the same for Windows, Netware and Solaris ?
>> On Solaris8 the binary of httpd is not yet available.
>>>
>>> BTW, I'm still waiting an account on moof to build a MacOSX
>>> version.
>> That is the same for MacOSX.
>> On moof I will try to build the httpd and I will put it under  
>> /Volumes/data/Users/jfclere/apache43 so that you can use it.
>
>
> I have the mod_jk.so for MacOSX ready. I will put it in  
> http://jakarta.apache.org/builds/jakarta-tomcat-connectors/jk/release/ 
> v1.2.0/bin/macosx/
> on Monday.
>
>>>
>>>
>>>
>>> -- 
>>> To unsubscribe, e-mail:
>>> 
>>> For additional commands, e-mail:  
>>> 
>>>
>>>
>> -- 
>> To unsubscribe, e-mail:
>> 
>> For additional commands, e-mail:  
>> 
>
>
>
>
> --
> To unsubscribe, e-mail:
> 
> For additional commands, e-mail:  
> 
>


--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

Re: Apache 2.0.43 is out

[jean-frederic clere]

Clere, Jean-Frederic wrote:
> Henri Gomez wrote:
> 
>> We should provide new binaries for JK and JK2.
>>
>> I'll do JK/JK2 for Linux boxes (and FreeBSD)
>>
>> Who could do the same for Windows, Netware and Solaris ?
> 
> 
> On Solaris8 the binary of httpd is not yet available.
> 
>>
>> BTW, I'm still waiting an account on moof to build a MacOSX
>> version.
> 
> 
> That is the same for MacOSX.
> On moof I will try to build the httpd and I will put it under 
> /Volumes/data/Users/jfclere/apache43 so that you can use it.


I have the mod_jk.so for MacOSX ready. I will put it in 
http://jakarta.apache.org/builds/jakarta-tomcat-connectors/jk/release/v1.2.0/bin/macosx/
on Monday.

> 
>>
>>
>>
>> -- 
>> To unsubscribe, e-mail:   
>> 
>> For additional commands, e-mail: 
>> 
>>
>>
> 
> 
> 
> 
> -- 
> To unsubscribe, e-mail:   
> 
> For additional commands, e-mail: 
> 
> 
> 




--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

DO NOT REPLY [Bug 13300] - Incorrect system id's in various xml files

[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://nagoya.apache.org/bugzilla/show_bug.cgi?id=13300

Incorrect system id's in various xml files





--- Additional Comments From [EMAIL PROTECTED]  2002-10-04 16:38 ---
Created an attachment (id=3355)
Fix for incorrect system id's

--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

DO NOT REPLY [Bug 13300] New: - Incorrect system id's in various xml files

[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://nagoya.apache.org/bugzilla/show_bug.cgi?id=13300

Incorrect system id's in various xml files

   Summary: Incorrect system id's in various xml files
   Product: Tomcat 4
   Version: Nightly Build
  Platform: All
OS/Version: All
Status: NEW
  Severity: Minor
  Priority: Other
 Component: Webapps:Examples
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]


4.1.12 and current CVS has a couple of incorrect system ID URLs in tester, admin
and example webapps.  I'll attach a trivial patch.

--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

Re: Is Compile Failure? was Re: Need some clarifications

[Han Ming Ong]

On Friday, October 4, 2002, at 12:55  AM, Henri Gomez wrote:

> Steve Downey wrote:
>> On Thursday 03 October 2002 12:14 pm, Henri Gomez wrote:
>>> Steve Downey wrote:
>>>
 Actually, with the recent release of commons-logging, we should be  
 able
 to get rid of the explicit LogKit and Log4J. They're there so as to  
 get a
 complete build of commons-logging. Tomcat 5 itself doesn't use  
 either
 directly.

 Xerces is a different issue. There was a bug that was preventing  
 Tomcat
 from migrating to the latest version. Unfortunately, I no longer  
 remember
 the details. Anyone know why we're using 2.1.0 instead of 2.2.0?
>>>
>>> From what I experienced with Xerces j 2.2.0 it seems it does
>>> much more validity check and for instance found a '--' somewhere
>>> in comments (1 EUR to the first who find where).
>>>
>>> Previous version of Xerces or crimson didn't got that problem.
>>>
>>> if we could see which xml/dtd/tld is reported buggy, which
>>> will able to see if it's a bug or a features (ie a more strict
>>> check of xml rules)
>> OK, from the 'this shouldn't work department', this patch 'fixes' the  
>> problem:
>> Index: ./jsr152/src/share/dtd/web-jsptaglibrary_1_2.dtd
>> ===
>> RCS file:  
>> /home/cvspublic/jakarta-servletapi-5/jsr152/src/share/dtd/web- 
>> jsptaglibrary_1_2.dtd,v
>> retrieving revision 1.1.1.1
>> diff -u -r1.1.1.1 web-jsptaglibrary_1_2.dtd
>> --- ./jsr152/src/share/dtd/web-jsptaglibrary_1_2.dtd13 Aug 2002  
>> 16:20:58 -  1.1.1.1
>> +++ ./jsr152/src/share/dtd/web-jsptaglibrary_1_2.dtd3 Oct 2002  
>> 20:42:30 -
>> @@ -304,6 +304,7 @@
>>   java.lang.String is default.
>>  declare  Whether the variable is declared or not.
>> +
>>   True is the default.
>>  scopeThe scope of the scripting varaible
>> Something quite strange is going on.
>
> You just add an empty line in this dtd and it works now ?
>
> I was thinking it could be with -- in some dtd, ie
>  line in web-app_2_3.dtd :
>
I checked that long line before. It's made up of underscores.


--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

cvs commit: jakarta-tomcat-connectors/jk/native2/server/apache13 mod_jk2.c

[mturk]

mturk   2002/10/04 09:23:42

  Modified:jk/native2/server/apache13 mod_jk2.c
  Log:
  Uuups wrong editor :) CRLF.
  
  Revision  ChangesPath
  1.24  +11 -11jakarta-tomcat-connectors/jk/native2/server/apache13/mod_jk2.c
  
  Index: mod_jk2.c
  ===
  RCS file: /home/cvs/jakarta-tomcat-connectors/jk/native2/server/apache13/mod_jk2.c,v
  retrieving revision 1.23
  retrieving revision 1.24
  diff -u -r1.23 -r1.24
  --- mod_jk2.c 4 Oct 2002 16:10:38 -   1.23
  +++ mod_jk2.c 4 Oct 2002 16:23:42 -   1.24
  @@ -73,7 +73,7 @@
   #include "http_main.h"
   #include "http_log.h"
   #include "util_script.h"
  -#include "http_conf_globals.h"
  +#include "http_conf_globals.h"
   
   /*
* Jakarta (jk_) include files
  @@ -173,8 +173,8 @@
   /* Create the logger . We use the default jk logger, will output
  to a file. Check the logger for default settings.
   */
  -jkb=env->createBean2( env, env->globalPool, "logger.file", "");
  -env->alias( env, "logger.file:", "logger");
  +jkb=env->createBean2( env, env->globalPool, "logger.file", "");
  +env->alias( env, "logger.file:", "logger");
   env->alias( env, "logger.file:", "logger:"); 
   if( jkb==NULL ) {
   fprintf(stderr, "Error creating logger ");
  @@ -198,14 +198,14 @@
   return JK_ERR;
   }
   
  -/* serverRoot via ap_server_root
  - */
  -workerEnv->initData->add( env, workerEnv->initData, "serverRoot",
  - workerEnv->pool->pstrdup( env, workerEnv->pool, 
ap_server_root));
  -
  +/* serverRoot via ap_server_root
  + */
  +workerEnv->initData->add( env, workerEnv->initData, "serverRoot",
  + workerEnv->pool->pstrdup( env, workerEnv->pool, 
ap_server_root));
  +
/* Local initialization.
  - */
  -env->l->jkLog(env, env->l, JK_LOG_INFO, "Set serverRoot %s\n", ap_server_root); 

  + */
  +env->l->jkLog(env, env->l, JK_LOG_INFO, "Set serverRoot %s\n", ap_server_root); 
   
   workerEnv->_private = (void *)s;
   
  
  
  

--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

cvs commit: jakarta-tomcat-connectors/jk/native2/common jk_uriEnv.c

[mturk]

mturk   2002/10/04 09:13:15

  Modified:jk/native2/common jk_uriEnv.c
  Log:
  Compute the suffix_len for the extracted suffix.
  
  Revision  ChangesPath
  1.37  +2 -0  jakarta-tomcat-connectors/jk/native2/common/jk_uriEnv.c
  
  Index: jk_uriEnv.c
  ===
  RCS file: /home/cvs/jakarta-tomcat-connectors/jk/native2/common/jk_uriEnv.c,v
  retrieving revision 1.36
  retrieving revision 1.37
  diff -u -r1.36 -r1.37
  --- jk_uriEnv.c   3 Oct 2002 01:33:14 -   1.36
  +++ jk_uriEnv.c   4 Oct 2002 16:13:15 -   1.37
  @@ -335,6 +335,7 @@
   uriEnv->prefix  = uri;
   uriEnv->prefix_len  =strlen( uriEnv->prefix );
   uriEnv->suffix  = asterisk + 3;
  +uriEnv->suffix_len  = strlen(asterisk + 3);
   uriEnv->match_type  = MATCH_TYPE_SUFFIX;
   if( uriEnv->mbean->debug > 0 ) {
   env->l->jkLog(env, env->l, JK_LOG_DEBUG,
  @@ -345,6 +346,7 @@
   /* general suffix rule /context/prefix/ASTERISKextraData */
   asterisk[1] = '\0';
   uriEnv->suffix  = asterisk + 2;
  +uriEnv->suffix_len  = strlen(asterisk + 2);
   uriEnv->prefix  = uri;
   uriEnv->prefix_len  =strlen( uriEnv->prefix );
   uriEnv->match_type = MATCH_TYPE_GENERAL_SUFFIX;
  
  
  

--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

cvs commit: jakarta-tomcat-connectors/jk/native2/server/apache13 mod_jk2.c

[mturk]

mturk   2002/10/04 09:10:38

  Modified:jk/native2/server/apache13 mod_jk2.c
  Log:
  Fix the logger.file, using ap_server_root like on Apache2.
  
  Revision  ChangesPath
  1.23  +14 -8 jakarta-tomcat-connectors/jk/native2/server/apache13/mod_jk2.c
  
  Index: mod_jk2.c
  ===
  RCS file: /home/cvs/jakarta-tomcat-connectors/jk/native2/server/apache13/mod_jk2.c,v
  retrieving revision 1.22
  retrieving revision 1.23
  diff -u -r1.22 -r1.23
  --- mod_jk2.c 27 Sep 2002 13:18:26 -  1.22
  +++ mod_jk2.c 4 Oct 2002 16:10:38 -   1.23
  @@ -73,6 +73,7 @@
   #include "http_main.h"
   #include "http_log.h"
   #include "util_script.h"
  +#include "http_conf_globals.h"
   
   /*
* Jakarta (jk_) include files
  @@ -172,7 +173,9 @@
   /* Create the logger . We use the default jk logger, will output
  to a file. Check the logger for default settings.
   */
  -jkb=env->createBean2( env, env->globalPool, "logger.file", "");
  +jkb=env->createBean2( env, env->globalPool, "logger.file", "");
  +env->alias( env, "logger.file:", "logger");
  +env->alias( env, "logger.file:", "logger:"); 
   if( jkb==NULL ) {
   fprintf(stderr, "Error creating logger ");
   return JK_ERR;
  @@ -195,14 +198,17 @@
   return JK_ERR;
   }
   
  -/* Local initialization.
  - */
  +/* serverRoot via ap_server_root
  + */
  +workerEnv->initData->add( env, workerEnv->initData, "serverRoot",
  + workerEnv->pool->pstrdup( env, workerEnv->pool, 
ap_server_root));
  +
  + /* Local initialization.
  + */
  +env->l->jkLog(env, env->l, JK_LOG_INFO, "Set serverRoot %s\n", ap_server_root); 

  +
   workerEnv->_private = (void *)s;
   
  -/* serverRoot via ap_server_root_relative()
  - */
  -workerEnv->initData->add( env, workerEnv->initData, "serverRoot",
  -  ap_server_root_relative(p,""));
   return JK_OK;
   }
   
  
  
  

--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

cvs commit: jakarta-tomcat-connectors/jk/native2/common jk_logger_file.c

[mturk]

mturk   2002/10/04 09:08:19

  Modified:jk/native2/common jk_logger_file.c
  Log:
  1. Change the default logger to the jk2.log (was mod_jk.log)
  2. Fix the ${serverRoot} replaceProperties.
  3. Do not close log file if it is stderr.
  
  Revision  ChangesPath
  1.35  +8 -7  jakarta-tomcat-connectors/jk/native2/common/jk_logger_file.c
  
  Index: jk_logger_file.c
  ===
  RCS file: /home/cvs/jakarta-tomcat-connectors/jk/native2/common/jk_logger_file.c,v
  retrieving revision 1.34
  retrieving revision 1.35
  diff -u -r1.34 -r1.35
  --- jk_logger_file.c  27 Sep 2002 13:08:17 -  1.34
  +++ jk_logger_file.c  4 Oct 2002 16:08:19 -   1.35
  @@ -153,11 +153,11 @@
   FILE *f=NULL;
   jk_workerEnv_t *workerEnv=env->getByName( env, "workerEnv" );
   if( _this->name==NULL ) {
  -_this->name="${serverRoot}/logs/mod_jk.log";
  +_this->name="${serverRoot}/logs/jk2.log";
   }
  -jk2_config_replaceProperties( env, workerEnv->initData,
  -  _this->mbean->pool,_this->name);
  -if( strcmp( "stderr", _this->name )==0 ) {
  +_this->name = jk2_config_replaceProperties(env, workerEnv->initData,
  +   _this->mbean->pool, _this->name);
  +if( !_this->name || strcmp( "stderr", _this->name )==0 ) {
   _this->logger_private = stderr;
   } else {
   
  @@ -176,7 +176,7 @@
   } 
   _this->jkLog(env, _this,JK_LOG_INFO,
"Initializing log file %s\n", _this->name );
  -if( oldF!=NULL ) {
  +if( oldF!=NULL && oldF != stderr) {
   fclose( oldF );
   }
   return JK_OK;
  @@ -185,7 +185,8 @@
   static int jk2_logger_file_close(jk_env_t *env,jk_logger_t *_this)
   {
   FILE *f = _this->logger_private;
  -if( f==NULL ) return JK_OK;
  +if (f == NULL || f != stderr)
  +return JK_OK;
   
   fflush(f);
   fclose(f);
  
  
  

--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

Re: xerces-j2 2.2.0 problem submitted in bugzilla

[Jean-Francois Arcand]

I just spoke to a Xalan member and he told me they have the same problem 
(exception) but this time with "/" instead of "--". We  should stick 
with Xerces 2.1.0seems to have more that one bug in Xerces 2.2.0.

-- Jeanfrancois

Henri Gomez wrote:

> I reported the error in xerces2 bugzilla about xerces 2.2.0
> and tomcat 4.1.12.
>
> http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13282
>
> Thanks to comments if you have interesting clues.
>
>
>
> --
> To unsubscribe, e-mail:   
> 
> For additional commands, e-mail: 
> 
>
>


--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

RE: Localization in tomcat 4.1

[iasandcb]

See
http://developer.java.sun.com/developer/technicalArticles/Intl/Multiling
ualJSP/ ,
you can find some alternative to do so with JSTL under JSP technology.
In addition, so far there's no such page-file-based l10n in JSP spec. 
Personally I tried JSTL l10n and it has worked fine on my site:
http://www.iasandcb.pe.kr

IAS

-Original Message-
From: Tony Mandatori [mailto:[EMAIL PROTECTED]] 
Sent: Friday, October 04, 2002 5:42 AM
To: [EMAIL PROTECTED]
Subject: Localization in tomcat 4.1


Team,
 
I thought that Localization of html files was supported in Tomcat.  What
I mean is.
- if I look for index.jsp
-- and index_fr.jsp exists and
-- and I have French as my default language in my browser, 
 
Then I should see index_fr.jsp.
 
I tried this and it doesn't seem to be working.
 
Can anyone tell me how to get this working in Tomcat.
 
Thanks
Tony 
 

--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

Re: [5.0] [VOTE] Removal of the LE distribution

[Jean-Francois Arcand]

Bill Barker wrote:

>- Original Message -
>From: "Remy Maucherat" <[EMAIL PROTECTED]>
>To: "Tomcat Developers List" <[EMAIL PROTECTED]>
>Sent: Thursday, October 03, 2002 7:50 PM
>Subject: Re: [5.0] [VOTE] Removal of the LE distribution
>
>
>  
>
>>Costin Manolache wrote:
>>
>>
>>>Remy Maucherat wrote:
>>>
>>>
>>>  
>>>
Hi all,

Before starting to release 5.0.x milestones, I would like to propose
having only one distribution for Tomcat 5.0.x, and standardize on what
the LE distribution contains (so well, it's more the other distribution
which gets removed).

It has some advantages:
- it is slightly smaller (less these days now that the XML parser has to
be shipped again with Tomcat)
- runs as-is on JDK 1.3 (because of the Xerces inclusion)
- 99% Apache or Apache-style licence (the JDBC 2 standard extension is
needed for JDK 1.3 DataSource support :-()
- less user confusion

The main "problem" is that the user will need additional downloads for
some of the more advanced features, and the package will also not run on
JDK 1.2 as is (but from what I've seen, JDK 1.2 compatibility may not be
a priority for developers).


+1 [X] Yes, remove the LE distribution
-1 [ ] No, keep both distributions



>>>What would it take to be 100% Apache-style licence ? Can we do some
>>>introspection tricks or conditional compilation to solve this ?
>>>  
>>>
>>I can remove the JDBC SE JAR, but then the JDBC connection pooling
>>features won't work right out of the box on JDK 1.3 (assuming it is
>>possible to run JDK 1.3 with TC 5).
>>
>>A great blinking warning should be added to the download page and the
>>release notes if we do that.
>>
>>If somehow the Catalina (with JSP 2 support) adapter requires JDK 1.4,
>>then JDBC SE can be removed.
>>
>>
>
>Well, it seems that this has already been done without a [VOTE].  After a
>long time away from 5.0, I attempted to build it, only to discover that it
>can't be built any more.  As a result, I'm now (belatedly) posting my -1 to
>R1.2 of o.a.c.core.StandardWrapper.java. and R1.1 of o.a.c.u.SecurityUtil.
>Please change to a version that compiles under 1.2 at least until there is a
>[VOTE] to change the target version.  AFAIK, the target version is still the
>same as 4.x (e.g. 1.2).
>
I'm confuse. The Tomcat 4.0-4.1 documentatopm requires JDK 1.3 for 
compilling the source code:

" This subproject contains the source code Tomcat 4.0, a server that implements
the Servlet 2.3 and JSP 1.2 Specifications from Java Software.  In order to
build a binary distribution version of the container from a source
distribution, you must have a Java Development Kit (JDK) for version 1.3 (or
later) downloaded and installed (version 1.3.1 recommended), and do the
following:"

Tomcat should run on 1.2, but should it compile?

-- Jeanfrancois




>
>  
>
>>Remy
>>
>>
>>--
>>To unsubscribe, e-mail:
>>
>>
>
>  
>
>>For additional commands, e-mail:
>>
>>
>
>  
>
>
>
>--
>To unsubscribe, e-mail:   
>For additional commands, e-mail: 
>
>
>  
>

DO NOT REPLY [Bug 13241] - Tomcat 4.1.12 / Webapps:Examples / Disabled

[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://nagoya.apache.org/bugzilla/show_bug.cgi?id=13241

Tomcat 4.1.12 / Webapps:Examples / Disabled





--- Additional Comments From [EMAIL PROTECTED]  2002-10-04 12:45 ---
After switch to t4.1.12 I got this error:
0INFO  mill.startup.StartupServlet  - Application path: C:\opt2
\www\_toner.irk.ru\data\
0INFO  mill.startup.StartupServlet  - class 
org.bouncycastle.jce.provider.BouncyCastleProvider present
0INFO  mill.startup.StartupServlet  - class 
com.oreilly.servlet.multipart.FilePart present
0INFO  mill.startup.StartupServlet  - class org.apache.log4j.Category 
present
50   INFO  mill.startup.StartupServlet  - class 
org.exolab.castor.mapping.Mapping present
16530 DEBUG mill.member.MemberMapping  - Create Mapping instance from file 
c:\opt2\www\_toner.irk.ru\data\WEB-INF\mill\castor_mapping.xml
16530 DEBUG mill.member.MemberMapping  - Previos instance not found. Create new 
instance, file - c:\opt2\www\_toner.irk.ru\data\WEB-INF\mill\castor_mapping.xml
16810 FATAL mill.member.MemberMapping  - Error get instance of 
org.exolab.castor.mapping.Mapping
java.net.MalformedURLException: unknown protocol: c
at java.net.URL.(URL.java:586)
at java.net.URL.(URL.java:476)
at java.net.URL.(URL.java:425)
at org.apache.xerces.impl.XMLEntityManager.startEntity(Unknown Source)
at org.apache.xerces.impl.XMLEntityManager.startDocumentEntity(Unknown 
Source)
at org.apache.xerces.impl.XMLDocumentScannerImpl.setInputSource(Unknown 
Source)
at org.apache.xerces.parsers.DTDConfiguration.parse(Unknown Source)
at org.apache.xerces.parsers.DTDConfiguration.parse(Unknown Source)
at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
at org.exolab.castor.xml.Unmarshaller.unmarshal(Unmarshaller.java:463)
at org.exolab.castor.mapping.Mapping.loadMappingInternal
(Mapping.java:488)
at org.exolab.castor.mapping.Mapping.loadMappingInternal
(Mapping.java:441)
at org.exolab.castor.mapping.Mapping.loadMapping(Mapping.java:368)
at mill.member.MemberMapping.getInstance(MemberMapping.java:61)
at mill.member.MemberMapping.getInstance(MemberMapping.java:27)
at mill.startup.InitParam.parseConfigFile(InitParam.java:120)
at mill.startup.InitParam.readConfig(InitParam.java:237)
at mill.startup.InitParam.getHTMLCharset(InitParam.java:429)
at mill.port.InitPage.setContentType(InitPage.java:92)
at mill.portlet.ContextNavigator.doGet(ContextNavigator.java:513)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter
(ApplicationFilterChain.java:247)
at org.apache.catalina.core.ApplicationFilterChain.doFilter
(ApplicationFilterChain.java:193)
at org.apache.catalina.core.StandardWrapperValve.invoke
(StandardWrapperValve.java:260)
at 
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNex
t(StandardPipeline.java:643)
at org.apache.catalina.core.StandardPipeline.invoke
(StandardPipeline.java:480)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at org.apache.catalina.core.StandardContextValve.invoke
(StandardContextValve.java:191)
at 
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNex
t(StandardPipeline.java:643)
at org.apache.catalina.core.StandardPipeline.invoke
(StandardPipeline.java:480)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at org.apache.catalina.core.StandardContext.invoke
(StandardContext.java:2396)
at org.apache.catalina.core.StandardHostValve.invoke
(StandardHostValve.java:180)
at 
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNex
t(StandardPipeline.java:643)
at org.apache.catalina.valves.ErrorDispatcherValve.invoke
(ErrorDispatcherValve.java:170)
at 
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNex
t(StandardPipeline.java:641)
at org.apache.catalina.valves.ErrorReportValve.invoke
(ErrorReportValve.java:172)
at 
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNex
t(StandardPipeline.java:641)
at org.apache.catalina.valves.AccessLogValve.invoke
(AccessLogValve.java:469)
at 
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNex
t(StandardPipeline.java:641)
at org.apache.catalina.core.StandardPip

DO NOT REPLY [Bug 13285] New: - admin web application fail with virtual host

[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://nagoya.apache.org/bugzilla/show_bug.cgi?id=13285

admin web application fail with virtual host

   Summary: admin web application fail with virtual host
   Product: Tomcat 3
   Version: 3.3.1 Final
  Platform: PC
OS/Version: Linux
Status: NEW
  Severity: Critical
  Priority: Other
 Component: Config
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]


My environnement :
  Tomcat 3.3.1 with Apache 1.3.26/mod_jk/ajp13
  Java HotSpot(TM) Server VM (build 1.3.1_02-b02, mixed mode)
  Linux 2.4.18 i686

I define a virtual host in apache with redirection of servlets in tomcat :

  ...
  ServerName applitestservlet
  ...
  JkMount /*.jgi ajp13


In Tomcat, I have apps-127.0.0.1.xml with :

  
  
  
  


So, when I start tomcat, I have in my logs :
2002-10-04 12:18:42 - ContextManager: Adding  DEFAULT:/admin
2002-10-04 12:18:42 - ContextManager: Adding  applitestservlet:/ROOT
2002-10-04 12:18:42 - ContextManager: Adding  applitestservlet:/*.jgi
...

If I GET http://applitestservlet/Login.jgi, my request is OK

BUT, after removing Context applitextservlet and re-add it via the admin web 
application (http://localhost:8080/admin/contextAdmin/contextAdmin.html) the 
request is KO

Note : after re-add the context, the tomcat logs says :
2002-10-04 12:19:04 - ContextManager: Adding context DEFAULT:/ROOT
2002-10-04 12:19:04 - ContextManager: Adding context DEFAULT:/*.jgi
!!!
(instead of applitestservlet:/*.jgi)

So the virtual host is lost for tomcat ... :-(

--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

cvs commit: jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/valves ErrorReportValve.java

[remm]

remm2002/10/04 05:30:53

  Modified:catalina/src/share/org/apache/catalina/valves
ErrorReportValve.java
  Log:
  - Experiment with not returning a status report for codes < 400.
  
  Revision  ChangesPath
  1.13  +6 -9  
jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/valves/ErrorReportValve.java
  
  Index: ErrorReportValve.java
  ===
  RCS file: 
/home/cvs/jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/valves/ErrorReportValve.java,v
  retrieving revision 1.12
  retrieving revision 1.13
  diff -u -r1.12 -r1.13
  --- ErrorReportValve.java 11 Sep 2002 14:44:45 -  1.12
  +++ ErrorReportValve.java 4 Oct 2002 12:30:52 -   1.13
  @@ -250,11 +250,8 @@
   if (message == null)
   message = "";
   
  -// Do nothing on a 1xx and 2xx status
  -if (statusCode < 300)
  -return;
  -// Do nothing on a NOT MODIFIED status
  -if (statusCode == HttpServletResponse.SC_NOT_MODIFIED)
  +// Do nothing on a 1xx, 2xx and 3xx status
  +if (statusCode < 400)
   return;
   
   // FIXME: Reset part of the request
  
  
  

--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

cvs commit: jakarta-tomcat-4.0/catalina/src/share/org/apache/naming/resources ProxyDirContext.java

[remm]

remm2002/10/04 05:26:11

  Modified:catalina/src/share/org/apache/naming/resources
ProxyDirContext.java
  Log:
  - Fix performance bug where directories could not be cached.
  - Also allow caching the list of non existing resources (which considerably
helps welcome pages checks).
  
  Revision  ChangesPath
  1.13  +31 -23
jakarta-tomcat-4.0/catalina/src/share/org/apache/naming/resources/ProxyDirContext.java
  
  Index: ProxyDirContext.java
  ===
  RCS file: 
/home/cvs/jakarta-tomcat-4.0/catalina/src/share/org/apache/naming/resources/ProxyDirContext.java,v
  retrieving revision 1.12
  retrieving revision 1.13
  diff -u -r1.12 -r1.13
  --- ProxyDirContext.java  11 Jun 2002 00:31:43 -  1.12
  +++ ProxyDirContext.java  4 Oct 2002 12:26:10 -   1.13
  @@ -267,7 +267,6 @@
   if (entry != null) {
   if (entry.resource != null) {
   // Check content caching.
  -
   return entry.resource;
   } else {
   return entry.context;
  @@ -1375,7 +1374,8 @@
   /**
* Lookup in cache.
*/
  -protected CacheEntry cacheLookup(String name) {
  +protected CacheEntry cacheLookup(String name)
  +throws NamingException {
   if (cache == null)
   return (null);
   CacheEntry cacheEntry = (CacheEntry) cache.get(name);
  @@ -1383,9 +1383,7 @@
   cacheEntry = new CacheEntry();
   cacheEntry.name = name;
   // Load entry
  -if (!cacheLoad(cacheEntry))
  -return null;
  -return (cacheEntry);
  +cacheLoad(cacheEntry);
   } else {
   if (!validate(cacheEntry)) {
   if (!revalidate(cacheEntry)) {
  @@ -1396,8 +1394,11 @@
   System.currentTimeMillis() + cacheTTL;
   }
   }
  -return (cacheEntry);
   }
  +if (!cacheEntry.exists) {
  +throw new NamingException("Resource not found");
  +}
  +return (cacheEntry);
   }
   
   
  @@ -1405,8 +1406,10 @@
* Validate entry.
*/
   protected boolean validate(CacheEntry entry) {
  -if ((entry.resource != null) 
  -&& (entry.resource.getContent() != null) 
  +if (((!entry.exists)
  + || (entry.context != null)
  + || ((entry.resource != null) 
  + && (entry.resource.getContent() != null)))
   && (System.currentTimeMillis() < entry.timestamp)) {
   return true;
   }
  @@ -1420,6 +1423,8 @@
   protected boolean revalidate(CacheEntry entry) {
   // Get the attributes at the given path, and check the last 
   // modification date
  +if (!entry.exists)
  +return false;
   if (entry.attributes == null)
   return false;
   long lastModified = entry.attributes.getLastModified();
  @@ -1447,14 +1452,12 @@
   /**
* Load entry into cache.
*/
  -protected boolean cacheLoad(CacheEntry entry) {
  -
  -if (cache == null)
  -return false;
  +protected void cacheLoad(CacheEntry entry) {
   
   String name = entry.name;
   
   // Retrieve missing info
  +boolean exists = true;
   
   // Retrieving attributes
   if (entry.attributes == null) {
  @@ -1467,12 +1470,12 @@
   entry.attributes = (ResourceAttributes) attributes;
   }
   } catch (NamingException e) {
  -return false;
  +exists = false;
   }
   }
   
   // Retriving object
  -if ((entry.resource == null) && (entry.context == null)) {
  +if ((exists) && (entry.resource == null) && (entry.context == null)) {
   try {
   Object object = dirContext.lookup(name);
   if (object instanceof InputStream) {
  @@ -1486,12 +1489,13 @@
   (object.toString().getBytes()));
   }
   } catch (NamingException e) {
  -return false;
  +exists = false;
   }
   }
   
   // Load object content
  -if ((entry.resource != null) && (entry.resource.getContent() == null) 
  +if ((exists) && (entry.resource != null) 
  +&& (entry.resource.getContent() == null) 
   && (entry.attributes.getContentLength() >= 0)
   && (entry.attributes.getContentLength() < cacheObjectMaxSize)) {
   int length = (int) entry.attributes.getContentLength();
  @@ -1518,15 +1522,16 @@
   }
   }
   }
  -
  +
  +// Set existence flag
  +   

Need info

[Tanmaya]

Hi There,

I have installed tomcat-4.1.12 in my system.But I was unable to run the server with 
JDK1.2.2. When I tried with JDK1.3, it works fine.Is this behavior right ?? Please let 
me know the list of supported Tomcat version vs JDK version.

Thanks,
Tanmaya 

Tomcat 4.1.2 CoyoteConnector Authentication Problem

[Jonathan Pierce]

The 4.1.2 dist using the CoyoteConnector through IIS doesn't seem to support
authentication. Is this a bug, or do I need to reconfigure the default
server.xml to make this work?

When I hit the secure URL on port 8080, I get redirected to the login screen as
expected.
When I hit it through the Coyote Connector from IIS, I get a resource denied
error instead of the expected login screen.

http://localhost:8080/examples/jsp/security/protected/iindex.jsp redirects
correctly to the login screen.

http://localhost/examples/jsp/security/protected/iindex.jsp generates a 403 -
access denied error.



**
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the system manager.

This footnote also confirms that this email message has been swept by
MIMEsweeper for the presence of computer viruses.

www.diageo.com
**


--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

Localization in tomcat 4.1

[Tony Mandatori]

Team,
 
I thought that Localization of html files was supported in Tomcat.  What
I mean is.
- if I look for index.jsp
-- and index_fr.jsp exists and
-- and I have French as my default language in my browser, 
 
Then I should see index_fr.jsp.
 
I tried this and it doesn't seem to be working.
 
Can anyone tell me how to get this working in Tomcat.
 
Thanks
Tony 
 

Tomcat as a service

[David Oxley]

I have Tomcat 4.1.10 installed as a service on Windows and have changed
the JVM options by editing the registry. I wanted to use the new GC options
available in JDK 1.4.1. See the attached reg file. This works fine half the
time, but gives a GPF the rest of the time. This may be a bug with the new JDK
1.4.1 or with JavaService.

 

I am creating a wrapper.properties for TC4.1 so that I can use
jk_nt_service.exe. Was there a reason this wasn't used in the first
place? It is far more flexible than JavaService. Once I have got this working
do you want me to contribute the wrapper.properties for use in TC5.0 or TC4.1?

 

Dave

[EMAIL PROTECTED]








tc.reg
Description: Binary data

--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

Re: Is Compile Failure? was Re: Need some clarifications

[Steve Downey]

Yes, just a blank line before the line indicated in the parsing exception. I 
found this trying to move the line number, hoping to find the -- that 
shouldn't be there. Putting blanks at the beginning of the file moved the 
error line from 307 to 308:

SEVERE: Parse Fatal Error at line 307 column 39: The string "--" is not 
permitted within comments.
org.xml.sax.SAXParseException: The string "--" is not permitted within 
comments.

to
SEVERE: Parse Fatal Error at line 308 column 39: The string "--" is not 
permitted within comments.
org.xml.sax.SAXParseException: The string "--" is not permitted within 
comments.

So I went to line 306, added a /n and tried again. I was just trying to locate 
the problem. And it vanished.


On Friday 04 October 2002 03:55 am, Henri Gomez wrote:
> Steve Downey wrote:
> > On Thursday 03 October 2002 12:14 pm, Henri Gomez wrote:
> >>Steve Downey wrote:
> >>>Actually, with the recent release of commons-logging, we should be able
> >>>to get rid of the explicit LogKit and Log4J. They're there so as to get
> >>> a complete build of commons-logging. Tomcat 5 itself doesn't use either
> >>> directly.
> >>>
> >>>Xerces is a different issue. There was a bug that was preventing Tomcat
> >>>from migrating to the latest version. Unfortunately, I no longer
> >>> remember the details. Anyone know why we're using 2.1.0 instead of
> >>> 2.2.0?
> >>
> >> From what I experienced with Xerces j 2.2.0 it seems it does
> >>much more validity check and for instance found a '--' somewhere
> >>in comments (1 EUR to the first who find where).
> >>
> >>Previous version of Xerces or crimson didn't got that problem.
> >>
> >>if we could see which xml/dtd/tld is reported buggy, which
> >>will able to see if it's a bug or a features (ie a more strict
> >>check of xml rules)
> >
> > OK, from the 'this shouldn't work department', this patch 'fixes' the
> > problem: Index: ./jsr152/src/share/dtd/web-jsptaglibrary_1_2.dtd
> > ===
> > RCS file:
> > /home/cvspublic/jakarta-servletapi-5/jsr152/src/share/dtd/web-jsptaglibra
> >ry_1_2.dtd,v retrieving revision 1.1.1.1
> > diff -u -r1.1.1.1 web-jsptaglibrary_1_2.dtd
> > --- ./jsr152/src/share/dtd/web-jsptaglibrary_1_2.dtd13 Aug 2002
> > 16:20:58 -  1.1.1.1
> > +++ ./jsr152/src/share/dtd/web-jsptaglibrary_1_2.dtd3 Oct 2002
> > 20:42:30 -
> > @@ -304,6 +304,7 @@
> >   java.lang.String is default.
> >
> >  declare  Whether the variable is declared or not.
> > +
> >   True is the default.
> >
> >  scopeThe scope of the scripting varaible
> >
> >
> >
> > Something quite strange is going on.
>
> You just add an empty line in this dtd and it works now ?
>
> I was thinking it could be with -- in some dtd, ie
>  line in web-app_2_3.dtd :
>
> 


--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

xerces-j2 2.2.0 problem submitted in bugzilla

[Henri Gomez]

I reported the error in xerces2 bugzilla about xerces 2.2.0
and tomcat 4.1.12.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13282

Thanks to comments if you have interesting clues.



--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

Re: cvs commit: jakarta-tomcat-4.0 build.properties.sample

[Henri Gomez]

> Ooops that has nothing to do with xerces but the ant installation: xalan 
> was missing in my installation...

That's what I thinked (cf my prev message) ;-)


--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

Re: cvs commit: jakarta-tomcat-4.0 build.properties.sample

[jean-frederic clere]

Clere, Jean-Frederic wrote:
> Henri Gomez wrote:
> 
>> jean-frederic clere wrote:
>>
>>> Henri Gomez wrote:
>>>
 [EMAIL PROTECTED] wrote:

> jfclere 2002/10/04 01:46:33
>
>   Modified:.build.properties.sample
>   Log:
>   Upgrade to the lastest xerces.
> Revision  ChangesPath
>   1.52  +3 -3  jakarta-tomcat-4.0/build.properties.sample
> Index: build.properties.sample
>   ===
>   RCS file: /home/cvs/jakarta-tomcat-4.0/build.properties.sample,v
>   retrieving revision 1.51
>   retrieving revision 1.52
>   diff -u -r1.51 -r1.52
>   --- build.properties.sample4 Oct 2002 08:43:48 -1.51
>   +++ build.properties.sample4 Oct 2002 08:46:33 -1.52
>   @@ -117,9 +117,9 @@
>   # - Xerces XML Parser, version 2.0.0 or later -
># Note: Optional with JDK 1.4+, or if Xerces 1.x is present
>   -xerces.home=${base.path}/xerces-2_1_0
>   +xerces.home=${base.path}/xerces-2_2_0
>xerces.lib=${xerces.home}
>   
> -xerces.loc=http://xml.apache.org/dist/xerces-j/Xerces-J-bin.2.1.0.tar.gz 
>
>   
> +xerces.loc=http://xml.apache.org/dist/xerces-j/Xerces-J-bin.2.2.0.tar.gz 
>
>xercesImpl.jar=${xerces.lib}/xercesImpl.jar
>xmlParserAPIs.jar=${xerces.lib}/xmlParserAPIs.jar





 Shouln't we stay with xerces 2.1.0 until we found the problem with 
 2.2.0 ?
>>>
>>>
>>
>> yep, 2.1.0 moved to :
>>
>> http://xml.apache.org/dist/xerces-j/old_xerces2/
>>
>> Did someone contacted Xerces Team about our problem of comment checking ?
> 
> 
> No, and I have another problem probably due to 2.2.0:
> +++
> build-main:
> [style] DEPRECATED - xslp processor is deprecated. Use trax or xalan 
> instead.
> [style] java.lang.NoClassDefFoundError: com/kvisco/xsl/XSLProcessor
> [style] at 
> org.apache.tools.ant.taskdefs.optional.XslpLiaison.(XslpLiaison.java:80) 
> 
> [style] at java.lang.Class.newInstance0(Native Method)
> [style] at java.lang.Class.newInstance(Class.java:232)
> [style] at 
> org.apache.tools.ant.taskdefs.XSLTProcess.resolveProcessor(XSLTProcess.java:376) 
> 
> [style] at 
> org.apache.tools.ant.taskdefs.XSLTProcess.getLiaison(XSLTProcess.java:557)
> [style] at 
> org.apache.tools.ant.taskdefs.XSLTProcess.execute(XSLTProcess.java:195)
> [style] at org.apache.tools.ant.Task.perform(Task.java:319)
> [style] at org.apache.tools.ant.Target.execute(Target.java:309)
> [style] at 
> org.apache.tools.ant.Target.performTasks(Target.java:336)
> [style] at 
> org.apache.tools.ant.Project.executeTarget(Project.java:1306)
> [style] at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:371)
> [style] at org.apache.tools.ant.Task.perform(Task.java:319)
> [style] at org.apache.tools.ant.Target.execute(Target.java:309)
> [style] at 
> org.apache.tools.ant.Target.performTasks(Target.java:336)
> [style] at 
> org.apache.tools.ant.Project.executeTarget(Project.java:1306)
> [style] at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:371)
> [style] at org.apache.tools.ant.Task.perform(Task.java:319)
> [style] at org.apache.tools.ant.Target.execute(Target.java:309)
> [style] at 
> org.apache.tools.ant.Target.performTasks(Target.java:336)
> [style] at 
> org.apache.tools.ant.Project.executeTarget(Project.java:1306)
> [style] at 
> org.apache.tools.ant.Project.executeTargets(Project.java:1250)
> [style] at org.apache.tools.ant.Main.runBuild(Main.java:610)
> [style] at org.apache.tools.ant.Main.start(Main.java:196)
> [style] at org.apache.tools.ant.Main.main(Main.java:235)
> [style] java.lang.NoClassDefFoundError: 
> org/apache/xalan/xslt/XSLTProcessorFactory
> [style] at 
> org.apache.tools.ant.taskdefs.optional.XalanLiaison.(XalanLiaison.java:84) 
> 
> [style] at java.lang.Class.newInstance0(Native Method)
> [style] at java.lang.Class.newInstance(Class.java:232)
> [style] at 
> org.apache.tools.ant.taskdefs.XSLTProcess.resolveProcessor(XSLTProcess.java:379) 
> 
> [style] at 
> org.apache.tools.ant.taskdefs.XSLTProcess.getLiaison(XSLTProcess.java:554)
> [style] at 
> org.apache.tools.ant.taskdefs.XSLTProcess.execute(XSLTProcess.java:195)
> [style] at org.apache.tools.ant.Task.perform(Task.java:319)
> [style] at org.apache.tools.ant.Target.execute(Target.java:309)
> [style] at 
> org.apache.tools.ant.Target.performTasks(Target.java:336)
> [style] at 
> org.apache.tools.ant.Project.executeTarget(Project.java:1306)
> [style] at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:371)
> [style] at org.apache.tools.ant.Task.perform(Task.java:319)
> [style] at org.apache.

Re: cvs commit: jakarta-tomcat-4.0 build.properties.sample

[Henri Gomez]

>> Did someone contacted Xerces Team about our problem of comment checking ?
> 
> 
> No, and I have another problem probably due to 2.2.0:

ant didn't find you Xalan 2.4.0 jar ?
Is it in ant/lib ?

> build-main:
> [style] DEPRECATED - xslp processor is deprecated. Use trax or xalan 
> instead.
> [style] java.lang.NoClassDefFoundError: com/kvisco/xsl/XSLProcessor
> [style] at 
> org.apache.tools.ant.taskdefs.optional.XslpLiaison.(XslpLiaison.java:80) 
> 
> [style] at java.lang.Class.newInstance0(Native Method)
> [style] at java.lang.Class.newInstance(Class.java:232)
> [style] at 
> org.apache.tools.ant.taskdefs.XSLTProcess.resolveProcessor(XSLTProcess.java:376) 
> 
> [style] at 
> org.apache.tools.ant.taskdefs.XSLTProcess.getLiaison(XSLTProcess.java:557)
> [style] at 
> org.apache.tools.ant.taskdefs.XSLTProcess.execute(XSLTProcess.java:195)
> [style] at org.apache.tools.ant.Task.perform(Task.java:319)
> [style] at org.apache.tools.ant.Target.execute(Target.java:309)
> [style] at 
> org.apache.tools.ant.Target.performTasks(Target.java:336)
> [style] at 
> org.apache.tools.ant.Project.executeTarget(Project.java:1306)
> [style] at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:371)
> [style] at org.apache.tools.ant.Task.perform(Task.java:319)
> [style] at org.apache.tools.ant.Target.execute(Target.java:309)
> [style] at 
> org.apache.tools.ant.Target.performTasks(Target.java:336)
> [style] at 
> org.apache.tools.ant.Project.executeTarget(Project.java:1306)
> [style] at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:371)
> [style] at org.apache.tools.ant.Task.perform(Task.java:319)
> [style] at org.apache.tools.ant.Target.execute(Target.java:309)
> [style] at 
> org.apache.tools.ant.Target.performTasks(Target.java:336)
> [style] at 
> org.apache.tools.ant.Project.executeTarget(Project.java:1306)
> [style] at 
> org.apache.tools.ant.Project.executeTargets(Project.java:1250)
> [style] at org.apache.tools.ant.Main.runBuild(Main.java:610)
> [style] at org.apache.tools.ant.Main.start(Main.java:196)
> [style] at org.apache.tools.ant.Main.main(Main.java:235)
> [style] java.lang.NoClassDefFoundError: 
> org/apache/xalan/xslt/XSLTProcessorFactory
> [style] at 
> org.apache.tools.ant.taskdefs.optional.XalanLiaison.(XalanLiaison.java:84) 
> 
> [style] at java.lang.Class.newInstance0(Native Method)
> [style] at java.lang.Class.newInstance(Class.java:232)
> [style] at 
> org.apache.tools.ant.taskdefs.XSLTProcess.resolveProcessor(XSLTProcess.java:379) 
> 
> [style] at 
> org.apache.tools.ant.taskdefs.XSLTProcess.getLiaison(XSLTProcess.java:554)
> [style] at 
> org.apache.tools.ant.taskdefs.XSLTProcess.execute(XSLTProcess.java:195)
> [style] at org.apache.tools.ant.Task.perform(Task.java:319)
> [style] at org.apache.tools.ant.Target.execute(Target.java:309)
> [style] at 
> org.apache.tools.ant.Target.performTasks(Target.java:336)
> [style] at 
> org.apache.tools.ant.Project.executeTarget(Project.java:1306)
> [style] at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:371)
> [style] at org.apache.tools.ant.Task.perform(Task.java:319)
> [style] at org.apache.tools.ant.Target.execute(Target.java:309)
> [style] at 
> org.apache.tools.ant.Target.performTasks(Target.java:336)
> [style] at 
> org.apache.tools.ant.Project.executeTarget(Project.java:1306)
> [style] at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:371)
> [style] at org.apache.tools.ant.Task.perform(Task.java:319)
> [style] at org.apache.tools.ant.Target.execute(Target.java:309)
> [style] at 
> org.apache.tools.ant.Target.performTasks(Target.java:336)
> [style] at 
> org.apache.tools.ant.Project.executeTarget(Project.java:1306)
> [style] at 
> org.apache.tools.ant.Project.executeTargets(Project.java:1250)
> [style] at org.apache.tools.ant.Main.runBuild(Main.java:610)
> [style] at org.apache.tools.ant.Main.start(Main.java:196)
> [style] at org.apache.tools.ant.Main.main(Main.java:235)
> 
> BUILD FAILED
> file:/home6/clere/jakarta-tomcat-4.1.12-src/webapps/tomcat-docs/build.xml:82: 
> javax.xml.transform.TransformerFactoryConfigurationError: Provider for 
> javax.xml.transform.TransformerFactory cannot be found
> +++




--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

Apache 2.0.43 and JK/JK2

[Henri Gomez]

You should know that Apache 2.0.43 as been released to
fix security failures.

The JK and JK2 connectors who has been built under 2.0.42
will WORKS with 2.0.43, no need to recompile anything.

For rpms users, I've uploaded new JK and JK2 rpms to be
used against 2.0.43 since rpm requires to have an apache 2
matching the one which with the mod_jk has been built :

JK :

mod_jk-ap20-1.2.0-1jpp.i386.rpmis for Apache 2.0.42
mod_jk-ap20-1.2.0-2jpp.i386.rpmis for Apache 2.0.43
http://jakarta.apache.org/builds/jakarta-tomcat-connectors/jk/release/v1.2.0/rpms/

JK2 :

mod_jk-ap20-1.2.0-1jpp.i386.rpm  is for Apache 2.0.42
mod_jk-ap20-1.2.0-2jpp.i386.rpm  is for Apache 2.0.43

http://jakarta.apache.org/builds/jakarta-tomcat-connectors/jk2/release/v2.0.0/rpms/


Regards

PS: As usually RPM for Apache 2.0.42/2.0.43 are at falsehope.com :

http://ftp.falsehope.com/home/gomez/apache2/



--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

DO NOT REPLY [Bug 13084] - jsp compilation with jikes fails

[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://nagoya.apache.org/bugzilla/show_bug.cgi?id=13084

jsp compilation with jikes fails

[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|CLOSED  |REOPENED
 Resolution|INVALID |



--- Additional Comments From [EMAIL PROTECTED]  2002-10-04 10:24 ---
I would definatly vote for this option since in the current state it excludes
the whole windows-branch from using jikes!!

(Or give us a jikes with encoding option under windows ;-)

--Holger

--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

Re: cvs commit: jakarta-tomcat-4.0 build.properties.sample

[jean-frederic clere]

Henri Gomez wrote:
> jean-frederic clere wrote:
> 
>> Henri Gomez wrote:
>>
>>> [EMAIL PROTECTED] wrote:
>>>
 jfclere 2002/10/04 01:46:33

   Modified:.build.properties.sample
   Log:
   Upgrade to the lastest xerces.
 Revision  ChangesPath
   1.52  +3 -3  jakarta-tomcat-4.0/build.properties.sample
 Index: build.properties.sample
   ===
   RCS file: /home/cvs/jakarta-tomcat-4.0/build.properties.sample,v
   retrieving revision 1.51
   retrieving revision 1.52
   diff -u -r1.51 -r1.52
   --- build.properties.sample4 Oct 2002 08:43:48 -1.51
   +++ build.properties.sample4 Oct 2002 08:46:33 -1.52
   @@ -117,9 +117,9 @@
   # - Xerces XML Parser, version 2.0.0 or later -
# Note: Optional with JDK 1.4+, or if Xerces 1.x is present
   -xerces.home=${base.path}/xerces-2_1_0
   +xerces.home=${base.path}/xerces-2_2_0
xerces.lib=${xerces.home}
   
 -xerces.loc=http://xml.apache.org/dist/xerces-j/Xerces-J-bin.2.1.0.tar.gz 

   
 +xerces.loc=http://xml.apache.org/dist/xerces-j/Xerces-J-bin.2.2.0.tar.gz 

xercesImpl.jar=${xerces.lib}/xercesImpl.jar
xmlParserAPIs.jar=${xerces.lib}/xmlParserAPIs.jar
>>>
>>>
>>>
>>>
>>> Shouln't we stay with xerces 2.1.0 until we found the problem with 
>>> 2.2.0 ?
>>
> 
> yep, 2.1.0 moved to :
> 
> http://xml.apache.org/dist/xerces-j/old_xerces2/
> 
> Did someone contacted Xerces Team about our problem of comment checking ?

No, and I have another problem probably due to 2.2.0:
+++
build-main:
 [style] DEPRECATED - xslp processor is deprecated. Use trax or xalan instead.
 [style] java.lang.NoClassDefFoundError: com/kvisco/xsl/XSLProcessor
 [style] at 
org.apache.tools.ant.taskdefs.optional.XslpLiaison.(XslpLiaison.java:80)
 [style] at java.lang.Class.newInstance0(Native Method)
 [style] at java.lang.Class.newInstance(Class.java:232)
 [style] at 
org.apache.tools.ant.taskdefs.XSLTProcess.resolveProcessor(XSLTProcess.java:376)
 [style] at 
org.apache.tools.ant.taskdefs.XSLTProcess.getLiaison(XSLTProcess.java:557)
 [style] at 
org.apache.tools.ant.taskdefs.XSLTProcess.execute(XSLTProcess.java:195)
 [style] at org.apache.tools.ant.Task.perform(Task.java:319)
 [style] at org.apache.tools.ant.Target.execute(Target.java:309)
 [style] at org.apache.tools.ant.Target.performTasks(Target.java:336)
 [style] at 
org.apache.tools.ant.Project.executeTarget(Project.java:1306)[style] at 
org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:371)
 [style] at org.apache.tools.ant.Task.perform(Task.java:319)
 [style] at org.apache.tools.ant.Target.execute(Target.java:309)
 [style] at org.apache.tools.ant.Target.performTasks(Target.java:336)
 [style] at 
org.apache.tools.ant.Project.executeTarget(Project.java:1306)[style] at 
org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:371)
 [style] at org.apache.tools.ant.Task.perform(Task.java:319)
 [style] at org.apache.tools.ant.Target.execute(Target.java:309)
 [style] at org.apache.tools.ant.Target.performTasks(Target.java:336)
 [style] at 
org.apache.tools.ant.Project.executeTarget(Project.java:1306)[style] at 
org.apache.tools.ant.Project.executeTargets(Project.java:1250)
 [style] at org.apache.tools.ant.Main.runBuild(Main.java:610)
 [style] at org.apache.tools.ant.Main.start(Main.java:196)
 [style] at org.apache.tools.ant.Main.main(Main.java:235)
 [style] java.lang.NoClassDefFoundError: 
org/apache/xalan/xslt/XSLTProcessorFactory
 [style] at 
org.apache.tools.ant.taskdefs.optional.XalanLiaison.(XalanLiaison.java:84)
 [style] at java.lang.Class.newInstance0(Native Method)
 [style] at java.lang.Class.newInstance(Class.java:232)
 [style] at 
org.apache.tools.ant.taskdefs.XSLTProcess.resolveProcessor(XSLTProcess.java:379)
 [style] at 
org.apache.tools.ant.taskdefs.XSLTProcess.getLiaison(XSLTProcess.java:554)
 [style] at 
org.apache.tools.ant.taskdefs.XSLTProcess.execute(XSLTProcess.java:195)
 [style] at org.apache.tools.ant.Task.perform(Task.java:319)
 [style] at org.apache.tools.ant.Target.execute(Target.java:309)
 [style] at org.apache.tools.ant.Target.performTasks(Target.java:336)
 [style] at 
org.apache.tools.ant.Project.executeTarget(Project.java:1306)[style] at 
org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:371)
 [style] at org.apache.tools.ant.Task.perform(Task.java:319)
 [style] at org.apache.tools.ant.Target.execute(Target.java:309)
 [style] at org.apache.tools.ant.Target.performTasks(Target.java:336)
 [style] at 
org.apache.tools.ant.Project.executeTarget(Project.java:1306

Re: Apache 2.0.43 is out

[jean-frederic clere]

Henri Gomez wrote:
> We should provide new binaries for JK and JK2.
> 
> I'll do JK/JK2 for Linux boxes (and FreeBSD)
> 
> Who could do the same for Windows, Netware and Solaris ?

On Solaris8 the binary of httpd is not yet available.

> 
> BTW, I'm still waiting an account on moof to build a MacOSX
> version.

That is the same for MacOSX.
On moof I will try to build the httpd and I will put it under 
/Volumes/data/Users/jfclere/apache43 so that you can use it.

> 
> 
> 
> -- 
> To unsubscribe, e-mail:   
> 
> For additional commands, e-mail: 
> 
> 
> 




--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

cvs commit: jakarta-tomcat-connectors/jk/native2/common jk_channel_apr_socket.c

[mturk]

mturk   2002/10/04 03:12:53

  Modified:jk/native2/common jk_channel_apr_socket.c
  Log:
  Fix the apr_socket default timeout value.
  Also fix the send/recv that caused wrong header readings.
  
  Revision  ChangesPath
  1.28  +32 -22
jakarta-tomcat-connectors/jk/native2/common/jk_channel_apr_socket.c
  
  Index: jk_channel_apr_socket.c
  ===
  RCS file: 
/home/cvs/jakarta-tomcat-connectors/jk/native2/common/jk_channel_apr_socket.c,v
  retrieving revision 1.27
  retrieving revision 1.28
  diff -u -r1.27 -r1.28
  --- jk_channel_apr_socket.c   3 Oct 2002 01:33:14 -   1.27
  +++ jk_channel_apr_socket.c   4 Oct 2002 10:12:52 -   1.28
  @@ -216,7 +216,7 @@
   int ndelay=socketInfo->ndelay;
   int keepalive=socketInfo->keepalive;
   
  -apr_socket_t *sock=endpoint->channelData;
  +apr_socket_t *sock;
   apr_status_t ret;
   apr_int32_t timeout = (apr_int32_t)(socketInfo->timeout * APR_USEC_PER_SEC);
   char msg[128];
  @@ -232,7 +232,8 @@
   remote_sa = remote_sa->next;
   continue;
   }
  -
  +/* store the channel information */
  +endpoint->channelData=sock;
   
   env->l->jkLog(env, env->l, JK_LOG_INFO,
   "channelApr.open(): create tcp socket %d\n", sock );
  @@ -240,8 +241,9 @@
   /* the default timeout (0) will set the socket to blocking with
  infinite timeouts.
   */
  +
   if (timeout <= 0)
  -apr_socket_timeout_set(sock, 0);
  +apr_socket_timeout_set(sock, -1);
   else
   apr_socket_timeout_set(sock, timeout);
   
  @@ -296,9 +298,6 @@
   env->l->jkLog(env, env->l, JK_LOG_DEBUG,
 "channelApr.open(), sock = %d\n", sock);
   
  -/* store the channel information */
  -endpoint->channelData=sock;
  -
   return JK_OK;
   }
   
  @@ -360,13 +359,20 @@
   b=msg->buf;
   
   length = (apr_size_t) len;
  -stat = apr_send(sock, b, &length);
  -if (stat!= APR_SUCCESS) {
  -env->l->jkLog(env, env->l, JK_LOG_ERROR,
  -  "jk2_channel_apr_send send failed %d %s\n",
  -  stat, apr_strerror( stat, data, sizeof(data) ) );
  -return -3; /* -2 is not possible... */
  -}
  +do {
  +apr_size_t written = length;
  +
  +stat = apr_send(sock, b, &written);
  +if (stat!= APR_SUCCESS) {
  +env->l->jkLog(env, env->l, JK_LOG_ERROR,
  +"jk2_channel_apr_send send failed %d %s\n",
  +stat, apr_strerror( stat, data, sizeof(data) ) );
  +return -3; /* -2 is not possible... */
  +}
  +length -= written;
  +b += written;
  +} while (length); 
  +
   return JK_OK;
   }
   
  @@ -395,17 +401,21 @@
   return JK_ERR;
   
   rdlen = 0;
  +length = (apr_size_t)len;
  +while (rdlen < len) {
   
  -length = (apr_size_t) len;
  -stat =  apr_recv(sock, b, &length);
  +stat =  apr_recv(sock, b + rdlen, &length);
   
  -if ( stat == APR_EOF)
  -return -1; /* socket closed. */
  -else if ( stat == APR_SUCCESS) {
  -rdlen = (int) length;
  -return rdlen; 
  -} else
  -return -1; /* any error. */
  +if (stat == APR_EOF)
  +return -1; /* socket closed. */
  +else if (APR_STATUS_IS_EAGAIN(stat))
  +continue;
  +else if (stat != APR_SUCCESS)
  +return -1; /* any error. */
  +rdlen += length;
  +length = (apr_size_t)(len - rdlen);
  +}
  +return rdlen;
   }
   
   /** receive len bytes.
  
  
  

--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

Re: cvs commit: jakarta-tomcat-4.0 build.properties.sample

[Henri Gomez]

jean-frederic clere wrote:
> Henri Gomez wrote:
> 
>> [EMAIL PROTECTED] wrote:
>>
>>> jfclere 2002/10/04 01:46:33
>>>
>>>   Modified:.build.properties.sample
>>>   Log:
>>>   Upgrade to the lastest xerces.
>>> Revision  ChangesPath
>>>   1.52  +3 -3  jakarta-tomcat-4.0/build.properties.sample
>>> Index: build.properties.sample
>>>   ===
>>>   RCS file: /home/cvs/jakarta-tomcat-4.0/build.properties.sample,v
>>>   retrieving revision 1.51
>>>   retrieving revision 1.52
>>>   diff -u -r1.51 -r1.52
>>>   --- build.properties.sample4 Oct 2002 08:43:48 -1.51
>>>   +++ build.properties.sample4 Oct 2002 08:46:33 -1.52
>>>   @@ -117,9 +117,9 @@
>>>   # - Xerces XML Parser, version 2.0.0 or later -
>>># Note: Optional with JDK 1.4+, or if Xerces 1.x is present
>>>   -xerces.home=${base.path}/xerces-2_1_0
>>>   +xerces.home=${base.path}/xerces-2_2_0
>>>xerces.lib=${xerces.home}
>>>   
>>> -xerces.loc=http://xml.apache.org/dist/xerces-j/Xerces-J-bin.2.1.0.tar.gz 
>>>
>>>   
>>> +xerces.loc=http://xml.apache.org/dist/xerces-j/Xerces-J-bin.2.2.0.tar.gz 
>>>
>>>xercesImpl.jar=${xerces.lib}/xercesImpl.jar
>>>xmlParserAPIs.jar=${xerces.lib}/xmlParserAPIs.jar
>>
>>
>>
>> Shouln't we stay with xerces 2.1.0 until we found the problem with 
>> 2.2.0 ?

yep, 2.1.0 moved to :

http://xml.apache.org/dist/xerces-j/old_xerces2/

Did someone contacted Xerces Team about our problem of comment checking ?






--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

Re: Apache 2.0.43 is out

[Henri Gomez]

Henri Gomez wrote:
> We should provide new binaries for JK and JK2.
> 
> I'll do JK/JK2 for Linux boxes (and FreeBSD)
> 
> Who could do the same for Windows, Netware and Solaris ?
> 
> BTW, I'm still waiting an account on moof to build a MacOSX
> version.

It seems that the Magic Module Number didn't change between
2.0.42 and 2.0.43 so the modules built on 2.0.42 works also
on 2.0.43.

But rpm requires same versions, so I'll release new rpms
for 2.0.43 (apache 2.0.43 rpm being uploaded to falsehope.com).



--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

Re: cvs commit: jakarta-tomcat-4.0 build.properties.sample

[jean-frederic clere]

Henri Gomez wrote:
> [EMAIL PROTECTED] wrote:
> 
>> jfclere 2002/10/04 01:46:33
>>
>>   Modified:.build.properties.sample
>>   Log:
>>   Upgrade to the lastest xerces.
>> Revision  ChangesPath
>>   1.52  +3 -3  jakarta-tomcat-4.0/build.properties.sample
>> Index: build.properties.sample
>>   ===
>>   RCS file: /home/cvs/jakarta-tomcat-4.0/build.properties.sample,v
>>   retrieving revision 1.51
>>   retrieving revision 1.52
>>   diff -u -r1.51 -r1.52
>>   --- build.properties.sample4 Oct 2002 08:43:48 -1.51
>>   +++ build.properties.sample4 Oct 2002 08:46:33 -1.52
>>   @@ -117,9 +117,9 @@
>>   # - Xerces XML Parser, version 2.0.0 or later -
>># Note: Optional with JDK 1.4+, or if Xerces 1.x is present
>>   -xerces.home=${base.path}/xerces-2_1_0
>>   +xerces.home=${base.path}/xerces-2_2_0
>>xerces.lib=${xerces.home}
>>   
>> -xerces.loc=http://xml.apache.org/dist/xerces-j/Xerces-J-bin.2.1.0.tar.gz
>>   
>> +xerces.loc=http://xml.apache.org/dist/xerces-j/Xerces-J-bin.2.2.0.tar.gz
>>xercesImpl.jar=${xerces.lib}/xercesImpl.jar
>>xmlParserAPIs.jar=${xerces.lib}/xmlParserAPIs.jar
> 
> 
> Shouln't we stay with xerces 2.1.0 until we found the problem with 2.2.0 ?

Even in this case we have to change the sample file:
+++
$ wget http://xml.apache.org/dist/xerces-j/Xerces-J-bin.2.1.0.tar.gz
--12:00:13--  http://xml.apache.org/dist/xerces-j/Xerces-J-bin.2.1.0.tar.gz
=> `Xerces-J-bin.2.1.0.tar.gz'
Resolving proxy.mch.fsc.net... done.
Connecting to proxy.mch.fsc.net[172.25.80.170]:81... connected.
Proxy request sent, awaiting response... 404 Not Found
12:00:13 ERROR 404: Not Found.
+++

> 
> 
> 
> -- 
> To unsubscribe, e-mail:   
> 
> For additional commands, e-mail: 
> 
> 
> 




--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

Re: cvs commit: jakarta-tomcat-4.0 build.properties.sample

[jean-frederic clere]

Hi,

Well the downlaod task needs a little more.
I would like to test *.loc:
if starting with http then use a download task.
if not use a cvs + build task.

Any comments?

Cheers

Jean-frederic


[EMAIL PROTECTED] wrote:
> jfclere 2002/10/04 01:43:48
> 
>   Modified:.build.properties.sample
>   Log:
>   Update to the laster commons-logging (the older gives problems with log4j).
>   
>   Revision  ChangesPath
>   1.51  +3 -3  jakarta-tomcat-4.0/build.properties.sample
>   
>   Index: build.properties.sample
>   ===
>   RCS file: /home/cvs/jakarta-tomcat-4.0/build.properties.sample,v
>   retrieving revision 1.50
>   retrieving revision 1.51
>   diff -u -r1.50 -r1.51
>   --- build.properties.sample 4 Sep 2002 13:38:50 -   1.50
>   +++ build.properties.sample 4 Oct 2002 08:43:48 -   1.51
>   @@ -78,11 +78,11 @@
>
>
># - Commons Logging, version 1.0.1 or later -
>   -commons-logging.home=${base.path}/commons-logging-1.0.1
>   +commons-logging.home=${base.path}/commons-logging-1.0.2
>commons-logging.lib=${commons-logging.home}
>commons-logging-api.jar=${commons-logging.lib}/commons-logging-api.jar
>commons-logging.jar=${commons-logging.lib}/commons-logging.jar
>   
>-commons-logging.loc=http://jakarta.apache.org/builds/jakarta-commons/release/commons-logging/v1.0.1/commons-logging-1.0.1.tar.gz
>   
>+commons-logging.loc=http://jakarta.apache.org/builds/jakarta-commons/release/commons-logging/v1.0.2/commons-logging-1.0.2.tar.gz
>
>
># - Java Naming and Directory Interface (JNDI), version 1.2 or later -
>   
>   
>   
> 
> --
> To unsubscribe, e-mail:   
> For additional commands, e-mail: 
> 
> 




--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

DO NOT REPLY [Bug 13270] - Container's AJP13 handler does not setTcpNoDelay on accept

[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://nagoya.apache.org/bugzilla/show_bug.cgi?id=13270

Container's AJP13 handler does not setTcpNoDelay on accept





--- Additional Comments From [EMAIL PROTECTED]  2002-10-04 09:05 ---
There must be something wrong on your OS setup, since I never saw a ajp13
req/replie took 200ms on others boxes (Linux, Windows), may be something
specific to MacOS X IP stack.

BTW, the support for no delay is included :

Just try to add tcpnoDelay=true in server.xml part of Ajp13.

Regards

--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

Re: cvs commit: jakarta-tomcat-4.0 build.properties.sample

[Henri Gomez]

[EMAIL PROTECTED] wrote:
> jfclere 2002/10/04 01:46:33
> 
>   Modified:.build.properties.sample
>   Log:
>   Upgrade to the lastest xerces.
>   
>   Revision  ChangesPath
>   1.52  +3 -3  jakarta-tomcat-4.0/build.properties.sample
>   
>   Index: build.properties.sample
>   ===
>   RCS file: /home/cvs/jakarta-tomcat-4.0/build.properties.sample,v
>   retrieving revision 1.51
>   retrieving revision 1.52
>   diff -u -r1.51 -r1.52
>   --- build.properties.sample 4 Oct 2002 08:43:48 -   1.51
>   +++ build.properties.sample 4 Oct 2002 08:46:33 -   1.52
>   @@ -117,9 +117,9 @@
>
># - Xerces XML Parser, version 2.0.0 or later -
># Note: Optional with JDK 1.4+, or if Xerces 1.x is present
>   -xerces.home=${base.path}/xerces-2_1_0
>   +xerces.home=${base.path}/xerces-2_2_0
>xerces.lib=${xerces.home}
>   -xerces.loc=http://xml.apache.org/dist/xerces-j/Xerces-J-bin.2.1.0.tar.gz
>   +xerces.loc=http://xml.apache.org/dist/xerces-j/Xerces-J-bin.2.2.0.tar.gz
>xercesImpl.jar=${xerces.lib}/xercesImpl.jar
>xmlParserAPIs.jar=${xerces.lib}/xmlParserAPIs.jar

Shouln't we stay with xerces 2.1.0 until we found the problem with 2.2.0 ?



--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

cvs commit: jakarta-tomcat-4.0 build.properties.sample

[jfclere]

jfclere 2002/10/04 01:46:33

  Modified:.build.properties.sample
  Log:
  Upgrade to the lastest xerces.
  
  Revision  ChangesPath
  1.52  +3 -3  jakarta-tomcat-4.0/build.properties.sample
  
  Index: build.properties.sample
  ===
  RCS file: /home/cvs/jakarta-tomcat-4.0/build.properties.sample,v
  retrieving revision 1.51
  retrieving revision 1.52
  diff -u -r1.51 -r1.52
  --- build.properties.sample   4 Oct 2002 08:43:48 -   1.51
  +++ build.properties.sample   4 Oct 2002 08:46:33 -   1.52
  @@ -117,9 +117,9 @@
   
   # - Xerces XML Parser, version 2.0.0 or later -
   # Note: Optional with JDK 1.4+, or if Xerces 1.x is present
  -xerces.home=${base.path}/xerces-2_1_0
  +xerces.home=${base.path}/xerces-2_2_0
   xerces.lib=${xerces.home}
  -xerces.loc=http://xml.apache.org/dist/xerces-j/Xerces-J-bin.2.1.0.tar.gz
  +xerces.loc=http://xml.apache.org/dist/xerces-j/Xerces-J-bin.2.2.0.tar.gz
   xercesImpl.jar=${xerces.lib}/xercesImpl.jar
   xmlParserAPIs.jar=${xerces.lib}/xmlParserAPIs.jar
   
  
  
  

--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

cvs commit: jakarta-tomcat-4.0 build.properties.sample

[jfclere]

jfclere 2002/10/04 01:43:48

  Modified:.build.properties.sample
  Log:
  Update to the laster commons-logging (the older gives problems with log4j).
  
  Revision  ChangesPath
  1.51  +3 -3  jakarta-tomcat-4.0/build.properties.sample
  
  Index: build.properties.sample
  ===
  RCS file: /home/cvs/jakarta-tomcat-4.0/build.properties.sample,v
  retrieving revision 1.50
  retrieving revision 1.51
  diff -u -r1.50 -r1.51
  --- build.properties.sample   4 Sep 2002 13:38:50 -   1.50
  +++ build.properties.sample   4 Oct 2002 08:43:48 -   1.51
  @@ -78,11 +78,11 @@
   
   
   # - Commons Logging, version 1.0.1 or later -
  -commons-logging.home=${base.path}/commons-logging-1.0.1
  +commons-logging.home=${base.path}/commons-logging-1.0.2
   commons-logging.lib=${commons-logging.home}
   commons-logging-api.jar=${commons-logging.lib}/commons-logging-api.jar
   commons-logging.jar=${commons-logging.lib}/commons-logging.jar
  
-commons-logging.loc=http://jakarta.apache.org/builds/jakarta-commons/release/commons-logging/v1.0.1/commons-logging-1.0.1.tar.gz
  
+commons-logging.loc=http://jakarta.apache.org/builds/jakarta-commons/release/commons-logging/v1.0.2/commons-logging-1.0.2.tar.gz
   
   
   # - Java Naming and Directory Interface (JNDI), version 1.2 or later -
  
  
  

--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

DO NOT REPLY [Bug 12946] - parameter serverRoot from jk2.properties not read; workaround

[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://nagoya.apache.org/bugzilla/show_bug.cgi?id=12946

parameter serverRoot from jk2.properties not read; workaround





--- Additional Comments From [EMAIL PROTECTED]  2002-10-04 08:15 ---
Right!
As I now notice, there is no "serverRoot" parameter mentioned in Jakarta's JK2-
Documentation.

Even so: How does the native side JK get to know about the location of 
workers2.properties ?? Appearently the value of "serverRoot", as stated in 
$CATALINA_HOME/conf/jk2.properties or elsewhere, must be read in order for the 
native JK to take knowledge of the location of workers2.properties and be able 
to process it.

At the time I submitted this report, $CATALINA_HOME/conf/jk2.properties was one 
I took from Simon Steward's web site 
http://www.pubbitch.org/jboss/mod_jk2.html, having only modified 
$CATALINA_HOME. Locations were correct

# jk2.properties

# list of needed handlers.
handler.list=apr,channelSocket,channelUnix,request

# Set the default port for the channelSocket
channelSocket.port=8009

# State where the UNIX domain socket is located
channelUnix.file=/opt/jakarta-tomcat-4.1.10/work/jk2.socket

# Dynamic library
serverRoot=/usr/local/apache2
apr.NativeSo=/opt/jakarta-tomcat-4.1.10/lib/libjkjni.so

# end of jk2.properties
  
By the time, $APACHE_HOME/conf/workers2.properties also was one I took from the 
same JBoss web site, having only modified $CATALINA_HOME. Locations were correct

# workers2.properties

# Shared memory handling. Needs to be set.
[shm]
file=/usr/local/apache2/logs/shm.file
size=1048576

# Example socket channel, explicitly set port and host.
[channel.socket:localhost:8009]
port=8009
host=127.0.0.1

# Example UNIX domain socket
[channel.un:/usr/local/tomcat/work/jk2.socket]
tomcatId=localhost:8009
debug=0

# define the worker
[ajp13:localhost:8009]
channel=channel.un:/usr/local/tomcat/work/jk2.socket
# To use the TCP/IP socket instead, just comment out the above
# line, and uncomment the one below
#channel=channel.socket:localhost:8009

# Announce a "status" worker
[status:status]

# Uri mapping
[uri:/examples/*]
#worker=ajp13:localhost:8009
worker=ajp13:/usr/local/tomcat/work/jk2.socket

[uri:/status/*]
worker=status:status

# end of workers2.properties

Before exporting  "serverRoot=/usr/local/apache2", thee startup messages in 
$CATALINA_HOME/logs/catalina.out were like


[INFO] Registry - -Loading registry information
[INFO] Registry - -Creating new Registry instance
[INFO] Registry - -Creating MBeanServer
[INFO] Http11Protocol - -Initializing Coyote HTTP/1.1 on port 8080
Starting service Tomcat-Standalone
Apache Tomcat/4.1.10
[INFO] Http11Protocol - -Starting Coyote HTTP/1.1 on port 8080
[Fri Oct 04 09:51:29 2002] (error ) [jk_config_file.c (261)]  config.update(): 
Can't find config file ${serverRoot}/conf/workers2.properties
[Fri Oct 04 09:51:29 2002] ( info ) [jk_config.c (246)]  config.setAttribute() 
Error setting config: file ${serverRoot}/conf/workers2.properties
[Fri Oct 04 09:51:29 2002] (error ) [jk_logger_file.c (171)]  Initializing log 
file stderr
[Fri Oct 04 09:51:29 2002] (error ) [jk_shm.c (333)]  shm.init(): No file
[Fri Oct 04 09:51:29 2002] ( info ) [jk_workerEnv.c (403)]  workerEnv.init() ok 
${serverRoot}/conf/workers2.properties
[INFO] ChannelSocket - -JK2: ajp13 listening on tcp port 8009
[INFO] ChannelUn - -JK: listening on unix socket: /opt/jakarta-tomcat-
4.1.10/work/jk2.socket
[INFO] JkMain - -Jk running ID=0 time=1/87  config=/opt/jakarta-tomcat-
4.1.10/conf/jk2.properties
[INFO] ChannelSocket - -Port busy 8009 java.net.BindException: Address already 
in use
[INFO] ChannelSocket - -JK2: ajp13 listening on tcp port 8010
[INFO] ChannelUn - -JK: listening on unix socket: /opt/jakarta-tomcat-
4.1.10/work/jk2.socket1
[INFO] JkMain - -Jk running ID=1 time=1/18  config=/opt/jakarta-tomcat-
4.1.10/conf/jk2.properties
[Fri Oct 04 09:51:29 2002] ( info ) [jk_jni_aprImpl.c (470)]  jkInvoke() invoke 
f30d4c38 
[Fri Oct 04 09:51:29 2002] ( info ) [jk_jni_aprImpl.c (470)]  jkInvoke() invoke 
f30d4c38 


AFTER putting

serverRoot=/usr/local/apache2
export serverRoot

at the top of $CATALINA_HOME/bin/startup.sh

the startup messages turned to

[INFO] Registry - -Loading registry information
[INFO] Registry - -Creating new Registry instance
[INFO] Registry - -Creating MBeanServer
[INFO] Http11Protocol - -Initializ

Apache 2.0.43 is out

[Henri Gomez]

We should provide new binaries for JK and JK2.

I'll do JK/JK2 for Linux boxes (and FreeBSD)

Who could do the same for Windows, Netware and Solaris ?

BTW, I'm still waiting an account on moof to build a MacOSX
version.



--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

Re: [PROPOSAL] Splitting docs for JK2

[Henri Gomez]

Costin Manolache wrote:
> Mladen Turk wrote:
> 
> 
>>>-Original Message-
>>>From: Henri Gomez [mailto:[EMAIL PROTECTED]]
>>>
>>>+0 (Ok but can't help right now)
>>
>>Could you check:
>>
>>http://jakarta.apache.org/~mturk/docs/
> 
> 
> Looks good. Can you check in ? 
> 
> Henri: would you mind if we remove the reference to ajp14 ? 

My little proposal baby ?

> I thought we decided we'll stick with ajp13 and just add new 
> message types for the extra functions - so we should at 
> least rename it to 'future extensions to ajp13'.

So I will rename it to 'proposed extensions for ajp13'



--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

Re: [5.0] [VOTE] Removal of the LE distribution

[Henri Gomez]

Remy Maucherat wrote:
> Hi all,
> 
> Before starting to release 5.0.x milestones, I would like to propose 
> having only one distribution for Tomcat 5.0.x, and standardize on what 
> the LE distribution contains (so well, it's more the other distribution 
> which gets removed).
> 
> It has some advantages:
> - it is slightly smaller (less these days now that the XML parser has to 
> be shipped again with Tomcat)
> - runs as-is on JDK 1.3 (because of the Xerces inclusion)
> - 99% Apache or Apache-style licence (the JDBC 2 standard extension is 
> needed for JDK 1.3 DataSource support :-()
> - less user confusion
> 
> The main "problem" is that the user will need additional downloads for 
> some of the more advanced features, and the package will also not run on 
> JDK 1.2 as is (but from what I've seen, JDK 1.2 compatibility may not be 
> a priority for developers).
> 
> 
> +1 [ ] Yes, remove the LE distribution
> -1 [ ] No, keep both distributions
> 

I'm OK till we could add easily missing stuff to make Tomcat 5.0 works.

It's exactly what we does in jpackage.org project in our 'strict' 
distribution.

There is 3 set of distro for Tomcat 4.1.12 RPMS :

- One is the full distro, including everything, so it's the same
   that jakarta-tomcat-4.1.12.tar.gz

- Second one is the LE distro, ie without XML parser, JDBC-STDEXT,
   ACTIVATION, JTA, MAIL, JAAS, JNDI.

   In this case at install time, rpm install via symlink
   XML stuff (parser/apis) from a known location (/usr/share/java).

   The other components activation, mail, jdbc-stdext, jaas and jndi
   should be installed by users.

- In the strict mode, only tomcat jars, ie all jars (including
   jakarta-commons-*, servlet.jar, mx4j), should be present at rpm
   install time and will be automatically installed via
   symlink in tomcat directories.

So I'm fine with having a single tomcat distribution, if we explains
users WHERE it could find the missing jars.

And having a Tomcat 5.0 containing only 100% OSS stuffs seems natural
for an ASF project.

BTW, support should be added in TC 5.0 to detect missing jars, ie
JDBC-EXT, JNDI, JAAS, and automatically (with reports log) remove
functionalities.

Regards




--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

Re: Is Compile Failure? was Re: Need some clarifications

[Henri Gomez]

Steve Downey wrote:
> On Thursday 03 October 2002 12:14 pm, Henri Gomez wrote:
> 
>>Steve Downey wrote:
>>
>>>Actually, with the recent release of commons-logging, we should be able
>>>to get rid of the explicit LogKit and Log4J. They're there so as to get a
>>>complete build of commons-logging. Tomcat 5 itself doesn't use either
>>>directly.
>>>
>>>Xerces is a different issue. There was a bug that was preventing Tomcat
>>>from migrating to the latest version. Unfortunately, I no longer remember
>>>the details. Anyone know why we're using 2.1.0 instead of 2.2.0?
>>
>> From what I experienced with Xerces j 2.2.0 it seems it does
>>much more validity check and for instance found a '--' somewhere
>>in comments (1 EUR to the first who find where).
>>
>>Previous version of Xerces or crimson didn't got that problem.
>>
>>if we could see which xml/dtd/tld is reported buggy, which
>>will able to see if it's a bug or a features (ie a more strict
>>check of xml rules)
> 
> OK, from the 'this shouldn't work department', this patch 'fixes' the problem:
> Index: ./jsr152/src/share/dtd/web-jsptaglibrary_1_2.dtd
> ===
> RCS file: 
> /home/cvspublic/jakarta-servletapi-5/jsr152/src/share/dtd/web-jsptaglibrary_1_2.dtd,v
> retrieving revision 1.1.1.1
> diff -u -r1.1.1.1 web-jsptaglibrary_1_2.dtd
> --- ./jsr152/src/share/dtd/web-jsptaglibrary_1_2.dtd13 Aug 2002 16:20:58 
> -  1.1.1.1
> +++ ./jsr152/src/share/dtd/web-jsptaglibrary_1_2.dtd3 Oct 2002 20:42:30 
> -
> @@ -304,6 +304,7 @@
>   java.lang.String is default.
> 
>  declare  Whether the variable is declared or not.
> +
>   True is the default.
> 
>  scopeThe scope of the scripting varaible
> 
> 
> 
> Something quite strange is going on.

You just add an empty line in this dtd and it works now ?

I was thinking it could be with -- in some dtd, ie
 line in web-app_2_3.dtd :






--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

Re: [5.0] [VOTE] Removal of the LE distribution

[Henri Gomez]

> For example - is JDK1.4 available for BSD or Sparc/Linux or Arm/Linux ? 
> I think BSD and linux are fine operating systems and Tomcat should run
> on them.

And that's not only true for Linux/BSD.

For example IBM OS (AIX, OS/2, OS400) have still no JDK 1.4
(and these are not hackers OS ;)



--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

Re: [5.0] [VOTE] Removal of the LE distribution

[Henri Gomez]

> My opinion on this issue is that Tomcat 5 should have J2SE 1.4 in
> compliance with JSP 2.0 spec basically.

Sorry but making JDK 1.4 mandatory for Tomcat 5 will prevent us to
use it on many systems. Many still use IBM SDK and the IBM SDK 1.4
is only available on zSeries.

So a big -1 to make JDK 1.4 mandatory for TC5.



--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

Re: cvs commit: jakarta-tomcat-connectors/jk/native2/common jk_worker_lb.c

[Henri Gomez]

> No, but extending one dtd would be better than reinventing everything.
> I will try to make a cleanup as soon as I have time. (docs need a lot of 
> time).

I confirm ;-)

BTW, any DTD will be fine but we should take a look at what others
jakarta and xml projects are using.





--
To unsubscribe, e-mail:   
For additional commands, e-mail: