Bug: Close client w/o closing file = can't change to other channel

[abiharbani]

This might be a bug. If I close client app / crashed the client app, when I get back in, the client wouldn't change to another channel _unless_ I watch the last channel. Please advice.

I'm a newbie on Sage, so I might be missing something.

-- Abi

[mandrews44]

Abi,

Please check if this happening again if you properly close down the client or only when it crashes.

If the client is crashing on you, there isn't anything that can be done until the server recognises the client isn't there anymore and resets the connection. The issue is TCP/IP has no real way of knowing the client has crashed and doesn't report a disconnect to the server. I believe the server will eventually correct the problem but not right away in the event of a client crash.

I believe if you fix the client crash, you will solve the channel change issue.

What is happening when the client crashes? Can you recreate the crash? If so, what do you do. Also, Once you can recreate the crash, start sage and cause the crash. Then, upload the latest sage_x.txt file found in your sagetv folder.

Regards,

Mark

[mandrews44]

Abi,

Just tested the same thing as you reported without crashing the client. Just to make sure, I did the following.

1> Confirmed there is nothing being recorded on the server
2> Opened the client and changed the channel so I would now own the tuner.
3> Watched tv for a few minutes and then closed the client without going to close file.
4> Re-opened the client and retuned to a different channel.

#4 worked as expected, channel changed just fine.

I know if I crash the client, force a shutdown or cut by network cable, this will be a different story and there isn't much more than a server side timeout can be added (if it doesn't already exist) that would assist you with this issue.

Waiting to hear more about the client crashing.

What version are you using, I am using RC3.

Regards,

Mark

[abiharbani]

Mark, I don't have to have the client crash to reproduce the problem. I'm using RC3.

Maybe it's the way I shutdown the client? I'm using Alt-F4.

I also notice some errors when I shutdown the client in the log file:

...
Error with c/s comm:java.lang.NullPointerException
NetworkManager CommunicationFailure : gigastudio/192.168.5.10:42024 type=3
...

Here's the log file:

http://gokil.is-a-geek.org:9001/pers...tvclient_0.txt

Thanks,

-- Abi