The issue tracker is ONLY used for the go client (feature request of RocketMQ need to follow RIP process). Keep in mind, please check whether there is an existing same report before your raise a new one.
Alternately (especially if your communication is not a bug report), you can send mail to our mailing lists. We welcome any friendly suggestions, bug fixes, collaboration, and other improvements.
Please ensure that your bug report is clear and that it is complete. Otherwise, we may be unable to understand it or to reproduce it, either of which would prevent us from fixing the bug. We strongly recommend the report(bug report or feature request) could include some hints as to the following:
BUG REPORT
Please describe the issue you observed:
What did you do (The steps to reproduce)?
restart server
What did you expect to see?
start normal
What did you see instead?
start common producer error start producer failed
Please tell us about your environment:
What is your OS?
centos7
What is your client version?
github.com/apache/rocketmq-client-go v1.2.4
Other information (e.g. detailed explanation, logs, related issues, suggestions on how to fix, etc):
pConfig := &rocketmq.ProducerConfig{
ClientConfig: rocketmq.ClientConfig{
GroupID: "GID_XXXXXXXXXXXX",
NameServer: "127.0.0.135:9876",
},
//Set to Common Producer as default.
ProducerModel: rocketmq.OrderlyProducer,
}
var err error
producer, err = rocketmq.NewProducer(pConfig)
if err != nil {
fmt.Println("create common producer failed, error:", err)
os.Exit(1)
}
err = producer.Start()
if err != nil {
fmt.Println("start common producer error", err)
os.Exit(1)
}
The issue tracker is ONLY used for the go client (feature request of RocketMQ need to follow RIP process). Keep in mind, please check whether there is an existing same report before your raise a new one.
Alternately (especially if your communication is not a bug report), you can send mail to our mailing lists. We welcome any friendly suggestions, bug fixes, collaboration, and other improvements.
Please ensure that your bug report is clear and that it is complete. Otherwise, we may be unable to understand it or to reproduce it, either of which would prevent us from fixing the bug. We strongly recommend the report(bug report or feature request) could include some hints as to the following:
BUG REPORT
Please describe the issue you observed:
Please tell us about your environment:
Other information (e.g. detailed explanation, logs, related issues, suggestions on how to fix, etc):