[jcifs] Another fix for Transport deadlock issue ?

Michael B Allen mba2000 at ioplex.com
Sat Apr 29 19:21:57 GMT 2006

On Fri, 28 Apr 2006 21:48:55 -0400
"Levi Purvis" <jcifs at purvis.ws> wrote:

> On 4/28/06, Michael B Allen <mba2000 at ioplex.com> wrote:
> >
> > PS: Actually the REAL problem with all of this is that Java thread locking
> > sucks like a hoover. If we had a way to unlock a lock or just try to
> > lock without actually blocking the solution would be trivial.
> >
> See:
> http://java.sun.com/j2se/1.5.0/docs/api/java/util/concurrent/package-summary.html
> Or for backwards-compatibility:
> http://gee.cs.oswego.edu/dl/classes/EDU/oswego/cs/dl/util/concurrent/intro.html
> The official 1.5 package is based off of the latter -- essentially the
> same threading guru wrote both.  In these packages, you can find the
> constructs you want, such as class ReentrantLock with the method
> tryLock().

This is sad. NoIO. Log4bloat. And now this. Obviously no one's in control
over there.

This give me an idea though. We could write a lock class that has
unlock()/trylock() methods.


More information about the jcifs mailing list