Petals ESB Container

OutgoingConnections & IncomingConnections return both local and remote containers

Details

  • Type: Bug Bug
  • Status: Resolved Resolved
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 5.2.0
  • Fix Version/s: 5.3.0
  • Component/s: None
  • Security Level: Public
  • Description:
    Hide

    TCP container metrics OutgoingConnections & IncomingConnections return both local and remote containers connections, which appears at time of testing to be the same (and unique) container. Indeed these methods return a Map which key is a String array, allowing two different entries referring to a same container.

    Note: PETALSDISTRIB-394 will work around this by arbitrarily ignoring one of the duplicates.

    Show
    TCP container metrics OutgoingConnections & IncomingConnections return both local and remote containers connections, which appears at time of testing to be the same (and unique) container. Indeed these methods return a Map which key is a String array, allowing two different entries referring to a same container. Note: PETALSDISTRIB-394 will work around this by arbitrarily ignoring one of the duplicates.
  • Environment:
    -

Issue Links

Depends
 

Activity

Descending order - Click to sort in ascending order
Hide
Permalink
Pierre Souquet added a comment - Mon, 14 Jan 2019 - 16:23:00 +0100

TCP transporter metrics now return only remote containers (and not anymore current container)

Show
Pierre Souquet added a comment - Mon, 14 Jan 2019 - 16:23:00 +0100 TCP transporter metrics now return only remote containers (and not anymore current container)
Hide
Permalink
Pierre Souquet added a comment - Tue, 8 Jan 2019 - 17:20:38 +0100

Current container will be filtered out of the following TCP transporter metrics:

  • IncomingMessagesCount
  • OutgoingMessagesCount
  • IncomingConnections
  • OutgoingConnections
Show
Pierre Souquet added a comment - Tue, 8 Jan 2019 - 17:20:38 +0100 Current container will be filtered out of the following TCP transporter metrics:
  • IncomingMessagesCount
  • OutgoingMessagesCount
  • IncomingConnections
  • OutgoingConnections
Hide
Permalink
Pierre Souquet added a comment - Mon, 7 Jan 2019 - 15:43:29 +0100 - edited

After investigations, it seems that a single container will return itself twice (once as remote, once as local) container for some metrics. In essence, it makes no sense for TCP communications to return the current container anyway. Current container will be filtered out of the list in TCP metrics.

Show
Pierre Souquet added a comment - Mon, 7 Jan 2019 - 15:43:29 +0100 - edited After investigations, it seems that a single container will return itself twice (once as remote, once as local) container for some metrics. In essence, it makes no sense for TCP communications to return the current container anyway. Current container will be filtered out of the list in TCP metrics.

People

Dates

  • Created:
    Thu, 6 Dec 2018 - 17:31:58 +0100
    Updated:
    Mon, 14 Jan 2019 - 16:23:01 +0100
    Resolved:
    Mon, 14 Jan 2019 - 16:23:00 +0100
Atlassian JIRA (v4.1.2#531) | Report a problem | Request a feature | Contact administrators
Powered by a free Atlassian JIRA open source license for Petals ESB. Try JIRA - bug tracking software for your team.