Mysql在哪里查询优化(Mysql where between query optimization)

 第二次查看你的代码（在我的咖啡之后，它更好）， java.io.IOException: Pipe closed使用JSch 0.1.42 java.io.IOException: Pipe closed是由你建议的逻辑问题引起的： 
 
 你的finally块在你的for循环中。 因为始终调用finally块，无论是否发生异常，客户端总是在第一个iteraton末尾的finally块中断开连接： 
 
for(...){
    try{
        ...
    }catch(...){
        ...
    }finally{
        # this finally block is inside your for loop
        # finally block is always called whether an exception occur or not
        # on the first iteration, this is called and close your client
        try{
            if(client!=null){
                # nope, it will close the client for next iteration!
                client.disconnect();
            }if(fsdisPath!=null){
                # good to close this however
                fsdisPath.close();
            }
        }catch(Exceptionex){
            ex.printStackTrace();
        }
    }
}
 
 相反，你应该有类似的东西： 
 
try {
    for(...){
        try{
            ...
        }catch(...){
            ...
        }finally{
            try{
                if(fsdisPath!=null){
                    fsdisPath.close();
                }
            }catch(Exceptionex){
                ex.printStackTrace();
            }
        }
    }
} finally {
    if(client!=null){
        client.disconnect();
    }
}
 
 将for循环作为代码可用性的函数也可能是个好主意;） 
 
 java.lang.NoSuchFieldError: identities是由您的应用程序使用不同的JSch版本的另一个标准引起的，因为您根据Maven依赖关系树提供了证据。 
 
 
 
 做了一个mvn依赖：tree -Dverbose在项目中（使用jsch 0.1.50）我发现该项目和我在原帖中添加了所有日志：特别是：+ - org.mule.transports：mule-transport -sftp：jar：3.4.0：编译[INFO] | + - （com.jcraft：jsch：jar：0.1.44-1：compile - 与0.1.42冲突省略）+ - （com.jcraft：jsch：jar：0.1.42：compile - 省略与0.1的冲突。 50）[INFO] - com.jcraft：jsch：jar：0.1.50：编译[INFO] 
 

Looking at your code a second time (right after my coffee, it's better), java.io.IOException: Pipe closed with JSch 0.1.42 is effectively caused by a logic issue as you suggested:
 
Your finally block is inside your for loop. As a finally block is always called whether an exception occur or not your client is always disconnected by the finally block at the end of the very first iteraton: 
 
for(...){
    try{
        ...
    }catch(...){
        ...
    }finally{
        # this finally block is inside your for loop
        # finally block is always called whether an exception occur or not
        # on the first iteration, this is called and close your client
        try{
            if(client!=null){
                # nope, it will close the client for next iteration!
                client.disconnect();
            }if(fsdisPath!=null){
                # good to close this however
                fsdisPath.close();
            }
        }catch(Exceptionex){
            ex.printStackTrace();
        }
    }
}
 
Instead you should have something like:
 
try {
    for(...){
        try{
            ...
        }catch(...){
            ...
        }finally{
            try{
                if(fsdisPath!=null){
                    fsdisPath.close();
                }
            }catch(Exceptionex){
                ex.printStackTrace();
            }
        }
    }
} finally {
    if(client!=null){
        client.disconnect();
    }
}
 
It may also be a good idea to have your for loop as a function for code lisibility ;)
 
java.lang.NoSuchFieldError: identities is caused by another par of your application using a different JSch version as you put into evidence per your Maven dependency tree. 
 
 
 
did a mvn dependency:tree -Dverbose in the project (using jsch 0.1.50) and I found that the project and I have added all the logs in the original post: Particularly this : +- org.mule.transports:mule-transport-sftp:jar:3.4.0:compile [INFO] | +- (com.jcraft:jsch:jar:0.1.44-1:compile - omitted for conflict with 0.1.42) +- (com.jcraft:jsch:jar:0.1.42:compile - omitted for conflict with 0.1.50) [INFO] - com.jcraft:jsch:jar:0.1.50:compile [INFO]