Uploaded image for project: 'Data Management'
  1. Data Management
  2. DM-1121

Simplify and refactor the Event Services API

    XMLWordPrintable

    Details

    • Type: Epic
    • Status: Done
    • Resolution: Done
    • Fix Version/s: None
    • Component/s: ctrl_events
    • Labels:
      None
    • Epic Name:
      Refactor Event Services
    • Story Points:
      18
    • WBS:
      02C.07.02.01
    • Team:
      Data Facility
    • Cycle:
      Summer 2015

      Description

      Remove old fixed metadata; refactor using more generic metadata interface.

      For W15:
      Pietrowicz, S - 100%
      Start Dec 2014, finish Dec 2014

      For S15 rollover:
      Pietrowicz, S - 11%
      Start March 2015, finish April 2015

        Attachments

          Issue Links

          blocks

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. DM-1122 Write a log4cxx handler that emits events for log messages

          • Done

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. DM-1123 requirements and specifications for initial version of inter-Task communication

          • Won't Fix

            Activity

            Hide
            Permalink
            spietrowicz Steve Pietrowicz added a comment -

            One thing to keep in mind is that the tests for this package all hit the ActiveMQ broker, which is not a good thing. We've already run into an instance where the timeout values in tests have hit someone because they were 100ms, and they didn't get a response in time. Those tests have been increased to timeout values of 1000ms.

            We have to either decide to set up a local broker for people to test (which would involve requiring Java, since the broker is in Java), or to disable the package and/or tests for this package.

            Show
            spietrowicz Steve Pietrowicz added a comment - One thing to keep in mind is that the tests for this package all hit the ActiveMQ broker, which is not a good thing. We've already run into an instance where the timeout values in tests have hit someone because they were 100ms, and they didn't get a response in time. Those tests have been increased to timeout values of 1000ms. We have to either decide to set up a local broker for people to test (which would involve requiring Java, since the broker is in Java), or to disable the package and/or tests for this package.

              People

              Assignee:
              spietrowicz Steve Pietrowicz
              Reporter:
              ktl Kian-Tat Lim
              Watchers:
              Darko Jevremovic, Kian-Tat Lim, Steve Pietrowicz
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Jenkins Builds

                  No builds found.