Bug #83008 | MySQL X plugin - improve reporting if port in use | ||
---|---|---|---|
Submitted: | 15 Sep 2016 8:38 | Modified: | 24 Jan 2017 14:36 |
Reporter: | Simon Mudd (OCA) | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server: Document Store: X Plugin | Severity: | S3 (Non-critical) |
Version: | 8.0.0 | OS: | Any |
Assigned to: | CPU Architecture: | Any |
[15 Sep 2016 8:38]
Simon Mudd
[15 Sep 2016 8:42]
Daniƫl van Eeden
Might be a duplicate of: Bug #81826 X Plugin startup error messages Related: Bug #82761 If binding to mysqlx port fails this is not visible from status vars
[16 Sep 2016 9:23]
MySQL Verification Team
Hello Simon, Thank you for the report and feedback. Verifying based on my internal discussion with the Developer. I too initially thought it is dup of Bug#81826, but we concluded that this popped up after Bug #81826 fixed. Thanks, Umesh
[24 Jan 2017 14:36]
Tony Bedford
Posted by developer: An entry has been added to the 5.7.17 and 8.0.1 changelogs: When two X Plugin instances were started on the same port, the resulting error message was split over two lines and contained duplicate information.