[JBoss JIRA] Created: (JBPORTAL-2464) Creating a users dashboard results in a high number of sql selects
by Martin Putz (JIRA)
Creating a users dashboard results in a high number of sql selects
------------------------------------------------------------------
Key: JBPORTAL-2464
URL: https://jira.jboss.org/jira/browse/JBPORTAL-2464
Project: JBoss Portal
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Portal Core
Affects Versions: 2.7.2 Final
Reporter: Martin Putz
Assignee: Thomas Heute
Fix For: 2.7.3 Final
Creating a users dashboard results in a high number of the following sql selects issued against the database:
select portalobje0_.PK as PK64_0_, portalobje0_.LISTENER as LISTENER64_0_, portalobje0_4_.INSTANCE_REF as INSTANCE2_72_0_, case when portalobje0_1_.PK is not null then 1 when portalobje0_2_.PK is not null then 2 when portalobje0_3_.PK is not null then 3 when portalobje0_4_.PK is not null then 4 when portalobje0_.PK is not null then 0 end as clazz_0_, declaredpr1_.OBJECT_KEY as OBJECT1_2_, declaredpr1_.jbp_VALUE as jbp2_2_, declaredpr1_.NAME as NAME2_, modes2_.PK as PK3_, modes2_.name as name3_, windowstat3_.PK as PK4_, windowstat3_.name as name4_ from JBP_PORTAL_OBJECT portalobje0_ left outer join JBP_CONTEXT portalobje0_1_ on portalobje0_.PK=portalobje0_1_.PK left outer join JBP_PORTAL portalobje0_2_ on portalobje0_.PK=portalobje0_2_.PK left outer join JBP_PAGE portalobje0_3_ on portalobje0_.PK=portalobje0_3_.PK left outer join JBP_WINDOW portalobje0_4_ on portalobje0_.PK=portalobje0_4_.PK left outer join JBP_PORTAL_OBJECT_PROPS declaredpr1_ on portalobje0_.PK=declaredpr1_.OBJECT_KEY left outer join JBP_PORTAL_MODE modes2_ on portalobje0_.PK=modes2_.PK left outer join JBP_PORTAL_WINDOW_STATE windowstat3_ on portalobje0_.PK=windowstat3_.PK where portalobje0_.PK=?
This results in bad performance when testing with a high number of portal objects.
--
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, 10 months
[JBoss JIRA] Updated: (JBAS-2681) Add real support for password-stacking (useFirstPass) in LDAPExtLoginModule
by Andrew Oliver (JIRA)
[ https://jira.jboss.org/jira/browse/JBAS-2681?page=com.atlassian.jira.plug... ]
Andrew Oliver updated JBAS-2681:
--------------------------------
Attachment: LdapExtLoginModule.class
(jdk 6 version of a compiled LdapExtLoginModule to help the lazy, update this in your $JBOSS_HOME/server/xxx/lib/jbosssx.jar by creating a path structure: org/jboss/security/auth/spi/LdapExtLoginModule.class and doing jar -uf $JBOSS_HOME/server/xxx/lib/jbosssx.jar org/jboss/security/auth/spi/LdapExtLoginModule.class from the parent of the path structure)
> Add real support for password-stacking (useFirstPass) in LDAPExtLoginModule
> ---------------------------------------------------------------------------
>
> Key: JBAS-2681
> URL: https://jira.jboss.org/jira/browse/JBAS-2681
> Project: JBoss Application Server
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Security
> Affects Versions: JBossAS-4.0.3 SP1
> Environment: All
> Reporter: Didier Kreutter
> Assignee: Andrew Oliver
> Attachments: LDAPAuth.patch, LdapExtLoginModule.class, ldapextpatch
>
>
> It would be nice, we could use the "useFirstPass" option of this login-module, like it can be done with the DatabaseServerLoginModule.
> With the construct of the LDAPExtLoginModule, it is not possible to use the LDAP-Directory to search for Roles without having to validate the Password, if this has been done by an precedent LoginModule (DB or SSO).
> I think the problem is in the fact, that the effective Role-Search is done in the overridden "validatePassword" function... witch will never been called when the "useFirstPass" option is set. Is it Possible to fulfill the roles in the getRoleSets() function?
--
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, 10 months
[JBoss JIRA] Created: (JBID-228) FileBasedMetadataConfigurationStore.loadTrustedProviders keeps trustedFile locked for some indeterminate period
by Jaap Reitsma (JIRA)
FileBasedMetadataConfigurationStore.loadTrustedProviders keeps trustedFile locked for some indeterminate period
---------------------------------------------------------------------------------------------------------------
Key: JBID-228
URL: https://jira.jboss.org/jira/browse/JBID-228
Project: JBoss Identity
Issue Type: Bug
Components: Identity-Federation
Environment: Windows XP SP3, JBoss 5.1.0.GA
Reporter: Jaap Reitsma
Assignee: Anil Saldhana
In package org.jboss.identity.federation.core.saml.v2.metadata.store, class FileBasedMetadataConfigurationStore, the method.loadTrustedProviders() locks the trustedFile for a (short) indeterminate period, due to a missing ois.close() at the end of the method. In the unit test a failure will occur in
FileBasedMetadataConfigurationStoreUnitTestCase.testTrustedProviders() due to a sharing violation (Windows) error, because it cannot delete a file which is held open, at least not in Windows.
Solution: Close the stream explicitly instead of waiting for the garbage collector.
--
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, 10 months
[JBoss JIRA] Created: (JBAS-6492) Include basic smoke tests of JTS into AS testsuite
by Ivo Studensky (JIRA)
Include basic smoke tests of JTS into AS testsuite
--------------------------------------------------
Key: JBAS-6492
URL: https://jira.jboss.org/jira/browse/JBAS-6492
Project: JBoss Application Server
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Test Suite
Reporter: Ivo Studensky
Assignee: Ivo Studensky
Fix For: JBossAS-5.1.0.Beta1
Citation of jhalliday's demand:
... to modify the default AS test run so that it installs
the JTS to a new sever config and runs the equivalent of
./build.sh -Dtest=jca test
./build.sh -Dtest=tm test
possibly without some of the stress tests which are known to
be broken. This won't add too much time to the default AS
test run i.e.
./build.sh tests
but will provide some basic smoke test cover for the JTS.
--
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, 10 months