1. Bug MXS-297
    postinstall on debian copies wrong file in /etc/init.d
  2. New Feature MXS-463
    .secret file path has double slash
  3. Bug MXS-450
    Syslog default prefix is MaxScale not maxscale
  4. New Feature MXS-389
    Please statically link maxbinlogcheck (and maybe other cli utilities)
  5. Task MXS-367
    Initial sensible /etc/maxscale.cnf is needed.
  6. Bug MXS-363
    rpm building seems to do something wrong with maxscale libraries
  7. Task MXS-362
    Make the logging augmentation configurable.
  8. Task MXS-357
    It should be possible to disable augmentation of logged messages.
  9. Bug MXS-352
    With no backend connection, services aren't started
  10. Bug MXS-310
    MaxScale 1.2 does not completely cleanly change to the maxscale user
  11. New Feature MXS-302
    Allow maxscale startup configuration to be controlled on rpms via /etc/sysconfig/maxscale
  12. New Feature MXS-298
    Please tag in git your release versions and provide better linking to the download locations
  13. Bug MXS-293
    Bug in init script, and maxscale --user=maxscale does run as root
  14. Bug MXS-276
    Memory leak of buffer in connection router readQuery
  15. Bug MXS-267
    wrong results when connecting from pymysql driver
  16. Bug MXS-266
    pt-log-player fails with readwritesplit
  17. Bug MXS-258
    ERR_error_string could overflow in future
  18. New Feature MXS-257
    filters not always intercept 'USE db' calls
  19. Task MXS-241
    Allow priority definition for galera monitor nodes
  20. New Feature MXS-224
    BLR: Improve disconnection reporting of connections via the MySQL interface
  21. Bug MXS-210
    Check MaxScale user privileges
  22. Bug MXS-175
    sudden signal 6 abort after running for 2 days
  23. Bug MXS-164
    setting log_debug=1 triggers signal 11 crash
  24. Sub-Task MXS-132
    Add support for mandatory option master-uu-id in MaxScale binlog server
  25. Bug MXS-111
    maxscale binlog events shown in show services seems to be double-counted for the master connection
  26. Bug MXS-588
    weightby and readwritesplit not working as expected
  27. Bug MXS-583
    MaxScale malloc(): memory corruption with wrong router_option
  28. New Feature MXS-555
    allow setting ulimit -FSn xxxxxx via /etc/default/maxscale on debian/ubuntu
  29. Bug MXS-552
    Maxscale BETA 1.3.0 missing dependencies
  30. New Feature MXS-502
    Log server state changes
  31. Bug MXS-487
    lost connection to backend server
  32. Bug MXS-38
    bugzillaId-688: Incorrect backend state leads to confusing and untraced client errors
  33. Bug MXS-35
    bugzillaId-451: maxscale main() exit code is always 0 after it daemonizes
  34. Bug MXS-29
    bugzillaId-589: detect if MAXSCALE_SCHEMA.HEARTBEAT table is not replicated
  35. Bug MXS-3
    Remove code for atomic_add in skygw_utils.cc
  36. Bug MXS-454
    log_augmentation does not accept boolean parameters
  37. New Feature MXS-451
    LEAST_GLOBAL_CONNECTIONS unclear in docs
  38. Sub-Task MXS-438
    Add shutdown/restart commands to maxinfo
  39. Sub-Task MXS-437
    Add flush logs and set/clear server to maxinfo
  40. Bug MXS-436
    Invalid threads argument is ignored and MaxScale starts with one thread
  41. Bug MXS-427
    Logging a large string causes a segmentation fault
  42. Bug MXS-407
    Maxscale binlogrouter binlog names are unncessarily length-limited
  43. Bug MXS-392
    Update to "Rabbit MQ setup and MaxScale Integration" document
  44. Bug MXS-386
    max_sescmd_history should not close connections
  45. Bug MXS-385
    disable_sescmd_history can cause false data to be read.
  46. Task MXS-382
    Regular asserts should not be used in test programs.
  47. Bug MXS-379
    Incorrect handing of a GWBUF may cause SIGABRT.
  48. Bug MXS-373
    If config file is non-existent, maxscale crashes.
  49. Bug MXS-366
    Multi-source slave servers are not detected.
  50. Bug MXS-365
    Load data local infile connection abort when loading certain files
Refresh results