I also see a lot of jdbc/my name is not bound in this context. Unable to
find jdbc
On Thu, May 24, 2018, 5:30 PM Alex O'Ree wrote:
> Yes it is a tomcat managed data source with postgres. The cpu usage is my
> app trying to get a managed data source. Perhaps the jdbc driver is the
> issue. ..
>
>
Looking at my stack traces it seems pretty clear. Tomcat can't
lookup/establish a connection to the database because the postgres jdbc
driver failed because of a socket exception, "the network is unreachable".
I'm not sure why this behavior is different from tomcat 7 to 8.5 but it's
becoming a bit
I did not copy any tomcat specific jars. I have validation queries
implemented programmatically.
On Sun, Jun 3, 2018 at 8:44 AM, Felix Schumacher <
felix.schumac...@internetallee.de> wrote:
>
>
> Am 02.06.2018 um 20:51 schrieb Alex O'Ree:
>
>> I think I've narrowed it down to an issue specific wi
Am 02.06.2018 um 20:51 schrieb Alex O'Ree:
I think I've narrowed it down to an issue specific with terracotta quartz
based jobs. I've wired it into using tomcat's jdbc connection pooling. I'm
also using a super
old version of it so that could be part of the problem. Interestingly this
didn't h
I think I've narrowed it down to an issue specific with terracotta quartz
based jobs. I've wired it into using tomcat's jdbc connection pooling. I'm
also using a super
old version of it so that could be part of the problem. Interestingly this
didn't happen with tomcat7 but it's more than probably s
Am 24. Mai 2018 23:30:10 MESZ schrieb Alex O'Ree :
>Yes it is a tomcat managed data source with postgres. The cpu usage is
>my
>app trying to get a managed data source. Perhaps the jdbc driver is the
>issue. ..
Care to post your configuration? Maybe there are some changes missing when you
upda
Yes it is a tomcat managed data source with postgres. The cpu usage is my
app trying to get a managed data source. Perhaps the jdbc driver is the
issue. ..
On Wed, May 23, 2018, 11:28 AM Christopher Schultz <
ch...@christopherschultz.net> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Alex,
On 5/22/18 7:39 PM, Alex O'Ree wrote:
> I've noticed a behavioral difference from tomcat 7 to 8.5. In v7, I
> used to be able to put a computer to "sleep" with tomcat running.
> On resume, everything would be just fine. On tomcat 8.5, i'm
> no
I've noticed a behavioral difference from tomcat 7 to 8.5. In v7, I used to
be able to put a computer to "sleep" with tomcat running. On resume,
everything would be just fine. On tomcat 8.5, i'm noticing that all
database connections are basically dropped and do not appear to to
restart/resume when
