[rabbitmq-discuss] Unexpected server crash and .NET API: disconnect is not detected?

[Alfonso Pantoja]

Emile,

I've compared Subscription class with my custom subscription using Beyond
compare
and the only differences are:


1. I've added custom binding methods
2. I deleted "shouldDelete" logic because don't wanted to remove queues


I can confirm the RabbitMQ is listing the connection.

In fact in queues appear something like this.

Listing connections ...
guest   192.168.0.121   62966   running

(checked after more than 5 minutes after killing the application)
Using TCPVIEW  (SysInternals tools) there is no connection from my machine
to the server.


Name  | Node |  Parameters  | status |  Ready |  unacked   | Total  |
incoming |  deliver/get  | ack

alfonsoqueue | rabbit at nodename | D | Idle | 0 | 1000 | 1000 |   |  0/s|   |

In connection and channels (web admin) I can see the connection in state
Running

Regards,

Alfonso

2011/3/31 Emile Joubert <emile at rabbitmq.com>

> Hi Alfonso,
>
> I'm still not able to reproduce the problem you describe. As far as I can
> see the subscription and the underlying connection are properly disposed and
> the shutdown eventhandler is called if the connection is interrupted.
>
> As previously suggested, is it possible that some of your modifications
> prevent the socket exception from affecting the Subscription? Are you able
> to reproduce the problem without any modifications to the rabbit library?
>
> On 31/03/11 10:49, Alfonso wrote:
>
>> One more thing regarding my previous message:
>>
>> 1. I disabled the newtwork connection from my development machine
>> (RabbitMQ server is on another machine).
>>
>> 2. I've see that the connection is still in some way "alive" even if I
>>
>
> You can confirm whether the connection is alive by running "rabbitmqctl
> list_connections" or "netstat".
>
>
>
> Regards
>
> Emile
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20110331/9da2e4aa/attachment.htm>