Uploaded image for project: 'Blacktie'
  1. Blacktie
  2. BLACKTIE-186

Extend stompconnectservice to allow further administration functions


    • Type: Feature Request
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: 2.0 MR1
    • Component/s: None
    • Labels:


      We need the following functions:
      1. To determine the state of the domains servers (e.g. started/stopped for each service on each server)
      2. To stop the domain (i.e. all services on all servers)

      To achieve this it is suggested to deploy an administration (XATMI) service at all services name <SERVER_NAME>-Administration which can respond to calls from the stompconnectservice to determine the state of the domain. The only problem with this is that if there is more than one instance of the same server, you will only get one response per tpcall per server group - perhaps we could use a topic but then the client would need to know how many responses it was expecting....

      If we run two servers on different machines, the latter will failed with
      > following:
      > 2009-07-01 17:41:16,408 [0xb7fc0770] ERROR AtmiBrokerServer -
      > serverinit - Unexpected CORBA exception: AlreadyBound
      > 2009-07-01 17:41:16,410 [0xb7fc0770] INFO AtmiBrokerLogc -
      > main Unexpected exception in serverrun()
      I think there will still be an issue in that the server currently deploys an old administration service which needs to be disabled and refactored to be a standard XATMI service

        Gliffy Diagrams




              • Assignee:
                zhfeng Zheng Feng
                tomjenkinson Thomas Jenkinson
              • Votes:
                0 Vote for this issue
                0 Start watching this issue


                • Created: