NonSerializableException / setting log writer to DataSource

Question

Hi,
Moving from 2.2.2 to 2.2.3 there arised 2 different problems:
With 2.2.3 I get a
java.io.NotSerializableException:
com.solarmetric.kodo.impl.jdbc.JDBCPrefsConfiguration
when binding a JDBCPersistenceManagerFactory to the jndi. Are there some
classes not implementing Serializable that are part of the
JDBCPersistenceManagerFactory in some configurations?
Another problem that arised with 2.2.3 (I think I had the same problem
in some early kodo implementations) is this:
Constructing a JDBCPersistenceManagerFactory with a DataSource that is
part of the jndi leads to problems if JDBCPersistenceManagerFactory
..setLogWriter is invoked.
The method then calls DataSource.setLogWriter. Some pooling layer
implementations as the one of jboss throw an exception if
DataSource.setLogWriter or other resetting methods are invoked after the
first binding of the DataSource.
In my opinion the problem could easily be solved:
-No call to DataSource.setLogWriter from
JDBCPersistenceManagerFactory .setLogWriterif
DataSource.getLogWriter is not null, or maybe better
-A configurable behaviour
Best Regards,
Christian

Answer 1

How soon can we expect the next version to be released. Is it possible
to obtain a build of the version that has this bug fixed.
Amol.
Marc Prud'hommeaux wrote:
Christian Elsen <[email protected]> wrote:
Hi,
Moving from 2.2.2 to 2.2.3 there arised 2 different problems:
With 2.2.3 I get a
java.io.NotSerializableException:
com.solarmetric.kodo.impl.jdbc.JDBCPrefsConfiguration
when binding a JDBCPersistenceManagerFactory to the jndi. Are there some
classes not implementing Serializable that are part of the
JDBCPersistenceManagerFactory in some configurations?
This is a known problem with 2.2.3:
https://bugzilla.solarmetric.com/show_bug.cgi?id=117
In 2.2.3, it is not possible to manually bind a PersistenceManagerFactory
into JNDI unless the application server is able to bind an object
that is Referencable but not Serializable.
This problem has been fixed for the next release.
Another problem that arised with 2.2.3 (I think I had the same problem
in some early kodo implementations) is this:
Constructing a JDBCPersistenceManagerFactory with a DataSource that is
part of the jndi leads to problems if JDBCPersistenceManagerFactory
.setLogWriter is invoked.
The method then calls DataSource.setLogWriter. Some pooling layer
implementations as the one of jboss throw an exception if
DataSource.setLogWriter or other resetting methods are invoked after the
first binding of the DataSource.
In my opinion the problem could easily be solved:
-No call to DataSource.setLogWriter from
JDBCPersistenceManagerFactory .setLogWriterif
DataSource.getLogWriter is not null, or maybe better
-A configurable behaviour
I have made an enhancement request for this:
https://bugzilla.solarmetric.com/show_bug.cgi?id=133
It is technically a bug in JBoss's DataSource implementstion, since
setLogWriter() is only supposed to throw a SQLException (which
we currently handle and ignore), but there is probably no harm
in just catching all Exceptions when setLogWriter() fails.
Best Regards,
Christian