The following issue introduced in version 4.4 affects showValues.

Despite one should be able to call showValues at any time during the lifetime of a table (i.e. after addTable and before removeTable),
the call will be refused in case the Engine is currently disconnected or still connecting and an exception will be thrown to the caller.

Hence, any use of showValues as a means to populate the table at startup will probably fail with an exception.
On the other hand, any use of showValues to modify a table while data is coming will work, but it might throw an exception as well, as soon as a disconnection occurred.