Hi pkragunath,
don't know much about client side BB code but I can tell you with the log..
Apr 25, 2009 3:00:29 PM nl.gx.webmanager.handler.forms.foundation.FormProcessor processForm
INFO: replacing host: foo:-1 to e.test.hari.com, new URL: http://e.test.hari.com
Apr 25, 2009 3:00:29 PM nl.gx.webmanager.handler.forms.foundation.FormHandler doPost
INFO: redirecting to: http://e.test.hari.com
End of a regular form post. The redirect URL is being constructed and the redirect is send. From this log snippet I cannot determine how long execution took but anyway at this point your browser gets its response.
Application time: 18.0690497 seconds
28831.299: [GC [PSYoungGen: 595248K->21763K(635840K)] 1167107K->606190K(1938368K), 0.4373016 secs]
Total time for which application threads were stopped: 0.4398899 seconds
Verbose GC. Looks good, although I hope you don't get too many of them taking .4 seconds. If so I'd be looking into my GC settings.
Apr 25, 2009 3:00:35 PM nl.gx.webmanager.handler.forms.foundation.FormHandler doPost
WARNING: Unable to retrieve flow id from the request
Apr 25, 2009 3:00:35 PM nl.gx.webmanager.handler.forms.foundation.FormHandler doPost
WARNING: Unable to retrieve flow id from the request
Apr 25, 2009 3:00:35 PM nl.gx.webmanager.handler.forms.foundation.FormHandler doPost
WARNING: Unable to retrieve flow id from the request
These are 3 separate illegal posts to the formhandler. When the handler is unable to retrieve a valid flow id it will return directly.
So.. we are looking at 1 valid post that is returned normally, a GC that take a while and 3 invalid but separate posts that are returned invalid. If your client is non responsive during this time it looks like it is doing additional invalid requests that block it? I suggest analyzing what actually goes over the wire using a httpproxy or firebug. You can then combine this information with browser behavior and determine where the problem is.
regards,
Bram