> I am trying to write a windows service that uses jabber-net to
> communicate with a Jabber server. Everything is working great. I am
> trying to make sure the connection to the server is resilient. I had a
> scenario occur where network connectivity with the server was lost and
> the auto reconnection did not occur.

> I can reproduce this scenario by connecting to the server. Releasing
> my network interface's IP by doing an "ipconfig /release" and
> "ipconfig /renew" If the connection comes back immediately a
> reconnection occurs. If the connection is not restored within 20
> seconds I get this exception:

> bedrock.net.AsyncSocketConnectionException: Bad host: jabber80.com

> Can anyone on this list speak to this behavior. Is this a bug. Does
> this work as expected? I am willing to put my own connection
> management code around the JabberClient's connection but I just wanted
> to check with the community to see if there was a best practice I was
> missing or a jabber-net wizard out there with a good idea.

> I have created this issue to capture this problem:
> http://code.google.com/p/jabber-net/issues/detail?id=23

> The intent is that for recoverable errors, auto-reconnection happens, but
> for non-recoverable ones (like invalid DNS), reconnection stops.

> For the moment, I would just turn auto-reconnect off, and handle
> reconnects
> yourself in OnDisconnected and OnError.

> For the future, let's have a discussion about what we should do on
> different
> sorts of failure modes; it's possible that the current approach isn't
> right.

> On 4/29/08 11:11 AM, "KevM" <scound...@gmail.com> wrote:

> > I am trying to write a windows service that uses jabber-net to
> > communicate with a Jabber server. Everything is working great. I am
> > trying to make sure the connection to the server is resilient. I had a
> > scenario occur where network connectivity with the server was lost and
> > the auto reconnection did not occur.

> > I can reproduce this scenario by connecting to the server. Releasing
> > my network interface's IP by doing an "ipconfig /release" and
> > "ipconfig /renew" If the connection comes back immediately a
> > reconnection occurs. If the connection is not restored within 20
> > seconds I get this exception:

> > bedrock.net.AsyncSocketConnectionException: Bad host: jabber80.com

> > Can anyone on this list speak to this behavior. Is this a bug. Does
> > this work as expected? I am willing to put my own connection
> > management code around the JabberClient's connection but I just wanted
> > to check with the community to see if there was a best practice I was
> > missing or a jabber-net wizard out there with a good idea.

> > I have created this issue to capture this problem:
> > http://code.google.com/p/jabber-net/issues/detail?id=23

> For the moment, I would just turn auto-reconnect off, and handle reconnects
> yourself in OnDisconnected and OnError.

> For the future, let's have a discussion about what we should do on different
> sorts of failure modes; it's possible that the current approach isn't right.

> On 4/29/08 11:11 AM, "KevM" <scound...@gmail.com> wrote:

> > I am trying to write a windows service that uses jabber-net to
> > communicate with a Jabber server. Everything is working great. I am
> > trying to make sure the connection to the server is resilient. I had a
> > scenario occur where network connectivity with the server was lost and
> > the auto reconnection did not occur.

> > I can reproduce this scenario by connecting to the server. Releasing
> > my network interface's IP by doing an "ipconfig /release" and
> > "ipconfig /renew" If the connection comes back immediately a
> > reconnection occurs. If the connection is not restored within 20
> > seconds I get this exception:

> > bedrock.net.AsyncSocketConnectionException: Bad host: jabber80.com

> > Can anyone on this list speak to this behavior. Is this a bug. Does
> > this work as expected? I am willing to put my own connection
> > management code around the JabberClient's connection but I just wanted
> > to check with the community to see if there was a best practice I was
> > missing or a jabber-net wizard out there with a good idea.

> > I have created this issue to capture this problem:
> >http://code.google.com/p/jabber-net/issues/detail?id=23