Bug 41032 - [XMA] Unstable XMA connection - timing out.
Summary: [XMA] Unstable XMA connection - timing out.
Alias: None
Product: Visual Studio Extensions
Classification: Xamarin
Component: XMA ()
Version: 4.0.0 (C6)
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: Bugzilla
Depends on:
Reported: 2016-05-11 19:04 UTC by Al Clark [MSFT]
Modified: 2016-10-07 16:48 UTC (History)
6 users (show)

Is this bug a regression?: ---
Last known good build:

Logs and version information (116.94 KB, application/zip)
2016-05-11 19:04 UTC, Al Clark [MSFT]

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.

Please create a new report on Developer Community with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:

Description Al Clark [MSFT] 2016-05-11 19:04:48 UTC
Created attachment 15974 [details]
Logs and version information

= Overview

Customer is experiencing time-outs when connected to Mac agent.

= Steps to replicate

Connect to Mac agent from Visual Studio

= Expected results

Mac should stay connected while in use

= Actual results

Mac disconnects on occasion.

=Other information

Possible relevant information in logs:

Xamarin.Messaging.VisualStudio.MessagingService Error: 0 : [2016-05-05 04:32:06.7116] An error occurred on the underlying client while executing an operation. Details: The operation has timed out.
Xamarin.Messaging.Client.MessagingClient Error: 0 : [2016-05-05 04:32:06.7306] An error occured on client vs7244fatma while executing a post for topic xma/ping/Broker403214
Xamarin.Messaging.Exceptions.MessagingException: There was an error while trying to subscribe to response topic xma/ping/Broker403214 ---> System.Net.Mqtt.Client.ClientException: A timeout occured while waiting for the subscribe confirmation of client for topic vs7244fatma/+/xma/ping/Broker403214 ---> System.TimeoutException: The operation has timed out.

Xamarin -
(Full information requested but not yet provided

=== Xamarin Studio Enterprise ===
Version 5.10.3 (build 51)
Installation UUID: eb716c73-19a6-42da-8386-d057991c82ab Runtime:
Mono 4.2.3 (explicit/832de4b)
GTK+ 2.24.23 (Raleigh theme)
Package version: 402030004 === Xamarin.Profiler ===
Not Installed
=== Apple Developer Tools === Xcode 7.3 (10183.3)
Build 7D175
=== Xamarin.iOS ===
Version: (Visual Studio Enterprise Trial) Hash: 5f11db8
Branch: master
Build date: 2016-03-25 21:26:55-0400
=== Xamarin.Android ===
Version: (Visual Studio Enterprise Trial) Android SDK: Not found
=== Xamarin Android Player ===
Not Installed
=== Xamarin.Mac ===
Version: (Visual Studio Enterprise Trial) === Build Information ===
Release ID: 510030051
Git revision: f3c0d982165f785772d125f02668370d929014fb Build date: 2016-03-24 18:51:31-04
Xamarin addins: ee5cfd3ecb6b20de47c1d25efb9a9abc101e8ce7 Build lane: monodevelop-lion-cycle6-c6sr3
=== Operating System ===
Mac OS X 10.11.4
Darwin 15.4.0 Darwin Kernel Version 15.4.0
Fri Feb 26 22:08:05 PST 2016 root:xnu-3248.40.184~3/RELEASE_X86_64 x86_64
Comment 1 Brendan Zagaeski (Xamarin Team, assistant) 2016-05-11 19:11:57 UTC
Some similar timeout issues have been reported by users to be fixed on Cycle 7 and higher. (See for example, Bug 38695, Comment 1, and the "preliminary customer verifications" in Bug 38695, Comment 5.)

I will mark as NEEDINFO to check if the reporting user on this bug still sees issues with Cycle 7 or higher. Thanks!
Comment 3 Brendan Zagaeski (Xamarin Team, assistant) 2016-10-07 16:48:26 UTC
Marking as "resolved noresponse" for now since there has been no further update from the user about the behavior after Cycle 7.  Cycle 8 – Service Release 0 contains additional changes to several timeout parameters that might also help with symptoms similar to this.

If the original reporting user still sees precisely the original symptom from Comment 0 when using the latest versions, please do reopen this bug report.

Support Team