[
https://issues.apache.org/jira/browse/JS2-1119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ate Douma updated JS2-1119:
---------------------------
Affects Version/s: 2.1.3
Fix Version/s: 2.1.4
After extensive debugging I found the real cause why login didn't work any
more: the change of sessionId by this new Tomcat feature also initiates a new
"sessionCreated" event...
As result, our PortalsSessionManager adds a new PortalSessionMonitor in the
session *on the same key*, which causes the *old* PortalSessionMonitor to be
removed, which then (as result of the removal) invalidates the session itself...
Some nice kind of cascading side-effect ...
I wonder which other applications will break because of this nice "added"
feature, especially the additional sessionCreated event on an already existing
session might throw some havoc ...
Anyway, I've come up with a slight modification to the PortalsSessionManager
handling of this which caters for this now.
It does require adding an additional method to the
PortletApplicationSessionMonitor (API) as now we'll have to synchronise the new
sessionId across.
Furthermore, I'll have to back port this to 2.1.4 as well (NB: including
Jetspeed API change...)
> Impossible to log in using Jetspeed 2 and Tomcat 6.0.24
> -------------------------------------------------------
>
> Key: JS2-1119
> URL: https://issues.apache.org/jira/browse/JS2-1119
> Project: Jetspeed 2
> Issue Type: Bug
> Components: Components Core
> Affects Versions: 2.1.3, 2.2.1
> Environment: Linux Ubuntu Lucid Lynx - Tomcat 6.0.24-2 - Java 1.5 and
> 1.6
> Reporter: Gonzalo Aguilar
> Assignee: Ate Douma
> Fix For: 2.1.4, 2.2.1
>
>
> Jetspeed Will not let you log in when deployed in Tomcat 6.0.24-2.
> After inserting user and password portal will reload as usual but will not
> update it's contents to reflect login success.
> No errors are shown in logs and no clue about what's going wrong as password
> are accept and normal login seems to perform normally. I traced the module to
> DefaultLoginModule.login() and it works well and return success when correct
> user and login are used. But portal doesn't seem to reflect the login. The
> problem must be other place but was not able to track it down.
> Steps to reproduce:
> 1.- Install Tomcat 6.0.22
> 2.- Deploy jetspeed 2 2.2.1 with libs in place.
> 3.- Log in as usual.
> It will not work.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscr...@portals.apache.org
For additional commands, e-mail: jetspeed-dev-h...@portals.apache.org
