MySQL Bugs: #60451: inconssistencies of server management

Bug #60451	inconssistencies of server management
Submitted:	13 Mar 2011 10:45	Modified:	6 Jun 2011 14:34
Reporter:	Peter Laursen (Basic Quality Contributor)	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Workbench: Administration	Severity:	S2 (Serious)
Version:	5.2.33	OS:	Windows (7/64)
Assigned to:		CPU Architecture:	Any
Tags:	qc

Description:
I listed in another report that it seems that WB completely randomly tells that a server instance is stopped or not. It will upload example screenshots.

I have MySQL 5.0, 5.1 and 5.5 as well as mariaDB 5.2 installed as services locally and registered in WB. The only server that responds correctly in WB is MariaDB (and note: it has *not* a service name prefixed with 'mysql' - the others are 'mysql50', 'mysql51' and 'mysql55')

I also experience memory violations, 'unhandled exceptions' and crashes when trying to manage server instance.  Yesterday it happened around 25% of times.  I will post another report about this is I am aable to isolate a clear case.

How to repeat:
see above.

Suggested fix:
don't know

first image

Attachment: inconsistent.jpg (image/jpeg, text), 43.22 KiB.

1) server stop done
2) status check returned running

.. is a 'contradiction in itself'.  Fact is that server *was* stopped.  But as WB believes it is running I cannot start it again.

image 2

Attachment: startstop.jpg (image/jpeg, text), 40.09 KiB.

Here we have " stop pending" displaying forever.  Server stopped fine in a few secons , but WB dos  not able to understand it.  So from now on server management in WB is unusable unless restarted.

All my servers are 64 bit servers if it matters.

Raising severity to "S2".

Without any desire to be involved in code internals I think that these (and a lots of similar problems in WB) could be because of using non-threadsafe code in a multi-threaded program.

Thank you for the bug report.

Fixed in release 5.2.34