[jira] [Created] (ROCKETMQ-292) Delete system.exit in MQAdminStartup
lindzh created ROCKETMQ-292: --- Summary: Delete system.exit in MQAdminStartup Key: ROCKETMQ-292 URL: https://issues.apache.org/jira/browse/ROCKETMQ-292 Project: Apache RocketMQ Issue Type: Improvement Components: rocketmq-tools Affects Versions: 4.1.0-incubating Reporter: lindzh Assignee: vongosling Fix For: 4.2.0-incubating When using MQAdminStartup in a java process,some args problem may cause MQAdminStartup to call system.ext and this lead to main java process shutdown. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (ROCKETMQ-291) System.out.printf throws UnknownFormatConversionException
lindzh created ROCKETMQ-291: --- Summary: System.out.printf throws UnknownFormatConversionException Key: ROCKETMQ-291 URL: https://issues.apache.org/jira/browse/ROCKETMQ-291 Project: Apache RocketMQ Issue Type: Bug Components: rocketmq-tools Affects Versions: 4.1.0-incubating Reporter: lindzh Assignee: vongosling Fix For: 4.2.0-incubating Use mqadmin printmsg -t %RETRY%consumerid ，it throws an exception like this: Exception in thread "main" java.util.UnknownFormatConversionException: Conversion = 'R' at java.util.Formatter$FormatSpecifier.conversion(Formatter.java:2691) at java.util.Formatter$FormatSpecifier.(Formatter.java:2720) at java.util.Formatter.parse(Formatter.java:2560) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (ROCKETMQ-278) Add specified cluster for cluster info cmd
lindzh created ROCKETMQ-278: --- Summary: Add specified cluster for cluster info cmd Key: ROCKETMQ-278 URL: https://issues.apache.org/jira/browse/ROCKETMQ-278 Project: Apache RocketMQ Issue Type: Improvement Components: rocketmq-client, rocketmq-namesrv, rocketmq-tools Affects Versions: 4.1.0-incubating Reporter: lindzh Assignee: Xiaorui Wang Fix For: 4.2.0-incubating When using mqadmin command clusterlist,it always display all cluster,i want to display specified cluster. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (ROCKETMQ-264) Unit test cost too long and there is exception in unit test
lindzh created ROCKETMQ-264: --- Summary: Unit test cost too long and there is exception in unit test Key: ROCKETMQ-264 URL: https://issues.apache.org/jira/browse/ROCKETMQ-264 Project: Apache RocketMQ Issue Type: Improvement Reporter: lindzh Assignee: vongosling When run mvn test , it cost too much time and some times there is exception in unit test and the test result is pass -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (ROCKETMQ-254) LoggerAppender unit test cost much time and sometimes test failure
lindzh created ROCKETMQ-254: --- Summary: LoggerAppender unit test cost much time and sometimes test failure Key: ROCKETMQ-254 URL: https://issues.apache.org/jira/browse/ROCKETMQ-254 Project: Apache RocketMQ Issue Type: Bug Components: rocketmq-client Affects Versions: 4.1.0-incubating Reporter: lindzh Assignee: Xiaorui Wang Fix For: 4.2.0-incubating LoggerAppender unit test cost much time, and in some cases it may cause test failure,fix this case this mockito. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (ROCKETMQ-239) Query message by time and get queue offset by time return is always less than want.
lindzh created ROCKETMQ-239: --- Summary: Query message by time and get queue offset by time return is always less than want. Key: ROCKETMQ-239 URL: https://issues.apache.org/jira/browse/ROCKETMQ-239 Project: Apache RocketMQ Issue Type: Bug Components: rocketmq-store Affects Versions: 4.1.0-incubating Reporter: lindzh Assignee: yukon Fix For: 4.2.0-incubating When using queryMessageByTime or searchOffsetByTime or resetOffsetByTime , DefaultMessageStore return offset is not so accurate as we want. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (ROCKETMQ-231) Pull result size is always less than given size in PullConsumer
lindzh created ROCKETMQ-231: --- Summary: Pull result size is always less than given size in PullConsumer Key: ROCKETMQ-231 URL: https://issues.apache.org/jira/browse/ROCKETMQ-231 Project: Apache RocketMQ Issue Type: Bug Components: rocketmq-broker Affects Versions: 4.0.0-incubating Reporter: lindzh Assignee: yukon Priority: Critical Fix For: 4.2.0-incubating When using PullConsumer pull message by default result size is 32,and messages is more than 32 in a queue,but broker always returns 31. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (ROCKETMQ-224) Client log4j2 logging
[ https://issues.apache.org/jira/browse/ROCKETMQ-224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16050106#comment-16050106 ] lindzh commented on ROCKETMQ-224: - Github pull request :https://github.com/apache/incubator-rocketmq/pull/120 > Client log4j2 logging > - > > Key: ROCKETMQ-224 > URL: https://issues.apache.org/jira/browse/ROCKETMQ-224 > Project: Apache RocketMQ > Issue Type: New Feature > Components: rocketmq-client >Affects Versions: 4.1.0-incubating > Environment: Jdk 1.7 >Reporter: lindzh >Assignee: Xiaorui Wang > Fix For: 4.2.0-incubating > > > When using RocketMQ client,we can only using logback or log4j for logging. If > we using log4j2,there is no client log. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (ROCKETMQ-194) log appender useing rocketmq
lindzh created ROCKETMQ-194: --- Summary: log appender useing rocketmq Key: ROCKETMQ-194 URL: https://issues.apache.org/jira/browse/ROCKETMQ-194 Project: Apache RocketMQ Issue Type: New Feature Affects Versions: 4.1.0-incubating Environment: jdk7 Reporter: lindzh Assignee: vongosling Fix For: 4.1.0-incubating As Rocketmq is widely used,A log appender is also necessary. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (ROCKETMQ-189) Misleading tip on consumeTimestamp and wrong consumeTimestamp exception message
[
https://issues.apache.org/jira/browse/ROCKETMQ-189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15984046#comment-15984046
]
lindzh commented on ROCKETMQ-189:
-
Github pull request :https://github.com/apache/incubator-rocketmq/pull/97
> Misleading tip on consumeTimestamp and wrong consumeTimestamp exception
> message
> ---
>
> Key: ROCKETMQ-189
> URL: https://issues.apache.org/jira/browse/ROCKETMQ-189
> Project: Apache RocketMQ
> Issue Type: Bug
> Components: rocketmq-client
>Affects Versions: 4.0.0-incubating
> Environment: macos,jdk8
>Reporter: lindzh
>Assignee: Xiaorui Wang
> Labels: easyfix
> Fix For: 4.1.0-incubating
>
> Original Estimate: 12h
> Remaining Estimate: 12h
>
> When I want to consume message,I use the following code,
> {quote}
> consumer.setConsumeFromWhere(ConsumeFromWhere.CONSUME_FROM_FIRST_OFFSET);
> consumer.setConsumeTimestamp("2017_0422_235500");
> {quote}
> and I got the tip as following:
> {quote}
> Exception in thread "main"
> org.apache.rocketmq.client.exception.MQClientException: consumeTimestamp is
> invalid, _MMDD_HHMMSS
> See http://rocketmq.apache.org/docs/faq/ for further details.
> at
> org.apache.rocketmq.client.impl.consumer.DefaultMQPushConsumerImpl.checkConfig(DefaultMQPushConsumerImpl.java:661)
> {quote}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
