Dear All,
We're expiriencing a strange behaviour of JRun 3.1 running on Solaris 2.8 box.
Our web application is time-to-time expiriencing some weird blackouts. After
some investigation I came to the conclusion that something is wrong with the
JRun -> Apache connector.
Our apache error log contains several entries like the following ones:
[Sun Apr 28 22:46:48 2002] [notice] jrApache[2985] command error: 0 Error 0 <-
[8]
[Sun Apr 28 22:46:54 2002] [notice] jrApache[3015] Unexpected command 3 <- [8]
while fetching servlet-mappings
[Sun Apr 28 22:46:58 2002] [notice] jrApache[3030] Unexpected command 3 <- [8]
while fetching servlet-mappings
[Sun Apr 28 22:47:05 2002] [notice] jrApache[3055] Unexpected command 3 <- [8]
while fetching servlet-mappings
[Sun Apr 28 22:47:09 2002] [notice] jrApache[3077] Unexpected command 3 <- [8]
while fetching servlet-mappings
[Sun Apr 28 22:47:12 2002] [notice] jrApache[3090] command error: 0 Error 0 <-
[9]
Time to time a message "JRun Connector - Protocol Error ..." appears in
browsers.
Also in our own application's logs appears "corrupted" data, like:
[280402-223545] DEBUG - ['GET^L] - ......
or
[280402-223926] DEBUG - [servlet-m] - .....
Where the correct form of the log entry should be something like:
[280402-223941] DEBUG - [x.x.x.x] - ....
The text between the brackets is the visitor's IP which we obtain from the
HTTPRequest instace by issuing .getRemoteAddr() or
getHeader("X-Forwarded-For") (in the case when the client's request is
forwared by a HTTP proxy).
I think that something is wrong with the connector and it makes some serious
messing with the request's http headers.
Our enviroment:
SunOS 5.8 Generic_108528-07 sun4u sparc SUNW,UltraSPARC-IIi-cEngine
JRun 3.1.36494
java version "1.3.1_02"
Apache 1.3.20 with modSSL
We have re-compiled the modjrun.so module, according to the Macromedia's
recomendation (we had a problem with SSL (getScheme() was not working
corrently). All we did was to change the includes in the top-level makefile
and made them to point to the apache's includes (we've followed step-by-step
the article ; i really don't remember now the article's ID). We've compiled
the connector with gcc 2.95.2
Also, note, that we have several instances of JRun servers being "connected"
to a single apache instace (6 servers) and we are expiriencing problems with
one and only application which is entirely based on Turbine.
I really doubt that there is a bug in the web-application that makes the
JRun's connector to mess the HTTP headers, since the application was "heavily
tested" and anyway we've never encoutered such situations, while testing
under Apache & Tomcat 4.0.x
Any ideas ?
Best Regards
Filippos Slavik
--
################################################################
Filippos Slavik
FORTHnet R&D, Heraklion, Greece
e-mail : [EMAIL PROTECTED]
phone : (+3) 810 391230
################################################################
"The software said 'runs on Win95 or better,' so I installed it
on Linux..."
______________________________________________________________________
This list and all House of Fusion resources hosted by CFHosting.com. The place for
dependable ColdFusion Hosting.
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
