-----Original Message-----
From: Karl Avedal [mailto:[EMAIL PROTECTED]]
Sent: Jueves, 23 de Noviembre de 2000 16:06
To: Juan Lorandi (Chile)
Cc: [EMAIL PROTECTED]
Subject: Re: DataSourceConnection not closed
Hello Juan,
You can rest assure that we look at every bug report reported to bugzilla.
However, we can't guarantee to be able to fix every bug within a few days,
as
I'm sure you understand.
Regards,
Karl Avedal
"Juan Lorandi (Chile)" wrote:
> I think it's related to some bug in the connection pool code...
>
> I've set my max-connections to N in my datasource
> Whenever this "hanging" happens, the DS Pool shows N connections in use, 0
> on the pool
> and the XA DS (used by CMP) shows N connections in use, 1 in the pool...
> My guess is that this is a number of very minor bugs, that under these
> circumstances produce this very nasty
> behavior.
>
> Still, Marcus et all, I'm very worried about these issues because no
> comments from Orion Team have
> arrived, I'd like to hear if they're looking into it, if they've planned
to
> look into it or what...
> but that's not happening... and the bottom line is, if you use a DB
> connection in a certain page in your site,
> and it's an Orion site, it can be easily crashed by using WAStress Tool
(MS)
> or Apache's JMeter
> (and it really is bandwidth inexpensive IMO)....
>
> JP
>
> -----Original Message-----
> From: Marcus Ahnve [mailto:[EMAIL PROTECTED]]
> Sent: Jueves, 23 de Noviembre de 2000 12:59
> To: Orion-Interest
> Subject: Re: DataSourceConnection not closed
>
> > "Juan Lorandi (Chile)" wrote:
> >
> > yes, I've been complaining about this issues starting a month ago...
> > check bugs #161 & #170 for more info
> >
> > nobody from orion replies, and it's a shame, because I canīt license
> > the products until I work my way around these
> >
> > Anybody performing a DoS attack on any Orion Web Site will effectively
> > crash the server
>
> Bug #170 was filed due to the fact that the server chrashed and burned
> if it ran out of connections. For some weird reason, it seems to be very
> CPU expensive to wait for a connection. However, now that you can
> specify the wait-timeout property we can keep the server alive, with
> tons of timeouts though. I've set the status of #170 to fixed, since the
> immediate problem is fixed. Now, for "DataSource not closed", that's a
> whole new story, but I believe that there are other reports in bugzilla
> regarding that topic. FYI, we not only get it due to timeouts, but when
> testing our app against Hypersonic's in-memory db too. No clue why.
>
> /Marcus
>
> --
> Marcus Ahnve email: [EMAIL PROTECTED]
> Lecando AB Office: +46-(0)8-634 94 18
> Sweden Mobile: +46-(0)70-462 19 18
> www.lecando.com ICQ#: 4564879
