DO NOT REPLY [Bug 32141] - memory leak in jk1.2 with tomcat-5.0.27,apache 1.3.31

[bugzilla]

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

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





--- Additional Comments From [EMAIL PROTECTED]  2004-12-06 07:22 ---
The problem is that I can't identify who could be holding a reference to the 
ObjectNames.  The screen shots don't show a corresponding number of 
RequestInfos, so it seems that request unregistration is working, and there 
also aren't a corresponding number of MsgContexts, which is the only other 
object that should have a reference.

If you can provide more research into the leak, it would be very appreciated.


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

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

DO NOT REPLY [Bug 32141] - memory leak in jk1.2 with tomcat-5.0.27,apache 1.3.31

[bugzilla]

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

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





--- Additional Comments From [EMAIL PROTECTED]  2004-12-06 04:25 ---
The JMX Request-Registration is enabled by default. I need to restart my tomcat 
every week before out-of-memory error.

I re-test my case again and set the heap size to 64M. I did not stick with 
Optimizeit this time and I got an out-of-memory error after one night of non-
stopping requests.

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

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

Bug report for Tomcat 4 [2004/12/06]

[bugzilla]

+---+
| Bugzilla Bug ID   |
| +-+
| | Status: UNC=Unconfirmed NEW=New ASS=Assigned|
| | OPN=ReopenedVER=Verified(Skipped Closed/Resolved)   |
| |   +-+
| |   | Severity: BLK=Blocker CRI=CriticalMAJ=Major |
| |   |   MIN=Minor   NOR=Normal  ENH=Enhancement   |
| |   |   +-+
| |   |   | Date Posted |
| |   |   |  +--+
| |   |   |  | Description  |
| |   |   |  |  |
| 3614|Opn|Nor|2001-09-14|bug in manager webapp |
| 3839|Opn|Maj|2001-09-26|Problem bookmarking login page|
| 3888|Opn|Blk|2001-09-30|WebappClassLoader: Lifecycle error : CL stopped   |
| 4138|Opn|Nor|2001-10-12|Processor threads have inconsistent ClassLoader st|
| 5329|New|Nor|2001-12-08|NT Service exits startup before Tomcat is finished|
| 5795|New|Enh|2002-01-10|Catalina Shutdown relies on localhost causing prob|
| 5829|New|Enh|2002-01-13|StandardManager needs to cope with sessions throwi|
| 5985|New|Enh|2002-01-23|Tomcat should perform a more restrictive validatio|
| 6229|New|Enh|2002-02-04|Need way to specify where to write catalina.out   |
| 6582|New|Min|2002-02-20|Sample code does not match behavior   |
| 6600|Opn|Enh|2002-02-20|enodeURL adds 'jsession' when 'isRequestedSessionI|
| 6614|New|Enh|2002-02-21|Have Bootstrap and StandardClassLoader use the sam|
| 6671|New|Enh|2002-02-25|Simple custom tag example uses old declaration sty|
| 7043|New|Enh|2002-03-12|database user and password for JDBC Based Store   |
| 7360|New|Nor|2002-03-22|res-sharing-scope not supported   |
| 7374|New|Enh|2002-03-22|Apache Tomcat/4.0.1 message on standard output|
| 7676|New|Enh|2002-04-02|Allow name property to use match experssions in  without className in server.xml produces N|
|10982|New|Min|2002-07-19|JNDI URL Handler class is missing in naming-resour|
|11069|Opn|Enh|2002-07-23|Tomcat not flag error if tld is outside of /WEB-IN|
|11129|New|Enh|2002-07-24|New valve for putting the sessionIDs in the reques|
|11248|New|Enh|2002-07-29|DefaultServlet doesn't send expires header|
|11645|New|Nor|2002-08-13|RequestStream and HttpRequestStream throw an IOExc|
|11662|New|Maj|2002-08-13|GlobalResources unavailable in DefaultContext |
|11748|Opn|Maj|2002-08-15|Location header for redirection does not contain t|
|11754|Opn|Enh|2002-08-15|Synchronous shutdown script - shutdown.sh should w|
|12069|New|Enh|2002-08-27|Creation of more HttpSession objects for one previ|
|12428|Opn|Maj|2002-09-09|request.getUserPrincipal(): Misinterpretation of s|
|12658|New|Enh|2002-09-15|a proxy host and port at the  element level |
|12682|Unc|Nor|2002-09-16|Problem when recompiling servlets with JDBC connec|
|12766|New|Enh|2002-09-18|Tomcat should use tld files in /WEB-INF/ over vers|
|12946|Unc|Nor|2002-09-24|parameter serverRoot from jk2.properties not read;|
|13014|New|Blk|2002-09-26|OS/390/USS - Invalid   in servlet ma|
|13040|New|Nor|2002-09-26|can't retrieve external context who's uri is a sub|
|13240|New|Nor|2002-10-03|CGI works only with Java version 1.3+ |
|13309|Opn|Enh|2002-10-04|Catalina calls System.exit()  |
|13430|New|Nor|2002-10-09|WWW-Authenticate Header Is Not Sent   |
|13606|Opn|Nor|2002-10-14|Compiler not thread safe  |
|13634|New|Enh|2002-10-15|Allowing system properties to be substituted in co|
|13689|Opn|Enh|2002-10-16|Classloader paths for 'Common' classes and librari|
|13731|New|Enh|2002-10-17|Final request, response, session and other variabl|
|13846|New|Nor|2002-10-22|If-Modified-Since results in incorrect headers|
|13941|New|Enh|2002-10-24|reload is VERY slow   |
|13965|New|Enh|2002-10-25|Catalina.sh correction request for Tru64 Unix |
|13983|New|Nor|2002-10-25|RMI call from Web Application throws SocketExcepti|
|14097|New|Enh|2002-10-30|hardcoded registry value for vm lets tomcat servic|
|14323|Unc|Nor|2002-11-07|Form Based Authentication Not Triggered By Coyote |
|14416|New|Enh|2002-11-10|blank tag name in TLD cause NullPointerException  |
|14635|New|Enh|2002-11-18|Should be possible not to have -MM-DD in log f|
|14766|New|Enh|2002-11-22|Redirect Vavle|
|14993|New|Enh|2002-12-02|Possible obselete synchronized declaration|
|15115|New|Enh|2002-12-05|correct docs... XML parser *cannot* b

Bug report for Watchdog [2004/12/06]

[bugzilla]

+---+
| Bugzilla Bug ID   |
| +-+
| | Status: UNC=Unconfirmed NEW=New ASS=Assigned|
| | OPN=ReopenedVER=Verified(Skipped Closed/Resolved)   |
| |   +-+
| |   | Severity: BLK=Blocker CRI=CriticalMAJ=Major |
| |   |   MIN=Minor   NOR=Normal  ENH=Enhancement   |
| |   |   +-+
| |   |   | Date Posted |
| |   |   |  +--+
| |   |   |  | Description  |
| |   |   |  |  |
|  278|Unc|Nor|2000-12-04|Bug in GetParameterValuesTestServlet.java file Bug|
|  279|Unc|Nor|2000-12-04|Logical Error in GetParameterValuesTestServlet Bug|
|  469|Unc|Nor|2001-01-17|in example-taglib.tld "urn" should be "uri" BugRat|
|  470|Unc|Nor|2001-01-17|FAIL positiveForward.jsp and positiveInclude.jsp B|
| 9634|New|Enh|2002-06-05|No tests exist for ServletContext.getResourcePaths|
|10703|New|Enh|2002-07-11|Need to test getRequestURI after RequestDispatcher|
|11336|New|Enh|2002-07-31|Test wrapped path methods with RD.foward()|
|11663|New|Maj|2002-08-13|JSP precompile tests rely on Jasper specific behav|
|11664|New|Maj|2002-08-13|A sweep is needed of all Watchdog 4.0 tag librarie|
|11665|New|Maj|2002-08-13|ServletToJSPErrorPageTest and ServletToServletErro|
|11666|New|Maj|2002-08-13|SetBufferSize_1TestServlet is invalid.|
|14004|New|Maj|2002-10-28|Incorrent behaviour of all attribute-related lifec|
|15504|New|Nor|2002-12-18|JSP positiveGetValues test relies on order preserv|
|24649|New|Nor|2003-11-12|getRemoteHost fails when agent has uppercase chara|
|29398|New|Nor|2004-06-04|Update site and note current status   |
+-+---+---+--+--+
| Total   15 bugs   |
+---+

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

Bug report for Tomcat 3 [2004/12/06]

[bugzilla]

+---+
| Bugzilla Bug ID   |
| +-+
| | Status: UNC=Unconfirmed NEW=New ASS=Assigned|
| | OPN=ReopenedVER=Verified(Skipped Closed/Resolved)   |
| |   +-+
| |   | Severity: BLK=Blocker CRI=CriticalMAJ=Major |
| |   |   MIN=Minor   NOR=Normal  ENH=Enhancement   |
| |   |   +-+
| |   |   | Date Posted |
| |   |   |  +--+
| |   |   |  | Description  |
| |   |   |  |  |
| 2350|Ver|Nor|2001-06-27|ServletConfig.getInitParameter() requires url-patt|
| 2478|Opn|Cri|2001-07-06|Passing Session variables between JSP's and Servle|
| 4551|Opn|Nor|2001-10-31|Ctx( /tt01 ): IOException in: R( /tt01 + /com/abc/|
| 4980|New|Min|2001-11-20|Startup message indicates incorrect log file  |
| 4994|New|Nor|2001-11-21|Tomcat needs a mechanism for clean and certain shu|
| 5064|New|Cri|2001-11-25|Socket write error when include files is more than|
| 5108|New|Maj|2001-11-26|Docs for Tomcat 3.2.x appear to be for Tomcat 3.3 |
| 5137|New|Nor|2001-11-27|Null pointer in class loader after attempting to r|
| 5160|Unc|Maj|2001-11-28|'IllegalStateException'   |
| 5331|New|Nor|2001-12-09|getPathInfo vs URL normalization  |
| 5510|New|Blk|2001-12-19|How to call ejb deployed in JBoss from Tomcat serv|
| 5756|New|Nor|2002-01-08|jspc.bat exits with wrong ERRORLEVEL  |
| 5797|New|Nor|2002-01-10|UnCatched ? StringIndexOutOfBoundsException: Strin|
| 6027|New|Maj|2002-01-25|Tomcat  Automatically shuts down as service   |
| 6168|New|Blk|2002-02-01|IllegalStateException |
| 6451|New|Cri|2002-02-14|Stackoverflow |
| 6478|New|Enh|2002-02-14|Default Tomcat Encoding   |
| 6488|Ver|Maj|2002-02-15|Error: 304. Apparent bug in default ErrorHandler c|
| 6648|New|Nor|2002-02-25|jakarta-servletapi build with java 1.4 javadoc err|
| 6702|New|Cri|2002-02-27|win 2k services not working   |
| 6796|New|Cri|2002-03-01|Tomcat dies periodically  |
| 6989|New|Maj|2002-03-08|Unable to read tld file during parallel JSP compil|
| 7013|New|Cri|2002-03-10|Entering a servlet path with non-ISO8859-1 charact|
| 7227|New|Nor|2002-03-19| directive don't work |
| 7626|New|Nor|2002-03-29|classloader not working properly  |
| 7652|New|Cri|2002-04-01|Tomcat stalls periodically|
| 7785|New|Blk|2002-04-06|tomcat bug in context reloading   |
| 7863|New|Maj|2002-04-09|I have a problem when running Tomcat with IIS |
| 8187|New|Cri|2002-04-17|Errors when Tomcat used with MS Access database   |
| 8239|New|Cri|2002-04-18|Resource temporary unavailable|
| 8263|New|Cri|2002-04-18|url-pattern easy to circumvent|
| 9250|New|Maj|2002-05-20|outOfMemoryError  |
| 9367|New|Maj|2002-05-23|HttpSessionBindingEvent not thrown for HttpSession|
| 9390|New|Nor|2002-05-24|jasper compilation error in tomcat|
| 9480|New|Nor|2002-05-29|Data connection pooling   |
| 9607|New|Maj|2002-06-04|precompile JSP|
| 9737|Ver|Nor|2002-06-10|ArrayIndexOutOfBoundsException when sending just p|
|10047|New|Cri|2002-06-20|IllegalStateException |
|10202|New|Maj|2002-06-25|Tomcat is not responding in time  |
|10357|Unc|Blk|2002-06-30|java.lang.IllegalArgumentException: Short Read|
|10406|New|Cri|2002-07-02|IllegalStateException |
|11087|New|Blk|2002-07-23|IllegalStateException |
|11286|New|Maj|2002-07-30|Tomcat threads not respond if increase JVM size   |
|11466|New|Nor|2002-08-05|ContextManager: SocketException reading request   |
|12156|New|Cri|2002-08-29|Apache and Tomcat 3.3.1 Interworking problem  |
|12194|New|Maj|2002-08-30|Tomcat does not send WWW-Authenticate header  |
|12475|New|Nor|2002-09-10|CPU Usage is 0%, Tomcat doesn't response  |
|12852|New|Nor|2002-09-20|May be error in _jspService() -> out.flushBuffers(|
|13706|New|Nor|2002-10-16|Many Processs Java / TOMCAT in a PC with Linux Con|
|14386|New|Maj|2002-11-08|Date headers corrupted using setDateHeader|
|15632|New|Nor|2002-12-23|Problem with the Tomcat Sessions Parameter on URL |
|15872|New|Blk|2003

HTTP headers and end of response, reposted for better reading

[Hans Verschoor]

Hi all,

 (repost for better reading)
I am working at an inplementation of RFC2671 Digest Authentication.
I want to do the authentication in my servlet application because I need 
additional data with
the userid and password. For reasons of session management and security I 
should be able
to send an Authentication-Info header in my response.
This is the commonly accepted implementation scheme: If the login fails a 401 
is sent thus:
new login, when the login is ok an Authentication-Info header is send together 
with the normal
200 OK response.
So what, "You can set headers in the HttpServletResponse" would one say, but 
here's a problem:
RFC2617 literally states: "The Authentication-Info" header is allowed in the 
trailer of an HTTP
message transferred via chunked transfer encoding".
Some browsers (MSIE and Mozilla) have taken this as: '... is ONLY allowed ...'.
I had a discussion with Paul Leach from Microsoft, one of the co-authors of 
RFC2617, and he
pointed out that the reason for it was that with a given quality of protection 
("auth-int")  the content
of the message is part of the calculation to check wether the 
Authentication-Info header is valid
and "for that reason" (huh?) the Authentication-Info header has to follow the 
message content
block (funny enough MSIE and Mozilla do not support this option, only Opera 
does).
However, the placement of HTTP headers at the end of a response is currently 
not supported in
Tomcat.
This all brings me in a stalemate position: IE and Mozilla are the most widely 
used browsers by
far but will only accept the Authentication-Info header at the end but Tomcat 
does not support this.
This leaves only the "standard" options for digest athentication: a fairly 
simple check against
userid:password pairs, which is not acceptable for me ( no user categories, 
only atomic userid's,
database replications needed, no addtional data allowed when checking login, 
less detection of
tampering, no password change polices, no "invisible" digest changes, session 
management by
cookies, etc).
I realize that the implementation of  "trailing headers" means implications for 
the Servlet API,
something like: HttpServletResponse.setHeader(String name, String value, 
boolean atEnd).
So I had the idea to prefix the header name with a + sign to indicate that the 
header should follow
the content and that chunked encoding should be in place. I had a look at the 
Response source
code, but until now it was not very clear to me how to implement the trick.
To conclude, of course my preferred suggestion would be: append a boolean 
argument to the
setHeader methods of the HttpServletResponse interface, not to the addHeader of 
course and
add a method: isHeaderAtEnd (String name) to detect wether the header is before 
or after the
content. This suggestions should be followed by all servlet engine implementors.
The + sign prepending "trick" would not have implications for the Servlet API. 
When looking at
the Tomcat source I cannot oversee what sources would be affected, especially 
those involved
in connectors.
Now that was a long story, who can help me ?

KR, Hans

DO NOT REPLY [Bug 32317] - Making mod_jk replication aware (Clustering Support)

[bugzilla]

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

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





--- Additional Comments From [EMAIL PROTECTED]  2004-12-05 22:27 ---
Created an attachment (id=13650)
 --> (http://issues.apache.org/bugzilla/attachment.cgi?id=13650&action=view)
Add hierarchical routing to load balancer

The attached patch concerns jk_lb_worker.c and jk_util.c.
It introduces the following features:

- additional property "domain" for workers in workers.properties
- Make routing decision hierarchical:
a) sticky worker if not in error
b) else worker from same domain
c) else local worker
d) else local domain (worker inside domain of one of the local workers)
e) any other worker

- erroneous non-sticky workers get chosen after recovery time only if their
lb_value is maximum. Avoids continously decrementing lb_value for erroneous
workers.

Patch was transformed from a patch for version 1.2.6. I did not yet have the
time to compile and test, but I know that at least Peter waits for it, so I
submit it untested.

It's predecessor for 1.2.6 has been tested and in production for several weeks
now.


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

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

Re: Annoyance in the deployer

[Remy Maucherat]

Bill Barker wrote:
Hi,
Not something major, but there's that in the deployer:
   // Make sure there is an application configuration 
directory
   // This is needed if the Context appBase is the same 
as the
   // web server document root to make sure only web 
applications
   // are deployed and not directories for web space.
   File webInf = new File(dir, "/WEB-INF");
   if (!webInf.exists() || !webInf.isDirectory() ||
   !webInf.canRead())
   continue;

Is that really useful ? I ask because it prevents dropping a folder 
containing a bunch of files in webapps (without creating a stupid 
WEB-INF folder), which could be annoying.

Actually, I recently had a case where someone accidentally deleted 
WEB-INF on a development box.  When the Context didn't load, the 
problem was noticed immediately :).
Yes, I guess it's easier to spot that particular problem :)
Personally, I like the check (but won't veto the change).  But then, I 
believe that dropping in a folder containing a bunch of static files 
is what the Alias directive in Apache/httpd is for ;-).
Ok.
Maybe I can see if we could try to make recommendations for that kind of 
defaults and behaviors in the specification.

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

Re: tomcat 5.0.29 and request.getScheme

[Luis Fernando Pardo]

Thanks for your response. I have test Tomcat with secure="trust" and I 
have got a proxy error response. This is the configuration directives 
from apache where proxypass is done:
...
ProxyPassReverse /formae http://127.0.0.1:9080/formae
RewriteRule ^/formae(.*) http://127.0.0.1:9080/formae$1 [P,L]
...

So the connection between apache and tomcat is HTTP (not HTTPS). I think 
I am ussing a correct Connection configuration because it works on 
tomcat 5.0.16 (in this configuration I did not use secure attribute). If 
I use this configuration on 5.0.29, my WEB application works fine: when 
I call to getServerName or getServerPort  methods I get my hostName and 
443 port (obtained from proxyName and proxyHost attribute values from 
Connector configuration); but when I call getScheme I do not get the 
scheme configured in this Connector.

Best regards
Peter Rossbach escribió:
Hey,,
please use secure="true"

  

Don't forget to create the Server keystore.
Please read the Connector docs:
http://jakarta.apache.org/tomcat/tomcat-5.0-doc/ssl-howto.html
http://jakarta.apache.org/tomcat/tomcat-5.0-doc/config/http.html
Regards
Peter
Luis Fernando Pardo schrieb:
Hello,
I have just upgraded my tomcat version from 5.0.16 to 5.0.29 and I 
have found a problem with the request.getScheme method. I have set 
apache server to listen on 443 port (SSL) and proxypass to Tomcat on 
local address (127.0.0.1) and port 9080. This is the connector 
configuration in Tomcat:

   
   

With this configuration in Tomcat 5.0.16, when I call to getScheme 
method, it returns "https" value, but in the new version 5.0.29 I 
always get "http".

Does anyone know if connector configuration in 5.0.29 has changed 
from 5.0.16? or may I have doing something wrong?

Thanks  in advance



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




smime.p7s
Description: S/MIME Cryptographic Signature

Re: tomcat 5.0.29 and request.getScheme

[Peter Rossbach]

Hey,,
please use secure="true"

  

Don't forget to create the Server keystore.
Please read the Connector docs:
http://jakarta.apache.org/tomcat/tomcat-5.0-doc/ssl-howto.html
http://jakarta.apache.org/tomcat/tomcat-5.0-doc/config/http.html
Regards
Peter
Luis Fernando Pardo schrieb:
Hello,
I have just upgraded my tomcat version from 5.0.16 to 5.0.29 and I 
have found a problem with the request.getScheme method. I have set 
apache server to listen on 443 port (SSL) and proxypass to Tomcat on 
local address (127.0.0.1) and port 9080. This is the connector 
configuration in Tomcat:

   
   

With this configuration in Tomcat 5.0.16, when I call to getScheme 
method, it returns "https" value, but in the new version 5.0.29 I 
always get "http".

Does anyone know if connector configuration in 5.0.29 has changed from 
5.0.16? or may I have doing something wrong?

Thanks  in advance


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

tomcat 5.0.29 and request.getScheme

[Luis Fernando Pardo]

Hello,
I have just upgraded my tomcat version from 5.0.16 to 5.0.29 and I have 
found a problem with the request.getScheme method. I have set apache 
server to listen on 443 port (SSL) and proxypass to Tomcat on local 
address (127.0.0.1) and port 9080. This is the connector configuration 
in Tomcat:

   
   

With this configuration in Tomcat 5.0.16, when I call to getScheme 
method, it returns "https" value, but in the new version 5.0.29 I always 
get "http".

Does anyone know if connector configuration in 5.0.29 has changed from 
5.0.16? or may I have doing something wrong?

Thanks  in advance


smime.p7s
Description: S/MIME Cryptographic Signature