|
Hello folks,
I’m working on porting some legacy code into Java, piecewise. The legacy code has a script (which I have to keep for now) that generates a header and footer separately for a page using SSIs for a given HTML page request, e.g., a page on the server would look like
<!--#exec cmd=”/path/to/headerfooterscript --showheader”à … (some HTML or other SSI directives here) … <!--#exec cmd=”/path/to/headerfooterscript --showfooter”à
Instead of HTML files now, I have JSPs. I have an Apache (2.0.53) installation handing off requests to a Tomcat (5.5.7) server via mod_jk (1.2.8). The output from those requests has the header/footer includes in it, after which Apache is configured to process the output for the SSIs (using “SetOutputFilter INCLUDES” in the configuration) and run those. Apache parses the output for SSIs but fails to run the “headerfooterscript”, returning this message in the log:
(2)No such file or directory: change of working directory failed
The directory exists, the script exists, it’s executable, the Apache user has permissions to run it, but I get this message. Doing a little debugging, I see that the value that Apache has for the working directory is empty.
Now, one odd thing is that doing this works if I use “#exec cgi” or “#include virtual” commands in the JSP output instead of “#exec cgi” (using either of those is undesirable for other reasons right now), it works --- I get the output from a test script or file included in the output from the JSP.
The other odd thing is that if I write a plain CGI script (Perl in this case) to return as output the header/footer includes using the “#exec cmd” syntax, it also works --- no “(2)No such file or directory: change of working directory failed” messages. Debugging shows that the value for the working directory is being set correctly for all the working cases.
So it appears that it might be a bug vis-à-vis Apache and mod_jk in some fashion, either before the request is handed off, or after it comes back. I should note that the original issue was spotted under Solaris 8, but it also happens under Solaris 9. Also, I don’t have any third-party modules compiled either. I haven’t tested Apache under Linux (wouldn’t be the production environment anyway) to see if it also happens there.
If this rings a bell with anyone and you have a solution (or viable suggestions), I’d be happy to hear it. If it seems like a bug, I’ll put a bug report in at http://issues.apache.org/bugzilla/ (I’ve been searching there but haven’t found any similar-sounding issues yet).
Regards, Joel Parramore
|
|