1 2 3 Previous Next 61 Replies Latest reply: Feb 21, 2008 8:42 AM by Andy Taylor RSS

JBM 2 Management Interfaces

Andy Taylor Master

Ive checked into trunk the first pass at the new management interfaces, JMSServerManager and MessagingServerManagement. Its still a work in progress but if theres anything you think needs changing/adding then shout.

  • 1. Re: JBM 2 Management Interfaces
    Tim Fox Master

    A few initial comments:

    I would not provide overloaded methods which take a JBossDestination as well as others which take a destination name. A destination name should be sufficient.

    Other functionality we should have:

    1) Delete a single message from a queue
    2) Move a single message from one queue to another (e.g. to DLQ or expiry queue).
    3) Expire a message
    4) Change message priority

  • 2. Re: JBM 2 Management Interfaces
    Tim Fox Master

    Anything else anyone can think of?

  • 3. Re: JBM 2 Management Interfaces
    Tim Fox Master

    More ideas:

    1. Change a header on a message
    2. Drop a user connection
    3. Drop a single subscription.

  • 4. Re: JBM 2 Management Interfaces
    Tim Fox Master

    1. List connections for a user
    2. View statistics for a user (number of messages sent, number of messages consumed etc)

  • 5. Re: JBM 2 Management Interfaces
    Tim Fox Master

    Block a user, freeze a user out.

    The list goes on....

    We don't necessarily need to implement everything, but we should certainly think about it.

  • 6. Re: JBM 2 Management Interfaces
    Tim Fox Master

    List temporary destinations

    List sessions

  • 7. Re: JBM 2 Management Interfaces
    Clebert Suconic Master

    set BrainStorm On

    What about something to list internal routes?

    Maybe listRoutes (DestinationName), and listRoutes() calling it for everything.

    set BrainStorm Off ( :-) )

  • 8. Re: JBM 2 Management Interfaces
    Tim Fox Master

     

    "clebert.suconic@jboss.com" wrote:


    What about something to list internal routes?

    Maybe listRoutes (DestinationName), and listRoutes() calling it for everything.


    Yes, on the core interface we should have something like:

    listAvailableAddresses (these are the "routes").

    on the jms interface we should have

    listAllQueues
    listAllTopics



  • 9. Re: JBM 2 Management Interfaces
    Andy Taylor Master

     

    1) Delete a single message from a queue
    2) Move a single message from one queue to another (e.g. to DLQ or expiry queue).
    3) Expire a message
    4) Change message priority


    sounds good, via message id i guess.

    1. Change a header on a message
    2. Drop a user connection
    3. Drop a single subscription.


    All good, especially the second one.Would this force the client to reconnect in a clustered environment?

    1. List connections for a user
    2. View statistics for a user (number of messages sent, number of messages consumed etc)


    first one trivial, I'll have to investigate the second!


    Block a user, freeze a user out.


    Again, i'll investigate!

    List temporary destinations

    List sessions


    trivial, I'll add.

    listAvailableAddresses (these are the "routes").

    on the jms interface we should have

    listAllQueues
    listAllTopics


    again, trivial, so i'll add.

  • 10. Re: JBM 2 Management Interfaces
    Tim Fox Master

    A few more ideas:

    Ability to stop and start server (probably have this already)

    Ability to "lock" server. I.e. don't accept any new connections, but keep the old ones.

    Drop all connections.

    JMS:

    Search for all queues, topics with names using a search string.

    Core:

    Search for all queues given a search string.

    Search for all address given a search string.

  • 11. Re: JBM 2 Management Interfaces
    Tim Fox Master

    How about: have an ability to

    a) Send a test message to a destination from the management console (just specify the destination and hit a button).

    b) Consume a message from a destination from the management console (just specify the destination).

    This would be useful in validating the system after installation - e.g. checking clustered queues are working correctly without having to write a client program or run one of the examples.




  • 12. Re: JBM 2 Management Interfaces
    Aaron Walker Newbie

    I like the idea of sending management messages. Such as a message to create a new destination, locking and unlocking the server, shutdown the server, etc

  • 13. Re: JBM 2 Management Interfaces
    mazz Master

    I heard "management" and my ears perked up.

    Take a look at our new OSS project we just released that may have some bearing on this (side note: the comm layer between RHQ's server and agent has JBoss/Remoting 2 under the covers):

    http://rhq-project.org

    We can incorporate your management APIs into some "remoting plugin" to expose your management capabilities into a full managment UI.

  • 14. Re: JBM 2 Management Interfaces
    Tim Fox Master

    Is that the one derived from JBoss ON, that Charles spoke about at the developer conference?

    If so, that looks very cool, and we are definitely thinking of using it for our web based management view. :)

    One other thing we would like is a non web (Swing?) UI, although I'm not sure what is available in that area at the moment or whether we'd have to write it ourselves.

1 2 3 Previous Next