Building tomcat-connectors with ANT
Has anyone been successful in this? The documentation seems to be very scarce to say the least. -SB - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Building tomcat-connectors with ANT
BATCHELOR, SCOTT (CONTRACTOR) wrote: Has anyone been successful in this? Yes. Regularly. 4.1.x, 5.0.x and 5.5.x Mark - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Building tomcat-connectors with ANT
Would you mind pointing me in the right direction for some docs? I really only want to build mod_jk Thanks, -SB -Original Message- From: Mark Thomas [mailto:[EMAIL PROTECTED] Sent: Monday, June 27, 2005 2:08 PM To: Tomcat Users List Subject: Re: Building tomcat-connectors with ANT BATCHELOR, SCOTT (CONTRACTOR) wrote: Has anyone been successful in this? Yes. Regularly. 4.1.x, 5.0.x and 5.5.x Mark - 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: Building tomcat-connectors with ANT
Ah. It wasn't clear from your original post which part of the connectors you were trying to build. I was referring to the Tomcat end of things (the Java AJP/HTTP connectors) rather than mod_jk. The following from the dev list might help. Failing that, with the clarification of what it is you want to do, someone else may pitch in with some help. http://marc.theaimsgroup.com/?l=tomcat-devm=50341215849w=2 Mark BATCHELOR, SCOTT (CONTRACTOR) wrote: Would you mind pointing me in the right direction for some docs? I really only want to build mod_jk Thanks, -SB -Original Message- From: Mark Thomas [mailto:[EMAIL PROTECTED] Sent: Monday, June 27, 2005 2:08 PM To: Tomcat Users List Subject: Re: Building tomcat-connectors with ANT BATCHELOR, SCOTT (CONTRACTOR) wrote: Has anyone been successful in this? Yes. Regularly. 4.1.x, 5.0.x and 5.5.x Mark - 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: Building tomcat-connectors with ANT
I must really be missing something? It was my understanding that using mod_jk-1-2-10.so was the same thing as using the ajp connector? Am I completely misinformed in this? -SB -Original Message- From: Mark Thomas [mailto:[EMAIL PROTECTED] Sent: Monday, June 27, 2005 3:08 PM To: Tomcat Users List Subject: Re: Building tomcat-connectors with ANT Ah. It wasn't clear from your original post which part of the connectors you were trying to build. I was referring to the Tomcat end of things (the Java AJP/HTTP connectors) rather than mod_jk. The following from the dev list might help. Failing that, with the clarification of what it is you want to do, someone else may pitch in with some help. http://marc.theaimsgroup.com/?l=tomcat-devm=50341215849w=2 Mark BATCHELOR, SCOTT (CONTRACTOR) wrote: Would you mind pointing me in the right direction for some docs? I really only want to build mod_jk Thanks, -SB -Original Message- From: Mark Thomas [mailto:[EMAIL PROTECTED] Sent: Monday, June 27, 2005 2:08 PM To: Tomcat Users List Subject: Re: Building tomcat-connectors with ANT BATCHELOR, SCOTT (CONTRACTOR) wrote: Has anyone been successful in this? Yes. Regularly. 4.1.x, 5.0.x and 5.5.x Mark - 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: Building tomcat-connectors with ANT
There are two parts to any connector that links Tomcat and a web server, a Java part and a native part. See http://jakarta.apache.org/tomcat/tomcat-4.1-doc/config/connectors.html for my attempt at a fuller explanation. Mark BATCHELOR, SCOTT (CONTRACTOR) wrote: I must really be missing something? It was my understanding that using mod_jk-1-2-10.so was the same thing as using the ajp connector? Am I completely misinformed in this? -SB -Original Message- From: Mark Thomas [mailto:[EMAIL PROTECTED] Sent: Monday, June 27, 2005 3:08 PM To: Tomcat Users List Subject: Re: Building tomcat-connectors with ANT Ah. It wasn't clear from your original post which part of the connectors you were trying to build. I was referring to the Tomcat end of things (the Java AJP/HTTP connectors) rather than mod_jk. The following from the dev list might help. Failing that, with the clarification of what it is you want to do, someone else may pitch in with some help. http://marc.theaimsgroup.com/?l=tomcat-devm=50341215849w=2 Mark BATCHELOR, SCOTT (CONTRACTOR) wrote: Would you mind pointing me in the right direction for some docs? I really only want to build mod_jk Thanks, -SB -Original Message- From: Mark Thomas [mailto:[EMAIL PROTECTED] Sent: Monday, June 27, 2005 2:08 PM To: Tomcat Users List Subject: Re: Building tomcat-connectors with ANT BATCHELOR, SCOTT (CONTRACTOR) wrote: Has anyone been successful in this? Yes. Regularly. 4.1.x, 5.0.x and 5.5.x Mark - 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: Building tomcat-connectors with ANT
Mark Thomas [EMAIL PROTECTED] wrote in message news:[EMAIL PROTECTED] Ah. It wasn't clear from your original post which part of the connectors you were trying to build. I was referring to the Tomcat end of things (the Java AJP/HTTP connectors) rather than mod_jk. The following from the dev list might help. Failing that, with the clarification of what it is you want to do, someone else may pitch in with some help. http://marc.theaimsgroup.com/?l=tomcat-devm=50341215849w=2 Yup. The Ant build of mod_jk isn't supported and I don't think that it has worked in a very long time. Use the configure/make option as outlined in the link above. Mark BATCHELOR, SCOTT (CONTRACTOR) wrote: Would you mind pointing me in the right direction for some docs? I really only want to build mod_jk Thanks, -SB -Original Message- From: Mark Thomas [mailto:[EMAIL PROTECTED] Sent: Monday, June 27, 2005 2:08 PM To: Tomcat Users List Subject: Re: Building tomcat-connectors with ANT BATCHELOR, SCOTT (CONTRACTOR) wrote: Has anyone been successful in this? Yes. Regularly. 4.1.x, 5.0.x and 5.5.x Mark - 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: tomcat connectors
Mladen, You are my hero! Setting connectionTimeout=2 to the AJP connector has resolved my accumulating threads and connections problem. --patty On Sat, 23 Apr 2005, Mladen Turk wrote: Date: Sat, 23 Apr 2005 10:21:27 +0200 From: Mladen Turk [EMAIL PROTECTED] Reply-To: Tomcat Users List tomcat-user@jakarta.apache.org To: Tomcat Users List tomcat-user@jakarta.apache.org Subject: Re: tomcat connectors Patty O'Reilly wrote: Thanks very much for responding. I'm still stuggling with an ever growing number of connections to the apache server and an ever growing number of threads on my tomcat server. I'm fairly certain it is not the application. I have all three timeouts set but no joy. worker.ifa-prod.jweb1.cachesize=1 worker.ifa-prod.jweb1.cache_timeout=600 worker.ifa-prod.jweb1.socket_keepalive=1 worker.ifa-prod.jweb1.socket_timeout=300 worker.ifa-prod.jweb1.recycle_timeout=300 You are probably using prefork mpm, so there is no way to control the number of connections to Tomcat in any way, trough mod_jk. You can limit it only by setting MaxClients in the httpd.conf to the maximum number desired. Because of pre-forking mechanism each child process will eventually establish a single connection to Tomcat, thus the number of connections will rise from StartServers to MaxClients. So there are two solutions for prefork. 1. Make maxThreads==MaxClients 2. Add connectionTimeout=2 to AJP connector. The leter one will recycle inactive connections, but degrade the performance. Regards, Mladen. - 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 connectors
First off, I really appreaciate your help. Many thanks. It looks like I am using the prefork module. $ ./httpd -l Compiled in modules: core.c prefork.c http_core.c mod_so.c MaxClients is set to 150 on apache. maxThreads in the tomcat server.xml is set to 150 as well, along with aditional threads: Connector acceptCount=100 connectionTimeout=2 disableUploadTimeout=true port=8140 redirectPort=8443 maxSpareThreads=75 maxThreads=150 minSpareThreads=25 I am going to change AJP connector and add the connectionTimeout that you suggested like this: Connector port=8142 protocol=AJP/1.3 protocolHandlerClassName=org.apache.jk.server.JkCoyoteHandler redirectPort=8443 connectionTimeout=2 /Connector I'm also going to bump maxThreads to 175. Tonight we are going to do some load testing. Fingers crossed. On Sat, 23 Apr 2005, Mladen Turk wrote: Date: Sat, 23 Apr 2005 10:21:27 +0200 From: Mladen Turk [EMAIL PROTECTED] Reply-To: Tomcat Users List tomcat-user@jakarta.apache.org To: Tomcat Users List tomcat-user@jakarta.apache.org Subject: Re: tomcat connectors Patty O'Reilly wrote: Thanks very much for responding. I'm still stuggling with an ever growing number of connections to the apache server and an ever growing number of threads on my tomcat server. I'm fairly certain it is not the application. I have all three timeouts set but no joy. worker.ifa-prod.jweb1.cachesize=1 worker.ifa-prod.jweb1.cache_timeout=600 worker.ifa-prod.jweb1.socket_keepalive=1 worker.ifa-prod.jweb1.socket_timeout=300 worker.ifa-prod.jweb1.recycle_timeout=300 You are probably using prefork mpm, so there is no way to control the number of connections to Tomcat in any way, trough mod_jk. You can limit it only by setting MaxClients in the httpd.conf to the maximum number desired. Because of pre-forking mechanism each child process will eventually establish a single connection to Tomcat, thus the number of connections will rise from StartServers to MaxClients. So there are two solutions for prefork. 1. Make maxThreads==MaxClients 2. Add connectionTimeout=2 to AJP connector. The leter one will recycle inactive connections, but degrade the performance. Regards, Mladen. - 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 connectors
Patty O'Reilly wrote: Thanks very much for responding. I'm still stuggling with an ever growing number of connections to the apache server and an ever growing number of threads on my tomcat server. I'm fairly certain it is not the application. I have all three timeouts set but no joy. worker.ifa-prod.jweb1.cachesize=1 worker.ifa-prod.jweb1.cache_timeout=600 worker.ifa-prod.jweb1.socket_keepalive=1 worker.ifa-prod.jweb1.socket_timeout=300 worker.ifa-prod.jweb1.recycle_timeout=300 You are probably using prefork mpm, so there is no way to control the number of connections to Tomcat in any way, trough mod_jk. You can limit it only by setting MaxClients in the httpd.conf to the maximum number desired. Because of pre-forking mechanism each child process will eventually establish a single connection to Tomcat, thus the number of connections will rise from StartServers to MaxClients. So there are two solutions for prefork. 1. Make maxThreads==MaxClients 2. Add connectionTimeout=2 to AJP connector. The leter one will recycle inactive connections, but degrade the performance. Regards, Mladen. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: tomcat connectors
Hi, As described here : http://jakarta.apache.org/tomcat/connectors-doc/config/workers.html the goal of socket_timeout is very different than recyle_timeout : socket_timeout is a timeout during the activity (between apache and tomcat) recycle_timeout is a timeout after the activity; when the exchanges between apache and tomcat are finished, the socket remains open during recycle_timeout of inactivity (this feature is close to cache_timeout). Regards. On Wed, 20 Apr 2005 17:30:32 -0700 (PDT) Patty O'Reilly [EMAIL PROTECTED] wrote: The descriptions of recycle_timeout and socket_timeout seem very similar in the Jakarta Tomcat Connector doc. Does anyone know when you would use one over the other, or should both directives be used together? I'm using 1.2.8 for Apache 2.0.52 + RHAS3. Many thanks --patty - 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 connectors
Thanks very much for responding. I'm still stuggling with an ever growing number of connections to the apache server and an ever growing number of threads on my tomcat server. I'm fairly certain it is not the application. I have all three timeouts set but no joy. worker.ifa-prod.jweb1.cachesize=1 worker.ifa-prod.jweb1.cache_timeout=600 worker.ifa-prod.jweb1.socket_keepalive=1 worker.ifa-prod.jweb1.socket_timeout=300 worker.ifa-prod.jweb1.recycle_timeout=300 --patty On Fri, 22 Apr 2005, Lionel Farbos wrote: Date: Fri, 22 Apr 2005 16:03:59 +0200 From: Lionel Farbos [EMAIL PROTECTED] To: Tomcat Users List tomcat-user@jakarta.apache.org Cc: [EMAIL PROTECTED] Subject: Re: tomcat connectors Hi, As described here : http://jakarta.apache.org/tomcat/connectors-doc/config/workers.html the goal of socket_timeout is very different than recyle_timeout : socket_timeout is a timeout during the activity (between apache and tomcat) recycle_timeout is a timeout after the activity; when the exchanges between apache and tomcat are finished, the socket remains open during recycle_timeout of inactivity (this feature is close to cache_timeout). Regards. On Wed, 20 Apr 2005 17:30:32 -0700 (PDT) Patty O'Reilly [EMAIL PROTECTED] wrote: The descriptions of recycle_timeout and socket_timeout seem very similar in the Jakarta Tomcat Connector doc. Does anyone know when you would use one over the other, or should both directives be used together? I'm using 1.2.8 for Apache 2.0.52 + RHAS3. Many thanks --patty - 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 connectors
The descriptions of recycle_timeout and socket_timeout seem very similar in the Jakarta Tomcat Connector doc. Does anyone know when you would use one over the other, or should both directives be used together? I'm using 1.2.8 for Apache 2.0.52 + RHAS3. Many thanks --patty - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Jakarta-tomcat-connectors-1.2.10-src error
I am getting error in error_log No JkShmFile defined in httpd.conf. LoadBalancer will not function properly! I am using new Jk Connector.. With tomcat 5.5.7 Jakarta connector -1.2.8 is working well with 5.5.7 on my other machine... ( so configuration is fine and working well ) Something has changed in new connector Any suggestion Vaneet Vaneet Sharma executive manager iDeasTank Limited an iwg business dolphins' court po 388 valletta, m-malta/europe mobile: +356 9943 8263 skype: CALLVANEET fax: +356 9952 phone: +356 9942 [EMAIL PROTECTED] call me on www.skype.com - my ID is CALLVANEET Want a signature like this? - www.plaxo.com\signature iwg is a global e-mobile company creating, building and growing new businesses. iwg founders are pioneers in creating multi-billion dollar mobile and Internet businesses in Europe, Asia and the US. www.iWG.info www.countryprofiler.com/iWG www.visitmalta.com www.mfc.com.mt Privileged/Confidential Information may be contained in this message. If you are not the addressee indicated in this message (or responsible for delivery of the message to such person), you may not copy or deliver this message to anyone. In such case, you should destroy this message and kindly notify the sender by reply email.
RE: Jakarta-tomcat-connectors-1.2.10-src error
This is introduced by jk 1.2.10. Simply add into your httpd.conf JkShmFile logs/mod_jk.shm shall fix this error. -Original Message- From: Vaneet Sharma [mailto:[EMAIL PROTECTED] Sent: April 4, 2005 8:54 AM To: Tomcat Users List Subject: Jakarta-tomcat-connectors-1.2.10-src error I am getting error in error_log No JkShmFile defined in httpd.conf. LoadBalancer will not function properly! I am using new Jk Connector.. With tomcat 5.5.7 Jakarta connector -1.2.8 is working well with 5.5.7 on my other machine... ( so configuration is fine and working well ) Something has changed in new connector Any suggestion Vaneet Vaneet Sharma executive manager iDeasTank Limited an iwg business dolphins' court po 388 valletta, m-malta/europe mobile: +356 9943 8263 skype: CALLVANEET fax: +356 9952 phone: +356 9942 [EMAIL PROTECTED] call me on www.skype.com - my ID is CALLVANEET Want a signature like this? - www.plaxo.com\signature iwg is a global e-mobile company creating, building and growing new businesses. iwg founders are pioneers in creating multi-billion dollar mobile and Internet businesses in Europe, Asia and the US. www.iWG.info www.countryprofiler.com/iWG www.visitmalta.com www.mfc.com.mt Privileged/Confidential Information may be contained in this message. If you are not the addressee indicated in this message (or responsible for delivery of the message to such person), you may not copy or deliver this message to anyone. In such case, you should destroy this message and kindly notify the sender by reply email. !DSPAM:42513bd2242272030513583!
[ANN] Jakarta Tomcat Connectors 1.2.8-rc-1 released
The Apache Jakarta Tomcat team is proud to announce the immediate availability of Jakarta Tomcat Connectors 1.2.8-rc-1 (Relase Canditate 1). We expect it to be ratified as a Stable release when the vote takes place in the next week. Please see the http://jakarta.apache.org/tomcat/connectors-doc/changelog.html for a full list of changes. You can download sources from: http://www.apache.org/dist/jakarta/tomcat-connectors/jk/source The binaries (for WIN32 only at the moment) are availabe at: http://www.apache.org/dist/jakarta/tomcat-connectors/jk/binaries/win32/ The Jakarta Tomcat Connectors Team - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[ANN] Jakarta Tomcat Connectors 1.2.7-beta-2 released
The Apache Jakarta Tomcat team is proud to announce the immediate availability of Jakarta Tomcat Connectors 1.2.7-beta-2. The release contains a fixes to few compilation problems detected with JK-1.2.7-beta version. This release also introduces a new domain concept clustering support. See Bugzilla #32317 for details. We expect it to be ratified as a Stable release when the vote takes place in the next two weeks. Please see the http://jakarta.apache.org/tomcat/connectors-doc/changelog.html for a full list of changes. This release since been declared as beta does not contain any binaries. The Jakarta Tomcat Connectors Team - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Content-Type rewriting in jakarta-tomcat-connectors
Hi again, Shapira, Yoav wrote: Hi, After upgrading from tomcat 4.1 to 5.0, a critical application here has It'd be a shame if the upgrade wasn't tested first in a test/QA environment ;( In 5.0.29, this comes out as Content-Type: application/xml;charset=utf-8 It's also interesting that you chose a beta version of Tomcat, as opposed to a stable version, for such an important application. However, that's irrelevant to this discussion. However, the key here is that the connector (more specifically around line 520 in jakarta-tomcat-connectors/coyote/src/java/org/apache/coyote/Response.ja va) is rewriting the carefully-constructed Content-Type string in a way that 1: I didn't ask for and 2: wasn't done in 4.1. So you've identified the specific location of the code you need to change. Given that it is highly unlikely that anyone at the other end is going to do anything about this any time soon, and given that the solution is very trivial (add a space in that string composer in Response.java), how are the chances of seeing this 'fixed' in an upcoming release of Tomcat 5.0.x? In an upcoming release, the chances are good. But we just released 5.0.30 so 5.0.31 won't happen in the next few days. So don't hold your breath, especially since it sounds like this is affecting a production instance. You could patch only the Response class, compile it, and put it in server/classes (which has priority over server/lib by definition), and that way fix the problem for your immediate needs in a custom but relatively effortless manner. Until now I have simply placed the tomcat-coyote.jar file into server/lib; this has worked fine. However, when following your suggestion (placing the modified Response.class in server/classes), the old behavior is seen again. It seems as if the server/classes directory is not included in the classpath used. Any idea what I've missed? Thanks, /Eirik You could also consider a Filter-based approach that sets the encoding including a charset: that way the connector won't have to rewrite/append the charset for you at all. And that way, your solution is portable and does not depend on a Tomcat release. As an aside, note that in general our implementation of these specs (HTTP, servlet, JSP) is stricter as Tomcat evolves. There are a number of things that worked in Tomcat 4.x that may not work (or work the same) in 5.x, so complete testing is a good idea when doing this major version upgrade. Yoav Shapira http://www.yoavshapira.com This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. 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: Content-Type rewriting in jakarta-tomcat-connectors
Hi, When you get a chance, please read http://www.river.com/users/share/etiquette/#quotes -- it's helpful and appreciated on this list ;) Until now I have simply placed the tomcat-coyote.jar file into server/lib; this has worked fine. However, when following your suggestion (placing the modified Response.class in server/classes), the old behavior is seen again. It seems as if the server/classes directory is not included in the classpath used. Any idea what I've missed? No idea what you've missed: that should work. If I take a class from a jar in server/lib, add a couple of System.out.println dummy statements, compile it, and put it in server/classes, it's loaded and I can see the output, so this works for me just fine. Yoav Shapira http://www.yoavshapira.com This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Content-Type rewriting in jakarta-tomcat-connectors
Shapira, Yoav wrote: Hi, When you get a chance, please read http://www.river.com/users/share/etiquette/#quotes -- it's helpful and appreciated on this list ;) I'm sorry; I'm following several mailing lists, and the etiquette expected varies slightly. I will keep this in mind ;) /Eirik - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Content-Type rewriting in jakarta-tomcat-connectors
On Thu, Dec 02, 2004 at 03:26:39PM +0100, Eirik ?verby wrote: : http://www.river.com/users/share/etiquette/#quotes -- it's helpful and : appreciated on this list ;) : : I'm sorry; I'm following several mailing lists, and the etiquette : expected varies slightly. I will keep this in mind ;) expected or enforced? ;) They aren't always the same. -QM -- software -- http://www.brandxdev.net tech news -- http://www.RoarNetworX.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Content-Type rewriting in jakarta-tomcat-connectors
Hi, After upgrading from tomcat 4.1 to 5.0, a critical application here has stopped working as expected. Upon replying to incoming requests, it would usually spit out the following - just like the servlet says: Content-Type: application/xml; charset=utf-8 In 5.0.29, this comes out as Content-Type: application/xml;charset=utf-8 In the second variant, the space between the ; and the charset string is gone. This breaks a *very* important service that we provide for a rather large credit card company. Without having studied RFCs and so on, I am pretty certain that it would be good coding-etiquette to have your app accept a Content-Type string with or without that space. Yes, I therefore know, it's their server - which sends the request to us - that has a lousy implementation. However, the key here is that the connector (more specifically around line 520 in jakarta-tomcat-connectors/coyote/src/java/org/apache/coyote/Response.java) is rewriting the carefully-constructed Content-Type string in a way that 1: I didn't ask for and 2: wasn't done in 4.1. Given that it is highly unlikely that anyone at the other end is going to do anything about this any time soon, and given that the solution is very trivial (add a space in that string composer in Response.java), how are the chances of seeing this 'fixed' in an upcoming release of Tomcat 5.0.x? I really would rather not have to maintain my own source for Tomcat - I've spent the better part of the last 6 months trying to wrestle the application we are running out of a customized environment and into a standardized one; this would go head-on with that effort.. :( Thanks for listening, /Eirik - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Content-Type rewriting in jakarta-tomcat-connectors
Eirik, Does it have anything to do with UTF-8 encoding support (using different charsets - Chinese or Japanese) on jsp page and would break (not displaying the non-english characters) on tomcat 5.0.29. Arnab -Original Message- From: Eirik Øverby [mailto:[EMAIL PROTECTED] Sent: Wednesday, December 01, 2004 11:15 PM To: [EMAIL PROTECTED] Subject: Content-Type rewriting in jakarta-tomcat-connectors Hi, After upgrading from tomcat 4.1 to 5.0, a critical application here has stopped working as expected. Upon replying to incoming requests, it would usually spit out the following - just like the servlet says: Content-Type: application/xml; charset=utf-8 In 5.0.29, this comes out as Content-Type: application/xml;charset=utf-8 In the second variant, the space between the ; and the charset string is gone. This breaks a *very* important service that we provide for a rather large credit card company. Without having studied RFCs and so on, I am pretty certain that it would be good coding-etiquette to have your app accept a Content-Type string with or without that space. Yes, I therefore know, it's their server - which sends the request to us - that has a lousy implementation. However, the key here is that the connector (more specifically around line 520 in jakarta-tomcat-connectors/coyote/src/java/org/apache/coyote/Response.java) is rewriting the carefully-constructed Content-Type string in a way that 1: I didn't ask for and 2: wasn't done in 4.1. Given that it is highly unlikely that anyone at the other end is going to do anything about this any time soon, and given that the solution is very trivial (add a space in that string composer in Response.java), how are the chances of seeing this 'fixed' in an upcoming release of Tomcat 5.0.x? I really would rather not have to maintain my own source for Tomcat - I've spent the better part of the last 6 months trying to wrestle the application we are running out of a customized environment and into a standardized one; this would go head-on with that effort.. :( Thanks for listening, /Eirik - 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: Content-Type rewriting in jakarta-tomcat-connectors
Hi, no, it is not related at all to the oft-discussed UTF-8 issues. This simply has to do with how the connector splits up the Content-Type string and then sews it together without adding a space after the ;. /Eirik Arnab Chakravarty wrote: Eirik, Does it have anything to do with UTF-8 encoding support (using different charsets - Chinese or Japanese) on jsp page and would break (not displaying the non-english characters) on tomcat 5.0.29. Arnab -Original Message- From: Eirik Øverby [mailto:[EMAIL PROTECTED] Sent: Wednesday, December 01, 2004 11:15 PM To: [EMAIL PROTECTED] Subject: Content-Type rewriting in jakarta-tomcat-connectors Hi, After upgrading from tomcat 4.1 to 5.0, a critical application here has stopped working as expected. Upon replying to incoming requests, it would usually spit out the following - just like the servlet says: Content-Type: application/xml; charset=utf-8 In 5.0.29, this comes out as Content-Type: application/xml;charset=utf-8 In the second variant, the space between the ; and the charset string is gone. This breaks a *very* important service that we provide for a rather large credit card company. Without having studied RFCs and so on, I am pretty certain that it would be good coding-etiquette to have your app accept a Content-Type string with or without that space. Yes, I therefore know, it's their server - which sends the request to us - that has a lousy implementation. However, the key here is that the connector (more specifically around line 520 in jakarta-tomcat-connectors/coyote/src/java/org/apache/coyote/Response.java) is rewriting the carefully-constructed Content-Type string in a way that 1: I didn't ask for and 2: wasn't done in 4.1. Given that it is highly unlikely that anyone at the other end is going to do anything about this any time soon, and given that the solution is very trivial (add a space in that string composer in Response.java), how are the chances of seeing this 'fixed' in an upcoming release of Tomcat 5.0.x? I really would rather not have to maintain my own source for Tomcat - I've spent the better part of the last 6 months trying to wrestle the application we are running out of a customized environment and into a standardized one; this would go head-on with that effort.. :( Thanks for listening, /Eirik - 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: Content-Type rewriting in jakarta-tomcat-connectors
Hi, Follow-up: The same happens when using Tomcat stand-alone - i.e. no Apache and no jk. /Eirik Eirik Øverby wrote: Hi, no, it is not related at all to the oft-discussed UTF-8 issues. This simply has to do with how the connector splits up the Content-Type string and then sews it together without adding a space after the ;. /Eirik Arnab Chakravarty wrote: Eirik, Does it have anything to do with UTF-8 encoding support (using different charsets - Chinese or Japanese) on jsp page and would break (not displaying the non-english characters) on tomcat 5.0.29. Arnab -Original Message- From: Eirik Øverby [mailto:[EMAIL PROTECTED] Sent: Wednesday, December 01, 2004 11:15 PM To: [EMAIL PROTECTED] Subject: Content-Type rewriting in jakarta-tomcat-connectors Hi, After upgrading from tomcat 4.1 to 5.0, a critical application here has stopped working as expected. Upon replying to incoming requests, it would usually spit out the following - just like the servlet says: Content-Type: application/xml; charset=utf-8 In 5.0.29, this comes out as Content-Type: application/xml;charset=utf-8 In the second variant, the space between the ; and the charset string is gone. This breaks a *very* important service that we provide for a rather large credit card company. Without having studied RFCs and so on, I am pretty certain that it would be good coding-etiquette to have your app accept a Content-Type string with or without that space. Yes, I therefore know, it's their server - which sends the request to us - that has a lousy implementation. However, the key here is that the connector (more specifically around line 520 in jakarta-tomcat-connectors/coyote/src/java/org/apache/coyote/Response.java) is rewriting the carefully-constructed Content-Type string in a way that 1: I didn't ask for and 2: wasn't done in 4.1. Given that it is highly unlikely that anyone at the other end is going to do anything about this any time soon, and given that the solution is very trivial (add a space in that string composer in Response.java), how are the chances of seeing this 'fixed' in an upcoming release of Tomcat 5.0.x? I really would rather not have to maintain my own source for Tomcat - I've spent the better part of the last 6 months trying to wrestle the application we are running out of a customized environment and into a standardized one; this would go head-on with that effort.. :( Thanks for listening, /Eirik - 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: Content-Type rewriting in jakarta-tomcat-connectors
Hi, After upgrading from tomcat 4.1 to 5.0, a critical application here has It'd be a shame if the upgrade wasn't tested first in a test/QA environment ;( In 5.0.29, this comes out as Content-Type: application/xml;charset=utf-8 It's also interesting that you chose a beta version of Tomcat, as opposed to a stable version, for such an important application. However, that's irrelevant to this discussion. However, the key here is that the connector (more specifically around line 520 in jakarta-tomcat-connectors/coyote/src/java/org/apache/coyote/Response.ja va) is rewriting the carefully-constructed Content-Type string in a way that 1: I didn't ask for and 2: wasn't done in 4.1. So you've identified the specific location of the code you need to change. Given that it is highly unlikely that anyone at the other end is going to do anything about this any time soon, and given that the solution is very trivial (add a space in that string composer in Response.java), how are the chances of seeing this 'fixed' in an upcoming release of Tomcat 5.0.x? In an upcoming release, the chances are good. But we just released 5.0.30 so 5.0.31 won't happen in the next few days. So don't hold your breath, especially since it sounds like this is affecting a production instance. You could patch only the Response class, compile it, and put it in server/classes (which has priority over server/lib by definition), and that way fix the problem for your immediate needs in a custom but relatively effortless manner. You could also consider a Filter-based approach that sets the encoding including a charset: that way the connector won't have to rewrite/append the charset for you at all. And that way, your solution is portable and does not depend on a Tomcat release. As an aside, note that in general our implementation of these specs (HTTP, servlet, JSP) is stricter as Tomcat evolves. There are a number of things that worked in Tomcat 4.x that may not work (or work the same) in 5.x, so complete testing is a good idea when doing this major version upgrade. Yoav Shapira http://www.yoavshapira.com This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Content-Type rewriting in jakarta-tomcat-connectors
Shapira, Yoav wrote: Hi, After upgrading from tomcat 4.1 to 5.0, a critical application here has It'd be a shame if the upgrade wasn't tested first in a test/QA environment ;( Well that's the thing.. It was tested, worked, but then the other end changed their stuff in a way that turned out to be incompatible. In any case, testing can always be better, and perhaps I should have hinted they should test with other Tomcat versions than 3.x and 4.x - so I accept partial responsibility here.. ;) In 5.0.29, this comes out as Content-Type: application/xml;charset=utf-8 It's also interesting that you chose a beta version of Tomcat, as opposed to a stable version, for such an important application. I was actually of the impression that 5.0.29 was *not* a beta release; possibly because it is the only current version available in the FreeBSD ports tree. I was also advised by the developer of the webapp that 5.0.29 had proven stable with their application, just like many previous releases of 5.0.x. Weird though, that 5.5.x is not in the FreeBSD ports tree, but that's not a discussion for this list. However, that's irrelevant to this discussion. Trueism. However, the key here is that the connector (more specifically around line 520 in jakarta-tomcat-connectors/coyote/src/java/org/apache/coyote/Response.ja va) is rewriting the carefully-constructed Content-Type string in a way that 1: I didn't ask for and 2: wasn't done in 4.1. So you've identified the specific location of the code you need to change. I have, and I have tested the change and found it to work. All prescribed test cases completed successfully. Given that it is highly unlikely that anyone at the other end is going to do anything about this any time soon, and given that the solution is very trivial (add a space in that string composer in Response.java), how are the chances of seeing this 'fixed' in an upcoming release of Tomcat 5.0.x? In an upcoming release, the chances are good. But we just released 5.0.30 so 5.0.31 won't happen in the next few days. So don't hold your breath, especially since it sounds like this is affecting a production instance. But you are saying 5.0.31 or 5.0.32 or something along those lines might see the change? That's certainly more encouraging than 'never' or '7.x' or anything like that. I will anyhow not take this for granted, only use it as input to the discussion that will arise as to what path we choose from here. You could patch only the Response class, compile it, and put it in server/classes (which has priority over server/lib by definition), and that way fix the problem for your immediate needs in a custom but relatively effortless manner. That might, indeed, be a good way to do it. Extracting it from the tomcat-coyote.jar file after a build would be sufficient? You could also consider a Filter-based approach that sets the encoding including a charset: that way the connector won't have to rewrite/append the charset for you at all. And that way, your solution is portable and does not depend on a Tomcat release. That's for the application developers to look into. I will certainly propose such an approach. As an aside, note that in general our implementation of these specs (HTTP, servlet, JSP) is stricter as Tomcat evolves. There are a number of things that worked in Tomcat 4.x that may not work (or work the same) in 5.x, so complete testing is a good idea when doing this major version upgrade. I have noticed, thanks.. And thanks for your input and time! /Eirik Yoav Shapira http://www.yoavshapira.com This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. 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: Content-Type rewriting in jakarta-tomcat-connectors
Hi, Well that's the thing.. It was tested, worked, but then the other end changed their stuff in a way that turned out to be incompatible. In any Gotta love it ;) I was actually of the impression that 5.0.29 was *not* a beta release; possibly because it is the only current version available in the FreeBSD ports tree. I don't know how the FreeBSD ports tree is managed, but 5.0.29 is beta, as is 5.0.30. 5.0.28 and 5.5.4 are stable. But you are saying 5.0.31 or 5.0.32 or something along those lines might see the change? Yes, that's what I'm saying. That might, indeed, be a good way to do it. Extracting it from the tomcat-coyote.jar file after a build would be sufficient? Yes. Yoav Shapira http://www.yoavshapira.com This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Content-Type rewriting in jakarta-tomcat-connectors
Hi again, Shapira, Yoav wrote: Hi, Well that's the thing.. It was tested, worked, but then the other end changed their stuff in a way that turned out to be incompatible. In any Gotta love it ;) I was actually of the impression that 5.0.29 was *not* a beta release; possibly because it is the only current version available in the FreeBSD ports tree. I don't know how the FreeBSD ports tree is managed, but 5.0.29 is beta, as is 5.0.30. 5.0.28 and 5.5.4 are stable. But you are saying 5.0.31 or 5.0.32 or something along those lines might see the change? Yes, that's what I'm saying. Anything I can do to increase the probability of this happening? Like, filing a bug report or feature request or whatever it should be called? Note that this also happens if you run Tomcat as a standalone HTTP/HTTPS server.. Thanks again. /Eirik That might, indeed, be a good way to do it. Extracting it from the tomcat-coyote.jar file after a build would be sufficient? Yes. Yoav Shapira http://www.yoavshapira.com This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. 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: Content-Type rewriting in jakarta-tomcat-connectors
Hi, Anything I can do to increase the probability of this happening? Like, filing a bug report or feature request or whatever it should be called? Note that this also happens if you run Tomcat as a standalone HTTP/HTTPS server.. You can file a bug report which would decrease the probability of us forgetting about the issue. But there's not much you can do to make a release happen faster. 5.0.x is not the focus of the development right now, 5.5 is, and we just made a couple of maintenance releases in 5.0.x which address the vast majority of its open issues. Yoav Shapira http://www.yoavshapira.com This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [ANN] Jakarta Tomcat Connectors 1.2.7-beta released
Cool! I'm anxious to try the wildchar uri matching. the regular expressions I'm using with JK2 aren't very complex, so this looks like it will do the trick. [EMAIL PROTECTED] 11/30/2004 9:24:44 AM The Apache Jakarta Tomcat team is proud to announce the immediate availability of Jakarta Tomcat Connectors 1.2.7-beta. The release contains a significant number of bug fixes and new features. We expect it to be ratified as a Stable release when the vote takes place in the next two weeks. Please see the http://jakarta.apache.org/tomcat/connectors-doc/changelog.html for a full list of changes. This release since been declared as beta does not contain any binaries. The Jakarta Tomcat Connectors Team - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Problems with jakarta-tomcat-connectors-jk2-2.0.[24]-src/jk/native2/configure and HP-UX 11.0
I cannot get the jk/native2/configure script that comes with
jakarta-tomcat-connectors-jk2-2.0.4-src (or jakarta-tomcat-connectors-jk2-2.0.2-src)
to work without errors under HP-UX 11.0. The problems occur when the script does
something like:
if ${TEST} ${apxs_support} = false ; then
or
if ${TEST} -z $tempval ; then
and the variable being tested has not been previously set. With 'set -x' turned on to
assist in debugging, the first test gives an error of:
+ /usr/bin/test = false
/usr/bin/test[7]: test: Specify a parameter with this command.
while the second ones gives:
+ /usr/bin/test -z
/usr/bin/test[7]: test: Specify a parameter with this command.
This style of variable checking is used extensively throughout the script. Short of
hacking each one to be something like:
if ${TEST} ${apxs_support}x = falsex ; then
or
if ${TEST} ${tempval}x = x ; then
does anyone have any ideas how I can get around this? Is this an autoconf issue?
I've tried re-generating the configure script using buildconf.sh by installing GNU
autoconf-2.58, automake-1.9.2 and libtool-1.5.8 but I get the same problems.
Mark A. Horstman
SBC Services, Inc.
St. Louis, MO 63101
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Request: Webpage update jakarta.apache.org/tomcat/connectors-doc /jk2/jk2/ for IIS-Setup
Hi Webmasters of that site, Some errors re: Setup on Windows/IIS/JK2 (2.0.4) took me a week to find out. Please correct! See resolved Bug [Bug 30383] Problem was that the Website was outdated. The info on http://jakarta.apache.org/tomcat/connectors-doc/jk2/jk2/ configwebcom.html#Common%20properties is invalid! It says that version is a common property, instead, it is ver. Also on http://jakarta.apache.org/tomcat/connectors-doc/jk2/jk2/installhowto.html#In stallation it says that the registry entry HKEY_LOCAL_MACHINE\SOFTWARE\Apache Software Foundation\Jakarta Isapi Redirector\2.0 - serverRoot has to point to the tomcat Installation. This does not apply to environments where the tomcat is on a different server. Instead, this entry HAS TO point to the dir where workers2.properties resides. Please update the Website or tell me where I can do it. Also, would be nice to update the IIS-Part of that site, a lot referes only to JK1, and IIS6 in IIS6-mode works too now. Last thing: The anchors on the side would work better when you would not use spaces in them. (e.g. ..m.html#Common%20properties - ...html#Common_properties or similar) -- Bjoern Andersen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Request: Webpage update jakarta.apache.org/tomcat/connectors-doc/jk2/jk2/ for IIS-Setup
Hi, OK, docs fixed in CVS. The next release will update the jakarta.apache.org site as well. Thanks for sending the corrections, Yoav Shapira Millennium Research Informatics -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 11, 2004 9:19 AM To: [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: Request: Webpage update jakarta.apache.org/tomcat/connectors- doc/jk2/jk2/ for IIS-Setup Hi Webmasters of that site, Some errors re: Setup on Windows/IIS/JK2 (2.0.4) took me a week to find out. Please correct! See resolved Bug [Bug 30383] Problem was that the Website was outdated. The info on http://jakarta.apache.org/tomcat/connectors-doc/jk2/jk2/ configwebcom.html#Common%20properties is invalid! It says that version is a common property, instead, it is ver. Also on http://jakarta.apache.org/tomcat/connectors- doc/jk2/jk2/installhowto.html#In stallation it says that the registry entry HKEY_LOCAL_MACHINE\SOFTWARE\Apache Software Foundation\Jakarta Isapi Redirector\2.0 - serverRoot has to point to the tomcat Installation. This does not apply to environments where the tomcat is on a different server. Instead, this entry HAS TO point to the dir where workers2.properties resides. Please update the Website or tell me where I can do it. Also, would be nice to update the IIS-Part of that site, a lot referes only to JK1, and IIS6 in IIS6-mode works too now. Last thing: The anchors on the side would work better when you would not use spaces in them. (e.g. ..m.html#Common%20properties - ...html#Common_properties or similar) -- Bjoern Andersen - 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]
Wrong Source-Codes for jakarta-tomcat-connectors-jk-1.2-src-curr ent.tar.gz ?
Hello everyone! Last time mailed I Had problems with jakarta-tomcat-connectors-jk-1.2-src-current.tar.gz, and I still have. I told you I found out that there ist a ':' too much in Makefile.in for the connector. I removed it, and then make works little better, but ends up with followig error: make: Fatal error: Command failed for target `mod_jk.lo' I did a -- # ls -la in /jk/native/apache-1.3/, and got following line: -- -rw-r--r-- 1 root other214 Jul 22 12:46 mod_jk.loT I had to -- # mv mod_jk.loT mod_jk.lo and after redoing -- # make it works somewhat better until this line (it still works!): -- (cd .libs rm -f mod_jk.la ln -s ../mod_jk.la mod_jk.la) but ends again with a different error in the next output lines on screen: -- /usr/local/bin/libtool --mode=install cp `pwd`/mod_jk.so -- libtool: install: you must specify a destination -- Try `libtool --help --mode=install' for more information. -- *** Error code 1 -- make: Fatal error: Command failed for target `mod_jk.so' -- # I am doing this compiling on solaris8 SPARC, with Apache 1.3.31, Tomcat 4.1.30 and java version 1.4.1_02 So, finally, here is my Question: Am I Doing sth. wrong, or did the developers just put damaged code on the website? (I downloaded it several times to reduce the chance of corruting code while downloading...) Did someone have any similar problem, or may it be that I just did make a big mistake? Thank each one in advance! - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Makefile for jakarta-tomcat-connectors-jk-1.2.5-src
Hello!
This is my first time ever being on a mailing list, so please forgive me mistakes, if
I do some...
I nearly got crazy while compiling jakarta-tomcat-connectors-jk-1.2.5-src to get
mod_jk.so on my Solaris 8 SPARC. I found many HowTo's, but none did work, I always got
following error message: (after I did the configure, of course)
--make: Fatal error in reader: Makefile, line 21: Unexpected end of line seen--
I took a look to Makefile in
jakarta-tomcat-connectors-jk-1.2.5-src/jk/native/apache-1.3, an made following change:
[EMAIL PROTECTED] # vi Makefile
...
OEXT=.lo
libexecdir=${APACHE_DIR}/libexec
--JK_DIR = .. instead of -- JK_DIR := ..
BUILD_DIR = ${JK_DIR}/../build/jk/apache13
Now I receive a different error:
make: Fatal error: Command failed for target `mod_jk.lo'
I didn't find any hint at google, so has anyone of you had a similar problem?
-- I also took a look to the source code after unpacking, an recognised that the
Makefile.in has the : at the same place,--
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
problem compiling jakarta-tomcat-connectors-jk2-2.0.4 native Module
Hi guys, I have given up trying to do anything with Ant. I found some instruction to build mod_jk2.so with configure scripts and the like. However, am coming across a problem which seems quite common, but can't find the fix in my instance. I am trying to compile on Tru64 using GNU Make (specially installed for this) and the latest Apache 2. I customise my make file to include CFLAGS -pthread. Here are my configure arguments: $ ./configure --with-apxs2=/usr/local/qut/bpr/httpd2/bin/apxs \ --with-tomcat41=/usr/local/qut/bpr/utils/jakarta-tomcat-4.1.30 \ --with-java-home=/usr/opt/java142 \ --with-apache2=/usr/local/qut/bpr/httpd2 I get the error at the bottom. I tried following the instructions at this site: http://www.linuxquestions.org/questions/showthread.php?s=threadid=171478 to no avail. What will end my struggle? Thanks. -- ranlib ../../../build/jk2/apache2/.libs/libmod_jk2.a creating ../../../build/jk2/apache2/mod_jk2.la (cd ../../../build/jk2/apache2/.libs rm -f mod_jk2.la ln -s ../mod_jk2.la mod_jk2.la) /usr/local/qut/bpr/httpd2/build/libtool --mode=install /sbin/cp ../../../build/jk2/apache2/mod_jk2.la `pwd`/../../../build/jk2/apache2//usr/local/qut/bpr/httpd2/modules /sbin/cp ../../../build/jk2/apache2/.libs/libmod_jk2.so /usr/local/qut/bpr/appsrc/jakarta-tomcat-connectors-jk2-2.0.4-src/jk/native2/server/apache2/../../../build/jk2/apache2//usr/local/qut/bpr/httpd2/modules/libmod_jk2.so /sbin/cp ../../../build/jk2/apache2/.libs/mod_jk2.lai /usr/local/qut/bpr/appsrc/jakarta-tomcat-connectors-jk2-2.0.4-src/jk/native2/server/apache2/../../../build/jk2/apache2//usr/local/qut/bpr/httpd2/modules/mod_jk2.la /sbin/cp ../../../build/jk2/apache2/.libs/libmod_jk2.a /usr/local/qut/bpr/appsrc/jakarta-tomcat-connectors-jk2-2.0.4-src/jk/native2/server/apache2/../../../build/jk2/apache2//usr/local/qut/bpr/httpd2/modules/libmod_jk2.a ranlib /usr/local/qut/bpr/appsrc/jakarta-tomcat-connectors-jk2-2.0.4-src/jk/native2/server/apache2/../../../build/jk2/apache2//usr/local/qut/bpr/httpd2/modules/libmod_jk2.a chmod 644 /usr/local/qut/bpr/appsrc/jakarta-tomcat-connectors-jk2-2.0.4-src/jk/native2/server/apache2/../../../build/jk2/apache2//usr/local/qut/bpr/httpd2/modules/libmod_jk2.a libtool: install: warning: remember to run `libtool --finish /usr/local/qut/bpr/httpd2/modules' /sbin/cp ../../../build/jk2/apache2//usr/local/qut/bpr/httpd2/modules/mod_jk2.so ../../../build/jk2/apache2/mod_jk2.so cp: ../../../build/jk2/apache2//usr/local/qut/bpr/httpd2/modules/mod_jk2.so: No such file or directory make[1]: *** [../../../build/jk2/apache2/mod_jk2.so] Error 1 make[1]: Leaving directory `/usr/local/qut/bpr/appsrc/jakarta-tomcat-connectors-jk2-2.0.4-src/jk/native2/server/apache2' make: *** [jk2-build] Error 1 -- Evan Read Business Process Consultant Call Center Section Information Technology Services Queensland University of Technology Phone: 3864 2160 (x2160) Email: [EMAIL PROTECTED] CRICOS No. 00213J - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Resend: [Fwd: problem compiling jakarta-tomcat-connectors-jk2-2.0.4 native Module]
Resend due to SPAM blockage. Thanks. -- Hi guys, I have given up trying to do anything with Ant. I found some instruction to build mod_jk2.so with configure scripts and the like. However, am coming across a problem which seems quite common, but can't find the fix in my instance. I am trying to compile on Tru64 using GNU Make (specially installed for this) and the latest Apache 2. I customise my make file to include CFLAGS -pthread. Here are my configure arguments: $ ./configure --with-apxs2=/usr/local/qut/bpr/httpd2/bin/apxs \ --with-tomcat41=/usr/local/qut/bpr/utils/jakarta-tomcat-4.1.30 \ --with-java-home=/usr/opt/java142 \ --with-apache2=/usr/local/qut/bpr/httpd2 I get the error at the bottom. I tried following the instructions at this site: http://www.linuxquestions.org/questions/showthread.php?s=threadid=171478 to no avail. What will end my struggle? Thanks. -- ranlib ../../../build/jk2/apache2/.libs/libmod_jk2.a creating ../../../build/jk2/apache2/mod_jk2.la (cd ../../../build/jk2/apache2/.libs rm -f mod_jk2.la ln -s ../mod_jk2.la mod_jk2.la) /usr/local/qut/bpr/httpd2/build/libtool --mode=install /sbin/cp ../../../build/jk2/apache2/mod_jk2.la `pwd`/../../../build/jk2/apache2//usr/local/qut/bpr/httpd2/modules /sbin/cp ../../../build/jk2/apache2/.libs/libmod_jk2.so /usr/local/qut/bpr/appsrc/jakarta-tomcat-connectors-jk2-2.0.4-src/jk/native2/server/apache2/../../../build/jk2/apache2//usr/local/qut/bpr/httpd2/modules/libmod_jk2.so /sbin/cp ../../../build/jk2/apache2/.libs/mod_jk2.lai /usr/local/qut/bpr/appsrc/jakarta-tomcat-connectors-jk2-2.0.4-src/jk/native2/server/apache2/../../../build/jk2/apache2//usr/local/qut/bpr/httpd2/modules/mod_jk2.la /sbin/cp ../../../build/jk2/apache2/.libs/libmod_jk2.a /usr/local/qut/bpr/appsrc/jakarta-tomcat-connectors-jk2-2.0.4-src/jk/native2/server/apache2/../../../build/jk2/apache2//usr/local/qut/bpr/httpd2/modules/libmod_jk2.a ranlib /usr/local/qut/bpr/appsrc/jakarta-tomcat-connectors-jk2-2.0.4-src/jk/native2/server/apache2/../../../build/jk2/apache2//usr/local/qut/bpr/httpd2/modules/libmod_jk2.a chmod 644 /usr/local/qut/bpr/appsrc/jakarta-tomcat-connectors-jk2-2.0.4-src/jk/native2/server/apache2/../../../build/jk2/apache2//usr/local/qut/bpr/httpd2/modules/libmod_jk2.a libtool: install: warning: remember to run `libtool --finish /usr/local/qut/bpr/httpd2/modules' /sbin/cp ../../../build/jk2/apache2//usr/local/qut/bpr/httpd2/modules/mod_jk2.so ../../../build/jk2/apache2/mod_jk2.so cp: ../../../build/jk2/apache2//usr/local/qut/bpr/httpd2/modules/mod_jk2.so: No such file or directory make[1]: *** [../../../build/jk2/apache2/mod_jk2.so] Error 1 make[1]: Leaving directory `/usr/local/qut/bpr/appsrc/jakarta-tomcat-connectors-jk2-2.0.4-src/jk/native2/server/apache2' make: *** [jk2-build] Error 1 -- Evan Read Business Process Consultant Call Center Section Information Technology Services Queensland University of Technology Phone: 3864 2160 (x2160) Email: [EMAIL PROTECTED] CRICOS No. 00213J -- Evan Read Business Process Consultant Call Center Section Information Technology Services Queensland University of Technology Phone: 3864 2160 (x2160) Email: [EMAIL PROTECTED] CRICOS No. 00213J - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Resend: [Fwd: problem compiling jakarta-tomcat-connectors-jk2-2.0.4 native Module]
I think you have a success. The error you're getting is at the very end of the build process after all the compiles and linking. Do a find for the mod_jk2.so file in your build directory. The error you saw could be because of the // in the middle of the source path for the cp command. --David Evan Read wrote: Resend due to SPAM blockage. Thanks. -- Hi guys, I have given up trying to do anything with Ant. I found some instruction to build mod_jk2.so with configure scripts and the like. However, am coming across a problem which seems quite common, but can't find the fix in my instance. I am trying to compile on Tru64 using GNU Make (specially installed for this) and the latest Apache 2. I customise my make file to include CFLAGS -pthread. Here are my configure arguments: $ ./configure --with-apxs2=/usr/local/qut/bpr/httpd2/bin/apxs \ --with-tomcat41=/usr/local/qut/bpr/utils/jakarta-tomcat-4.1.30 \ --with-java-home=/usr/opt/java142 \ --with-apache2=/usr/local/qut/bpr/httpd2 I get the error at the bottom. I tried following the instructions at this site: http://www.linuxquestions.org/questions/showthread.php?s=threadid=171478 to no avail. What will end my struggle? Thanks. -- ranlib ../../../build/jk2/apache2/.libs/libmod_jk2.a creating ../../../build/jk2/apache2/mod_jk2.la (cd ../../../build/jk2/apache2/.libs rm -f mod_jk2.la ln -s ../mod_jk2.la mod_jk2.la) /usr/local/qut/bpr/httpd2/build/libtool --mode=install /sbin/cp ../../../build/jk2/apache2/mod_jk2.la `pwd`/../../../build/jk2/apache2//usr/local/qut/bpr/httpd2/modules /sbin/cp ../../../build/jk2/apache2/.libs/libmod_jk2.so /usr/local/qut/bpr/appsrc/jakarta-tomcat-connectors-jk2-2.0.4-src/jk/native2/server/apache2/../../../build/jk2/apache2//usr/local/qut/bpr/httpd2/modules/libmod_jk2.so /sbin/cp ../../../build/jk2/apache2/.libs/mod_jk2.lai /usr/local/qut/bpr/appsrc/jakarta-tomcat-connectors-jk2-2.0.4-src/jk/native2/server/apache2/../../../build/jk2/apache2//usr/local/qut/bpr/httpd2/modules/mod_jk2.la /sbin/cp ../../../build/jk2/apache2/.libs/libmod_jk2.a /usr/local/qut/bpr/appsrc/jakarta-tomcat-connectors-jk2-2.0.4-src/jk/native2/server/apache2/../../../build/jk2/apache2//usr/local/qut/bpr/httpd2/modules/libmod_jk2.a ranlib /usr/local/qut/bpr/appsrc/jakarta-tomcat-connectors-jk2-2.0.4-src/jk/native2/server/apache2/../../../build/jk2/apache2//usr/local/qut/bpr/httpd2/modules/libmod_jk2.a chmod 644 /usr/local/qut/bpr/appsrc/jakarta-tomcat-connectors-jk2-2.0.4-src/jk/native2/server/apache2/../../../build/jk2/apache2//usr/local/qut/bpr/httpd2/modules/libmod_jk2.a libtool: install: warning: remember to run `libtool --finish /usr/local/qut/bpr/httpd2/modules' /sbin/cp ../../../build/jk2/apache2//usr/local/qut/bpr/httpd2/modules/mod_jk2.so ../../../build/jk2/apache2/mod_jk2.so cp: ../../../build/jk2/apache2//usr/local/qut/bpr/httpd2/modules/mod_jk2.so: No such file or directory make[1]: *** [../../../build/jk2/apache2/mod_jk2.so] Error 1 make[1]: Leaving directory `/usr/local/qut/bpr/appsrc/jakarta-tomcat-connectors-jk2-2.0.4-src/jk/native2/server/apache2' make: *** [jk2-build] Error 1 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Build Problem - jakarta-tomcat-connectors-4.1.30-src
Hi everyone. I am trying to build jakarta-tomcat-connectors-4.1.30-src.
I get the following errors (mainly unresolved symbols) and I am not
sure why. Obviously it can't find the right packages, but I thought the
Servlet Java stuff was implimented in Tomcat itself. Do I need another
package I can't find anywhere?
I have just pasted a sample of the errors. Most are identical. Missing
things from this javax.servlet package. I am running ant (properly
setup of course) from the jakarta-tomcat-connectors-4.1.30-src directory.
Thanks.
Evan
--
Buildfile: build.xml
build:
detect:
build-prepare:
build-main:
[echo] - Java-utils -
[echo] -- puretls.present = ${puretls.present}
[echo] -- jsse.present = true $/usr/opt/java142/jre/lib/jsse.jar
[echo] -- commons-logging = true
[echo] -- jmx = true
/usr/local/qut/bpr/utils/mx4j-2.0.1/lib/mx4j-jmx.jar
[echo] -- modeler = true
/usr/local/qut/bpr/utils/commons-modeler-1.1/commons-modeler.jar
[echo] -- JDK14 = true
init:
[echo] Coyote 1.0-dev
prepare:
static:
report-tc5:
[echo] Tomcat5 detected
report-tc4:
[echo] Tomcat4 detected
report-tc33:
report:
compile.shared:
compile.tomcat4:
[javac] Compiling 13 source files to
/usr/local/qut/bpr/appsrc/jakarta-tomcat-connectors-4.1.30-src/build/classes
[javac]
/usr/local/qut/bpr/appsrc/jakarta-tomcat-connectors-4.1.30-src/coyote/src/java/org/apache/coyote/tomcat4/CoyoteAdapter.java:68:
package javax.ser
vlet.http does not exist
[javac] import javax.servlet.http.Cookie;
[javac] ^
[javac]
/usr/local/qut/bpr/appsrc/jakarta-tomcat-connectors-4.1.30-src/coyote/src/java/org/apache/coyote/tomcat4/CoyoteAdapter.java:69:
package javax.ser
vlet.http does not exist
[javac] import javax.servlet.http.HttpServletRequest;
[javac] ^
[javac]
/usr/local/qut/bpr/appsrc/jakarta-tomcat-connectors-4.1.30-src/coyote/src/java/org/apache/coyote/tomcat4/CoyoteRequest.java:89:
package javax.ser
vlet does not exist
[javac] import javax.servlet.RequestDispatcher;
[javac] ^
[javac]
/usr/local/qut/bpr/appsrc/jakarta-tomcat-connectors-4.1.30-src/coyote/src/java/org/apache/coyote/tomcat4/CoyoteRequest.java:90:
package javax.ser
vlet does not exist
[javac] import javax.servlet.ServletContext;
[javac]
[javac]
/usr/local/qut/bpr/appsrc/jakarta-tomcat-connectors-4.1.30-src/coyote/src/java/org/apache/coyote/tomcat4/CoyoteRequest.java:91:
package javax.ser
vlet does not exist
[javac] import javax.servlet.ServletInputStream;
[javac] ^
[javac]
/usr/local/qut/bpr/appsrc/jakarta-tomcat-connectors-4.1.30-src/coyote/src/java/org/apache/coyote/tomcat4/CoyoteRequest.java:92:
package javax.ser
vlet does not exist
[javac] import javax.servlet.ServletRequest;
[javac] ^
[javac]
/usr/local/qut/bpr/appsrc/jakarta-tomcat-connectors-4.1.30-src/coyote/src/java/org/apache/coyote/tomcat4/CoyoteRequest.java:93:
package javax.ser
vlet.http does not exist
[javac] import javax.servlet.http.Cookie;
[javac] ^
[javac]
/usr/local/qut/bpr/appsrc/jakarta-tomcat-connectors-4.1.30-src/coyote/src/java/org/apache/coyote/tomcat4/CoyoteRequest.java:94:
package javax.ser
vlet.http does not exist
[javac] import javax.servlet.http.HttpServletRequest;
[javac] ^
[javac]
/usr/local/qut/bpr/appsrc/jakarta-tomcat-connectors-4.1.30-src/coyote/src/java/org/apache/coyote/tomcat4/CoyoteRequest.java:95:
package javax.ser
vlet.http does not exist
[javac] import javax.servlet.http.HttpServletResponse;
[javac] ^
[javac]
/usr/local/qut/bpr/appsrc/jakarta-tomcat-connectors-4.1.30-src/coyote/src/java/org/apache/coyote/tomcat4/CoyoteRequest.java:96:
package javax.ser
vlet.http does not exist
[javac] import javax.servlet.http.HttpSession;
[javac] ^
[javac]
/usr/local/qut/bpr/appsrc/jakarta-tomcat-connectors-4.1.30-src/coyote/src/java/org/apache/coyote/tomcat4/CoyoteRequest.java:125:
cannot resolve s
ymbol
[javac] symbol : class HttpServletRequest
[javac] location: class org.apache.coyote.tomcat4.CoyoteRequest
[javac] implements HttpRequest, HttpServletRequest {
[javac] ^
[javac]
/usr/local/qut/bpr/appsrc/jakarta-tomcat-connectors-4.1.30-src/coyote/src/java/org/apache/coyote/tomcat4/CoyoteRequest.java:186:
cannot resolve s
ymbol
[javac] symbol : class Cookie
[javac] location: class org.apache.coyote.tomcat4.CoyoteRequest
[javac] protected Cookie[] cookies = null;
[javac] ^
[javac]
/usr/local/qut/bpr/appsrc/jakarta-tomcat-connectors-4.1.30-src/coyote/src/java/org/apache/coyote/tomcat4/CoyoteInputStream.java:76:
cannot resolv
e symbol
[javac
RE: Build Problem - jakarta-tomcat-connectors-4.1.30-src
Do you have j2ee downloaded as well? As you know, It is looking for servlet
package. I am not sure where this package is set as classpath in your ant
script.
But you can try to apend this classpath to some classpath mentioned in your
ant scripts or else, try to set CLASSPATH in you evnvironment and tell me
:-)
-Original Message-
From: Evan Read [mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 09, 2004 8:51 AM
To: [EMAIL PROTECTED]
Subject: Build Problem - jakarta-tomcat-connectors-4.1.30-src
Hi everyone. I am trying to build jakarta-tomcat-connectors-4.1.30-src.
I get the following errors (mainly unresolved symbols) and I am not
sure why. Obviously it can't find the right packages, but I thought the
Servlet Java stuff was implimented in Tomcat itself. Do I need another
package I can't find anywhere?
I have just pasted a sample of the errors. Most are identical. Missing
things from this javax.servlet package. I am running ant (properly
setup of course) from the jakarta-tomcat-connectors-4.1.30-src directory.
Thanks.
Evan
--
Buildfile: build.xml
build:
detect:
build-prepare:
build-main:
[echo] - Java-utils -
[echo] -- puretls.present = ${puretls.present}
[echo] -- jsse.present = true $/usr/opt/java142/jre/lib/jsse.jar
[echo] -- commons-logging = true
[echo] -- jmx = true
/usr/local/qut/bpr/utils/mx4j-2.0.1/lib/mx4j-jmx.jar
[echo] -- modeler = true
/usr/local/qut/bpr/utils/commons-modeler-1.1/commons-modeler.jar
[echo] -- JDK14 = true
init:
[echo] Coyote 1.0-dev
prepare:
static:
report-tc5:
[echo] Tomcat5 detected
report-tc4:
[echo] Tomcat4 detected
report-tc33:
report:
compile.shared:
compile.tomcat4:
[javac] Compiling 13 source files to
/usr/local/qut/bpr/appsrc/jakarta-tomcat-connectors-4.1.30-src/build/classes
[javac]
/usr/local/qut/bpr/appsrc/jakarta-tomcat-connectors-4.1.30-src/coyote/src/ja
va/org/apache/coyote/tomcat4/CoyoteAdapter.java:68:
package javax.ser
vlet.http does not exist
[javac] import javax.servlet.http.Cookie;
[javac] ^
[javac]
/usr/local/qut/bpr/appsrc/jakarta-tomcat-connectors-4.1.30-src/coyote/src/ja
va/org/apache/coyote/tomcat4/CoyoteAdapter.java:69:
package javax.ser
vlet.http does not exist
[javac] import javax.servlet.http.HttpServletRequest;
[javac] ^
[javac]
/usr/local/qut/bpr/appsrc/jakarta-tomcat-connectors-4.1.30-src/coyote/src/ja
va/org/apache/coyote/tomcat4/CoyoteRequest.java:89:
package javax.ser
vlet does not exist
[javac] import javax.servlet.RequestDispatcher;
[javac] ^
[javac]
/usr/local/qut/bpr/appsrc/jakarta-tomcat-connectors-4.1.30-src/coyote/src/ja
va/org/apache/coyote/tomcat4/CoyoteRequest.java:90:
package javax.ser
vlet does not exist
[javac] import javax.servlet.ServletContext;
[javac]
[javac]
/usr/local/qut/bpr/appsrc/jakarta-tomcat-connectors-4.1.30-src/coyote/src/ja
va/org/apache/coyote/tomcat4/CoyoteRequest.java:91:
package javax.ser
vlet does not exist
[javac] import javax.servlet.ServletInputStream;
[javac] ^
[javac]
/usr/local/qut/bpr/appsrc/jakarta-tomcat-connectors-4.1.30-src/coyote/src/ja
va/org/apache/coyote/tomcat4/CoyoteRequest.java:92:
package javax.ser
vlet does not exist
[javac] import javax.servlet.ServletRequest;
[javac] ^
[javac]
/usr/local/qut/bpr/appsrc/jakarta-tomcat-connectors-4.1.30-src/coyote/src/ja
va/org/apache/coyote/tomcat4/CoyoteRequest.java:93:
package javax.ser
vlet.http does not exist
[javac] import javax.servlet.http.Cookie;
[javac] ^
[javac]
/usr/local/qut/bpr/appsrc/jakarta-tomcat-connectors-4.1.30-src/coyote/src/ja
va/org/apache/coyote/tomcat4/CoyoteRequest.java:94:
package javax.ser
vlet.http does not exist
[javac] import javax.servlet.http.HttpServletRequest;
[javac] ^
[javac]
/usr/local/qut/bpr/appsrc/jakarta-tomcat-connectors-4.1.30-src/coyote/src/ja
va/org/apache/coyote/tomcat4/CoyoteRequest.java:95:
package javax.ser
vlet.http does not exist
[javac] import javax.servlet.http.HttpServletResponse;
[javac] ^
[javac]
/usr/local/qut/bpr/appsrc/jakarta-tomcat-connectors-4.1.30-src/coyote/src/ja
va/org/apache/coyote/tomcat4/CoyoteRequest.java:96:
package javax.ser
vlet.http does not exist
[javac] import javax.servlet.http.HttpSession;
[javac] ^
[javac]
/usr/local/qut/bpr/appsrc/jakarta-tomcat-connectors-4.1.30-src/coyote/src/ja
va/org/apache/coyote/tomcat4/CoyoteRequest.java:125:
cannot resolve s
ymbol
[javac] symbol : class HttpServletRequest
[javac] location: class org.apache.coyote.tomcat4.CoyoteRequest
[javac] implements HttpRequest
Re: Build Problem - jakarta-tomcat-connectors-4.1.30-src
Hey,
Thanks for the pointer. I am on Tru64 which doesn't provide a J2EE but
I was able to downloaded the classes anyway and add them to my class path.
I am following some instructions for getting the connector working and I
am expecting a jtc.jar file to be created when running ant in the
connectors source directory.
The Build is now successful (with your help) but this file is not being
created. Do I need something further defined?
Thanks for your help.
Kommuru, Bhaskar wrote:
Do you have j2ee downloaded as well? As you know, It is looking for servlet
package. I am not sure where this package is set as classpath in your ant
script.
But you can try to apend this classpath to some classpath mentioned in your
ant scripts or else, try to set CLASSPATH in you evnvironment and tell me
:-)
-Original Message-
From: Evan Read [mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 09, 2004 8:51 AM
To: [EMAIL PROTECTED]
Subject: Build Problem - jakarta-tomcat-connectors-4.1.30-src
Hi everyone. I am trying to build jakarta-tomcat-connectors-4.1.30-src.
I get the following errors (mainly unresolved symbols) and I am not
sure why. Obviously it can't find the right packages, but I thought the
Servlet Java stuff was implimented in Tomcat itself. Do I need another
package I can't find anywhere?
I have just pasted a sample of the errors. Most are identical. Missing
things from this javax.servlet package. I am running ant (properly
setup of course) from the jakarta-tomcat-connectors-4.1.30-src directory.
Thanks.
Evan
--
Buildfile: build.xml
build:
detect:
build-prepare:
build-main:
[echo] - Java-utils -
[echo] -- puretls.present = ${puretls.present}
[echo] -- jsse.present = true $/usr/opt/java142/jre/lib/jsse.jar
[echo] -- commons-logging = true
[echo] -- jmx = true
/usr/local/qut/bpr/utils/mx4j-2.0.1/lib/mx4j-jmx.jar
[echo] -- modeler = true
/usr/local/qut/bpr/utils/commons-modeler-1.1/commons-modeler.jar
[echo] -- JDK14 = true
init:
[echo] Coyote 1.0-dev
prepare:
static:
report-tc5:
[echo] Tomcat5 detected
report-tc4:
[echo] Tomcat4 detected
report-tc33:
report:
compile.shared:
compile.tomcat4:
[javac] Compiling 13 source files to
/usr/local/qut/bpr/appsrc/jakarta-tomcat-connectors-4.1.30-src/build/classes
[javac]
/usr/local/qut/bpr/appsrc/jakarta-tomcat-connectors-4.1.30-src/coyote/src/ja
va/org/apache/coyote/tomcat4/CoyoteAdapter.java:68:
package javax.ser
vlet.http does not exist
[javac] import javax.servlet.http.Cookie;
[javac] ^
[javac]
/usr/local/qut/bpr/appsrc/jakarta-tomcat-connectors-4.1.30-src/coyote/src/ja
va/org/apache/coyote/tomcat4/CoyoteAdapter.java:69:
package javax.ser
vlet.http does not exist
[javac] import javax.servlet.http.HttpServletRequest;
[javac] ^
[javac]
/usr/local/qut/bpr/appsrc/jakarta-tomcat-connectors-4.1.30-src/coyote/src/ja
va/org/apache/coyote/tomcat4/CoyoteRequest.java:89:
package javax.ser
vlet does not exist
[javac] import javax.servlet.RequestDispatcher;
[javac] ^
[javac]
/usr/local/qut/bpr/appsrc/jakarta-tomcat-connectors-4.1.30-src/coyote/src/ja
va/org/apache/coyote/tomcat4/CoyoteRequest.java:90:
package javax.ser
vlet does not exist
[javac] import javax.servlet.ServletContext;
[javac]
[javac]
/usr/local/qut/bpr/appsrc/jakarta-tomcat-connectors-4.1.30-src/coyote/src/ja
va/org/apache/coyote/tomcat4/CoyoteRequest.java:91:
package javax.ser
vlet does not exist
[javac] import javax.servlet.ServletInputStream;
[javac] ^
[javac]
/usr/local/qut/bpr/appsrc/jakarta-tomcat-connectors-4.1.30-src/coyote/src/ja
va/org/apache/coyote/tomcat4/CoyoteRequest.java:92:
package javax.ser
vlet does not exist
[javac] import javax.servlet.ServletRequest;
[javac] ^
[javac]
/usr/local/qut/bpr/appsrc/jakarta-tomcat-connectors-4.1.30-src/coyote/src/ja
va/org/apache/coyote/tomcat4/CoyoteRequest.java:93:
package javax.ser
vlet.http does not exist
[javac] import javax.servlet.http.Cookie;
[javac] ^
[javac]
/usr/local/qut/bpr/appsrc/jakarta-tomcat-connectors-4.1.30-src/coyote/src/ja
va/org/apache/coyote/tomcat4/CoyoteRequest.java:94:
package javax.ser
vlet.http does not exist
[javac] import javax.servlet.http.HttpServletRequest;
[javac] ^
[javac]
/usr/local/qut/bpr/appsrc/jakarta-tomcat-connectors-4.1.30-src/coyote/src/ja
va/org/apache/coyote/tomcat4/CoyoteRequest.java:95:
package javax.ser
vlet.http does not exist
[javac] import javax.servlet.http.HttpServletResponse;
[javac] ^
[javac]
/usr/local/qut/bpr/appsrc/jakarta-tomcat-connectors-4.1.30-src/coyote/src/ja
va/org/apache/coyote/tomcat4/CoyoteRequest.java:96
jakarta-tomcat-connectors 2.0.4 binary file for windows is not available on the apache site
The Windows Binary JK2 zip file contains the binary Unix file, mod_jk2.so, and not mod_jk2.dll. (http://apache.mirror.positive-internet.com/jakarta/tomcat-conn ectors/jk2/binaries/win32/jakarta-tomcat-connectors-jk2.0.4-win32-apache2.0.49.zip). Where can I get the correct binary files for the jk2 connector for windows, that contains mod_jk2.dll? Any help you can give would be great!! Thanks. Regards, Doris - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: jakarta-tomcat-connectors 2.0.4 binary file for windows is not available on the apache site
I had similar problem today and did google search. The following url has mod_jk2 module (against Apache2.0.48 build) for Windows: http://downloads.esri.com/support/techArticles/IMS/tomcat4129_Windows/Tomcat4129_Apache2048_IMS9_win.zip I tried this one with Apache 2.0.48 and it works. For older mod_jk2 module: http://jakarta.apache.org/builds/jakarta-tomcat-connectors/jk2/release/v2.0.2/bin/win32/mod_jk2-2.0.43.dll Regards, Tim -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Monday, April 19, 2004 4:39 AM To: [EMAIL PROTECTED] Subject: jakarta-tomcat-connectors 2.0.4 binary file for windows is not available on the apache site The Windows Binary JK2 zip file contains the binary Unix file, mod_jk2.so, and not mod_jk2.dll. (http://apache.mirror.positive-internet.com/jakarta/tomcat-conn ectors/jk2/binaries/win32/jakarta-tomcat-connectors-jk2.0.4-win32-apache2.0.49.zip). Where can I get the correct binary files for the jk2 connector for windows, that contains mod_jk2.dll? Any help you can give would be great!! Thanks. Regards, Doris - 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]
build problem with jakarta-tomcat-connectors
Hi all, I am trying to build an initial install of tomcat and am getting the following error during 'ant dist'. It would seem that I need a build.properties in the jakarta-comcat-connectors/util directory, but I don't know the first place to start to either build one from scratch or if there is boiler-plate version somewhere. Any suggestions would be very helpful. Thanks, Brendan -- ant -v dist -- lots of stuff deleted- build-tomcat-util: Project base dir set to: /export/home/local/jakarta-tomcat-connectors/util [ant] calling target build-main in build file /export/home/local/jakarta-tomcat-connectors/util/build.xml parsing buildfile /export/home/local/jakarta-tomcat-connectors/util/build.xml with URI = file:/export/home/local/jakarta-tomcat-connectors/util/build.xml Project base dir set to: /export/home/local/jakarta-tomcat-connectors/util [property] Loading /export/home/local/jakarta-tomcat-connectors/util/build.properties Override ignored for property compile.debug [property] Loading /build.properties [property] Unable to find property file: /build.properties BUILD FAILED file:/export/home/local/jakarta-tomcat-4.1.30/catalina/build.xml:795: Target `build-main' does not exist in this project. at org.apache.tools.ant.Project.tsort(Project.java:1718) at org.apache.tools.ant.Project.topoSort(Project.java:1640) at org.apache.tools.ant.Project.executeTarget(Project.java:1299) at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:371) at org.apache.tools.ant.Task.perform(Task.java:319) at org.apache.tools.ant.Target.execute(Target.java:309) at org.apache.tools.ant.Target.performTasks(Target.java:336) at org.apache.tools.ant.Project.executeTarget(Project.java:1306) at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:371) at org.apache.tools.ant.Task.perform(Task.java:319) at org.apache.tools.ant.Target.execute(Target.java:309) at org.apache.tools.ant.Target.performTasks(Target.java:336) at org.apache.tools.ant.Project.executeTarget(Project.java:1306) at org.apache.tools.ant.Project.executeTargets(Project.java:1250) at org.apache.tools.ant.Main.runBuild(Main.java:610) at org.apache.tools.ant.Main.start(Main.java:196) at org.apache.tools.ant.Main.main(Main.java:235) Total time: 7 seconds - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: bad signature for jakarta-tomcat-connectors-jk2-2.0.2-src.tar.gz
Eric Emminger wrote, On 1/24/2004 12:25 PM: I'm trying to verify the signature of jakarta-tomcat-connectors-jk2-2.0.2-src.tar.gz, but gpg says public key not found. I DID import the KEYS from http://www.apache.org/dist/jakarta/tomcat-connectors/KEYS. Here's the output of the gpg verify command. $ gpg --verify jakarta-tomcat-connectors-jk2-2.0.2-src.tar.gz.asc gpg: Signature made Wed Nov 27 03:15:54 2002 EST using DSA key ID 881EBC94 gpg: Can't check signature: public key not found Looks like that is an old key of Mladen Turk, so he probably accidently used an old key instead of his new one, or something fishy is going on. Google for 881EBC94 and you'll find his old key. Better bring this up on the -dev list. -Dave - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
bad signature for jakarta-tomcat-connectors-jk2-2.0.2-src.tar.gz
I'm trying to verify the signature of jakarta-tomcat-connectors-jk2-2.0.2-src.tar.gz, but gpg says public key not found. I DID import the KEYS from http://www.apache.org/dist/jakarta/tomcat-connectors/KEYS. Here's the output of the gpg verify command. $ gpg --verify jakarta-tomcat-connectors-jk2-2.0.2-src.tar.gz.asc gpg: Signature made Wed Nov 27 03:15:54 2002 EST using DSA key ID 881EBC94 gpg: Can't check signature: public key not found I'd appreciate any help. Also, why doesn't a binary exist for linux? Eric - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Building jakarta-tomcat-connectors-jk2-2.0.2-src [HOW?]
Carlos Cajina - Hotmail wrote: Hi everyone. Tryin' to build mod_jk2 for my Slackware box (version 9.1 with reiserfs) I've come to a dead-end, and I would appreciate any help since the documentation I've looked into (including the mailing lists) seems to be out of date regarding the building process for version 2.0.2 of the Jakarta-Tomcat-Connectors. ...snip... This worked like a charm for me... http://marc.theaimsgroup.com/?l=tomcat-userm=105103815630094w=2 Also see Ian Harwood's work: http://marc.theaimsgroup.com/?l=tomcat-userm=107321319222031w=2 I also got it to build on Mac OS X Panther: http://forums.serverlogistics.com/viewtopic.php?t=644 Hope any of these helps. Tim - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Building jakarta-tomcat-connectors-jk2-2.0.2-src [HOW?]
Hi everyone. Tryin' to build mod_jk2 for my Slackware box (version 9.1 with reiserfs) I've come to a dead-end, and I would appreciate any help since the documentation I've looked into (including the mailing lists) seems to be out of date regarding the building process for version 2.0.2 of the Jakarta-Tomcat-Connectors. Please consider the necessary enviroment variables set up as follows: JTC_HOME = /usr/src/jakarta-tomcat-connectors-jk2-2.0.2-src/ JAVA_HOME = /usr/local/java/j2sdk1.4.2_03 TOMCAT_HOME = /usr/local/tomcat/jakarta-tomcat-4.1.29 APACHE2_HOME = /usr/local/apache2 ANT_HOME = /usr/local/ant/apache-ant-1.5.4 In order to successfully run the Ant build file I had to: 1. Modify the provided $JTC_HOME/jk/build.properties.sample to match my enviroment (set up paths, basically) 2. Create an empty 'java' directory inside $JTC_HOME/jk 3. Create the following directory structure inside $JTC_HOME: 'coyote/build/lib' 4. Copy every $TOMCAT_HOME/server/lib/*.jar file into $JTC_HOME/coyote/build/lib After the build process, the necessary files to actually generate the *.so module file for the JK2 connector are left in $JTC_HOME/jk/native2/server/apache2 I assumed that the 'Makefile.in' file was the one to be renamed as 'Makefile' in order tu run make, so I did renamed it and executed make but got the following output: mkdir -p ../../../build/jk2/apache2 make: APACHE2_HOME@/build/libtool: Command not found make: *** [../../../build/jk2/apache2/jk_channel.lo] Error 127 Apparently, the APACHE2_HOME@ variable was the source of the problem, so I went and modified the Makefile changing [EMAIL PROTECTED]@ into APACHE2_HOME=/usr/local/apache2 That solved the problem, but then another one came up. When executing make again, I got the folling output: mkdir -p ../../../build/jk2/apache2 /usr/local/apache2/build/libtool --mode=compile @CC@ @APXS2_CFLAGS@ @APXS2_CPPFLAGS@ -I../../include @APACHE2_INCL@ @APR_CFLAGS@ -I @JAVA_HOME@/include -I @JAVA_HOME@/include/@OS@ -DCHUNK_SIZE=4096 -DUSE_APACHE_MD5 -DHAS_APR @HAVE_JNI@ @HAS_PCRE@ -c ./../common/jk_channel.c -o ../../../build/jk2/apache2/jk_channel.lo rm -f ../../../build/jk2/apache2/.libs/jk_channel.lo @CC@ @APXS2_CFLAGS@ @APXS2_CPPFLAGS@ -I../../include @APACHE2_INCL@ @APR_CFLAGS@ -I @JAVA_HOME@/include -I @JAVA_HOME@/include/@OS@ -DCHUNK_SIZE=4096 -DUSE_APACHE_MD5 -DHAS_APR @HAVE_JNI@ @HAS_PCRE@ -c ./../common/jk_channel.c -fPIC -DPIC -o ./../../build/jk2/apache2/.libs/jk_channel.lo /usr/local/apache2/build/libtool: line 1: @CC@: command not found make: *** [../../../build/jk2/apache2/jk_channel.lo] Error 1 Its seemed that the problem was now with the @CC@ variable -which I think should point to /usr/bin/cc. I used the same reasoning as before I changed [EMAIL PROTECTED]@ for CC=/usr/bin/cc, but got an error message pretty much like the last one except for the two last lines: .. cc: cannot specify -o with -c or -S and multiple compilations make: *** [../../../build/jk2/apache2/jk_channel.lo] Error 1 ...And finally Here's where I'm stalled :-( Any help will be geratly appreciated. Regards, Carlos
Re: Building jakarta-tomcat-connectors-jk2-2.0.2-src [HOW?]
Carlos, See my recent mail message concerning mod_jk2 doesn't make jk2.socket. It has an abreviated configure, compile, and install for mod_jk2 contained in it. Basically, don't use ant to compile just the native portion of the connector. Go to the subdirectory native/jk2, run configure, and then run make. Then switch to the build/jk2/apache2 directory and copy the resulting .so files to the modules location. Please read the other mail message for configure, environment, and Makefile alterations that are required to get this all to work. HTH /mde/ just my two cents . . . . __ Do you Yahoo!? Yahoo! Hotjobs: Enter the Signing Bonus Sweepstakes http://hotjobs.sweepstakes.yahoo.com/signingbonus - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Building jakarta-tomcat-connectors-jk2-2.0.2-src [HOW?]
Howdy, I don't deal with the connectors, much less building them, but just from a generic unix point of view isn't Makefile.in a feeder into a configure script to be run before make? You need to run configure, which will diagnose your system and create a normal Makefile from the Makefile.in template, with the variables properly substituted. Just a guess. Yoav Shapira Millennium ChemInformatics -Original Message- From: Carlos Cajina - Hotmail [mailto:[EMAIL PROTECTED] Sent: Friday, January 09, 2004 3:14 PM To: Tomcat Users List Subject: Building jakarta-tomcat-connectors-jk2-2.0.2-src [HOW?] Hi everyone. Tryin' to build mod_jk2 for my Slackware box (version 9.1 with reiserfs) I've come to a dead-end, and I would appreciate any help since the documentation I've looked into (including the mailing lists) seems to be out of date regarding the building process for version 2.0.2 of the Jakarta-Tomcat-Connectors. Please consider the necessary enviroment variables set up as follows: JTC_HOME = /usr/src/jakarta-tomcat-connectors-jk2-2.0.2-src/ JAVA_HOME = /usr/local/java/j2sdk1.4.2_03 TOMCAT_HOME = /usr/local/tomcat/jakarta-tomcat-4.1.29 APACHE2_HOME = /usr/local/apache2 ANT_HOME = /usr/local/ant/apache-ant-1.5.4 In order to successfully run the Ant build file I had to: 1. Modify the provided $JTC_HOME/jk/build.properties.sample to match my enviroment (set up paths, basically) 2. Create an empty 'java' directory inside $JTC_HOME/jk 3. Create the following directory structure inside $JTC_HOME: 'coyote/build/lib' 4. Copy every $TOMCAT_HOME/server/lib/*.jar file into $JTC_HOME/coyote/build/lib After the build process, the necessary files to actually generate the *.so module file for the JK2 connector are left in $JTC_HOME/jk/native2/server/apache2 I assumed that the 'Makefile.in' file was the one to be renamed as 'Makefile' in order tu run make, so I did renamed it and executed make but got the following output: mkdir -p ../../../build/jk2/apache2 make: APACHE2_HOME@/build/libtool: Command not found make: *** [../../../build/jk2/apache2/jk_channel.lo] Error 127 Apparently, the APACHE2_HOME@ variable was the source of the problem, so I went and modified the Makefile changing [EMAIL PROTECTED]@ into APACHE2_HOME=/usr/local/apache2 That solved the problem, but then another one came up. When executing make again, I got the folling output: mkdir -p ../../../build/jk2/apache2 /usr/local/apache2/build/libtool --mode=compile @CC@ @APXS2_CFLAGS@ @APXS2_CPPFLAGS@ -I../../include @APACHE2_INCL@ @APR_CFLAGS@ -I @JAVA_HOME@/include -I @JAVA_HOME@/include/@OS@ -DCHUNK_SIZE=4096 - DUSE_APACHE_MD5 -DHAS_APR @HAVE_JNI@ @HAS_PCRE@ -c ./../common/jk_channel.c -o ../../../build/jk2/apache2/jk_channel.lo rm -f ../../../build/jk2/apache2/.libs/jk_channel.lo @CC@ @APXS2_CFLAGS@ @APXS2_CPPFLAGS@ -I../../include @APACHE2_INCL@ @APR_CFLAGS@ -I @JAVA_HOME@/include -I @JAVA_HOME@/include/@OS@ - DCHUNK_SIZE=4096 -DUSE_APACHE_MD5 -DHAS_APR @HAVE_JNI@ @HAS_PCRE@ -c ./../common/jk_channel.c -fPIC -DPIC -o ./../../build/jk2/apache2/.libs/jk_channel.lo /usr/local/apache2/build/libtool: line 1: @CC@: command not found make: *** [../../../build/jk2/apache2/jk_channel.lo] Error 1 Its seemed that the problem was now with the @CC@ variable -which I think should point to /usr/bin/cc. I used the same reasoning as before I changed [EMAIL PROTECTED]@ for CC=/usr/bin/cc, but got an error message pretty much like the last one except for the two last lines: .. cc: cannot specify -o with -c or -S and multiple compilations make: *** [../../../build/jk2/apache2/jk_channel.lo] Error 1 ...And finally Here's where I'm stalled :-( Any help will be geratly appreciated. Regards, Carlos This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Building jakarta-tomcat-connectors-jk2-2.0.2-src [HOW?]
Hello again.
Thanks A LOT for que quick answers.
Mr. Shapira was absolutely right with his UNIX point of view, and along with
his reasoning the instructions from Mr. Eggers helped me (finally) build the
jk2 module for Apache. Basically, the rest of the building process after
running Ant is as follows:
1. Go ${JTC_HOME}/jk/native2 and run ./buildconf.sh. (as stated in
http://www.blacksheepnetworks.com/security/resources/apache2-tomcat404-howto.html)
This will create the configure file.
2. Run
/configure --with-apxs2=${APACHE_HOME}/bin/apxs --with-java-home=${JAVA_HOM
E} . This will create the Makefile file.
3. Run make.
4. Look for mod_jk2.so file and place it in the proper location
(${APACHE_HOME}/modules)
* Mr. Eggers mini how-to
(http://marc.theaimsgroup.com/?l=tomcat-userm=106541574307371w=2) is more
complete and I think has gone through a whole lot more testing than my
procedure; I suggest to look at and try his instructions first.
Now, since I'm dealing with the embedded version of Tomcat (JBoss/Tomcat
bundle), I'll dive into configuring it to work with Apache... again, any
help would be greatly appreciated... ;^) Any results (good bad) will also
be posted :-)
Best regards,
Carlos
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
tomcat-connectors
Greetings, I hope everyone is feeling well in the new year. I recently upgraded a web server from redhat7.2 to the fedora os. The apache was upgraded in the process and now we are running Apache/2.0.47. I have been unable to get a mod_jk or mod_jk2 that will install or compile. I have tried the src files from the apache site found here: http://jakarta.apache.org/site/sourceindex.cgi but I get the following error during the make: jk_connect.c:99:28: apr_network_io.h: No such file or directory ( all the apr rpms for fedora have been installed ). Someone suggested trying the rpms at jpackage.org, so I have also tried all the source and non source rpms from jpackage.org. Does anyone have mod_jk or mod_jk2 working with tomcat 4.x on the fedora os? Any help or insight is greatly appreciated. Take Care Shannon Fedora Core 1 Apache 2.0.47 Tomcat 4.1.24
Re: tomcat-connectors
Hi, I emailed you a compiled mod_jk that should work on fedora, if for some reason you do not get the attachment let me know and i will send you a link. Camron G. Levanger The Dreamlab www.dreamlabmedia.com (866) 890-3705 On Jan 5, 2004, at 8:49 AM, Shannon Scott wrote: Greetings, I hope everyone is feeling well in the new year. I recently upgraded a web server from redhat7.2 to the fedora os. The apache was upgraded in the process and now we are running Apache/2.0.47. I have been unable to get a mod_jk or mod_jk2 that will install or compile. I have tried the src files from the apache site found here: http://jakarta.apache.org/site/sourceindex.cgi but I get the following error during the make: jk_connect.c:99:28: apr_network_io.h: No such file or directory ( all the apr rpms for fedora have been installed ). Someone suggested trying the rpms at jpackage.org, so I have also tried all the source and non source rpms from jpackage.org. Does anyone have mod_jk or mod_jk2 working with tomcat 4.x on the fedora os? Any help or insight is greatly appreciated. Take Care Shannon Fedora Core 1 Apache 2.0.47 Tomcat 4.1.24 smime.p7s Description: S/MIME cryptographic signature
RE: tomcat-connectors
Camron, Thank you for your quick response. I appreciate your effort. When I tried your mod_jk.so file, apache would not start. I got the following error. Starting httpd: httpd: module mod_jk.c is not compatible with this version of Apache (found 20020628, need 20020903). Please contact the vendor for the correct version. Any ideas? What version of apache are you running? Where did you obtain your apache from? I have the httpd files from the fedora rpms. Thank you again. Take Care Shannon -Original Message- From: Camron G. Levanger [mailto:[EMAIL PROTECTED] Sent: Monday, January 05, 2004 10:57 AM To: Tomcat Users List Subject: Re: tomcat-connectors Hi, I emailed you a compiled mod_jk that should work on fedora, if for some reason you do not get the attachment let me know and i will send you a link. Camron G. Levanger The Dreamlab www.dreamlabmedia.com (866) 890-3705 On Jan 5, 2004, at 8:49 AM, Shannon Scott wrote: Greetings, I hope everyone is feeling well in the new year. I recently upgraded a web server from redhat7.2 to the fedora os. The apache was upgraded in the process and now we are running Apache/2.0.47. I have been unable to get a mod_jk or mod_jk2 that will install or compile. I have tried the src files from the apache site found here: http://jakarta.apache.org/site/sourceindex.cgi but I get the following error during the make: jk_connect.c:99:28: apr_network_io.h: No such file or directory ( all the apr rpms for fedora have been installed ). Someone suggested trying the rpms at jpackage.org, so I have also tried all the source and non source rpms from jpackage.org. Does anyone have mod_jk or mod_jk2 working with tomcat 4.x on the fedora os? Any help or insight is greatly appreciated. Take Care Shannon Fedora Core 1 Apache 2.0.47 Tomcat 4.1.24 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: tomcat-connectors
Sorry to hear that, I am running 2.0.47. I can't understand why it wouldn't work. But anyway, I compiled mine from the jakarta-tomcat-connectors-4.1.27-src. I will do a little research see if i can't dig up something. Camron G. Levanger The Dreamlab www.dreamlabmedia.com (866) 890-3705 On Jan 5, 2004, at 9:16 AM, Shannon Scott wrote: Camron, Thank you for your quick response. I appreciate your effort. When I tried your mod_jk.so file, apache would not start. I got the following error. Starting httpd: httpd: module mod_jk.c is not compatible with this version of Apache (found 20020628, need 20020903). Please contact the vendor for the correct version. Any ideas? What version of apache are you running? Where did you obtain your apache from? I have the httpd files from the fedora rpms. Thank you again. Take Care Shannon -Original Message- From: Camron G. Levanger [mailto:[EMAIL PROTECTED] Sent: Monday, January 05, 2004 10:57 AM To: Tomcat Users List Subject: Re: tomcat-connectors Hi, I emailed you a compiled mod_jk that should work on fedora, if for some reason you do not get the attachment let me know and i will send you a link. Camron G. Levanger The Dreamlab www.dreamlabmedia.com (866) 890-3705 On Jan 5, 2004, at 8:49 AM, Shannon Scott wrote: Greetings, I hope everyone is feeling well in the new year. I recently upgraded a web server from redhat7.2 to the fedora os. The apache was upgraded in the process and now we are running Apache/2.0.47. I have been unable to get a mod_jk or mod_jk2 that will install or compile. I have tried the src files from the apache site found here: http://jakarta.apache.org/site/sourceindex.cgi but I get the following error during the make: jk_connect.c:99:28: apr_network_io.h: No such file or directory ( all the apr rpms for fedora have been installed ). Someone suggested trying the rpms at jpackage.org, so I have also tried all the source and non source rpms from jpackage.org. Does anyone have mod_jk or mod_jk2 working with tomcat 4.x on the fedora os? Any help or insight is greatly appreciated. Take Care Shannon Fedora Core 1 Apache 2.0.47 Tomcat 4.1.24 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] smime.p7s Description: S/MIME cryptographic signature
Re: tomcat-connectors
Hi, I am having similar problems, though not with the same configuration as yours. My config is: RH9, Apache 2.0.48, Tomcat 5.0.16, JK2_2.0.2. I cannot get the make files to produce the .so's. It's as if libtool is not working. I am following the instructions to the letter, but still no mod_jk2.so, or jkjni.so. Any ideas? James Shannon Scott wrote: Greetings, I hope everyone is feeling well in the new year. I recently upgraded a web server from redhat7.2 to the fedora os. The apache was upgraded in the process and now we are running Apache/2.0.47. I have been unable to get a mod_jk or mod_jk2 that will install or compile. I have tried the src files from the apache site found here: http://jakarta.apache.org/site/sourceindex.cgi but I get the following error during the make: jk_connect.c:99:28: apr_network_io.h: No such file or directory ( all the apr rpms for fedora have been installed ). Someone suggested trying the rpms at jpackage.org, so I have also tried all the source and non source rpms from jpackage.org. Does anyone have mod_jk or mod_jk2 working with tomcat 4.x on the fedora os? Any help or insight is greatly appreciated. Take Care Shannon Fedora Core 1 Apache 2.0.47 Tomcat 4.1.24 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: tomcat-connectors
Shannon, Here try this rpm, if you haven't already. http://rpm.pbone.net/index.php3/stat/4/idpl/857409/com/mod_jk-ap20 -1.2.5-2jpp.i386.rpm.html Camron G. Levanger The Dreamlab www.dreamlabmedia.com (866) 890-3705 On Jan 5, 2004, at 9:16 AM, Shannon Scott wrote: Camron, Thank you for your quick response. I appreciate your effort. When I tried your mod_jk.so file, apache would not start. I got the following error. Starting httpd: httpd: module mod_jk.c is not compatible with this version of Apache (found 20020628, need 20020903). Please contact the vendor for the correct version. Any ideas? What version of apache are you running? Where did you obtain your apache from? I have the httpd files from the fedora rpms. Thank you again. Take Care Shannon -Original Message- From: Camron G. Levanger [mailto:[EMAIL PROTECTED] Sent: Monday, January 05, 2004 10:57 AM To: Tomcat Users List Subject: Re: tomcat-connectors Hi, I emailed you a compiled mod_jk that should work on fedora, if for some reason you do not get the attachment let me know and i will send you a link. Camron G. Levanger The Dreamlab www.dreamlabmedia.com (866) 890-3705 On Jan 5, 2004, at 8:49 AM, Shannon Scott wrote: Greetings, I hope everyone is feeling well in the new year. I recently upgraded a web server from redhat7.2 to the fedora os. The apache was upgraded in the process and now we are running Apache/2.0.47. I have been unable to get a mod_jk or mod_jk2 that will install or compile. I have tried the src files from the apache site found here: http://jakarta.apache.org/site/sourceindex.cgi but I get the following error during the make: jk_connect.c:99:28: apr_network_io.h: No such file or directory ( all the apr rpms for fedora have been installed ). Someone suggested trying the rpms at jpackage.org, so I have also tried all the source and non source rpms from jpackage.org. Does anyone have mod_jk or mod_jk2 working with tomcat 4.x on the fedora os? Any help or insight is greatly appreciated. Take Care Shannon Fedora Core 1 Apache 2.0.47 Tomcat 4.1.24 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] smime.p7s Description: S/MIME cryptographic signature
RE: tomcat-connectors
That one works. Thank You Much. Take Care. Shannon -Original Message- From: Camron G. Levanger [mailto:[EMAIL PROTECTED] Sent: Monday, January 05, 2004 11:41 AM To: Tomcat Users List Subject: Re: tomcat-connectors Shannon, Here try this rpm, if you haven't already. http://rpm.pbone.net/index.php3/stat/4/idpl/857409/com/mod_jk-ap20 -1.2.5-2jpp.i386.rpm.html Camron G. Levanger The Dreamlab www.dreamlabmedia.com (866) 890-3705 On Jan 5, 2004, at 9:16 AM, Shannon Scott wrote: Camron, Thank you for your quick response. I appreciate your effort. When I tried your mod_jk.so file, apache would not start. I got the following error. Starting httpd: httpd: module mod_jk.c is not compatible with this version of Apache (found 20020628, need 20020903). Please contact the vendor for the correct version. Any ideas? What version of apache are you running? Where did you obtain your apache from? I have the httpd files from the fedora rpms. Thank you again. Take Care Shannon -Original Message- From: Camron G. Levanger [mailto:[EMAIL PROTECTED] Sent: Monday, January 05, 2004 10:57 AM To: Tomcat Users List Subject: Re: tomcat-connectors Hi, I emailed you a compiled mod_jk that should work on fedora, if for some reason you do not get the attachment let me know and i will send you a link. Camron G. Levanger The Dreamlab www.dreamlabmedia.com (866) 890-3705 On Jan 5, 2004, at 8:49 AM, Shannon Scott wrote: Greetings, I hope everyone is feeling well in the new year. I recently upgraded a web server from redhat7.2 to the fedora os. The apache was upgraded in the process and now we are running Apache/2.0.47. I have been unable to get a mod_jk or mod_jk2 that will install or compile. I have tried the src files from the apache site found here: http://jakarta.apache.org/site/sourceindex.cgi but I get the following error during the make: jk_connect.c:99:28: apr_network_io.h: No such file or directory ( all the apr rpms for fedora have been installed ). Someone suggested trying the rpms at jpackage.org, so I have also tried all the source and non source rpms from jpackage.org. Does anyone have mod_jk or mod_jk2 working with tomcat 4.x on the fedora os? Any help or insight is greatly appreciated. Take Care Shannon Fedora Core 1 Apache 2.0.47 Tomcat 4.1.24 - 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-connectors
If you are using the rpms, you will have to tell configure where to find the libraries and include files. Type ./configure --help for the syntax --with-PACKAGE[=ARG]use PACKAGE [ARG=yes] --without-PACKAGE do not use PACKAGE (same as --with-PACKAGE=no) --with-gnu-ld assume the C compiler uses GNU ld default=no --with-pic try to use only PIC/non-PIC objects default=use both --with-apxs=FILE location of apxs for Apache 1.3 --with-apxs2=FILE location of apxs for Apache 2.0 --with-apache13=DIR Location of apache13 source dir --with-apache13-include=DIR Location of apache13 include dir --with-apache13-lib=DIR Location of apache13 lib dir --with-apache2=DIR Location of apache2 source dir --with-apache2-include=DIR Location of apache2 include dir --with-apache2-lib=DIR Location of apache2 lib dir --with-iis=DIR Location of iis source dir --with-iis-include=DIR Location of iis include dir --with-iis-lib=DIR Location of iis lib dir --with-iplanet=DIR Location of iplanet source dir --with-iplanet-include=DIR Location of iplanet include dir --with-iplanet-lib=DIR Location of iplanet lib dir --with-tomcat33=DIR Location of tomcat33 --with-tomcat40=DIR Location of tomcat40 --with-tomcat41=DIR Location of tomcat41 --with-apr=DIR Location of APR source dir --with-apr-include=DIR Location of APR include dir --with-apr-lib=DIR Location of APR lib dir --with-java-home=DIR Location of JDK directory. --with-java-platform=2 Force the Java platorm (value is 1 for 1.1.x or 2 for 1.2.x or greater) --with-os-type=SUBDIRLocation of JDK os-type subdirectory. --with-jni Build jni support --with-pcre Build pcre support I don't use the RPMs for the web server, but I think it's because those RPMs place the include and library files in a place not known by apxs2. HTH /mde/ just my two cents . . . . __ Do you Yahoo!? New Yahoo! Photos - easier uploading and sharing. http://photos.yahoo.com/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: tomcat-connectors
Everything I'm sure will work great if you compile apache from source. Oscar http://daydream.stanford.edu/tomcat/install_web_services.html On Mon, 5 Jan 2004, Shannon Scott wrote: Camron, Thank you for your quick response. I appreciate your effort. When I tried your mod_jk.so file, apache would not start. I got the following error. Starting httpd: httpd: module mod_jk.c is not compatible with this version of Apache (found 20020628, need 20020903). Please contact the vendor for the correct version. Any ideas? What version of apache are you running? Where did you obtain your apache from? I have the httpd files from the fedora rpms. Thank you again. Take Care Shannon -Original Message- From: Camron G. Levanger [mailto:[EMAIL PROTECTED] Sent: Monday, January 05, 2004 10:57 AM To: Tomcat Users List Subject: Re: tomcat-connectors Hi, I emailed you a compiled mod_jk that should work on fedora, if for some reason you do not get the attachment let me know and i will send you a link. Camron G. Levanger The Dreamlab www.dreamlabmedia.com (866) 890-3705 On Jan 5, 2004, at 8:49 AM, Shannon Scott wrote: Greetings, I hope everyone is feeling well in the new year. I recently upgraded a web server from redhat7.2 to the fedora os. The apache was upgraded in the process and now we are running Apache/2.0.47. I have been unable to get a mod_jk or mod_jk2 that will install or compile. I have tried the src files from the apache site found here: http://jakarta.apache.org/site/sourceindex.cgi but I get the following error during the make: jk_connect.c:99:28: apr_network_io.h: No such file or directory ( all the apr rpms for fedora have been installed ). Someone suggested trying the rpms at jpackage.org, so I have also tried all the source and non source rpms from jpackage.org. Does anyone have mod_jk or mod_jk2 working with tomcat 4.x on the fedora os? Any help or insight is greatly appreciated. Take Care Shannon Fedora Core 1 Apache 2.0.47 Tomcat 4.1.24 - 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]
src/jakarta-tomcat-connectors/util/build.xml bug with IBM jdk 1.4
Problem build tomcat 5.0.16 with IBMJava2-SDK 1.4.1 on intel.
ant from src abort on src/jakarta-tomcat-connectors/util/build.xml, so I
have tried ant from this dir:
[EMAIL PROTECTED]:~/jakarta-tomcat-5.0.16-src/src/jakarta-tomcat-connectors/
util=ant
Buildfile: build.xml
detect:
build-prepare:
[mkdir] Created dir:
/usr/local/src/jakarta-tomcat-5.0.16-src/src/jakarta-tomcat-connectors/util
/build
[mkdir] Created dir:
/usr/local/src/jakarta-tomcat-5.0.16-src/src/jakarta-tomcat-connectors/util
/build/classes
[mkdir] Created dir:
/usr/local/src/jakarta-tomcat-5.0.16-src/src/jakarta-tomcat-connectors/util
/build/lib
build-main:
[echo] - Java-utils -
[echo] -- puretls.present = ${puretls.present}
[echo] -- jsse.present = true /usr/share/java/jsse-1.0.3/lib/jsse.jar
[echo] -- commons-logging = true
[echo] -- jmx = true /usr/share/java/mx4j-1.1.1/lib/mx4j-jmx.jar
[echo] -- modeler = ${modeler.present}
/usr/share/java/commons-modeler-1.1M1/commons-modeler.jar
[echo] -- JDK14 = true
[javac] Compiling 71 source files to
/usr/local/src/jakarta-tomcat-5.0.16-src/src/jakarta-tomcat-connectors/util
/build/classes
[javac]
/usr/local/src/jakarta-tomcat-5.0.16-src/src/jakarta-tomcat-connectors/util
/java/org/apache/tomcat/util/net/jsse/JSSE13SocketFactory.java:105: cannot
resolve symbol
[javac] symbol : class Sun
[javac] location: package provider
[javac] Security.addProvider (new
sun.security.provider.Sun());
[javac]^
[javac]
/usr/local/src/jakarta-tomcat-5.0.16-src/src/jakarta-tomcat-connectors/util
/java/org/apache/tomcat/util/net/jsse/JSSE13SocketFactory.java:106: package
com.sun.net.ssl.internal.ssl does not exist
[javac] Security.addProvider (new
com.sun.net.ssl.internal.ssl.Provider());
[javac]
^
[...]
[javac] Note:
/usr/local/src/jakarta-tomcat-5.0.16-src/src/jakarta-tomcat-connectors/util
/java/org/apache/tomcat/util/threads/ThreadPool.java uses or overrides a
deprecated API.
[javac] Note: Recompile with -deprecation for details.
[javac] 9 errors
BUILD FAILED
file:/usr/local/src/jakarta-tomcat-5.0.16-src/src/jakarta-tomcat-connectors
/util/build.xml:67: Compile failed; see the compiler error output for
details.
Total time: 10 seconds
A second attempt (without a clean) fail too:
[EMAIL PROTECTED]:~/jakarta-tomcat-5.0.16-src/src/jakarta-tomcat-connectors/
util=ant
Buildfile: build.xml
detect:
build-prepare:
build-main:
[echo] - Java-utils -
[echo] -- puretls.present = ${puretls.present}
[echo] -- jsse.present = true /usr/share/java/jsse-1.0.3/lib/jsse.jar
[echo] -- commons-logging = true
[echo] -- jmx = true /usr/share/java/mx4j-1.1.1/lib/mx4j-jmx.jar
[echo] -- modeler = ${modeler.present}
/usr/share/java/commons-modeler-1.1M1/commons-modeler.jar
[echo] -- JDK14 = true
[javac] Compiling 68 source files to
/usr/local/src/jakarta-tomcat-5.0.16-src/src/jakarta-tomcat-connectors/util
/build/classes
[javac]
/usr/local/src/jakarta-tomcat-5.0.16-src/src/jakarta-tomcat-connectors/util
/java/org/apache/tomcat/util/net/jsse/JSSE13SocketFactory.java:105: cannot
resolve symbol
[javac] symbol : class Sun
[javac] location: package provider
[javac] Security.addProvider (new
sun.security.provider.Sun());
[javac]^
It try to compile JSSE for jdk 1.4 (JSSE13*) with jdk 1.4 too.
I have added:
exclude name=**/util/net/jsse/JSSE13* if=jdk1.4.present /
after:
exclude name=**/util/net/jsse/JSSE14* unless=jdk1.4.present
/
(patch attached)
First ant fail, but the second attempt no:
[EMAIL PROTECTED]:~/jakarta-tomcat-5.0.16-src/src/jakarta-tomcat-connectors/
util=ant
Buildfile: build.xml
detect:
build-prepare:
[mkdir] Created dir:
/usr/local/src/jakarta-tomcat-5.0.16-src/src/jakarta-tomcat-connectors/util
/build
[mkdir] Created dir:
/usr/local/src/jakarta-tomcat-5.0.16-src/src/jakarta-tomcat-connectors/util
/build/classes
[mkdir] Created dir:
/usr/local/src/jakarta-tomcat-5.0.16-src/src/jakarta-tomcat-connectors/util
/build/lib
build-main:
[echo] - Java-utils -
[echo] -- puretls.present = ${puretls.present}
[echo] -- jsse.present = true /usr/share/java/jsse-1.0.3/lib/jsse.jar
[echo] -- commons-logging = true
[echo] -- jmx = true /usr/share/java/mx4j-1.1.1/lib/mx4j-jmx.jar
[echo] -- modeler = ${modeler.present}
/usr/share/java/commons-modeler-1.1M1/commons-modeler.jar
[echo] -- JDK14 = true
[javac] Compiling 69 source files to
/usr/local/src/jakarta-tomcat-5.0.16-src/src/jakarta-tomcat-connectors/util
/build/classes
[javac]
/usr/local/src/jakarta-tomcat-5.0.16-src/src/jakarta-tomcat-connectors/util
/java/org/apache/tomcat/util/net/jsse
Re: src/jakarta-tomcat-connectors/util/build.xml bug with IBM jdk 1.4
In data Sat, 27 Dec 2003 19:24:33 +0100 Gianluca Toso scrisse: Problem build tomcat 5.0.16 with IBMJava2-SDK 1.4.1 on intel. ant from src abort on src/jakarta-tomcat-connectors/util/build.xml, so I have tried ant from this dir: [...] /usr/local/src/jakarta-tomcat-5.0.16-src/src/jakarta-tomcat-connectors/ut il/java/org/apache/tomcat/util/net/jsse/JSSE13SocketFactory.java:105: cannot resolve symbol [javac] symbol : class Sun [javac] location: package provider [javac] Security.addProvider (new sun.security.provider.Sun()); It try to compile JSSE for jdk 1.4 (JSSE13*) with jdk 1.4 too. I have added: exclude name=**/util/net/jsse/JSSE13* if=jdk1.4.present / after: exclude name=**/util/net/jsse/JSSE14* unless=jdk1.4.present / I don't understand why, but it seems to include the support for JDK 1.4 even if compiled with JDK 1.4.x So I have restored build.xml and modified JSSE13SocketFactory.java in order to work with the JDK of IBM. One of the reasons to compile sources would have to be to be able to choose which features to include/to exclude and to obtain optimized binaries for own system? IMHO would be useful one first phase style autoconf or at least one explanation on how to make this with ant and the several one build.properties. What of it you say? I'm in mistake? -- Gianluca Toso jakarta-tomcat-5.0.16-src_ibmjdk14.patch-2.gz Description: Binary data pgp0.pgp Description: PGP signature
Re: src/jakarta-tomcat-connectors/util/build.xml bug with IBM jdk 1.4
You should report this as a bug and attach the patch you provided here to the bug, otherwise it may get lost in the shuffle. http://issues.apache.org/bugzilla/ Jake At 11:33 PM 12/27/2003 +0100, you wrote: In data Sat, 27 Dec 2003 19:24:33 +0100 Gianluca Toso scrisse: Problem build tomcat 5.0.16 with IBMJava2-SDK 1.4.1 on intel. ant from src abort on src/jakarta-tomcat-connectors/util/build.xml, so I have tried ant from this dir: [...] /usr/local/src/jakarta-tomcat-5.0.16-src/src/jakarta-tomcat-connectors/ut il/java/org/apache/tomcat/util/net/jsse/JSSE13SocketFactory.java:105: cannot resolve symbol [javac] symbol : class Sun [javac] location: package provider [javac] Security.addProvider (new sun.security.provider.Sun()); It try to compile JSSE for jdk 1.4 (JSSE13*) with jdk 1.4 too. I have added: exclude name=**/util/net/jsse/JSSE13* if=jdk1.4.present / after: exclude name=**/util/net/jsse/JSSE14* unless=jdk1.4.present / I don't understand why, but it seems to include the support for JDK 1.4 even if compiled with JDK 1.4.x So I have restored build.xml and modified JSSE13SocketFactory.java in order to work with the JDK of IBM. One of the reasons to compile sources would have to be to be able to choose which features to include/to exclude and to obtain optimized binaries for own system? IMHO would be useful one first phase style autoconf or at least one explanation on how to make this with ant and the several one build.properties. What of it you say? I'm in mistake? -- Gianluca Toso - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: src/jakarta-tomcat-connectors/util/build.xml bug with IBM jdk 1.4
Gianluca Toso [EMAIL PROTECTED] wrote in message news:[EMAIL PROTECTED] In data Sat, 27 Dec 2003 19:24:33 +0100 Gianluca Toso scrisse: Problem build tomcat 5.0.16 with IBMJava2-SDK 1.4.1 on intel. ant from src abort on src/jakarta-tomcat-connectors/util/build.xml, so I have tried ant from this dir: [...] /usr/local/src/jakarta-tomcat-5.0.16-src/src/jakarta-tomcat-connectors/ut il/java/org/apache/tomcat/util/net/jsse/JSSE13SocketFactory.java:105: cannot resolve symbol [javac] symbol : class Sun [javac] location: package provider [javac] Security.addProvider (new sun.security.provider.Sun()); It try to compile JSSE for jdk 1.4 (JSSE13*) with jdk 1.4 too. I have added: exclude name=**/util/net/jsse/JSSE13* if=jdk1.4.present / after: exclude name=**/util/net/jsse/JSSE14* unless=jdk1.4.present / I don't understand why, but it seems to include the support for JDK 1.4 even if compiled with JDK 1.4.x So I have restored build.xml and modified JSSE13SocketFactory.java in order to work with the JDK of IBM. Well, the reason is that the binary release version of Tomcat shouldn't depend on SDK version that it was compiled with. Don't bother with Jacob's recommendation to submit it to Bugzilla, since I will resolve it as WONTFIX. It is easy enough to include the JDK 1.3 classes in the build, and they won't be used in a 1.4 environment. One of the reasons to compile sources would have to be to be able to choose which features to include/to exclude and to obtain optimized binaries for own system? IMHO would be useful one first phase style autoconf or at least one explanation on how to make this with ant and the several one build.properties. What of it you say? I'm in mistake? -- Gianluca Toso - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Apache-Tomcat connectors... why??
If your application is using the HTTPSession, then you will want apache to stick you to the same instance of tomcat on the backend for all requests for that session. mod_jk and mod_jk2 both support this. Forgive me if I am wrong, but I dont think mod_proxy will do this for you. -sean -Original Message- From: Wesley Hall [mailto:[EMAIL PROTECTED] Sent: Tuesday, December 16, 2003 12:54 PM To: Tomcat Users List Subject: RE: Apache-Tomcat connectors... why?? Thank you Howard and Jim, I will look into mod_proxy. Things seem a little more complicated because I am attempted to integrate with the JBoss tomcat bundle. Obviously the configuration is a little different here and most howto's require a little bit more thinking about as to where to find the files etc... Im not sure about using tomcat as a static content server. Apache has many features that tomcat doesnt as it is designed for this task. It might solve the problem, but the powers-that-be are quite keen on full integration. Im not sure that servlets do require anything extra at HTTP level. Perhaps I am missing something but due to the relative simplicity of HTTP and the fact its stateless I would assume that the servlet container cant require anything extra. From the browsers perspective it is requesting a static resource, by name, from a domain. The proxying route would have the added advantage of not having to reconfigure mod_jk(2) everytime a new web app is added. The browser says Give me /index.jsp, apache says I cant find index.jsp, but i know about THIS http server (tomcat), that might, tomcat says yup, i can do that for you, here it is, apache says Here you go... i found it eventually... all over HTTP. It seems to make a lot of sense to me, but as you say, if this simple solution has not been shouted about, it will mean there is a fundemental flaw... lots of smarter guys than me working on this stuff =o) Thanks again for your help! -Original Message- From: Howard Jim [mailto:[EMAIL PROTECTED] Sent: 16 December 2003 19:34 To: Tomcat Users List Subject: RE: Apache-Tomcat connectors... why?? I believe what you are referring to is the ProxyPass Directive http://httpd.apache.org/docs-2.0/mod/mod_proxy.html#proxypass I have used this before, but haven't played with it as a way to reference the app server. If it were that simple, I imagine it would have already been done. I am just getting going with the connectors, but things like parameters, servlets, and the like have their own needs which may require a closer integration with the webserver than can be provided by a simple reverse proxy setup. If all you need is the reverse proxy setup, then perhaps you don't even need the webserver. Just let tomcat serve it all, then all your connector worries are moot. Jim -Original Message- From: Wesley Hall [mailto:[EMAIL PROTECTED] Sent: Tuesday, December 16, 2003 1:27 PM To: [EMAIL PROTECTED] Subject: Apache-Tomcat connectors... why?? Hello all, Hopefully I picked a good list to bring this topic up on. There were several candidates. I have spent some time today attempting to perform the non-trival task of configuring communication between the apache web server and the tomcat servlet engine. This seems to be a fairly complicated process involving quite a lot of configuration and some degree of black magic. It occured to me that a simpler approch would be to simply have apache forward requests at HTTP level to a list of slave servers in the form of Cant find this resource!! Can you??. Before apache returns a 404 error it could consult some form of list and ask other servers on the network (tomcat for instance ;o)) to attempt to find the resource via HTTP. I dont see a reason why this would perform particually badly in the most common set up of apache + tomcat. Presumably there is a way to configure apache to do this already (if anyone could point me to the write manaual page I would be grateful), but it doesnt seem to be offered up a simple solution to a complex problem on the tomcat integration pages. My question... why is this solution not mentioned more often given the number of how do i configure mod_jk2?? results on google and would their be any serious disadvantages with such an approch? Thanks Wesley Hall - 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
Apache-Tomcat connectors... why??
Hello all, Hopefully I picked a good list to bring this topic up on. There were several candidates. I have spent some time today attempting to perform the non-trival task of configuring communication between the apache web server and the tomcat servlet engine. This seems to be a fairly complicated process involving quite a lot of configuration and some degree of black magic. It occured to me that a simpler approch would be to simply have apache forward requests at HTTP level to a list of slave servers in the form of Cant find this resource!! Can you??. Before apache returns a 404 error it could consult some form of list and ask other servers on the network (tomcat for instance ;o)) to attempt to find the resource via HTTP. I dont see a reason why this would perform particually badly in the most common set up of apache + tomcat. Presumably there is a way to configure apache to do this already (if anyone could point me to the write manaual page I would be grateful), but it doesnt seem to be offered up a simple solution to a complex problem on the tomcat integration pages. My question... why is this solution not mentioned more often given the number of how do i configure mod_jk2?? results on google and would their be any serious disadvantages with such an approch? Thanks Wesley Hall - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Apache-Tomcat connectors... why??
http://jakarta.apache.org/tomcat/faq/connectors.html In a nutshell, tomcat anc apache talk to each via the AJP protocol. The AJP protocol is like the HTTP protocol but more efficient for various reasons. An alternative to having apache talk to tomcat via AJP can also be mod_proxy sounds similar to your situation below. mod_jk and mod_jk2 are both modules written in C to be used by apache (or insert server here) jk2 is a rewrite of jk but for the same protocol. So the configuration of the jk vs jk2 is different. On the tomcat side, it really doesn't know that the apache instance is using mod_jk or mod_jk2. -Tim Wesley Hall wrote: Hello all, Hopefully I picked a good list to bring this topic up on. There were several candidates. I have spent some time today attempting to perform the non-trival task of configuring communication between the apache web server and the tomcat servlet engine. This seems to be a fairly complicated process involving quite a lot of configuration and some degree of black magic. It occured to me that a simpler approch would be to simply have apache forward requests at HTTP level to a list of slave servers in the form of Cant find this resource!! Can you??. Before apache returns a 404 error it could consult some form of list and ask other servers on the network (tomcat for instance ;o)) to attempt to find the resource via HTTP. I dont see a reason why this would perform particually badly in the most common set up of apache + tomcat. Presumably there is a way to configure apache to do this already (if anyone could point me to the write manaual page I would be grateful), but it doesnt seem to be offered up a simple solution to a complex problem on the tomcat integration pages. My question... why is this solution not mentioned more often given the number of how do i configure mod_jk2?? results on google and would their be any serious disadvantages with such an approch? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Apache-Tomcat connectors... why??
I believe what you are referring to is the ProxyPass Directive http://httpd.apache.org/docs-2.0/mod/mod_proxy.html#proxypass I have used this before, but haven't played with it as a way to reference the app server. If it were that simple, I imagine it would have already been done. I am just getting going with the connectors, but things like parameters, servlets, and the like have their own needs which may require a closer integration with the webserver than can be provided by a simple reverse proxy setup. If all you need is the reverse proxy setup, then perhaps you don't even need the webserver. Just let tomcat serve it all, then all your connector worries are moot. Jim -Original Message- From: Wesley Hall [mailto:[EMAIL PROTECTED] Sent: Tuesday, December 16, 2003 1:27 PM To: [EMAIL PROTECTED] Subject: Apache-Tomcat connectors... why?? Hello all, Hopefully I picked a good list to bring this topic up on. There were several candidates. I have spent some time today attempting to perform the non-trival task of configuring communication between the apache web server and the tomcat servlet engine. This seems to be a fairly complicated process involving quite a lot of configuration and some degree of black magic. It occured to me that a simpler approch would be to simply have apache forward requests at HTTP level to a list of slave servers in the form of Cant find this resource!! Can you??. Before apache returns a 404 error it could consult some form of list and ask other servers on the network (tomcat for instance ;o)) to attempt to find the resource via HTTP. I dont see a reason why this would perform particually badly in the most common set up of apache + tomcat. Presumably there is a way to configure apache to do this already (if anyone could point me to the write manaual page I would be grateful), but it doesnt seem to be offered up a simple solution to a complex problem on the tomcat integration pages. My question... why is this solution not mentioned more often given the number of how do i configure mod_jk2?? results on google and would their be any serious disadvantages with such an approch? Thanks Wesley Hall - 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: Apache-Tomcat connectors... why??
Thank you Howard and Jim, I will look into mod_proxy. Things seem a little more complicated because I am attempted to integrate with the JBoss tomcat bundle. Obviously the configuration is a little different here and most howto's require a little bit more thinking about as to where to find the files etc... Im not sure about using tomcat as a static content server. Apache has many features that tomcat doesnt as it is designed for this task. It might solve the problem, but the powers-that-be are quite keen on full integration. Im not sure that servlets do require anything extra at HTTP level. Perhaps I am missing something but due to the relative simplicity of HTTP and the fact its stateless I would assume that the servlet container cant require anything extra. From the browsers perspective it is requesting a static resource, by name, from a domain. The proxying route would have the added advantage of not having to reconfigure mod_jk(2) everytime a new web app is added. The browser says Give me /index.jsp, apache says I cant find index.jsp, but i know about THIS http server (tomcat), that might, tomcat says yup, i can do that for you, here it is, apache says Here you go... i found it eventually... all over HTTP. It seems to make a lot of sense to me, but as you say, if this simple solution has not been shouted about, it will mean there is a fundemental flaw... lots of smarter guys than me working on this stuff =o) Thanks again for your help! -Original Message- From: Howard Jim [mailto:[EMAIL PROTECTED] Sent: 16 December 2003 19:34 To: Tomcat Users List Subject: RE: Apache-Tomcat connectors... why?? I believe what you are referring to is the ProxyPass Directive http://httpd.apache.org/docs-2.0/mod/mod_proxy.html#proxypass I have used this before, but haven't played with it as a way to reference the app server. If it were that simple, I imagine it would have already been done. I am just getting going with the connectors, but things like parameters, servlets, and the like have their own needs which may require a closer integration with the webserver than can be provided by a simple reverse proxy setup. If all you need is the reverse proxy setup, then perhaps you don't even need the webserver. Just let tomcat serve it all, then all your connector worries are moot. Jim -Original Message- From: Wesley Hall [mailto:[EMAIL PROTECTED] Sent: Tuesday, December 16, 2003 1:27 PM To: [EMAIL PROTECTED] Subject: Apache-Tomcat connectors... why?? Hello all, Hopefully I picked a good list to bring this topic up on. There were several candidates. I have spent some time today attempting to perform the non-trival task of configuring communication between the apache web server and the tomcat servlet engine. This seems to be a fairly complicated process involving quite a lot of configuration and some degree of black magic. It occured to me that a simpler approch would be to simply have apache forward requests at HTTP level to a list of slave servers in the form of Cant find this resource!! Can you??. Before apache returns a 404 error it could consult some form of list and ask other servers on the network (tomcat for instance ;o)) to attempt to find the resource via HTTP. I dont see a reason why this would perform particually badly in the most common set up of apache + tomcat. Presumably there is a way to configure apache to do this already (if anyone could point me to the write manaual page I would be grateful), but it doesnt seem to be offered up a simple solution to a complex problem on the tomcat integration pages. My question... why is this solution not mentioned more often given the number of how do i configure mod_jk2?? results on google and would their be any serious disadvantages with such an approch? Thanks Wesley Hall - 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]
Tomcat connectors on Aix
Hello.
I need your help to compile mod_jk2 connectors on Aix 4.3.3
I use gcc 3.2.1, libtool 1.4.2, autoconf 2.53, automake 1.5
I have downloaded jakarta-tomcat-4.1.29 and it is works fine.
Now i need apache 2.0.48 works with tomcat and i have downloaded
jakarta-tomcat-connectors-4.1.29-src (i don't know if i need this version or JK 2.0.2
Source Release tar.gz)
I have followed steps on notes of jeff
trawick(http://www.apache.org/~trawick/tomcataix.html#mod_jk2_gcc):
$cd jk/native2
$ chmod +x ./buildconf.sh
$ ./buildconf.sh
$ CC=gcc ./configure --with-java-home=/usr/java131
--with-apxs2=/usr/local/apache2/bin/apxs
At last Before running make, edit ../../jk/native2/server/apache2/Makefile and change
the line
MOD_LINK = $(LIBTOOL) --mode=link $(CC) -avoid-version -module -rpath
--${APACHE2_LIBEXEC} $(LT_LDFLAGS) $(ALL_LDFLAGS)
to
MOD_LINK = $(LIBTOOL) --mode=link $(CC) -avoid-version -module -rpath
${APACHE2_LIBEXEC} $(LT_LDFLAGS) $(ALL_LDFLAGS) -Wl,-brtl
But i get a lot of warnings.
Any idea ?
Thanks.
virtual hosts tomcat connectors
Hello Is there any documentation that works on the subject of jk, jk2 or mod_webapp? I've had all 3 running using the context as a mount point but I want to have http://www.mydomain.com/Action ..not http://www.mydomain.com/webappname/Action I'm using tc 4.1.27 and apache 2 , jk, jk2 or mod_webapp .. i really dont care which just something that works and not a http://localhost/webappname this seems to be the only thing the connectors do... this looked great until i tried it, http://jakarta.apache.org/tomcat/tomcat-4.1-doc/jk2/jk2/vhosthowto.html Cheers Mark - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Cannot find jakarta-tomcat-connectors/webapp
I have downloaded and packages and am now trying to compile tomcat. But I get the following exception message: BUILD FAILED file:/hfx/opt/lenya/jakarta-tomcat-4.1.27-src/catalina/build.xml:902: Basedir /hfx/opt/lenya/jakarta-tomcat-connectors/webapp does not exist Total time: 1 minute 42 seconds I've looked at the jakarta-tomcat-connectors/ and can confirm that this does not exist! But I do not know how to correct the problem. Can somebody help. Regards Simon The following information shows the packages we downloaded and installed for the tomcat build. $ java -version java version 1.4.1_01 Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.1_01-b01) Java HotSpot(TM) Client VM (build 1.4.1_01-b01, mixed mode) (1) jakarta-ant-1.5.1-bin.zip $ ant -version Apache Ant version 1.5.1 compiled on October 2 2002 (2) This is optional with JDK 1.3 or later. (3) This is optional with JDK 1.3 or later (4) Xerces-J-bin.2.5.0.tar.gz (5) tomcat-4.1.27-src.tar.gz tomcat-connectors-1.1M1-src.tar.gz (6) jakarta-servletapi-4-20030914.tar.gz (7) commons-beanutils-1.6.1.tar.gz (8) collections-2.1.tar.gz ** documentation refers to commons-collections-X.Y.tar.gz (9) commons-digester-1.5.tar.gz (10) commons-logging-1.0.3.tar.gz (11) jakarta-regexp-1.3.tar.gz (12) full.dist NOT SET to on (13) Could not find the download (14) mx4j-1.1.1.tar.gz (15) jaf-1.0.2 (16) Not installed. (17) Not installed (18) Not installed although the jta jar is found in .. ./tyrex-1.0/jta_1.0.1.jar (19) jakarta-struts-1.1.tar.gz (20) tyrex-1.0.gz (21) junit3.7.zip (22) modeler-1.1.tar.gz (23) commons-dbcp-1.0.zip (24) pool-1.0.1.tar.gz ** documentation refers to commons-pool-1.0.tar.gz (25) could not find this (26) Extras: JavaService-bin-1.2.0.zip cocoon-latest-src.tar.gz cocoon-lenya-latest-src.tar.gz commons-fileupload-current.tar.gz nsis198.exe Simon Richardson Technology Tel: 020 7574 8838 E Mail: [EMAIL PROTECTED] HBOS Treasury Services plc 33 Old Broad Street London EC2N 1HZ -- -- For more information on HBOS Treasury Services, please visit http://www.HBOSTS.com Or for details of our online FX Deposit services, please go to http://www.HBOSdeal.com HBOS Treasury Services plc is part of the HBOS Group, which also includes Halifax plc and Bank of Scotland. Registered Office: 33 Old Broad Street, London EC2N 1HZ. Registered No. 2692890. Registered in England. Regulated by the Financial Services Authority. The information contained in this message is confidential and is intended for the addressee only. If you have received this message in error or there are any problems please notify the originator immediately. The unauthorised use, disclosure, copying or alteration of this message is strictly forbidden. This mail and any attachments have been scanned for viruses prior to leaving the HBOS Treasury Services plc network. HBOS Treasury Services plc will not be liable for direct, special, indirect or consequential damages arising from alteration of the contents of this message by a third party or as a result of any virus being passed on. HBOS Treasury Services plc reserves the right to monitor and record e-mail messages sent to and from this address for the purposes of investigating or detecting any unauthorised use of its system and ensuring its effective operation. == - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Problem with jakarta-tomcat-connectors-4.0.6-src
Greetings, I'm trying to configure the jakarta-tomcat-connectors-4.0.6-src and when I run ./buildconf.sh I get the following error message libtoolize --force --automake --copy libtoolize: `configure.ac' does not exist Try `libtoolize --help' for more information. aclocal aclocal: `configure.ac' or `configure.in' is required aclocal: `configure.ac' or `configure.in' is required automake -a --foreign -i --copy automake: `configure.ac' or `configure.in' is required autoconf autoconf: no input file Any help would be appreciated Thanks, Bobbie Bobbie Atristain Internet Systems Administrator Media General, INC. 804.649.6156 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Apache/Tomcat Connectors
Oh No - Not another Connector Issue - lol I am about to attempt to put together, the best latest combination of Apache and Tomcat with the jk2 connector. So this is a question about which versions work with which versions. I plan to use Apache 2.0.47 and Tomcat 4.1.24 In searching through the binary connectors I found one for Apache 2.0.46. Can I use it or should I build my own from the source distribution? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Apache/Tomcat Connectors
Hi Ray, According to the message I got from the [EMAIL PROTECTED] mailing list regarding this latest release, any module built for Apache 2.0.42 or later should work with 2.0.47: quote This release is compatible with modules compiled for 2.0.42 and later versions. /quote Cheers, Morgan -Original Message- From: Ray Madigan [mailto:[EMAIL PROTECTED] Sent: Thursday, July 10, 2003 16:24 To: Tomcat-User Subject: Apache/Tomcat Connectors Oh No - Not another Connector Issue - lol I am about to attempt to put together, the best latest combination of Apache and Tomcat with the jk2 connector. So this is a question about which versions work with which versions. I plan to use Apache 2.0.47 and Tomcat 4.1.24 In searching through the binary connectors I found one for Apache 2.0.46. Can I use it or should I build my own from the source distribution? - 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]
RV: Fix for SEVERE: Certificate convertion failed, bug in Tomcat-connectors-4.1.24
This is the patched class. It must be replaced at
$(TOMCAT_HOME)/server/lib/tomcat-jk2.jar jar-file.
You simply need to un-jar the file tomcat-jk2.jar and replace JkCoyoteHandler.class
with the patched one.
Thanks to Thorvald Natvig.
--
José Antonio Tarifa Lorenzo
Departamento de Desarrollo
Compañía Operadora del Mercado Español de Electricidad, S.A.
c/Alfonso XI, 6 4ª Planta. 28014 Madrid
email: [EMAIL PROTECTED]
--
-Mensaje original-
De: Ramsay Domloge [mailto:[EMAIL PROTECTED]
Enviado el: martes, 25 de marzo de 2003 19:01
Para: Tomcat Users List
Asunto: Re: Fix for SEVERE: Certificate convertion failed, bug in
Tomcat-connectors-4.1.24
Thank God!
I have been stuck on this for 10 days now, and I have been going a bit
loopy!
I really need to apply this patch *today*, but I'm having difficulty
getting hold of all the sourcecode that I need to apply the patch to
I would *really* appreciate it if you could help me out here and give me
a little more info on what I need to do; where to get the sourcecode and
what I need to build a new Tomcat, etc etc.
I am supposed to be delivering this project at the end of the week and
this bug has held me back 10 days... my boss is going loopy!
Thanks in advance,
Ramsay
Thorvald Natvig wrote:
For those that have been suffering problems using 2-way authenticating
with the JK2 Coyote connector, this patch should fix the problem. It's not
a good fix, but it's a fix nonetheless.
---
jakarta-tomcat-connectors-4.1.24-src/jk/java/org/apache/jk/server/JkCoyoteHandler.java
2003-03-19 10:21:04.0 +0100
+++
jakarta-tomcat-connectors-4.1.24-src-new/jk/java/org/apache/jk/server/JkCoyoteHandler.java
2003-03-25 17:10:54.0 +0100
@@ -384,7 +384,7 @@
// Extract SSL certificate information (if requested)
MessageBytes certString =
(MessageBytes)req.getNote(WorkerEnv.SSL_CERT_NOTE);
if( certString != null ) {
-byte[] certData = certString.getByteChunk().getBytes();
+byte[] certData = certString.toString().getBytes();
ByteArrayInputStream bais = new ByteArrayInputStream(certData);
// Fill the first element.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
A R K E M E D I A T E C H N O L O G I E S L T D
VIEW POINTBASING VIEWBASINGSTOKEHAMPSHIRERG21 4RG
http://www.arkemedia.com
mailto:[EMAIL PROTECTED]
Tel : +44 1256 869 200 Fax : +44 1256 329 119
The information in this e-mail and in any attachments is confidential and
is intended solely for the attention and use of the named addressee(s).
If you are not the intended recipient, or a person responsible for passing
it on to the intended recipient, you are not authorised to hold a copy of
this information and you must therefore not disclose, copy, distribute, or
retain this message or any part of it. MAILTO:[EMAIL PROTECTED]
jk.zip
Description: jk.zip
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: RV: Fix for SEVERE: Certificate convertion failed, bug in Tomcat-connectors-4.1.24
You know that you should really post this to bugzilla if you really hope
for the problem to be fixed. It will get lost in this list otherwise.
http://nagoya.apache.org/bugzilla/
Jake
At 12:07 PM 3/26/2003 +0100, you wrote:
This is the patched class. It must be replaced at
$(TOMCAT_HOME)/server/lib/tomcat-jk2.jar jar-file.
You simply need to un-jar the file tomcat-jk2.jar and replace
JkCoyoteHandler.class with the patched one.
Thanks to Thorvald Natvig.
--
José Antonio Tarifa Lorenzo
Departamento de Desarrollo
Compañía Operadora del Mercado Español de Electricidad, S.A.
c/Alfonso XI, 6 4ª Planta. 28014 Madrid
email: [EMAIL PROTECTED]
--
-Mensaje original-
De: Ramsay Domloge [mailto:[EMAIL PROTECTED]
Enviado el: martes, 25 de marzo de 2003 19:01
Para: Tomcat Users List
Asunto: Re: Fix for SEVERE: Certificate convertion failed, bug in
Tomcat-connectors-4.1.24
Thank God!
I have been stuck on this for 10 days now, and I have been going a bit
loopy!
I really need to apply this patch *today*, but I'm having difficulty
getting hold of all the sourcecode that I need to apply the patch to
I would *really* appreciate it if you could help me out here and give me
a little more info on what I need to do; where to get the sourcecode and
what I need to build a new Tomcat, etc etc.
I am supposed to be delivering this project at the end of the week and
this bug has held me back 10 days... my boss is going loopy!
Thanks in advance,
Ramsay
Thorvald Natvig wrote:
For those that have been suffering problems using 2-way authenticating
with the JK2 Coyote connector, this patch should fix the problem. It's not
a good fix, but it's a fix nonetheless.
---
jakarta-tomcat-connectors-4.1.24-src/jk/java/org/apache/jk/server/JkCoyoteHandler.java
2003-03-19 10:21:04.0 +0100
+++
jakarta-tomcat-connectors-4.1.24-src-new/jk/java/org/apache/jk/server/JkCoyoteHandler.java
2003-03-25 17:10:54.0 +0100
@@ -384,7 +384,7 @@
// Extract SSL certificate information (if requested)
MessageBytes certString =
(MessageBytes)req.getNote(WorkerEnv.SSL_CERT_NOTE);
if( certString != null ) {
-byte[] certData = certString.getByteChunk().getBytes();
+byte[] certData = certString.toString().getBytes();
ByteArrayInputStream bais = new
ByteArrayInputStream(certData);
// Fill the first element.
-
Re: Fix for SEVERE: Certificate convertion failed, bug in Tomcat-connectors-4.1.24
Thank God!
I have been stuck on this for 10 days now, and I have been going a bit
loopy!
I really need to apply this patch *today*, but I'm having difficulty
getting hold of all the sourcecode that I need to apply the patch to
I would *really* appreciate it if you could help me out here and give me
a little more info on what I need to do; where to get the sourcecode and
what I need to build a new Tomcat, etc etc.
I am supposed to be delivering this project at the end of the week and
this bug has held me back 10 days... my boss is going loopy!
Thanks in advance,
Ramsay
Thorvald Natvig wrote:
For those that have been suffering problems using 2-way authenticating
with the JK2 Coyote connector, this patch should fix the problem. It's not
a good fix, but it's a fix nonetheless.
--- jakarta-tomcat-connectors-4.1.24-src/jk/java/org/apache/jk/server/JkCoyoteHandler.java 2003-03-19 10:21:04.0 +0100
+++ jakarta-tomcat-connectors-4.1.24-src-new/jk/java/org/apache/jk/server/JkCoyoteHandler.java 2003-03-25 17:10:54.0 +0100
@@ -384,7 +384,7 @@
// Extract SSL certificate information (if requested)
MessageBytes certString = (MessageBytes)req.getNote(WorkerEnv.SSL_CERT_NOTE);
if( certString != null ) {
-byte[] certData = certString.getByteChunk().getBytes();
+byte[] certData = certString.toString().getBytes();
ByteArrayInputStream bais = new ByteArrayInputStream(certData);
// Fill the first element.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
A R K E M E D I A T E C H N O L O G I E S L T D
VIEW POINTBASING VIEWBASINGSTOKEHAMPSHIRERG21 4RG
http://www.arkemedia.com
mailto:[EMAIL PROTECTED]
Tel : +44 1256 869 200 Fax : +44 1256 329 119
The information in this e-mail and in any attachments is confidential and
is intended solely for the attention and use of the named addressee(s).
If you are not the intended recipient, or a person responsible for passing
it on to the intended recipient, you are not authorised to hold a copy of
this information and you must therefore not disclose, copy, distribute, or
retain this message or any part of it. MAILTO:[EMAIL PROTECTED]
Fix for SEVERE: Certificate convertion failed, bug in Tomcat-connectors-4.1.24
For those that have been suffering problems using 2-way authenticating
with the JK2 Coyote connector, this patch should fix the problem. It's not
a good fix, but it's a fix nonetheless.
---
jakarta-tomcat-connectors-4.1.24-src/jk/java/org/apache/jk/server/JkCoyoteHandler.java
2003-03-19 10:21:04.0 +0100
+++
jakarta-tomcat-connectors-4.1.24-src-new/jk/java/org/apache/jk/server/JkCoyoteHandler.java
2003-03-25 17:10:54.0 +0100
@@ -384,7 +384,7 @@
// Extract SSL certificate information (if requested)
MessageBytes certString =
(MessageBytes)req.getNote(WorkerEnv.SSL_CERT_NOTE);
if( certString != null ) {
-byte[] certData = certString.getByteChunk().getBytes();
+byte[] certData = certString.toString().getBytes();
ByteArrayInputStream bais = new ByteArrayInputStream(certData);
// Fill the first element.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
build tomcat-connectors xdocs
Hi, Anybody knows how to build xdocs from jakarta-tomcat-connectors? It comes in XML format without linking to XSL... I suppose that it need to be build to HTML. Thanks, Herbert - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: RE : Apache - Tomcat connectors
A Connector consists of two parts: - A apache module in C (in this case mod_jk2) - A Tomcat module in java As the apache module runs as an integral part of apache, it makes sense to assume that apache is there to build this part of the connector. The connector is built against the headers and libraries of apache. -Original Message- From: Kelly, Terence [mailto:[EMAIL PROTECTED] Sent: Friday, March 14, 2003 11:13 PM To: 'Tomcat Users List' Subject: RE: RE : Apache - Tomcat connectors snip/ Why must we have Apache installed on the same machine on which mod_jk2 is built? snip/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: RE : Apache - Tomcat connectors
Hmmm, I thought I would illustrate my point about the JK2 docs being contradictory and incomplete by giving some examples of options from the online docs that do not work or are not supported in the current version of JK2 ... but now the whole section seems to have been removed from the page? Perhaps this is being updated to match the current code as we speak. If it is being updated, can you please show some virtual host examples for JK2. This is what had me baffled for a bit. I eventually did get JK2 running for my configuration, but the heaps of scary looking messages filling the logs and the slower than JK performance prompted me to remove it and go back to JK. Building it was a non event. If you can build JK, JK2 is no harder. Dennis -Original Message- From: apachep2 [mailto:[EMAIL PROTECTED] Sent: Friday, March 14, 2003 1:01 PM To: 'Tomcat Users List' Subject: RE: RE : Apache - Tomcat connectors Build: Search archive you will find a link to a site that teaches you step by step how to build mod_jk2. Since it's Friday, why don't I just give you the link http://www.pubbitch.org/jboss/mod_jk2.html. Configure: Follow tomcat-connector's document. -Original Message- From: LAGALISSE Eric [mailto:[EMAIL PROTECTED] Sent: March 14, 2003 12:12 PM To: Tomcat Users List Subject: RE : Apache - Tomcat connectors I'm not sure that configuring jk2 will be easier if we build it because someone can easily build something without knowing how to configure it. But i'm ready to believe you so provide us YOUR method to build this module and i'll write back onto this forum my point of view. I'm sure a lot of people are waiting for this build method. Eric LAGALISSE -Message d'origine- De : apachep2 [mailto:[EMAIL PROTECTED] Envoyé : vendredi 14 mars 2003 17:43 À : 'Tomcat Users List' Objet : RE: Apache - Tomcat connectors Disagree. I think the simplicity of jk2 configuration (not building of jk2) confuses people. Because, we as developer, get used to think complicated. I did feel frustrated building jk2. Once I built it, I was surprised that the configuration is so simple. -Original Message- From: Dennis Cartier [mailto:[EMAIL PROTECTED] Sent: March 14, 2003 11:32 AM To: Tomcat Users List Subject: RE: Apache - Tomcat connectors I agree. I struggled with JK2 for awhile but finally gave up and went back to JK. The docs were very confusing and contradictory. I suppose I could have appealed for help, but I got the impression that JK2 was still under constant change and without being able to be self sufficient, I felt the risk was unwarranted. Dennis -Original Message- From: Chris Dodunski [mailto:[EMAIL PROTECTED] Sent: Friday, March 14, 2003 7:07 AM To: Tomcat Users List Subject: Apache - Tomcat connectors I'm honestly astounded at the number of people struggling with successfully installing and configuring Apache - Tomcat connectors. An extensive search of apache.org (and other sites) reveals why. Documentation is vague, fragmented, and quite frankly confusing. It's frustrating and it's time wasting. Time I say for some clear, concise, blow by blow documentation on performing what should be a relatively simple procedure. Do you agree? - 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]
RE: RE : Apache - Tomcat connectors
I found the apache.org documentation as pertaining to JK2 quite simply inadequate, and that's putting it mildly. I've drafted my own procedure as a consequence. If you are interested, email me direct. Good luck! Chris. -Original Message- From: Dennis Cartier [mailto:[EMAIL PROTECTED] Sent: Tuesday, 18 March 2003 2:07 a.m. To: Tomcat Users List Subject: RE: RE : Apache - Tomcat connectors Hmmm, I thought I would illustrate my point about the JK2 docs being contradictory and incomplete by giving some examples of options from the online docs that do not work or are not supported in the current version of JK2 ... but now the whole section seems to have been removed from the page? Perhaps this is being updated to match the current code as we speak. If it is being updated, can you please show some virtual host examples for JK2. This is what had me baffled for a bit. I eventually did get JK2 running for my configuration, but the heaps of scary looking messages filling the logs and the slower than JK performance prompted me to remove it and go back to JK. Building it was a non event. If you can build JK, JK2 is no harder. Dennis -Original Message- From: apachep2 [mailto:[EMAIL PROTECTED] Sent: Friday, March 14, 2003 1:01 PM To: 'Tomcat Users List' Subject: RE: RE : Apache - Tomcat connectors Build: Search archive you will find a link to a site that teaches you step by step how to build mod_jk2. Since it's Friday, why don't I just give you the link http://www.pubbitch.org/jboss/mod_jk2.html. Configure: Follow tomcat-connector's document. -Original Message- From: LAGALISSE Eric [mailto:[EMAIL PROTECTED] Sent: March 14, 2003 12:12 PM To: Tomcat Users List Subject: RE : Apache - Tomcat connectors I'm not sure that configuring jk2 will be easier if we build it because someone can easily build something without knowing how to configure it. But i'm ready to believe you so provide us YOUR method to build this module and i'll write back onto this forum my point of view. I'm sure a lot of people are waiting for this build method. Eric LAGALISSE -Message d'origine- De : apachep2 [mailto:[EMAIL PROTECTED] Envoyé : vendredi 14 mars 2003 17:43 À : 'Tomcat Users List' Objet : RE: Apache - Tomcat connectors Disagree. I think the simplicity of jk2 configuration (not building of jk2) confuses people. Because, we as developer, get used to think complicated. I did feel frustrated building jk2. Once I built it, I was surprised that the configuration is so simple. -Original Message- From: Dennis Cartier [mailto:[EMAIL PROTECTED] Sent: March 14, 2003 11:32 AM To: Tomcat Users List Subject: RE: Apache - Tomcat connectors I agree. I struggled with JK2 for awhile but finally gave up and went back to JK. The docs were very confusing and contradictory. I suppose I could have appealed for help, but I got the impression that JK2 was still under constant change and without being able to be self sufficient, I felt the risk was unwarranted. Dennis -Original Message- From: Chris Dodunski [mailto:[EMAIL PROTECTED] Sent: Friday, March 14, 2003 7:07 AM To: Tomcat Users List Subject: Apache - Tomcat connectors I'm honestly astounded at the number of people struggling with successfully installing and configuring Apache - Tomcat connectors. An extensive search of apache.org (and other sites) reveals why. Documentation is vague, fragmented, and quite frankly confusing. It's frustrating and it's time wasting. Time I say for some clear, concise, blow by blow documentation on performing what should be a relatively simple procedure. Do you agree? - 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Apache - Tomcat connectors
I'm honestly astounded at the number of people struggling with successfully installing and configuring Apache - Tomcat connectors. An extensive search of apache.org (and other sites) reveals why. Documentation is vague, fragmented, and quite frankly confusing. It's frustrating and it's time wasting. Time I say for some clear, concise, blow by blow documentation on performing what should be a relatively simple procedure. Do you agree? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Apache - Tomcat connectors
Hi Why do so many other sites need to do this. Should the definitive source not be the Tomcat site? If people have time they should submit a working example. It would be nice if there was an official source for this type of information. It sure is a waste of time roaming the web for basic documentation when it should be readily available. I haven't much experience of all areas of Tomcat but I'd defiantly submit a HOW-TO for parts I do know. All it need is for a webmaster to look after the submissions. They could be easily then added to the existing tomcat site. Donie -Original Message- From: Chris Dodunski [mailto:[EMAIL PROTECTED] Sent: 14 March 2003 12:07 To: Tomcat Users List Subject: Apache - Tomcat connectors I'm honestly astounded at the number of people struggling with successfully installing and configuring Apache - Tomcat connectors. An extensive search of apache.org (and other sites) reveals why. Documentation is vague, fragmented, and quite frankly confusing. It's frustrating and it's time wasting. Time I say for some clear, concise, blow by blow documentation on performing what should be a relatively simple procedure. Do you agree? - 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: Apache - Tomcat connectors
I'm sure the tomcat developers would be delighted if you provided this documentation... -Original Message- From: Chris Dodunski [mailto:[EMAIL PROTECTED] Sent: 14 March 2003 12:07 To: Tomcat Users List Subject: Apache - Tomcat connectors I'm honestly astounded at the number of people struggling with successfully installing and configuring Apache - Tomcat connectors. An extensive search of apache.org (and other sites) reveals why. Documentation is vague, fragmented, and quite frankly confusing. It's frustrating and it's time wasting. Time I say for some clear, concise, blow by blow documentation on performing what should be a relatively simple procedure. Do you agree? - 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: Apache - Tomcat connectors
I submitted my write-up to the Linux StepxStep (http://www.linux-sxs.org) , and it can be found under Internet - Serving Apache Tomcat Java Server. This may sound really egotistical or something, but I would be very happy to include any articles or write-ups here (under your own name, of course). Or you could send them to the Linux StepxStep administrators directly (see the website for details). Regards, pascal chong Bodycombe, Andrew wrote: I'm sure the tomcat developers would be delighted if you provided this documentation... -Original Message- From: Chris Dodunski [mailto:[EMAIL PROTECTED] Sent: 14 March 2003 12:07 To: Tomcat Users List Subject: Apache - Tomcat connectors I'm honestly astounded at the number of people struggling with successfully installing and configuring Apache - Tomcat connectors. An extensive search of apache.org (and other sites) reveals why. Documentation is vague, fragmented, and quite frankly confusing. It's frustrating and it's time wasting. Time I say for some clear, concise, blow by blow documentation on performing what should be a relatively simple procedure. Do you agree? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Apache - Tomcat connectors
Hi Chris, I had the same problems, but I received to help from here, and now I can help you, the best page for it was www.johnturner.com/howto/winxp-howto.html It is excellent! Regards, Victor Gonzalez -Original Message- From: Chris Dodunski [mailto:[EMAIL PROTECTED] Sent: Friday, March 14, 2003 6:07 AM To: Tomcat Users List Subject: Apache - Tomcat connectors I'm honestly astounded at the number of people struggling with successfully installing and configuring Apache - Tomcat connectors. An extensive search of apache.org (and other sites) reveals why. Documentation is vague, fragmented, and quite frankly confusing. It's frustrating and it's time wasting. Time I say for some clear, concise, blow by blow documentation on performing what should be a relatively simple procedure. Do you agree? - 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: Apache - Tomcat connectors
I agree. I struggled with JK2 for awhile but finally gave up and went back to JK. The docs were very confusing and contradictory. I suppose I could have appealed for help, but I got the impression that JK2 was still under constant change and without being able to be self sufficient, I felt the risk was unwarranted. Dennis -Original Message- From: Chris Dodunski [mailto:[EMAIL PROTECTED] Sent: Friday, March 14, 2003 7:07 AM To: Tomcat Users List Subject: Apache - Tomcat connectors I'm honestly astounded at the number of people struggling with successfully installing and configuring Apache - Tomcat connectors. An extensive search of apache.org (and other sites) reveals why. Documentation is vague, fragmented, and quite frankly confusing. It's frustrating and it's time wasting. Time I say for some clear, concise, blow by blow documentation on performing what should be a relatively simple procedure. Do you agree? - 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: Apache - Tomcat connectors
Disagree. I think the simplicity of jk2 configuration (not building of jk2) confuses people. Because, we as developer, get used to think complicated. I did feel frustrated building jk2. Once I built it, I was surprised that the configuration is so simple. -Original Message- From: Dennis Cartier [mailto:[EMAIL PROTECTED] Sent: March 14, 2003 11:32 AM To: Tomcat Users List Subject: RE: Apache - Tomcat connectors I agree. I struggled with JK2 for awhile but finally gave up and went back to JK. The docs were very confusing and contradictory. I suppose I could have appealed for help, but I got the impression that JK2 was still under constant change and without being able to be self sufficient, I felt the risk was unwarranted. Dennis -Original Message- From: Chris Dodunski [mailto:[EMAIL PROTECTED] Sent: Friday, March 14, 2003 7:07 AM To: Tomcat Users List Subject: Apache - Tomcat connectors I'm honestly astounded at the number of people struggling with successfully installing and configuring Apache - Tomcat connectors. An extensive search of apache.org (and other sites) reveals why. Documentation is vague, fragmented, and quite frankly confusing. It's frustrating and it's time wasting. Time I say for some clear, concise, blow by blow documentation on performing what should be a relatively simple procedure. Do you agree? - 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 : Apache - Tomcat connectors
I'm not sure that configuring jk2 will be easier if we build it because someone can easily build something without knowing how to configure it. But i'm ready to believe you so provide us YOUR method to build this module and i'll write back onto this forum my point of view. I'm sure a lot of people are waiting for this build method. Eric LAGALISSE -Message d'origine- De : apachep2 [mailto:[EMAIL PROTECTED] Envoyé : vendredi 14 mars 2003 17:43 À : 'Tomcat Users List' Objet : RE: Apache - Tomcat connectors Disagree. I think the simplicity of jk2 configuration (not building of jk2) confuses people. Because, we as developer, get used to think complicated. I did feel frustrated building jk2. Once I built it, I was surprised that the configuration is so simple. -Original Message- From: Dennis Cartier [mailto:[EMAIL PROTECTED] Sent: March 14, 2003 11:32 AM To: Tomcat Users List Subject: RE: Apache - Tomcat connectors I agree. I struggled with JK2 for awhile but finally gave up and went back to JK. The docs were very confusing and contradictory. I suppose I could have appealed for help, but I got the impression that JK2 was still under constant change and without being able to be self sufficient, I felt the risk was unwarranted. Dennis -Original Message- From: Chris Dodunski [mailto:[EMAIL PROTECTED] Sent: Friday, March 14, 2003 7:07 AM To: Tomcat Users List Subject: Apache - Tomcat connectors I'm honestly astounded at the number of people struggling with successfully installing and configuring Apache - Tomcat connectors. An extensive search of apache.org (and other sites) reveals why. Documentation is vague, fragmented, and quite frankly confusing. It's frustrating and it's time wasting. Time I say for some clear, concise, blow by blow documentation on performing what should be a relatively simple procedure. Do you agree? - 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: RE : Apache - Tomcat connectors
Build: Search archive you will find a link to a site that teaches you step by step how to build mod_jk2. Since it's Friday, why don't I just give you the link http://www.pubbitch.org/jboss/mod_jk2.html. Configure: Follow tomcat-connector's document. -Original Message- From: LAGALISSE Eric [mailto:[EMAIL PROTECTED] Sent: March 14, 2003 12:12 PM To: Tomcat Users List Subject: RE : Apache - Tomcat connectors I'm not sure that configuring jk2 will be easier if we build it because someone can easily build something without knowing how to configure it. But i'm ready to believe you so provide us YOUR method to build this module and i'll write back onto this forum my point of view. I'm sure a lot of people are waiting for this build method. Eric LAGALISSE -Message d'origine- De : apachep2 [mailto:[EMAIL PROTECTED] Envoyé : vendredi 14 mars 2003 17:43 À : 'Tomcat Users List' Objet : RE: Apache - Tomcat connectors Disagree. I think the simplicity of jk2 configuration (not building of jk2) confuses people. Because, we as developer, get used to think complicated. I did feel frustrated building jk2. Once I built it, I was surprised that the configuration is so simple. -Original Message- From: Dennis Cartier [mailto:[EMAIL PROTECTED] Sent: March 14, 2003 11:32 AM To: Tomcat Users List Subject: RE: Apache - Tomcat connectors I agree. I struggled with JK2 for awhile but finally gave up and went back to JK. The docs were very confusing and contradictory. I suppose I could have appealed for help, but I got the impression that JK2 was still under constant change and without being able to be self sufficient, I felt the risk was unwarranted. Dennis -Original Message- From: Chris Dodunski [mailto:[EMAIL PROTECTED] Sent: Friday, March 14, 2003 7:07 AM To: Tomcat Users List Subject: Apache - Tomcat connectors I'm honestly astounded at the number of people struggling with successfully installing and configuring Apache - Tomcat connectors. An extensive search of apache.org (and other sites) reveals why. Documentation is vague, fragmented, and quite frankly confusing. It's frustrating and it's time wasting. Time I say for some clear, concise, blow by blow documentation on performing what should be a relatively simple procedure. Do you agree? - 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: RE : Apache - Tomcat connectors
Regarding the document that apachep2 refers to: Step 4 (which describes the process of building the pieces of mod_jk2) contains something puzzling: You will also need to point the apache2.home property somewhere sensible. Why must we have Apache installed on the same machine on which mod_jk2 is built?? I'm trying to run Apache and Tomcat on different machines, but the two seem to be entangled in counter-intuitive ways, as illustrated by the dependence of the mod_jk2 build procedure on Apache. This isn't really a question, just a comment for developers. Newcomers to Tomcat will have fewer confused questions for you if Tomcat is kept orthogonal to other things, like Apache. Clean separations between components make it easier to reason about what's going on. In the present case, there seems to be an implicit assumption that mod_jk2 will be used to connect an Apache and a Tomcat that are both running on the same machine. Wouldn't we be better off without assumptions like this? -Original Message- From: apachep2 [mailto:[EMAIL PROTECTED] Sent: Friday, March 14, 2003 10:01 AM To: 'Tomcat Users List' Subject: RE: RE : Apache - Tomcat connectors Build: Search archive you will find a link to a site that teaches you step by step how to build mod_jk2. Since it's Friday, why don't I just give you the link http://www.pubbitch.org/jboss/mod_jk2.html. Configure: Follow tomcat-connector's document. -Original Message- From: LAGALISSE Eric [mailto:[EMAIL PROTECTED] Sent: March 14, 2003 12:12 PM To: Tomcat Users List Subject: RE : Apache - Tomcat connectors I'm not sure that configuring jk2 will be easier if we build it because someone can easily build something without knowing how to configure it. But i'm ready to believe you so provide us YOUR method to build this module and i'll write back onto this forum my point of view. I'm sure a lot of people are waiting for this build method. Eric LAGALISSE -Message d'origine- De : apachep2 [mailto:[EMAIL PROTECTED] Envoyé : vendredi 14 mars 2003 17:43 À : 'Tomcat Users List' Objet : RE: Apache - Tomcat connectors Disagree. I think the simplicity of jk2 configuration (not building of jk2) confuses people. Because, we as developer, get used to think complicated. I did feel frustrated building jk2. Once I built it, I was surprised that the configuration is so simple. -Original Message- From: Dennis Cartier [mailto:[EMAIL PROTECTED] Sent: March 14, 2003 11:32 AM To: Tomcat Users List Subject: RE: Apache - Tomcat connectors I agree. I struggled with JK2 for awhile but finally gave up and went back to JK. The docs were very confusing and contradictory. I suppose I could have appealed for help, but I got the impression that JK2 was still under constant change and without being able to be self sufficient, I felt the risk was unwarranted. Dennis -Original Message- From: Chris Dodunski [mailto:[EMAIL PROTECTED] Sent: Friday, March 14, 2003 7:07 AM To: Tomcat Users List Subject: Apache - Tomcat connectors I'm honestly astounded at the number of people struggling with successfully installing and configuring Apache - Tomcat connectors. An extensive search of apache.org (and other sites) reveals why. Documentation is vague, fragmented, and quite frankly confusing. It's frustrating and it's time wasting. Time I say for some clear, concise, blow by blow documentation on performing what should be a relatively simple procedure. Do you agree? - 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]
Re: Apache - Tomcat connectors
Thanks Victor, You weren't exaggerating either! This author does three things typically lacking in software documentation. 1) Gives a methodical blow by blow instruction on performing all that is required (unambiguous, how good code is written :-) 2) Explains the reason 'why' at each step 3) Clearly describes how to perform a self check (test) every so often, eliminating mistakes Points 2 and 3 (frequently overlooked) are critical for acquiring the ability to effectively solve unanticipated problems when they arise. Even failing a successful result, at least problems then posted to this mailing list are more specific and detailed. Almost miraculously, the one with the problem is now more informed! This is a good thing, yes? Chris. - Original Message - From: Victor Gonzalez [EMAIL PROTECTED] To: 'Tomcat Users List' [EMAIL PROTECTED] Sent: Saturday, March 15, 2003 3:55 AM Subject: RE: Apache - Tomcat connectors Hi Chris, I had the same problems, but I received to help from here, and now I can help you, the best page for it was www.johnturner.com/howto/winxp-howto.html It is excellent! Regards, Victor Gonzalez -Original Message- From: Chris Dodunski [mailto:[EMAIL PROTECTED] Sent: Friday, March 14, 2003 6:07 AM To: Tomcat Users List Subject: Apache - Tomcat connectors I'm honestly astounded at the number of people struggling with successfully installing and configuring Apache - Tomcat connectors. An extensive search of apache.org (and other sites) reveals why. Documentation is vague, fragmented, and quite frankly confusing. It's frustrating and it's time wasting. Time I say for some clear, concise, blow by blow documentation on performing what should be a relatively simple procedure. Do you agree? - 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: Apache - Tomcat connectors
You've hit the nail on the head Donie. - Original Message - From: Donie Kelly [EMAIL PROTECTED] To: 'Tomcat Users List' [EMAIL PROTECTED] Sent: Saturday, March 15, 2003 1:09 AM Subject: RE: Apache - Tomcat connectors Hi Why do so many other sites need to do this. Should the definitive source not be the Tomcat site? If people have time they should submit a working example. It would be nice if there was an official source for this type of information. It sure is a waste of time roaming the web for basic documentation when it should be readily available. I haven't much experience of all areas of Tomcat but I'd defiantly submit a HOW-TO for parts I do know. All it need is for a webmaster to look after the submissions. They could be easily then added to the existing tomcat site. Donie -Original Message- From: Chris Dodunski [mailto:[EMAIL PROTECTED] Sent: 14 March 2003 12:07 To: Tomcat Users List Subject: Apache - Tomcat connectors I'm honestly astounded at the number of people struggling with successfully installing and configuring Apache - Tomcat connectors. An extensive search of apache.org (and other sites) reveals why. Documentation is vague, fragmented, and quite frankly confusing. It's frustrating and it's time wasting. Time I say for some clear, concise, blow by blow documentation on performing what should be a relatively simple procedure. Do you agree? - 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]
Question about building jakarta-tomcat-connectors-4.1.18-src
Hi, I'm having issues building the jakarta-tomcat-connectors (4.1.18) from source. The build environment is: server platform: redhat linux 7.3 java version: j2sdk 1.4.1_01 ant version: 1.5 tomcat version: 4.1.18 I've setup up the environment for JAVA_HOME, CATALINA_HOME, PATH, etc. The errors I'm getting are: jkjava: [javac] Compiling 31 source files to /usr/local/src/jakarta-tomcat-connectors-4.1.18-src/jk/build/classes [javac] /usr/local/src/jakarta-tomcat-connectors-4.1.18-src/jk/java/org/apache/jk/common/JkInputStream.java:66: package javax.servlet does not exist [javac] import javax.servlet.ServletInputStream; [javac] ^ [javac] /usr/local/src/jakarta-tomcat-connectors-4.1.18-src/jk/java/org/apache/jk/common/JkInputStream.java:67: package javax.servlet.http does not exist [javac] import javax.servlet.http.HttpServletRequest; [javac] ^ [javac] /usr/local/src/jakarta-tomcat-connectors-4.1.18-src/jk/java/org/apache/jk/common/JkInputStream.java:68: package javax.servlet.http does not exist [javac] import javax.servlet.http.Cookie; [javac] ^ [javac] Note: Some input files use or override a deprecated API. [javac] Note: Recompile with -deprecation for details. [javac] 3 errors Any help would be appreciated. Cheers, Ryan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Question about building jakarta-tomcat-connectors-4.1.18-src
Servlet.jar is not in your classpath Regards, PQ This Guy Thinks He Knows Everything This Guy Thinks He Knows What He Is Doing -Original Message- From: Ryan Dooley [mailto:[EMAIL PROTECTED]] Sent: February 19, 2003 12:57 PM To: [EMAIL PROTECTED] Subject: Question about building jakarta-tomcat-connectors-4.1.18-src Hi, I'm having issues building the jakarta-tomcat-connectors (4.1.18) from source. The build environment is: server platform: redhat linux 7.3 java version: j2sdk 1.4.1_01 ant version: 1.5 tomcat version: 4.1.18 I've setup up the environment for JAVA_HOME, CATALINA_HOME, PATH, etc. The errors I'm getting are: jkjava: [javac] Compiling 31 source files to /usr/local/src/jakarta-tomcat-connectors-4.1.18-src/jk/build/classes [javac] /usr/local/src/jakarta-tomcat-connectors-4.1.18-src/jk/java/org/apache/jk/co mmon/JkInputStream.java:66: package javax.servlet does not exist [javac] import javax.servlet.ServletInputStream; [javac] ^ [javac] /usr/local/src/jakarta-tomcat-connectors-4.1.18-src/jk/java/org/apache/jk/co mmon/JkInputStream.java:67: package javax.servlet.http does not exist [javac] import javax.servlet.http.HttpServletRequest; [javac] ^ [javac] /usr/local/src/jakarta-tomcat-connectors-4.1.18-src/jk/java/org/apache/jk/co mmon/JkInputStream.java:68: package javax.servlet.http does not exist [javac] import javax.servlet.http.Cookie; [javac] ^ [javac] Note: Some input files use or override a deprecated API. [javac] Note: Recompile with -deprecation for details. [javac] 3 errors Any help would be appreciated. Cheers, Ryan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Question about building jakarta-tomcat-connectors-4.1.18-src
In my opinion you will have a much easier time of it if you use configure instead: ./configure --with-apxs=/path/to/apache/bin/apxs make make install I've had all kinds of problems with ant on RH 7.2 trying to build the connectors. The configure method is painless. John -Original Message- From: Ryan Dooley [mailto:[EMAIL PROTECTED]] Sent: Wednesday, February 19, 2003 12:57 PM To: [EMAIL PROTECTED] Subject: Question about building jakarta-tomcat-connectors-4.1.18-src Hi, I'm having issues building the jakarta-tomcat-connectors (4.1.18) from source. The build environment is: server platform: redhat linux 7.3 java version: j2sdk 1.4.1_01 ant version: 1.5 tomcat version: 4.1.18 I've setup up the environment for JAVA_HOME, CATALINA_HOME, PATH, etc. The errors I'm getting are: jkjava: [javac] Compiling 31 source files to /usr/local/src/jakarta-tomcat-connectors-4.1.18-src/jk/build/classes [javac] /usr/local/src/jakarta-tomcat-connectors-4.1.18-src/jk/java/or g/apache/jk/common/JkInputStream.java:66: package javax.servlet does not exist [javac] import javax.servlet.ServletInputStream; [javac] ^ [javac] /usr/local/src/jakarta-tomcat-connectors-4.1.18-src/jk/java/or g/apache/jk/common/JkInputStream.java:67: package javax.servlet.http does not exist [javac] import javax.servlet.http.HttpServletRequest; [javac] ^ [javac] /usr/local/src/jakarta-tomcat-connectors-4.1.18-src/jk/java/or g/apache/jk/common/JkInputStream.java:68: package javax.servlet.http does not exist [javac] import javax.servlet.http.Cookie; [javac] ^ [javac] Note: Some input files use or override a deprecated API. [javac] Note: Recompile with -deprecation for details. [javac] 3 errors Any help would be appreciated. Cheers, Ryan - 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: Question about building jakarta-tomcat-connectors-4.1.18-src
Hi, Thanks, that got me past that part. I had put the common lib directory in my class path but not the jar directly. Thanks again, Cheers, Ryan [EMAIL PROTECTED] wrote: Servlet.jar is not in your classpath Regards, PQ This Guy Thinks He Knows Everything This Guy Thinks He Knows What He Is Doing -Original Message- From: Ryan Dooley [mailto:[EMAIL PROTECTED]] Sent: February 19, 2003 12:57 PM To: [EMAIL PROTECTED] Subject: Question about building jakarta-tomcat-connectors-4.1.18-src Hi, I'm having issues building the jakarta-tomcat-connectors (4.1.18) from source. The build environment is: server platform: redhat linux 7.3 java version: j2sdk 1.4.1_01 ant version: 1.5 tomcat version: 4.1.18 I've setup up the environment for JAVA_HOME, CATALINA_HOME, PATH, etc. The errors I'm getting are: jkjava: [javac] Compiling 31 source files to /usr/local/src/jakarta-tomcat-connectors-4.1.18-src/jk/build/classes [javac] /usr/local/src/jakarta-tomcat-connectors-4.1.18-src/jk/java/org/apache/jk/co mmon/JkInputStream.java:66: package javax.servlet does not exist [javac] import javax.servlet.ServletInputStream; [javac] ^ [javac] /usr/local/src/jakarta-tomcat-connectors-4.1.18-src/jk/java/org/apache/jk/co mmon/JkInputStream.java:67: package javax.servlet.http does not exist [javac] import javax.servlet.http.HttpServletRequest; [javac] ^ [javac] /usr/local/src/jakarta-tomcat-connectors-4.1.18-src/jk/java/org/apache/jk/co mmon/JkInputStream.java:68: package javax.servlet.http does not exist [javac] import javax.servlet.http.Cookie; [javac] ^ [javac] Note: Some input files use or override a deprecated API. [javac] Note: Recompile with -deprecation for details. [javac] 3 errors Any help would be appreciated. Cheers, Ryan - 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]
