I have investigated a bit more on the problems with ncWMS/thredds. On a
freshly restarted server, I don't see any problems as long as I don't
use our openlayers-based WMS client. I even put a high load on the
machine, reading both getCapabilities and getMap.
The difference between the command-line and openlayer-client is, that
the openlayer-client has to read the getCapabilities document through a
web-proxy, which is on the same machine as the client-web-page. This is
from a different domain.
As long as a request is stateless, reading through a proxy is no
problem, but the GetCapabilities response is strange since it sets a new
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2)
HTTP/1.1 200 OK
Set-Cookie: JSESSIONID=FC5891CC7B9BE38017750523E0CAEE83; Path=/thredds
Expires: Thu, 01 Jan 1970 00:00:00 GMT
Date: Thu, 18 Feb 2010 10:25:08 GMT
Why does ncWMS start a new session, ignoring the old one? And in my case
with the proxy, the cookie will be set against the proxy, not the
thredds, so all further requests to thredds will use the old, outdated
I don't know if this is actually the reason, it is just an idea yet. Is
it simple to disable session for the whole ncWMS part?