[GitHub] [rocketmq-client-go] 1216114309zpf opened a new issue #547: message could be sent after you shutdown rmq client and start it again

[GitBox <gi...@apache.org>]

1216114309zpf opened a new issue #547:
URL: https://github.com/apache/rocketmq-client-go/issues/547


   The issue tracker is **ONLY** used for the go client (feature request of RocketMQ need to follow [RIP process](https://github.com/apache/rocketmq/wiki/RocketMQ-Improvement-Proposal)). 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](http://rocketmq.apache.org/about/contact/). 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 add the branch name [Native]/[Master] at the header of the Isssue title.**
   
   1. Please describe the issue you observed:
   
       - What did you do (The steps to reproduce)?
          I integrate rocketmq-client-go to a long-running service, which send message when some event happens. Start() in 
          internal/client.go is executed before sending each message and Shutdown() is executed after sending each message.
   
       - What did you expect to see?
          each message could be sent successfully and properly.
   
       - What did you see instead?
          first message is send successfully and properly, and when i send second message error happens: "service close is not running, please check"
   
   2. Please tell us about your environment:
   
        - What is your OS?
           centos 7
   
        - What is your client version?
           v2.0.0
   
        - What is your RocketMQ version?
           v2.0.0
   3. Other information (e.g. detailed explanation, logs, related issues, suggestions on how to fix, etc):
   
   **FEATURE REQUEST**
   
   1. Please describe the feature you are requesting.
   
   2. Provide any additional detail on your proposed use case for this feature.
   
   2. Indicate the importance of this issue to you (blocker, must-have, should-have, nice-to-have). Are you currently using any workarounds to address this issue?
   
   4. If there are some sub-tasks using -[] for each subtask and create a corresponding issue to map to the sub task:
   
       - [sub-task1-issue-number](example_sub_issue1_link_here): sub-task1 description here, 
       - [sub-task2-issue-number](example_sub_issue2_link_here): sub-task2 description here,
       - ...
   


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org