On Aug 30, 2007, at 4:59 PM, Anita Kulshreshtha wrote:
I left geronimo overnight on a remote machine and forgot to shut it
down. Next morning I found the following exception on the console.
There were some exception in geronimo.log which I think are not
related
to this.
Exception in thread "Persistence Adaptor Task"
java.lang.NullPointerException
at org.apache.derby.jdbc.XAStatementControl.<init>(Unknown
Source)
at
org.apache.derby.jdbc.EmbedXAConnection.wrapStatement(Unknown
Source)
<snip>
Hi Anita,
Were you running tests from the standalone client? Were you running
the admin console, perhaps? I've certainly left servers running for
extended periods, without a problem...
--kevan
geronimo.log
..............................................
22:05:35,015 INFO [OpenEJB] The following method doesn't have a
transaction policy assigned: public abstract java.util.Set
javax.management.j2ee.Management.queryNames
(javax.management.ObjectName,javax.management.QueryExp)
throws java.rmi.RemoteException
.....................................................
.....................................................
22:05:39,656 INFO [OpenEJB] The following method doesn't have a
transaction policy assigned: public abstract java.lang.Object
javax.management.j2ee.Management.getAttribute
(javax.management.ObjectName,java.lang.String)
throws
javax.management.MBeanException,javax.management.AttributeNotFoundExce
ption,javax.management.InstanceNotFoundException,javax.management.Refl
ectionException,java.rmi.RemoteException
.............................................
The stand alone client seemed to work correctly.