Re: [linux CP COMMAND options]
On Tue, 2002-09-10 at 03:56, micael wrote: I will investigate this and do thank you. You are welcome. Bojan -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: cvs commit: jakarta-tomcat-connectors/jk/xdocs menu.idx style.xsl.in
Henri Gomez wrote: [EMAIL PROTECTED] wrote: jfclere 2002/09/09 08:00:58 Modified:jk/xdocs menu.idx style.xsl.in Log: Add code to allow a dummy document/ in menu.idx: To separte jk and jk2. Excellent, we just need now to pass the subpart name and will be ready ;) I'm still waiting comments on jk load-balancing settings after the commited lb patches from May 2002 (Costin, Bern, Matthias) I got your mail and sent it to you directly. Should I send it to the list too? Bernd -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- Dipl.-Inform. Bernd Koecke UNIX-Entwicklung Schlund+Partner AG Fon: +49-721-91374-0 E-Mail: [EMAIL PROTECTED] msg32976/pgp0.pgp Description: PGP signature
DO NOT REPLY [Bug 12434] - Version ID of 4.1.10 is wrong
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=12434. 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=12434 Version ID of 4.1.10 is wrong --- Additional Comments From [EMAIL PROTECTED] 2002-09-10 07:36 --- Created an attachment (id=2986) Additional Comment -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
cvs commit: jakarta-tomcat-connectors/jk/xdocs menu.idx style.xsl.in
hgomez 2002/09/10 01:02:13
Modified:jk/xdocs menu.idx style.xsl.in
Log:
Add section in document, allowing spacing in final HTML.
Still behind JF for XSL but ...
Revision ChangesPath
1.9 +14 -5 jakarta-tomcat-connectors/jk/xdocs/menu.idx
Index: menu.idx
===
RCS file: /home/cvs/jakarta-tomcat-connectors/jk/xdocs/menu.idx,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -r1.8 -r1.9
--- menu.idx 9 Sep 2002 15:00:57 - 1.8
+++ menu.idx 10 Sep 2002 08:02:13 - 1.9
@@ -1,18 +1,27 @@
?xml version=1.0?
index
+ section name=Presentation
document href=index.xml/
+ /section
+
+ section name=Commons
document href=common/AJPv13.xml/
document href=common/AJPv14-proposal.xml/
- document/
+ document href=faq.xml/
+ /section
+
+ section name=JK
document href=jk/aphowto.xml/
+ document href=jk/domhowto.xml/
document href=jk/iishowto.xml/
document href=jk/neshowto.xml/
- document href=jk/domhowto.xml/
document href=jk/workershowto.xml/
- document/
+ /section
+
+ section name=JK2
document href=jk2/configtc.xml/
document href=jk2/configweb.xml/
- document/
- document href=faq.xml/
+ /section
+
/index
1.10 +46 -36jakarta-tomcat-connectors/jk/xdocs/style.xsl.in
Index: style.xsl.in
===
RCS file: /home/cvs/jakarta-tomcat-connectors/jk/xdocs/style.xsl.in,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -r1.9 -r1.10
--- style.xsl.in 9 Sep 2002 15:00:57 - 1.9
+++ style.xsl.in 10 Sep 2002 08:02:13 - 1.10
@@ -150,50 +150,60 @@
within the index.
--
xsl:variable name=root select=//
-xsl:for-each select=document('menu.idx')/index/document
- xsl:variable name=href select=@href/
- xsl:if test=string-length($href) = 0
-tr height=6/
- /xsl:if
- tr
-td bgcolor=#cc width=150 colspan=2
- nobr
-a class=menu
- xsl:call-template name=converturi
-xsl:with-param name=href select=@href/
- /xsl:call-template
-/a
- /nobr
-/td
- /tr
- tr height=2
+xsl:for-each select=document('menu.idx')/index/section
+ tr height=6
+ td bgcolor=#cc width=150 colspan=2
+ xsl:value-of select=@name/
+ /td
/tr
+ xsl:for-each select=./document
+ xsl:variable name=href select=@href/
+ tr
+ td bgcolor=#cc width=150 colspan=2
+ nobr
+ a class=menu
+ xsl:call-template name=converturi
+ xsl:with-param name=href select=@href/
+ /xsl:call-template
+ /a
+ /nobr
+ /td
+ /tr
+ tr height=2
+ /tr
- !--
-Slightly more complicated, we use the document-location function
-and compare against it to see whether we are in the same file or
-not. If we actually are, we expand to the section level.
- --
- xsl:if test=$root/document/properties/title =
document(@href)/document/properties/title
-xsl:for-each select=document(@href)/document/section
- tr
-td bgcolor=#cc width=10/
-td bgcolor=#cc width=140
- a class=menu href=#{@name}
-xsl:value-of select=@name/
- /a
-/td
- /tr
- tr height=1
- /tr
-/xsl:for-each
- /xsl:if
+ !--
+ Slightly more complicated, we use the document-location
function
+ and compare against it to see whether we are in the same
file or
+ not. If we actually are, we expand to the section level.
+ --
+ xsl:if
cvs commit: jakarta-tomcat-connectors/jk/xdocs faq.xml index.xml
hgomez 2002/09/10 01:02:50 Modified:jk/xdocs/jk workershowto.xml iishowto.xml aphowto.xml neshowto.xml domhowto.xml jk/xdocs/common AJPv14-proposal.xml AJPv13.xml jk/xdocs faq.xml index.xml Log: Fixes typos and styles Revision ChangesPath 1.3 +12 -10jakarta-tomcat-connectors/jk/xdocs/jk/workershowto.xml Index: workershowto.xml === RCS file: /home/cvs/jakarta-tomcat-connectors/jk/xdocs/jk/workershowto.xml,v retrieving revision 1.2 retrieving revision 1.3 diff -u -r1.2 -r1.3 --- workershowto.xml 9 Sep 2002 09:56:35 - 1.2 +++ workershowto.xml 10 Sep 2002 08:02:49 - 1.3 @@ -73,7 +73,7 @@ p Each named worker should also have a few entries to provide additional information on his behalf. This information includes the worker's type and other related worker information. -Currently the following worker types that exists are (jk 1.2.0): +Currently the following worker types that exists are (JK 1.2.0): /p table @@ -203,13 +203,13 @@ /p p -bcachesize/b property is usefull when you're using jk in multithreaded +bcachesize/b property is usefull when you're using JK in multithreaded web servers such as Apache 2.0, IIS and Netscape. They will benefit the most by setting this value to a higher level (such as the estimated average concurrent users for Tomcat). /p p -bcache_timeout/b property should be used with bcachesize/b to specify how to time jk should keep +bcache_timeout/b property should be used with bcachesize/b to specify how to time JK should keep an open socket in cache before closing it. This property should be used to reduce the number of threads on the Tomcat WebServer. /p @@ -244,9 +244,11 @@ /p p -bsocket_timeout/b property told webserver to cut an ajp13 connection after some time of use. -It's a good way to ensure that there won't be any unused threads living on Tomcat side, with the -extra cost of reopening sockets next time a request be forwarded. +bsocket_timeout/b property told webserver to cut an ajp13 connection after some time of +inactivity. When choosing an endpoint for a request and the assigned socket is open, it will be +closed if it was not used for the configured time. +It's a good way to ensure that there won't too old threads living on Tomcat side, +with the extra cost you need to reopen the socket next time a request be forwarded. This property is very similar to bcache_timeout/b but works also in non-cache mode. /p @@ -323,7 +325,7 @@ Note: Since the JVM is multithreaded; the jni worker should be used only within multithreaded servers such as AOLServer, IIS, Netscape and Apache 2.0.br/ You should also make sure that the threading scheme used by the web servers match the one -used to build the jk web server plugin. +used to build the JK web server plugin. /p p @@ -344,7 +346,7 @@ p The bclass_path/b property can be given in multiple lines. -In this case the jk environment will concatenate all the classpath entries together +In this case the JK environment will concatenate all the classpath entries together by putting path delimiter (:/;) between the entries. /p @@ -361,7 +363,7 @@ p The cmd_line property can be given in multiple lines. -In this case the jk environment will concatenate all the cmd_line entries together by putting spaces +In this case the JK environment will concatenate all the cmd_line entries together by putting spaces between the entries. /p @@ -458,7 +460,7 @@ section name=A sample worker.properties p Since coping with worker.properties on your own is not an easy thing to do, -a sample worker.properties file is bundled along jk. +a sample worker.properties file is bundled along JK. /p p 1.3 +1 -1 jakarta-tomcat-connectors/jk/xdocs/jk/iishowto.xml Index: iishowto.xml === RCS file: /home/cvs/jakarta-tomcat-connectors/jk/xdocs/jk/iishowto.xml,v retrieving revision 1.2 retrieving revision 1.3 diff -u -r1.2 -r1.3 --- iishowto.xml 9 Sep 2002 09:57:10 - 1.2 +++ iishowto.xml 10 Sep 2002 08:02:49 - 1.3 @@ -13,7 +13,7 @@ p Normally IIS can not execute Servlets and Java Server Pages (JSPs), -configuring IIS to use the mod_jk redirector plugin will let IIS send servlet and +configuring IIS to use the JK ISAPI redirector plugin will let IIS send servlet and JSP requests to Tomcat (and this way, serve them to clients). /p 1.5 +4 -4 jakarta-tomcat-connectors/jk/xdocs/jk/aphowto.xml Index: aphowto.xml
DO NOT REPLY [Bug 12472] New: - Trying to display the admin application results in JVM crash
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=12472. 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=12472 Trying to display the admin application results in JVM crash Summary: Trying to display the admin application results in JVM crash Product: Tomcat 4 Version: 4.1.10 Platform: Macintosh URL: http://localhost:8080/admin OS/Version: MacOS X Status: NEW Severity: Blocker Priority: Other Component: Webapps:Administration AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] After having logged in as an administrator, the application can't show up and I get a JVM crash warning. Here's the crash log output: ** Date/Time: 2002-09-10 09:46:06 +0200 OS Version: 10.2 (Build 6C115) Host: pudong Command:java PID:618 Exception: EXC_BAD_ACCESS (0x0001) Codes: KERN_PROTECTION_FAILURE (0x0002) at 0x0090 Thread 0: #0 0x90031b0c in accept #1 0x93db1a8c in Java_java_net_PlainSocketImpl_socketAccept #2 0x02102668 in 0x2102668 #3 0x0210068c in 0x210068c #4 0x0210068c in 0x210068c #5 0x0210068c in 0x210068c #6 0x021005cc in 0x21005cc #7 0x0210086c in 0x210086c #8 0x0210068c in 0x210068c #9 0x0210068c in 0x210068c #10 0xa2843c38 in typeinfo name for std::bad_exception #11 0x92838bdc in JVM_CurrentTimeMillis #12 0x92872ed4 in JVM_GetCPClassNameUTF #13 0x92907430 in JVM_InvokeMethod #14 0x92906a90 in JVM_InvokeMethod #15 0x92906738 in JVM_InvokeMethod #16 0x02102668 in 0x2102668 #17 0x021005cc in 0x21005cc #18 0xa2843c38 in typeinfo name for std::bad_exception #19 0x92838bdc in JVM_CurrentTimeMillis #20 0x92872ed4 in JVM_GetCPClassNameUTF #21 0x9287a3b8 in JVM_GetCPMethodModifiers #22 0x928d66c4 in JVM_RawMonitorCreate #23 0x2aa4 in 0x2aa4 #24 0x21ac in 0x21ac #25 0x202c in 0x202c Thread 1: #0 0x90074328 in mach_msg_trap #1 0x90006670 in mach_msg #2 0x928ec28c in JNI_CreateJavaVM_Impl #3 0x928ec224 in JNI_CreateJavaVM_Impl #4 0x928a51fc in JVM_GetClassMethodsCount #5 0x90021428 in _pthread_body Thread 2: #0 0x90074328 in mach_msg_trap #1 0x90006670 in mach_msg #2 0x9283ddf4 in JVM_NewInstance #3 0x9285eae4 in JVM_FillInStackTrace #4 0x9285a430 in JVM_GetCPMethodNameUTF #5 0x92864948 in JVM_Send #6 0x9290114c in JNI_CreateJavaVM_Impl #7 0x928a51fc in JVM_GetClassMethodsCount #8 0x90021428 in _pthread_body Thread 3: #0 0x90074328 in mach_msg_trap #1 0x90006670 in mach_msg #2 0x9283ddf4 in JVM_NewInstance #3 0x92845d80 in JVM_ArrayCopy #4 0x9285d620 in JVM_MonitorNotify #5 0x9285e2f8 in JVM_MonitorWait #6 0x02102668 in 0x2102668 #7 0x0210068c in 0x210068c #8 0x0210068c in 0x210068c #9 0xa2843c38 in typeinfo name for std::bad_exception #10 0x92838bdc in JVM_CurrentTimeMillis #11 0x92878c28 in JVM_FindClassFromClass #12 0x92892c90 in JVM_IsSameClassPackage #13 0x9288cf70 in JVM_GetMethodIxExceptionTableEntry #14 0x928787a0 in JVM_FindClassFromClass #15 0x928a51fc in JVM_GetClassMethodsCount #16 0x90021428 in _pthread_body Thread 4: #0 0x90074328 in mach_msg_trap #1 0x90006670 in mach_msg #2 0x9283ddf4 in JVM_NewInstance #3 0x92845d80 in JVM_ArrayCopy #4 0x9285d620 in JVM_MonitorNotify #5 0x9285e2f8 in JVM_MonitorWait #6 0x02102668 in 0x2102668 #7 0x0210068c in 0x210068c #8 0x021005cc in 0x21005cc #9 0x021005cc in 0x21005cc #10 0xa2843c38 in typeinfo name for std::bad_exception #11 0x92838bdc in JVM_CurrentTimeMillis #12 0x92878c28 in JVM_FindClassFromClass #13 0x92892c90 in JVM_IsSameClassPackage #14 0x9288cf70 in JVM_GetMethodIxExceptionTableEntry #15 0x928787a0 in JVM_FindClassFromClass #16 0x928a51fc in JVM_GetClassMethodsCount #17 0x90021428 in _pthread_body Thread 5: #0 0x90074328 in mach_msg_trap #1 0x90006670 in mach_msg #2 0x9283de9c in JVM_NewInstance #3 0x92844e18 in JVM_GetClassLoader #4 0x92844ba4 in JVM_GetClassLoader #5 0x928a51fc in JVM_GetClassMethodsCount #6 0x90021428 in _pthread_body Thread 6: #0 0x90074328 in mach_msg_trap #1 0x90006670 in mach_msg #2 0x9283ddf4 in JVM_NewInstance #3 0x9285eb40 in JVM_FillInStackTrace #4 0x92903300 in JVM_InitProperties #5 0x92903138 in JVM_InitProperties #6 0x928787a0 in JVM_FindClassFromClass #7 0x928a51fc in JVM_GetClassMethodsCount #8 0x90021428 in _pthread_body Thread 7: #0 0x90074328 in mach_msg_trap #1 0x90006670 in mach_msg #2 0x9283ddf4 in JVM_NewInstance #3 0x9285eb40 in JVM_FillInStackTrace #4 0x9288890c in JVM_StartThread #5 0x92876c10 in JVM_FindLoadedClass #6 0x928787a0 in
DO NOT REPLY [Bug 12472] - Trying to display the admin application results in JVM crash
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=12472. 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=12472 Trying to display the admin application results in JVM crash --- Additional Comments From [EMAIL PROTECTED] 2002-09-10 08:15 --- Created an attachment (id=2987) crash log output after trying to display administrator page on Mac OS X -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 12472] - Trying to display the admin application results in JVM crash
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=12472. 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=12472 Trying to display the admin application results in JVM crash [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||INVALID --- Additional Comments From [EMAIL PROTECTED] 2002-09-10 08:21 --- JVM crashes are JVM bugs. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
cvs commit: jakarta-tomcat-connectors/jk/xdocs/jk workershowto.xml
hgomez 2002/09/10 01:36:30 Modified:jk/xdocs/jk workershowto.xml Log: Added the documentation on advanced lb ie, local_worker and local_worker_only Revision ChangesPath 1.4 +81 -0 jakarta-tomcat-connectors/jk/xdocs/jk/workershowto.xml Index: workershowto.xml === RCS file: /home/cvs/jakarta-tomcat-connectors/jk/xdocs/jk/workershowto.xml,v retrieving revision 1.3 retrieving revision 1.4 diff -u -r1.3 -r1.4 --- workershowto.xml 10 Sep 2002 08:02:49 - 1.3 +++ workershowto.xml 10 Sep 2002 08:36:30 - 1.4 @@ -313,6 +313,87 @@ /subsection +subsection name=Advanced lb Worker properties +p +With JK 1.2.x, new load-balancing and fault-tolerant support has been added via +2 new properties, blocal_worker_only/b and blocal_worker/b. +/p + +p +Let's take an example environment: +/p + +p +A cluster with two nodes (worker1+worker2), running a webserver + tomcat tandem on each node and +a loadbalancer in front of the nodes. +/p + +screen +noteThe advanced router LB worker/note +readworker.list=router/read +note# Define a 'local_worker' worker using ajp13/note +readworker.worker1.port=8009/read +readworker.worker1.host=node1.domain.org/read +readworker.worker1.type=ajp13/read +readworker.worker1.lbfactor=1/read +readworker.worker1.local_worker=1/read +note# Define another 'local_worker' worker using ajp13/note +readworker.worker2.port=8009/read +readworker.worker2.host=node2.domain.org/read +readworker.worker2.type=ajp13/read +readworker.worker2.lbfactor=1/read +readworker.worker2.local_worker=0/read +note# Define the LB worker/note +readworker.router.type=lb/read +readworker.router.balanced_workers=worker1,worker2/read +readworker.router.local_worker_only=1/read +/screen + +p +The blocal_worker/b flag on worker1 and worker2 tells the blb_worker/b which connections are going +to the local worker. +/p + +p +If local_worker is an int and is not 0 it is set to JK_TRUE and marked as local worker, JK_FALSE otherwise. +If in minimum one worker is marked as local worker, lb_worker is in local worker mode. +All local workers are moved to the beginning of the internal worker list in lb_worker during validation. +/p + +p +This means that if a request with a session id comes in it would be routed to the appropriate worker. +If this worker is down it will be send to the first local worker which is not in error state. +/p + +p +If a request without a session comes in, it would be routed to the first local worker. +If all local worker are in error state, then the 'local_worker_only' flag is important. +If it was set to an int and this wasn't 0 it is set to JK_TRUE, JK_FALSE otherwise. With set to JK_TRUE, this request gets an error response. If set to JK_FALSE lb_worker tries to route the request to another balanced worker. +/p + +p +If one of the worker was in error state and has recovered nothing changes. +The local worker will be check for requests without a session id (and with a session on himself) and +the other worker will only be checked if a request with a session id of this worker comes in. +/p + +p +Why do we need souch a complex behavior ? +/p + +p +We need a graceful shut down of a node for maintenance. The balancer in front asks a special port on each +node periodically. If we want to remove a node from the cluster, we switch off this port. +The loadbalancer can't connect to it and marks the node as down. +But we don't move the sessions to another node. In this environment it is an error if the balancer sends a request without a session to an apache+mod_jk+tomcat which port is switched off. And if the load balancer determines that a node is down no other node is allowed to send a request without a session to it. Only requests with old sessions on the switched off node would be routed to this node. After some time nobody uses the old sessions and the sessions will time out. Then nobody uses this node, because all session are gone and the node is unreachable without a session-id in the request. If someone uses a session which timed out, our servlet system sends a redirect response without a session id to the browser. This is necessary for me, because on a switched off node apache and tomcat can still be up and running, but they are in an old state and should only be asked for valid old sessions. After the last session timed out, I could update the node etc. without killing sessions or moving them to another node. Sometimes we have a lot of big objects in our sessions, so it would be really time consuming to move them. +/p + +p +The defaults are still local_worker: 0 and local_worker_only:0 +/p + +/subsection + subsection name=jni Worker properties p The jni
cvs commit: jakarta-tomcat-connectors/jk/xdocs/jk aphowto.xml
hgomez 2002/09/10 01:38:27 Modified:jk/xdocs/jk aphowto.xml Log: Changed the name of iSeries SRVPGM (shared lib) from QCZTC to MODJK to avoid clash with original SRVPGM Revision ChangesPath 1.6 +1 -1 jakarta-tomcat-connectors/jk/xdocs/jk/aphowto.xml Index: aphowto.xml === RCS file: /home/cvs/jakarta-tomcat-connectors/jk/xdocs/jk/aphowto.xml,v retrieving revision 1.5 retrieving revision 1.6 diff -u -r1.5 -r1.6 --- aphowto.xml 10 Sep 2002 08:02:49 - 1.5 +++ aphowto.xml 10 Sep 2002 08:38:27 - 1.6 @@ -850,7 +850,7 @@ note5250Launch the build/note5250 type5250CALL MOD_JK/BLDJK/type5250br/ note5250If the build if successfull, copy the new mod_jk module/note5250 -type5250CRTDUPOBJ OBJ(MOD_JK) FROMLIB(MOD_JK) OBJTYPE(*SRVPGM) TOLIB(QHTTPSVR) NEWOBJ(QZTCJK)/type5250 +type5250CRTDUPOBJ OBJ(MOD_JK) FROMLIB(MOD_JK) OBJTYPE(*SRVPGM) TOLIB(QHTTPSVR) NEWOBJ(MODJK)/type5250 /screen5250 p Next, you should restart your Apache 2.0 server and enjoy this piece of OpenSource on iSeries. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: cvs commit: jakarta-tomcat-connectors/jk/xdocs menu.idx style.xsl.in
Excellent, we just need now to pass the subpart name and will be ready ;) Fixed with latest menu.idx and style.xsl.in I'm still waiting comments on jk load-balancing settings after the commited lb patches from May 2002 (Costin, Bern, Matthias) I got your mail and sent it to you directly. Should I send it to the list too? Not needed since it's allready commited ;) -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
cvs commit: jakarta-tomcat-4.0/webapps/tomcat-docs/config jk2.xml
remm2002/09/10 01:49:05
Modified:webapps/tomcat-docs build.xml project.xml
webapps/tomcat-docs/config jk2.xml
Log:
- Integrate JK2 docs.
- Cleanups.
Revision ChangesPath
1.12 +10 -0 jakarta-tomcat-4.0/webapps/tomcat-docs/build.xml
Index: build.xml
===
RCS file: /home/cvs/jakarta-tomcat-4.0/webapps/tomcat-docs/build.xml,v
retrieving revision 1.11
retrieving revision 1.12
diff -u -r1.11 -r1.12
--- build.xml 16 Sep 2001 04:58:28 - 1.11
+++ build.xml 10 Sep 2002 08:49:05 - 1.12
@@ -10,6 +10,8 @@
property file=../../build.properties/
property file=${user.home}/build.properties/
+ property name=tomcat-jk.home value=${jtc.home}/jk/
+
property name=build.compiler value=classic/
property name=webapps.build value=../build/
property name=webapps.distvalue=../dist/
@@ -112,6 +114,14 @@
includes=*.xml
param name=relative-path expression=../
/style
+
+!-- Build Coyote JK2 documentation --
+mkdir dir=${webapps.build}/${webapp.name}/jk2/
+ant dir=${tomcat-jk.home} target=docs/
+
+copy todir=${webapps.build}/${webapp.name}/jk2
+ fileset dir=${tomcat-jk.home}/build/docs/
+/copy
/target
1.17 +5 -1 jakarta-tomcat-4.0/webapps/tomcat-docs/project.xml
Index: project.xml
===
RCS file: /home/cvs/jakarta-tomcat-4.0/webapps/tomcat-docs/project.xml,v
retrieving revision 1.16
retrieving revision 1.17
diff -u -r1.16 -r1.17
--- project.xml 8 Sep 2002 17:56:04 - 1.16
+++ project.xml 10 Sep 2002 08:49:05 - 1.17
@@ -22,10 +22,14 @@
item name=Building from Source href=BUILDING.txt/
/menu
+menu name=Configuration
+item name=Reference href=config/index.html/
+/menu
+
menu name=Administrators
item name=CGI HOW-TOhref=cgi-howto.html/
-item name=Config. Reference href=config/index.html/
item name=Class Loader HOW-TO href=class-loader-howto.html/
+item name=Connectors List href=config/connectors.html/
item name=JNDI DataSource HOW-TO
href=jndi-datasource-examples-howto.html/
item name=JNDI Resources HOW-TO href=jndi-resources-howto.html/
1.3 +2 -442jakarta-tomcat-4.0/webapps/tomcat-docs/config/jk2.xml
Index: jk2.xml
===
RCS file: /home/cvs/jakarta-tomcat-4.0/webapps/tomcat-docs/config/jk2.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- jk2.xml 16 Apr 2002 17:48:56 - 1.2
+++ jk2.xml 10 Sep 2002 08:49:05 - 1.3
@@ -157,448 +157,8 @@
section name=Configuration HOWTOs
- subsection name=Apache
-
- subsection name=Introduction
-
-pThis section explains how to connect Tomcat 4 to the popular
-open source web server, Apache. It was originally part of
-iTomcat: A Minimalistic User's Guide/i by Gal Shachor, but
-has been split off for organizational reasons. It should be
-considered a bwork in progress/b. Since the Tomcat source
-tree is constantly changing, the information herein may be out
-of date. The only definitive reference at this point is the a
-href=http://jakarta.apache.org/site/sourceindex.html;source
-code/a./p
-
- /subsection
-
- subsection name=Installation
-
-subsection name=Needed Components
-
- pIn a nutshell a web server is waiting for client HTTP requests.
- When these requests arrive the server does whatever is needed to
- serve the requests by providing the necessary content. Adding a
- servlet container may somewhat change this behavior. Now the web
- server needs also to perform the following:/p
-
- ul
-liLoad the servlet container adapter library
-and initialize it (prior to serving requests). /li
-liWhen a request arrives, it needs to check and see if a certain
-request belongs to a servlet, if so it needs to let the adapter
-take the request and handle it./li
- /ul
-
- pThe adapter on the other hand needs to know what requests it is
- going to serve, usually based on some pattern in the request URL,
- and to where to direct these requests./p
-
- pThings are even more complex when the user wants to set
- a configuration that uses virtual hosts, or when they want multiple
- developers to work on the same web
Re: mod_jk 1.2.0 doc need review before release
Then I will arrange 1. And document 2 and 3 ;-) The doc has been updated : http://jakarta.apache.org/~hgomez/jk_docs/jk/ PS: Will you document 2 and 3 in aphowto.xml ? -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
[4.1] JK 2 docs
I've integrated the JK 2 docs bundle in the TC 4.1.11 docs package (except the javadocs, which I'll do later today). I also plan to update the online docs bundle with the latest snapshot later today. Remy -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
cvs commit: jakarta-tomcat-site/xdocs index.xml
remm2002/09/10 01:54:14 Modified:docs index.html xdocsindex.xml Log: - Version number update. Revision ChangesPath 1.27 +3 -3 jakarta-tomcat-site/docs/index.html Index: index.html === RCS file: /home/cvs/jakarta-tomcat-site/docs/index.html,v retrieving revision 1.26 retrieving revision 1.27 diff -u -r1.26 -r1.27 --- index.html11 Aug 2002 15:35:27 - 1.26 +++ index.html10 Sep 2002 08:54:14 - 1.27 @@ -175,7 +175,7 @@ /td td bgcolor=#a0ddf0 colspan= rowspan= valign=top align=left font color=#00 size=-1 face=arial,helvetica,sanserif -4.0.4 +4.1.10 /font /td /tr @@ -223,7 +223,7 @@ Catalina) that is based on completely new architecture. The 4.x releases implement the strongServlet 2.3/strong and strongJSP 1.2/strong specifications./p -pstrongTomcat 4.1.x/strong. Tomcat 4.1.8 Beta is the latest release. +pstrongTomcat 4.1.x/strong. Tomcat 4.1.10 Stable is the latest release. Tomcat 4.1 is a refactoring of Tomcat 4.0.x, and contains significant enhancements, including: ul @@ -238,7 +238,7 @@ from build.xml scripts/li /ul /p -pstrongTomcat 4.0.x/strong. Tomcat 4.0.4 is the current production +pstrongTomcat 4.0.x/strong. Tomcat 4.0.4 is the old production quality release. Tomcat 4.0 is the next generation of Tomcat. The 4.0 servlet container (Catalina) has been developed from the ground up for flexibility and performance. Version 4.0 implements the final released versions of the Servlet 1.23 +3 -3 jakarta-tomcat-site/xdocs/index.xml Index: index.xml === RCS file: /home/cvs/jakarta-tomcat-site/xdocs/index.xml,v retrieving revision 1.22 retrieving revision 1.23 diff -u -r1.22 -r1.23 --- index.xml 11 Aug 2002 15:35:27 - 1.22 +++ index.xml 10 Sep 2002 08:54:14 - 1.23 @@ -45,7 +45,7 @@ tr td2.3/1.2/td - td4.0.4/td + td4.1.10/td /tr tr @@ -75,7 +75,7 @@ implement the strongServlet 2.3/strong and strongJSP 1.2/strong specifications./p -pstrongTomcat 4.1.x/strong. Tomcat 4.1.8 Beta is the latest release. +pstrongTomcat 4.1.x/strong. Tomcat 4.1.10 Stable is the latest release. Tomcat 4.1 is a refactoring of Tomcat 4.0.x, and contains significant enhancements, including: ul @@ -91,7 +91,7 @@ /ul /p -pstrongTomcat 4.0.x/strong. Tomcat 4.0.4 is the current production +pstrongTomcat 4.0.x/strong. Tomcat 4.0.4 is the old production quality release. Tomcat 4.0 is the next generation of Tomcat. The 4.0 servlet container (Catalina) has been developed from the ground up for flexibility and performance. Version 4.0 implements the final released versions of the Servlet -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
cvs commit: jakarta-tomcat-4.0/webapps/tomcat-docs index.xml project.xml
remm2002/09/10 02:06:55 Modified:webapps/tomcat-docs index.xml project.xml Log: - Add visible links to the JK documentation. Revision ChangesPath 1.16 +11 -4 jakarta-tomcat-4.0/webapps/tomcat-docs/index.xml Index: index.xml === RCS file: /home/cvs/jakarta-tomcat-4.0/webapps/tomcat-docs/index.xml,v retrieving revision 1.15 retrieving revision 1.16 diff -u -r1.15 -r1.16 --- index.xml 8 Sep 2002 17:56:04 - 1.15 +++ index.xml 10 Sep 2002 09:06:55 - 1.16 @@ -47,6 +47,10 @@ steps necessary to download Tomcat 4 source code (and the other packages that it depends on), and build a binary distribution from those sources. /li +lia href=config/index.htmlstrongServer Configuration Reference/strong/a +- Reference manual that documents all available elements and attributes + that may be placed into a Tomcat 4 codeconf/server.xml/code file. +/li /ul /section @@ -60,10 +64,9 @@ ul lia href=cgi-howto.htmlstrongCGI HOW-TO/strong/a - Configuring Tomcat to use CGI (Common Gateway Interface)./li -lia href=config/index.htmlstrongServer Configuration Reference/strong/a -- Reference manual that documents all available elements and attributes - that may be placed into a Tomcat 4 codeconf/server.xml/code file. -/li +lia href=config/connectors.htmlstrongConnectors List/strong/a +- List of the connectors (both HTTP and native webservers) available for + use with Tomcat./li lia href=class-loader-howto.htmlstrongClass Loader HOW-TO/strong/a - Information about class loading in Tomcat 4, including where to place your application classes so that they are visible./li @@ -71,6 +74,10 @@ strongJNDI DataSource HOW-TO/strong/a - Configuring a JNDI DataSoure with a dB connection pool. Examples for many popular databases./li +lia href=jk2/index.htmlstrongJK Documenation/strong/a +- Complete documentation and HOWTOs on the JK native webserver connector, + used to interface Tomcat with servers like Apache HTTPd, IIS + and others./li lia href=jndi-resources-howto.htmlstrongJNDI Resources HOW-TO/strong/a - Configuring standard and custom resources in the JNDI naming context that is provided to each web application./li 1.18 +1 -0 jakarta-tomcat-4.0/webapps/tomcat-docs/project.xml Index: project.xml === RCS file: /home/cvs/jakarta-tomcat-4.0/webapps/tomcat-docs/project.xml,v retrieving revision 1.17 retrieving revision 1.18 diff -u -r1.17 -r1.18 --- project.xml 10 Sep 2002 08:49:05 - 1.17 +++ project.xml 10 Sep 2002 09:06:55 - 1.18 @@ -30,6 +30,7 @@ item name=CGI HOW-TOhref=cgi-howto.html/ item name=Class Loader HOW-TO href=class-loader-howto.html/ item name=Connectors List href=config/connectors.html/ +item name=JK Documentation href=jk2/index.html/ item name=JNDI DataSource HOW-TO href=jndi-datasource-examples-howto.html/ item name=JNDI Resources HOW-TO href=jndi-resources-howto.html/ -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
cvs commit: jakarta-tomcat-connectors/jk/xdocs style.xsl.in
hgomez 2002/09/10 02:08:18
Modified:jk/xdocs style.xsl.in
Log:
Change color for section
Revision ChangesPath
1.11 +2 -2 jakarta-tomcat-connectors/jk/xdocs/style.xsl.in
Index: style.xsl.in
===
RCS file: /home/cvs/jakarta-tomcat-connectors/jk/xdocs/style.xsl.in,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -r1.10 -r1.11
--- style.xsl.in 10 Sep 2002 08:02:13 - 1.10
+++ style.xsl.in 10 Sep 2002 09:08:18 - 1.11
@@ -152,7 +152,7 @@
xsl:variable name=root select=//
xsl:for-each select=document('menu.idx')/index/section
tr height=6
- td bgcolor=#cc width=150 colspan=2
+ td bgcolor=#d0d0d0 width=150 colspan=2
xsl:value-of select=@name/
/td
/tr
@@ -200,7 +200,7 @@
both for C and for Java
--
tr height=6
-td bgcolor=#cc width=150 colspan=2
+td bgcolor=#d0d0d0 width=150 colspan=2
Developpers
/td
/tr
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 12474] New: - Exception processing jar in Struts war
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=12474. 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=12474 Exception processing jar in Struts war Summary: Exception processing jar in Struts war Product: Tomcat 4 Version: 4.1.9 Platform: PC OS/Version: Windows NT/2K Status: NEW Severity: Normal Priority: Other Component: Catalina AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] Both Tomcat 4.1.9 and 4.1.10 had an exception (shown below) processing the struts WARs (1.0.2 and 1.1-b2) while Tomcat 4.0.4 was OK. I used the LE version with JDK 1.4.1-rc-b19 and Windows 2002 with SP3. The problem did not occur on another PC running JDK 1.4.0-b92 and Windows 2000 without any SPs 2002-09-10 09:28:41 WebappLoader[/struts-documentation]: Deploy JAR /WEB- INF/lib/struts.jar to C:\java\jakarta-tomcat-4.1.9-LE-jdk14 \bin\..\webapps\struts-documentation\WEB-INF\lib\struts.jar 2002-09-10 09:28:41 ContextConfig[/struts-documentation] Exception processing JAR at resource path /WEB-INF/lib/struts.jar javax.servlet.ServletException: Exception processing JAR at resource path /WEB- INF/lib/struts.jar at org.apache.catalina.startup.ContextConfig.tldScanJar (ContextConfig.java:930) at org.apache.catalina.startup.ContextConfig.tldScan (ContextConfig.java:868) at org.apache.catalina.startup.ContextConfig.start (ContextConfig.java:647) at org.apache.catalina.startup.ContextConfig.lifecycleEvent (ContextConfig.java:243) at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent (LifecycleSupport.java:166) at org.apache.catalina.core.StandardContext.start (StandardContext.java:3445) at org.apache.catalina.core.ContainerBase.addChildInternal (ContainerBase.java:821) at org.apache.catalina.core.ContainerBase.addChild (ContainerBase.java:807) at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:579) at org.apache.catalina.core.StandardHostDeployer.install (StandardHostDeployer.java:257) at org.apache.catalina.core.StandardHost.install(StandardHost.java:772) at org.apache.catalina.startup.HostConfig.deployWARs (HostConfig.java:502) at org.apache.catalina.startup.HostConfig.deployApps (HostConfig.java:410) at org.apache.catalina.startup.HostConfig.start(HostConfig.java:879) at org.apache.catalina.startup.HostConfig.lifecycleEvent (HostConfig.java:368) at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent (LifecycleSupport.java:166) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1196) at org.apache.catalina.core.StandardHost.start(StandardHost.java:738) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1188) at org.apache.catalina.core.StandardEngine.start (StandardEngine.java:347) at org.apache.catalina.core.StandardService.start (StandardService.java:497) at org.apache.catalina.core.StandardServer.start (StandardServer.java:2188) at org.apache.catalina.startup.Catalina.start(Catalina.java:510) at org.apache.catalina.startup.Catalina.execute(Catalina.java:400) at org.apache.catalina.startup.Catalina.process(Catalina.java:180) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:203) - Root Cause - java.io.IOException: The system cannot find the path specified at java.io.WinNTFileSystem.createFileExclusively(Native Method) at java.io.File.checkAndCreate(File.java:1313) at java.io.File.createTempFile(File.java:1401) at java.io.File.createTempFile(File.java:1438) at sun.net.www.protocol.jar.URLJarFile$1.run(URLJarFile.java:169) at java.security.AccessController.doPrivileged(Native Method) at sun.net.www.protocol.jar.URLJarFile.retrieve(URLJarFile.java:164) at sun.net.www.protocol.jar.URLJarFile.getJarFile(URLJarFile.java:42) at sun.net.www.protocol.jar.JarFileFactory.get(JarFileFactory.java:78) at sun.net.www.protocol.jar.JarURLConnection.connect (JarURLConnection.java:85) at sun.net.www.protocol.jar.JarURLConnection.getJarFile (JarURLConnection.java:69) at org.apache.catalina.startup.ContextConfig.tldScanJar (ContextConfig.java:906) at org.apache.catalina.startup.ContextConfig.tldScan (ContextConfig.java:868)
DO NOT REPLY [Bug 12474] - Exception processing jar in Struts war
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=12474. 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=12474 Exception processing jar in Struts war [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||DUPLICATE --- Additional Comments From [EMAIL PROTECTED] 2002-09-10 09:51 --- *** This bug has been marked as a duplicate of 11489 *** -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 11489] - Scanning JAR files in WEB-INF/lib without temp directory
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=11489. 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=11489 Scanning JAR files in WEB-INF/lib without temp directory [EMAIL PROTECTED] changed: What|Removed |Added CC||[EMAIL PROTECTED] --- Additional Comments From [EMAIL PROTECTED] 2002-09-10 09:51 --- *** Bug 12474 has been marked as a duplicate of this bug. *** -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: mod_jk 1.2.0 doc need review before release
Henri Gomez wrote: Then I will arrange 1. And document 2 and 3 ;-) The doc has been updated : http://jakarta.apache.org/~hgomez/jk_docs/jk/ PS: Will you document 2 and 3 in aphowto.xml ? -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] End of the document. I go for it ;-) -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 12475] New: - CPU Usage is 0%, Tomcat doesn't response
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=12475. 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=12475 CPU Usage is 0%, Tomcat doesn't response Summary: CPU Usage is 0%, Tomcat doesn't response Product: Tomcat 3 Version: Unknown Platform: Other OS/Version: All Status: NEW Severity: Normal Priority: Other Component: Connectors AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] Hi! We use tomcat 3.2.x and 3.3.x on Windows 2k and Linux. Sometimes (one time in one/two day(s) ) tomcat hangs up. Stack traces show that there is no our code in them, only tomcat's. Today I debugged hanged tomcat with the help of remote debug. I find out that there is no thread, which listen HTTP port (port from HttpConnectionHandler). There were two threads with the following on top: java.net.PlainSocketImpl.socketAccept(java.net.SocketImpl). But these threads listern ports from Ajp12ConnectionHandler and Ajp13ConnectionHandler. Besides two threads above and systems threads such as AWT-Threads, Finalizer and etc., there were many waiting threads with following stack: java.lang.Object.wait(long) line: not available [native method] org.apache.tomcat.util.threads.ThreadPool$ControlRunnable (java.lang.Object).wait() line: 420 org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run() line: 495 java.lang.Thread.run() line: 484 Do you have an idea what's wrong with tomcat ? Why is it hanging up ? -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: [4.1] JK 2 docs
Remy Maucherat wrote: I've integrated the JK 2 docs bundle in the TC 4.1.11 docs package (except the javadocs, which I'll do later today). I also plan to update the online docs bundle with the latest snapshot later today. Remy -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] Why did you include JK2 docs into Tomcat 4.1.11 ? I think it's better to have them on jakarta site (will have to create a jakarta-tomcat-connector/jk and jk2 from main pages). I agree you should include the java side of JK2 but not the native one. Don't forget that many users will use jk instead of jk2 since it's their current setup and may be desoriented by seing ref to jk2 in TC4... -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: What is the difference between mod_jk and mod_jk2 modules?
Dev Zero G Ltd wrote: Hello. Can anybody suggest what is the difference (benefits/shortages) beetween mod_jk and mod_jk2 connectors from the user point of view? Thanks for help! Dev Zero G Ltd team. http://devzerog.com -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] Just take a look at the doc in progress : http://jakarta.apache.org/~hgomez/jk_docs/ -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
cvs commit: jakarta-tomcat-connectors/jk/xdocs/jk aphowto.xml
jfclere 2002/09/10 04:15:15 Modified:jk/xdocs/jk aphowto.xml Log: Add a session and 2 examples for the static linking of mod_jk. Revision ChangesPath 1.7 +63 -0 jakarta-tomcat-connectors/jk/xdocs/jk/aphowto.xml Index: aphowto.xml === RCS file: /home/cvs/jakarta-tomcat-connectors/jk/xdocs/jk/aphowto.xml,v retrieving revision 1.6 retrieving revision 1.7 diff -u -r1.6 -r1.7 --- aphowto.xml 10 Sep 2002 08:38:27 - 1.6 +++ aphowto.xml 10 Sep 2002 11:15:15 - 1.7 @@ -857,4 +857,67 @@ /p /section +section name=Getting mod_jk linked staticly with Apache +p +mod_jk allows to install mod_jk in the Apache source tree to get a staticly +linked mod_jk. Having mod_jk in the httpd executable brings some performance +improvements. The configure option --with-apache prepare mod_jk to install it +in the Apache source tree. +The option --with-apache works both for Apache-1.3 and Apache-2.0. +The examples below show how to get mod_jk in the httpd process. +/p + +subsection name=Installation in Apache-2.0 +screen +note /home/apache20/httpd-2.0.40 is the directory where the httpd-2.0 sources +are located. /note +type./configure --with-apache=/home/apache20/httpd-2.0.40/typebr/ +typemake/typebr/ +noteInstall the mod_jk library and other files in +/home/apache20/httpd-2.0.40/modules: /note +typemake install/typebr/ +note It is not possible to configure Apache directly because the config.m4 of mod_jk must +be added to the configure of httpd-2.0. /note +typecd /home/apache20/httpd-2.0.40/type +typesh buildconf/type +typeconfigure ... --with-mod_jk/type +typemake/type +typemake install/typebr/ +/screen +p +The enable-jk=share and enable-jk=static are not supported. --with-mod_jk only +allow static linking of mod_jk. +/p +/subsection + +subsection name=Installation in Apache-1.3 +screen +note /home/apache/apache_1.3.26 is the directory where the apache-1.3 sources +are located. /note +type./configure --with-apache=/home/apache/apache_1.3.26/typebr/ +typemake/typebr/ +noteInstall the libjk library, mod_jk.c, includes and other files in +/home/apache/apache_1.3.26/src/modules/jk: /note +typemake install/typebr/ +note Configure in the Apache sources: /note +typecd /home/apache/apache_1.3.26/type +typeconfigure ... --enable-module=dir --disable-shared=dir \ /type +type --activate-module=src/modules/jk/libjk.a \ /type +type --disable-shared=jk/type +typemake/type +typemake install/typebr/ +/screen +p +The --enable-shared=jk is also working and builds a dso file. +/p +screen +note Just change the configure in the Apache sources: /note +typeconfigure ... --enable-module=dir --enable-shared=dir \ /type +type --activate-module=src/modules/jk/libjk.a \ /type +type --enable-shared=jk/type +/screen +/subsection + +/section + /document -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: [4.1] JK 2 docs
Henri Gomez wrote: Why did you include JK2 docs into Tomcat 4.1.11 ? Because people who download Tomcat usually want to configure JK also, without going online again after downloading the binaries. I think it's better to have them on jakarta site (will have to create a jakarta-tomcat-connector/jk and jk2 from main pages). No, it's a bad idea. Experience has shown that people see JK + Tomcat as being one product, although we may develop it separately. They also have no idea where to look for documentation, and I don't want to link back to the web. So I'd like to include the whole doc bundle with the Tomcat download (and have some connector binaries also). I agree you should include the java side of JK2 but not the native one. Don't forget that many users will use jk instead of jk2 since it's their current setup and may be desoriented by seing ref to jk2 in TC4... JK the Java code is dead (deprecated, and unsupported). JK 2 the Java code is the current code. mod_jk OTOH is the current code, and mod_jk2 is experimental. Remy -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
cvs commit: jakarta-tomcat-connectors/jk/xdocs/jk aphowto.xml
hgomez 2002/09/10 04:35:20 Modified:jk/xdocs/jk aphowto.xml Log: Fixes typos :) Revision ChangesPath 1.8 +2 -2 jakarta-tomcat-connectors/jk/xdocs/jk/aphowto.xml Index: aphowto.xml === RCS file: /home/cvs/jakarta-tomcat-connectors/jk/xdocs/jk/aphowto.xml,v retrieving revision 1.7 retrieving revision 1.8 diff -u -r1.7 -r1.8 --- aphowto.xml 10 Sep 2002 11:15:15 - 1.7 +++ aphowto.xml 10 Sep 2002 11:35:20 - 1.8 @@ -857,9 +857,9 @@ /p /section -section name=Getting mod_jk linked staticly with Apache +section name=Getting mod_jk linked statically with Apache p -mod_jk allows to install mod_jk in the Apache source tree to get a staticly +mod_jk allows to install mod_jk in the Apache source tree to get a statically linked mod_jk. Having mod_jk in the httpd executable brings some performance improvements. The configure option --with-apache prepare mod_jk to install it in the Apache source tree. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: [4.1] JK 2 docs
I have refreshed the online docs bundle (which was really stale) so that people can see the result. http://jakarta.apache.org/tomcat/tomcat-4.1-doc/index.html Other new additions include the much needed Jasper documentation by Glenn. Remy -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: [4.1] JK 2 docs
Henri Gomez wrote: Remy Maucherat wrote: Henri Gomez wrote: Why did you include JK2 docs into Tomcat 4.1.11 ? Because people who download Tomcat usually want to configure JK also, without going online again after downloading the binaries. I think it's better to have them on jakarta site (will have to create a jakarta-tomcat-connector/jk and jk2 from main pages). No, it's a bad idea. Experience has shown that people see JK + Tomcat as being one product, although we may develop it separately. They also have no idea where to look for documentation, and I don't want to link back to the web. So I'd like to include the whole doc bundle with the Tomcat download (and have some connector binaries also). I agree you should include the java side of JK2 but not the native one. Don't forget that many users will use jk instead of jk2 since it's their current setup and may be desoriented by seing ref to jk2 in TC4... JK the Java code is dead (deprecated, and unsupported). JK 2 the Java code is the current code. mod_jk OTOH is the current code, and mod_jk2 is experimental. When I said JK, I was thinking jk 1.2.0 (native). So what to do with jk 1.2.0 doc ? JF and I worked on it for at least 2 weeks, since doc allways was a leak in connector are. Do you plan to included also jk 1.2.0 doc or make reference to it ? I tried including everything. The idea would be to have users be able to download the bundle (eventually), put it on a CD, and don't have to browse the web for more info. Remy -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: [4.1] JK 2 docs
I tried it. I kinda like the result (but we can choose to link to the JK docs instead), except for the JK 1 / JK 2 confusion. may be better make link to jk instead of jk2. the doc split between commons, jk and jk2 specifics, and I think we'll focus next time of jk2 specific. I tried to avoid confusion between jk, jk2, mod_jk See you -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: [4.1] JK 2 docs
Mladen Turk wrote: Excelent! Finally the docs are where they should be. The only thing left IMO is to make the jk 2 docs style the same as in the Tomcat. Or vice versa. The JK docs look a bit like the Maven or Turbine style, so it may be the next-gen look for Jakarta. http://jakarta.apache.org/turbine/index.html What about building docs? We can have one release of TC that is not necessary to be in sync with the release of any jk, and the connector docs may change. How did you plan to deal with that. I don't know yet. Remy -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: [4.1] JK 2 docs
The JK docs look a bit like the Maven or Turbine style, so it may be the next-gen look for Jakarta http://jakarta.apache.org/turbine/index.html Largelly grabbed from Pier's mod_webapp documentation style. What about building docs? We can have one release of TC that is not necessary to be in sync with the release of any jk, and the connector docs may change. How did you plan to deal with that. I don't know yet. The jk/jk2 doc will make its own life on jtc cvs and I think we should make it also available online at jakarta at each jk/jk2 release ... What do you think ? -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: [4.1] JK 2 docs
Remy Maucherat wrote: I have refreshed the online docs bundle (which was really stale) so that people can see the result. http://jakarta.apache.org/tomcat/tomcat-4.1-doc/index.html Other new additions include the much needed Jasper documentation by Glenn. What about also having a link to mod_webapp? I have the pages at http://www.apache.org/~jfclere/webapp_docs/ there are build like the mod_jk ones. Remy -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 12145] - [PATCH] AccessLogValve - %{xxx}i implementation
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=12145.
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=12145
[PATCH] AccessLogValve - %{xxx}i implementation
--- Additional Comments From [EMAIL PROTECTED] 2002-09-10 12:16 ---
Created an attachment (id=2988)
used -u flag for cvs diff: [cvs diff -u AccessLogValve.java AccessLogValve.diff2]
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 12476] New: - Variables are not initialized with custom tag whichextends TagSupport
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=12476. 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=12476 Variables are not initialized with custom tag whichextends TagSupport Summary: Variables are not initialized with custom tag whichextends TagSupport Product: Tomcat 4 Version: 4.1.10 Platform: PC OS/Version: Linux Status: NEW Severity: Major Priority: Other Component: Jasper 2 AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] With a custom tag which extends TagSupport class and has variables defined in tag-extra-info as VariableInfo.NESTED, the variables are not initialized at a start tag. For example, the following JSP file is expected that it outputs a, but it outputs null: EXAMPLE JSP FILE START custom:test value=a %= value % /custom:test EXAMPLE JSP FILE END custom:test tag has variable named value as String in tag extra info class, and the tag sets a -- value of attribute 'value' -- to the value. So it is expected that %= value % is interpreted as a, but it is interpreted as null. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
cvs commit: jakarta-tomcat-connectors/jk/native2/common jk_logger_file.c
mturk 2002/09/10 06:40:08
Modified:jk/native2/common jk_logger_file.c
Log:
Fix the successful log initialization logging as INFO not as ERROR
Revision ChangesPath
1.32 +2 -2 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.31
retrieving revision 1.32
diff -u -r1.31 -r1.32
--- jk_logger_file.c 11 Jun 2002 02:51:18 - 1.31
+++ jk_logger_file.c 10 Sep 2002 13:40:08 - 1.32
@@ -168,7 +168,7 @@
}
_this-logger_private = f;
}
-_this-jkLog(env, _this,JK_LOG_ERROR,
+_this-jkLog(env, _this,JK_LOG_INFO,
Initializing log file %s\n, _this-name );
if( oldF!=NULL ) {
fclose( oldF );
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
[Jasper2] Test suite ?
As the 4.1.10 release revealed, despite our best efforts, some bugs slipped in the tag handling code, due to the complexity of the specification. Watchdog is unfortunately only testing very simple cases, and cannot be used to catch those problems (on the servlet side, OTOH, it seems to be willing to test some highly dubious assertions), so I think some kind of test suite is needed for Jasper. Unfortunately, I don't have time to contribute to it, but I hope to get the process started ... Remy -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 12476] - Variables are not initialized with custom tag whichextends TagSupport
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=12476. 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=12476 Variables are not initialized with custom tag whichextends TagSupport [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED --- Additional Comments From [EMAIL PROTECTED] 2002-09-10 14:41 --- This was already reported and fixed. The fix will be in 4.1.11. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
cvs commit: jakarta-tomcat-connectors/jk/native/apache-2.0 mod_jk.c
jfclere 2002/09/10 08:08:13
Modified:jk/native/apache-2.0 mod_jk.c
Log:
I prefer to get 500 when something goes wrong than getting not found.
Revision ChangesPath
1.56 +3 -2 jakarta-tomcat-connectors/jk/native/apache-2.0/mod_jk.c
Index: mod_jk.c
===
RCS file: /home/cvs/jakarta-tomcat-connectors/jk/native/apache-2.0/mod_jk.c,v
retrieving revision 1.55
retrieving revision 1.56
diff -u -r1.55 -r1.56
--- mod_jk.c 4 Sep 2002 11:31:32 - 1.55
+++ mod_jk.c 10 Sep 2002 15:08:13 - 1.56
@@ -1376,7 +1376,8 @@
if(rc) {
return OK;/* NOT r-status, even if it has changed. */
-}
+} else
+return HTTP_INTERNAL_SERVER_ERROR;
}
else
return HTTP_INTERNAL_SERVER_ERROR;
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
cvs commit: jakarta-tomcat-catalina build.xml gump.xml
bobh2002/09/10 08:50:49
Modified:.build.xml gump.xml
Log:
- Changes to get gump working. Namely build.xml, make catalina deploy
target configurable so that catalina builds without building coyote
(gump hates this.) Namely gump.xml, added values for otherwise
undefined properties (as build.xml was designed to be used when these
properties were set from another build.xml)
Revision ChangesPath
1.5 +4 -1 jakarta-tomcat-catalina/build.xml
Index: build.xml
===
RCS file: /home/cvs/jakarta-tomcat-catalina/build.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- build.xml 11 Aug 2002 11:54:48 - 1.4
+++ build.xml 10 Sep 2002 15:50:49 - 1.5
@@ -11,6 +11,9 @@
!-- Build Defaults --
!--property name=catalina.build value=${basedir}/catalina/build/--
+ !-- used by gump to keep from building more that just catalina --
+ property name=catalina.target value=deploy
+
!-- Source dependencies --
property name=api.home
value=${basedir}/../jakarta-servletapi-5/
@@ -42,7 +45,7 @@
target name=deploy depends=deploy-static
description=Build and deploy all components
echoTarget: Catalina - Deploy .../echo
-ant dir=${basedir}/catalina target=deploy/
+ant dir=${basedir}/catalina target=${catalina.target}/
echoTarget: Webapps - Deploy .../echo
ant dir=${basedir}/webapps target=deploy/
/target
1.6 +4 -0 jakarta-tomcat-catalina/gump.xml
Index: gump.xml
===
RCS file: /home/cvs/jakarta-tomcat-catalina/gump.xml,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- gump.xml 9 Sep 2002 04:16:16 - 1.5
+++ gump.xml 10 Sep 2002 15:50:49 - 1.6
@@ -11,6 +11,10 @@
packageorg.apache.catalina/package
ant target=deploy
+ property name=catalina.target value=deploy-catalina /
+ property name=jtc.home value=/home/bob/jk/jakarta-tomcat-connectors /
+ property name=catalina.home value=/home/bob/jk/jakarta-tomcat-catalina /
+ property name=tomcat.build path=build/
property name=ant.home reference=home project=jakarta-ant/
property name=jsse.home reference=home project=jsse/
property name=jmx.home reference=home project=jmx/
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
cvs commit: jakarta-tomcat-catalina build.xml
bobh2002/09/10 08:53:38
Modified:.build.xml
Log:
- Oops, forgot to close the property tag. (test then commit, not commit and test.)
Revision ChangesPath
1.6 +1 -1 jakarta-tomcat-catalina/build.xml
Index: build.xml
===
RCS file: /home/cvs/jakarta-tomcat-catalina/build.xml,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- build.xml 10 Sep 2002 15:50:49 - 1.5
+++ build.xml 10 Sep 2002 15:53:38 - 1.6
@@ -12,7 +12,7 @@
!--property name=catalina.build value=${basedir}/catalina/build/--
!-- used by gump to keep from building more that just catalina --
- property name=catalina.target value=deploy
+ property name=catalina.target value=deploy /
!-- Source dependencies --
property name=api.home
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: cvs commit: jakarta-tomcat-catalina build.xml gump.xml
On 10 Sep 2002, [EMAIL PROTECTED] wrote: + property name=jtc.home value=/home/bob/jk/jakarta-tomcat-connectors / I don't think this is going to work on my machine (no user bob here 8-). You probably want to do something like property name=jtc.home project=jakarta-tomcat-connectors reference=home/ Same for catalina-home. Stefan -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: cvs commit: jakarta-tomcat-catalina build.xml gump.xml
Picky picky. On Tue, 2002-09-10 at 12:07, Stefan Bodewig wrote: On 10 Sep 2002, [EMAIL PROTECTED] wrote: + property name=jtc.home value=/home/bob/jk/jakarta-tomcat-connectors / I don't think this is going to work on my machine (no user bob here 8-). You probably want to do something like property name=jtc.home project=jakarta-tomcat-connectors reference=home/ Same for catalina-home. Stefan -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- Cheers, -bob -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
cvs commit: jakarta-tomcat-catalina gump.xml
bobh2002/09/10 09:16:54 Modified:.gump.xml Log: - had absolute paths, not relative paths - my bad. Revision ChangesPath 1.7 +4 -2 jakarta-tomcat-catalina/gump.xml Index: gump.xml === RCS file: /home/cvs/jakarta-tomcat-catalina/gump.xml,v retrieving revision 1.6 retrieving revision 1.7 diff -u -r1.6 -r1.7 --- gump.xml 10 Sep 2002 15:50:49 - 1.6 +++ gump.xml 10 Sep 2002 16:16:54 - 1.7 @@ -12,8 +12,10 @@ ant target=deploy property name=catalina.target value=deploy-catalina / - property name=jtc.home value=/home/bob/jk/jakarta-tomcat-connectors / - property name=catalina.home value=/home/bob/jk/jakarta-tomcat-catalina / + property name=jtc.home project=jakarta-tomcat-connectors +reference=home/ + property name=catalina.home project=jakarta-tomcat-catalina +reference=home/ property name=tomcat.build path=build/ property name=ant.home reference=home project=jakarta-ant/ property name=jsse.home reference=home project=jsse/ -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
cvs commit: jakarta-tomcat-catalina build.xml gump.xml
bobh2002/09/10 10:26:17
Modified:.build.xml gump.xml
Log:
- Larry Isaacs suggests that using an additional target is more
typical way to handle this situation (different build paths for gump
vs other build.xml)
Revision ChangesPath
1.7 +10 -3 jakarta-tomcat-catalina/build.xml
Index: build.xml
===
RCS file: /home/cvs/jakarta-tomcat-catalina/build.xml,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- build.xml 10 Sep 2002 15:53:38 - 1.6
+++ build.xml 10 Sep 2002 17:26:17 - 1.7
@@ -11,9 +11,6 @@
!-- Build Defaults --
!--property name=catalina.build value=${basedir}/catalina/build/--
- !-- used by gump to keep from building more that just catalina --
- property name=catalina.target value=deploy /
-
!-- Source dependencies --
property name=api.home
value=${basedir}/../jakarta-servletapi-5/
@@ -46,6 +43,16 @@
description=Build and deploy all components
echoTarget: Catalina - Deploy .../echo
ant dir=${basedir}/catalina target=${catalina.target}/
+echoTarget: Webapps - Deploy .../echo
+ant dir=${basedir}/webapps target=deploy/
+ /target
+
+ !-- == DEPLOY: Deploy Core Components === --
+ !-- used by gump to build just catalina and not the j-t-connectors --
+ target name=deploy-catalina depends=deploy-static
+ description=Build and deploy all components
+echoTarget: Catalina - Deploy .../echo
+ant dir=${basedir}/catalina target=deploy-catalina/
echoTarget: Webapps - Deploy .../echo
ant dir=${basedir}/webapps target=deploy/
/target
1.8 +1 -2 jakarta-tomcat-catalina/gump.xml
Index: gump.xml
===
RCS file: /home/cvs/jakarta-tomcat-catalina/gump.xml,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- gump.xml 10 Sep 2002 16:16:54 - 1.7
+++ gump.xml 10 Sep 2002 17:26:17 - 1.8
@@ -10,8 +10,7 @@
project name=jakarta-tomcat-catalina
packageorg.apache.catalina/package
-ant target=deploy
- property name=catalina.target value=deploy-catalina /
+ant target=deploy-catalina
property name=jtc.home project=jakarta-tomcat-connectors
reference=home/
property name=catalina.home project=jakarta-tomcat-catalina
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 12280] - Bogus exception stack trace
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=12280. 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=12280 Bogus exception stack trace [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||WONTFIX --- Additional Comments From [EMAIL PROTECTED] 2002-09-10 17:27 --- Tomcat's WebAppLoader class expects the webapp's class loader to be a subclass of java.net.URLClassLoader. The URLClassLoader class has a getClasspath() method that is used to build a classpath string for the Jasper compiler. If the webapp's class loader is not a subclass of URLClassLoader, then Tomcat's WebAppLoader class will attempt to invoke the class loader's getClasspath() method via reflection. In your particular instance, you are using a custom class loader as the webapp's class loader. Since this custom class loader has no getClasspath() method nor does it subclass URLClassLoader, Tomcat generates the warning to warn that the classpath for the webapp's class loader (and its parent class loaders) will be missing from any Jasper compilations. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: cvs commit: jakarta-tomcat-catalina build.xml gump.xml
Perhaps you could also change
ant dir=${basedir}/catalina target=${catalina.target}/
back to target=deploy, since you deleted the catalina.target property?
On Tuesday 10 September 2002 01:26 pm, [EMAIL PROTECTED] wrote:
bobh2002/09/10 10:26:17
Modified:.build.xml gump.xml
Log:
- Larry Isaacs suggests that using an additional target is more
typical way to handle this situation (different build paths for gump
vs other build.xml)
Revision ChangesPath
1.7 +10 -3 jakarta-tomcat-catalina/build.xml
Index: build.xml
===
RCS file: /home/cvs/jakarta-tomcat-catalina/build.xml,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- build.xml 10 Sep 2002 15:53:38 - 1.6
+++ build.xml 10 Sep 2002 17:26:17 - 1.7
@@ -11,9 +11,6 @@
!-- Build Defaults --
!--property name=catalina.build
value=${basedir}/catalina/build/--
- !-- used by gump to keep from building more that just catalina --
- property name=catalina.target value=deploy /
-
!-- Source dependencies --
property name=api.home
value=${basedir}/../jakarta-servletapi-5/
@@ -46,6 +43,16 @@
description=Build and deploy all components
echoTarget: Catalina - Deploy .../echo
ant dir=${basedir}/catalina target=${catalina.target}/
+echoTarget: Webapps - Deploy .../echo
+ant dir=${basedir}/webapps target=deploy/
+ /target
+
+ !-- == DEPLOY: Deploy Core Components
=== -- + !-- used by gump to build just catalina and not
the j-t-connectors -- + target name=deploy-catalina
depends=deploy-static
+ description=Build and deploy all components
+echoTarget: Catalina - Deploy .../echo
+ant dir=${basedir}/catalina target=deploy-catalina/
echoTarget: Webapps - Deploy .../echo
ant dir=${basedir}/webapps target=deploy/
/target
1.8 +1 -2 jakarta-tomcat-catalina/gump.xml
Index: gump.xml
===
RCS file: /home/cvs/jakarta-tomcat-catalina/gump.xml,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- gump.xml10 Sep 2002 16:16:54 - 1.7
+++ gump.xml10 Sep 2002 17:26:17 - 1.8
@@ -10,8 +10,7 @@
project name=jakarta-tomcat-catalina
packageorg.apache.catalina/package
-ant target=deploy
- property name=catalina.target value=deploy-catalina /
+ant target=deploy-catalina
property name=jtc.home project=jakarta-tomcat-connectors
reference=home/
property name=catalina.home project=jakarta-tomcat-catalina
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
cvs commit: jakarta-tomcat-catalina build.xml
bobh2002/09/10 11:08:29
Modified:.build.xml
Log:
- fix subproject catalina target. thanks Steve Downey
Revision ChangesPath
1.8 +1 -1 jakarta-tomcat-catalina/build.xml
Index: build.xml
===
RCS file: /home/cvs/jakarta-tomcat-catalina/build.xml,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- build.xml 10 Sep 2002 17:26:17 - 1.7
+++ build.xml 10 Sep 2002 18:08:29 - 1.8
@@ -42,7 +42,7 @@
target name=deploy depends=deploy-static
description=Build and deploy all components
echoTarget: Catalina - Deploy .../echo
-ant dir=${basedir}/catalina target=${catalina.target}/
+ant dir=${basedir}/catalina target=deploy/
echoTarget: Webapps - Deploy .../echo
ant dir=${basedir}/webapps target=deploy/
/target
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 12492] New: - JSP with lots of custom tags crashes tomcat VM
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=12492. 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=12492 JSP with lots of custom tags crashes tomcat VM Summary: JSP with lots of custom tags crashes tomcat VM Product: Tomcat 4 Version: 4.1.2 Platform: PC OS/Version: Windows NT/2K Status: NEW Severity: Critical Priority: Other Component: Jasper AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] I'm about to attach a simple WAR that, when deployed in tomcat 4.1.2 (happens also in 4.0.1), crashes when visiting the main JSP page. It appears the page compiles ok. Java and class files are generated in work. Then it crashes with this error: Starting service Internal Services Java Web Services Developer Pack/1.0_01-fcs Starting service Java Web Services Developer Pack Java Web Services Developer Pack/1.0_01-fcs # # HotSpot Virtual Machine Error, Internal Error # Please report this error at # http://java.sun.com/cgi-bin/bugreport.cgi # # Error ID: 47454E45524154452F4F502D41500E435050084B # # Problematic Thread: prio=5 tid=0xd04ff28 nid=0x608 runnable # I'll attach the war. Ed -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 12492] - JSP with lots of custom tags crashes tomcat VM
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=12492. 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=12492 JSP with lots of custom tags crashes tomcat VM --- Additional Comments From [EMAIL PROTECTED] 2002-09-10 18:43 --- Created an attachment (id=2994) War that crashes tomcat VM -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 12493] New: - Unable to create a variable scope to a fragment
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=12493. 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=12493 Unable to create a variable scope to a fragment Summary: Unable to create a variable scope to a fragment Product: Tomcat 5 Version: Nightly Build Platform: Other OS/Version: Other Status: NEW Severity: Major Priority: Other Component: Jasper2 AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] If a tag file has a vraibale directive with a fragment attribute that mentions the fragment to which the variable should be scoped , the container does not sem to behave in the expected way. It expects the user to add a jsp:param sub-elemnt to the jsp:invoke element. Also the variable is available in the body of the tag defined by the tag file. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
cvs commit: jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina/startup ContextConfig.java
jfarcand2002/09/10 12:40:25 Modified:catalina/src/share/org/apache/catalina/startup ContextConfig.java Log: Change the logging levelo from Info to Log when performance information are displayed.CVS: -- Revision ChangesPath 1.12 +6 -6 jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina/startup/ContextConfig.java Index: ContextConfig.java === RCS file: /home/cvs/jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina/startup/ContextConfig.java,v retrieving revision 1.11 retrieving revision 1.12 diff -u -r1.11 -r1.12 --- ContextConfig.java24 Aug 2002 02:27:27 - 1.11 +++ ContextConfig.java10 Sep 2002 19:40:25 - 1.12 @@ -329,7 +329,7 @@ } long t2=System.currentTimeMillis(); if( (t2-t1 ) 200 ) -log.info(Processed + url ++ ( t2-t1)); +log.log(Processed + url ++ ( t2-t1)); } @@ -663,7 +663,7 @@ } long t2=System.currentTimeMillis(); if( (t2-t1) 200 ) -log.info(Processed default web.xml + file ++ ( t2-t1)); +log.log(Processed default web.xml + file ++ ( t2-t1)); } -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
cvs commit: jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina/startup Catalina.java
jfarcand2002/09/10 12:41:40
Modified:catalina/src/share/org/apache/catalina/startup Catalina.java
Log:
Change the loggin level from Info toLog when performance number are displayed.CVS:
--
Revision ChangesPath
1.3 +7 -7
jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina/startup/Catalina.java
Index: Catalina.java
===
RCS file:
/home/cvs/jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina/startup/Catalina.java,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- Catalina.java 6 Aug 2002 16:50:38 - 1.2
+++ Catalina.java 10 Sep 2002 19:41:40 - 1.3
@@ -363,7 +363,7 @@
parentClassLoader));
long t2=System.currentTimeMillis();
-log.info(Digester for server.xml created + ( t2-t1 ));
+log.log(Digester for server.xml created + ( t2-t1 ));
return (digester);
}
@@ -456,7 +456,7 @@
System.exit(1);
}
long t2=System.currentTimeMillis();
-log.info( Server.xml processed + (t2-t1 ));
+log.log( Server.xml processed + (t2-t1 ));
// Setting additional variables
if (!useNaming) {
@@ -515,7 +515,7 @@
server.initialize();
((Lifecycle) server).start();
long t4=System.currentTimeMillis();
-log.info( server.start + server + + (t4-t3 ));
+log.log( server.start + server + + (t4-t3 ));
try {
// Register shutdown hook
Runtime.getRuntime().addShutdownHook(shutdownHook);
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 12492] - JSP with lots of custom tags crashes tomcat VM
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=12492. 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=12492 JSP with lots of custom tags crashes tomcat VM --- Additional Comments From [EMAIL PROTECTED] 2002-09-10 19:58 --- Created an attachment (id=2999) war file has no faces dependencies -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 12492] - JSP with lots of custom tags crashes tomcat VM
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=12492. 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=12492 JSP with lots of custom tags crashes tomcat VM --- Additional Comments From [EMAIL PROTECTED] 2002-09-10 20:00 --- JVM crash does not occur with jdk1.4 -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 12492] - JSP with lots of custom tags crashes tomcat VM
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=12492. 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=12492 JSP with lots of custom tags crashes tomcat VM [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||INVALID -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 12492] - JSP with lots of custom tags crashes tomcat VM
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=12492. 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=12492 JSP with lots of custom tags crashes tomcat VM --- Additional Comments From [EMAIL PROTECTED] 2002-09-10 20:37 --- Please report the bug to SUN's VM team. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 12501] New: - Custom loaderClass=... ignored in Loader.../Loader
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=12501.
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=12501
Custom loaderClass=... ignored in Loader.../Loader
Summary: Custom loaderClass=... ignored in Loader.../Loader
Product: Tomcat 4
Version: 4.0.4 Final
Platform: All
OS/Version: Other
Status: NEW
Severity: Blocker
Priority: Other
Component: Catalina
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]
The implementation ignores custom loader class settings as in the following
example:
Loader className=org.apache.catalina.loader.WebappLoader delegate=false
checkInterval=15 loaderClass=Custom.WebClassLoader debug=1/
This behavior is due to the hardcoding of the initialization of a
org.apache.cataline.loader.WebappClassLoader in WebappLoader.java, offending
code segment below (lines 614-629):
if (parentClassLoader == null) {
classLoader = new WebappClassLoader(container.getResources());
} else {
classLoader = new WebappClassLoader(parentClassLoader, container.getResources
());
}
There is private variable named loaderClass which does
contain Custom.WebClassLoader, the value specified in the loaderClass=
WebappLoader completely ignores this value and proceeds to load
WebappClassLoader.
I believe this is in error! WebappLoader should consider the directive given in
the server.xml file and load the appropriate class!
Michael
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 12492] - JSP with lots of custom tags crashes tomcat VM
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=12492. 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=12492 JSP with lots of custom tags crashes tomcat VM [EMAIL PROTECTED] changed: What|Removed |Added Status|RESOLVED|CLOSED --- Additional Comments From [EMAIL PROTECTED] 2002-09-10 20:58 --- This is a JVM bug. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 12319] - Compile Error when a Classic Tag is nested in the jsp:attribute of a Simple Tag
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=12319. 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=12319 Compile Error when a Classic Tag is nested in the jsp:attribute of a Simple Tag [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED --- Additional Comments From [EMAIL PROTECTED] 2002-09-10 21:51 --- Fixed. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
cvs commit: jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/compiler Generator.java
luehe 2002/09/10 14:52:35
Modified:jasper2/src/share/org/apache/jasper/compiler Generator.java
Log:
Fixed 12319: Compile Error when a Classic Tag is nested in the
jsp:attribute of a Simple Tag
Revision ChangesPath
1.97 +21 -10
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.96
retrieving revision 1.97
diff -u -r1.96 -r1.97
--- Generator.java10 Sep 2002 00:36:01 - 1.96
+++ Generator.java10 Sep 2002 21:52:35 - 1.97
@@ -2661,7 +2661,8 @@
// body. The implementation of this fragment can come from
// the org.apache.jasper.runtime package as a support class.
FragmentHelperClass.Fragment fragment =
-fragmentHelperClass.openFragment(n, tagHandlerVar);
+fragmentHelperClass.openFragment(n, tagHandlerVar,
+ methodNesting);
ServletWriter outSave = out;
out = fragment.getMethodsBuffer().getOut();
String tmpParent = parent;
@@ -2669,7 +2670,7 @@
visitBody( n );
out = outSave;
parent = tmpParent;
- fragmentHelperClass.closeFragment( fragment );
+ fragmentHelperClass.closeFragment(fragment, methodNesting);
// XXX - Need to change pageContext to jspContext if
// we're not in a place where pageContext is defined (e.g.
// in a fragment or in a tag file.
@@ -3362,7 +3363,8 @@
out.printil( } );
}
- public Fragment openFragment(Node parent, String tagHandlerVar)
+ public Fragment openFragment(Node parent, String tagHandlerVar,
+ int methodNesting)
throws JasperException
{
Fragment result = new Fragment( fragments.size() );
@@ -3378,8 +3380,13 @@
// meaning only the fragment is skipped. The JSR-152
// expert group is currently discussing what to do in this case.
// See comment in closeFragment()
- out.printil( public boolean invoke + result.getId() + ( +
- java.io.Writer out, java.util.Map params ) );
+ if (methodNesting 0) {
+ out.printin(public boolean invoke);
+ } else {
+ out.printin(public void invoke);
+ }
+ out.println(result.getId() + ( +
+ java.io.Writer out, java.util.Map params ) );
out.pushIndent();
// Note: Throwable required because methods like _jspx_meth_*
// throw Throwable.
@@ -3395,10 +3402,14 @@
return result;
}
-public void closeFragment( Fragment fragment ) {
+public void closeFragment( Fragment fragment, int methodNesting ) {
ServletWriter out = fragment.getMethodsBuffer().getOut();
// XXX - See comment in openFragment()
-out.printil( return false; );
+ if (methodNesting 0) {
+ out.printil( return false; );
+ } else {
+ out.printil(return;);
+ }
out.popIndent();
out.printil( } );
}
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Form auth status not persisted between tomcat reloads
If a user is logged in (by using FORM auth), and tomcat is restarted, the logged in status for the user is forgotten, even though the session and session attributes are remembered. Apparently the status is not stored in the session (but in a HttpRequest note)? Is this a feature, or is there going to be work on it in the future? BTW, using SSO cookies doesn't seem to help (don't know if this is related). -km -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: Form auth status not persisted between tomcat reloads
Humm. To be 'logged in' is to have a 'principal' StandardSession.java declares it's principal like this /** * The authenticated Principal associated with this session, if any. * bIMPLEMENTATION NOTE:/b This object is inot/i saved and * restored across session serializations! */ private transient Principal principal = null; I don't know of any effort to change this behavior in Tomcat. Cheers -bob On Tue, 2002-09-10 at 17:54, Kristoffer Michael wrote: If a user is logged in (by using FORM auth), and tomcat is restarted, the logged in status for the user is forgotten, even though the session and session attributes are remembered. Apparently the status is not stored in the session (but in a HttpRequest note)? Is this a feature, or is there going to be work on it in the future? BTW, using SSO cookies doesn't seem to help (don't know if this is related). -km -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- Cheers, -bob -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: Form auth status not persisted between tomcat reloads
Well that's a shame. This feature seemed to work in eg. Resin, and it's very convenient. Is there some reason to this behaviour in Tomcat? But if this isn't going to change, maybe the docs should reflect this. From Realm HOW-TO (under JDBCRealm Additional notes): == # Once a user has been authenticated, the user (and his or her associated roles) are cached within Tomcat for the duration of the user's login. (For FORM-based authentication, that means until the session times out or is invalidated; for BASIC authentication, that means until the user closes their browser). == -km Bob Herrmann writes: Humm. To be 'logged in' is to have a 'principal' StandardSession.java declares it's principal like this /** * The authenticated Principal associated with this session, if any. * bIMPLEMENTATION NOTE:/b This object is inot/i saved and * restored across session serializations! */ private transient Principal principal = null; I don't know of any effort to change this behavior in Tomcat. Cheers -bob On Tue, 2002-09-10 at 17:54, Kristoffer Michael wrote: If a user is logged in (by using FORM auth), and tomcat is restarted, the logged in status for the user is forgotten, even though the session and session attributes are remembered. Apparently the status is not stored in the session (but in a HttpRequest note)? Is this a feature, or is there going to be work on it in the future? BTW, using SSO cookies doesn't seem to help (don't know if this is related). -km -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- Cheers, -bob -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 12503] New: - default servlet overrides welcome file
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=12503. 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=12503 default servlet overrides welcome file Summary: default servlet overrides welcome file Product: Tomcat 5 Version: Unknown Platform: All OS/Version: Windows NT/2K Status: NEW Severity: Normal Priority: Other Component: Catalina AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] If the default servlet is set in the applicaiton, the welcome file does not work. In web.xml if the following servlet has been set as the default servlet for the application. servlet-mapping servlet-namewebAdminPoint/servlet-name url-pattern//url-pattern /servlet-mapping The welcome file was set as: welcome-file-list welcome-fileindex.jsp/welcome-file /welcome-file-list The correct behaviour: If access webcontext/ (there is index.jsp in webcontext ), the containter should still direct the request to the index.jsp (see Servlet Spec SRV .9.10) But Tomcat does not use the welcome file once the default servlet is set. All access with end of / was handled by the default servlet. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 12286] - NullPointerException in JDBCStore (fix included)
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=12286. 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=12286 NullPointerException in JDBCStore (fix included) [EMAIL PROTECTED] changed: What|Removed |Added Version|4.0.4 Final |4.1.10 -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 12504] New: - Subject: Tomcat 4.1.10 Would not load jars from WEB-INF if context is on another drive
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=12504. 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=12504 Subject: Tomcat 4.1.10 Would not load jars from WEB-INF if context is on another drive Summary: Subject: Tomcat 4.1.10 Would not load jars from WEB-INF if context is on another drive Product: Tomcat 4 Version: 4.1.9 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: Other Component: Jasper AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] A very strange regression in tomcat 4.1.10 (worked fine in 4.1.9) I am running win2000 JDK 1.4.1 (the same with other JDKs) Tomcat (more likely JASPER but I did not try servlets or complied JSPs) would not find classes deployed as jars in context's WEB-INF/lib directory under some circumstances: 1. Context explicitly defined in server.xml or in webapps/my-context.xml 2. Context's directory is on another drive (not where tomcat is) I should add that it works if - deployed as war (and context in server.xml specify docBase to this war) OR - deployed as directory in webapps with no explicit context definition OR - deployed to the same drive where tomcat resides. The same type of deployment with explicit context in server.xml. Directory does not matter as long as it is tomcat's drive I also should add that context gets mounted and all resources in it are accessible. What is happening can be seen from log file. First I thought there are some problems with network drive z: (long name issues or whatever) so I tried c: instead - the same log file seems to be the same for all cases: 2002-09-09 17:48:34 WebappLoader[/gctrack]: Deploying class repositories to work directory D:\java\apache\tomcat41\work\Standalone\localhost\gctrack 2002-09-09 17:48:34 WebappLoader[/gctrack]: Deploy JAR /WEB-INF/lib/pti- common.jar to D:\java\apache\tomcat41\work\Standalone\localhost\gctrack\WEB-INF\lib\pti- common.jar 2002-09-09 17:48:34 WebappLoader[/gctrack]: Deploy JAR /WEB-INF/lib/pti-gctrack-jdo-config.jar to D:\java\apache\tomcat41\work\Standalone\localhost\gctrack\WEB-INF\lib\pti- gctrack-jdo-config.jar 2002-09-09 17:48:34 WebappLoader[/gctrack]: Deploy JAR /WEB-INF/lib/pti-gctrack-jdo.jar to D:\java\apache\tomcat41\work\Standalone\localhost\gctrack\WEB-INF\lib\pti- gctrack-jdo.jar 2002-09-09 17:48:34 LdapRealmCatalina[/gctrack]: Loading Role Map [null] ... 2002-09-09 17:48:35 ContextConfig[/gctrack]: WARNING: Security role name staff- hours used in an auth-constraint without being defined in a security-role 2002-09-09 17:48:35 ContextConfig[/gctrack]: Configured an authenticator for method FORM 2002-09-09 17:48:35 StandardManager[/gctrack]: Seeding random number generator class java.security.SecureRandom 2002-09-09 17:48:35 StandardManager[/gctrack]: Seeding of random number generator has been completed 2002-09-09 17:48:35 StandardWrapper[/gctrack:default]: Loading container servlet default 2002-09-09 17:48:35 StandardWrapper[/gctrack:invoker]: Loading container servlet invoker 2002-09-09 17:50:24 WebappLoader[/gctrack]: Deploying class repositories to work directory D:\java\apache\tomcat41\work\Standalone\localhost\gctrack 2002-09-09 17:50:24 WebappLoader[/gctrack]: Deploy JAR /WEB-INF/lib/pti- common.jar to z:\Projects\Gao\ogc\gctrack\main\web\gctrack\WEB-INF\lib\pti-common.jar 2002-09-09 17:50:24 WebappLoader[/gctrack]: Deploy JAR /WEB-INF/lib/pti-gctrack-jdo-config.jar to z:\Projects\Gao\ogc\gctrack\main\web\gctrack\WEB-INF\lib\pti-gctrack-jdo- config.jar 2002-09-09 17:50:24 WebappLoader[/gctrack]: Deploy JAR /WEB-INF/lib/pti-gctrack-jdo.jar to z:\Projects\Gao\ogc\gctrack\main\web\gctrack\WEB-INF\lib\pti-gctrack-jdo.jar 2002-09-09 17:50:25 LdapRealmCatalina[/gctrack]: Loading Role Map [null] ... 2002-09-09 17:50:25 ContextConfig[/gctrack]: WARNING: Security role name staff- hours used in an auth-constraint without being defined in a security-role 2002-09-09 17:50:25 ContextConfig[/gctrack]: Configured an authenticator for method FORM 2002-09-09 17:50:25 StandardManager[/gctrack]: Seeding random number generator class java.security.SecureRandom 2002-09-09 17:50:25 StandardManager[/gctrack]: Seeding of random number generator has been completed 2002-09-09 17:50:25 StandardWrapper[/gctrack:default]: Loading container servlet default 2002-09-09 17:50:25 StandardWrapper[/gctrack:invoker]: Loading container servlet invoker 2002-09-09 17:57:51 WebappLoader[/gctrack]: Deploying class repositories to work directory D:\java\apache\tomcat41\work\Standalone\localhost\gctrack 2002-09-09 17:57:51 WebappLoader[/gctrack]: Deploy JAR /WEB-INF/lib/pti- common.jar to
RE: cvs commit: jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina/startup Catalina.java
This commit has stopped Tomcat compiling. There is no log method in org.apache.commons.logging.Log. Dave
RE: cvs commit:jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina/startupCatalina.java
Yea, I changed references of log.log to log.info -bob On Tue, 2002-09-10 at 19:19, Dave wrote: This commit has stopped Tomcat compiling. There is no log method in org.apache.commons.logging.Log. Dave -- Cheers, -bob -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: cvs commit: jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina/startup ContextConfig.java
Broken build, please revert this. Log has no log method. (Second time today. Bound to happen once in while.) On Tuesday 10 September 2002 03:40 pm, [EMAIL PROTECTED] wrote: jfarcand2002/09/10 12:40:25 Modified:catalina/src/share/org/apache/catalina/startup ContextConfig.java Log: Change the logging levelo from Info to Log when performance information are displayed.CVS: -- -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 12053] - HTML Manager is not allowed to reset/start/stop the root context
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=12053. 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=12053 HTML Manager is not allowed to reset/start/stop the root context [EMAIL PROTECTED] changed: What|Removed |Added Summary|Manager is not allowed to |HTML Manager is not allowed |reset/start/stop the root |to reset/start/stop the root |context |context -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 12053] - HTML Manager is not allowed to reset/start/stop the root context
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=12053. 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=12053 HTML Manager is not allowed to reset/start/stop the root context --- Additional Comments From [EMAIL PROTECTED] 2002-09-11 01:54 --- I initially submitted this bug incorrectly. Should read: The html manager cannot reset/start/stop the root context -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 12250] - response.encodeURL does not working correctly.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=12250. 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=12250 response.encodeURL does not working correctly. [EMAIL PROTECTED] changed: What|Removed |Added Version|4.1.9 |4.1.10 --- Additional Comments From [EMAIL PROTECTED] 2002-09-11 01:56 --- Problem also exists with 4.1.10 release stable version. To add more details, it's complaining about: Given: /context/file.jsp;jsessionid=123 Error: Resource not available. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 12053] - HTML Manager is not allowed to reset/start/stop the root context
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=12053. 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=12053 HTML Manager is not allowed to reset/start/stop the root context --- Additional Comments From [EMAIL PROTECTED] 2002-09-11 02:51 --- Created an attachment (id=3006) Proposed patch for org.apache.catalina.servlets.HTMLManagerServlet -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Some url fixes
Please find attached some url fixes. There are still some more to fix. Dave fixes.diff Description: Binary data fixes2.diff Description: Binary data -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 12053] - HTML Manager is not allowed to reset/start/stop the root context
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=12053. 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=12053 HTML Manager is not allowed to reset/start/stop the root context --- Additional Comments From [EMAIL PROTECTED] 2002-09-11 02:56 --- The displayPath for the root context was getting renamed to / to soon. deployer.findDeployedApp expects the root context to be referred to as and not /. The patch above fixes this problem. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
[5][PATCH] catalina/tester fix some false positive and false negative tests
This patch builds tester against the servletapi-5 classes and repairs the URLs in the JSP examples used by tester. These were causing some false positve and false negative test results. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
cvs commit: jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina/startup ContextConfig.java Catalina.java
bobh2002/09/10 20:24:05
Modified:catalina/src/share/org/apache/catalina/startup
ContextConfig.java Catalina.java
Log:
- This quick fix allows compiling in my environment
Revision ChangesPath
1.13 +6 -6
jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina/startup/ContextConfig.java
Index: ContextConfig.java
===
RCS file:
/home/cvs/jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina/startup/ContextConfig.java,v
retrieving revision 1.12
retrieving revision 1.13
diff -u -r1.12 -r1.13
--- ContextConfig.java10 Sep 2002 19:40:25 - 1.12
+++ ContextConfig.java11 Sep 2002 03:24:05 - 1.13
@@ -329,7 +329,7 @@
}
long t2=System.currentTimeMillis();
if( (t2-t1 ) 200 )
-log.log(Processed + url ++ ( t2-t1));
+log.info(Processed + url ++ ( t2-t1));
}
@@ -663,7 +663,7 @@
}
long t2=System.currentTimeMillis();
if( (t2-t1) 200 )
-log.log(Processed default web.xml + file ++ ( t2-t1));
+log.info(Processed default web.xml + file ++ ( t2-t1));
}
1.4 +7 -7
jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina/startup/Catalina.java
Index: Catalina.java
===
RCS file:
/home/cvs/jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina/startup/Catalina.java,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- Catalina.java 10 Sep 2002 19:41:40 - 1.3
+++ Catalina.java 11 Sep 2002 03:24:05 - 1.4
@@ -363,7 +363,7 @@
parentClassLoader));
long t2=System.currentTimeMillis();
-log.log(Digester for server.xml created + ( t2-t1 ));
+log.info(Digester for server.xml created + ( t2-t1 ));
return (digester);
}
@@ -456,7 +456,7 @@
System.exit(1);
}
long t2=System.currentTimeMillis();
-log.log( Server.xml processed + (t2-t1 ));
+log.info( Server.xml processed + (t2-t1 ));
// Setting additional variables
if (!useNaming) {
@@ -515,7 +515,7 @@
server.initialize();
((Lifecycle) server).start();
long t4=System.currentTimeMillis();
-log.log( server.start + server + + (t4-t3 ));
+log.info( server.start + server + + (t4-t3 ));
try {
// Register shutdown hook
Runtime.getRuntime().addShutdownHook(shutdownHook);
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: [5][PATCH] catalina/tester fix some false positive and false negative tests
sigh/
On Tuesday 10 September 2002 10:56 pm, Steve Downey wrote:
This patch builds tester against the servletapi-5 classes and repairs the
URLs in the JSP examples used by tester. These were causing some false
positve and false negative test results.
Index: build.xml
===
RCS file: /home/cvspublic/jakarta-tomcat-catalina/tester/build.xml,v
retrieving revision 1.1.1.1
diff -u -w -r1.1.1.1 build.xml
--- build.xml 18 Jul 2002 16:47:24 - 1.1.1.1
+++ build.xml 11 Sep 2002 02:54:01 -
@@ -8,14 +8,14 @@
property file=${user.home}/build.properties/
property name=build.compiler value=classic/
- property name=servletapi.home value=../../jakarta-servletapi-4/dist/
+ property name=api.home value=../../jakarta-servletapi-5/dist/
property name=tester.buildvalue=${basedir}/build/
property name=tester.deploy value=${basedir}/../build/
property name=tester.dist value=${basedir}/dist/
!-- == Derived Property Values = --
property name=ant.jar value=${ant.home}/lib/ant.jar/
- property name=servlet.jar value=${servletapi.home}/lib/servlet.jar/
+ property name=servlet-api.jar value=${api.home}/jsr154/dist/lib/servlet-api.jar/
!-- === BUILD: Create Directories == --
target name=build-prepare
@@ -56,7 +56,7 @@
!-- Compile tester components and tools --
javac srcdir=src/tester destdir=${tester.build}/classes
- classpath=${ant.jar}:${servlet.jar}:${xerces.jar}
+ classpath=${ant.jar}:${servlet-api.jar}:${xercesImpl.jar}
deprecation=off debug=on optimize=off
excludes=**/CVS/**/
@@ -87,7 +87,7 @@
tofile=${tester.build}/web/WEB-INF/classes/org/apache/tester/Unpacked05.txt/
!-- Install Xerces --
-copy todir=${tester.build}/web/WEB-INF/lib file=${xerces.jar}/
+copy todir=${tester.build}/web/WEB-INF/lib file=${xercesImpl.jar}/
!-- Create and install tester library --
mkdir dir=${tester.build}/web/WEB-INF/lib/
Index: src/bin/tester.xml
===
RCS file: /home/cvspublic/jakarta-tomcat-catalina/tester/src/bin/tester.xml,v
retrieving revision 1.2
diff -u -w -r1.2 tester.xml
--- src/bin/tester.xml 9 Aug 2002 02:12:13 - 1.2
+++ src/bin/tester.xml 11 Sep 2002 02:54:01 -
@@ -8,11 +8,15 @@
!-- property name=protocol value=HTTP/1.0/ --
property name=protocol value=/ !-- Use HttpURLConnection --
property name=context.path value=/tester/
- property name=examples.path value=/examples/
+ property name=examples.path value=/jsp-examples/
property name=golden.pathvalue=${context.path}/golden/
property name=manager.path value=/manager/
property name=reload.pathvalue=/tester/
- taskdef name=tester classname=org.apache.tester.TestClient/
+ taskdef name=tester classname=org.apache.tester.TestClient
+classpath
+ pathelement location=${catalina.home}/webapps/tester/WEB-INF/lib/tester.jar/
+/classpath
+ /taskdef
target name=all depends=ROOT,Authentication,CaseSensitive,Decoding,ErrorPage,FilterRequest,FilterResponse,Jndi,Jsp,Lifecycle,RequestDispatcher,Resources,Security,ServletContext,ServletRequest,ServletResponse,HttpSession,XercesTest/
@@ -110,33 +114,23 @@
status=404/
!-- Should be able to execute the Date example --
-touch file=${catalina.home}/webapps/examples/jsp/dates/date.jsp/
tester host=${host} port=${port} protocol=${protocol}
- request=${examples.path}/jsp/dates/date.jsp debug=${debug}
+ request=${examples.path}/dates/date.jsp debug=${debug}
status=200/
!-- Should not be able to view the source of the Date example --
-touch file=${catalina.home}/webapps/examples/jsp/dates/date.jsp/
tester host=${host} port=${port} protocol=${protocol}
- request=${examples.path}/jsp/dates/date.Jsp debug=${debug}
+ request=${examples.path}/dates/date.Jsp debug=${debug}
status=404/
!-- Should not be able to view the source of the Date example --
-touch file=${catalina.home}/webapps/examples/jsp/dates/date.jsp/
tester host=${host} port=${port} protocol=${protocol}
- request=${examples.path}/jsp/dates/Date.jsp debug=${debug}
+ request=${examples.path}/dates/Date.jsp debug=${debug}
status=404/
!-- Should not be able to view the source of the Date example --
-touch file=${catalina.home}/webapps/examples/jsp/dates/date.jsp/
tester host=${host} port=${port} protocol=${protocol}
- request=${examples.path}/jsp/Dates/date.jsp debug=${debug}
- status=404/
-
-!-- Should not be able to view the source of the Date example --
-touch file=${catalina.home}/webapps/examples/jsp/dates/date.jsp/
-tester host=${host} port=${port} protocol=${protocol}
-
cvs commit: jakarta-tomcat/src/share/org/apache/tomcat/util/depend DependClassLoader.java DependClassLoader12.java
billbarker2002/09/10 20:27:30
Modified:src/share/org/apache/tomcat/util/depend
DependClassLoader.java DependClassLoader12.java
Log:
Check for Windows device names before attempting to read the class file.
At least under XP, this can cause a request to hang. However, it also has a very
simple work-around.
Revision ChangesPath
1.17 +4 -2
jakarta-tomcat/src/share/org/apache/tomcat/util/depend/DependClassLoader.java
Index: DependClassLoader.java
===
RCS file:
/home/cvs/jakarta-tomcat/src/share/org/apache/tomcat/util/depend/DependClassLoader.java,v
retrieving revision 1.16
retrieving revision 1.17
diff -u -r1.16 -r1.17
--- DependClassLoader.java11 Jun 2002 23:16:19 - 1.16
+++ DependClassLoader.java11 Sep 2002 03:27:30 - 1.17
@@ -199,8 +199,10 @@
// resources.
byte data[]=null;
try {
- data=readFully( is );
- if( data.length==0 ) data=null;
+ if( is.available() 0) {
+ data=readFully( is );
+ if( data.length==0 ) data=null;
+ }
is.close();
} catch(IOException ex ) {
if( debug 0 ) ex.printStackTrace();
1.12 +4 -2
jakarta-tomcat/src/share/org/apache/tomcat/util/depend/DependClassLoader12.java
Index: DependClassLoader12.java
===
RCS file:
/home/cvs/jakarta-tomcat/src/share/org/apache/tomcat/util/depend/DependClassLoader12.java,v
retrieving revision 1.11
retrieving revision 1.12
diff -u -r1.11 -r1.12
--- DependClassLoader12.java 12 Jun 2002 00:13:37 - 1.11
+++ DependClassLoader12.java 11 Sep 2002 03:27:30 - 1.12
@@ -251,8 +251,10 @@
// resources.
byte data[]=null;
try {
- data=readFully( is );
- if( data.length==0 ) data=null;
+ if( is.available() 0 ) {
+ data=readFully( is );
+ if( data.length==0 ) data=null;
+ }
is.close();
} catch(IOException ex ) {
if( debug 0 ) ex.printStackTrace();
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
cvs commit: jakarta-tomcat-catalina/tester/src/bin tester.xml
bobh2002/09/10 20:33:58
Modified:tester build.xml
tester/src/bin tester.xml
Log:
fix some false positive and false negative tests
from Steve Downey [EMAIL PROTECTED]
Revision ChangesPath
1.2 +4 -4 jakarta-tomcat-catalina/tester/build.xml
Index: build.xml
===
RCS file: /home/cvs/jakarta-tomcat-catalina/tester/build.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- build.xml 18 Jul 2002 16:47:24 - 1.1
+++ build.xml 11 Sep 2002 03:33:58 - 1.2
@@ -8,14 +8,14 @@
property file=${user.home}/build.properties/
property name=build.compiler value=classic/
- property name=servletapi.home value=../../jakarta-servletapi-4/dist/
+ property name=api.home value=../../jakarta-servletapi-5/dist/
property name=tester.buildvalue=${basedir}/build/
property name=tester.deploy value=${basedir}/../build/
property name=tester.dist value=${basedir}/dist/
!-- == Derived Property Values = --
property name=ant.jar value=${ant.home}/lib/ant.jar/
- property name=servlet.jar value=${servletapi.home}/lib/servlet.jar/
+ property name=servlet-api.jar
value=${api.home}/jsr154/dist/lib/servlet-api.jar/
!-- === BUILD: Create Directories == --
target name=build-prepare
@@ -56,7 +56,7 @@
!-- Compile tester components and tools --
javac srcdir=src/tester destdir=${tester.build}/classes
- classpath=${ant.jar}:${servlet.jar}:${xerces.jar}
+ classpath=${ant.jar}:${servlet-api.jar}:${xercesImpl.jar}
deprecation=off debug=on optimize=off
excludes=**/CVS/**/
@@ -87,7 +87,7 @@
tofile=${tester.build}/web/WEB-INF/classes/org/apache/tester/Unpacked05.txt/
!-- Install Xerces --
-copy todir=${tester.build}/web/WEB-INF/lib file=${xerces.jar}/
+copy todir=${tester.build}/web/WEB-INF/lib file=${xercesImpl.jar}/
!-- Create and install tester library --
mkdir dir=${tester.build}/web/WEB-INF/lib/
1.3 +13 -19jakarta-tomcat-catalina/tester/src/bin/tester.xml
Index: tester.xml
===
RCS file: /home/cvs/jakarta-tomcat-catalina/tester/src/bin/tester.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- tester.xml9 Aug 2002 02:12:13 - 1.2
+++ tester.xml11 Sep 2002 03:33:58 - 1.3
@@ -8,11 +8,15 @@
!-- property name=protocol value=HTTP/1.0/ --
property name=protocol value=/ !-- Use HttpURLConnection --
property name=context.path value=/tester/
- property name=examples.path value=/examples/
+ property name=examples.path value=/jsp-examples/
property name=golden.pathvalue=${context.path}/golden/
property name=manager.path value=/manager/
property name=reload.pathvalue=/tester/
- taskdef name=tester classname=org.apache.tester.TestClient/
+ taskdef name=tester classname=org.apache.tester.TestClient
+classpath
+ pathelement
location=${catalina.home}/webapps/tester/WEB-INF/lib/tester.jar/
+/classpath
+ /taskdef
target name=all
depends=ROOT,Authentication,CaseSensitive,Decoding,ErrorPage,FilterRequest,FilterResponse,Jndi,Jsp,Lifecycle,RequestDispatcher,Resources,Security,ServletContext,ServletRequest,ServletResponse,HttpSession,XercesTest/
@@ -110,33 +114,23 @@
status=404/
!-- Should be able to execute the Date example --
-touch file=${catalina.home}/webapps/examples/jsp/dates/date.jsp/
tester host=${host} port=${port} protocol=${protocol}
- request=${examples.path}/jsp/dates/date.jsp debug=${debug}
+ request=${examples.path}/dates/date.jsp debug=${debug}
status=200/
!-- Should not be able to view the source of the Date example --
-touch file=${catalina.home}/webapps/examples/jsp/dates/date.jsp/
tester host=${host} port=${port} protocol=${protocol}
- request=${examples.path}/jsp/dates/date.Jsp debug=${debug}
+ request=${examples.path}/dates/date.Jsp debug=${debug}
status=404/
!-- Should not be able to view the source of the Date example --
-touch file=${catalina.home}/webapps/examples/jsp/dates/date.jsp/
tester host=${host} port=${port} protocol=${protocol}
- request=${examples.path}/jsp/dates/Date.jsp debug=${debug}
+ request=${examples.path}/dates/Date.jsp debug=${debug}
status=404/
!-- Should not be able to view the source of the Date example --
-touch file=${catalina.home}/webapps/examples/jsp/dates/date.jsp/
tester host=${host}
cvs commit: jakarta-tomcat-catalina gump.xml
bobh2002/09/10 20:37:47 Modified:.gump.xml Log: - fix some properties. Revision ChangesPath 1.9 +7 -1 jakarta-tomcat-catalina/gump.xml Index: gump.xml === RCS file: /home/cvs/jakarta-tomcat-catalina/gump.xml,v retrieving revision 1.8 retrieving revision 1.9 diff -u -r1.8 -r1.9 --- gump.xml 10 Sep 2002 17:26:17 - 1.8 +++ gump.xml 11 Sep 2002 03:37:47 - 1.9 @@ -15,7 +15,13 @@ reference=home/ property name=catalina.home project=jakarta-tomcat-catalina reference=home/ - property name=tomcat.build path=build/ + property name=catalina.build project=jakarta-tomcat-catalina +reference=home/ + property name=catalina.deploy project=jakarta-tomcat-catalina +reference=home/ + property name=tomcat.build project=jakarta-tomcat-catalina +reference=home/ + property name=tomcat33.home value=/ property name=ant.home reference=home project=jakarta-ant/ property name=jsse.home reference=home project=jsse/ property name=jmx.home reference=home project=jmx/ -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
cvs commit: jakarta-tomcat-catalina/catalina build.xml
bobh2002/09/10 20:44:57
Modified:catalina build.xml
Log:
- minor gump related tweak
Revision ChangesPath
1.19 +1 -0 jakarta-tomcat-catalina/catalina/build.xml
Index: build.xml
===
RCS file: /home/cvs/jakarta-tomcat-catalina/catalina/build.xml,v
retrieving revision 1.18
retrieving revision 1.19
diff -u -r1.18 -r1.19
--- build.xml 16 Aug 2002 18:51:20 - 1.18
+++ build.xml 11 Sep 2002 03:44:56 - 1.19
@@ -10,6 +10,7 @@
property file=${user.home}/build.properties/--
!-- Build Defaults --
+ property name=catalina.home value=${basedir}/../
property name=catalina.buildvalue=${catalina.home}/catalina/build/
property name=catalina.deploy value=${catalina.home}/build/
property name=catalina.dist value=${catalina.home}/dist/
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
[5][PATCH] Enable manager app in catalina/tester deployment
The tester app needs to unload and reload the tester webapp, but, of course,
the manager app is not enabled by default. This adds a tomcat-users.xml so
that it can be deployed and run automatically.
Now there are only a few failures left that I'm seeing.
The tomcat-users.xml should go into a new directory conf, under src. i.e.
jakarta-tomcat-catalina/tester/src/conf.
Index: build.xml
===
RCS file: /home/cvspublic/jakarta-tomcat-catalina/tester/build.xml,v
retrieving revision 1.1.1.1
diff -u -w -r1.1.1.1 build.xml
--- build.xml 18 Jul 2002 16:47:24 - 1.1.1.1
+++ build.xml 11 Sep 2002 03:50:23 -
@@ -8,19 +8,20 @@
property file=${user.home}/build.properties/
property name=build.compiler value=classic/
- property name=servletapi.home value=../../jakarta-servletapi-4/dist/
+ property name=api.home value=../../jakarta-servletapi-5/dist/
property name=tester.buildvalue=${basedir}/build/
property name=tester.deploy value=${basedir}/../build/
property name=tester.dist value=${basedir}/dist/
!-- == Derived Property Values = --
property name=ant.jar value=${ant.home}/lib/ant.jar/
- property name=servlet.jar value=${servletapi.home}/lib/servlet.jar/
+ property name=servlet-api.jar value=${api.home}/jsr154/dist/lib/servlet-api.jar/
!-- === BUILD: Create Directories == --
target name=build-prepare
mkdir dir=${tester.build}/
mkdir dir=${tester.build}/bin/
+mkdir dir=${tester.build}/conf/
mkdir dir=${tester.build}/classes/
mkdir dir=${tester.build}/lib/
/target
@@ -30,7 +31,6 @@
target name=build-static depends=build-prepare
!-- Executable Commands --
-mkdir dir=${tester.build}/bin/
copy todir=${tester.build}/bin
fileset dir=src/bin /
/copy
@@ -38,8 +38,11 @@
fixcrlf srcdir=${tester.build}/bin includes=*.bat eol=crlf/
chmod perm=+x file=${tester.build}/bin/tester.sh/
+copy todir=${tester.build}/conf
+ fileset dir=src/conf /
+/copy
+
!-- Compiled Classes --
-mkdir dir=${tester.build}/classes/
!-- Web Application --
mkdir dir=${tester.build}/web/
@@ -56,7 +59,7 @@
!-- Compile tester components and tools --
javac srcdir=src/tester destdir=${tester.build}/classes
- classpath=${ant.jar}:${servlet.jar}:${xerces.jar}
+ classpath=${ant.jar}:${servlet-api.jar}:${xercesImpl.jar}
deprecation=off debug=on optimize=off
excludes=**/CVS/**/
@@ -87,7 +90,7 @@
tofile=${tester.build}/web/WEB-INF/classes/org/apache/tester/Unpacked05.txt/
!-- Install Xerces --
-copy todir=${tester.build}/web/WEB-INF/lib file=${xerces.jar}/
+copy todir=${tester.build}/web/WEB-INF/lib file=${xercesImpl.jar}/
!-- Create and install tester library --
mkdir dir=${tester.build}/web/WEB-INF/lib/
@@ -132,6 +135,7 @@
target name=deploy-prepare
mkdir dir=${tester.deploy}/
mkdir dir=${tester.deploy}/bin/
+mkdir dir=${tester.deploy}/conf/
/target
@@ -145,6 +149,10 @@
fixcrlf srcdir=${tester.deploy}/bin includes=*.sh eol=lf/
fixcrlf srcdir=${tester.deploy}/bin includes=*.bat eol=crlf/
chmod perm=+x file=${tester.deploy}/bin/tester.sh/
+
+copy todir=${tester.deploy}/conf overwrite=yes
+ fileset dir=${tester.build}/conf /
+/copy
!-- Unpacked Shared Classes --
mkdir dir=${tester.deploy}/shared/classes/
!--
NOTE: By default, no user is included in the manager role required
to operate the /manager web application. If you wish to use this app,
you must define such a user - the username and password are arbitrary.
--
tomcat-users
user name=tomcat password=tomcat roles=tomcat,role1,manager /
/tomcat-users
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 12504] - Subject: Tomcat 4.1.10 Would not load jars from WEB-INF if context is on another drive
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=12504. 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=12504 Subject: Tomcat 4.1.10 Would not load jars from WEB-INF if context is on another drive [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||DUPLICATE Summary|Subject: Tomcat 4.1.10 Would|Subject: Tomcat 4.1.10 Would |not load jars from WEB-INF |not load jars from WEB-INF |if context is on another|if context is on another |drive |drive --- Additional Comments From [EMAIL PROTECTED] 2002-09-11 05:24 --- *** This bug has been marked as a duplicate of 12387 *** -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 12387] - JSP Compilation errors: jars in WEB-INF/lib and classes in WEB-INF/classes not in classpath
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=12387. 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=12387 JSP Compilation errors: jars in WEB-INF/lib and classes in WEB-INF/classes not in classpath [EMAIL PROTECTED] changed: What|Removed |Added CC||[EMAIL PROTECTED] --- Additional Comments From [EMAIL PROTECTED] 2002-09-11 05:24 --- *** Bug 12504 has been marked as a duplicate of this bug. *** -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
cvs commit: jakarta-tomcat build.xml
billbarker2002/09/10 22:36:43
Modified:.build.xml
Log:
Add commons-logging to the ClassPath for Util.
Preliminary step for starting on converting Util to c-l (which makes debugging s
much nicer :)
Revision ChangesPath
1.186 +5 -0 jakarta-tomcat/build.xml
Index: build.xml
===
RCS file: /home/cvs/jakarta-tomcat/build.xml,v
retrieving revision 1.185
retrieving revision 1.186
diff -u -r1.185 -r1.186
--- build.xml 30 Jul 2002 19:07:28 - 1.185
+++ build.xml 11 Sep 2002 05:36:42 - 1.186
@@ -84,6 +84,10 @@
property name=commons-pool.lib location=${commons-pool.home}/dist/
property name=commons-pool.jar
location=${commons-pool.lib}/commons-pool.jar/
+ property name=commons-logging.home
location=${jakarta-commons}/commons-logging-1.0 /
+ property name=commons-logging.lib location=${jakarta-logging.home} /
+ property name=commons-logging.jar
location=${commons-logging.lib}/commons-logging-api.jar /
+
property name=commons-collections.home
location=${jakarta-commons}/collections/
property name=commons-collections.lib
location=${commons-collections.home}/dist/
property name=commons-collections.jar
location=${commons-collections.lib}/commons-collections.jar/
@@ -310,6 +314,7 @@
srcdir=src/share
classpath
pathelement location=${tomcat-util.jar}/
+ pathelement location=${commons-logging.jar} /
/classpath
include name=org/apache/tomcat/util/**/
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
