Weblogic Not responding to HEAD requests!

[MattYeates]

Hi, I'm a bit of a n00bie on weblogic, but here goes....

I have a two machine cluster with one admin server (machines: bea1 and bea2 for ease). I have two apache 1.3.23 servers accessed via alteon load balancers (machines: alteon, web1 and web2). When the portal was first developed access was:

http://myserver/myapp/index.jsp

Whereas what was required is

http://myserver

So to get past this I made my "myapp" the default application for both my managed servers, and the default server name is set to "alteon". In my apache conf I have the following:


<IfModule mod_weblogic.c>
MatchExpression *.jsp
WebLogicCluster bea1:7468,bea2:7468
CookieName myapp
MaxPostSize 2048
ConnectTimeoutSecs 120
DefaultFileName index.jsp
ConnectRetrySecs 2
</IfModule>

<Location /myapp>
SetHandler weblogic-handler
PathTrim /myapp
</Location>

<Location >
SetHandler weblogic-handler
DefaultFileName index.jsp
# PathPrepend /myapp
</Location>

<Location /static>
SetHandler default-handler
</Location>

<Location /staticimages>
SetHandler default-handler
</Location>


This acheives what I require (although the <Location > is a bit extreme>) but the following script returns a server error 500...

telnet alteon 80
HEAD / HTTP1.1
Host: alteon
Connection: Close
<cr>
<cr>

If I replace the head with something that apache serves :

telnet alteon 80
HEAD /static/image.gif HTTP1.1
Host: alteon
Connection: Close
<cr>
<cr>

I get a 200 response (most favourable).

With Bea returning an error 500, it means that none of my pages are being cached by the site host and ultimately means I get far too many database hits.

What am I doing wrong and can someone point me in the right direction?

Hopefully


Matthew

 

[MattYeates]

Oops - additional - using Weblogic 6.1 sp 2 and Portal 4.0 sp1 on Solaris 2.8 - Everything is patched to advised levels