I am running a Junit test. Example
@Test
public void ReturnEntityByPrimaryKeyTest()
{
PkEntity oPkEntity = new PkEntity();
oPkEntity.setId("908210");
oPkEntity.setType("CUS");
oPkEntity.setBusinessType("1");
try
{
Assert.assertNotNull(this.m_entity.ReturnEntity(oPkEntity));
}
catch(Exception ex)
{
fail(ex.toString());
}
}
When I run this test right after build and deploy, it errors out. It tells me
junit.framework.AssertionFailedError: at
com.mds.ecommerce.base.EntityEmdsTest.ReturnEntityByPrimaryKeyTest(EntityEmdsTest.java:73)
The subsequent tests run fine. When I rerun this same test,
Russell Collins
Sr. Software Engineer
McLane Advanced Technology
"Do or do not, there is no try." - Yoda
From: David Jencks [mailto:[email protected]]
Sent: Wednesday, July 22, 2009 7:47 PM
To: [email protected]
Subject: Re: Geronimo Sleeping
More details would be good.... for instance, "does not get the ejb object" mean
you get null or an exception? I personally have never seen anything like this;
a sample to reproduce it would be extremely helpful.
thanks
david jencks
On Jul 22, 2009, at 5:24 PM, Russell Collins wrote:
**Update** This is most notable when I do a deployment. First, the existing
application is undeployed and removed and then the newly compiled application
(EAR) is deployed to the application server.
Russell Collins
Sr. Software Engineer
McLane Advanced Technology
"Do or do not, there is no try." - Yoda
From: Russell Collins [mailto:[email protected]]
Sent: Wednesday, July 22, 2009 2:36 PM
To: '[email protected]<mailto:'[email protected]>'
Subject: Geronimo Sleeping
I am having a some interesting behavior with Geronimo and I wondering if this
can be remedied. It seems that the Geronimo server is falling asleep when it
has been inactive for a while. I am running unit tests with Junit 4 bringing
back Remote ejb objects. During the first call, the first ejb retrieval does
not get the ejb object. The rest of the calls are fine even when re-running
the first call that originally failed. It seems as though Geronimo is closing
a connection and then timing out while it reopens a connect that has been
closed (maybe this is totally false). If anyone can point me in the right
direction, I would greatly appreciate it.
Russell Collins
