Hi everyone,
First I want to thank you for sharing the Apache Ignite product, it's
really a cutting edge technology.
My question is related to a use case which implies the JDO persistence ORM
from datanucleus,.
I want to run a suite of JUnit tests on multiple machines in batches, this
is where Apache Ignite come in play, every batch of tests it's creating a
connection to a test database through JDO.
The first issue, from my investigations is that on the remote nodes the JDO
does't initialise properly, more specific the "plugin.xml" files from data
nucleus jars aren't found by the grid class loader.
I'm using p2p class loading, because the unit test classes can change, and I
have copied the dependency jars including datanulceus jars on the remote
nodes so there won't be high network traffic for transporting this
libraries.
Here is a sample code where createExecutableExtension is null instead of the
JDOAdapter implementation, this code is run inside a task through ignite
ExecutorService:
import org.datanucleus.plugin.PluginManager;
.......
PluginManager createPluginManager = PluginManager.createPluginManager(null,
this.getClass()
.getClassLoader());
Object createExecutableExtension =
createPluginManager.createExecutableExtension(
"org.datanucleus.api_adapter", "name", "JDO", "class-name", null,
null);
I appreciate any help regarding this case.
Have a nice day,
George.
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Data-Nucleus-plugin-extensions-aren-t-loaded-by-the-grid-class-loader-tp4928.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
