Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Null pointer in login service #7925

Closed
cyberduck opened this issue May 1, 2014 · 3 comments
Closed

Null pointer in login service #7925

cyberduck opened this issue May 1, 2014 · 3 comments

Comments

@cyberduck
Copy link
Collaborator

fddb1b7 created the issue

Hello,
I just updated to Cyberduck 4.4.4 (Windows 7 64bit) from 4.4.3 and it seems that SFTP login is now broken. I did not check any other protocols though.
When logging in, Cyberduck seems to connect to the server, but when successful, disconnects immediately without switching to the file browser view.

This error appears in the log file (cyberduck.log):

[background-1] FATAL ch.cyberduck.ui.AbstractController - Unhandled exception running background task null
java.lang.NullPointerException
	at ch.cyberduck.core.sftp.SFTPSession.login(SFTPSession.java:133)
	at ch.cyberduck.core.KeychainLoginService.login(KeychainLoginService.java:76)
	at ch.cyberduck.core.KeychainLoginService.login(KeychainLoginService.java:98)
	at ch.cyberduck.core.LoginConnectionService.connect(LoginConnectionService.java:149)
	at ch.cyberduck.core.LoginConnectionService.check(LoginConnectionService.java:101)
	at ch.cyberduck.core.threading.SessionBackgroundAction.connect(SessionBackgroundAction.java:175)
	at ch.cyberduck.ui.threading.BrowserBackgroundAction.connect(BrowserBackgroundAction.java:58)
	at ch.cyberduck.core.threading.SessionBackgroundAction.call(SessionBackgroundAction.java:158)
	at ch.cyberduck.ui.AbstractController$BackgroundCallable.call(AbstractController.java:159)
	at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
	at java.util.concurrent.FutureTask.run(FutureTask.java:167)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:604)
	at ch.cyberduck.core.threading.NamedThreadFactory$1.run(NamedThreadFactory.java:57)
	at java.lang.Thread.run(Thread.java:937)
@cyberduck
Copy link
Collaborator Author

@dkocher commented

In 17f2bbb. Please update to the latest snapshot build available.

@cyberduck
Copy link
Collaborator Author

fddb1b7 commented

Unfortunately, that does not seem to fix the original problem. Although there's no NullPointerException anymore, I now find the following in the logfile:

[Thread-0] ERROR ch.cyberduck.ui.AbstractController - Error scheduling background task cli.Ch.Cyberduck.Ui.Controller.ConnectionController$ReachabilityAction@1ec0c6 for execution. Task java.util.concurrent.FutureTask@3b60695 rejected from java.util.concurrent.ThreadPoolExecutor@981557[Shutting down, pool size # 1, active threads1, queued tasks # 0, completed tasks2]

There's no stack trace there.

I'm now using Cyberduck 4.5 (14559) from the snapshot channel.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Replying to [comment:3 some_user]:

Unfortunately, that does not seem to fix the original problem. Although there's no NullPointerException anymore, I now find the following in the logfile:

[Thread-0] ERROR ch.cyberduck.ui.AbstractController - Error scheduling background task cli.Ch.Cyberduck.Ui.Controller.ConnectionController$ReachabilityAction@1ec0c6 for execution. Task java.util.concurrent.FutureTask@3b60695 rejected from java.util.concurrent.ThreadPoolExecutor@981557[Shutting down, pool size # 1, active threads1, queued tasks # 0, completed tasks2]

There's no stack trace there.

I'm now using Cyberduck 4.5 (14559) from the snapshot channel.

That looks like #7680.

@iterate-ch iterate-ch locked as resolved and limited conversation to collaborators Nov 26, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant