RHQ 1.1 has been tagged GA -- and brings High Availability

The RHQ code base has been tagged with the GA (General Availability) tag for release 1.1 and brings a lot of new features and improvements. Most notably this includes High Availability (HA) for the servers. Read more...

Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.
  1. Oct 09, 2008

    alexs says:

    Hellow all. First of all: GREAT WORK, GUYS!!!!!!!&#...

    Hellow all.

    First of all:
    GREAT WORK, GUYS!!!!!!!!!!!

    I tryed to build the new GA write now...
    Where is one build issue in safe-invoker

    Safe-invokers version does not accord to tag's version.

    TODO:

    1) /path/to/tag/rhq-1.1.0/modules/enterprise/server/safe-invoker/pom.xml

    .....
    
    <groupId>org.rhq</groupId>
    
    <artifactId>safe-invoker</artifactId>
    
    <packaging>jar</packaging>
    
    >> <version>1.0.1</version>
    
    << <version>${pom.parent.version}</version>
    
    ....
    


    2) /path/to/tag/rhq-1.1.0/modules/enterprise/server/container/src/main/scripts/rhq-container.build.xml

    .....
    
    >> <copy file="${settings.localRepository}/org/rhq/safe-invoker/1.0.1/safe-invoker-1.0.1.jar" toDir="${jboss.deploy.dir}/jbossws.sar" verbose="true" />
    
    << <copy file="${settings.localRepository}/org/rhq/safe-invoker/${rhq.version}/safe-invoker-${rhq.version}.jar" toDir="${jboss.deploy.dir}/jbossws.sar" verbose="true" />
    
    ....
    


    RHQ-973 open to paint 1.2

    Second thing.

    Embedded agent failed to connect to local http invoker.
    Where is a bug, if not architectural error...
    When an agent is named "embedded", isn't it have to talk to an already local interface?

    But, when I thinking HA fail over logic:

    The embedded agent must go to be disabled.
    So LOCAL agent will talk via loadbalancer or RHQ internal fail over mechanism.
    For example: local agent of secondary RHQ node MUST talk to primary node till primary node is up.
    In same way local agent of primary node MUST continue to talk to a secondary one when it's LOCAL RHQ server crashes.
    NOTE: an embedded agent will crash within it's own RHQ(JBOSS) instance.
    So in words of Secondary RHQ server which becomes Active:
    Primary RHQ server machine is unavailable, not a concrete JBOSS(RHQ) instance

    Third thing

    UI bugs
    a) A bug in Compatible Group "M" & "I" View:
    "New Group" button instead of "Add to favorites"

    b) Three bugs in Mixed Group "I" View

    "Add to favorites" fails with NPE at
    org.rhq.enterprise.gui.legacy.action.resource.common.QuickFavoritesAction.execute(QuickFavoritesAction.java:40)

    "Remove from Favorites" button appears when it doesn't actually where

    • the way to get NPE DOOMed...

    "New Group" button....!?!?

    c) No way to add existing groups at favorites resource editor: RHQ-972 open to paint 1.2
    d) No way to save Charts, to get them available in SavedCharts: RHQ-971 open to paint 1.2

    I found something close to a,b in bug tracking, but not exactly: RHQ-420 paints to 2.0

    Feature requests

    a) Tree view in problem resources

    +platfom
       server
          service1
          service2
          ......
    

    and the initial view

    +platfom1                  summary alerts number
    +platfom2                  summary alerts number
    +platfom3                  summary alerts number
    ......
    

    because it is difficult to have a look what exactly the problem: server, process, hole network segment... on 30 unit view.
    Only one server then is going down makes at least 150 resources unavailable.

    b) Correlation between Alert to Problem Resource with automatic alert closing when resource comes available back.

    c) Manual Alert disabling ("fixed" button per alert)