LAN plugin no longer reconnects after failing with "j is already closed", requires force kill after connection loss

[nabijaczleweli]

On LineageOS 14 (Android 9) with Total Commander 3.0b12 and TotalCmd-LAN (Windows shares) 3.09, when connection is lost to a share (phone off, wifi off, whatever), opening a folder either (a) succeeds transparently, (b) fails once with "connection lost" or "j has already been closed", then you see the same folder view, and clicking it opens the folder, or (c) fails once with "j has already been closed", you get booted to home screen, and you can open the share again and it connects.

On LineageOS 21 (Android 14) with Total Commander 3.50d and TotalCmd-LAN (Windows shares) 3.50 (as well as another similar Android 12 (Sony stock) installation), you always get "j has already been closed", booted to home screen, and opening the share again gives "j has already been closed" ad mortam defecatam. The only way to solve this is to kill Total Commander by swiping it away from the task switcher but this doesn't really work if you're playing audio through the TC media queue (notification keeps it alive so you need to kill the audio, kill TC, reopen the queue, maybe requeue and seek).

This feels like it should Just™ reconnect transparently, as it (by accident?) did under 3.0b12/3.09.

[ghisler(Author)]

1. Can you tell me which version of Samba your server is running? So far I haven't been able to get the error "j has already been closed".
You can use one of the following commands:
smbstatus --version
or
smbd -V
2. When exactly does this happen? Do I need to keep the connection open for a longer amount of time?

[www.manyplay.de]

hi,
this problem exists also on network drives (ds-play,d-link - etc pipi), when they are in hibernate mode.

clicking on a content for example a media file, does not refresh the device and its still "sleeping".

only after a hard termination of the lan plugin in apps (i tried it with several from A5 to 14) gives
you a chance to open the connection again.

after a reconnect the network device starts spinning again and a connection apears till the next
hibernation/spindown starts again.

the easiest way is to integrate a "stop plugin" wenn TC checks that a connection is already given.

the message "...is already closed" happens after clicking again on that connection to obtain a new one
after already one was taken for this connection a while ago.

the device does not respond and the message apears...