I'm new to RHQ so please be gentle…
I setup RHQ 4.2 to auth against AD. Logged in as me, got prompt to enter new info and did. Now on subsequent login attempts, I can enter ANY password and get access. This has to be broken, correct? Log snip below. Clearly something is broken in my config but I'd think that any LDAP failure should prevent an access, no?
As well, if I enter ANY username (nonexistent user) it prompts me to create an account. Is this expected behavior?
----------------------- 2012-02-28 14:22:09,351 WARN [gwt-log] Sending exception to client: [1330456929349] javax.ejb.EJBException: java.lang.RuntimeException: javax.naming.AuthenticationException: [LDAP: err or code 49 - 80090308: LdapErr: DSID-0C090334, comment: AcceptSecurityContext error, data 525, vece] at org.jboss.ejb3.tx.Ejb3TxPolicy.handleExceptionInOurTx(Ejb3TxPolicy.java:63) at org.jboss.aspects.tx.TxPolicy.invokeInOurTx(TxPolicy.java:83) at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:191) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.aspects.tx.TxPropagationInterceptor.invoke(TxPropagationInterceptor.java:95) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.stateless.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor .java:62) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
I'm seeing the 4.2 agent growing memory usage in a prefect linear pattern. Chart attached.
This eventually exhausts all swap space.
The one odd thing I've found is that I installed and managed rhq using puppet. If I remove the puppet manifest to ensure the service is running, this growth doesn't happen.
rhq-users@lists.stg.fedorahosted.org