[AG-DEV] Odd AG3 Bridge Behavior

[Todd Zimmerman]

Just to follow up on this, I've checked the Bridge.log, and here is a better definition of what
exactly is (not) happening:


1. Restarted Venueserver, RegistryPeer and Bridge services
2. Enter venue from client
3. Request bridge.
On server, 3 bridges are started:
	Starting bridge: /usr/bin/QuickBridge ['-g', '233.59.192.2', '-m', '60502', '-u', '56906']
	Starting bridge: /usr/bin/QuickBridge ['-g', '233.59.192.2', '-m', '60500', '-u', '60302']
	Starting bridge: /usr/bin/QuickBridge ['-g', '233.59.192.10', '-m', '58404', '-u', '62738']
The first two bridges are correct and properly setup.  The third bridge is to an unused ip and port.
 Not sure why it is generated, it seems completely random and incorrect.

4.  VenueClient properly connects media tools to the first 2 bridges.

5. Then I switch venues on the venue client.  Again, just as above, three more bridges are started
(2 of them correct, one of them random) and the media tools again correctly connect to the bridges.

6. Then I switch BACK to the original venue in the venueclient.  This is where it gets really odd.
The Bridge.Log file shows (properly) "Using Existing" twice (I assume for each of the media
streams).  However, again a 3rd bridge is started, again to a random address/port.  Finally, the
media tools on the venueclient connect to the correct bridge address - but to the incorrect ports.
Ports that do not appear anywhere in the logs and that are not associated with any bridge or venue,
etc.  Basically random incorrect ports.

The media tools never connect back to the original bridges (even though the processes are still
running).

I've attached the Bridge.log file, although I'm not sure its of any real use....

I'll be posting this in bugzilla, but thought I'd throw it out to the ag-dev community in hopes that
perhaps someone would have a suggestion of where I should start poking around.  This issue is quite
critical to us, since without proper bridging we can't get a large community to test/bug report this
infrastructure.


Todd




Todd Zimmerman wrote:
> I'm experiencing some odd AG3 bridge behaviour...
> 
> I'm running an AG3 venueserver and bridge setup, running the bridge as documented in one of my
> earlier posts.
> 
> The first time I connect to the bridge, a QuickBridge process is properly started on the
> bridgeserver, and connected to the multicast addresses/ports as required.  The media tools are sent
> the correct address/port and everything works.
> 
> However, when I re-enter the venue, or restart my venueclient and choose the bridge, the media tools
> start with ports that do _not_ have a QuickBridge process running.  Further, the original
> QuickBridge processes are still running on the bridgeserver; however, the venueclient/mediatools do
> not connect to those ports.  Looking through the Bridge.log file shows no reference to the ports
> that the media tools are connecting to.
> 
> As an aside, there are a few other QuickBridge processes started (3 in total) for IP addresses that
> are within the range specified in the venueserver config; however, there is no venue configured with
> these addresses (all of my venues are statically assigned).
> 
> Can I send a log in for diagnosis - and if so, which log would you like?? I'm not sure the
> Bridge.log will have relevant info or not without context for how I was connecting.
> 
> Todd
> 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Bridge.log
Type: text/x-log
Size: 6496 bytes
Desc: not available
URL: <http://lists.mcs.anl.gov/pipermail/ag-dev/attachments/20060407/c94fd0c2/attachment.bin>