On 16 February 2017 17:26:18 GMT+00:00, Chris Keilitz wrote:
>I've implemented Tomcat JDBC connection pool stand-alone, outside of
>Tomcat
>or any app server or container and cannot get the Juli logging working
>-
>console or file. The connection pool works great, but I
I will look into both suggestions, conflicting property files and the debug
version.
I am connecting to MS SQL Server 2008 R2 (SP1), using the sqljdbc41.jar
file. The access to SQL Server works great, insert, updates, queries,
stored procedures...no issues. I am just trying to activate the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Chris,
On 2/16/17 1:08 PM, Chris Keilitz wrote:
> I'm assuming, once configured properly, the Tomcat JDBC connection
> pool would output log messages. Unfortunately, I currently get no
> console or file output...even after trying numerous
>
What database are you connecting to ? Oracle ? MySQL ? If Oracle, then
you're probably using its specific driver, and there is a debug version
(the "_g" version) that logs.
According to you, what kind of log the Tomcat driver should write ?
2017-02-16 19:08 GMT+01:00 Chris Keilitz
I'm assuming, once configured properly, the Tomcat JDBC connection pool
would output log messages. Unfortunately, I currently get no console or
file output...even after trying numerous logging.properties changes.
I'm hoping for a little help to understand the proper way to configure a
stand alone
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Chris,
On 2/16/17 12:26 PM, Chris Keilitz wrote:
> I've implemented Tomcat JDBC connection pool stand-alone, outside
> of Tomcat or any app server or container and cannot get the Juli
> logging working - console or file. The connection pool works
I've implemented Tomcat JDBC connection pool stand-alone, outside of Tomcat
or any app server or container and cannot get the Juli logging working -
console or file. The connection pool works great, but I cannot get the
logging going. I've added CATALINA_HOME to the local directory and have