1 2 Previous Next 26 Replies Latest reply on Feb 12, 2009 9:39 AM by mazz Go to original post
      • 15. Re: error in jopr console

        oh... did not go through that doc ( i guess i was a bit excited doing it all for the first time :) )... yes i am on windows ( xp sp2 )... by the length of 19 chars you mean the path before the server directory or is the server directory name also included in it ?

        • 16. Re: error in jopr console
          mazz

          I wouldn't take that 19 limit literally - I'm pretty sure that the limit is different depending on certain configurations in your Windows environment (I have no idea what those factors are, but I'm pretty sure I've installed in my file system with my base dir longer than 19 and I know people have installed in directories shorter than 19 and saw problems.

          I guess the point is, if you ever have odd errors like the ones you got, try to shorten the install directory and see if it fixes it. To eliminate this as the possible cause, its best to just install in a short directory like "C:\jopr" and see what happens. From there, you can figure out what your limit is by increasing the length of your directory names.

          > you mean the path before the server directory

          we mean the directory where you unzipped the distro. "C:\jopr" for example.

          • 17. Re: error in jopr console

            now i have another question... i am able to see a platform and servers running on it in the jopr dashboard... besides the jboss server i am able to see the quick links for "monitoring M", "inventory I" , "operations O", "alerts A" and "Packages P" but i am not able to see the link for "configure C" which is required for doing administrative work on the server like starting stopping, crating datasource etc etc... what else do i need to do get that link...

            • 18. Re: error in jopr console
              mazz

              "C" is for configuration - this is to set configuration settings for a particular resource (i.e. settings in .properties files, or xml files or settings in some database - it depends on the specific resource being configured, but in general, "C" is to set configuration settings for a resource)

              Admin work like "starting" and "stopping" are not configuration - they are "operations".

              Creating a datasource involves adding new resources to your inventory - hence, you would do this in your "Inventory" tab (this is not configuration per-se).

              Now, to set the JDBC URL for a datasource, THAT is configuration - so that would be done in the "C"onfiguration tab for the data source that you want to re-configure.

              Do you see the distinction? We've provided very specific subsystems for the things you want to do. This allows for different resources to support some subsystems, but not all (for example, some resources might have configuration settings you can see and modify, so it would have "C"onfiguration, but they might not have any "O"perations that can be invoked, so you won't see the "O"peration tab. When you write your own plugins, you have the option to support some of these subsystems - you do not have to support all of them).

              I recommend you read some of the docs on this - it would make it clearer:

              http://www.redhat.com/docs/en-US/JBoss_ON//html/Feature_Guide/chap-Feature_Guide-Overview.html

              • 19. Re: error in jopr console

                I have the jopr server installed on my machine... and i have started a jopr agent on another machine... however my server dashboard is not auto discovering the machine on which the agent has been started... what could be the reason ?

                • 20. Re: error in jopr console

                  the earlier problem was solved... but i have a new query now... when the jopr agent is being configured , one has to give the jopr server bind address ( the default )... if i bind thew agent to a particular server will be able to view the platform details of that agent on any other server (i.e. a server other than the one to which it was bound ) ?
                  what exactly is achieved by binding the agent to a particular server ? shouldn't the scenario be something like any server being able to auto detect an agent instead of binding the latter to a particular one ?

                  • 21. Re: error in jopr console
                    ips

                    This could be a number of things. The easiest way to figure it out is to inspect both the Server and Agent logfiles just after the Agent tries to connect to the Server. Try the following:

                    1) Stop the Agent.
                    2) Restart the Agent with -lu and answer the setup prompts.
                    3) At this point the Agent will try to connect to the Server, register, and then send its first autodiscovery report. Check the Server and Agent logfiles for any errors or warnings.

                    -Ian

                    • 22. Re: error in jopr console
                      mazz

                       

                      "jbosstcs" wrote:
                      the earlier problem was solved... but i have a new query now... when the jopr agent is being configured , one has to give the jopr server bind address ( the default )... if i bind thew agent to a particular server will be able to view the platform details of that agent on any other server (i.e. a server other than the one to which it was bound ) ?
                      what exactly is achieved by binding the agent to a particular server ? shouldn't the scenario be something like any server being able to auto detect an agent instead of binding the latter to a particular one ?


                      OK, this can get complicated, so hopefully I'll explain it properly here.

                      First, when the agent is first installed, it knows nothing about the server cloud it should be talking to. Yes there is an "auto-discovery via multicast" feature inside the agent to help it find servers, but we cannot require the agent to have to run in a network that allows multicast traffic (many network admins disable multicast traffic). So, we need to come up with a way that will work anywhere in any network. (the agent's multicast auto-detection feature is only used to detect when a known Jopr server has gone up or down - it is not used to detect unknown Jopr servers). For the same reason, the server cannot rely on multicast traffic to detect new agents (because, again, many (most?) network admins disable multicast traffic and thus this won't work for them).

                      So, when you first start the agent it needs to know its "registration server". This is the first server the agent will ever talk to. So, if you run "rhq-agent.sh", it'll ask you the setup questions, one of which is the server's endpoint. THIS is the "registration" server the agent will talk to. The agent connects to the registration server, and registers on the Jopr server cloud.

                      At this point, the agent has joined the Jopr environment - it is registered and all Jopr servers in the cloud know about this agent. So, even though the agent talked to this one server, the agent isn't "owned" by that server - ALL servers now know about this agent and will be able to talk to that agent. What happens as part of the registration handshake is the "registration" server will send down to the agent a "failover list". This failover list contains a list of all the servers in the cloud (the public endpoint addresses and ports that all the servers are listening to). You can see this failover list by using the agent's "failover" prompt command (type "help failover" for information about this prompt command). This failover list is customized per agent (so the agents are spread out over all the servers in the cloud, spreading out the load). Once the agent gets this failover list, it will immediately switch over to its "primary" server (i.e. the server at the top of this failover list). This primary server can be different than the registration server you gave the agent at startup.

                      If the primary server goes down, or is switched to "maintenance mode", the agent will use this failover list to try to talk to another server in the cloud - moving its way down the list until it finds a server that is up and can process its request. (and yes, you can set up affinity for agents to prefer to talk to one server over another - affinity groups is discussed in the docs - it helps determine the order of the failover list).

                      Note that the IP addresses in your failover list are the "public endpoints" as configured for all your servers. If you start your agent and you get odd connection errors after registering, go to the Administration page in the UI and click the "Manage Servers" link and look at all the endpoints for all your servers - these are the public endpoints and MUST be routable by ALL agents. You can edit the endpoints from this UI screen if you need to change them.

                      • 23. Re: error in jopr console
                        mazz

                        BTW: these are all excellent questions - plus post further questions like this as separate threads so we can put them under appropriate subjects and have the information separate. This thread is monolithic :)

                        • 24. Re: error in jopr console
                          mazz

                          "plus post" == "PLEASE post"

                          • 25. Re: error in jopr console

                            wow !!!... must say that was an awesome explanation... i have a doubt... how is that "cloud" that you were referring to configured ?... where can i see it ?

                            • 26. Re: error in jopr console
                              mazz

                              (moving this discussion to a separate thread: http://www.jboss.org/index.html?module=bb&op=viewtopic&t=150411 )

                              1 2 Previous Next