Let's just push out 1.2 asis nowish and then address this and any
other fixes in a 1.2.1.
I don't think we should drop it... But also let's not drop a ton of
time in it.
--jason
On Jul 16, 2007, at 6:24 PM, Matt Hogstrom <[EMAIL PROTECTED]> wrote:
Yup.
In my testing CMP mode as well as JDBC mode was working fine. The
new runtime Mode Chris had added to DayTrader was failing. The
problem manifested itself in two different ways. One manifestation
I saw was an exhaustion of the connection pool and a flurry of
connection timeouts. The second was a concurrent modification
exception. I believe they may be the same problem.
It only occurred running underload when more than one client was
accessing the system at a time. I didn't get much further than
that. I started adding some debug code but was waffling between 1.2
and 2.0.
The next step is to start adding some code to OEJB 2.x.
On Jul 16, 2007, at 8:55 PM, Dain Sundstrom wrote:
It was some connector thing Matt found. Matt can you fill Jason in
on the details?
-dain
On Jul 16, 2007, at 2:02 PM, Jason Dillon wrote:
What were the bugs that were to be "quickly fixed"? I forget its
been so long.
Why not just push it out asis?
--jason
On Jul 16, 2007, at 9:53 AM, Dain Sundstrom wrote:
1.2 has been sitting in a branch for well over 6 months now.
Originally, it was going to be delayed so some bugs could be
"quickly fixed", but it doesn't look like that is ever going to
happen. I'm not really interested in being the manager for this
release anymore, but if there is good interest in getting this
released in, say, the next two weeks, I'm willing to continue
on. Otherwise, someone else can take over.
So, does anyone care about releasing 1.2?
-dain
