Android平台下如何保持Jsch Session持续存活？

Hey there! Let's tackle this SSH connection drop issue you're facing in your Android app. I've dealt with similar problems when running long-lived SSH sessions in background services, so here are some common fixes and things to check:

1. Implement SSH Keep-Alive Mechanisms #

Most SSH servers will automatically drop idle connections after a set period (often 15-30 minutes). To prevent this, you need to send periodic keep-alive packets from your client to tell the server the connection is still active.

Using JSch (the most common SSH library for Android), add these lines right after creating your Session object:

// Send a keep-alive packet every 60 seconds
session.setServerAliveInterval(60000);
// Allow up to 3 missed keep-alives before considering the connection dead
session.setServerAliveCountMax(3);

This ensures your client regularly pings the server, preventing it from marking the connection as idle and closing it.

2. Bypass Android Background Restrictions #

Android (especially API 26+) aggressively limits background services to save battery. If your SSH service runs in the background, the system might kill it after some time, which would drop your SSH connection.

Fix this by using a Foreground Service:

// In your SSH Service's onCreate() or start method
Notification notification = new NotificationCompat.Builder(this, "ssh_connection_channel")
        .setContentTitle("SSH Connection Active")
        .setContentText("Connected to " + hostname)
        .setSmallIcon(R.drawable.ic_ssh_notification)
        .build();

// Start the service in foreground mode with a persistent notification
startForeground(1, notification);

This tells Android your service is doing important work and reduces the chance of it being terminated.

3. Handle Network Changes #

Mobile devices frequently switch between WiFi and cellular data, which can break existing SSH connections. You need to listen for network state changes and re-establish the connection when connectivity is restored.

• Register a ConnectivityManager.NetworkCallback to monitor network availability.
• Add a listener for Session or Channel disconnections, and trigger a reconnection (with exponential backoff to avoid spamming) when a drop is detected.

4. Avoid Blocking I/O Streams #

If you're using a shell or exec channel, failing to read the input stream can cause buffer overflow, which will eventually block the connection and lead to a timeout. Always spawn a background thread to read from the channel's input stream:

InputStream channelInput = channel.getInputStream();
new Thread(() -> {
    byte[] buffer = new byte[1024];
    int bytesRead;
    try {
        while ((bytesRead = channelInput.read(buffer)) != -1) {
            // You can log the output or process it here—just don't ignore it
        }
    } catch (IOException e) {
        // Handle the disconnection, trigger reconnection logic
    }
}).start();

5. Check Server-Side SSH Configurations #

Sometimes the issue is on the server end. Verify your SSH server's sshd_config file for timeout settings:

# Example sshd_config settings
ClientAliveInterval 60
ClientAliveCountMax 5

These settings make the server send keep-alive packets to your client. If the server's timeout is shorter than your client's keep-alive interval, it might still drop the connection. Adjust these values to match your client's configuration.

Start with the keep-alive mechanism first—it's the quickest fix for idle timeouts. Then move on to checking background service restrictions, as Android's battery optimizations are a frequent culprit for dropped background connections.

内容的提问来源于stack exchange，提问作者ItsRedstone