Title: SV: How to set orion to perform a timely task..
We use
a client application that runs in the orion vm that uses a scheduledTIMER
- they've been added in JDK1.3
Timer t = new
Timer(true); t.schedule(new Job(), 0,
20);
Jaco
-Original Message-From:
[EMAIL PROTECTED]
Title: SV: How to set orion to perform a timely task..
We use
a client application that runs in the orion vm that uses a scheduledTIMER
- they've been added in JDK1.3
Timer t = new
Timer(true); t.schedule(new Job(), 0,
20);
Jaco
-Original Message-From:
[EMAIL PROTECTED]
Correction:
We ran a profiler on the Orion VM it showed that the server hold the beans
in a List object so the GC cannot have it. Further, the server aint
passivating. We wrote to Orion they admitted it as a bug.
Jaco
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL
The problem is not that simple. There's a bug.
We then ran a test program that creates a simple entity bean in an infinite
loop and then releases the reference of this entity bean. We ran a profiler
on the VM and counted the memory instances. The server keeps the beans in a
list, so the GC cant
Indeed
We then ran a test program that creates a simple entity bean in an infinite
loop and then releases the reference of this entity bean. We ran a profiler
on the VM and counted the memory instances. It turns out that
even though memory seems to be running out, orion does not passivate the
Sounds good, but WHERE does these parameters go? I include a snippit of my
orion-ejb-jar.xml file...
entity-deployment name="ejb/ActualBankControl"
location="ejb/ActualBankControl"
wrapper="ActualBankControlHome_EntityHomeWrapper78"
table="ejb/ActualBankControl"
Hi
We urgently need a solution to the following problem:
We get java.lang.OutOfMemoryErrors with our application. We increased the
amount of allocated memory to the heap, with the result that the application
just took a bit longer to run out of memory.
We then ran a test program that creates a
to close the connection when you
were finished using it.
-Original Message-
From: Jaco van Rooijen [mailto:[EMAIL PROTECTED]]
Sent: Monday, October 09, 2000 12:08 AM
To: Orion-Interest
Subject: RE: LogicalDriverManagerXAConnection not closed
Anybody have any ideas?
-Original Message
Anybody have any ideas?
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Jaco van
Rooijen
Sent: 06 October 2000 13:40
To: Orion-Interest
Subject: LogicalDriverManagerXAConnection not closed
I am developing against the stable 1.3.8
I get an output
I am developing against the stable 1.3.8
I get an output stating:
LogicalDriverManagerXAConnection not closed, check your code!
Created at:
java.lang.Throwable: OrionCMTConnection created
at com.evermind.sql.ai.init(JAX)
at com.evermind.sql.OrionCMTDataSource.getConnection(JAX)
10 matches
Mail list logo