5 Replies Latest reply on Apr 27, 2010 9:16 AM by Patrick Conway

    backend not available

    Patrick Conway Newbie

      I keep getting an error when trying to login

       

      RHQ3.0.0.b04 on fedora core 8

      with postgresql 8.4

       

       

       

      when I try to login I get a message the backend is not available

       

       

      The system log error is below

       

       

      2010-04-26 16:06:55,304 WARN  [org.jboss.seam.ui.renderkit.DefaultActionRendererBase] Must set an id for the default action source
      2010-04-26 16:07:12,563 ERROR [org.rhq.enterprise.gui.authentication.AuthenticateUserAction] Could not log into the web application
      javax.ejb.EJBException: java.lang.IllegalArgumentException: Unknown entry name: JON
      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)
      at org.jboss.aspects.security.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:77)
      at org.jboss.ejb3.security.Ejb3AuthenticationInterceptor.invoke(Ejb3AuthenticationInterceptor.java:110)
      at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
      at org.jboss.ejb3.ENCPropagationInterceptor.invoke(ENCPropagationInterceptor.java:46)
      at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
      at org.jboss.ejb3.asynchronous.AsynchronousInterceptor.invoke(AsynchronousInterceptor.java:106)
      at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
      at org.jboss.ejb3.stateless.StatelessContainer.localInvoke(StatelessContainer.java:240)
      at org.jboss.ejb3.stateless.StatelessContainer.localInvoke(StatelessContainer.java:210)
      at org.jboss.ejb3.stateless.StatelessLocalProxy.invoke(StatelessLocalProxy.java:84)
      at $Proxy234.login(Unknown Source)
      at org.rhq.enterprise.gui.authentication.AuthenticateUserAction.execute(AuthenticateUserAction.java:75)
      at org.rhq.enterprise.gui.legacy.action.BaseRequestProcessor.processActionPerform(BaseRequestProcessor.java:46)
      at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:236)
      at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1196)
      at org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:432)
      at javax.servlet.http.HttpServlet.service(HttpServlet.java:710)
      at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
      at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
      at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
      at org.rhq.enterprise.gui.legacy.WebUserTrackingFilter.doFilter(WebUserTrackingFilter.java:47)
      at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
      at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
      at org.rhq.enterprise.gui.legacy.AuthenticationFilter.doFilter(AuthenticationFilter.java:89)
      at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
      at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
      at org.rhq.helpers.rtfilter.filter.RtFilter.doFilter(RtFilter.java:124)
      at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
      at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
      at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
      at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
      at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
      at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230)
      at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
      at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:182)
      at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84)
      at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
      at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
      at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157)
      at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
      at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:262)
      at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
      at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583)
      at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:446)
      at java.lang.Thread.run(Unknown Source)
      Caused by: java.lang.IllegalArgumentException: Unknown entry name: JON
      at org.mc4j.ems.impl.jmx.connection.support.providers.jaas.JBossConfiguration.getAppConfigurationEntry(JBossConfiguration.java:51)
      at javax.security.auth.login.LoginContext.init(Unknown Source)
      at javax.security.auth.login.LoginContext.<init>(Unknown Source)
      at org.rhq.enterprise.server.auth.SubjectManagerBean.login(SubjectManagerBean.java:276)
      at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
      at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
      at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
      at java.lang.reflect.Method.invoke(Unknown Source)
      at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:112)
      at org.jboss.ejb3.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:166)
      at org.rhq.enterprise.server.common.TransactionInterruptInterceptor.addCheckedActionToTransactionManager(TransactionInterruptInterceptor.java:77)
      at sun.reflect.GeneratedMethodAccessor111.invoke(Unknown Source)
      at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
      at java.lang.reflect.Method.invoke(Unknown Source)
      at org.jboss.ejb3.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:118)
      at org.rhq.enterprise.server.authz.RequiredPermissionsInterceptor.checkRequiredPermissions(RequiredPermissionsInterceptor.java:156)
      at sun.reflect.GeneratedMethodAccessor110.invoke(Unknown Source)
      at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
      at java.lang.reflect.Method.invoke(Unknown Source)
      at org.jboss.ejb3.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:118)
      at org.jboss.ejb3.interceptor.EJB3InterceptorsInterceptor.invoke(EJB3InterceptorsInterceptor.java:63)
      at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
      at org.jboss.ejb3.entity.TransactionScopedEntityManagerInterceptor.invoke(TransactionScopedEntityManagerInterceptor.java:54)
      at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
      at org.jboss.ejb3.AllowedOperationsInterceptor.invoke(AllowedOperationsInterceptor.java:47)
      at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
      at org.jboss.aspects.tx.TxPolicy.invokeInOurTx(TxPolicy.java:79)
      ... 51 more

       

       

       

      POSTGRES is still running

       

      postgres 10579  0.0  0.3 211392  6048 ?        S    15:28   0:01 /opt/PostgreSQL/8.4/bin/postgres -D /opt/PostgreSQL/8.4/data

      postgres 10580  0.0  0.0 123724  1104 ?        Ss   15:28   0:00 postgres: logger process                                   

      postgres 10582  0.0  0.5 211392 10000 ?        Ss   15:28   0:00 postgres: writer process                                   

      postgres 10583  0.0  0.0 211392  1412 ?        Ss   15:28   0:00 postgres: wal writer process                               

      postgres 10584  0.0  0.0 211664  1764 ?        Ss   15:28   0:00 postgres: autovacuum launcher process                      

      postgres 10585  0.0  0.0 123912  1512 ?        Ss   15:28   0:00 postgres: stats collector process                          

      postgres 10665  0.0  0.4 213684  9212 ?        Ss   15:29   0:00 postgres: rhqadmin rhq 127.0.0.1(56921) idle               

      postgres 10667  0.0  0.9 218496 19596 ?        Ss   15:29   0:02 postgres: rhqadmin rhq 127.0.0.1(56922) idle               

      postgres 10668  0.0  0.9 217552 18372 ?        Ss   15:29   0:01 postgres: rhqadmin rhq 127.0.0.1(56923) idle               

      postgres 10704  0.0  0.3 213684  7148 ?        Ss   15:29   0:01 postgres: rhqadmin rhq 127.0.0.1(38367) idle               

      postgres 10705  0.0  0.3 213672  7152 ?        Ss   15:29   0:01 postgres: rhqadmin rhq 127.0.0.1(38368) idle               

      postgres 10822  0.0  0.3 213296  6600 ?        Ss   15:30   0:00 postgres: postgres postgres 127.0.0.1(38389) idle          

      postgres 11651  0.0  0.3 213692  7060 ?        Ss   15:52   0:00 postgres: rhqadmin rhq 127.0.0.1(35385) idle               

      postgres 11782  0.4  1.2 218132 24792 ?        Ss   15:59   0:04 postgres: rhqadmin rhq 127.0.0.1(53421) idle               

      postgres 11810  0.0  0.2 212780  4924 ?        Ss   16:00   0:00 postgres: rhqadmin rhq 127.0.0.1(33406) idle               

      postgres 12116  0.1  0.6 214236 13628 ?        Ss   16:06   0:00 postgres: rhqadmin rhq 127.0.0.1(53246) idle

       

       

       

       

      If I restart rhq I can login again....

       

      but after a short period of time, if I log out and back in....I get the error again

        • 1. Re: backend not available
          Heiko Rupp Master

          This is very strange. Are you trying to run 2 RHQ servers against this postgres server? I could imagine that there are not enough connections configured in postgres to handle both of them.

           

          Can you look very early in the startup process if an exception has been thrown - the entry "JON" seems to refer to something else than rhq.

          • 2. Re: backend not available
            Ian Springer Master

            The JBossConfiguration class in your stack trace is from the EMS library, which should only be used on the Agent side (it's a dependency of the JMX Agent-plugin). Do you have the embedded Agent enabled in the RHQ Server by any chance?

            • 3. Re: backend not available
              Patrick Conway Newbie

              yes...I have the embedded agent installed

               

               

              ........

              also although I'm not sure if its related, I installed a standalone agent on the same machine as the server.  (Because after installing the embedded agent didn't show up). I had some problem initially where no agents appeared. I restarted the server and the both the embedded and standalone were in auto discovery. I imported both.  Uninventoried the standalone and deleted it from the file system

               

              ........

               

               

              I will try reinstalling the server without the embedded agent

              • 4. Re: backend not available
                Ian Springer Master

                Ok, that's most likely causing the issue - switching to a standalone Agent should clear up your troubles.

                 

                The embedded Agent is an experimental feature that has several known issues. The main intention of the embedded Agent was to facilitate quick demos, but I don't think it's even stable enough for that. It has several known issues (try searching for "embedded agent" in RHQ Bugzilla). The specific issue that you've encountered appears to be that Agent plugin classes are leaking into the Server EAR's classloader.

                • 5. Re: backend not available
                  Patrick Conway Newbie

                  issue resolved thanks