Unable to bind EEPersistenceManagerFactory to JNDI

Question

I get the following exception trying to bind EEPersistenceManagerFactory to
JNDI with Kodo 2.2.3 (running with Weblogic 6.1 SP1):
javax.naming.ConfigurationException. Root exception is
java.rmi.MarshalException: failed to marshal
bind(Ljava.lang.String;Ljava.lang.Object;Ljava.util.Hashtable;); nested
exception is:
java.io.NotSerializableException:
com.solarmetric.kodo.impl.jdbc.JDBCPrefsConfiguration
java.io.NotSerializableException:
com.solarmetric.kodo.impl.jdbc.JDBCPrefsConfiguration
at java.io.ObjectOutputStream.outputObject(ObjectOutputStream.java:1148)
at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:366)
at
java.io.ObjectOutputStream.outputClassFields(ObjectOutputStream.java:1827)
at
java.io.ObjectOutputStream.defaultWriteObject(ObjectOutputStream.java:480)
at java.io.ObjectOutputStream.outputObject(ObjectOutputStream.java:1214)
Anyone else run into this?

Answer 1

Sasha-
That exception indicates that your PersistenceManagerFactory has not
yet been configured with the proper driver information. Note that the
JDOConnectionFactory does not use the system.prefs information by
default: it is designed to be configured internally as per
the JCA specification.
I'm sorry to say, but it actually looks like there is no way to bind
either the EEPersistenceManagerFactory or the JDOConnectionFactory into
JNDI (unless you extends the EEPersistenceFactory with your own
Referenceable implementation).
I have made a bug report about this:
https://bugzilla.solarmetric.com/show_bug.cgi?id=117
We will certainly try to have this fixed as soon as possible. Can you
please add a comment to the bug report with how urgently this is
affecting you?
Sasha Haghani <[email protected]> wrote:
Patrick,
I get a different problem with JDOConnectionFactory (in 2.2.3)...calling
getPersistenceManager() on it throws this exception:
Exception in thread "main" javax.jdo.JDODataStoreException: The JDBC driver
name "null" is not a valid class.
NestedThrowables:
java.lang.NullPointerException
at com.solarmetric.kodo.impl.jdbc.schema.DB.<init>(DB.java:62)
at com.solarmetric.kodo.impl.jdbc.schema.DB.getInstance(DB.java:37)
at
com.solarmetric.kodo.impl.jdbc.JDBCPersistenceManagerFactory.initConfigurati
on(JDBCPersistenceManagerFactory.java:155)
at
com.solarmetric.kodo.impl.jdbc.JDBCPersistenceManagerFactory.setup(JDBCPersi
stenceManagerFactory.java:265)
at
com.solarmetric.kodo.runtime.PersistenceManagerFactoryImpl.privateSetup(Pers
istenceManagerFactoryImpl.java:810)
at
com.solarmetric.kodo.runtime.PersistenceManagerFactoryImpl.getPersistenceMan
ager(PersistenceManagerFactoryImpl.java:53)
"Patrick Linskey" <[email protected]> wrote:
Sasha,
This is a known problem with Kodo JDO 2.2.3 EE, caused by a bug in our
JCA implementation.
You should be able to work around this problem by binding a
JDOConnectionFactory instead of an EEPersistenceManagerFactory.
com.solarmetric.kodo.impl.jdbc.ee.JDOConnectionFactory extends
EEPersistenceManagerFactory.
Unfortunately, JDOConnectionFactory implements Serializable although it
is not actually serializable. However, as JDOConnectionFactory also
implements javax.resource.Referenceable, the JNDI bind should succeed.
Finally, one other alternative is to use Kodo's JCA support to locate
the PersistenceManagerFactory. Unfortunately, you are using WebLogic 6.1
SP1, which has a flaky JCA implementation. Weblogic 6.1 SP2 resolves
these problems. So, your best option is probably to upgrade your
Weblogic install to SP2 and use JCA (as outlined in our docs).
JDBCPrefsConfiguration will properly serialize in the next patch release
of Kodo JDO.
-Patrick
Patrick Linskey [email protected]
SolarMetric Inc. http://www.solarmetric.com
Marc Prud'hommeaux [email protected]
SolarMetric Inc. http://www.solarmetric.com
Kodo Java Data Objects Full featured JDO: eliminate the SQL from your code