Open GoogleCodeExporter opened 9 years ago
Ok, after experimenting with other browsers and clearing server and client side
cache, I saw lines like these that look suspicious - getting HTTP 404 on
cache.html:
10.0.254.17 - - [17/Apr/2012:12:32:50 +0200] "GET
/pithos/E51B1BDBE35014125F2D8FCE2362E48D.cache.html HTTP/1.1" 404 1101
"http://example.org/pithos/" "Mozilla/5.0 (X11; Linux x86_64)
AppleWebKit/535.19 (KHTML, like Gecko) Chrome/18.0.1025.162 Safari/535.19"
Original comment by ngara...@gmail.com
on 17 Apr 2012 at 10:36
Check if this .cache file exists somewhere in gss.ear/gss.war. If it does not
exist then your browser still caches something that it shouldn't. If it does
exist then there is probably a problem with apache configuration.
Original comment by chstath
on 17 Apr 2012 at 11:04
Hmm, these *.cache.html files are present in the /tmp/ directory inside jboss
directory - /tmp/.../gss.war/ and /tmp/..../gss-admin.war/
What do you mean by "there is something wrong with apache configuration"? If
files exist in this tmp directory and I still get HTTP 404 instead HTTP 200?
Original comment by ngara...@gmail.com
on 17 Apr 2012 at 12:21
Files in the tmp inside jboss may be there from previous deployments. I was
referring to the gss.ear file used for deployment.
If files exist there and apache cannot serve them what else can it be ?
Did you try to hit jboss directly (bypassing the web server) ?
Original comment by chstath
on 17 Apr 2012 at 1:27
I discovered gss.ear files on two nodes were not the same. After fixing this
issue, there is no blue screen appearing as it seems.
Thanks for help.
Original comment by ngara...@gmail.com
on 18 Apr 2012 at 11:02
Original issue reported on code.google.com by
ngara...@gmail.com
on 17 Apr 2012 at 7:52Attachments: