#1285 jEdit never appears if ftp server is dead

[Mike Maxwell]

I am using the FTP and sessions plugins. When I last closed down jEdit, all of the files I had open were on an SFTP server. The server later died. Re-starting jEdit after the server died results in jEdit never appearing on-screen. The ftp plugin request to login to the server (by supplying username and password, or verifying a previously supplied pair) comes up, but then the jEdit screen never comes up.

I have to admit that I'm not sure that it *never* comes up. It was trying to open around 15 files on the dead server; so if it did this in sequence, waiting for each file to time out before trying the next, I suppose maybe I didn't wait long enough, although I did wait an awfully long time. Still, if that's what's happening, jEdit should display *something* (like the editor itself, and individual I/O error msgs); otherwise, it appears as if jEdit is simply dead, and there's no way to cancel loading of the files.

This is jEdit 4.3 server mode, Java 1.6.0_17, Windows Vista SP2. The problem was previously discussed on the jEdit-users mailing list (first msg in thread with same subject line as Summary above) was dated 24 Jan 2010.

[Alan Ezust]

In order to determine where the problem is, can you disable the sessions plugin and get the same problem?
If so, then the bug is in the sessions plugin, not jEdit.

[Alan Ezust]

I meant, if *not* then the bug is in the sessions plugin.
Btw, jEdit has an option in "restore previously open files on startup" with a sub-option "including remote files over VFS". I usually disable restoring remote files.

[Mike Maxwell]

Unfortunately, I can't test this, because the ftp server I was having the problem with is back up. And if I feed it the url of a non-existent ftp server, it responds immediately. Do you have an sftp server somewhere that I can save some dummy files to, and then we can take down the server?

About your comment
> I usually disable restoring remote files.
Nearly all the files I edit are on a remote server, and I want them to automatically open when I start up jEdit again. So disabling the restoring of files on remote servers isn't an option for me.

[Vadim Voituk]

Looks like the problem in FTP plugin.
It happens because VFS trying to open few remote buffers one by one, and each connection timeouts after 60 seonds.

So if you have 15 remote files should be opened at startup - the jEdit will appear in 15 mins.

Unfortunately i have no idea how to fix this.
Any ideas?

[Mike Maxwell]

On 4/19/2014 12:28 AM, Alan Ezust wrote:

• status: open --> closed-out-of-date
• Group: -->
• Comment:

Is this still an issue with jEdit 5.1?

I'm the original poster. I have not seen this happen in a long time, but I
don't think the SFTP server has gone down in a long time either. So it's hard
to tell. And I'm not sure how to simulate it. I tried just now simulating it
by giving it a non-existent ftp server, but it came back instantly with an
appropriate error msg.

So I guess you could mark it "probably fixed" :-).

---

[plugin-bugs:#1285] http://sourceforge.net/p/jedit/plugin-bugs/1285/ jEdit
never appears if ftp server is dead

Status: closed-out-of-date
Group:
Created: Tue Jan 26, 2010 04:20 AM UTC by Mike Maxwell
Last Updated: Tue Jan 26, 2010 04:20 AM UTC
Owner: nobody

I am using the FTP and sessions plugins. When I last closed down jEdit, all of
the files I had open were on an SFTP server. The server later died. Re-starting
jEdit after the server died results in jEdit never appearing on-screen. The ftp
plugin request to login to the server (by supplying username and password, or
verifying a previously supplied pair) comes up, but then the jEdit screen never
comes up.

I have to admit that I'm not sure that it never comes up. It was trying to
open around 15 files on the dead server; so if it did this in sequence, waiting
for each file to time out before trying the next, I suppose maybe I didn't wait
long enough, although I did wait an awfully long time. Still, if that's what's
happening, jEdit should display something (like the editor itself, and
individual I/O error msgs); otherwise, it appears as if jEdit is simply dead,
and there's no way to cancel loading of the files.

This is jEdit 4.3 server mode, Java 1.6.0_17, Windows Vista SP2. The problem was
previously discussed on the jEdit-users mailing list (first msg in thread with
same subject line as Summary above) was dated 24 Jan 2010.

---

Sent from sourceforge.net because you indicated interest in
https://sourceforge.net/p/jedit/plugin-bugs/1285/

To unsubscribe from further messages, please visit
https://sourceforge.net/auth/subscriptions/

--
Mike Maxwell
maxwell@umiacs.umd.edu
"My definition of an interesting universe is
one that has the capacity to study itself."
--Stephen Eastmond

[Alan Ezust]

Is this still an issue with jEdit 5.1?

[Alan Ezust]

You can simulate a server going down by unplugging your network cable or switching off wifi.

[Mike Maxwell]

On 4/19/2014 11:14 AM, Alan Ezust wrote:

You can simulate a server going down by unplugging your network cable or
switching off wifi.

Duh.

I'll have to find an ftp server that I could try this on; the one I was using
back in 2010 no longer exists.
--
Mike Maxwell
maxwell@umiacs.umd.edu
"My definition of an interesting universe is
one that has the capacity to study itself."
--Stephen Eastmond