Sorry, this email showed up as if it had been sent on Jun 15th... weird.
(woldn't have found it had glen not im'd about it)
Regardless of this, we should not attempt to make POI threadsafe. There
are many reasons for this (most of which are obvious, 2 threads
modifying 1 stream is generally a bad idea anyhow). To clarify:
ThreadLocal and synchronized (Object) {} should be avoided. It would be
purely deceptive and nothing more than a performance drag to introduce
thread safety.
Secondly, while I don't double JDK 1.2 on Win2k is a very unideal
platform, I suspect removing thread synchronization/etc will reduce the
number of glitches.
Does anyone have a compelling reason why POI should be thread safe (lack
of thread safety does not mean you can't use it in multithreaded
applications, it just means that two threads can't use POI at once --
which they can't do so successfully at the end of the day anyhow -- or
at least not to any actual advantage)? Loaded question, but I'd like to
settle that issue.
Thanks,
Andy
On Sat, 2002-06-15 at 18:09, Avik Sengupta wrote:
> The problem is not JServ, its JDK1.2 on Win2K .. this has issues for
> IllegalMonitorState exception on correct code.
>
> For eg., see http://marc.theaimsgroup.com/?l=ant-user&m=102276404123305&w=2
> and http://marc.theaimsgroup.com/?l=ant-dev&m=102387539321688&w=2
>
> Quoting "Laubach, Shawn - TAFB/LAB NCC (SAIC)"
> <[EMAIL PROTECTED]>:
>
> > This is running under Oracle 9ias Rel. 1 so
> >
> > 1. A 1.2.1 version is what they say the are completely compatible with.
> > 2. JServ 1.1 (Don't have a choice in this)
> > 3. Win2k fully patched
> > 4. P4 1.4 1gig 2x36gig SCSI Hardrives
> >
> > I went back to the 1.5 version of POI and it reacted the same.
> >
> > Shawn Laubach
> > SAIC - Web Developer
> > B-1B System Support Management Division
> > OC-ALC/LAB, Building 3001, Tinker AFB, Oklahoma
> > dsn: 336-2473 comm: 405-736-2473 mobile: 405-245-9562
> >
> >
> > -----Original Message-----
> > From: Andrew C. Oliver [mailto:[EMAIL PROTECTED]]
> > Sent: Friday, July 05, 2002 10:34 PM
> > To: POI Users List
> > Subject: Re: IllegalMonitorStateException
> >
> >
> > Thats a threading error. POI isn't threaded. That totally makes no
> > sense. I bet its a cooincidence as to where its
> > happening. Please provide:
> >
> > 1. JDK version
> > 2. Servlet container version
> > 3. OS version
> > 4. Hardware statistics.
> >
> > -Andy
> >
> > Shawn Laubach wrote:
> >
> > >Inside a class being called by a servlet, I'm getting a
> > >IllegalMonitorStateException thrown. I've narrowed it down to three lines
> > >of code where it is occuring. A row.createCell, cell.setCellValue, and
> > >cell.setCellStyle calls. I haven't had time to narrow it down any
> > furthur.
> > >What I'm curious about, is why it would be thrown anyways. I've just
> > >started using the 1.8 dev release and I plan to try the 1.7 release next
> > >chance to see if that works.
> > >
> > >BTW, it runs fine standalone and other similar code runs fine both
> > >standalone and as a servlet.
> > >
> > >Shawn
> > >
> > >
> > >--
> > >To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
> > >For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
> > >
> > >
> > >
> > >
> >
> >
> >
> >
> > --
> > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
> >
>
>
>
> --
> To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
>
--
http://www.superlinksoftware.com - software solutions for business
http://jakarta.apache.org/poi - Excel/Word/OLE 2 Compound Document in
Java
http://krysalis.sourceforge.net/centipede - the best build/project
structure
a guy/gal could have! - Make Ant simple on complex Projects!
The avalanche has already started. It is too late for the pebbles to
vote.
-Ambassador Kosh
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
