With the migration and rewrite of the LDAP security mapping from Jetspeed 2.1.3 to 2.2 several problems and issues were introduced.
One specific area is the authentication and context proxying which more or less got broken under certain conditions and configurations.
JS2-1030 already indicates one of these, but also the context proxying (auto-recreation of stale/broken context) no longer works properly.
As with Jetspeed 2.2 we started using Spring LDAP which provides an LDAP context pooling solution, I've decided to largely rewrite the LdapAuthenticationProvider to leverage Spring LDAP and drop the LdapContextProxy.
As result of this rewrite, AFAIK
JS2-1030 now also should be fixed as side-effect.