ibatis-user-java mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Chris McMahon <cochran...@hotmail.com>
Subject RE: [ANNOUNCE] iBATIS 2.3.1 Beta Available
Date Wed, 26 Mar 2008 02:01:56 GMT

Does this thread fix have anything to do with a problem I posted previously:


I recently had a problem with a multi-threaded application that would
hang after I created and disposed of around 128 threads.  I suspected
the threads were somehow causing the problem, so I switched to a Thread
Pool for my threads and the problem went away.  I was going to forget
about this problem, but I was lucky enough to stumble across this
previous email:

http://www.mail-archive.com/user-java@ibatis.apache.org/msg00026.html

It
sounds like the same problem I had and it sounds like I'm not closing
the sessions with the Thread Pool, I'm just side-stepping the problem
by reusing the same threads.  I would like to actually close the
sessions properly to avoid any problems in the future.  However, I
don't think I can use the solution offered in that email thread,
because I don't explicitly open and close sessions in my code. I'm
using declarative transactions in Spring along with its
SqlMapClientTemplate, so I don't really have direct access to the
sessions.  I would think Spring's SqlMapClientTemplate would take care
of this.  Is there a bug in Spring that isn't properly closing
sessions?  Could I not be configuring Spring correctly to do this
properly?



> Date: Tue, 25 Mar 2008 17:01:27 -0600
> From: clinton.begin@gmail.com
> To: user-java@ibatis.apache.org; dev@ibatis.apache.org
> Subject: [ANNOUNCE] iBATIS 2.3.1 Beta Available
> 
> This is a long overdue maintenance release. Fixes about 20 issues and
> includes two significant improvements. The first is the elimination of
> the Throttle. Originally included to artificially constrain threads,
> requests, and transactions to improve performance on certain
> infrastructure. It's not as much of an issue anymore and today the
> Throttle caused more problems than it solved. So bye-bye. :-) The only
> real impact you'll see is that the
> maxSessions/maxTransactions/maxRequests no longer have any effect
> whatsoever. They remain in the DTD only for backward compatibility.
> The other new change is built-in support for enums out of the box!
> It's currently a Beta release as per our process. But if all goes well
> over the next week or two, we'll vote to promote it to GA. The best
> thing you can do is test it out for us!
> 
> http://ibatis.apache.org/javadownloads.cgi
> 
> Clinton

_________________________________________________________________
How well do you know your celebrity gossip?
http://originals.msn.com/thebigdebate?ocid=T002MSN03N0707A
Mime
View raw message