-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Yuval,
On 9/19/16 2:55 AM, Yuval Schwartz wrote:
> Hello Chris,
>
> On Sat, Sep 17, 2016 at 7:40 PM, Christopher Schultz <
> ch...@christopherschultz.net> wrote:
>
> Yuval,
>
> On 9/16/16 2:33 PM, Yuval Schwartz wrote:
Hey Chris,
Hello Chris,
On Sat, Sep 17, 2016 at 7:40 PM, Christopher Schultz <
ch...@christopherschultz.net> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Yuval,
>
> On 9/16/16 2:33 PM, Yuval Schwartz wrote:
> > Hey Chris,
> >
> > You have a line in your link that reads:
> >
> > // if you w
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Yuval,
On 9/16/16 2:33 PM, Yuval Schwartz wrote:
> Hey Chris,
>
> You have a line in your link that reads:
>
> // if you want to issue multiple queries and/or // work with
> multiple result sets, either declare more Statement // and
> ResultSet lo
Hey Chris,
You have a line in your link that reads:
// if you want to issue multiple queries and/or
// work with multiple result sets, either declare more Statement
// and ResultSet locals above and duplicate all cleanup logic for them,
// or make sure you close each object along
Thanks Chris, I'll have a look.
On Fri, Sep 16, 2016 at 6:41 PM, Christopher Schultz <
ch...@christopherschultz.net> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Yuval,
>
> On 9/16/16 3:32 AM, Yuval Schwartz wrote:
> > A few more words/questions on my issue:
> >
> > My Resource
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Yuval,
On 9/16/16 3:32 AM, Yuval Schwartz wrote:
> A few more words/questions on my issue:
>
> My Resource element used the attribute "removeAbandoned" rather
> than "removeAbandonedOnBorrow". I have now corrected this. Does
> this affect what gets
On 16/09/2016 08:32, Yuval Schwartz wrote:
> A few more words/questions on my issue:
>
> My Resource element used the attribute "removeAbandoned" rather than
> "removeAbandonedOnBorrow". I have now corrected this. Does this affect what
> gets logged (ie: I've had "logAbandoned" on this whole time
On 15/09/2016 09:30, Yuval Schwartz wrote:
> Questions:
> 1) What order does a thread dump print in? That is, I'd like to know what
> the first thread was in my thread dump (temporally) so that I might know
> which thread caused the actual issue. Is this the beginning of the thread
> dump or the
A few more words/questions on my issue:
My Resource element used the attribute "removeAbandoned" rather than
"removeAbandonedOnBorrow". I have now corrected this. Does this affect what
gets logged (ie: I've had "logAbandoned" on this whole time but have not
seen anything in the logs about abandone
Hello,
I'd rather narrow down the problem a bit more before upgrading (to make
sure that that's the issue).
It happened again, this time I took a thread dump of the instance that went
down (actually, it's only the DB connection pool that becomes unresponsive
but I remove the instance from my load
On 12/09/2016 19:02, Yuval Schwartz wrote:
> Hey Mark, thanks a lot.
>
> On Mon, Sep 12, 2016 at 4:42 PM, Mark Thomas wrote:
>
>> On 12/09/2016 11:54, Yuval Schwartz wrote:
>> It might also be a bug in the connection pool that has been fixed.
>> Upgrading to the latest 8.0.x (or better still
Hey Mark, thanks a lot.
On Mon, Sep 12, 2016 at 4:42 PM, Mark Thomas wrote:
> On 12/09/2016 11:54, Yuval Schwartz wrote:
> > Hello,
> >
> > Tomcat: 8.0.22
> > Java: jdk1.8.0_05
> > Server: Amazon Linux
> >
> > My web application looses access to the database after about 24hrs of
> > running (pro
On 12/09/2016 11:54, Yuval Schwartz wrote:
> Hello,
>
> Tomcat: 8.0.22
> Java: jdk1.8.0_05
> Server: Amazon Linux
>
> My web application looses access to the database after about 24hrs of
> running (probably dependent on amount of users, not time).
>
> No messages/exceptions are printed to the c
Hello,
Tomcat: 8.0.22
Java: jdk1.8.0_05
Server: Amazon Linux
My web application looses access to the database after about 24hrs of
running (probably dependent on amount of users, not time).
No messages/exceptions are printed to the console or log files.
When I stop tomcat, then I get a few "INF
14 matches
Mail list logo