Conflicts between 2 lib in Tomcat 4.0.3
Hi, I'm working with TC 4.0.3. In the WEB-INF/lib directory, I've got 2 libraries : xerces.jar (I think it's an old Xerces, I didn't put myself there : someone else need it) and xercesImpl.jar (a newer version of xerces). I coded a class that need xerces2, but when I launch it (via a servlet) in my Tomcat, it throws a NoSuchMethoError cause it doesn't take the good jar ! How can I force TC to take the new librairy ? Thanx in advance - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
JNDI DBCP resources, another problem.
Hello list. I fought with that for about two weeks recently and had done it, so my JNDIRealm works. But! Now servlet that just gets a connection from JNDI resource and tries to query database is broken! Situation is that: ... GlobalNamingResource Resource ... / ResourceParams ... /ResourceParams /GlobalNamingResource ... Context ResourceLink ... / Realm ... / /Context ... works with JNDIRealm, but not with common servlet getting resource from JNDI, and ... Context Resource ... / ResourceParams ... /ResourceParams Realm ... / /Context ... works with servlet but not with JNDIRealm! It's only two options to have a resource in JNDI -- define it inside GlobalNamingResource or inside Context , and each of it works separately but not simultaneously. Any advice/suggestion/RTFM link will be GREATELY appreciated because I'm really want to know what's going on behind the scene to not ask such a stupid questions again. Thanks a lot. -- Veniamin Fichin [EMAIL PROTECTED] Programmer athttp://www.rbcsoft.ru/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
tomcat, tyrex and mysql, and autocommit
Martin Jacobson wrote: emiliano albiani wrote: HI, I'm trying configuring tyrex in my tomcat installation to use MySql xa driver. I did it as described in tomcat documentation: http://jakarta.apache.org/tomcat/to...les-howto.html, http://jakarta.apache.org/tomcat/tomcat-4.1-doc/jndi-datasource-examples-howto.html, but something is going wrong. snip Error trace: 2003-01-31 12:04:24,631 ERROR [Thread-3](ConnectionPool.java:1046) - Error attempting to destory connection XAConnection: unused by connection pool iseDatasource java.sql.SQLException: Can't call commit when autocommit=true at com.mysql.jdbc.Connection.commit(Unknown Source) at com.mysql.jdbc.xa.XAConnectionImpl.close(Unknown Source) at tyrex.resource.jdbc.ConnectionPool.discard(ConnectionPool.java:1042) at tyrex.resource.jdbc.ConnectionPool.release(ConnectionPool.java:852) at tyrex.resource.jdbc.ConnectionPool.connectionErrorOccurred(ConnectionPool.java:636) at com.mysql.jdbc.xa.XAConnectionImpl.getConnection(Unknown Source) at tyrex.resource.jdbc.ConnectionPool.getConnection(ConnectionPool.java:427) at tyrex.resource.jdbc.ConnectionPool.getConnection(ConnectionPool.java:398) By default MySQL is in autocommit mode - you should turn it off to enable transactions. Martin How can I do it? This is what I did with no success: mysql ise set autocommit=0; but tyrex still have the same problem. What am I missing? Thanks in advance. Emiliano. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: tomcat, tyrex and mysql, and autocommit
If you are running Tomcat 4.1.x you should be using DBCP for database connections. Tyrex is no longer used as of 4.1 -Original Message- From: emiliano albiani [mailto:[EMAIL PROTECTED]] Sent: Montag, 03. Februar 2003 10:57 To: Tomcat Users List Subject: tomcat, tyrex and mysql, and autocommit Martin Jacobson wrote: emiliano albiani wrote: HI, I'm trying configuring tyrex in my tomcat installation to use MySql xa driver. I did it as described in tomcat documentation: http://jakarta.apache.org/tomcat/to...les-howto.html, http://jakarta.apache.org/tomcat/tomcat-4.1-doc/jndi-datasource-examples-howto.html, but something is going wrong. snip Error trace: 2003-01-31 12:04:24,631 ERROR [Thread-3](ConnectionPool.java:1046) - Error attempting to destory connection XAConnection: unused by connection pool iseDatasource java.sql.SQLException: Can't call commit when autocommit=true at com.mysql.jdbc.Connection.commit(Unknown Source) at com.mysql.jdbc.xa.XAConnectionImpl.close(Unknown Source) at tyrex.resource.jdbc.ConnectionPool.discard(ConnectionPool.java:1042) at tyrex.resource.jdbc.ConnectionPool.release(ConnectionPool.java:852) at tyrex.resource.jdbc.ConnectionPool.connectionErrorOccurred(ConnectionPool.java:636) at com.mysql.jdbc.xa.XAConnectionImpl.getConnection(Unknown Source) at tyrex.resource.jdbc.ConnectionPool.getConnection(ConnectionPool.java:427) at tyrex.resource.jdbc.ConnectionPool.getConnection(ConnectionPool.java:398) By default MySQL is in autocommit mode - you should turn it off to enable transactions. Martin How can I do it? This is what I did with no success: mysql ise set autocommit=0; but tyrex still have the same problem. What am I missing? Thanks in advance. Emiliano. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: tomcat, tyrex and mysql, and autocommit
emiliano albiani wrote: This is what I did with no success: mysql ise set autocommit=0; but tyrex still have the same problem. What am I missing? Sorry, Emiliano, I don't use Tyrex, so I don't know how you'd do this :-( Martin - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: mod_jk
In production, you only want the connectors used for actual connections to be enabled. If you're leaving port 8080 open, there's really no purpose for Apache, as one of the primary purposes of using Apache on port 80 instead of Tomcat is security. Leaving Tomcat available on 8080 undermines this goal. So, if you are using a connector at all, there's no reason to have any port open except the connector port. The protocol used by the JK/JK2 connectors is not HTTP. It is called AJP, which, I believe, stands for Apache JServ Protocol. JServ was the original Apache + Tomcat connector. John -Original Message- From: rf [mailto:[EMAIL PROTECTED]] Sent: Monday, February 03, 2003 2:29 AM To: Tomcat Users List Subject: Re: mod_jk Thank you Lajos and Oscar. Btw, what is the interface Apache uses to communicate to Tomcat at 8009? I guess it wont be HTTP. For security reasons, I assume it would be safer to run all tomcat processes on the lo interface. Is this correct, and recommended? ~rf. --- Lajos [EMAIL PROTECTED] wrote: Rf - When you use mod_jk, Apache communicates to Tomcat on (default) port 8009. Port 8080 is for direct HTTP connections to Tomcat which, by default is enabled. So, the answer is yes: you can expose web applications to Apache via mod_jk, and access them on the Apache port, but also access them by point your browser directly to the Tomcat port. Regards, Lajos rf wrote: When I use a tomcat-apache connector to redirect http requests to port 80 to port 8080, can I still use port 8080 to connect to tomcat directly bypassing apache? If yes, how do I not allow this? By running tomcat on lo's 8080? What about on Windows? Thank you Rf __ Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now. http://mailplus.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Lajos Moczar Open Source Support, Consulting and Training Cocoon Developer's Handbook (www.amazon.com/exec/obidos/tg/detail/-/0672322579) _ _ / \ / /___\ / / \ / http://www.galatea.com -- powered by AzSSL - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] __ Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now. http://mailplus.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --- Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.449 / Virus Database: 251 - Release Date: 1/27/2003 --- Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.449 / Virus Database: 251 - Release Date: 1/27/2003 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: JK2 for Apache 2.0.44 on Linux
There aren't any 2.0.2. Apache 2.0.44 is module compatible with 2.0.43. Modules built against 2.0.43 will work with 2.0.44. Perhaps if you posted the errors you're getting trying to build the connector from 2.0.2 source, someone could help you. John -Original Message- From: Paul Gregoire [mailto:[EMAIL PROTECTED]] Sent: Sunday, February 02, 2003 11:22 PM To: Tomcat Users List Subject: Re: JK2 for Apache 2.0.44 on Linux That is the JK2 2.0.1 release and it does not include a build for 2.0.44 unless the 2.0.43 version works with 2.0.44. but anyhow im looking for JK2 2.0.2 - Original Message - From: Turner, John [EMAIL PROTECTED] To: 'Tomcat Users List ' [EMAIL PROTECTED] Sent: Sunday, February 02, 2003 8:09 PM Subject: RE: JK2 for Apache 2.0.44 on Linux http://jakarta.apache.org/builds/jakarta-tomcat-connectors/jk2/release/v2.0. 1/bin/linux/i386/ John -Original Message- From: Paul Gregoire To: Tomcat Users List Sent: 2/2/03 10:05 PM Subject: JK2 for Apache 2.0.44 on Linux Does anyone here know where i can find jk2 2.0.2 for apache 2.0.44?? i am trying to get tomcat 4.1.18 running on my Redhat 8 box, but i cannot seem to get connectors build for myself. I also cannot find them on Apache's site. Thanks in advance - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --- Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.449 / Virus Database: 251 - Release Date: 1/27/2003 --- Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.449 / Virus Database: 251 - Release Date: 1/27/2003 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: mod_jk
Hello John Thanks for your email. 1. What are the advantages of using Apache on top of Tomcat (with regards to security and otherwise)? If there is a document already, please point me to that. 2. Where can I know more about the AJP protocol? ~rf --- Turner, John [EMAIL PROTECTED] wrote: In production, you only want the connectors used for actual connections to be enabled. If you're leaving port 8080 open, there's really no purpose for Apache, as one of the primary purposes of using Apache on port 80 instead of Tomcat is security. Leaving Tomcat available on 8080 undermines this goal. So, if you are using a connector at all, there's no reason to have any port open except the connector port. The protocol used by the JK/JK2 connectors is not HTTP. It is called AJP, which, I believe, stands for Apache JServ Protocol. JServ was the original Apache + Tomcat connector. John -Original Message- From: rf [mailto:[EMAIL PROTECTED]] Sent: Monday, February 03, 2003 2:29 AM To: Tomcat Users List Subject: Re: mod_jk Thank you Lajos and Oscar. Btw, what is the interface Apache uses to communicate to Tomcat at 8009? I guess it wont be HTTP. For security reasons, I assume it would be safer to run all tomcat processes on the lo interface. Is this correct, and recommended? ~rf. --- Lajos [EMAIL PROTECTED] wrote: Rf - When you use mod_jk, Apache communicates to Tomcat on (default) port 8009. Port 8080 is for direct HTTP connections to Tomcat which, by default is enabled. So, the answer is yes: you can expose web applications to Apache via mod_jk, and access them on the Apache port, but also access them by point your browser directly to the Tomcat port. Regards, Lajos rf wrote: When I use a tomcat-apache connector to redirect http requests to port 80 to port 8080, can I still use port 8080 to connect to tomcat directly bypassing apache? If yes, how do I not allow this? By running tomcat on lo's 8080? What about on Windows? Thank you Rf __ Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now. http://mailplus.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Lajos Moczar Open Source Support, Consulting and Training Cocoon Developer's Handbook (www.amazon.com/exec/obidos/tg/detail/-/0672322579) _ _ / \ / /___\ / / \ / http://www.galatea.com -- powered by AzSSL - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] __ Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now. http://mailplus.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --- Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.449 / Virus Database: 251 - Release Date: 1/27/2003 --- Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.449 / Virus Database: 251 - Release Date: 1/27/2003 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Missed your favourite TV serial last night? Try the new, Yahoo! TV. visit http://in.tv.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: mod_jk
1. There's really no document (that I know of), and hopefully my comments weren't taken as a claim that Tomcat is inherently insecure. Lots of administrators, especially in the UNIX/Linux world, have an aversion to running services as root, especially web servers. In order for Tomcat to bind to port 80, it has to run as root (ports less than 1024 require root privileges for services to bind). Apache runs as root, but uses child processes with more restrictive privileges to serve actual requests. On the Windows side, everything runs as SYSTEM (essentially the equivalent of root) by default (yuck!). There are all sorts of reasons why you might want to use Apache with Tomcat: - don't have to run a service as root - need support for Apache modules like mod_rewrite or a custom Apache module - need support for PHP or other CGI-type technologies - need support for Apache-style access restrictions - need to load-balance to multiple Tomcats (JK and JK2 can do this) - need to support various types of virtual hosting, not all of which require a servlet container - and more 2. You can always look through the source, and I'm sure your specific questions would get answered pretty fast on the tomcat-dev list. John -Original Message- From: rf [mailto:[EMAIL PROTECTED]] Sent: Monday, February 03, 2003 7:21 AM To: Tomcat Users List Subject: RE: mod_jk Hello John Thanks for your email. 1. What are the advantages of using Apache on top of Tomcat (with regards to security and otherwise)? If there is a document already, please point me to that. 2. Where can I know more about the AJP protocol? ~rf --- Turner, John [EMAIL PROTECTED] wrote: In production, you only want the connectors used for actual connections to be enabled. If you're leaving port 8080 open, there's really no purpose for Apache, as one of the primary purposes of using Apache on port 80 instead of Tomcat is security. Leaving Tomcat available on 8080 undermines this goal. So, if you are using a connector at all, there's no reason to have any port open except the connector port. The protocol used by the JK/JK2 connectors is not HTTP. It is called AJP, which, I believe, stands for Apache JServ Protocol. JServ was the original Apache + Tomcat connector. John -Original Message- From: rf [mailto:[EMAIL PROTECTED]] Sent: Monday, February 03, 2003 2:29 AM To: Tomcat Users List Subject: Re: mod_jk Thank you Lajos and Oscar. Btw, what is the interface Apache uses to communicate to Tomcat at 8009? I guess it wont be HTTP. For security reasons, I assume it would be safer to run all tomcat processes on the lo interface. Is this correct, and recommended? ~rf. --- Lajos [EMAIL PROTECTED] wrote: Rf - When you use mod_jk, Apache communicates to Tomcat on (default) port 8009. Port 8080 is for direct HTTP connections to Tomcat which, by default is enabled. So, the answer is yes: you can expose web applications to Apache via mod_jk, and access them on the Apache port, but also access them by point your browser directly to the Tomcat port. Regards, Lajos rf wrote: When I use a tomcat-apache connector to redirect http requests to port 80 to port 8080, can I still use port 8080 to connect to tomcat directly bypassing apache? If yes, how do I not allow this? By running tomcat on lo's 8080? What about on Windows? Thank you Rf __ Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now. http://mailplus.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Lajos Moczar Open Source Support, Consulting and Training Cocoon Developer's Handbook (www.amazon.com/exec/obidos/tg/detail/-/0672322579) _ _ / \ / /___\ / / \ / http://www.galatea.com -- powered by AzSSL - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] __ Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now. http://mailplus.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: mod_jk
You don't have to dig that deep in the first attempt. There is some documentation online: http://jakarta.apache.org/tomcat/tomcat-4.1-doc/jk2/common/AJPv13.html http://jakarta.apache.org/tomcat/tomcat-4.1-doc/jk2/common/AJPv13-extensions-proposal.html -Original Message- From: Turner, John [mailto:[EMAIL PROTECTED]] Sent: Monday, February 03, 2003 2:08 PM To: 'Tomcat Users List' Subject: RE: mod_jk 2. You can always look through the source, and I'm sure your specific questions would get answered pretty fast on the tomcat-dev list. John -Original Message- From: rf [mailto:[EMAIL PROTECTED]] Sent: Monday, February 03, 2003 7:21 AM To: Tomcat Users List Subject: RE: mod_jk 2. Where can I know more about the AJP protocol? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
FYI Update on LogConfigurationException (Using Struts and Tomcat)
Hi, I sent an email to this group a week or so going asking if anyone gets a LogConfigurationException that crashes Tomcat. I have done some more research and the problem happens when an application uses Commons logging. In my case Struts uses Commons logging. The solution is to move the commons logging jar file and the commons beans-utils jar files from server/lib to common/lib and ensure that you don't deploy these jar files with your Web app. I hope this helps anyone else who gets the same problem as it is a show stopper because it crashes Tomcat. Regards Jim. PLEASE READ: The information contained in this email is confidential and intended for the named recipient(s) only. If you are not an intended recipient of this email you must not copy, distribute or take any further action in reliance on it and you should delete it and notify the sender immediately. Email is not a secure method of communication and Nomura International plc cannot accept responsibility for the accuracy or completeness of this message or any attachment(s). Please examine this email for virus infection, for which Nomura International plc accepts no responsibility. If verification of this email is sought then please request a hard copy. Unless otherwise stated any views or opinions presented are solely those of the author and do not represent those of Nomura International plc. This email is intended for informational purposes only and is not a solicitation or offer to buy or sell securities or related financial instruments. Nomura International plc is regulated by the Financial Services Authority and is a member of the London Stock Exchange. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Datasource and connection
Hi everybody! I'm using datasource of tomcat for get connection. Well, when i do this: ... DataSource ds = (DataSource)ctx.lookup( java:comp/env/jdbc/Anything); if (ds != null) connection = ds.getConnection(); ... In the next time, will give tomcat to me a new connection or the same? I think that is same, but i didn't read anything about this. And when Tomcat close this connection? Only through the timeout? Thanks in advanced.
sharing resourses across webapps
Hi, I need your openion about sharing a resourse across webapps. Imagine I have two webapps, App1, App2. A resourse named Central.java must be shared across the two webapps. The idea is to have unique acess to a method in Central.java for threads from two or more webapps. I suppose, I can define a Resourse and share the resourse across webapps. Ref: http://jakarta.apache.org/tomcat/tomcat-4.1-doc/jndi-resources-howto.html it says, Create the JavaBean class which will be instantiated each time that the resource factory is looked up. For this example, assume you create a class com.mycompany.MyBean, which looks like this: If I like my resourse to contain a static synchronised method ( block if you like, for performace reasons ), will this synchronization work across Webapps? Theoritically, it must work. If am in the correct direction until now, in fact I need to share a resourse across a SOAP Service and one Web application, not between two webapps. How different is sharing a resourse across webapps than sharing across SOAP and webapps? Thanks in advance for your suggestions... Madhav
Custom tag life cycle
The webapp which I am developing (see http://www.timeczar.com for details) uses a moderately complex custom tag library, and I've found the lifecycle of a TagSupport object to be very confusing. As I understand it, a TagSupport object may (but is not guaranteed to) be reused for subsequent occurrences of the same tag in a JSP. This means that attribute variables can't safely be initialized in the constructor, because they may not get reinitialized for subsequent occurrences of the tag. (Here I'm assuming that setter functions for attributes simply set an instance variable.) After some digging, I found that the recommended way to reset attribute instance varaibles is to use the doEndTag method. This probably doesn't work if a tag is nested within a tag of the same name, but I can live with that. Doing this works fine in Tomcat. However, I recently ported my webapp to Resin and found that it doesn't work there. Here's a cut-back excerpt from my JSP: caltags:eventset caltags:evtstartdate mode=date length=m/ - caltags:evtenddate mode=date length=m/ /caltags:eventset The class which implements eventset includes the tag body once for each event in the set. The evtstartdate and evtenddate tags are implemented by a class called DateTag, which extends TagSupport. Under Tomcat, DateTag.setMode and DateTag.SetLength get called once for each tag in each inclusion of the tag body. Under Resin, only two calls (one for each of the date tags) are made to each of setMode and setLength. If I clear the mode and length fields when I call doEndTag, then all occurrences of the date tags except the first take on their default attributes, which is not the behavior I want. Are both Tomcat and Resin within spec in implementing different behaviors here? If so, what is the correct point in the lifecycle to reset attribute values in a TagSupport object? Gary McGath http://www.mcgath.com/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Getting SSL info using mod_jk
Hi, I've just joined this list and see from previous messages that there are a lot of people having trouble getting mod_jk to pass SSL certificate info to Tomcat. I can't get this to work either (trying using Apache 1.3, Tomcat 4.1.18, mod_jk and either the AJP13 or Coyote JK2 connectors). I've tried everything I can find on various web pages but no joy. Has anyone got this working correctly? (i.e. can do req.getAttribute(javax.servlet.request.X509Certificate) and get something other than null). Like a previous poster I can get the javax.servlet.request.cipher_suite attribute but nothing else. Thanks for any info, Martin. -- Martin Craig [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Tomcat /examples app. won't start from Web ApplicationManager
Hello, How can I restart, with success, the Tomcat/4.1.12. Example applications? It simply will not start by clicking the start session in the WAM. The url for that is: http://localhost:8080/manager/html/start?path=/examples Is there another way? Thanks, DRH -- DENNIS R. HASCH Smithsonian Institution, National Museum of Natural History (NMNH) Research Collections, Informatics Office [EMAIL PROTECTED] // 202.357.4267 - - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Help sought: regular expressions and isapi_redirector2.dll
Version 2.0.2 and later of isapi_redirector2.dll is supposed to allow PCRE 3.9-type regular expressions in uri maps in workers2.properties so that you can use more than just an asterisk for pattern matching. Has anyone gotten this to work? I've spent a dozen or more hours trying different combinations of regex's without success. Any help is appreciated!
testing Tomcat on SMP box
hi! For few days I run performance tests on 4 (Intel's) processor box. One of them is servlet running on Tomcat - this is just creating MD5 digest of some short text about 1000 times and some loop to glue these digests with some HTML tags and no other activity. I run tests with httperf or apachebench (ab). Problem is, I cannot reach 100% of CPUs usage. On top it seems, test take about 50-80% (it depends on concurrency rate). When I run two Tomcats as separate processes, I could reach about 90% (but still not 100%). In opposite - when I run PHP script with near code (creating MD5 of the same text, and loop with HTML pieces) on Apache - I reach 100% of CPUs usage at about 80 req/s without any problems. May be, I'm not aware of some conf issues, but I try to influence on usage by changing number of allowed Tomcat's HttpProcessors - it seems, that with increasing number of threads usage of machine decreases (of course performance also) And here few questions: - anybody knows about complications with threads on SMP Intel based machines with Tomcat (or JVM itself maybe)? - or maybe I misconfigured something in Tomcat, what prevents me from reaching 100% usage of system/CPUs Best regards and thanks for any advices Remigiusz - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Error 500
Sometime appears this exception: HTTP Status 500 - Internal Server Error type Exception report message Internal Server Error description The server encountered an internal error (Internal Server Error) that prevented it from fulfilling this request. --- Has anyone any comments about this exception. Thanks again.
RE: Error 500
Without further informations from your log files nobody can help you. it's also a good idea to say a bit mor about your environment. -Original Message- From: Lindomar [mailto:[EMAIL PROTECTED]] Sent: Monday, February 03, 2003 3:10 PM To: Tomcat Users List Subject: Error 500 HTTP Status 500 - Internal Server Error message Internal Server Error description The server encountered an internal error (Internal Server Error) that prevented it from fulfilling this request. --- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Error 500
Am Montag, 3. Februar 2003 15:09 schrieb Lindomar: Sometime appears this exception: HTTP Status 500 - Internal Server Error --- - type Exception report message Internal Server Error description The server encountered an internal error (Internal Server Error) that prevented it from fulfilling this request. --- Has anyone any comments about this exception. Tomcat has. In it's logfile catalina.out. With kind regards / mit freundlichem Gruß Holger Klawitter -- Holger Klawitter http://www.klawitter.de [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: JNDI DBCP resources, another problem.
Veniamin Fichin wrote: Hello list. I fought with that for about two weeks recently and had done it, so my JNDIRealm works. But! Now servlet that just gets a connection from JNDI resource and tries to query database is broken! Situation is that: Correction: not JNDIRealm, but DataSourceRealm. Sorry for inconvenience. ... GlobalNamingResource Resource ... / ResourceParams ... /ResourceParams /GlobalNamingResource ... Context ResourceLink ... / Realm ... / /Context ... works with JNDIRealm, but not with common servlet getting resource from JNDI, and ... Context Resource ... / ResourceParams ... /ResourceParams Realm ... / /Context ... works with servlet but not with JNDIRealm! It's only two options to have a resource in JNDI -- define it inside GlobalNamingResource or inside Context , and each of it works separately but not simultaneously. Any advice/suggestion/RTFM link will be GREATELY appreciated because I'm really want to know what's going on behind the scene to not ask such a stupid questions again. Thanks a lot. -- Veniamin Fichin [EMAIL PROTECTED] Programmer athttp://www.rbcsoft.ru/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Error 500
There could be many reasons, please post your full error message.. Madhav -Original Message- From: Lindomar [mailto:[EMAIL PROTECTED]] Sent: Monday, February 03, 2003 3:10 PM To: Tomcat Users List Subject: Error 500 Sometime appears this exception: HTTP Status 500 - Internal Server Error type Exception report message Internal Server Error description The server encountered an internal error (Internal Server Error) that prevented it from fulfilling this request. --- Has anyone any comments about this exception. Thanks again.
Re: Conflicts between 2 lib in Tomcat 4.0.3
Put it in CATALINA_HOME/common/endorsed or common/lib. You aren't supposed to put endorsed packages such as javax.* and org.w3c.* in WEB-INF/lib. It causes all sorts of problems and violates the Sun classloading spec which Tomcat, as of 4.0.2, enforces. Jake At 10:11 AM 2/3/2003 +0100, you wrote: Hi, I'm working with TC 4.0.3. In the WEB-INF/lib directory, I've got 2 libraries : xerces.jar (I think it's an old Xerces, I didn't put myself there : someone else need it) and xercesImpl.jar (a newer version of xerces). I coded a class that need xerces2, but when I launch it (via a servlet) in my Tomcat, it throws a NoSuchMethoError cause it doesn't take the good jar ! How can I force TC to take the new librairy ? Thanx in advance - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Conflicts between 2 lib in Tomcat 4.0.3
I already tried to remove those libs from WEB-INF/lib to CATALINA_HOME/common/lib or CATALINA_HOME/lib, but all the classes in WEB-INF/classes that were coded by another developpers didn't worked any more ! Put it in CATALINA_HOME/common/endorsed or common/lib. You aren't supposed to put endorsed packages such as javax.* and org.w3c.* in WEB-INF/lib. It causes all sorts of problems and violates the Sun classloading spec which Tomcat, as of 4.0.2, enforces. Jake At 10:11 AM 2/3/2003 +0100, you wrote: Hi, I'm working with TC 4.0.3. In the WEB-INF/lib directory, I've got 2 libraries : xerces.jar (I think it's an old Xerces, I didn't put myself there : someone else need it) and xercesImpl.jar (a newer version of xerces). I coded a class that need xerces2, but when I launch it (via a servlet) in my Tomcat, it throws a NoSuchMethoError cause it doesn't take the good jar ! How can I force TC to take the new librairy ? Thanx in advance - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: JK2 for Apache 2.0.44 on Linux
There's one available on my site: http://www.johnturner.com/howto John -Original Message- From: Paul Gregoire [mailto:[EMAIL PROTECTED]] Sent: Sunday, February 02, 2003 11:22 PM To: Tomcat Users List Subject: Re: JK2 for Apache 2.0.44 on Linux That is the JK2 2.0.1 release and it does not include a build for 2.0.44 unless the 2.0.43 version works with 2.0.44. but anyhow im looking for JK2 2.0.2 - Original Message - From: Turner, John [EMAIL PROTECTED] To: 'Tomcat Users List ' [EMAIL PROTECTED] Sent: Sunday, February 02, 2003 8:09 PM Subject: RE: JK2 for Apache 2.0.44 on Linux http://jakarta.apache.org/builds/jakarta-tomcat-connectors/jk2 /release/v2.0. 1/bin/linux/i386/ John -Original Message- From: Paul Gregoire To: Tomcat Users List Sent: 2/2/03 10:05 PM Subject: JK2 for Apache 2.0.44 on Linux Does anyone here know where i can find jk2 2.0.2 for apache 2.0.44?? i am trying to get tomcat 4.1.18 running on my Redhat 8 box, but i cannot seem to get connectors build for myself. I also cannot find them on Apache's site. Thanks in advance - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --- Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.449 / Virus Database: 251 - Release Date: 1/27/2003 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[OFFTOPIC] MySQL Exception - Need Suggestions
Somewhat offtopic, I apologize if it is completely, I know there are some SMART people on this list (ass kissing always helps :) Tomcat 4.1.18 MySQL 3.22.32 MySQL Connector J 2.0.14 Trying to establish a connection from client to server, getting a MySQL Versions Older than 3.23.15 do not support transactions exception. Fine - I really don't care as I just need to build a 2 table form input application, really simple, I don't really care about transactions, so why am I getting this error through Tomcat when I try to start? Is there something I need to configure somewhere before I try to download and update MySQL? Thanks, Geoff Geoff Peters, BScFE, AIT Phone : (441) 296-9640 Applications DeveloperFax: (441) 292-1509 Logic Communications E-mail : [EMAIL PROTECTED] 12 Par-La-Ville Road WWW: http://www.logic.bm Hamilton, Bermuda HM JX - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[offtopic] Opinion - Error messages
I have been in IT for approximately 25 years and worked with Cobol, C++, Fortran, PL1, Java, and others on IBM S390, PDPs, AS400s, PCs. I believe Tomcat is a great server environment. It has a lot of strengths and is evolving rapidly. Many talented developers dedicate vast amounts of time to the project. I appreciate their efforts. In all cases, error processing and reporting could be a difficult task. I appreciate the effort that it requires. But I do believe for Tomcat to flourish, which I hope it does, it needs more attention in this area. For over a week I have been painstakingly trying to set up Server.xml with my context data. Yet, I am simply rewarded with the following non-descriptive error message. I pity people that are in a production environment with development schedules who encounter similar situations. In general, Tomcat deserves high marks. But for error processing and reporting, it deserves an F. Just my $0.02 2003-02-03 09:32:57 StandardContext[/mfnettags]: Starting 2003-02-03 09:32:57 StandardContext[/mfnettags]: Processing start(), current available=false 2003-02-03 09:32:57 StandardContext[/mfnettags]: Configuring default Resources 2003-02-03 09:32:57 StandardContext[/mfnettags]: Resources start failed: 2003-02-03 09:32:57 StandardContext[/mfnettags]: Configuring non-privileged default Loader 2003-02-03 09:32:57 StandardContext[/mfnettags]: Configuring default Manager 2003-02-03 09:32:57 StandardContext[/mfnettags]: Processing standard container startup 2003-02-03 09:32:57 StandardContext[/mfnettags]: Context startup failed due to previous errors 2003-02-03 09:32:57 StandardContext[/mfnettags]: Exception during cleanup after start failed LifecycleException: Container StandardContext[/mfnettags] has not been started at org.apache.catalina.core.StandardContext.stop(StandardContext.java:3643) at org.apache.catalina.core.StandardContext.start(StandardContext.java:3621) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1188) 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:2189) at org.apache.catalina.startup.Catalina.start(Catalina.java:512) 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) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [offtopic] Opinion - Error messages
Is this a request for help, or just a rant? Please let us know. John -Original Message- From: Jim Henderson [mailto:[EMAIL PROTECTED]] Sent: Monday, February 03, 2003 11:04 AM To: [EMAIL PROTECTED] Subject: [offtopic] Opinion - Error messages I have been in IT for approximately 25 years and worked with Cobol, C++, Fortran, PL1, Java, and others on IBM S390, PDPs, AS400s, PCs. I believe Tomcat is a great server environment. It has a lot of strengths and is evolving rapidly. Many talented developers dedicate vast amounts of time to the project. I appreciate their efforts. In all cases, error processing and reporting could be a difficult task. I appreciate the effort that it requires. But I do believe for Tomcat to flourish, which I hope it does, it needs more attention in this area. For over a week I have been painstakingly trying to set up Server.xml with my context data. Yet, I am simply rewarded with the following non-descriptive error message. I pity people that are in a production environment with development schedules who encounter similar situations. In general, Tomcat deserves high marks. But for error processing and reporting, it deserves an F. Just my $0.02 2003-02-03 09:32:57 StandardContext[/mfnettags]: Starting 2003-02-03 09:32:57 StandardContext[/mfnettags]: Processing start(), current available=false 2003-02-03 09:32:57 StandardContext[/mfnettags]: Configuring default Resources 2003-02-03 09:32:57 StandardContext[/mfnettags]: Resources start failed: 2003-02-03 09:32:57 StandardContext[/mfnettags]: Configuring non-privileged default Loader 2003-02-03 09:32:57 StandardContext[/mfnettags]: Configuring default Manager 2003-02-03 09:32:57 StandardContext[/mfnettags]: Processing standard container startup 2003-02-03 09:32:57 StandardContext[/mfnettags]: Context startup failed due to previous errors 2003-02-03 09:32:57 StandardContext[/mfnettags]: Exception during cleanup after start failed LifecycleException: Container StandardContext[/mfnettags] has not been started at org.apache.catalina.core.StandardContext.stop(StandardContext. java:3643) at org.apache.catalina.core.StandardContext.start(StandardContext .java:3621) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1188) 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.j ava:2189) at org.apache.catalina.startup.Catalina.start(Catalina.java:512) 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(NativeMethodAccess orImpl.java:39 ) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMeth odAccessorImpl .java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:203) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Conflicts between 2 lib in Tomcat 4.0.3
hmm Seems to me that they might have been accessing the Xerces implementation classes rather than just the public interfaces. If they were doign things like loading classes dynamically such as using Class.forName(com.mypackage.MyClass) you would get exactly this problem because that will only look for the class in the current classloader instead of looking at all available classloaders. If you can post a stacktrace, we might be able to make that determination. Without a full stack trace, no one will be able to help you much further. Also, in what environment was all this working before? A previous versions of Tomcat? If so, which version? And why not stick with that versionor make the developers fix the bad coding? Jake At 04:25 PM 2/3/2003 +0100, you wrote: I already tried to remove those libs from WEB-INF/lib to CATALINA_HOME/common/lib or CATALINA_HOME/lib, but all the classes in WEB-INF/classes that were coded by another developpers didn't worked any more ! Put it in CATALINA_HOME/common/endorsed or common/lib. You aren't supposed to put endorsed packages such as javax.* and org.w3c.* in WEB-INF/lib. It causes all sorts of problems and violates the Sun classloading spec which Tomcat, as of 4.0.2, enforces. Jake At 10:11 AM 2/3/2003 +0100, you wrote: Hi, I'm working with TC 4.0.3. In the WEB-INF/lib directory, I've got 2 libraries : xerces.jar (I think it's an old Xerces, I didn't put myself there : someone else need it) and xercesImpl.jar (a newer version of xerces). I coded a class that need xerces2, but when I launch it (via a servlet) in my Tomcat, it throws a NoSuchMethoError cause it doesn't take the good jar ! How can I force TC to take the new librairy ? Thanx in advance - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
General Question about JSP Database
I have a general question about creating a website with JSP and wanting to connect to a mySQL database to store form data. Which driver would I need to do this? If more than one option, which would be the best choice? Are these decisions affected by what Tomcat will or will not allow? Thanks! Denise Mangano Help Desk Analyst Complus Data Innovations, Inc. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [offtopic] Opinion - Error messages
Jim Henderson wrote: I have been in IT for approximately 25 years Scary ;-) and worked with Cobol, C++, Fortran, PL1, Java, and others on IBM S390, PDPs, AS400s, PCs. No Lisp? That's the problem! I believe Tomcat is a great server environment. It has a lot of strengths and is evolving rapidly. Many talented developers dedicate vast amounts of time to the project. I appreciate their efforts. In all cases, error processing and reporting could be a difficult task. I appreciate the effort that it requires. But I do believe for Tomcat to flourish, which I hope it does, it needs more attention in this area. For over a week I have been painstakingly trying to set up Server.xml with my context data. Yet, I am simply rewarded with the following non-descriptive error message. I pity people that are in a production environment with development schedules who encounter similar situations. In general, Tomcat deserves high marks. But for error processing and reporting, it deserves an F. You deverse an F also for the kind of information you just posted ;-) Please tell us more what you are trying to do. Which platform?, Which Tomcat version (I guess its 4.1.x...but I don't like guessing), What your app is trying to do and most importantly, add your web.xml file. Is the Tomcat example working? Have you try to increase the logging level? Then we will revise your note and maybe help you and give a C ;-) -- Jeanfrancois ---see--- (http://jakarta.apache.org/site/mail.html) :-) Just my $0.02 2003-02-03 09:32:57 StandardContext[/mfnettags]: Starting 2003-02-03 09:32:57 StandardContext[/mfnettags]: Processing start(), current available=false 2003-02-03 09:32:57 StandardContext[/mfnettags]: Configuring default Resources 2003-02-03 09:32:57 StandardContext[/mfnettags]: Resources start failed: 2003-02-03 09:32:57 StandardContext[/mfnettags]: Configuring non-privileged default Loader 2003-02-03 09:32:57 StandardContext[/mfnettags]: Configuring default Manager 2003-02-03 09:32:57 StandardContext[/mfnettags]: Processing standard container startup 2003-02-03 09:32:57 StandardContext[/mfnettags]: Context startup failed due to previous errors 2003-02-03 09:32:57 StandardContext[/mfnettags]: Exception during cleanup after start failed LifecycleException: Container StandardContext[/mfnettags] has not been started at org.apache.catalina.core.StandardContext.stop(StandardContext.java:3643) at org.apache.catalina.core.StandardContext.start(StandardContext.java:3621) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1188) 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:2189) at org.apache.catalina.startup.Catalina.start(Catalina.java:512) 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) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [offtopic] Opinion - Error messages
I take help! :) (I am just frustrated and the post was intended to be positive criticism.) My app works just fine (minus the mail function) IF I do not add my Context info to server.xml. My context data is larger (includes Valve, Logger, Resource, ResourceParms, and Environment items) but I have trimmed it down to the following that is inserted in the 4.1.18 distribution after the examples context and before /Host. And it is strange, if I run the app then add the server.xml entry without clearing the work subdirectory and without redeploying, the error does not occur. This was a very confusing issue, it seemed to work sometimes and sometimes not. But if I add my Context tag to the server.xml, then deploy am WAR file, the error occurs. It is the following trimmed Context that caused the error. Context path=/mfnettags docBase=mfnettags reloadable=false debug=5 swallowOutput=false useNaming=true /Context Thanks! -Original Message- From: Turner, John [mailto:[EMAIL PROTECTED]] Sent: Monday, February 03, 2003 10:08 AM To: 'Tomcat Users List' Subject: RE: [offtopic] Opinion - Error messages Is this a request for help, or just a rant? Please let us know. John -Original Message- From: Jim Henderson [mailto:[EMAIL PROTECTED]] Sent: Monday, February 03, 2003 11:04 AM To: [EMAIL PROTECTED] Subject: [offtopic] Opinion - Error messages I have been in IT for approximately 25 years and worked with Cobol, C++, Fortran, PL1, Java, and others on IBM S390, PDPs, AS400s, PCs. I believe Tomcat is a great server environment. It has a lot of strengths and is evolving rapidly. Many talented developers dedicate vast amounts of time to the project. I appreciate their efforts. In all cases, error processing and reporting could be a difficult task. I appreciate the effort that it requires. But I do believe for Tomcat to flourish, which I hope it does, it needs more attention in this area. For over a week I have been painstakingly trying to set up Server.xml with my context data. Yet, I am simply rewarded with the following non-descriptive error message. I pity people that are in a production environment with development schedules who encounter similar situations. In general, Tomcat deserves high marks. But for error processing and reporting, it deserves an F. Just my $0.02 2003-02-03 09:32:57 StandardContext[/mfnettags]: Starting 2003-02-03 09:32:57 StandardContext[/mfnettags]: Processing start(), current available=false 2003-02-03 09:32:57 StandardContext[/mfnettags]: Configuring default Resources 2003-02-03 09:32:57 StandardContext[/mfnettags]: Resources start failed: 2003-02-03 09:32:57 StandardContext[/mfnettags]: Configuring non-privileged default Loader 2003-02-03 09:32:57 StandardContext[/mfnettags]: Configuring default Manager 2003-02-03 09:32:57 StandardContext[/mfnettags]: Processing standard container startup 2003-02-03 09:32:57 StandardContext[/mfnettags]: Context startup failed due to previous errors 2003-02-03 09:32:57 StandardContext[/mfnettags]: Exception during cleanup after start failed LifecycleException: Container StandardContext[/mfnettags] has not been started at org.apache.catalina.core.StandardContext.stop(StandardContext. java:3643) at org.apache.catalina.core.StandardContext.start(StandardContext .java:3621) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1188) 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.j ava:2189) at org.apache.catalina.startup.Catalina.start(Catalina.java:512) 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(NativeMethodAccess orImpl.java:39 ) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMeth odAccessorImpl .java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:203) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands,
tomcat NT service memory
Hi, I am experiencing problems with Tomcat because of default JVM memory size and want to let it use more memory. The only way i know is to change/add environmental variable for the service in the registry (CATALINA_OPTS=-Xmx256m)... However, i am not sure if this is the best/correct way. Could anyone either confirm that this is the correct approach, or give me suggestions. Thanks, Vlad Vladimer Shioshvili QRC Division of Macro International Inc. 7315 Wisconsin Avenue, Suite 400W Bethesda, MD 20814 Phone: (301) 657 3077 ext. 155 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: General Question about JSP Database
Hi - You'll want a JDBC Type 4 driver (Type 4 means 100% Java, not something like an ODBC/JDBC bridge or hybrid). For MySQL, you'll probably want to check out Connector/J: http://www.mysql.com/products/connector-j/ This driver was previously MM.MySQL, which was the typical open source driver used. John -Original Message- From: Denise Mangano [mailto:[EMAIL PROTECTED]] Sent: Monday, February 03, 2003 11:28 AM To: 'Tomcat Users List' Subject: General Question about JSP Database I have a general question about creating a website with JSP and wanting to connect to a mySQL database to store form data. Which driver would I need to do this? If more than one option, which would be the best choice? Are these decisions affected by what Tomcat will or will not allow? Thanks! Denise Mangano Help Desk Analyst Complus Data Innovations, Inc. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Conflicts between 2 lib in Tomcat 4.0.3
Or maybehe is using the old Xerces (1.4.4) with the new Xerces(2.x). They have make huge changes between the 2 versions and backward compatibility is no longer supported (Xerces 1.4.4 doesn't fully supports JAXP, Xerces 2.x does). They probably use a public API, but not the JAXP one. You will have to stick with that version or ask other app to update to Xerces 2.x :-( Also, the classloader will not properly load the second jar since it doesn't load a class that is in memory. Since your 2 xerces share some base classes, that's probably why it doesn't work. -- Jeanfrancois Jacob Kjome wrote: hmm Seems to me that they might have been accessing the Xerces implementation classes rather than just the public interfaces. If they were doign things like loading classes dynamically such as using Class.forName(com.mypackage.MyClass) you would get exactly this problem because that will only look for the class in the current classloader instead of looking at all available classloaders. If you can post a stacktrace, we might be able to make that determination. Without a full stack trace, no one will be able to help you much further. Also, in what environment was all this working before? A previous versions of Tomcat? If so, which version? And why not stick with that versionor make the developers fix the bad coding? Jake At 04:25 PM 2/3/2003 +0100, you wrote: I already tried to remove those libs from WEB-INF/lib to CATALINA_HOME/common/lib or CATALINA_HOME/lib, but all the classes in WEB-INF/classes that were coded by another developpers didn't worked any more ! Put it in CATALINA_HOME/common/endorsed or common/lib. You aren't supposed to put endorsed packages such as javax.* and org.w3c.* in WEB-INF/lib. It causes all sorts of problems and violates the Sun classloading spec which Tomcat, as of 4.0.2, enforces. Jake At 10:11 AM 2/3/2003 +0100, you wrote: Hi, I'm working with TC 4.0.3. In the WEB-INF/lib directory, I've got 2 libraries : xerces.jar (I think it's an old Xerces, I didn't put myself there : someone else need it) and xercesImpl.jar (a newer version of xerces). I coded a class that need xerces2, but when I launch it (via a servlet) in my Tomcat, it throws a NoSuchMethoError cause it doesn't take the good jar ! How can I force TC to take the new librairy ? Thanx in advance - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: General Question about JSP Database
Thanks John!! I was just reading up on that driver, and though it is what I need, but I just wanted to get an outside opinion :) Denise Mangano Help Desk Analyst Complus Data Innovations, Inc. -Original Message- From: Turner, John [mailto:[EMAIL PROTECTED]] Sent: Monday, February 03, 2003 11:35 AM To: 'Tomcat Users List' Subject: RE: General Question about JSP Database Hi - You'll want a JDBC Type 4 driver (Type 4 means 100% Java, not something like an ODBC/JDBC bridge or hybrid). For MySQL, you'll probably want to check out Connector/J: http://www.mysql.com/products/connector-j/ This driver was previously MM.MySQL, which was the typical open source driver used. John -Original Message- From: Denise Mangano [mailto:[EMAIL PROTECTED]] Sent: Monday, February 03, 2003 11:28 AM To: 'Tomcat Users List' Subject: General Question about JSP Database I have a general question about creating a website with JSP and wanting to connect to a mySQL database to store form data. Which driver would I need to do this? If more than one option, which would be the best choice? Are these decisions affected by what Tomcat will or will not allow? Thanks! Denise Mangano Help Desk Analyst Complus Data Innovations, Inc. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: JK2 for Apache 2.0.44 on Linux
From what ive seen on this list you are a great help to people trying get tomcat and apache working together, for that thanks. But ive also noticed that you are mostly windows centric, so im wondering where you found this jk2 2.0.2 lib for linux?? Maybe youre just better at google'ing than i am :) - Original Message - From: Turner, John [EMAIL PROTECTED] To: 'Tomcat Users List' [EMAIL PROTECTED] Sent: Monday, February 03, 2003 7:46 AM Subject: RE: JK2 for Apache 2.0.44 on Linux There's one available on my site: http://www.johnturner.com/howto John -Original Message- From: Paul Gregoire [mailto:[EMAIL PROTECTED]] Sent: Sunday, February 02, 2003 11:22 PM To: Tomcat Users List Subject: Re: JK2 for Apache 2.0.44 on Linux That is the JK2 2.0.1 release and it does not include a build for 2.0.44 unless the 2.0.43 version works with 2.0.44. but anyhow im looking for JK2 2.0.2 - Original Message - From: Turner, John [EMAIL PROTECTED] To: 'Tomcat Users List ' [EMAIL PROTECTED] Sent: Sunday, February 02, 2003 8:09 PM Subject: RE: JK2 for Apache 2.0.44 on Linux http://jakarta.apache.org/builds/jakarta-tomcat-connectors/jk2 /release/v2.0. 1/bin/linux/i386/ John -Original Message- From: Paul Gregoire To: Tomcat Users List Sent: 2/2/03 10:05 PM Subject: JK2 for Apache 2.0.44 on Linux Does anyone here know where i can find jk2 2.0.2 for apache 2.0.44?? i am trying to get tomcat 4.1.18 running on my Redhat 8 box, but i cannot seem to get connectors build for myself. I also cannot find them on Apache's site. Thanks in advance - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --- Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.449 / Virus Database: 251 - Release Date: 1/27/2003 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Invalid JSP Error When Trying to View Source
Can anyone help me rectify an invalid JSP file error? I am getting an invalid JSP error when trying to view the JSP example source code through my browser. After starting Tomcat, I am navigating from the Tomcat welcome/index.jsp page through to view source of any of the jsp examples( e.g. http://localhost:8080/examples/jsp/source.jsp?/jsp/num/numguess.jsp). I have installed Tomcat 4.1.18 binaries on win2k. I have JAVA_HOME set to my jdk 1.3.1_06 directory, and have NOT set any other environment variables. The error comes back on a web page titled HTTP Status 500 - and the exeption contents are: org.apache.jasper.JasperException: Invalid JSP file /jsp/num/numguess.jsp at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.ja va:248) at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:295) at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:241) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Applica tionFilterChain.java:247) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilt erChain.java:193) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValv e.java:260) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.i nvokeNext(StandardPipeline.java:643) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:4 80) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValv e.java:191) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.i nvokeNext(StandardPipeline.java:643) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(Authenticator Base.java:493) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.i nvokeNext(StandardPipeline.java:641) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:4 80) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:241 5) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java :180) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.i nvokeNext(StandardPipeline.java:643) at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherVa lve.java:170) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.i nvokeNext(StandardPipeline.java:641) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java :172) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.i nvokeNext(StandardPipeline.java:641) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:4 80) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve. java:174) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.i nvokeNext(StandardPipeline.java:643) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:4 80) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter.java:223) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:43 2) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processC onnection(Http11Protocol.java:386) at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:53 4) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool .java:530) at java.lang.Thread.run(Thread.java:479) root cause javax.servlet.ServletException: Invalid JSP file /jsp/num/numguess.jsp at org.apache.jasper.runtime.PageContextImpl.handlePageException(PageContex tImpl.java:530) at org.apache.jsp.source_jsp._jspService(source_jsp.java:66) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:137) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.ja va:204) at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:295) at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:241) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Applica tionFilterChain.java:247) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilt erChain.java:193) at
RE: JK2 for Apache 2.0.44 on Linux
I built it this morning. I use both operating systems (75% Linux, 25% Windows). Red Hat for servers at work, but I'm required to use MS Outlook at work on my desktop, which means Windows 2000 (lone Linux guy in a vast sea of Microsofties, LOL). Thank god for Cygwin's XWin client and XFree86. I have a Windows XP machine and a couple RH 7.x machines at home. I don't have access to RH 8, though, so YMMV on that .so file. My 7.2 boxes are doing just fine, and at the moment I see no reason to upgrade to 8 any time in the future, so 7.2 it is. John -Original Message- From: Paul Gregoire [mailto:[EMAIL PROTECTED]] Sent: Monday, February 03, 2003 11:50 AM To: Tomcat Users List Subject: Re: JK2 for Apache 2.0.44 on Linux From what ive seen on this list you are a great help to people trying get tomcat and apache working together, for that thanks. But ive also noticed that you are mostly windows centric, so im wondering where you found this jk2 2.0.2 lib for linux?? Maybe youre just better at google'ing than i am :) - Original Message - From: Turner, John [EMAIL PROTECTED] To: 'Tomcat Users List' [EMAIL PROTECTED] Sent: Monday, February 03, 2003 7:46 AM Subject: RE: JK2 for Apache 2.0.44 on Linux There's one available on my site: http://www.johnturner.com/howto John -Original Message- From: Paul Gregoire [mailto:[EMAIL PROTECTED]] Sent: Sunday, February 02, 2003 11:22 PM To: Tomcat Users List Subject: Re: JK2 for Apache 2.0.44 on Linux That is the JK2 2.0.1 release and it does not include a build for 2.0.44 unless the 2.0.43 version works with 2.0.44. but anyhow im looking for JK2 2.0.2 - Original Message - From: Turner, John [EMAIL PROTECTED] To: 'Tomcat Users List ' [EMAIL PROTECTED] Sent: Sunday, February 02, 2003 8:09 PM Subject: RE: JK2 for Apache 2.0.44 on Linux http://jakarta.apache.org/builds/jakarta-tomcat-connectors/jk2 /release/v2.0. 1/bin/linux/i386/ John -Original Message- From: Paul Gregoire To: Tomcat Users List Sent: 2/2/03 10:05 PM Subject: JK2 for Apache 2.0.44 on Linux Does anyone here know where i can find jk2 2.0.2 for apache 2.0.44?? i am trying to get tomcat 4.1.18 running on my Redhat 8 box, but i cannot seem to get connectors build for myself. I also cannot find them on Apache's site. Thanks in advance - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --- Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.449 / Virus Database: 251 - Release Date: 1/27/2003 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Installing tomcat 4.4.1.18 on RH8.0
I already have SDK1.4 installed and setup so I downloaded the binary tomcat4-4.1.18-full.1jpp.noarch.rpm from the tomcat website and installed it as root (on RedHat 8.0) using, rpm -ivh tomcat4-4.1.18-full.1jpp.noarch.rpm Appears to install fine into /var/tomcat4 giving warnings about I need to alter my config files now. I am new to tomcat so I checked the RUNNING.TXT file and after reading it I am none the wiser! I have no /var/tomcat4/bin/startup.sh or /var/tomcat4/bin/shutdown.sh like it says, althought I can start and stop the server using the scripts in /etc/rc.d/init.d I managed to fiddle about (after reading the logs) and got something running, but when I connect to http://localhost:8080 I get an error about no context manager. Are there any comprehensive docs on how to setup tomcat under linux, or can someone provide with a step by step idiot guide? Thanks, Darren - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: jsp:useBean error
Nope, there is nothing special you have to do in JBuilder, it should take care of everything for you. But you do have to put your classfiles in a package, and then it will work. ie, your .java files should have a package statement in the top of it. Filip -Original Message- From: Steve R Burrus [mailto:[EMAIL PROTECTED]] Sent: Friday, January 31, 2003 10:29 PM To: Tomcat Users List Subject: RE: jsp:useBean error Hi Flip, it seems like I really don't get back to posting in this newsgroup of ours' before midnite :), but anyway, here is the particular war file which you went out yer way to request of me!! I think that there is something to the solution which I have received from at least 2 other people to put the class in question into some kind of a package!! The only thing is that, as I have already stated, I am trying/attempting to work in the JBuilder 8 Enterprise Trial app., and I am just wondering if there is something special that I have to do in that app. to do the job of packaging up the class, if you are yourself some kind of a semi-expert in using JBuilder I don't know. Well anyway, here is the war file attached to this that you wanted to see. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Installing tomcat 4.4.1.18 on RH8.0
the easiest thing for you to do is to 1. download jakarta-tomcat-4.1.18-blablabla.zip 2. Make sure you have JDK installed and that JAVA_HOME is set and your PATH is set export JAVA_HOME=/usr/local/jdk1.4.1 export PATH=$JAVA_HOME/bin:$PATH 3. Unzip the zip :) jar xvf jakarta-tomcat-4.1.18-blablabla.zip 4. cd jakarta-tomcat-4.1.18-blablabla/bin 5. ./catalina.sh badabim badabom, you should be good to go Filip -Original Message- From: Darren Edmonds [mailto:[EMAIL PROTECTED]] Sent: Monday, February 03, 2003 8:57 AM To: [EMAIL PROTECTED] Subject: Installing tomcat 4.4.1.18 on RH8.0 I already have SDK1.4 installed and setup so I downloaded the binary tomcat4-4.1.18-full.1jpp.noarch.rpm from the tomcat website and installed it as root (on RedHat 8.0) using, rpm -ivh tomcat4-4.1.18-full.1jpp.noarch.rpm Appears to install fine into /var/tomcat4 giving warnings about I need to alter my config files now. I am new to tomcat so I checked the RUNNING.TXT file and after reading it I am none the wiser! I have no /var/tomcat4/bin/startup.sh or /var/tomcat4/bin/shutdown.sh like it says, althought I can start and stop the server using the scripts in /etc/rc.d/init.d I managed to fiddle about (after reading the logs) and got something running, but when I connect to http://localhost:8080 I get an error about no context manager. Are there any comprehensive docs on how to setup tomcat under linux, or can someone provide with a step by step idiot guide? Thanks, Darren - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Problem with mod_jk, tomcat 4.1.18, apache 1.3.26, on FreeBSD 4.3
Hi, I've been unable to set up the ajp13 redirect for servlets between my apache and tomcat on freebsd, despite trying everything! The error I am getting is: Cannot load /home/y/libexec/mod_jk.so into server: /home/y/libexec/mod_jk.so: Undefined symbol ap_hook_post_config Having looked around, this is highlighted for when migrating a module from apache 1.3 to 2, but I am not running 2 here. I have tried all versions of the mod_jk.so available from the jakarta site :( I have done this before fine on both solaris and linux, but am having problems here on freebsd. I am not desperate to use tomcat 4, so if somebody has got this running with tomcat 3.3 I am happy to use that. I have to use apache 1.3.26. Manks thanks in advance, Ben - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Invalid JSP Error When Trying to View Source
http://localhost:8080/examples/jsp/num/numguess.txt Filip -Original Message- From: John Dapper [mailto:[EMAIL PROTECTED]] Sent: Monday, February 03, 2003 8:52 AM To: [EMAIL PROTECTED] Subject: Invalid JSP Error When Trying to View Source Can anyone help me rectify an invalid JSP file error? I am getting an invalid JSP error when trying to view the JSP example source code through my browser. After starting Tomcat, I am navigating from the Tomcat welcome/index.jsp page through to view source of any of the jsp examples( e.g. http://localhost:8080/examples/jsp/source.jsp?/jsp/num/numguess.jsp). I have installed Tomcat 4.1.18 binaries on win2k. I have JAVA_HOME set to my jdk 1.3.1_06 directory, and have NOT set any other environment variables. The error comes back on a web page titled HTTP Status 500 - and the exeption contents are: org.apache.jasper.JasperException: Invalid JSP file /jsp/num/numguess.jsp at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.ja va:248) at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:295) at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:241) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Applica tionFilterChain.java:247) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilt erChain.java:193) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValv e.java:260) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.i nvokeNext(StandardPipeline.java:643) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:4 80) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValv e.java:191) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.i nvokeNext(StandardPipeline.java:643) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(Authenticator Base.java:493) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.i nvokeNext(StandardPipeline.java:641) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:4 80) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:241 5) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java :180) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.i nvokeNext(StandardPipeline.java:643) at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherVa lve.java:170) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.i nvokeNext(StandardPipeline.java:641) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java :172) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.i nvokeNext(StandardPipeline.java:641) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:4 80) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve. java:174) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.i nvokeNext(StandardPipeline.java:643) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:4 80) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter.java:223) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:43 2) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processC onnection(Http11Protocol.java:386) at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:53 4) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool .java:530) at java.lang.Thread.run(Thread.java:479) root cause javax.servlet.ServletException: Invalid JSP file /jsp/num/numguess.jsp at org.apache.jasper.runtime.PageContextImpl.handlePageException(PageContex tImpl.java:530) at org.apache.jsp.source_jsp._jspService(source_jsp.java:66) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:137) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.ja va:204) at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:295) at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:241) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
RE: Installing tomcat 4.4.1.18 on RH8.0
I would change step 5 to ./startup.sh. ;) John -Original Message- From: Filip Hanik [mailto:[EMAIL PROTECTED]] Sent: Monday, February 03, 2003 12:05 PM To: Tomcat Users List Subject: RE: Installing tomcat 4.4.1.18 on RH8.0 the easiest thing for you to do is to 1. download jakarta-tomcat-4.1.18-blablabla.zip 2. Make sure you have JDK installed and that JAVA_HOME is set and your PATH is set export JAVA_HOME=/usr/local/jdk1.4.1 export PATH=$JAVA_HOME/bin:$PATH 3. Unzip the zip :) jar xvf jakarta-tomcat-4.1.18-blablabla.zip 4. cd jakarta-tomcat-4.1.18-blablabla/bin 5. ./catalina.sh badabim badabom, you should be good to go Filip -Original Message- From: Darren Edmonds [mailto:[EMAIL PROTECTED]] Sent: Monday, February 03, 2003 8:57 AM To: [EMAIL PROTECTED] Subject: Installing tomcat 4.4.1.18 on RH8.0 I already have SDK1.4 installed and setup so I downloaded the binary tomcat4-4.1.18-full.1jpp.noarch.rpm from the tomcat website and installed it as root (on RedHat 8.0) using, rpm -ivh tomcat4-4.1.18-full.1jpp.noarch.rpm Appears to install fine into /var/tomcat4 giving warnings about I need to alter my config files now. I am new to tomcat so I checked the RUNNING.TXT file and after reading it I am none the wiser! I have no /var/tomcat4/bin/startup.sh or /var/tomcat4/bin/shutdown.sh like it says, althought I can start and stop the server using the scripts in /etc/rc.d/init.d I managed to fiddle about (after reading the logs) and got something running, but when I connect to http://localhost:8080 I get an error about no context manager. Are there any comprehensive docs on how to setup tomcat under linux, or can someone provide with a step by step idiot guide? Thanks, Darren - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Problem with mod_jk, tomcat 4.1.18, apache 1.3.26, on FreeBSD 4.3
Are you comfortable with rolling your own connector? It's been years since I messed with FreeBSD, but assuming that you have a sane dev environment, compiling the .so is pretty straight-forward. John -Original Message- From: Benjamin Hart [mailto:[EMAIL PROTECTED]] Sent: Monday, February 03, 2003 12:03 PM To: Tomcat Users List Subject: Problem with mod_jk, tomcat 4.1.18, apache 1.3.26, on FreeBSD 4.3 Hi, I've been unable to set up the ajp13 redirect for servlets between my apache and tomcat on freebsd, despite trying everything! The error I am getting is: Cannot load /home/y/libexec/mod_jk.so into server: /home/y/libexec/mod_jk.so: Undefined symbol ap_hook_post_config Having looked around, this is highlighted for when migrating a module from apache 1.3 to 2, but I am not running 2 here. I have tried all versions of the mod_jk.so available from the jakarta site :( I have done this before fine on both solaris and linux, but am having problems here on freebsd. I am not desperate to use tomcat 4, so if somebody has got this running with tomcat 3.3 I am happy to use that. I have to use apache 1.3.26. Manks thanks in advance, Ben - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Installing tomcat 4.4.1.18 on RH8.0
Is your JAVA_HOME environment variable setup? What is the value of CATALINA_HOME after you login? You can check my RH HOWTO if you like, but it doesn't use the RPMs. Just ignore the sections on building Apache and installing a connector, and check out the sections on installing the JDK and installing Tomcat. http://www.johnturner.com/howto John -Original Message- From: Darren Edmonds [mailto:[EMAIL PROTECTED]] Sent: Monday, February 03, 2003 11:57 AM To: [EMAIL PROTECTED] Subject: Installing tomcat 4.4.1.18 on RH8.0 I already have SDK1.4 installed and setup so I downloaded the binary tomcat4-4.1.18-full.1jpp.noarch.rpm from the tomcat website and installed it as root (on RedHat 8.0) using, rpm -ivh tomcat4-4.1.18-full.1jpp.noarch.rpm Appears to install fine into /var/tomcat4 giving warnings about I need to alter my config files now. I am new to tomcat so I checked the RUNNING.TXT file and after reading it I am none the wiser! I have no /var/tomcat4/bin/startup.sh or /var/tomcat4/bin/shutdown.sh like it says, althought I can start and stop the server using the scripts in /etc/rc.d/init.d I managed to fiddle about (after reading the logs) and got something running, but when I connect to http://localhost:8080 I get an error about no context manager. Are there any comprehensive docs on how to setup tomcat under linux, or can someone provide with a step by step idiot guide? Thanks, Darren - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: tomcat NT service memory
I had to bump up the default memory size as well, and didn't get consistent
results from CATALINA_OPTS (for example, which user was used to start the
service, etc), so I changed wrapper.properties, and hard-coded the memory
stuff in. Example:
snippet
wrapper.cmd_line=$(wrapper.javabin) -Xrs -Xms128m -Xmx256m {remainder of
default line}
/snippet
I used jk_service_nt to create the service because that was available when
we first started using TC. Even though I have upgraded, I still use the
same service, etc, not what comes as part of the newer installation routine.
Not sure if the newer routine still uses wrapper.properties or not...
John
-Original Message-
From: Vladimer Shioshvili [mailto:[EMAIL PROTECTED]]
Sent: Monday, February 03, 2003 11:34 AM
To: Tomcat Users List
Subject: tomcat NT service memory
Hi,
I am experiencing problems with Tomcat because of default JVM memory size
and want to let it use more memory. The only way i know is to change/add
environmental variable for the service in the registry
(CATALINA_OPTS=-Xmx256m)... However, i am not sure if this is the
best/correct way. Could anyone either confirm that this is the correct
approach, or give me suggestions.
Thanks,
Vlad
Vladimer Shioshvili
QRC Division of Macro International Inc.
7315 Wisconsin Avenue, Suite 400W
Bethesda, MD 20814
Phone: (301) 657 3077 ext. 155
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: Installing tomcat 4.4.1.18 on RH8.0
I would change step 5 to ./startup.sh. ;) he, he, he :)) actually, what I meant was ./catalina.sh run that way it won't launch a process outside your shell :) Filip -Original Message- From: Turner, John [mailto:[EMAIL PROTECTED]] Sent: Monday, February 03, 2003 9:08 AM To: 'Tomcat Users List' Subject: RE: Installing tomcat 4.4.1.18 on RH8.0 I would change step 5 to ./startup.sh. ;) John -Original Message- From: Filip Hanik [mailto:[EMAIL PROTECTED]] Sent: Monday, February 03, 2003 12:05 PM To: Tomcat Users List Subject: RE: Installing tomcat 4.4.1.18 on RH8.0 the easiest thing for you to do is to 1. download jakarta-tomcat-4.1.18-blablabla.zip 2. Make sure you have JDK installed and that JAVA_HOME is set and your PATH is set export JAVA_HOME=/usr/local/jdk1.4.1 export PATH=$JAVA_HOME/bin:$PATH 3. Unzip the zip :) jar xvf jakarta-tomcat-4.1.18-blablabla.zip 4. cd jakarta-tomcat-4.1.18-blablabla/bin 5. ./catalina.sh badabim badabom, you should be good to go Filip -Original Message- From: Darren Edmonds [mailto:[EMAIL PROTECTED]] Sent: Monday, February 03, 2003 8:57 AM To: [EMAIL PROTECTED] Subject: Installing tomcat 4.4.1.18 on RH8.0 I already have SDK1.4 installed and setup so I downloaded the binary tomcat4-4.1.18-full.1jpp.noarch.rpm from the tomcat website and installed it as root (on RedHat 8.0) using, rpm -ivh tomcat4-4.1.18-full.1jpp.noarch.rpm Appears to install fine into /var/tomcat4 giving warnings about I need to alter my config files now. I am new to tomcat so I checked the RUNNING.TXT file and after reading it I am none the wiser! I have no /var/tomcat4/bin/startup.sh or /var/tomcat4/bin/shutdown.sh like it says, althought I can start and stop the server using the scripts in /etc/rc.d/init.d I managed to fiddle about (after reading the logs) and got something running, but when I connect to http://localhost:8080 I get an error about no context manager. Are there any comprehensive docs on how to setup tomcat under linux, or can someone provide with a step by step idiot guide? Thanks, Darren - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Problem with mod_jk, tomcat 4.1.18, apache 1.3.26, on FreeBSD 4.3
I did try doing this as well, but ran in to problems with the linux emulation libraries (I think, new to freebsd). Having followed the instructions to make a diy mod_kj.so, this is the error I got: Cannot load /home/y/libexec/mod_jk.so into server: /home/y/libexec/mod_jk.so: Undefined symbol jk_set_log_format Admittedly, I haven't hunted round very much for the causes of this error yet. One thing that dissuaded me from doing so was the difference in the file sizes, in case something was missing or had not compiled correctly: the d'loaded ones were ~370kb, and mine was ~70k. Cheers, Ben -Original Message- From: Turner, John [mailto:[EMAIL PROTECTED]] Sent: Monday, February 03, 2003 5:09 PM To: 'Tomcat Users List' Subject: RE: Problem with mod_jk, tomcat 4.1.18, apache 1.3.26, on FreeBSD 4.3 Are you comfortable with rolling your own connector? It's been years since I messed with FreeBSD, but assuming that you have a sane dev environment, compiling the .so is pretty straight-forward. John -Original Message- From: Benjamin Hart [mailto:[EMAIL PROTECTED]] Sent: Monday, February 03, 2003 12:03 PM To: Tomcat Users List Subject: Problem with mod_jk, tomcat 4.1.18, apache 1.3.26, on FreeBSD 4.3 Hi, I've been unable to set up the ajp13 redirect for servlets between my apache and tomcat on freebsd, despite trying everything! The error I am getting is: Cannot load /home/y/libexec/mod_jk.so into server: /home/y/libexec/mod_jk.so: Undefined symbol ap_hook_post_config Having looked around, this is highlighted for when migrating a module from apache 1.3 to 2, but I am not running 2 here. I have tried all versions of the mod_jk.so available from the jakarta site :( I have done this before fine on both solaris and linux, but am having problems here on freebsd. I am not desperate to use tomcat 4, so if somebody has got this running with tomcat 3.3 I am happy to use that. I have to use apache 1.3.26. Manks thanks in advance, Ben - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Encrypt tomcat-users.xml
Hi, Do you know any way to encrypt the Tomcat users file called tomcat-users.xml or another way to prevet the hacking of users file? Thank you Aleix Vergés - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Custom tag life cycle
On Mon, 3 Feb 2003, Gary McGath wrote:
Date: Mon, 3 Feb 2003 09:13:47 -0500
From: Gary McGath [EMAIL PROTECTED]
Reply-To: Tomcat Users List [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Custom tag life cycle
The webapp which I am developing (see http://www.timeczar.com for
details) uses a moderately complex custom tag library, and I've found
the lifecycle of a TagSupport object to be very confusing.
As I understand it, a TagSupport object may (but is not guaranteed to)
be reused for subsequent occurrences of the same tag in a JSP. This
means that attribute variables can't safely be initialized in the
constructor, because they may not get reinitialized for subsequent
occurrences of the tag. (Here I'm assuming that setter functions for
attributes simply set an instance variable.)
After some digging, I found that the recommended way to reset attribute
instance varaibles is to use the doEndTag method. This probably doesn't
work if a tag is nested within a tag of the same name, but I can live
with that.
Doing this works fine in Tomcat. However, I recently ported my webapp
to Resin and found that it doesn't work there. Here's a cut-back
excerpt from my JSP:
caltags:eventset
caltags:evtstartdate mode=date length=m/ -
caltags:evtenddate mode=date length=m/
/caltags:eventset
The class which implements eventset includes the tag body once for each
event in the set. The evtstartdate and evtenddate tags are implemented
by a class called DateTag, which extends TagSupport. Under Tomcat,
DateTag.setMode and DateTag.SetLength get called once for each tag in
each inclusion of the tag body. Under Resin, only two calls (one for
each of the date tags) are made to each of setMode and setLength. If I
clear the mode and length fields when I call doEndTag, then all
occurrences of the date tags except the first take on their default
attributes, which is not the behavior I want.
Are both Tomcat and Resin within spec in implementing different
behaviors here? If so, what is the correct point in the lifecycle to
reset attribute values in a TagSupport object?
Sounds like they are to me. The JSP page compiler has the option to
optimize out the second call to the setters, because tag instances can
only be shared if the combination of attribute values is identical (as
they are in your case above), but it's not required.
The easiest way to create tags that work portably and reliably across
containers is to *never* modify the values of the properties set via tag
attributes within the tag itself. Think of them as being readonly from
the perspective of your tag's code.
A common variation on this theme is to reset the references to null in the
release() method of the tag:
public class MyTag ... {
private String mode = null;
public void setMode(String mode) {
this.mode = mode;
}
private String length = null;
public void setLength(String length) {
this.length = length;
}
public void doStartTag() throws JspException {
... use but do not modify mode and length ...
}
public void doEndTag() throws JspException {
... use but do not modify mode and length ...
}
public void release() {
mode = null;
length = null;
}
}
which will release object references when the page is through using your
tag instance, but not modify them in between reuses.
Gary McGath http://www.mcgath.com/
Craig
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
How to determin what version of Tomcat is running?
How do you determine what version of Tomcat is running on your server? Thanks, Gary This transmission may contain information that is privileged, confidential and/or exempt from disclosure under applicable law. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or use of the information contained herein (including any reliance thereon) is STRICTLY PROHIBITED. If you received this transmission in error, please immediately contact the sender and destroy the material in its entirety, whether in electronic or hard copy format. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Installing tomcat 4.4.1.18 on RH8.0
Hmm, kind of easy when you do it like that ! I'd say the rpm versions are a little screwed up :) Thanks! Filip Hanik wrote: I would change step 5 to ./startup.sh. ;) he, he, he :)) actually, what I meant was ./catalina.sh run that way it won't launch a process outside your shell :) Filip -Original Message- From: Turner, John [mailto:[EMAIL PROTECTED]] Sent: Monday, February 03, 2003 9:08 AM To: 'Tomcat Users List' Subject: RE: Installing tomcat 4.4.1.18 on RH8.0 I would change step 5 to ./startup.sh. ;) John -Original Message- From: Filip Hanik [mailto:[EMAIL PROTECTED]] Sent: Monday, February 03, 2003 12:05 PM To: Tomcat Users List Subject: RE: Installing tomcat 4.4.1.18 on RH8.0 the easiest thing for you to do is to 1. download jakarta-tomcat-4.1.18-blablabla.zip 2. Make sure you have JDK installed and that JAVA_HOME is set and your PATH is set export JAVA_HOME=/usr/local/jdk1.4.1 export PATH=$JAVA_HOME/bin:$PATH 3. Unzip the zip :) jar xvf jakarta-tomcat-4.1.18-blablabla.zip 4. cd jakarta-tomcat-4.1.18-blablabla/bin 5. ./catalina.sh badabim badabom, you should be good to go Filip -Original Message- From: Darren Edmonds [mailto:[EMAIL PROTECTED]] Sent: Monday, February 03, 2003 8:57 AM To: [EMAIL PROTECTED] Subject: Installing tomcat 4.4.1.18 on RH8.0 I already have SDK1.4 installed and setup so I downloaded the binary tomcat4-4.1.18-full.1jpp.noarch.rpm from the tomcat website and installed it as root (on RedHat 8.0) using, rpm -ivh tomcat4-4.1.18-full.1jpp.noarch.rpm Appears to install fine into /var/tomcat4 giving warnings about I need to alter my config files now. I am new to tomcat so I checked the RUNNING.TXT file and after reading it I am none the wiser! I have no /var/tomcat4/bin/startup.sh or /var/tomcat4/bin/shutdown.sh like it says, althought I can start and stop the server using the scripts in /etc/rc.d/init.d I managed to fiddle about (after reading the logs) and got something running, but when I connect to http://localhost:8080 I get an error about no context manager. Are there any comprehensive docs on how to setup tomcat under linux, or can someone provide with a step by step idiot guide? Thanks, Darren - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: How to determin what version of Tomcat is running?
look in mail archives Filip -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Monday, February 03, 2003 9:28 AM To: [EMAIL PROTECTED] Subject: How to determin what version of Tomcat is running? How do you determine what version of Tomcat is running on your server? Thanks, Gary This transmission may contain information that is privileged, confidential and/or exempt from disclosure under applicable law. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or use of the information contained herein (including any reliance thereon) is STRICTLY PROHIBITED. If you received this transmission in error, please immediately contact the sender and destroy the material in its entirety, whether in electronic or hard copy format. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Custom tag life cycle
-Original Message-
From: Gary McGath [mailto:[EMAIL PROTECTED]]
Sent: Monday, February 03, 2003 9:14 AM
To: [EMAIL PROTECTED]
Subject: Custom tag life cycle
The webapp which I am developing (see http://www.timeczar.com for
details) uses a moderately complex custom tag library, and
I've found the lifecycle of a TagSupport object to be very confusing.
As I understand it, a TagSupport object may (but is not
guaranteed to) be reused for subsequent occurrences of the
same tag in a JSP. This means that attribute variables can't
safely be initialized in the constructor, because they may
not get reinitialized for subsequent occurrences of the tag.
(Here I'm assuming that setter functions for attributes
simply set an instance variable.)
After some digging, I found that the recommended way to reset
attribute instance varaibles is to use the doEndTag method.
This probably doesn't work if a tag is nested within a tag of
the same name, but I can live with that.
Actually I believe that containers would be required to use two
different instances when tags are nested. The instance can only be
reused for subsequent uses of the tag *after* the first one is closed.
But I would do the initialization in doStartTag rather than doEndTag.
The latter may not be called if an exception is thrown from within the
tag body.
Doing this works fine in Tomcat. However, I recently ported
my webapp to Resin and found that it doesn't work there.
Here's a cut-back excerpt from my JSP:
caltags:eventset
caltags:evtstartdate mode=date length=m/ -
caltags:evtenddate mode=date length=m/ /caltags:eventset
The class which implements eventset includes the tag body
once for each event in the set. The evtstartdate and
evtenddate tags are implemented by a class called DateTag,
which extends TagSupport. Under Tomcat, DateTag.setMode and
DateTag.SetLength get called once for each tag in each
inclusion of the tag body. Under Resin, only two calls (one
for each of the date tags) are made to each of setMode and
setLength. If I clear the mode and length fields when I call
doEndTag, then all occurrences of the date tags except the
first take on their default attributes, which is not the
behavior I want.
Are both Tomcat and Resin within spec in implementing
different behaviors here? If so, what is the correct point
in the lifecycle to reset attribute values in a TagSupport object?
The spec allows the container to assume that the attributes of a tag
handler will be retained across invocations, so if there are multiple
identical invocations, the setter methods do not need to be called
again.
Here's what I'd recommend:
Initialize the mode and length instance variables to null at
construction time.
Do something like this in doStartTag:
String mode = this.mode;
if (mode == null) {
mode = DEFAULT_MODE;
}
...and repeat for length. Never modify the instance variables or call
their setters yourself -- let the container manage them.
--
Tim Moore / Blackboard Inc. / Software Engineer
1899 L Street, NW / 5th Floor / Washington, DC 20036
Phone 202-463-4860 ext. 258 / Fax 202-463-4863
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Encrypt tomcat-users.xml
A better solution is to use a database to store your username/password information and configure the JDBCDatabaseRealm (instead of the default one: MemoryRealm). See http://jakarta.apache.org/tomcat/tomcat-4.1-doc/realm-howto.html -- Jeanfrancois A.VERGES wrote: Hi, Do you know any way to encrypt the Tomcat users file called tomcat-users.xml or another way to prevet the hacking of users file? Thank you Aleix Vergés - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
tomcat /apache2 / jk2 rewrites https:// requests as http://
Ok... What I want to do is have the tomcat root context accessible via https on /tomcat, running through apache2 with mod_jk2. Ok, no problem - jk2 is configured and running, the application paths in tomcat have all been changed to have /tomcat prepended. Maybe I should somehow use mod_rewrite instead, but this seems to work. I added the following in workers2.properties: [uri:/tomcat/*] info=Tomcat I can't figure out how to get this to apply only to the SSL virtual host in apache, but that's not a big deal - I can just deny access to that location from the non-SSL virtual host and allow access from the SSL host, or set up some kind of rule so that non-SSL requests get rewritten appropriately. The main problem is that if I go to https://somehost.umd.edu/tomcat, something feels the need to rewrite that to http://somehost.umd.edu:443/tomcat, which needless to say does not work. On the other hand, if there's no need to do any redirection, i.e. https://somehost.umd.edu/tomcat/index.jsp, everything works okay. What's going on here? -- Aaron Elkiss [EMAIL PROTECTED] Instructional Technologies - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Installing tomcat 4.4.1.18 on RH8.0
No, they're not screwed up, they just usually reflect the preferences/conventions of the RPM and/or distro maintainer, which may or may not coincide with yours. John -Original Message- From: Darren Edmonds [mailto:[EMAIL PROTECTED]] Sent: Monday, February 03, 2003 12:23 PM To: Tomcat Users List Subject: Re: Installing tomcat 4.4.1.18 on RH8.0 Hmm, kind of easy when you do it like that ! I'd say the rpm versions are a little screwed up :) Thanks! Filip Hanik wrote: I would change step 5 to ./startup.sh. ;) he, he, he :)) actually, what I meant was ./catalina.sh run that way it won't launch a process outside your shell :) Filip -Original Message- From: Turner, John [mailto:[EMAIL PROTECTED]] Sent: Monday, February 03, 2003 9:08 AM To: 'Tomcat Users List' Subject: RE: Installing tomcat 4.4.1.18 on RH8.0 I would change step 5 to ./startup.sh. ;) John -Original Message- From: Filip Hanik [mailto:[EMAIL PROTECTED]] Sent: Monday, February 03, 2003 12:05 PM To: Tomcat Users List Subject: RE: Installing tomcat 4.4.1.18 on RH8.0 the easiest thing for you to do is to 1. download jakarta-tomcat-4.1.18-blablabla.zip 2. Make sure you have JDK installed and that JAVA_HOME is set and your PATH is set export JAVA_HOME=/usr/local/jdk1.4.1 export PATH=$JAVA_HOME/bin:$PATH 3. Unzip the zip :) jar xvf jakarta-tomcat-4.1.18-blablabla.zip 4. cd jakarta-tomcat-4.1.18-blablabla/bin 5. ./catalina.sh badabim badabom, you should be good to go Filip -Original Message- From: Darren Edmonds [mailto:[EMAIL PROTECTED]] Sent: Monday, February 03, 2003 8:57 AM To: [EMAIL PROTECTED] Subject: Installing tomcat 4.4.1.18 on RH8.0 I already have SDK1.4 installed and setup so I downloaded the binary tomcat4-4.1.18-full.1jpp.noarch.rpm from the tomcat website and installed it as root (on RedHat 8.0) using, rpm -ivh tomcat4-4.1.18-full.1jpp.noarch.rpm Appears to install fine into /var/tomcat4 giving warnings about I need to alter my config files now. I am new to tomcat so I checked the RUNNING.TXT file and after reading it I am none the wiser! I have no /var/tomcat4/bin/startup.sh or /var/tomcat4/bin/shutdown.sh like it says, althought I can start and stop the server using the scripts in /etc/rc.d/init.d I managed to fiddle about (after reading the logs) and got something running, but when I connect to http://localhost:8080 I get an error about no context manager. Are there any comprehensive docs on how to setup tomcat under linux, or can someone provide with a step by step idiot guide? Thanks, Darren - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Cannot store SSL session to DBM file
I'm getting these errors on my Apache2/SSL server. [Mon Feb 03 09:26:28 2003] [error] (20014)Error string not specified yet: Cannot store SSL session to DBM file `/usr/local/apache2/logs/ssl_scache' [Mon Feb 03 09:26:28 2003] [error] (20014)Error string not specified yet: Cannot store SSL session to DBM file `/usr/local/apache2/logs/ssl_scache' Is there something I need to do to setup a DBM file properly? I have 2 files but they are not 'ssl_cache'. They are the .dir and .pag files created when the server is fired up.. -rw-r--r--1 nobody sys0 Jan 31 14:47 ssl_scache.dir -rw-r--r--1 nobody sys0 Jan 31 14:47 ssl_scache.pag Thanks for any help! Cheers, -- Trev - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Custom tag life cycle
If doEndTag isn't a good option for cleaning, why don't you use
doFinally()?
Anyway, it's incredible... i'm always finding out that writing custom
tags is a real nightmare :-)
On Mon, 2003-02-03 at 15:30, Tim Moore wrote:
-Original Message-
From: Gary McGath [mailto:[EMAIL PROTECTED]]
Sent: Monday, February 03, 2003 9:14 AM
To: [EMAIL PROTECTED]
Subject: Custom tag life cycle
The webapp which I am developing (see http://www.timeczar.com for
details) uses a moderately complex custom tag library, and
I've found the lifecycle of a TagSupport object to be very confusing.
As I understand it, a TagSupport object may (but is not
guaranteed to) be reused for subsequent occurrences of the
same tag in a JSP. This means that attribute variables can't
safely be initialized in the constructor, because they may
not get reinitialized for subsequent occurrences of the tag.
(Here I'm assuming that setter functions for attributes
simply set an instance variable.)
After some digging, I found that the recommended way to reset
attribute instance varaibles is to use the doEndTag method.
This probably doesn't work if a tag is nested within a tag of
the same name, but I can live with that.
Actually I believe that containers would be required to use two
different instances when tags are nested. The instance can only be
reused for subsequent uses of the tag *after* the first one is closed.
But I would do the initialization in doStartTag rather than doEndTag.
The latter may not be called if an exception is thrown from within the
tag body.
Doing this works fine in Tomcat. However, I recently ported
my webapp to Resin and found that it doesn't work there.
Here's a cut-back excerpt from my JSP:
caltags:eventset
caltags:evtstartdate mode=date length=m/ -
caltags:evtenddate mode=date length=m/ /caltags:eventset
The class which implements eventset includes the tag body
once for each event in the set. The evtstartdate and
evtenddate tags are implemented by a class called DateTag,
which extends TagSupport. Under Tomcat, DateTag.setMode and
DateTag.SetLength get called once for each tag in each
inclusion of the tag body. Under Resin, only two calls (one
for each of the date tags) are made to each of setMode and
setLength. If I clear the mode and length fields when I call
doEndTag, then all occurrences of the date tags except the
first take on their default attributes, which is not the
behavior I want.
Are both Tomcat and Resin within spec in implementing
different behaviors here? If so, what is the correct point
in the lifecycle to reset attribute values in a TagSupport object?
The spec allows the container to assume that the attributes of a tag
handler will be retained across invocations, so if there are multiple
identical invocations, the setter methods do not need to be called
again.
Here's what I'd recommend:
Initialize the mode and length instance variables to null at
construction time.
Do something like this in doStartTag:
String mode = this.mode;
if (mode == null) {
mode = DEFAULT_MODE;
}
...and repeat for length. Never modify the instance variables or call
their setters yourself -- let the container manage them.
--
Tim Moore / Blackboard Inc. / Software Engineer
1899 L Street, NW / 5th Floor / Washington, DC 20036
Phone 202-463-4860 ext. 258 / Fax 202-463-4863
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Felipe Schnack
Analista de Sistemas
[EMAIL PROTECTED]
Cel.: (51)91287530
Linux Counter #281893
Centro Universitário Ritter dos Reis
http://www.ritterdosreis.br
[EMAIL PROTECTED]
Fone/Fax.: (51)32303341
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: form-based auth
Craig, You understood my question correctly. And Bill, that's what I'm having to do (use sym-links) but I don't like that solution. I understand the form-login is required to be within the context, was just hoping there was a feature to deal with this issue of mine that I just hadn't found yet :) Thanks for confirming my suspicions. Looks like it's sym-links and I'll keep my fingers crossed that I don't have to do this setup on a Windows box! Colin -Original Message- From: Bill Barker [SMTP:[EMAIL PROTECTED]] Sent: Saturday, February 01, 2003 3:10 AM To: [EMAIL PROTECTED] Subject: Re: form-based auth Craig R. McClanahan [EMAIL PROTECTED] wrote in message [EMAIL PROTECTED]">news:[EMAIL PROTECTED]... Craig R. McClanahan [EMAIL PROTECTED] wrote in message [EMAIL PROTECTED]">news:[EMAIL PROTECTED]... On Fri, 31 Jan 2003, Madere, Colin wrote: Date: Fri, 31 Jan 2003 14:06:27 -0600 From: Madere, Colin [EMAIL PROTECTED] Reply-To: Tomcat Users List [EMAIL PROTECTED] To: '[EMAIL PROTECTED]' [EMAIL PROTECTED] Subject: form-based auth Anyone out there have multiple contexts (or simply multiple webapps) authenticating with the same form (login form in a single location)? The form login page has to be within the webapp, so this is not possible. Well, not really true. It's an all-or-nothing thing. If you use Single-Sign-On, then your login applies to all webapps once you log on to one of them. But, without writing your own custom Valve, you can't pick and choose which contexts get to see the login. It is true that the user's authentication applies to all webapps when you use SingleSignonValve, but I understood the initial question to be can I share a single copy of the form login page across multiple webapps. And that is something you cannot do -- each app needs their own login page (since the path for the form-login-page element is context-relative, not server-relative). Ok, you've got a point. Still, I routinely get around it (at least on *nix systems), by using sym-links and Entities. Craig - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DataSource.getConnection() hangs
ok, I configured data source, wrote those lines you can see below in server.xml, inside Context tag. Now Tomcat just hangs, when I call DataSource method getConnection. I use Tomcat 4.1.18 has anybody experienced this ? Maris Orbidans ResourceParams name=jdbc/BooksDB parameter namevalidationQuery/name value/ /parameter parameter nameurl/name valuejdbc:mysql://localhost/booksdb/value /parameter parameter namepassword/name valuehh/value /parameter parameter namemaxActive/name value16/value /parameter parameter namemaxWait/name value5000/value /parameter parameter namedriverClassName/name valuecom.mysql.jdbc.Driver/value /parameter parameter nameusername/name valuepoweruser/value /parameter parameter namemaxIdle/name value2/value /parameter /ResourceParams -Original Message- From: Cristian Draghici [mailto:[EMAIL PROTECTED]] Sent: Thursday, January 30, 2003 11:07 AM To: Tomcat Users List Subject: RE: Cannot load JDBC driver class 'null' yes it will shutdown tomcat and edit the server.xml file by hand. (add the ResourceParams entry under your context) add the necessary entries, start tomcat and the admin console should work. (at least that's what happens with my tomcat 4.1.18) hope this helps, cristi -Original Message- From: Maris Orbidans [mailto:[EMAIL PROTECTED]] Sent: Thursday, January 30, 2003 11:03 AM To: Tomcat Users List Subject: Cannot load JDBC driver class 'null' hello I have run into that problem too, I defined a datasource and put driver and common/lib and defined resource-ref in web.xml of my web. app. but if throws exception when I try to get a connection from datasource I have found. I tried to do it at home with different database with the same result, so I dont think I have mistyped something. I know this problem has been adressed before but I havent found any solution from maillist archives. BTW I have found one related thing: If you open Tomcat admin tool, choose host - context - context name - Data sources it will throw an exception: org.apache.jasper.JasperException: Exception retrieving attribute 'driverClassName' so... I there any known solution ? Maris Orbidans www.datapro.lv - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Error 500
First, thanks for all messages. Well, i'm using j2sdk 1.4, Tomcat 4.1.1, Win NT 4, my app access DB2. I searched anything in log, but don't have anything write about this error. LoginCommand and AdminServlet, as showing in error message, are my class, they are controls for beans and jsp. LoginCommand only receives two parameters, and they aren't empty. But this exception, don't appears with frequency, sometimes when i test a page a lot of. This is a curiosity mine, know why this. Full description of error: java.lang.NullPointerException at eshop.share.LoginCommand.execute(LoginCommand.java:47) at eshop.share.AdminServlet.service(AdminServlet.java:40) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:247) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:193) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:260) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643) at org.apache.catalina.valves.CertificatesValve.invoke(CertificatesValve.java:246) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2397) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643) at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java:170) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:171) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:174) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.connector.http.HttpProcessor.process(HttpProcessor.java:1040) at org.apache.catalina.connector.http.HttpProcessor.run(HttpProcessor.java:1151) at java.lang.Thread.run(Thread.java:536) =
m.s.craig@rl.ac.uk
If you happen to find out, pass the work along please. --Jonathan -Original Message- From: Martin Craig [mailto:[EMAIL PROTECTED]] Sent: Monday, February 03, 2003 6:20 AM To: [EMAIL PROTECTED] Subject: Getting SSL info using mod_jk Hi, I've just joined this list and see from previous messages that there are a lot of people having trouble getting mod_jk to pass SSL certificate info to Tomcat. I can't get this to work either (trying using Apache 1.3, Tomcat 4.1.18, mod_jk and either the AJP13 or Coyote JK2 connectors). I've tried everything I can find on various web pages but no joy. Has anyone got this working correctly? (i.e. can do req.getAttribute(javax.servlet.request.X509Certificate) and get something other than null). Like a previous poster I can get the javax.servlet.request.cipher_suite attribute but nothing else. Thanks for any info, Martin. -- Martin Craig [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
more about custam tag life cycle
I was thinking... Gary McGath, if I understood well what you said it's possible that a container will call the same tag instance concurrently??? This would be a real problem, as if this happens, you couldn't believe even in your pageContext, etc variables! -- Felipe Schnack Analista de Sistemas [EMAIL PROTECTED] Cel.: (51)91287530 Linux Counter #281893 Centro Universitário Ritter dos Reis http://www.ritterdosreis.br [EMAIL PROTECTED] Fone/Fax.: (51)32303341 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: DataSource.getConnection() hangs
Put this: == resource-ref descriptionany description/description res-ref-namejdbc/BooksDB/res-ref-name res-typejavax.sql.DataSource/res-type res-authContainer/res-auth /resource-ref == In web.xml of your application. See too http://jakarta.apache.org/tomcat/tomcat-4.1-doc/jndi-datasource-examples-how to.html Ok. - Original Message - From: Maris Orbidans [EMAIL PROTECTED] To: Tomcat Users List [EMAIL PROTECTED] Sent: Monday, February 03, 2003 15:47 Subject: DataSource.getConnection() hangs E-mail Premium BOL Antivírus, anti-spam e até 100 MB de espaço. Assine já! http://email.bol.com.br/ ok, I configured data source, wrote those lines you can see below in server.xml, inside Context tag. Now Tomcat just hangs, when I call DataSource method getConnection. I use Tomcat 4.1.18 has anybody experienced this ? Maris Orbidans ResourceParams name=jdbc/BooksDB parameter namevalidationQuery/name value/ /parameter parameter nameurl/name valuejdbc:mysql://localhost/booksdb/value /parameter parameter namepassword/name valuehh/value /parameter parameter namemaxActive/name value16/value /parameter parameter namemaxWait/name value5000/value /parameter parameter namedriverClassName/name valuecom.mysql.jdbc.Driver/value /parameter parameter nameusername/name valuepoweruser/value /parameter parameter namemaxIdle/name value2/value /parameter /ResourceParams -Original Message- From: Cristian Draghici [mailto:[EMAIL PROTECTED]] Sent: Thursday, January 30, 2003 11:07 AM To: Tomcat Users List Subject: RE: Cannot load JDBC driver class 'null' yes it will shutdown tomcat and edit the server.xml file by hand. (add the ResourceParams entry under your context) add the necessary entries, start tomcat and the admin console should work. (at least that's what happens with my tomcat 4.1.18) hope this helps, cristi -Original Message- From: Maris Orbidans [mailto:[EMAIL PROTECTED]] Sent: Thursday, January 30, 2003 11:03 AM To: Tomcat Users List Subject: Cannot load JDBC driver class 'null' hello I have run into that problem too, I defined a datasource and put driver and common/lib and defined resource-ref in web.xml of my web. app. but if throws exception when I try to get a connection from datasource I have found. I tried to do it at home with different database with the same result, so I dont think I have mistyped something. I know this problem has been adressed before but I havent found any solution from maillist archives. BTW I have found one related thing: If you open Tomcat admin tool, choose host - context - context name - Data sources it will throw an exception: org.apache.jasper.JasperException: Exception retrieving attribute 'driverClassName' so... I there any known solution ? Maris Orbidans www.datapro.lv - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Encrypt tomcat-users.xml
- Mensaje Original - De: Jeanfrancois Arcand [EMAIL PROTECTED] Fecha: Domingo, Febrero 2, 2003 6:32 pm Asunto: Re: Encrypt tomcat-users.xml A better solution is to use a database to store your username/password information and configure the JDBCDatabaseRealm (instead of the default one: MemoryRealm). See http://jakarta.apache.org/tomcat/tomcat-4.1-doc/realm-howto.html -- Jeanfrancois A.VERGES wrote: Hi, Do you know any way to encrypt the Tomcat users file called tomcat-users.xml or another way to prevet the hacking of users file? Thank you Aleix Vergés --- -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Thank you! I'll try it! Aleix Vergés - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: more about custam tag life cycle
This is NOT true, AFAIK. The same tag instance can be used multiple times *sequentially* but not *concurrently*. Check out the lifecycle state diagram in the JSP spec. -- Tim Moore / Blackboard Inc. / Software Engineer 1899 L Street, NW / 5th Floor / Washington, DC 20036 Phone 202-463-4860 ext. 258 / Fax 202-463-4863 -Original Message- From: Felipe Schnack [mailto:[EMAIL PROTECTED]] Sent: Monday, February 03, 2003 1:01 PM To: Tomcat Users List Subject: more about custam tag life cycle I was thinking... Gary McGath, if I understood well what you said it's possible that a container will call the same tag instance concurrently??? This would be a real problem, as if this happens, you couldn't believe even in your pageContext, etc variables! -- Felipe Schnack Analista de Sistemas [EMAIL PROTECTED] Cel.: (51)91287530 Linux Counter #281893 Centro Universitário Ritter dos Reis http://www.ritterdosreis.br [EMAIL PROTECTED] Fone/Fax.: (51)32303341 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: more about custam tag life cycle
This makes me feel much better :-) On Mon, 2003-02-03 at 16:09, Tim Moore wrote: This is NOT true, AFAIK. The same tag instance can be used multiple times *sequentially* but not *concurrently*. Check out the lifecycle state diagram in the JSP spec. -- Tim Moore / Blackboard Inc. / Software Engineer 1899 L Street, NW / 5th Floor / Washington, DC 20036 Phone 202-463-4860 ext. 258 / Fax 202-463-4863 -Original Message- From: Felipe Schnack [mailto:[EMAIL PROTECTED]] Sent: Monday, February 03, 2003 1:01 PM To: Tomcat Users List Subject: more about custam tag life cycle I was thinking... Gary McGath, if I understood well what you said it's possible that a container will call the same tag instance concurrently??? This would be a real problem, as if this happens, you couldn't believe even in your pageContext, etc variables! -- Felipe Schnack Analista de Sistemas [EMAIL PROTECTED] Cel.: (51)91287530 Linux Counter #281893 Centro Universitário Ritter dos Reis http://www.ritterdosreis.br [EMAIL PROTECTED] Fone/Fax.: (51)32303341 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Felipe Schnack Analista de Sistemas [EMAIL PROTECTED] Cel.: (51)91287530 Linux Counter #281893 Centro Universitário Ritter dos Reis http://www.ritterdosreis.br [EMAIL PROTECTED] Fone/Fax.: (51)32303341 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
form based authentication workflow problem
hello, i'm currently working on a web application where we want to use the container based authentication mechanism because of its standarized character. therefore we need to use form-based authentification. from the post within this forum i understood that the login page should never be accessed directly by the user and after the authentication the user gets redirected to the page he requested. the problem now occurs for us is that we want to have a list of all logged in users within our application, say in the servlet context. that wouldn't be the problem with a SessionListener. anyway we have the additional restriction that one user can only be logged in once at a time, say he/she can only have one session. therefore after every container based authentication process we need to check whether this user is already logged to the system and if so invalidate the session and send him/her out of the protected area. further reading in the list led me to posts of the year 2001 where people were discussing the session attribute tomcat.auth.originalLocation regarding to that topic. so with a filter it should be possible to look for that attribute, do some action and send the user either to the location stated in that attribute or outside. so what i need to know is whether i'm right with my statements above (can it be done this way) and whether there's a better more comfortable way to do that because this solution sounds a bit dirty to me. thanks for any help, ralf by the way: i tried to figure out when and from who the session is created after the authentication is complete but i couldn't figure out. can somebody explain me this? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
JSP:inlcude not working
I am porting an application from tomcat 3.2.3 to tomcat 4.1.12 and am having a problem with jsp:inlcude. I have a directory structure like this webapps/common/common jsps webapps/admin/specific jsps The common jsps directory contains a menu that I use in all of the specific jsp pages. This menu is just a table that does a bit of data processing to determine what menu items a specific user should see. Anyway, in version 3.2.3 the code to include the menu looks like this: jsp:include page=../common/navbar.jsp flush=true but in 4.1.12 this does not work. If, however, I change it to %@ include file=../common/navbar.jsp% it works fine. To further complicate things, if I place the navbar.jsp in the same directory as the specific jsps and add this code jsp:include page=navbar.jsp flush=true it also works fine. Anyone have any thoughts on why? C. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Datasource and connection
I'm curious as to why you're asking this question. You should be using the
connection pool according to the documentation provided, because that is how
it is intended to be used. That is...
void doPost(...)
{
InitialContext ic = new InitialContext();
Context jdbcCtx = (Context) ic.lookup(java:comp/env);
DataSource ds = (DataSource) jdbcCtx.lookup(jdbc/myDataSource);
Connection conn = null;
Statement stmt = null;
ResultSet rs = null;
try {
conn = ds.getConnection();
stmt = ...
rs = ...
}
catch(SQLException esql) {
}
finally {
if(rs != null)
rs.close();
if(stmt != null)
stmt.close();
if(conn != null)
conn.close();
}
}
What exactly are you THINKING of doing?
-Original Message-
From: Lindomar [mailto:[EMAIL PROTECTED]]
Sent: Monday, February 03, 2003 06:02
To: Tomcat Users List
Subject: Datasource and connection
Hi everybody!
I'm using datasource of tomcat for get connection.
Well, when i do this:
...
DataSource ds = (DataSource)ctx.lookup( java:comp/env/jdbc/Anything);
if (ds != null)
connection = ds.getConnection();
...
In the next time, will give tomcat to me a new connection or the same?
I think that is same, but i didn't read anything about this.
And when Tomcat close this connection? Only through the timeout?
Thanks in advanced.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: inlcude not working
you can't include files from a different webapp Filip -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Monday, February 03, 2003 10:24 AM To: [EMAIL PROTECTED] Subject: JSP:inlcude not working I am porting an application from tomcat 3.2.3 to tomcat 4.1.12 and am having a problem with jsp:inlcude. I have a directory structure like this webapps/common/common jsps webapps/admin/specific jsps The common jsps directory contains a menu that I use in all of the specific jsp pages. This menu is just a table that does a bit of data processing to determine what menu items a specific user should see. Anyway, in version 3.2.3 the code to include the menu looks like this: jsp:include page=../common/navbar.jsp flush=true but in 4.1.12 this does not work. If, however, I change it to %@ include file=../common/navbar.jsp% it works fine. To further complicate things, if I place the navbar.jsp in the same directory as the specific jsps and add this code jsp:include page=navbar.jsp flush=true it also works fine. Anyone have any thoughts on why? C. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Custom tag life cycle
From: Tim Moore [EMAIL PROTECTED] Sent: Monday, February 03, 2003 9:30 AM Subject: RE: Custom tag life cycle But I would do the initialization in doStartTag rather than doEndTag. The latter may not be called if an exception is thrown from within the tag body. The problem here is that the doStartTag is done after all of the properties are set. So, you don't know if a property value has been set from the current tag invocation or an earlier tag invocation. I think Felipes idea of using the doFinally as a reset to default contructed state is the smartest thing. I'd like to hope that the new JSP spec clarifies the lifecycle a bit better, taking in to account the aggressive caching that the containers are doing now. Regards, Will Hartung ([EMAIL PROTECTED]) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Reading client certificates
For something like a week now I've been trying to read SSL Client
Certificate information using:
Apache 2.0.44, Tomcat 4.1.18, mod_jk built from the connectors-4.1.18
package and the mod_ssl that comes with the 2.0.44 source
distribution.I have finally got things working in my environment in
a satisfactory way, and I thought I'd take a minute to post to the list
some of what I learned.
Thanks to all of you who responded to my requests for help. Most of the
reponses were helpful and all were appreciated.
First of all, I never could get mod_jk2 to pass SSL environment
variables between Apache and Tomcat. The only one that ever seemed to
get through was javax.servlet.request.cipher_suite. After a couple of
frustrating days, I gave up on mod_jk2 and went back to mod_jk. (If
anybody knows how to make this work with mod_jk2, I'd still like to hear
about it.) I set this up according to the excellent instructions at:
http://jakarta.apache.org/tomcat/tomcat-3.2-doc/tomcat-ssl-howto.html
In my httpd.conf file, I put the following directives in the global area:
### instruct mod_jk to play nicely with mod_ssl ##
IfModule mod_jk.c
JkExtractSSL On
JkHTTPSIndicator HTTPS
JkSESSIONIndicator SSL_SESSION_ID
JkCIPHERIndicator SSL_CIPHER
JkCERTSIndicator SSL_CLIENT_CERT
/IfModule
and in the VirtualHost section that controls the Tomcat context from
which I wish to read client certificate data:
Location /safe
SSLOptions +FakeBasicAuth +ExportCertData +StdEnvVars
SSLVerifyClient require
SSLVerifyDepth 1
SSLRequireSSL
/Location
Obviously, you should substitute your context name where I have safe.
Once Apache, Tomcat and mod_jk were all properly configured and playing
nicely with one another, the next challenge was to write some java code
in a servlet to get to the client certificate information. This proved
to be pretty easy, except for one avoidable blunder that I'll talk about
in a minute. Here's a code snippet that works for me:
import java.security.cert.*;
try {
Object o = request.getAttribute(
javax.servlet.request.X509Certificate);
if (o != null) {
X509Certificate certs[] = (X509Certificate[])o;
X509Certificate cert = certs[0];
// Get the Distinguished Name for the user.
String n = cert.getSubjectDN().getName();
}
else
out.println = Object was null.;
}
catch (Exception exc) {
out.println = exc.toString();
}
Nothing to it. Except that now I want to rant for a bit. The Servlet
2.3 specification says (in SRV.4.7):
If there is an SSL certificate associated with the request, it must
be exposed by the servlet container to the servlet programmer as an
array of objects of type java.security.cert.X509Certificate and
accessible via a ServletRequest attribute of
javax.servlet.request.X509Certificate...
Now, I KNOW it's my fault for not reading carefully, but I spent hours
trying to figure out why I was getting a ClassCast Exception for trying
to cast the request attribute object to
javax.security.cert.X509Certificate[]. (The problem, in case it has
escaped you as it did me for so long, is that I used javax instead of
java.) My mistake would have been a lot more transparent if not for
the fact that there does exist a class named
javax.security.cert.X509Certificate. Now, I suppose there's a good
reason for this but, damn, do we really need to have 2 X509Certificate
classes, one in the java.security.cert package and the other in the
javax.security.cert package? Yikes.
Anyway, I hope this synopsis is of some value. And thanks again to all
those who tried to help me.
Robert Dana
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Datasource and connection
So so Sean.
Then this is a way of tomcat implements the concept of connection pools.
Right, i only wanted have certain.
Thanks for all.
- Original Message -
From: Sean Dockery [EMAIL PROTECTED]
To: Tomcat Users List [EMAIL PROTECTED]
Sent: Monday, February 03, 2003 16:25
Subject: RE: Datasource and connection
I'm curious as to why you're asking this question. You should be using
the
connection pool according to the documentation provided, because that is
how
it is intended to be used. That is...
void doPost(...)
{
InitialContext ic = new InitialContext();
Context jdbcCtx = (Context) ic.lookup(java:comp/env);
DataSource ds = (DataSource) jdbcCtx.lookup(jdbc/myDataSource);
Connection conn = null;
Statement stmt = null;
ResultSet rs = null;
try {
conn = ds.getConnection();
stmt = ...
rs = ...
}
catch(SQLException esql) {
}
finally {
if(rs != null)
rs.close();
if(stmt != null)
stmt.close();
if(conn != null)
conn.close();
}
}
What exactly are you THINKING of doing?
-Original Message-
From: Lindomar [mailto:[EMAIL PROTECTED]]
Sent: Monday, February 03, 2003 06:02
To: Tomcat Users List
Subject: Datasource and connection
Hi everybody!
I'm using datasource of tomcat for get connection.
Well, when i do this:
...
DataSource ds = (DataSource)ctx.lookup( java:comp/env/jdbc/Anything);
if (ds != null)
connection = ds.getConnection();
...
In the next time, will give tomcat to me a new connection or the same?
I think that is same, but i didn't read anything about this.
And when Tomcat close this connection? Only through the timeout?
Thanks in advanced.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
error page for error code 500?
Greetings, My apologies for this simple question... I am using 4.0.4 I am able to capture the error codes 404 and 400 but not 500. My snippet bellow... !-- This works...-- error-page error-code404/error-code location/error/ServerError404Page.jsp/location /error-page error-page error-code400/error-code location/error/Server400ErrorPage.jsp/location /error-page !-- this does not work - why? -- error-page error-code500/error-code location/error/Server500ErrorPage.jsp/location /error-page - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: bean initialization code
Bill, Is there a way to make the constructor in the bean global to all sessions? Is there some other mechanisim that allows for this? I want to initialize some objects that will exist for all users of a .jsp page. How do I go about doing this? thanks! -jeff --- Bill Barker [EMAIL PROTECTED] wrote: Jeff Ousley [EMAIL PROTECTED] wrote in message [EMAIL PROTECTED]">news:[EMAIL PROTECTED]... Hello! Is there a method I can override in a bean that'll get executed when a bean is first used and not on subsequent calls? Basically I'm page that uses a bean such as: jsp:useBean id=termwatch class=termwatch.TermWatchBean scope=session/ In order to use the termwatch bean some code inside the bean needs to be executed first. I can create a method and explicitly call it, but is there a better way? Do beans have cnstructors? Or should I be handling this on my page in a jspInit() method? It is perfectly legal to specify a constructor for your bean, as long as it takes no arguments. thanks! -jeff __ Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now. http://mailplus.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] __ Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now. http://mailplus.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: more about custam tag life cycle
From: Felipe Schnack [EMAIL PROTECTED] Sent: Monday, February 03, 2003 10:12 AM Subject: RE: more about custam tag life cycle This makes me feel much better :-) On Mon, 2003-02-03 at 16:09, Tim Moore wrote: This is NOT true, AFAIK. The same tag instance can be used multiple times *sequentially* but not *concurrently*. Check out the lifecycle state diagram in the JSP spec. The way to look at it is simply that the generated code is going to use a tag pool for each distinct class of tags. Unfortunately, there is no specific action that tells the tag it is being pulled from or being put back from the pool. All tags follow the basic lifecycle of simpy constuctor setPageContext doStartTag doEndTag In the pooled environment, it's: constructor setPageContext doStartTag doEndTag doStartTag doEndTag etc. (I've seen some containers, I thinik Tomcat is one, that call setPageContext on each tag, but I've seen others that do not, so setPageContext is not a reliable method to reset the tag properties). If the tag implments the TryCatchFinally interface, then a doFinally is called after the doEndTag. What's is non-obvious is that the doEndTag and doFinally are supposed to assume the role of cleaning the tag up for reuse. I particularly like this quote from the spec: The particular code shown below assumes there is some pool of tag handlers that are managed (details not described, although pool managing is simpler when there are no optional attributes), This entire problem, at least as I've encountered it, revolves around not only optional, but also contradictory tags (i.e. it's okay to specify paramter a, b, or c, but no combination in the same tag). And like I said earlier, it would be nice if there were a pool interface added to the lifecycle to clean up the tag processing to make optional properties more portable and easier to write for. Regards, Will Hartung ([EMAIL PROTECTED]) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
HELP! - Tomcat 4.1 acting weird with redirect / sessions
Hi all, I have an application that has been up and running on Tomcat 3.x for over a year and I rewrote it on a Windows 2000 box using Tomcat 4.0 recently. I have uncovered a weird error once I moved it to the production server, which is running Linux 7.2 and Tomcat 4.1.X. Once I log into the application, I set a couple of variables into the session scope. All is cool (as in I can get and set values in the active session) until the FIRST time I use response.sendRedirect(). For whatever reason, the first time this occurs, the session is lost, and I get a new one (thus triggering my security code which redirects the user to the login page). But...once at the login page, if I log in again (without a restart or anything like that) all is OK and the exact code which caused this behaviour acts exactly as I would expect, and always maintains a valid handle on the current session. This has never happened on Tomcat 4.0 (at least on Windows...I went directly from Tomcat 3x to 4.1 on the prod. server). For now, I have simply asked users to log in twice, wich makes me look like a real pro...:-( So, does anyone have any ideas? I replaced the offending redirect with a requestDispatcher forward, but all that did was MOVE the problem to the next piece of code which uses response.sendRedirect(). I am not really in the mood to replace ALL instances of the redirects with forwards, as that feels like a band-aid solution, so please help if you can! Regards, JavaWanabe _ Tired of spam? Get advanced junk mail protection with MSN 8. http://join.msn.com/?page=features/junkmail - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: more about custam tag life cycle
I'm curious, how you get a PageContext when the container doesn't call setPageContext? Which container have this behavior? I don't see a reason why we should have pool-specific method for tag property cleaning. doFinally method is intended for tag cleaning... Probably when created it was intended for cleaning resources like database connections, etc but I don't see any reason to create yet another method just for tag reuse On Mon, 2003-02-03 at 17:00, Will Hartung wrote: From: Felipe Schnack [EMAIL PROTECTED] Sent: Monday, February 03, 2003 10:12 AM Subject: RE: more about custam tag life cycle This makes me feel much better :-) On Mon, 2003-02-03 at 16:09, Tim Moore wrote: This is NOT true, AFAIK. The same tag instance can be used multiple times *sequentially* but not *concurrently*. Check out the lifecycle state diagram in the JSP spec. The way to look at it is simply that the generated code is going to use a tag pool for each distinct class of tags. Unfortunately, there is no specific action that tells the tag it is being pulled from or being put back from the pool. All tags follow the basic lifecycle of simpy constuctor setPageContext doStartTag doEndTag In the pooled environment, it's: constructor setPageContext doStartTag doEndTag doStartTag doEndTag etc. (I've seen some containers, I thinik Tomcat is one, that call setPageContext on each tag, but I've seen others that do not, so setPageContext is not a reliable method to reset the tag properties). If the tag implments the TryCatchFinally interface, then a doFinally is called after the doEndTag. What's is non-obvious is that the doEndTag and doFinally are supposed to assume the role of cleaning the tag up for reuse. I particularly like this quote from the spec: The particular code shown below assumes there is some pool of tag handlers that are managed (details not described, although pool managing is simpler when there are no optional attributes), This entire problem, at least as I've encountered it, revolves around not only optional, but also contradictory tags (i.e. it's okay to specify paramter a, b, or c, but no combination in the same tag). And like I said earlier, it would be nice if there were a pool interface added to the lifecycle to clean up the tag processing to make optional properties more portable and easier to write for. Regards, Will Hartung ([EMAIL PROTECTED]) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Felipe Schnack Analista de Sistemas [EMAIL PROTECTED] Cel.: (51)91287530 Linux Counter #281893 Centro Universitário Ritter dos Reis http://www.ritterdosreis.br [EMAIL PROTECTED] Fone/Fax.: (51)32303341 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Single-Sign-On (SSO) with Tomcats in 2 different servers
Hi, I have 2 servers, both with Tomcat. On each server is installed a different web application. Therefore, server A has a Tomcat with application A, and server B has another Tomcat (but same version) with Application B. The access to the applications is restricted, so the user must provide his userId and password before accessing the applications. Both applications authenticate against the same LDAP server. The issue is that Id like to use Single Sign On (SSO) to access both applications, so that when a user accesses one application and identifies himself, he doesnt need to identify again when he accesses the other application. I think that in order to accomplishing this, the two Tomcats should be able to share sessions. Is this possible? Is there any other solution? Thanks in advance. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: more about custam tag life cycle
-Original Message- From: Will Hartung [mailto:[EMAIL PROTECTED]] Sent: Monday, February 03, 2003 2:01 PM To: Tomcat Users List Subject: Re: more about custam tag life cycle [snipped] This entire problem, at least as I've encountered it, revolves around not only optional, but also contradictory tags (i.e. it's okay to specify paramter a, b, or c, but no combination in the same tag). I think the intention of the spec writers was to make that a problem for the container implementors, not for the tag handler developer. From s.10.1.1: Note that since there are no guarantees on the state of the properties, a tag handler that had some optional properties set can only be reused if those properties are set to a new (known) value. This means that tag handlers can only be reused within the same 'AttSet' (set of attributes that have been set). -- Tim Moore / Blackboard Inc. / Software Engineer 1899 L Street, NW / 5th Floor / Washington, DC 20036 Phone 202-463-4860 ext. 258 / Fax 202-463-4863 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: tomcat-user Digest 3 Feb 2003 17:27:41 -0000 Issue 2142
On Monday, February 3, 2003, [EMAIL PROTECTED] wrote: Craig R. McClanahan [EMAIL PROTECTED] wrote: Are both Tomcat and Resin within spec in implementing different behaviors here? If so, what is the correct point in the lifecycle to reset attribute values in a TagSupport object? Sounds like they are to me. The JSP page compiler has the option to optimize out the second call to the setters, because tag instances can only be shared if the combination of attribute values is identical (as they are in your case above), but it's not required. That may be the missing piece: that tag instances can only be shared *if the combination of attribute values is identical*. I originally wrote my code the way you described, but I thought I was seeing cases where tags instances were being shared even when the attributes weren't identical. Since I didn't know what the exact behavior to expect was, I might have misread some other problem. A quick rewrite of my code in the way you suggested seems to be behaving correctly. Gary McGath http://www.mcgath.com/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: more about custam tag life cycle
-Original Message- From: Felipe Schnack [mailto:[EMAIL PROTECTED]] Sent: Monday, February 03, 2003 2:12 PM To: Tomcat Users List Subject: Re: more about custam tag life cycle I'm curious, how you get a PageContext when the container doesn't call setPageContext? Which container have this behavior? What he meant is that it may not call setPageContext *on each invocation*. It will always be called at least once before doStartTag. I don't see a reason why we should have pool-specific method for tag property cleaning. doFinally method is intended for tag cleaning... Probably when created it was intended for cleaning resources like database connections, etc but I don't see any reason to create yet another method just for tag reuse I think there might be some benefit in clarity to the tag developer. The current lifecycle behavior seems to confuse a lot of people (and I was certainly one of those people when I first started writing tag extensions). But when I made a suggestion like that on the tomcat-dev list, it was pointed out that JSP 2.0 offers a new SimpleTag interface that will never be pooled, and is much more straightforward than the classic tag interface. Hopefully in the future most tags can use that interface instead, and the classic Tag interface can be reserved for the rare tags that benefit from reuse. -- Tim Moore / Blackboard Inc. / Software Engineer 1899 L Street, NW / 5th Floor / Washington, DC 20036 Phone 202-463-4860 ext. 258 / Fax 202-463-4863 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: inlcude not working
Not sure why %@ include file=../common/navbar.jsp% works in 4.1.12 (I'm pretty sure this fails in 4.1.19). As Filip points out, the include directive and the jsp:include action are for including resources from the same context as the current page. You might want to check out JSTL's c:import tag: c:import url=/navbar.jsp context=/common/ Quoting Filip Hanik [EMAIL PROTECTED]: you can't include files from a different webapp Filip -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Monday, February 03, 2003 10:24 AM To: [EMAIL PROTECTED] Subject: JSP:inlcude not working I am porting an application from tomcat 3.2.3 to tomcat 4.1.12 and am having a problem with jsp:inlcude. I have a directory structure like this webapps/common/common jsps webapps/admin/specific jsps The common jsps directory contains a menu that I use in all of the specific jsp pages. This menu is just a table that does a bit of data processing to determine what menu items a specific user should see. Anyway, in version 3.2.3 the code to include the menu looks like this: jsp:include page=../common/navbar.jsp flush=true but in 4.1.12 this does not work. If, however, I change it to %@ include file=../common/navbar.jsp% it works fine. To further complicate things, if I place the navbar.jsp in the same directory as the specific jsps and add this code jsp:include page=navbar.jsp flush=true it also works fine. Anyone have any thoughts on why? C. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Kris Schneider mailto:[EMAIL PROTECTED] D.O.Tech http://www.dotech.com/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: URGENT: many apache processes
just for others: i had to set the number of maxProcessors in AJP13 connector to a value greater then MaxProcesses value in apache's http.conf. If you have a number of apache servers using the same Tomcat, do you have to set maxProcessors in the AJP13 connector to greater than MaxProcesses * number of apaches? On the page http://jakarta.apache.org/tomcat/tomcat-4.1-doc/config/jk.html you will find the following: maxProcessors: The maximum number of request processing threads to be created by this Connector, which therefore determines the maximum number of simultaneous requests that can be handled. If not specified, this attribute is set to 20. NOTE:For Apache 1.3 on Unix there is a 1 to 1 mapping between httpd processes and Ajp13Processors. You must configure maxProcessors to be greater than or equal to the maximum number of httpd processes your Apache web server spawns. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Custom tag life cycle
-Original Message-
From: Will Hartung [mailto:[EMAIL PROTECTED]]
Sent: Monday, February 03, 2003 1:38 PM
To: Tomcat Users List
Subject: Re: Custom tag life cycle
From: Tim Moore [EMAIL PROTECTED]
Sent: Monday, February 03, 2003 9:30 AM
Subject: RE: Custom tag life cycle
But I would do the initialization in doStartTag rather than
doEndTag.
The latter may not be called if an exception is thrown from
within the
tag body.
The problem here is that the doStartTag is done after all of
the properties are set.
So, you don't know if a property value has been set from the
current tag invocation or an earlier tag invocation.
I think Felipes idea of using the doFinally as a reset to
default contructed state is the smartest thing. I'd like to
hope that the new JSP spec clarifies the lifecycle a bit
better, taking in to account the aggressive caching that the
containers are doing now.
But did you see the rest of my message? It's important to not actually
reset the instance variables between invocations. So really, you don't
want to intialize those at all, but invocation-specific local variables.
More from the JSP 1.2 spec:
s.10.1:
It is the
responsability of user code, be it scriptlets, JavaBeans code, or code
inside custom
tags, to not invoke these setter methods, as doing otherwise would
interfere with
the container knowledge.
Once properly set, all properties are expected to be persistent, so
that if the
JSP container ascertains that a property has already been set on a given
tag
handler instance, it needs not set it again.
s.10.1.1 :
After the doEndTag invocation, the tag
handler is available for further invocations (and it is expected to have
retained its
properties).
So I misstated; you don't want to initialize properties themselves in
doStartTag, you want to do something like this:
String attr1 = this.attr1;
if (attr1 == null) {
attr1 = DEFAULT_ATTR1;
}
etc.
--
Tim Moore / Blackboard Inc. / Software Engineer
1899 L Street, NW / 5th Floor / Washington, DC 20036
Phone 202-463-4860 ext. 258 / Fax 202-463-4863
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: more about custam tag life cycle
On Mon, 3 Feb 2003, Will Hartung wrote: Date: Mon, 3 Feb 2003 11:00:46 -0800 From: Will Hartung [EMAIL PROTECTED] Reply-To: Tomcat Users List [EMAIL PROTECTED] To: Tomcat Users List [EMAIL PROTECTED] Subject: Re: more about custam tag life cycle From: Felipe Schnack [EMAIL PROTECTED] Sent: Monday, February 03, 2003 10:12 AM Subject: RE: more about custam tag life cycle This makes me feel much better :-) On Mon, 2003-02-03 at 16:09, Tim Moore wrote: This is NOT true, AFAIK. The same tag instance can be used multiple times *sequentially* but not *concurrently*. Check out the lifecycle state diagram in the JSP spec. The way to look at it is simply that the generated code is going to use a tag pool for each distinct class of tags. Unfortunately, there is no specific action that tells the tag it is being pulled from or being put back from the pool. The page will call release() before it is put back in the pool. All tags follow the basic lifecycle of simpy constuctor setPageContext doStartTag doEndTag In the pooled environment, it's: constructor setPageContext doStartTag doEndTag doStartTag doEndTag etc. (I've seen some containers, I thinik Tomcat is one, that call setPageContext on each tag, but I've seen others that do not, so setPageContext is not a reliable method to reset the tag properties). If the tag implments the TryCatchFinally interface, then a doFinally is called after the doEndTag. This only helps in a JSP 1.2 container, and comes with at least some performance price due to the extra try/catch/finally block that the page compiler has to create. What's is non-obvious is that the doEndTag and doFinally are supposed to assume the role of cleaning the tag up for reuse. That is not what they are for. The purpose of doEndTag() is to finish up whatever processing your tag does, at the end of the closing tag on the page. You should not be modifying the attribute values that were set by the page anyway, so there should be no need to clean up here. The purpose of doFinally() is to deal with exceptions that were thrown within the body of your tag. You really do not want to spend the extra processor cycles when such exceptions do not occur, or don't matter to you. I particularly like this quote from the spec: The particular code shown below assumes there is some pool of tag handlers that are managed (details not described, although pool managing is simpler when there are no optional attributes), This entire problem, at least as I've encountered it, revolves around not only optional, but also contradictory tags (i.e. it's okay to specify paramter a, b, or c, but no combination in the same tag). There are really two issues here -- tag *pooling* (the container recycles a previous tag instance instead of creating a new one every time) and tag *reuse* (the container uses the same instance for more than one tag with identical attributes). It's entirely legal to have tag reuse even in a container that does not implement tag pooling, so you have to account for both possibilities. Tag reuse is only allowed when the set of attributes that are used, and their values, are identical. For example, the following two tags will *always* use different instances: foo:bar baz=a/ foo:bar baz=b/ because the attribute value is different. Likewise, the following two tags will *always* use different instances: foo:bar baz=a/ foo:bar bif=a/ because different attribues are used. However, the following tag instances *can* be reused (and smart developers will always program their tags as if they *will* be reused): foo:bar baz=a/ foo:bar baz=a/ If your container does implement tag pooling (in addition to or instead of tag reuse), it will call release() before returning the instance to the pool. That makes release() the right place to reset everything to defaults. And like I said earlier, it would be nice if there were a pool interface added to the lifecycle to clean up the tag processing to make optional properties more portable and easier to write for. There are two simple rules for writing pooling-safe and reuse-safe tags: * Do not modify the instance variables that were set by your attribute setters in ANY of the doXxx() methods. * If you want to clean up, do so in release(), which will be called before a tag instance can be returned to the pool. Or, in JSP 2.0, use the new SimpleTag API and dispense with the whole set of concerns about tag lifecycle (such tag instances cannot be pooled, so you don't have to worry about it). Regards, Will Hartung ([EMAIL PROTECTED]) Craig - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Using Jigsaw with Tomcat
hi all, I have setup tomcat 4.1.18 with Jigsaw 2.2.2 and java 1.4.0_03, for use with JSPs on red hat linux 8... Here is a simple jsp page with a simple jsp:include...All Iam attempting is to add a footer to the JSP page... ... jsp:include page=common/footer.jsp flush=true .. Iam getting the following error when I run this page... org.apache.jasper.JasperException at org.apache.servlet.JspServletWrapper.service(JspServletWrapper.java:248) at org.apache.jasper.servlet.JspServlet.service.JspFile(JspServlet.java:295) at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:241) at javax.servlet.httpServlet.service(HttpServlet.java:83) at org.w3c.servlet.ServletWrapper$ServletRunner.run(ServletWrapper.java:542) at org.w3c.util.CachedThread.run(ThreadCache.java:87) Pls. note the following - 1. if the jsp:include is commented, the jsp works fine...So my settings, in general, seem fine... 2. the JSPs used in the include are shown as indexed in the JigAdmin UI... 3. the jsp file being included is a FileResource with ServletWrapperFrame... Any idea what the problem is? Any workarounds for this problem? Any help is highly appreciated... regards Durgadatt R Kamath
Re: include for server.xml
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sun, Feb 02, 2003 at 07:55:54PM -0500, Jeanfrancois Arcand wrote: Try this: !DOCTYPE blablabla [ !ENTITY coyoteConnector SYSTEM http://your_configuration.xml; ] Excellent, that works! and then reference it using Yep, I'd figured that out (helpful error message :) Thanks Jeanfrancois! Bye for now, Ward. -- Jeanfrancois Ward Vandewege wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hey thanks for that. Unfortunately, the Xerces doesn't seem to like the first line: !ENTITY coyoteConnector SYSTEM http://your_configuration.xml; Feb 2, 2003 11:22:56 PM org.apache.commons.digester.Digester fatalError SEVERE: Parse Fatal Error at line 1 column 3: The markup in the document preceding the root element must be well-formed. org.xml.sax.SAXParseException: The markup in the document preceding the root element must be well-formed. at org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:232) at org.apache.xerces.util.ErrorHandlerWrapper.fatalError(ErrorHandlerWrapper.java:213) at org.apache.xerces.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:375) at org.apache.xerces.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:305) at org.apache.xerces.impl.XMLScanner.reportFatalError(XMLScanner.java:1269) at org.apache.xerces.impl.XMLDocumentScannerImpl$PrologDispatcher.dispatch(XMLDocumentScannerImpl.java:681) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:329) at org.apache.xerces.parsers.DTDConfiguration.parse(DTDConfiguration.java:525) at org.apache.xerces.parsers.DTDConfiguration.parse(DTDConfiguration.java:581) at org.apache.xerces.parsers.XMLParser.parse(XMLParser.java:152) at org.apache.xerces.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1175) ... Any advice? bfn, Ward. On Sun, Feb 02, 2003 at 04:17:13PM -0500, Jeanfrancois Arcand wrote: There is no such concept associated with server.xml.But there is in XML :-) You can define an ENTITY element at the top of your server.xml file and reference it inside the body of the server element. Do something like this: !ENTITY coyoteConnector SYSTEM http://your_configuration.xml; and then inside the server element: server . coyoteConnector /server -- Jeanfrancois Ward Vandewege wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, I have a tomcat/apache setup with several virtual hosts. The information for the virtual hosts lives in a database. In the apache config file, I can just use the 'Include' directive to include my automatically generated configuration file (with all the virtual host definitions) in the httpd.conf. I've been looking all over the archives of this list, the jakarta site, and google, but have not been able to locate an equivalent for use in the server.xml file. Is there one? Bye for now, Ward. - -- Pong.be -( Those who do not understand Unix are condemned to )- Virtual hosting -( reinvent it, poorly. -- Henry Spencer )- http://pong.be -( )- GnuPG public key: http://gpg.dtype.org -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.0 (GNU/Linux) iD8DBQE+PYaBqC3O5tzmh5wRAsKtAJ9376Ne/7o9iX/oe0YwysUtSvNukACfTt3s JzWbEwo6Y+ETChW0FEWTZec= =a2/6 -END PGP SIGNATURE- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Ward Vandewege. - -- Pong.be -( The Linux philosophy is 'Laugh in the face of )- Virtual hosting -(danger'. Oops. Wrong One. 'Do it yourself'. Yes, )- http://pong.be -( that's it. -- Linus )- GnuPG public key: http://gpg.dtype.org -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.0 (GNU/Linux) iD8DBQE+PZp4qC3O5tzmh5wRAmCpAJ9ZUO9gR0dS0iSUBWEmeNqCFz2B8ACcDG41 m0z78XVHHraB6WcMc3tgkPU= =Q/4J -END PGP SIGNATURE- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - -- Pong.be -( Linux: Your Brain - Windows: Your brain on drugs)- Virtual hosting -( )- http://pong.be -( )- GnuPG public key: http://gpg.dtype.org -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.0 (GNU/Linux)
RE: more about custam tag life cycle
I'm curious, how you get a PageContext when the container doesn't call setPageContext? Which container have this behavior? What he meant is that it may not call setPageContext *on each invocation*. It will always be called at least once before doStartTag. But each invocation shouldn't get a different pagecontext? PageContext isn't something related to request's URL? I guess pagecontext's functionality isn't very clear to me... I don't see a reason why we should have pool-specific method for tag property cleaning. doFinally method is intended for tag cleaning... Probably when created it was intended for cleaning resources like database connections, etc but I don't see any reason to create yet another method just for tag reuse I think there might be some benefit in clarity to the tag developer. The current lifecycle behavior seems to confuse a lot of people (and I was certainly one of those people when I first started writing tag extensions). Yes, but add even more method would make it easier? Maybe just the way the current methods are defined in the docs should be changed. If you make it clear that doFinally() is ok for tag reuse cleaning, everybody will use it for this. But when I made a suggestion like that on the tomcat-dev list, it was pointed out that JSP 2.0 offers a new SimpleTag interface that will never be pooled, and is much more straightforward than the classic tag interface. Hopefully in the future most tags can use that interface instead, and the classic Tag interface can be reserved for the rare tags that benefit from reuse. Tag reusing is so rare to be useful at all? Why? -- Tim Moore / Blackboard Inc. / Software Engineer 1899 L Street, NW / 5th Floor / Washington, DC 20036 Phone 202-463-4860 ext. 258 / Fax 202-463-4863 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Felipe Schnack Analista de Sistemas [EMAIL PROTECTED] Cel.: (51)91287530 Linux Counter #281893 Centro Universitário Ritter dos Reis http://www.ritterdosreis.br [EMAIL PROTECTED] Fone/Fax.: (51)32303341 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Starting Tomcat as a service on 2000/NT
Is there any performance benefits if Tomcat is configures as a service on 2000/NT? Thanks -Manoj.
RE: more about custam tag life cycle
Tag reuse is only allowed when the set of attributes that are used, and their values, are identical. For example, the following two tags will *always* use different instances: foo:bar baz=a/ foo:bar baz=b/ because the attribute value is different. My understanding was that the same instance *could* be reused, as long as setBaz(b) is called between the first doEndTag and the second doStartTag. Am I mistaken? -- Tim Moore / Blackboard Inc. / Software Engineer 1899 L Street, NW / 5th Floor / Washington, DC 20036 Phone 202-463-4860 ext. 258 / Fax 202-463-4863 -Original Message- From: Craig R. McClanahan [mailto:[EMAIL PROTECTED]] Sent: Monday, February 03, 2003 2:37 PM To: Tomcat Users List Subject: Re: more about custam tag life cycle On Mon, 3 Feb 2003, Will Hartung wrote: Date: Mon, 3 Feb 2003 11:00:46 -0800 From: Will Hartung [EMAIL PROTECTED] Reply-To: Tomcat Users List [EMAIL PROTECTED] To: Tomcat Users List [EMAIL PROTECTED] Subject: Re: more about custam tag life cycle From: Felipe Schnack [EMAIL PROTECTED] Sent: Monday, February 03, 2003 10:12 AM Subject: RE: more about custam tag life cycle This makes me feel much better :-) On Mon, 2003-02-03 at 16:09, Tim Moore wrote: This is NOT true, AFAIK. The same tag instance can be used multiple times *sequentially* but not *concurrently*. Check out the lifecycle state diagram in the JSP spec. The way to look at it is simply that the generated code is going to use a tag pool for each distinct class of tags. Unfortunately, there is no specific action that tells the tag it is being pulled from or being put back from the pool. The page will call release() before it is put back in the pool. All tags follow the basic lifecycle of simpy constuctor setPageContext doStartTag doEndTag In the pooled environment, it's: constructor setPageContext doStartTag doEndTag doStartTag doEndTag etc. (I've seen some containers, I thinik Tomcat is one, that call setPageContext on each tag, but I've seen others that do not, so setPageContext is not a reliable method to reset the tag properties). If the tag implments the TryCatchFinally interface, then a doFinally is called after the doEndTag. This only helps in a JSP 1.2 container, and comes with at least some performance price due to the extra try/catch/finally block that the page compiler has to create. What's is non-obvious is that the doEndTag and doFinally are supposed to assume the role of cleaning the tag up for reuse. That is not what they are for. The purpose of doEndTag() is to finish up whatever processing your tag does, at the end of the closing tag on the page. You should not be modifying the attribute values that were set by the page anyway, so there should be no need to clean up here. The purpose of doFinally() is to deal with exceptions that were thrown within the body of your tag. You really do not want to spend the extra processor cycles when such exceptions do not occur, or don't matter to you. I particularly like this quote from the spec: The particular code shown below assumes there is some pool of tag handlers that are managed (details not described, although pool managing is simpler when there are no optional attributes), This entire problem, at least as I've encountered it, revolves around not only optional, but also contradictory tags (i.e. it's okay to specify paramter a, b, or c, but no combination in the same tag). There are really two issues here -- tag *pooling* (the container recycles a previous tag instance instead of creating a new one every time) and tag *reuse* (the container uses the same instance for more than one tag with identical attributes). It's entirely legal to have tag reuse even in a container that does not implement tag pooling, so you have to account for both possibilities. Tag reuse is only allowed when the set of attributes that are used, and their values, are identical. For example, the following two tags will *always* use different instances: foo:bar baz=a/ foo:bar baz=b/ because the attribute value is different. Likewise, the following two tags will *always* use different instances: foo:bar baz=a/ foo:bar bif=a/ because different attribues are used. However, the following tag instances *can* be reused (and smart developers will always program their tags as if they *will* be reused): foo:bar baz=a/ foo:bar baz=a/ If your container does implement tag pooling (in addition to or instead of tag reuse), it will call release() before returning the instance to the pool. That makes release() the right place to reset everything to defaults. And like I said earlier, it would be nice if there were a pool interface added to the lifecycle to clean up the tag processing
RE: more about custam tag life cycle
-Original Message- From: Felipe Schnack [mailto:[EMAIL PROTECTED]] Sent: Monday, February 03, 2003 2:46 PM To: Tomcat Users List Subject: RE: more about custam tag life cycle I'm curious, how you get a PageContext when the container doesn't call setPageContext? Which container have this behavior? What he meant is that it may not call setPageContext *on each invocation*. It will always be called at least once before doStartTag. But each invocation shouldn't get a different pagecontext? PageContext isn't something related to request's URL? I guess pagecontext's functionality isn't very clear to me... We're talking about reuse within a single page. I don't see a reason why we should have pool-specific method for tag property cleaning. doFinally method is intended for tag cleaning... Probably when created it was intended for cleaning resources like database connections, etc but I don't see any reason to create yet another method just for tag reuse I think there might be some benefit in clarity to the tag developer. The current lifecycle behavior seems to confuse a lot of people (and I was certainly one of those people when I first started writing tag extensions). Yes, but add even more method would make it easier? Maybe just the way the current methods are defined in the docs should be changed. If you make it clear that doFinally() is ok for tag reuse cleaning, everybody will use it for this. Except that it's not, really. But when I made a suggestion like that on the tomcat-dev list, it was pointed out that JSP 2.0 offers a new SimpleTag interface that will never be pooled, and is much more straightforward than the classic tag interface. Hopefully in the future most tags can use that interface instead, and the classic Tag interface can be reserved for the rare tags that benefit from reuse. Tag reusing is so rare to be useful at all? Why? Well I guess that's the conclusion they came to by JSP 2.0, and the rationale behind the SimpleTag interface. -- Tim Moore / Blackboard Inc. / Software Engineer 1899 L Street, NW / 5th Floor / Washington, DC 20036 Phone 202-463-4860 ext. 258 / Fax 202-463-4863 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Passing parameters to DB connection through web.xml/server.xml
I am using Oracle and I want to take advantage of the statement caching provided by the JDBC driver as well as the conneciton pooling provided by Tomcat through org.apache.commons.dbcp.BasicDataSourceFactory. I need to set/get the statement cache size (typically with calls to setStmtCacheSize and getStmtCacheSize) without doing so in the application code. Is there a way I can have BDSF pass values into the connection or am I stuck by tying the code to the db by using the getDelegate function in org.apache.commons.dbcp.DelegatingConnection? Thanks Andy Meadows - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: tomcat /apache2 / jk2 rewrites https:// requests as http://
I just had this same problem. Although I'm using mod_jk, but it should be same. You can create a virtual host in http.conf for port 80. You probably have a file called ssl.conf also for apache. It has a virtual host built in. You need to look at your tomcat/conf/auto/mod_jk.conf and take the appropriate lines and paste them into your http.conf and ssl.conf INSIDE VirtualHost tags. Particularly the JkMount directives. Then make sure you no longer have an include for that tomcat/conf/auto/mod_jk.conf file directly. Also make sure to have your DocumentRoot directives point to two different directories. Hopefully that works for you, if not I can give some more details. I'm currently documenting every step I need to do to install the following in RedHat 7.3: -JDK 1.4.0_01 (binary) -Tomcat 4.1.18 (binary) -Mod_jk Connector (binary) -Openssl 0.9.7 (source) -Apache/SSL/other modules/Virtual Host (source) -Struts -Ant -Postgresql 7.1.3 + JDBC (source) -Pgaccess (source) -Daemon scripts for all that run in /etc/rc.d/init.d/* I'll probably post it when I'm done. Good luck, Oscar On 3 Feb 2003, Aaron Elkiss wrote: Ok... What I want to do is have the tomcat root context accessible via https on /tomcat, running through apache2 with mod_jk2. Ok, no problem - jk2 is configured and running, the application paths in tomcat have all been changed to have /tomcat prepended. Maybe I should somehow use mod_rewrite instead, but this seems to work. I added the following in workers2.properties: [uri:/tomcat/*] info=Tomcat I can't figure out how to get this to apply only to the SSL virtual host in apache, but that's not a big deal - I can just deny access to that location from the non-SSL virtual host and allow access from the SSL host, or set up some kind of rule so that non-SSL requests get rewritten appropriately. The main problem is that if I go to https://somehost.umd.edu/tomcat, something feels the need to rewrite that to http://somehost.umd.edu:443/tomcat, which needless to say does not work. On the other hand, if there's no need to do any redirection, i.e. https://somehost.umd.edu/tomcat/index.jsp, everything works okay. What's going on here? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
classloader issues using ../common/lib vs. ../shared/lib
Are there any potential classloader problems with putting .jar files that are shared across webapps (ie. junit, cactus, etc) in ../common/lib vs. ../shared/lib? We've been tossing .jars into ../common/lib, but after reading the Tomcat classloader how-to it seems that's discouraged, ie. should be done only when the classes are needed both by Tomcat and applications such as db drivers for JDBC realm and application use. I'm guessing, but does putting the .jars in ../shared/lib would spread work out better between classloaders? Our application and integration tools are working great, but the fact we're not configured the way the how-to suggests concerns me. TIA - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
