Our Seam application is integrated with Tivoli Access Manager for authorisation. TAM performs authorisation then redirects to our application. The redirect request includes the jsessionid in the URL (ie .../login/;jessionid=23432413434...) and also in a cookie.
We've noticed an error in the last few days where this is resulting in a 404. Previously it was always working. Manually removing the ;jessionid and the problem goes away.
We have just recently updated to Seam 2.2.2Final.
Is there any change in Seam 2.2.2 that might have caused this? Anybody else seen this occur?