Hi all,
I am evaluating orion and everything is turning out fine, except
something that is worrying me. When I shutdown the server (
using the: java -jar admin.jar ormi://localhost <username> <password>
-shutdown), I get the following:
------------- CUT HERE --------------
[ListManagerEJB] Set context
[ListManagerEJB] Created
[ListManagerEJB] Datasource acquired
[ListManagerEJB] Connection acquired
[SecurityManagerEJB] User :fls was successfully authenticated
Shutting down...
[ListManagerEJB] Passivated
Error serializing bean: com.evermind.sql.af
[SecurityManagerEJB] Passivated
Error serializing bean: com.evermind.sql.af
[LibraryManagerEJB] Passivated
Error serializing bean: com.evermind.sql.af
[LibraryManagerEJB] Passivated
Error serializing bean: com.evermind.sql.af
[uniqueIDEJB] Passivated
Error serializing bean: com.evermind.sql.af
--------------- CUT HERE ---------------
And when I restart the server:
--------------- CUT HERE ---------------
[fls@dbs orion]$ java -jar orion.jar
Error deserializing session: java.io.WriteAbortedException: Writing
aborted by e
xception; java.io.NotSerializableException: com.evermind.sql.af
Error deserializing session: java.io.WriteAbortedException: Writing
aborted by e
xception; java.io.NotSerializableException: com.evermind.sql.af
Error deserializing session: java.io.WriteAbortedException: Writing
aborted by e
xception; java.io.NotSerializableException: com.evermind.sql.af
Error deserializing session: java.io.WriteAbortedException: Writing
aborted by e
xception; java.io.NotSerializableException: com.evermind.sql.af
Error deserializing session: java.io.WriteAbortedException: Writing
aborted by e
xception; java.io.NotSerializableException: com.evermind.sql.af
Orion/1.0 initialized
--------------- CUT HERE --------------
Is this normal ? Am I doing something wrong ? I don't think the problem
is with my beans, since the NotSerializableException seems to regard an
internal orion class (com.evermind.sql.af), but I could be wrong.
This worries me a bit, since, for now it isn't preventing me from doing
anything, but in a future, with the high load of the server when the
need comes for it to start passivating/activating the beans, might be a
problem.
Thanks in advance for your help
Fabio Silva
