Petals ESB Container

Container attachments are incomplete if launched concurrently

Details

  • Type: Bug Bug
  • Status: Resolved Resolved
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 5.0.0
  • Fix Version/s: 5.0.1
  • Component/s: Topology/network
  • Security Level: Public
  • Description:
    Hide

    I have 6 standalone containers that I want to attached to a target topology initially composed of 2 containers.
    All 6 standalone containers are attached concurrently using both containers of the target topology.

    When attachments done, I use Petals CLI to list the containers known on each containers. On some containers, I don't have all containers declared. In the following example, containers 'initial-container-1', 'initial-container-2' and 'initial-container-4' are missing :

    petals-cli@localhost:7700>connect -y
    Connected on localhost:7700 with 'petals'
    petals-cli@localhost:7700>topology-list 
    Domain: Target-PEtALS
    * Container: initial-container-3 (Started)
    ** Host: 192.168.1.100
    ** JMX port: 7705
    ** TCP port: 7805
    ** JMX username: ********
    ** JMX password: ********
    * Container: target-container-0 (Started)
    ** Host: localhost
    ** JMX port: 7700
    ** TCP port: 7800
    ** JMX username: ********
    ** JMX password: ********
    * Container: initial-container-5 (Started)
    ** Host: 192.168.1.100
    ** JMX port: 7707
    ** TCP port: 7807
    ** JMX username: ********
    ** JMX password: ********
    * Container: initial-container-0 (Started)
    ** Host: 192.168.1.100
    ** JMX port: 7702
    ** TCP port: 7802
    ** JMX username: ********
    ** JMX password: ********
    * Container: target-container-1 (Started)
    ** Host: localhost
    ** JMX port: 7701
    ** TCP port: 7801
    ** JMX username: ********
    ** JMX password: ********
    
    petals-cli@localhost:7700>
    Show
    I have 6 standalone containers that I want to attached to a target topology initially composed of 2 containers. All 6 standalone containers are attached concurrently using both containers of the target topology. When attachments done, I use Petals CLI to list the containers known on each containers. On some containers, I don't have all containers declared. In the following example, containers 'initial-container-1', 'initial-container-2' and 'initial-container-4' are missing :
    petals-cli@localhost:7700>connect -y
    Connected on localhost:7700 with 'petals'
    petals-cli@localhost:7700>topology-list 
    Domain: Target-PEtALS
    * Container: initial-container-3 (Started)
    ** Host: 192.168.1.100
    ** JMX port: 7705
    ** TCP port: 7805
    ** JMX username: ********
    ** JMX password: ********
    * Container: target-container-0 (Started)
    ** Host: localhost
    ** JMX port: 7700
    ** TCP port: 7800
    ** JMX username: ********
    ** JMX password: ********
    * Container: initial-container-5 (Started)
    ** Host: 192.168.1.100
    ** JMX port: 7707
    ** TCP port: 7807
    ** JMX username: ********
    ** JMX password: ********
    * Container: initial-container-0 (Started)
    ** Host: 192.168.1.100
    ** JMX port: 7702
    ** TCP port: 7802
    ** JMX username: ********
    ** JMX password: ********
    * Container: target-container-1 (Started)
    ** Host: localhost
    ** JMX port: 7701
    ** TCP port: 7801
    ** JMX username: ********
    ** JMX password: ********
    
    petals-cli@localhost:7700>
  • Environment:
    -

Activity

People

Dates

  • Created:
    Mon, 9 Nov 2015 - 11:29:20 +0100
    Updated:
    Mon, 16 Nov 2015 - 10:17:03 +0100
    Resolved:
    Mon, 16 Nov 2015 - 10:16:47 +0100