letContextEvent event) {
>
>ServletContext context = event.getServletContext();
>
>Scheduler scheduler = new Scheduler();
>
>Task slowQueryReport = new SlowQueryReport();
>
>try {
>
>i
public void contextInitialized(ServletContextEvent event) {
ServletContext context = event.getServletContext();
Scheduler scheduler = new Scheduler();
Task slowQueryReport = new SlowQueryReport();
try {
if (Tools.isTest()) {
schedu
ry="select 1"
> jdbcInterceptors="ConnectionState;SlowQueryReportJmx(threshold=1000)"
> testOnBorrow="true"/>
>
> There is my java code:
>Map map =
> SlowQueryReportJmx.getPoolStats("java:comp/env/jdbc/" + poolName);
And
;
testOnBorrow="true"/>
There is my java code:
Map map =
SlowQueryReportJmx.getPoolStats("java:comp/env/jdbc/" + poolName);
I tried the config with
jdbcInterceptors="ConnectionState;SlowQueryReport(threshold=1000)",
but there is no messages in the Tomca
On Jun 4, 2013, at 6:26 AM, Lutischán Ferenc wrote:
> Dear Users,
>
> Please help to me:
> How to get SlowQueryReport statistics?
Usually these are logged as WARN messages. Unless you use SlowQueryReportJmx
and then they are logged and sent as JMX notifications.
>
> I t
Dear Users,
Please help to me:
How to get SlowQueryReport statistics?
I tried:
Map map =
SlowQueryReport.getPoolStats("java:comp/env/jdbc/xxx");
and
Map map =
SlowQueryReport.getPoolStats("xxx");
The result in both case was a null map.
T
-O wrote:
I recently have started using the SlowQueryReport to tackle
performance issues. The log message, unfortunately, does not
contain the parameters passed to the prepared statements.
Though AbstractQueryReport receives this information in
protected String report*Query(String query, Object
rote:
>>>>>
>>>>>> -BEGIN PGP SIGNED MESSAGE- Hash: SHA256
>>>>>>
>>>>>> Michael,
>>>>>>
>>>>>> On 5/8/13 3:01 AM, Michael-O wrote:
>>>>>>> I rec
M, Michael-O wrote:
>>> I recently have started using the SlowQueryReport to tackle
>>> performance issues. The log message, unfortunately, does not
>>> contain the parameters passed to the prepared statements.
>>> Though AbstractQueryReport receives this inform
;>> Nick,
>>>
>>> On 5/8/13 8:08 AM, Nick Williams wrote:
>>>>
>>>> On May 8, 2013, at 6:54 AM, Christopher Schultz wrote:
>>>>
>>>>> -BEGIN PGP SIGNED MESSAGE- Hash: SHA256
>>>>>
>>>
6:54 AM, Christopher Schultz wrote:
>>>
>>>> -BEGIN PGP SIGNED MESSAGE- Hash: SHA256
>>>>
>>>> Michael,
>>>>
>>>> On 5/8/13 3:01 AM, Michael-O wrote:
>>>>> I recently have started using the SlowQueryRepor
Christopher,
Am 2013-05-08 13:54, schrieb Christopher Schultz:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Michael,
On 5/8/13 3:01 AM, Michael-O wrote:
I recently have started using the SlowQueryReport to tackle
performance issues. The log message, unfortunately, does not
contain the
wrote:
I recently have started using the SlowQueryReport to tackle
performance issues. The log message, unfortunately, does not
contain the parameters passed to the prepared statements.
Though AbstractQueryReport receives this information in
protected String report*Query(String query, Object[] args
Am 2013-05-08 14:08, schrieb Nick Williams:
On May 8, 2013, at 6:54 AM, Christopher Schultz wrote:
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256
Michael,
On 5/8/13 3:01 AM, Michael-O wrote:
I recently have started using the SlowQueryReport to tackle
performance issues. The log message
el-O wrote:
>>> I recently have started using the SlowQueryReport to tackle
>>> performance issues. The log message, unfortunately, does not
>>> contain the parameters passed to the prepared statements.
>>> Though AbstractQueryReport receives this inform
On May 8, 2013, at 6:54 AM, Christopher Schultz wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Michael,
>
> On 5/8/13 3:01 AM, Michael-O wrote:
>> I recently have started using the SlowQueryReport to tackle
>> performance issues. The log me
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Michael,
On 5/8/13 3:01 AM, Michael-O wrote:
> I recently have started using the SlowQueryReport to tackle
> performance issues. The log message, unfortunately, does not
> contain the parameters passed to the prepared statement
Hi,
I recently have started using the SlowQueryReport to tackle performance issues.
The log message, unfortunately, does not contain the parameters passed to the
prepared statements. Though AbstractQueryReport receives this information in
protected String report*Query(String query, Object
18 matches
Mail list logo