[JBoss JIRA] (GTNPORTAL-3108) LastLoginTime should be configurable
by Boleslaw Dawidowicz (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-3108?page=com.atlassian.jira.pl... ]
Boleslaw Dawidowicz updated GTNPORTAL-3108:
-------------------------------------------
Status: Resolved (was: Pull Request Sent)
Fix Version/s: 3.6.0.Final
(was: 3.7.0.Final)
Resolution: Done
> LastLoginTime should be configurable
> ------------------------------------
>
> Key: GTNPORTAL-3108
> URL: https://issues.jboss.org/browse/GTNPORTAL-3108
> Project: GateIn Portal
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Identity integration
> Affects Versions: 3.6.0.Beta02
> Reporter: Marek Posolda
> Assignee: Marek Posolda
> Fix For: 3.6.0.Final
>
>
> Description of problem:
> It would be good to have ability to configure (disable/enable) the LastLoginTime writing on database when a user logs in the portal.
> Currently lastLoginTime is always updated and this can make a problem when running a test with the big number of simultaneous users that are using the same username/password.
> The lastLoginTime is updated in authenticate() method of the UserDAOImpl [1].
> [1] http://anonsvn.jboss.org/repos/gatein/epp/portal/tags/EPP_5_1_1_GA/compon...
> Version-Release number of selected component (if applicable):
> EPP 5.2
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 7 months
[JBoss JIRA] (GTNPORTAL-3110) IDM DAO classes are only catching IdentityExceptions
by Boleslaw Dawidowicz (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-3110?page=com.atlassian.jira.pl... ]
Boleslaw Dawidowicz updated GTNPORTAL-3110:
-------------------------------------------
Status: Resolved (was: Pull Request Sent)
Fix Version/s: 3.6.0.Final
Resolution: Done
> IDM DAO classes are only catching IdentityExceptions
> ----------------------------------------------------
>
> Key: GTNPORTAL-3110
> URL: https://issues.jboss.org/browse/GTNPORTAL-3110
> Project: GateIn Portal
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Identity integration
> Affects Versions: 3.6.0.Beta02
> Reporter: Martin Weiler
> Assignee: Marek Posolda
> Fix For: 3.6.0.Final
>
>
> In some IDM DAO classes, such as GroupDAOImpl, MembershipDAOImpl and UserProfileDAOImpl all IDM calls are wrapped with try..catch(Exception e) blocks, which ensures that not only IdentityException, but also Hibernate exceptions are caught and recovered with rollback().
> But in UserDAOImpl only "IdentityException e" instances are caught. So HibernateException are not handled, which can result in transaction errors. Additionally, in MembershipTypeDAOImpl the IDM calls are not wrapped with any catch blocks, which also needs to be fixed.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 7 months
[JBoss JIRA] (GTNPORTAL-2917) NPEs thrown while accessing /portal context when JPP is being started
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-2917?page=com.atlassian.jira.pl... ]
RH Bugzilla Integration commented on GTNPORTAL-2917:
----------------------------------------------------
Boleslaw Dawidowicz <bdawidow(a)redhat.com> changed the Status of [bug 948301|https://bugzilla.redhat.com/show_bug.cgi?id=948301] from NEW to MODIFIED
> NPEs thrown while accessing /portal context when JPP is being started
> ---------------------------------------------------------------------
>
> Key: GTNPORTAL-2917
> URL: https://issues.jboss.org/browse/GTNPORTAL-2917
> Project: GateIn Portal
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 3.5.0.Final, 3.6.0.Beta01
> Reporter: Dominik Pospisil
> Assignee: Lucas Ponce
> Labels: JPP61-Test-dev
> Fix For: 3.6.0.Final
>
> Attachments: jsf2-rf4-test.zip, jsf2-rf4-test.zip
>
>
> JPP throws NPE if a client tries to access /portal context during server startup. The NPEs occur after the server logs "Registering web context: /portal" until the portal EAR is competely deployed.
> Steps to Reproduce:
> 1. start the server
> 2. access /portal context while the server is being started
>
> Exceptions thrown:
> 15:08:25,855 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/portal].[portal]] (http-/127.0.0.1:8080-1) Servlet.service() for servlet portal threw exception: java.lang.NullPointerException
> at org.exoplatform.frameworks.jcr.web.ThreadLocalSessionProviderInitializedFilter.doFilter(ThreadLocalSessionProviderInitializedFilter.java:138) [exo.jcr.framework.web-1.15.1-CP01-redhat-1.jar:1.15.1-CP01-redhat-1]
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.17.Final-redhat-1-JBPAPP6-1709.jar:]
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.17.Final-redhat-1-JBPAPP6-1709.jar:]
> at org.exoplatform.web.login.ConversationStateUpdateFilter.doFilter(ConversationStateUpdateFilter.java:66) [exo.portal.component.web.security-3.5.2.Final-redhat-4.jar:3.5.2.Final-redhat-4]
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.17.Final-redhat-1-JBPAPP6-1709.jar:]
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.17.Final-redhat-1-JBPAPP6-1709.jar:]
>
> 15:08:37,235 WARN [org.exoplatform.web.CacheUserProfileFilter] (http-/127.0.0.1:8080-1) An error occured while cache user profile: javax.servlet.ServletException: java.lang.NullPointerException
> at org.exoplatform.portal.application.PortalController.onService(PortalController.java:110) [exo.portal.webui.portal-3.5.2.Final-redhat-4.jar:3.5.2.Final-redhat-4]
> at org.exoplatform.container.web.AbstractHttpServlet.service(AbstractHttpServlet.java:132) [exo.kernel.container-2.4.1-GA-redhat-1.jar:2.4.1-GA-redhat-1]
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:847) [jboss-servlet-api_3.0_spec-1.0.1.Final-redhat-2.jar:1.0.1.Final-redhat-2]
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329) [jbossweb-7.0.17.Final-redhat-1-JBPAPP6-1709.jar:]
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.17.Final-redhat-1-JBPAPP6-1709.jar:]
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 7 months