Jan,
I will try to create a test case out of the code sample.
I think shutdown() will shut down thread pool when all requested tasks are
finished.
Thanks
On Wed, Sep 8, 2010 at 3:14 AM, Jan Torben Heuer <[email protected]>wrote:
> Augusttown wrote:
>
> > Is there a JUnit test or example written for testing
> > FeatureLock.TRANSACTION? There seems to be a problem when using
> > FeatureLock.TRANSACTION to lock and modify features. There is always a
> > java.lang.IllegalMonitorStateException exception being thrown out when
> the
> > release() is called on instance of TransactionLock. The change has
> > actually been committed to the database already before the exception.
>
> Maybe you can create a testcase from your snippet?
>
> One question, is it fine to call #shutdown() on the threadpool at that
> point? There are still threads running.
>
> Cheers,
>
> Jan
> --
> >From address is valid until 01.06.2011
>
>
>
> ------------------------------------------------------------------------------
> This SF.net Dev2Dev email is sponsored by:
>
> Show off your parallel programming skills.
> Enter the Intel(R) Threading Challenge 2010.
> http://p.sf.net/sfu/intel-thread-sfd
> _______________________________________________
> Geotools-gt2-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/geotools-gt2-users
>
------------------------------------------------------------------------------
This SF.net Dev2Dev email is sponsored by:
Show off your parallel programming skills.
Enter the Intel(R) Threading Challenge 2010.
http://p.sf.net/sfu/intel-thread-sfd
_______________________________________________
Geotools-gt2-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-gt2-users
