We have had a patch for a while related to a problem we ran into with TCP
https://github.com/ysw/mono-socket-problem/blob/master/Patches/cb_fix.patch
Its still not in trunk. We have provided tests of TCP not calling back
async (breaks async loop) under load without this fix. As of now our
Have you submitted the change as a pull request on github?
Alan
On 19 September 2012 13:43, Greg Young gregoryyou...@gmail.com wrote:
We have had a patch for a while related to a problem we ran into with TCP
https://github.com/ysw/mono-socket-problem/blob/master/Patches/cb_fix.patch
Its
doing now.
On Wed, Sep 19, 2012 at 3:46 PM, Alan alan.mcgov...@gmail.com wrote:
Have you submitted the change as a pull request on github?
Alan
On 19 September 2012 13:43, Greg Young gregoryyou...@gmail.com wrote:
We have had a patch for a while related to a problem we ran into with TCP
Ok, I'll push to 2.10/2.12
On Fri, Aug 17, 2012 at 1:19 AM, Gonzalo Paniagua Javier
gonzalo.m...@gmail.com wrote:
On Thu, Aug 9, 2012 at 11:57 AM, Greg Young gregoryyou...@gmail.com
wrote:
This would be a good one to get into trunk
Thanks guys. There is a matching push on list object pool I believe the two
are needed together. We have a few others as well...
On Friday, August 17, 2012, Rodrigo Kumpera wrote:
Ok, I'll push to 2.10/2.12
On Fri, Aug 17, 2012 at 1:19 AM, Gonzalo Paniagua Javier
gonzalo.m...@gmail.com
Well, I've been reviewing this change and I'm not sure how it does improve
our situation. It's hard
to commit a change without any sort of explanation on why it improve things.
The poll backend has its own synchronization on its modify callback. The
other two, kqueue and epool,
simply do a
On Thu, Aug 9, 2012 at 11:57 AM, Greg Young gregoryyou...@gmail.com wrote:
This would be a good one to get into trunk
https://github.com/ysw/mono-socket-problem/blob/master/Patches/cb_fix.patch
Rodrigo, I did the patch above and it seems to make things better for
Greg. I can't push it right
On Thu, Aug 9, 2012 at 1:47 PM, Greg Young gregoryyou...@gmail.com wrote:
An update to this. Some of the failures have been taken away (also
with our patch mentioned). However simple test apps using sockets (or
it appears any callbacks) in mono are not stable.
This I would imagine prevent
Actually its worse than that. We have found that *anything that uses
callbacks* suffers from the same problems (eg any async API, say a
timer).
We have looked at writing our own socket library but the scope of
these bugs is amazing.
On Thu, Aug 9, 2012 at 9:00 AM, gelin yan dynami...@gmail.com
Hi Greg,
As we're approaching the 2.12 release date, it would be superb if you could
file bugs with
test cases for your issues. I do want to ensure that mono parallel stack is
stable.
You can attach a test case as private if you can't disclosure it.
On Thu, Aug 9, 2012 at 2:01 AM, Greg Young
We already have put it here with some associated fixes.
On Thu, Aug 9, 2012 at 7:48 AM, Rodrigo Kumpera kump...@gmail.com wrote:
Hi Greg,
As we're approaching the 2.12 release date, it would be superb if you could
file bugs with
test cases for your issues. I do want to ensure that mono
This would be a good one to get into trunk
https://github.com/ysw/mono-socket-problem/blob/master/Patches/cb_fix.patch
On Thu, Aug 9, 2012 at 5:51 PM, Greg Young gregoryyou...@gmail.com wrote:
We already have put it here with some associated fixes.
On Thu, Aug 9, 2012 at 7:48 AM, Rodrigo
An update to this. Some of the failures have been taken away (also
with our patch mentioned). However simple test apps using sockets (or
it appears any callbacks) in mono are not stable.
This I would imagine prevent most from actually being able to use mono
for any serious work.
Greg
On Sun,
On Tue, Jul 17, 2012 at 7:49 AM, Greg Young gregoryyou...@gmail.com wrote:
Hey all.
As this is a big issue for us and I feel a huge problem for mono in general
at this point as it means sockets basically dont work which is a strong
point of unix environments, I would like to propose something
Brett,
No completion callback is what proves the problem, unless there is a
problem in the sample code itself.
I tried to rebuild mono with thread/pool instead of epoll socket
implementation and still get the same problem. So, I concluded it is
not epoll specific problem.
-yuriy
On Thu, Jul
Hi Yuriv, in which environments can you reproduce it? I tried on OSX with
mono 2.10 and 2.12 for half an hour each with no luck.
On Thu, Jul 19, 2012 at 3:55 AM, Yuriy Solodkyy yu...@couldbedone.comwrote:
Brett,
No completion callback is what proves the problem, unless there is a
problem in
Hey all.
As this is a big issue for us and I feel a huge problem for mono in general
at this point as it means sockets basically dont work which is a strong
point of unix environments, I would like to propose something I have done
in the past. I am willing to offer a bounty (personally) for a
Btw to avoid confusion and duplicated work if someone starts could we just
sync a bit in this thread?
On Tuesday, July 17, 2012, Greg Young wrote:
Hey all.
As this is a big issue for us and I feel a huge problem for mono in
general at this point as it means sockets basically dont work which
On Wed, Jun 27, 2012 at 9:23 AM, Greg Young gregoryyou...@gmail.com wrote:
Trying to get it into a testcase has been very difficult unfortunately
we only really see it at saturation levels and not commonly. Seems
like some kind of internal race condtion.
Are the begin/end calls more stable
Chatted with the guys and issues persist on trunk. I will try to get a test
app
On Thursday, June 28, 2012, Gonzalo Paniagua Javier wrote:
On Wed, Jun 27, 2012 at 9:23 AM, Greg Young
gregoryyou...@gmail.comjavascript:;
wrote:
Trying to get it into a testcase has been very difficult
We are experiencing an issue with async behaviours in sockets (with
SendAsync/callback not Begin/End).
Our visible issue is that when in a send loop we will fail on our
heartbeats. After debugging and counting calls into/out of
SendAsync/callback we see that we are inside of a call to SendAsync
Not knowing anything else, I saw that there was very recently work done
in Async Sockets, The following commit, date June 18th (about a week and
a half ago) is titled Fix Async Sockets, it's a one line change but
seems to include a unit test which would indicate they are working
properly now:
We've been aware of such issues, could you file a bug and attach a test
case with it please?
This would really really help us fix it.
On Wed, Jun 27, 2012 at 4:08 AM, Greg Young gregoryyou...@gmail.com wrote:
We are experiencing an issue with async behaviours in sockets (with
Trying to get it into a testcase has been very difficult unfortunately
we only really see it at saturation levels and not commonly. Seems
like some kind of internal race condtion.
Are the begin/end calls more stable and preferable at this time?
On Wed, Jun 27, 2012 at 9:14 AM, Rodrigo Kumpera
24 matches
Mail list logo
