Hello,
I have run into the following problem. When running a very long lasting
bean transaction on one BEA Weblogic 6.1 SP2 application server I get no errors,
but on the other one that in fact should be quite similar to the first one, I get:
EJB Exception: ; nested exception is:
weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ attempt to pop from an empty stack ] ...
The exception is raised from my EJB-s ejbPassivate() method, that only does the following:
public void ejbPassivate() {
logger = null;
monitorLogger = null;
try {
ctx.close();
} catch (Exception e) {
e.printStackTrace();
}
}
"ctx" represents a UserTransaction.
What I am doing is calculating some dividends, and this takes time. There I
have several thousand holders, and in a for loop, I calculate dividends for each
one of them. The application doing this represents a stateful session bean (EJB).
I have done research, consulted with developers by my side, but still get this
strange error.
What causes this? What should I check? Is it in Weblogic application server's configuration
or in the java bean?
Thanks in advance!
A.
I have run into the following problem. When running a very long lasting
bean transaction on one BEA Weblogic 6.1 SP2 application server I get no errors,
but on the other one that in fact should be quite similar to the first one, I get:
EJB Exception: ; nested exception is:
weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ attempt to pop from an empty stack ] ...
The exception is raised from my EJB-s ejbPassivate() method, that only does the following:
public void ejbPassivate() {
logger = null;
monitorLogger = null;
try {
ctx.close();
} catch (Exception e) {
e.printStackTrace();
}
}
"ctx" represents a UserTransaction.
What I am doing is calculating some dividends, and this takes time. There I
have several thousand holders, and in a for loop, I calculate dividends for each
one of them. The application doing this represents a stateful session bean (EJB).
I have done research, consulted with developers by my side, but still get this
strange error.
What causes this? What should I check? Is it in Weblogic application server's configuration
or in the java bean?
Thanks in advance!
A.