[jcifs] Endless looping occuring in SmbTransport::negotiate

[Allen, Michael B (RSCH)]

Just create a static object and syncronize on it.

static Object lock = new Object();

void copyTo(..) {
syncronized( lock ) {

//everything in here.

}
}

That will probably fix it (it will also probably slow it down pretty significantly).

> -----Original Message-----
> From:	Sujit Jagdev [SMTP:sujit.jagdev at casero.com]
> Sent:	Thursday, October 31, 2002 7:52 PM
> To:	Allen, Michael B (RSCH)
> Cc:	jcifs at lists.samba.org
> Subject:	RE: [jcifs] Endless looping occuring in SmbTransport::negotiate
> 
> Well then I am afraid I am going to have to do a MD5 or CRC32 to make
> sure the copy didnt corrupt.
> What do you think
> Sujit
> 
> -----Original Message-----
> From: Allen, Michael B (RSCH) [mailto:Michael_B_Allen at ml.com] 
> Sent: Thursday, October 31, 2002 7:43 PM
> To: Sujit Jagdev
> Cc: jcifs at lists.samba.org
> Subject: RE: [jcifs] Endless looping occuring in SmbTransport::negotiate
> 
> Ahh, you're right. You'll just have to wait. Sorry.
> 
> > -----Original Message-----
> > From:	Sujit Jagdev [SMTP:sujit.jagdev at casero.com]
> > Sent:	Thursday, October 31, 2002 7:40 PM
> > To:	Allen, Michael B (RSCH)
> > Cc:	jcifs at lists.samba.org
> > Subject:	RE: [jcifs] Endless looping occuring in
> SmbTransport::negotiate
> > 
> > I cant find that code anywhere in SmbFile jcifs7b3.
> > 
> > -----Original Message-----
> > From: Allen, Michael B (RSCH) [mailto:Michael_B_Allen at ml.com] 
> > Sent: Thursday, October 31, 2002 7:26 PM
> > To: Sujit Jagdev
> > Cc: jcifs at lists.samba.org
> > Subject: RE: [jcifs] Endless looping occuring in
> SmbTransport::negotiate
> > 
> > Ahh, I see. Well to fix the concurrency issue all you have to do is
> > change the:
> > 
> >   SmbComBlankResponse blank_resp;
> > 
> > to
> > 
> >   SmbComBlankResponse blank_resp = new SmbComBlankResponse();
> > 
> > where all the members of SmbFile are declared and remove the line:
> > 
> >   blank_resp = new SmbComBlankResponse();
> > 
> > in connect().
> > 
> > The best thing to do would be to wait for a 0.7.0b7 because 0.7.0b3
> has
> > it's
> > own problems. But if you want to walk the line ...ok.
> > 
> > > -----Original Message-----
> > > From:	Sujit Jagdev [SMTP:sujit.jagdev at casero.com]
> > > Sent:	Thursday, October 31, 2002 7:18 PM
> > > To:	Allen, Michael B (RSCH)
> > > Cc:	jcifs at lists.samba.org
> > > Subject:	RE: [jcifs] Endless looping occuring in
> > SmbTransport::negotiate
> > > 
> > > Dear Michael,
> > > 
> > > But if I am still using the jcifs7b3 library.
> > > Sujit
> > > 
> > > 
> > > -----
> > > 
> > > The information contained in this message is proprietary of Casero
> > Inc.,
> > > protected from disclosure, and may be privileged. The information is
> > > intended to be conveyed only to the designated recipient(s) of the
> > > message. If the reader of this message is not the intended
> recipient,
> > > you are hereby notified that any dissemination, use, distribution or
> > > copying of this communication is strictly prohibited and may be
> > > unlawful. If you have received this communication in error, please
> > > notify us immediately by replying to the message and deleting it
> from
> > > your computer. Thank you.
> > >
> > 
> > 
> > -----
> > 
> > The information contained in this message is proprietary of Casero
> Inc.,
> > protected from disclosure, and may be privileged. The information is
> > intended to be conveyed only to the designated recipient(s) of the
> > message. If the reader of this message is not the intended recipient,
> > you are hereby notified that any dissemination, use, distribution or
> > copying of this communication is strictly prohibited and may be
> > unlawful. If you have received this communication in error, please
> > notify us immediately by replying to the message and deleting it from
> > your computer. Thank you. << File: SmbFile.java >>
> 
> 
> -----
> 
> The information contained in this message is proprietary of Casero Inc.,
> protected from disclosure, and may be privileged. The information is
> intended to be conveyed only to the designated recipient(s) of the
> message. If the reader of this message is not the intended recipient,
> you are hereby notified that any dissemination, use, distribution or
> copying of this communication is strictly prohibited and may be
> unlawful. If you have received this communication in error, please
> notify us immediately by replying to the message and deleting it from
> your computer. Thank you.
>