4 Replies Latest reply on May 23, 2010 10:00 AM by cany cany

    Jopr moniter Multi JBossAs

    cany cany Newbie

      I have install the jopr (version =2.3.1) and  I also install embedded angent  function,
      Because my client already has the other JBossAs

      When I login in the jopr website, I can find the the two jbossas ,but I don't know why the other jbossas always can't moniter the status ,
      Then log dispaly error message "Could not establish connection to the JBoss AS instance [41] times for resource [D:\jboss-4.2.3.GA\server\default]"


      I am sure the jboss is run , but the jopr can't moniter this, I try several times


      please help !!!

        • 1. Re: Jopr moniter Multi JBossAs
          mazz Master

          > I also install embedded angent  function


          Regarding the embedded agent, read the big red box here:




          As for the JbossAS connectivity issues, its possible the remote jnp connections are secured and you don't have the proper credentials (or you didn't give the proper credentials in the UI).


          Other than that, read the agent logs to see if you have more specific details on the error. Set the env var  RHQ_AGENT_DEBUG=true and then restart the agent to turn on debug mode to get debug messages, which may also help track down the problem

          • 2. Re: Jopr moniter Multi JBossAs
            cany cany Newbie

            I see my properties, I configure the same as the document


            # Embedded RHQ Agent


            when I link the jboss , the embedded-agent.log has these error ,I am sure my boss has been started ,I don't know why Jopr can't connect this.


            23:10:39,031 WARN  [ResourceContainer.invoker.daemon-2] (org.rhq.plugins.jbossas.JBossASServerComponent)- Could not establish connection to the JBoss AS instance [1] times for resource [D:\jboss-4.2.3.GA\server\default]
            java.lang.ClassCastException: javax.management.ObjectName
            at org.mc4j.ems.impl.jmx.connection.DConnection.loadSynchronous(DConnection.java:147)
            at org.rhq.plugins.jbossas.JBossASServerComponent.loadConnection(JBossASServerComponent.java:1030)
            at org.rhq.plugins.jbossas.JBossASServerComponent.start(JBossASServerComponent.java:237)
            at sun.reflect.GeneratedMethodAccessor313.invoke(Unknown Source)
            at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
            at java.lang.reflect.Method.invoke(Unknown Source)
            at org.rhq.core.pc.inventory.ResourceContainer$ComponentInvocationThread.call(ResourceContainer.java:525)
            at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
            at java.util.concurrent.FutureTask.run(Unknown Source)
            at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
            at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
            at java.lang.Thread.run(Unknown Source)


            If  has any suggestion about this , please tell me .thanks

            • 3. Re: Jopr moniter Multi JBossAs
              mazz Master

              In my last reply, when I said, "Regarding the embedded agent, read the big red box here:", I was referring to this text found in the red box:


              "Use the embedded agent for demo/testing purposes only. It is not recommended to use it in a production environment.

              There are some known issues with managing certain resources with the embedded agent (for example, one specific issue deals with the inability to monitor some of the internal RHQ Server EJBs)."


              Read that specific issue here:




              So there are issues that occur when using the embedded agent.


              In other words, don't use the embedded agent when you hit JMX errors like your exception: "java.lang.ClassCastException: javax.management.ObjectName" - that is another manifestation of the error that caused the error in the bugzilla above.

              • 4. Re: Jopr moniter Multi JBossAs
                cany cany Newbie

                Thank for your answer, I will try other jbossap to moniter .