[JBoss JIRA] Created: (JBMETA-8) Ejb[Local]RefMetaData.getJndiName() should returned resolvedJndiName
by Alexey Loubyansky (JIRA)
Ejb[Local]RefMetaData.getJndiName() should returned resolvedJndiName
--------------------------------------------------------------------
Key: JBMETA-8
URL: http://jira.jboss.com/jira/browse/JBMETA-8
Project: JBoss Metadata
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 1.0.0.Beta6
Reporter: Alexey Loubyansky
Assigned To: Alexey Loubyansky
Fix For: 1.0.0.CR1
This is a dependency of JBAS-5285 *ReferenceMetadataResolverDeployers overridding explicitly-defined jndi-name.
Currently, getJndiName() returns mappedName. Deployers resolve links and set resolvedJndiName. So, that's the one that should be returned. For backwards compatibility (is there any, btw, except for the local tests?) I am going to fall back to the mapped name if the resolved name is not available.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
18 years, 4 months
[JBoss JIRA] Created: (JBPORTAL-1954) error when creating a new user with OpenDS
by Prabhat Jha (JIRA)
error when creating a new user with OpenDS
------------------------------------------
Key: JBPORTAL-1954
URL: http://jira.jboss.com/jira/browse/JBPORTAL-1954
Project: JBoss Portal
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Portal Identity
Affects Versions: Identity-1.0
Reporter: Prabhat Jha
Assigned To: Boleslaw Dawidowicz
I am using LDAPUserModuleImpl and LDAPRoleModuleImpl so that I can create a new user and role. When creating a new user, I get
13:41:00,450 ERROR [IdentityUserManagementServiceImpl] Error when creating user
org.jboss.portal.identity.IdentityException: Failed to create user
at org.jboss.portal.identity.ldap.LDAPUserModuleImpl.createUser(LDAPUserModuleImpl.java:191)
at org.jboss.portal.core.identity.services.impl.IdentityUserManagementServiceImpl.createUser(IdentityUserManagementServiceImpl.java:187)
at org.jboss.portal.core.identity.services.workflow.impl.RegistrationServiceImpl.registerUser(RegistrationServiceImpl.java:163)
caused by
Caused by: javax.naming.directory.SchemaViolationException: [LDAP: error code 65 - Entry uid=abcd,ou=People,o=test,dc=portal,dc=example,dc=com violates the Directory Server schema configuration because it includes multiple conflicting structural objectclasses person and inetUser. Only a single structural objectclass is allowed in an entry]; remaining name 'uid=abcd'
at com.sun.jndi.ldap.LdapCtx.mapErrorCode(LdapCtx.java:3016)
at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2931)
at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2737)
at com.sun.jndi.ldap.LdapCtx.c_createSubcontext(LdapCtx.java:770)
at com.sun.jndi.toolkit.ctx.ComponentDirContext.p_createSubcontext(ComponentDirContext.java:319)
at com.sun.jndi.toolkit.ctx.PartialCompositeDirContext.createSubcontext(PartialCompositeDirContext.java:248)
at com.sun.jndi.toolkit.ctx.PartialCompositeDirContext.createSubcontext(PartialCompositeDirContext.java:236)
at org.jboss.portal.identity.ldap.LDAPUserModuleImpl.createUser(LDAPUserModuleImpl.java:187)
This is with the latest OpenDS version which is OpenDS-1.0.0-build012. Despite the error, identity management portlet confirms the user creation and there is already a JBPORTAL-1935 to fix this.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
18 years, 4 months
[JBoss JIRA] Created: (JBRULES-1507) Objenesis too heavily used
by Wojciech Kudla (JIRA)
Objenesis too heavily used
--------------------------
Key: JBRULES-1507
URL: http://jira.jboss.com/jira/browse/JBRULES-1507
Project: JBoss Drools
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 4.0.4
Reporter: Wojciech Kudla
Assigned To: Mark Proctor
We are using drools in heavily concurrent environment. We build new rulebase for every request that hits our application.
There are no new bottlenecks or thread locks after using Jan's (I work in the same team as Jan Boboli does :)) hack to the rulebase classloader, but it seems drools spends a lot of time in objenesis package classes trying to resolve proper instantiators for the very same classes with each request.
This happens because method createObjenesis in AbstractRuleBase returns new instance of ObjenesisStd. There are scenarios in which this only causes performance degradadion (this is our case), so I decided to change the method to return static ObjenesisStd instead of new instance for each rulebase. After that drools rocketed up to 5 times faster than before :)
I think it would be a great idea if you added a new option for RuleBaseConfiguration to give the user a choice of how objenesis is instantiated.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
18 years, 4 months