Bug #82054 Removing schema after failure to initialize domain type handler
Submitted: 29 Jun 2016 14:41 Modified: 19 Dec 2018 9:55
Reporter: Alexander Potapov Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Cluster: Cluster/J Severity:S3 (Non-critical)
Version:7.4.11 OS:Windows
Assigned to: MySQL Verification Team CPU Architecture:Any

[29 Jun 2016 14:41] Alexander Potapov
Description:
We have mysql-cluster-gpl-7.4.11-winx64 running on Windows 8 64bits.
I use 7.4.11 ClusterJ with Java 1.8 64bits.

When I try to run the same code on Windows 10 64 bits I get following messages in the log:
Jun 29, 2016 12:11:11 PM com.mysql.clusterj.core.SessionFactoryImpl getDomainTypeHandler FINEST: DomainTypeToHandler for entities.IEntity(interface entities.IEntity) returned null

Jun 29, 2016 12:11:11 PM com.mysql.clusterj.core.metadata.DomainTypeHandlerFactoryImpl createDomainTypeHandler INFO: Removing schema entity after failure to initialize domain type handler for class entities.IEntity.

After that my code fails to map Java object to my database table by saying:
Failure getting NdbTable for class entities.IEntity, table entity. Verify that the table is defined with ENGINE=NDB.

How to repeat:
Have sample clusterj application with 64bits ndbclient.dll working on windows 8. Then run it on Windows 10.
[30 Jun 2016 9:54] Alexander Potapov
Situation is that code was trying to connect to non existent database. Miss leading logging messages!
[19 Nov 2018 9:55] MySQL Verification Team
Hi,

I do not see difference in behavior between windows 8 and windows 10 here?

thanks
Bogdan
[20 Dec 2018 1:00] Bugs System
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".