The PersistenceManager has been closed Exception

Question

Hi --
I'm gettting the following exception:
javax.jdo.JDOFatalUserException: The PersistenceManager has been closed.
     at
com.solarmetric.kodo.runtime.PersistenceManagerImpl.checkClosed(PersistenceManagerImpl.java:2080)
     at
com.solarmetric.kodo.runtime.PersistenceManagerImpl.isActive(PersistenceManagerImpl.java:481)
     at
com.solarmetric.kodo.runtime.StateManagerImpl.isLoaded(StateManagerImpl.java:840)
     at
net.nearlythere.utils.Money.jdoGetnet_nearlythere_utils_Money__amount(Money.java)
     at net.nearlythere.utils.Money.compareTo(Money.java:191)
     at
net.nearlythere.business.data.ServiceIntervalPricing.isPaying(ServiceIntervalPricing.java:248)
Now Money is a persistent class which looks like this (shortened greatly):
public class Money implements Comparable, Cloneable, Serializable
public static final Money ZERO = new Money(0.0);
private BigDecimal _amount;
public int compareTo(Money money)
return amount.compareTo(money.amount);
The code that throws the exception looks like:
     Money price = sip.getPrice();
     if(price.compareTo(Money.ZERO) > 0) {
I have reason to believe the price is persistent capable. My question
is: does jdo think the ZERO is persistent capable. Clearly, it is
simply a constant, but is jdo able to handle this?
Thanks,
Dan

Answer 1

Hi Patrick,
In my system.jdo file, "Money" only shows up in only place, here's the
portion of the jdo file in question:
<package name="net.nearlythere.utils">
     <class name="Money">
     </class>
</package>
It resides in a different package than all the other objects, in case
that matters...
Dan
Patrick Linskey wrote:
Dan,
What does your .jdo file look like for Money? In particular, are you
explicitly listing ZERO as a persistent field? If so, can you try explicitly
marking it as persistence-modifier="none":
<field name="MONEY" persistence-modifier="none"/>
This might be a bug in our default persistence assignment code.
-Patrick
On 6/26/02 1:48 PM, "Dan Finkelstein" <[email protected]> wrote:
Hi Patrick,
Here's some more info on this bug. With debug code, I have now
determined that kodo things that Money.ZERO is a persistent object using
the call JDOHelper.isPersistent(Money.ZERO). I've also verified that
"price" is a persistent object -- as well it should be.
It appears that kodo is throwing the PM has been closed exception
because Money.ZERO is thought of as persistent and not part of the
current PM.
Your help is most appreciated,
Dan
Patrick Linskey wrote:
This exception is probably not happening while accessing 'amount' in
Money.ZERO, but rather while accessing 'amount' in 'price'. Additionally,
the issue is not whether or not 'price' is a persistent instance; it's
whether or not the object's PM is still open. The fact that the PM is even
being used means that the object is associated with one.
To debug, use JDOHelper.getPersistenceManager(), JDOHelper.isPersistent(),
etc.
-Patrick
On 6/8/02 10:21 PM, "Dan Finkelstein" <[email protected]> wrote:
Hi --
I'm gettting the following exception:
javax.jdo.JDOFatalUserException: The PersistenceManager has been closed.
at
com.solarmetric.kodo.runtime.PersistenceManagerImpl.checkClosed(PersistenceM
an
agerImpl.java:2080)
at
com.solarmetric.kodo.runtime.PersistenceManagerImpl.isActive(PersistenceMana
ge
rImpl.java:481)
at
com.solarmetric.kodo.runtime.StateManagerImpl.isLoaded(StateManagerImpl.java
:8
40)
at
net.nearlythere.utils.Money.jdoGetnet_nearlythere_utils_Money__amount(Money.
ja
va)
at net.nearlythere.utils.Money.compareTo(Money.java:191)
at
net.nearlythere.business.data.ServiceIntervalPricing.isPaying(ServiceInterva
lP
ricing.java:248)
Now Money is a persistent class which looks like this (shortened greatly):
public class Money implements Comparable, Cloneable, Serializable
public static final Money ZERO = new Money(0.0);
private BigDecimal _amount;
public int compareTo(Money money)
return amount.compareTo(money.amount);
The code that throws the exception looks like:
Money price = sip.getPrice();
if(price.compareTo(Money.ZERO) > 0) {
I have reason to believe the price is persistent capable. My question
is: does jdo think the ZERO is persistent capable. Clearly, it is
simply a constant, but is jdo able to handle this?
Thanks,
Dan