20 reputation
5
bio website rockittsolutions.com
location London, United Kingdom
age
visits member for 4 years, 9 months
seen Jun 19 at 15:44

Apr
4
awarded  Supporter
Jun
18
accepted Varnish purge on POST or PUT
Jun
18
revised Varnish purge on POST or PUT
added 479 characters in body
Jun
18
comment Varnish purge on POST or PUT
Turns out I was mis-understanding the difference between purge and ban. A ban line seemed to have the right effect, although it's anyone's guess what will happen under load!
Jun
18
awarded  Student
Jun
18
comment Varnish purge on POST or PUT
That doesn't appear to work - Varnish is still not fetching the object freshly after the POST. I'm running a simple GET - change - POST - GET and the object returned isn't the changed object.
Jun
18
awarded  Editor
Jun
18
revised Varnish purge on POST or PUT
added 260 characters in body
Jun
18
asked Varnish purge on POST or PUT
Mar
14
answered Phantom process killing
Feb
9
comment Phantom process killing
It seems pressing return submits the comment. Interesting. I was going to ask - when you say "enabling core dumps" do you mean from Java or from the operating system? It seems Java has no warning when it's about to be killed.
Feb
9
comment Phantom process killing
I've built an identical setup on another of our servers and they're still being killed, so it's not faulty memory, and I'm still not getting any meaningful output.
Feb
3
asked Phantom process killing
Jul
5
awarded  Scholar
Jul
5
comment Jetty8 virtual hosts
Thanks Allen, this is roughly what I did, but I used Jetty instead, and each API instance tells the Jetty proxy server which port to find it on, and the Jetty proxy forwards the request appropriately.
Jul
5
accepted Jetty8 virtual hosts
Jun
21
awarded  Tumbleweed
Jun
14
asked Jetty8 virtual hosts