[GitHub] aiooly closed issue #309: The broker listen port is fixed to 10911

2018-05-16 Thread GitBox
aiooly closed issue #309: The broker listen port is fixed to 10911 URL: https://github.com/apache/rocketmq/issues/309 This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub

[GitHub] aiooly commented on issue #309: The broker listen port is fixed to 10911

2018-05-16 Thread GitBox
aiooly commented on issue #309: The broker listen port is fixed to 10911 URL: https://github.com/apache/rocketmq/issues/309#issuecomment-389418263 sorry i found how to config it! This is an automated message from the Apache

[GitHub] aiooly opened a new issue #309: The broker listen port is fixed to 10911

2018-05-16 Thread GitBox
aiooly opened a new issue #309: The broker listen port is fixed to 10911 URL: https://github.com/apache/rocketmq/issues/309 https://github.com/apache/rocketmq/blob/a8ef6d61149457088e55d9c260d7e5d5f5b1dd3a/broker/src/main/java/org/apache/rocketmq/broker/BrokerStartup.java#L107 how to

[GitHub] liyangbing commented on issue #249: master-slave sync model performance improve

2018-05-16 Thread GitBox
liyangbing commented on issue #249: master-slave sync model performance improve URL: https://github.com/apache/rocketmq/issues/249#issuecomment-389417176 i understand the question, i have two question first question handleDiskFlush(result, putMessageResult, msg);

[GSoC][ROCKETMQ-379][Support AMQP protocol for RocketMQ] Project Discussion.

2018-05-16 Thread Ratnasingam Kasthuriraajan
Hi all, I am working on the above mentioned project for GSoC 2018. My proposal for the project is below . I have mentioned the project plan and timeline on that proposal. Currently I am working on

[GitHub] vongosling closed pull request #155: [ROCKETMQ-280] improve dependency management in parent pom

2018-05-16 Thread GitBox
vongosling closed pull request #155: [ROCKETMQ-280] improve dependency management in parent pom URL: https://github.com/apache/rocketmq/pull/155 This is a PR merged from a forked repository. As GitHub hides the original diff on merge, it is displayed below for the sake of provenance: As

[GitHub] vongosling commented on issue #155: [ROCKETMQ-280] improve dependency management in parent pom

2018-05-16 Thread GitBox
vongosling commented on issue #155: [ROCKETMQ-280] improve dependency management in parent pom URL: https://github.com/apache/rocketmq/pull/155#issuecomment-389720768 Thanks @qqeasonchen. I will polish here before next release.

Re: [GSoC][ROCKETMQ-379][Support AMQP protocol for RocketMQ] Project Discussion.

2018-05-16 Thread Von Gosling
Hi, Well, I have created a branch naming gsoc-amqp, @Ratnasingam you could clone and pr it. As for the weekly meeting, we could schedule it on our timezone 11 am, I will have free time to collaborate with yours. For the AMQP project, we could first define how many exchange types we should

[GitHub] lizhanhui commented on issue #303: send message always failed

2018-05-16 Thread GitBox
lizhanhui commented on issue #303: send message always failed URL: https://github.com/apache/rocketmq/issues/303#issuecomment-389750484 Thanks @aluomaidi for reporting this issue. I'll look into this issue ASAP. If you have already fixed out how to fix it, you are encouraged to create a

[GitHub] lizhanhui closed issue #308: RocketMQ 4.2 代码版本及依赖问题

2018-05-16 Thread GitBox
lizhanhui closed issue #308: RocketMQ 4.2 代码版本及依赖问题 URL: https://github.com/apache/rocketmq/issues/308 This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL

[GitHub] lizhanhui commented on issue #308: RocketMQ 4.2 代码版本及依赖问题

2018-05-16 Thread GitBox
lizhanhui commented on issue #308: RocketMQ 4.2 代码版本及依赖问题 URL: https://github.com/apache/rocketmq/issues/308#issuecomment-389749831 This indeed is a distribution issue. As explained in the netty-tcnative project page [here](https://netty.io/wiki/forked-tomcat-native.html), we'd better

[GitHub] lizhanhui commented on issue #300: Ablout public network security

2018-05-16 Thread GitBox
lizhanhui commented on issue #300: Ablout public network security URL: https://github.com/apache/rocketmq/issues/300#issuecomment-389752382 Yes, it's not safe and should not deploy RocketMQ without applying security protocols. Thankfully, we have already provided transmission tier

[GitHub] lizhanhui commented on issue #300: Ablout public network security

2018-05-16 Thread GitBox
lizhanhui commented on issue #300: Ablout public network security URL: https://github.com/apache/rocketmq/issues/300#issuecomment-389752768 In case you need administrative instructions that set up a secure cluster, your welcome to write our user mailing list.

[GitHub] lizhanhui commented on issue #300: Ablout public network security

2018-05-16 Thread GitBox
lizhanhui commented on issue #300: Ablout public network security URL: https://github.com/apache/rocketmq/issues/300#issuecomment-389752768 In case you need administrative instructions that set up a secure cluster, you're welcome to write our user mailing list.