[JBoss JIRA] Created: (GTNPORTAL-996) GateIn+JOSSO integration: Problems with logout
by Marek Posolda (JIRA)
GateIn+JOSSO integration: Problems with logout
----------------------------------------------
Key: GTNPORTAL-996
URL: https://jira.jboss.org/jira/browse/GTNPORTAL-996
Project: GateIn Portal
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 3.0.0-GA
Environment: GateIn-3.0.0-GA+JBoss 5.1 bundle (port 8080 for HTTP),
JOSSO-1.8.1+Tomcat 6.0.18 bundle (port 8888 for HTTP),
Reporter: Marek Posolda
After integrating GateIn portal with JOSSO, I did these steps:
- Click to "Sign in" in GateIn
- Login as root in JOSSO console
- Logout in GateIn
- Click to "Sign in" link again. Now I am directly authenticated to GateIn which is not correct to me because now I am not able to login as different user in this web session.
Problem is that JOSSO cookie is not cleared from browser when doing logout from GateIn. I am able to login as different user after clearing the cookie directly from web browser via browser cookie manager.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 11 months
[JBoss JIRA] Created: (GTNPORTAL-855) javax.transaction.RollbackException when creating navigation node in GateIn
by Marek Posolda (JIRA)
javax.transaction.RollbackException when creating navigation node in GateIn
---------------------------------------------------------------------------
Key: GTNPORTAL-855
URL: https://jira.jboss.org/jira/browse/GTNPORTAL-855
Project: GateIn Portal
Issue Type: Bug
Security Level: Public (Everyone can see)
Environment: GateIn trunk (revision 2083) deployed on EAP5,
Sun JDK 1.6,
MySQL 5.1 shared database (between two GateIn nodes)
Reporter: Marek Posolda
Fix For: 3.1.0
I have a problem when having two GateIn instances on different servers running in cluster. Steps to simulate:
1) Run node1 with -Dexo.profiles=cluster
2) Run node2 with -Dexo.profiles=cluster
3) Login as root in node1 and go to portalnavigation -> Edit navigations -> Add node -> Use existing page in page selector (portal::classic::homepage) -> Fill node name and title -> click to Save
4) Now I am able to see my new node. But I can see exceptions in server logs in both node1 and node2.
Exception on node2 is "[TxInterceptor] prepare failed! java.lang.NullPointerException".
Exception on node1 is "[TxIsolatedOperation] Transaction has been rolled back javax.transaction.RollbackException: [com.arjuna.ats.internal.jta.transaction.arjunacore.commitwhenaborted] [com.arjuna.ats.internal.jta.transaction.arjunacore.commitwhenaborted] Could not commit transaction."
Full stacktraces of both exceptions are attached. Interesting is that I am also able to see the page on second node. So it seems that nothing happens in application itself, only exceptions in server logs are strange. Exception on node2 (NullPointerException) occurs first and exception "RollbackExcption" on node1, where new navigations were created, occurs after it. And I can see only when having cluster with more nodes. It doesn't occur in single node.
For completeness: I am using shared database MySQL with JBoss datasources in server/production/deploy directory and "no-tx-datasource" datasource. Both nodes are executed with "-Dexo.profiles=cluster". I am attaching my server/production/conf/gatein/configuration.xml.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 11 months