Re: [Dev] Metrics issue when doing long running tests for Message Broker

2016-10-14 Thread Isuru Perera 
Hi,

The issue is with the numeric data types defined in METRIC_TIMER. The
precision and scale of the numeric data types needs to be increased.

I have added a comment to JIRA [1]

I will change numeric data types to "numeric(50,30)", which will have 30
digits for fractional part [2].

I can give an updated script for you to test.

Thanks!

Best Regards,

[1]
https://wso2.org/jira/browse/MB-1833?focusedCommentId=128470=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-128470
[2] https://www.postgresql.org/docs/9.6/static/datatype-numeric.html

On Mon, Oct 10, 2016 at 10:11 AM, Hasitha Hiranya  wrote:

> Hi Malith and all,
>
> MB team (sub team under Integration) is planning to do beta release of MB
> 3.2.0 on 14th Friday OCT 2016. This issue is reported as Critical. Thus
> appreciate if we can look into the issue and come to a resolution. We will
> help to reproduce the issue if needed.
>
> Thanks
>
> On Thu, Oct 6, 2016 at 8:25 AM, Malith Jayasinghe 
> wrote:
>
>> Hi Hasitha,
>>
>> Thanks for reporting this issue. I don't think we tested the metrics with
>> postgresql. We will get back to you soon.
>>
>> On Wed, Oct 5, 2016 at 5:29 PM, Hasitha Hiranya 
>> wrote:
>>
>>> Hi Performance Team ,
>>>
>>> We observed following exception when doing long running tests for MB
>>> 3.2.0 [1].
>>> Have we tested metrics with postgresql? Any idea on the issue? We
>>> created jira [2] to follow up
>>>
>>> [1].
>>>
>>> TID: [] [] [2016-10-05 17:02:44,321] ERROR 
>>> {org.wso2.carbon.metrics.jdbc.reporter.JDBCReporter}
>>> -  Error when reporting timers {org.wso2.carbon.metrics.jdbc.
>>> reporter.JDBCReporter}
>>> java.sql.BatchUpdateException: Batch entry 0 INSERT INTO METRIC_TIMER
>>> (SOURCE,TIMESTAMP,NAME,COUNT,MAX,MEAN,MIN,STDDEV,P50,P75,P95
>>> ,P98,P99,P999,MEAN_RATE,M1_RATE,M5_RATE,M15_RATE,RATE_UNIT,DURATION_UNIT)
>>> VALUES ('MBNODE30',1475701364303,'org.wso2.mb.database.read',140,10
>>> 7728.4415579,37167.08968820929,0.321192,49845.8735788001
>>> 8,2.830612,107728.4415579,107728.4415579,107728.4415
>>> 579,107728.4415579,107728.4415579,0.020532036057
>>> 3999,0.009795331416994773,0.04902573050340198,0.0415817831
>>> 1107816,'calls/second','milliseconds') was aborted.  Call
>>> getNextException to see the cause.
>>> at org.postgresql.jdbc.BatchResultHandler.handleError(BatchResu
>>> ltHandler.java:137)
>>> at org.postgresql.core.v3.QueryExecutorImpl$1.handleError(Query
>>> ExecutorImpl.java:436)
>>> at org.postgresql.core.v3.QueryExecutorImpl.processResults(Quer
>>> yExecutorImpl.java:2024)
>>> at org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecut
>>> orImpl.java:377)
>>> at org.postgresql.jdbc.PgStatement.executeBatch(PgStatement.java:1026)
>>> at org.postgresql.jdbc.PgPreparedStatement.executeBatch(PgPrepa
>>> redStatement.java:1661)
>>> at org.wso2.carbon.metrics.jdbc.reporter.JDBCReporter.reportTim
>>> ers(JDBCReporter.java:389)
>>> at org.wso2.carbon.metrics.jdbc.reporter.JDBCReporter.report(JD
>>> BCReporter.java:200)
>>> at com.codahale.metrics.ScheduledReporter.report(ScheduledRepor
>>> ter.java:162)
>>> at com.codahale.metrics.ScheduledReporter$1.run(ScheduledReport
>>> er.java:117)
>>> at java.util.concurrent.Executors$RunnableAdapter.call(Executor
>>> s.java:511)
>>> at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
>>> at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFu
>>> tureTask.access$301(ScheduledThreadPoolExecutor.java:180)
>>> at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFu
>>> tureTask.run(ScheduledThreadPoolExecutor.java:294)
>>>
>>> [2]. https://wso2.org/jira/browse/MB-1833
>>>
>>> Thanks
>>> --
>>> *Hasitha Abeykoon*
>>> Senior Software Engineer; WSO2, Inc.; http://wso2.com
>>> *cell:* *+94 719363063*
>>> *blog: **abeykoon.blogspot.com* 
>>>
>>>
>>
>>
>> --
>> Malith Jayasinghe
>>
>> WSO2, Inc. (http://wso2.com)
>> Email   : mali...@wso2.com
>> Mobile : 0770704040
>> Lean . Enterprise . Middleware
>>
>
>
>
> --
> *Hasitha Abeykoon*
> Senior Software Engineer; WSO2, Inc.; http://wso2.com
> *cell:* *+94 719363063*
> *blog: **abeykoon.blogspot.com* 
>
>


-- 
Isuru Perera
Associate Technical Lead | WSO2, Inc. | http://wso2.com/
Lean . Enterprise . Middleware

about.me/chrishantha
Contact: +IsuruPereraWSO2 
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Metrics issue when doing long running tests for Message Broker

2016-10-09 Thread Hasitha Hiranya 
Hi Malith and all,

MB team (sub team under Integration) is planning to do beta release of MB
3.2.0 on 14th Friday OCT 2016. This issue is reported as Critical. Thus
appreciate if we can look into the issue and come to a resolution. We will
help to reproduce the issue if needed.

Thanks

On Thu, Oct 6, 2016 at 8:25 AM, Malith Jayasinghe  wrote:

> Hi Hasitha,
>
> Thanks for reporting this issue. I don't think we tested the metrics with
> postgresql. We will get back to you soon.
>
> On Wed, Oct 5, 2016 at 5:29 PM, Hasitha Hiranya  wrote:
>
>> Hi Performance Team ,
>>
>> We observed following exception when doing long running tests for MB
>> 3.2.0 [1].
>> Have we tested metrics with postgresql? Any idea on the issue? We
>> created jira [2] to follow up
>>
>> [1].
>>
>> TID: [] [] [2016-10-05 17:02:44,321] ERROR 
>> {org.wso2.carbon.metrics.jdbc.reporter.JDBCReporter}
>> -  Error when reporting timers {org.wso2.carbon.metrics.jdbc.
>> reporter.JDBCReporter}
>> java.sql.BatchUpdateException: Batch entry 0 INSERT INTO METRIC_TIMER
>> (SOURCE,TIMESTAMP,NAME,COUNT,MAX,MEAN,MIN,STDDEV,P50,P75,P95
>> ,P98,P99,P999,MEAN_RATE,M1_RATE,M5_RATE,M15_RATE,RATE_UNIT,DURATION_UNIT)
>> VALUES ('MBNODE30',1475701364303,'org.wso2.mb.database.read',140,
>> 107728.4415579,37167.08968820929,0.321192,49845.87357880
>> 018,2.830612,107728.4415579,107728.4415579,107728.44
>> 15579,107728.4415579,107728.4415579,0.020532036
>> 0573999,0.009795331416994773,0.04902573050340198,0.04158178
>> 311107816,'calls/second','milliseconds') was aborted.  Call
>> getNextException to see the cause.
>> at org.postgresql.jdbc.BatchResultHandler.handleError(BatchResu
>> ltHandler.java:137)
>> at org.postgresql.core.v3.QueryExecutorImpl$1.handleError(
>> QueryExecutorImpl.java:436)
>> at org.postgresql.core.v3.QueryExecutorImpl.processResults(Quer
>> yExecutorImpl.java:2024)
>> at org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecut
>> orImpl.java:377)
>> at org.postgresql.jdbc.PgStatement.executeBatch(PgStatement.java:1026)
>> at org.postgresql.jdbc.PgPreparedStatement.executeBatch(PgPrepa
>> redStatement.java:1661)
>> at org.wso2.carbon.metrics.jdbc.reporter.JDBCReporter.reportTim
>> ers(JDBCReporter.java:389)
>> at org.wso2.carbon.metrics.jdbc.reporter.JDBCReporter.report(JD
>> BCReporter.java:200)
>> at com.codahale.metrics.ScheduledReporter.report(ScheduledRepor
>> ter.java:162)
>> at com.codahale.metrics.ScheduledReporter$1.run(ScheduledReport
>> er.java:117)
>> at java.util.concurrent.Executors$RunnableAdapter.call(
>> Executors.java:511)
>> at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
>> at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFu
>> tureTask.access$301(ScheduledThreadPoolExecutor.java:180)
>> at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFu
>> tureTask.run(ScheduledThreadPoolExecutor.java:294)
>>
>> [2]. https://wso2.org/jira/browse/MB-1833
>>
>> Thanks
>> --
>> *Hasitha Abeykoon*
>> Senior Software Engineer; WSO2, Inc.; http://wso2.com
>> *cell:* *+94 719363063*
>> *blog: **abeykoon.blogspot.com* 
>>
>>
>
>
> --
> Malith Jayasinghe
>
> WSO2, Inc. (http://wso2.com)
> Email   : mali...@wso2.com
> Mobile : 0770704040
> Lean . Enterprise . Middleware
>



-- 
*Hasitha Abeykoon*
Senior Software Engineer; WSO2, Inc.; http://wso2.com
*cell:* *+94 719363063*
*blog: **abeykoon.blogspot.com* 
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Metrics issue when doing long running tests for Message Broker

2016-10-05 Thread Malith Jayasinghe 
Hi Hasitha,

Thanks for reporting this issue. I don't think we tested the metrics with
postgresql. We will get back to you soon.

On Wed, Oct 5, 2016 at 5:29 PM, Hasitha Hiranya  wrote:

> Hi Performance Team ,
>
> We observed following exception when doing long running tests for MB 3.2.0
> [1].
> Have we tested metrics with postgresql? Any idea on the issue? We created
> jira [2] to follow up
>
> [1].
>
> TID: [] [] [2016-10-05 17:02:44,321] ERROR 
> {org.wso2.carbon.metrics.jdbc.reporter.JDBCReporter}
> -  Error when reporting timers {org.wso2.carbon.metrics.jdbc.
> reporter.JDBCReporter}
> java.sql.BatchUpdateException: Batch entry 0 INSERT INTO METRIC_TIMER
> (SOURCE,TIMESTAMP,NAME,COUNT,MAX,MEAN,MIN,STDDEV,P50,P75,
> P95,P98,P99,P999,MEAN_RATE,M1_RATE,M5_RATE,M15_RATE,RATE_UNIT,DURATION_UNIT)
> VALUES ('MBNODE30',1475701364303,'org.wso2.mb.database.read',
> 140,107728.4415579,37167.08968820929,0.321192,49845.
> 87357880018,2.830612,107728.4415579,107728.4415579,107728.
> 4415579,107728.4415579,107728.4415579,0.0205320360573999,0.
> 009795331416994773,0.04902573050340198,0.04158178311107816,'calls/second','milliseconds')
> was aborted.  Call getNextException to see the cause.
> at org.postgresql.jdbc.BatchResultHandler.handleError(
> BatchResultHandler.java:137)
> at org.postgresql.core.v3.QueryExecutorImpl$1.
> handleError(QueryExecutorImpl.java:436)
> at org.postgresql.core.v3.QueryExecutorImpl.processResults(
> QueryExecutorImpl.java:2024)
> at org.postgresql.core.v3.QueryExecutorImpl.execute(
> QueryExecutorImpl.java:377)
> at org.postgresql.jdbc.PgStatement.executeBatch(PgStatement.java:1026)
> at org.postgresql.jdbc.PgPreparedStatement.executeBatch(
> PgPreparedStatement.java:1661)
> at org.wso2.carbon.metrics.jdbc.reporter.JDBCReporter.
> reportTimers(JDBCReporter.java:389)
> at org.wso2.carbon.metrics.jdbc.reporter.JDBCReporter.report(
> JDBCReporter.java:200)
> at com.codahale.metrics.ScheduledReporter.report(
> ScheduledReporter.java:162)
> at com.codahale.metrics.ScheduledReporter$1.run(
> ScheduledReporter.java:117)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
> at java.util.concurrent.ScheduledThreadPoolExecutor$
> ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
> at java.util.concurrent.ScheduledThreadPoolExecutor$
> ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
>
> [2]. https://wso2.org/jira/browse/MB-1833
>
> Thanks
> --
> *Hasitha Abeykoon*
> Senior Software Engineer; WSO2, Inc.; http://wso2.com
> *cell:* *+94 719363063*
> *blog: **abeykoon.blogspot.com* 
>
>


-- 
Malith Jayasinghe

WSO2, Inc. (http://wso2.com)
Email   : mali...@wso2.com
Mobile : 0770704040
Lean . Enterprise . Middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Metrics issue when doing long running tests for Message Broker

2016-10-05 Thread Hasitha Hiranya 
Hi Performance Team ,

We observed following exception when doing long running tests for MB 3.2.0
[1].
Have we tested metrics with postgresql? Any idea on the issue? We created
jira [2] to follow up

[1].

TID: [] [] [2016-10-05 17:02:44,321] ERROR
{org.wso2.carbon.metrics.jdbc.reporter.JDBCReporter} -  Error when
reporting timers {org.wso2.carbon.metrics.jdbc.reporter.JDBCReporter}
java.sql.BatchUpdateException: Batch entry 0 INSERT INTO METRIC_TIMER
(SOURCE,TIMESTAMP,NAME,COUNT,MAX,MEAN,MIN,STDDEV,P50,P75,P95,P98,P99,P999,MEAN_RATE,M1_RATE,M5_RATE,M15_RATE,RATE_UNIT,DURATION_UNIT)
VALUES
('MBNODE30',1475701364303,'org.wso2.mb.database.read',140,107728.4415579,37167.08968820929,0.321192,49845.87357880018,2.830612,107728.4415579,107728.4415579,107728.4415579,107728.4415579,107728.4415579,0.0205320360573999,0.009795331416994773,0.04902573050340198,0.04158178311107816,'calls/second','milliseconds')
was aborted.  Call getNextException to see the cause.
at
org.postgresql.jdbc.BatchResultHandler.handleError(BatchResultHandler.java:137)
at
org.postgresql.core.v3.QueryExecutorImpl$1.handleError(QueryExecutorImpl.java:436)
at
org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:2024)
at
org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:377)
at org.postgresql.jdbc.PgStatement.executeBatch(PgStatement.java:1026)
at
org.postgresql.jdbc.PgPreparedStatement.executeBatch(PgPreparedStatement.java:1661)
at
org.wso2.carbon.metrics.jdbc.reporter.JDBCReporter.reportTimers(JDBCReporter.java:389)
at
org.wso2.carbon.metrics.jdbc.reporter.JDBCReporter.report(JDBCReporter.java:200)
at com.codahale.metrics.ScheduledReporter.report(ScheduledReporter.java:162)
at com.codahale.metrics.ScheduledReporter$1.run(ScheduledReporter.java:117)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)

[2]. https://wso2.org/jira/browse/MB-1833

Thanks
-- 
*Hasitha Abeykoon*
Senior Software Engineer; WSO2, Inc.; http://wso2.com
*cell:* *+94 719363063*
*blog: **abeykoon.blogspot.com* 
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev