Swapping out jbossweb. Sar might work, but it's pretty risky in itself. If you're averse to the risk in moving to 5.1, I'd be just as averse to the risk of swapping JBossWeb.
Swapping out jbossweb. Sar might work, but it's pretty risky in itself. If you're averse to the risk in moving to 5.1, I'd be just as averse to the risk of swapping JBossWeb.
That said, if you have a good automated test suite, then you might be able to get enough confidence in the swap to take it to production. This sort of situation is where I get a lot of value from the RedHat/JBoss EAP subscription - they will backport fixes to the version of JBoss that you're running, plus test and verify it for you.
Thanks for that information. Yes - I plan to test this before deploying to production. Also I'm going to deploy on one production node first to verify it fixes the issue we have.
The issue is only occuring in production via our customer's mobile network and/or a buggy mobile client. – Conor Dec 3 '09 at 17:21 Interesting... what's the bug? – skaffman Dec 3 '09 at 17:23 ChunkedInputFilter in JBoss Web 2.1.2 is not very good at handling "Transfer-Encoding: chunked" requests.
There have been some fixes applied in 2.1.3. – Conor Dec 3 '09 at 17:33.
I managed to reproduce the bug we had and verified that it did not occur with jboss 5.1.0. I upgraded to jboss 5.1.0 to sort this out. That plus lots of system testing and everyone was happy.
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.