CraigM_17826
Jul 13, 2010Altostratus
Odd behaviour when pooling to a Tomcat server
Hi all,
we are experiencing an odd issue when traffic which contains specific text is directed to a Tomcat server pool. The URI detection works fine and the tomcat app itself is shown in a iFrame in the browser. The issue we have is that when the Tomcat application redirects back to the main web address it seems that Tomcat intercepts the request and tries to process it and then generates a 404 error. If we wait 10-15 seconds and do a page refresh the page loads from WebSphere. This does work on our current website and the Tomcat app is the same. The only difference I found was that the VIP for the new website being developed did not have a oneconnect profile defined whereas the working site did so I enabled this option. The redirect back from Tomcat now works as it does in our current production system but our developers are now saying other parts of the site are breaking with pages not loading completely so I have had to disable the oneconnect profile. This of course has brought back the Tomcat redirection issue again.
All I can tell you about the tomcat app is what one of our developers told me and thast is when the user clicks on a button to exit the tomcat app, some jsp code to clear the Tomcat session is run and then does an explicit 302 redirect back to a static page on our website.
So, can anyone tell me why oneconnect would have this effect on a redirect from a Tomcat server and if there are any possible ways to achieve the samew thing without using oneconnect profile?
tia
Craig