Uploaded image for project: 'Application Server 3  4  5 and 6'
  1. Application Server 3 4 5 and 6
  2. JBAS-2418

Ensure two instances of the "all" configuration can be started cleanly on a multi-homed machine

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Duplicate
    • Icon: Major Major
    • None
    • JBossAS-4.0.3 SP1
    • None
    • None

      (Background note: In 4.0.3 SP1 the SnmpAgentService reports a port conflict if two JBoss instances are started on the same node, even using the -b option. However, this request is more generic than fixing that specific issue)

      Comment from Matthew Quinlan:

      One of the most popular features of JBoss Clustering is ease of setup.
      However, our recent releases have had small bugs which make setting up
      a JBoss cluster a pain. Can we add the following scenario
      to our set of tests?

      1. multi-home the network card so that we have TWO IP-addresses
      2. copy ALL config to node1 and node2
      3. startup node1 with : run.bat -c node1 -b <IP-address#1>
      4. startup node2 with : run.bat -c node1 -b <IP-address#2>
      5. verify that there are NO EXCEPTIONS reported

      I used to unzip jboss and do this demonstration right in front of people
      and it was VERY powerful. I cannot do this anymore because of all
      of the manual steps I must take to fix this. Can you help fix this
      by creating this test case before each release of clustering?

            Unassigned Unassigned
            bstansbe@redhat.com Brian Stansberry
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: