Problems compiling mod_jk 1.2.6
Hi, We are trying to compile mod_jk 1.2.6 on a Linux system with 2.2 kernel where we get this error: [EMAIL PROTECTED] native]# make Making all in common make[1]: Entering directory `/downloads/jakarta-tomcat-connectors-jk-1.2.6-src/jk/native/common' /bin/sh /usr/local/apache2/build/libtool --silent --mode=compile gcc -I/usr/local/apache2/include -g -O2 -g -O2 -pthread -DHAVE_APR -I/downloads/httpd-2.0.52/srclib/apr/include -g -O2 -DLINUX=2 -D_REENTRANT -D_XOPEN_SOURCE=500 -D_BSD_SOURCE -D_SVID_SOURCE -D_GNU_SOURCE -I /usr/local/jdk1.4/include -I /usr/local/jdk1.4/include/ -c jk_ajp12_worker.c /bin/sh /usr/local/apache2/build/libtool --silent --mode=compile gcc -I/usr/local/apache2/include -g -O2 -g -O2 -pthread -DHAVE_APR -I/downloads/httpd-2.0.52/srclib/apr/include -g -O2 -DLINUX=2 -D_REENTRANT -D_XOPEN_SOURCE=500 -D_BSD_SOURCE -D_SVID_SOURCE -D_GNU_SOURCE -I /usr/local/jdk1.4/include -I /usr/local/jdk1.4/include/ -c jk_connect.c jk_connect.c: In function `jk_resolve': jk_connect.c:56: `in_addr_t' undeclared (first use in this function) jk_connect.c:56: (Each undeclared identifier is reported only once jk_connect.c:56: for each function it appears in.) jk_connect.c:56: parse error before `laddr' jk_connect.c:100: `laddr' undeclared (first use in this function) make[1]: *** [jk_connect.lo] Error 1 make[1]: Leaving directory `/downloads/jakarta-tomcat-connectors-jk-1.2.6-src/jk/native/common' make: *** [all-recursive] Error 1 Apparently when Googleing for it it seems like the older code base of the 2.2 kernel does not have that in_addr_t defined. How is this amended? Thanks, Lars - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Custom tag attribute runtime expression containing and delimited by quotes. Supported in Tomcat, but not other JSP containers. What is the standard?
We won't be going to Tomcat 5 at work for a couple of months yet, but I'll try it out at home when I have some spare time. Shapira, Yoav [EMAIL PROTECTED] wrote in message news:[EMAIL PROTECTED] Hi, What happens with Tomcat 5.x? (To which JSP Spec 2.0, not 1.2, applies). The reason I ask is that while you can file away bugs against 4.x to your heart's content, it's not being actively developed and you shouldn't hold your breath waiting for a fix. Yoav Shapira http://www.yoavshapira.com -Original Message- From: news [mailto:[EMAIL PROTECTED] On Behalf Of Sean Dockery Sent: Thursday, November 18, 2004 11:21 AM To: [EMAIL PROTECTED] Subject: Re: Custom tag attribute runtime expression containing and delimited by quotes. Supported in Tomcat, but not other JSP containers. What is the standard? Hmmm... We found in section JSP 2.6 (page 41) in the Core Syntax and Semantics chapter of the JSP 1.2 specification that this... mytags:tag value=%= hi! % / ...is expressly illegal. Should this be considered to be a bug in Jasper? Sean Dockery [EMAIL PROTECTED] wrote in message news:[EMAIL PROTECTED] Hello, We recently came upon an issue in migrating our web application from Tomcat 4.1.x to SAP Web AS 6.4 SP7. Here is an example of the offending code (which involves indexed beans managed by a Struts ActionForm): logic:iterate ... indexId=offset Name: html:text property=%= people[ + offset + ].name %/ /logic:iterate The quotes embedded in the property attribute's runtime expression work fine under Tomcat, but failed under SAP Web AS during JSP translation. The Web AS JSP compiler sees the quote before the word people as the closing delimiter for the property attribute value. We found that the following variations work in both Tomcat and SAP Web AS. html:text property='%= people[ + offset + ].name %'/ (using apostrophes instead of quotes to delimit the attribute values) html:text property=%= \people[\ + offset + \].name\ %/ (escaping the embedded quotes) The former solution seems to be sanctioned (according to Google, anyway). The latter solution (though looking to be pure evil) seems to solve a situation where you would have both quotes and apostrophes in the same attribute value. Is there anything in the (current or previous) JSP specification dealing with quotes embedded in runtime expressions? (It is an unfortunately happy coincidence that Jasper supports embedded quotes; anyone else enjoying this behaviour should be aware that it may not be supported by other containers.) Thanks for your precious time. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Errors in mod_jk2 log
Hi Phillip, I think it would be nice if this is explained by someone and then ideally put into the docs for Tomcat. I wonder how many more system admins sort of silently inore these messages since they do not harm necessarly - but then who knows. So I second your idea. Lars Phillip Qin wrote: There are tons of these messages appeared in my log. I've asked this question before, no one seems bother answering it. Shall we post it to connector's dev list? -Original Message- From: Lars George [mailto:[EMAIL PROTECTED] Sent: November 17, 2004 7:31 PM To: Tomcat Users List Subject: Errors in mod_jk2 log Hi, We get these errors in the Apache logs coming from mod_jk2: [Wed Nov 17 13:37:32 2004] [error] ajp13.service() ajpGetReply recoverable error 3 [Wed Nov 17 13:37:32 2004] [error] ajp13.service() Error forwarding ajp13:b19socket 1 0 [Wed Nov 17 13:37:32 2004] [error] mod_jk2.handler() Error connecting to tomcat 3, status 200 I read the jk_worker_ajp13.c code to see what that means, but cannot really make out how to determine the actual reason. Could someone suggest how to investigate that further? Would the extra debug help? And where would I switch it on best? I mean on the channel or socket element? Thanks, Lars - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] !DSPAM:419bed4791457924012082! - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
