[jcifs] Exceptions "getting eaten" during SmbFile.copyTo

Michael B Allen ioplex at gmail.com
Tue Mar 3 16:06:18 GMT 2009

On Tue, Mar 3, 2009 at 3:40 AM,  <cje at atp.dk> wrote:
> Hi.
> I'm working with v1.3.1. I experience exceptions "getting eaten" during
> copyTo. In SmbFile method
> void copyTo0( SmbFile dest, byte[][] b, int bsize, WriterThread w,
> SmbComReadAndX req, SmbComReadAndXResponse resp ) throws SmbException
> there's a try-catch block:
> } catch( Exception ex ) {
> if( log.level > 1 )
> ex.printStackTrace( log );

Yeah, that is wrong.

If you comment out those three lines (starting with } catch), are the
exceptions thrown as you would expect?

I have to wonder why that catch is there at all.

Another thing that could be done is to simply rethrow it by adding a
"throw ex;" after the printStackTrace.

The "handle is invalid" error is of course a separate issue but for
the moment you might as well use that to fix the "exceptions getting
eaten" problem.


Michael B Allen
Java Active Directory Integration

More information about the jcifs mailing list