[ 
https://issues.apache.org/jira/browse/HBASE-21108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16591154#comment-16591154
 ] 

Hadoop QA commented on HBASE-21108:
-----------------------------------

| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue}  0m  
0s{color} | {color:blue} Docker mode activated. {color} |
| {color:red}-1{color} | {color:red} patch {color} | {color:red}  0m  4s{color} 
| {color:red} HBASE-21108 does not apply to master. Rebase required? Wrong 
Branch? See https://yetus.apache.org/documentation/0.7.0/precommit-patchnames 
for help. {color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Issue | HBASE-21108 |
| JIRA Patch URL | 
https://issues.apache.org/jira/secure/attachment/12936947/HBASE-21108.002.patch 
|
| Console output | 
https://builds.apache.org/job/PreCommit-HBASE-Build/14181/console |
| Powered by | Apache Yetus 0.7.0   http://yetus.apache.org |


This message was automatically generated.



> RpcServer when trace enabled might get the following exception. 
> java.lang.StringIndexOutOfBoundsException: 
> -----------------------------------------------------------------------------------------------------------
>
>                 Key: HBASE-21108
>                 URL: https://issues.apache.org/jira/browse/HBASE-21108
>             Project: HBase
>          Issue Type: Bug
>            Reporter: Krish Dey
>            Assignee: Krish Dey
>            Priority: Major
>         Attachments: HBASE-21108.002.patch
>
>
> In the RpcServer#logResponse method the logic
> stringifiedParam = stringifiedParam.subSequence(
> 0, LOG.isTraceEnabled() ? 1000 : 150) + " <TRUNCATED>";
> If the trace is on and the length of stringifiedParam is 150< 
> stringifiedParam.length() < 1000  will get the following exception.
> java.lang.StringIndexOutOfBoundsException: String index out of range: 1000



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to