|
Moving down the path of porting from WLS to JBoss,
I came across this issue.
We are using both XA and non-XA datasources/drivers
in our application.
I have a testprogram
that calls a number of sessionbeans each of which calls a number of entity
beans. These entity beans all use the non-xa driver. these entity beans collects
a number of informations(definitions) that is used to call external
databases to create dynamic SQL statements. The external databases all use
XA-datasources.
Doing this with WLS takes approx. 1- to 3+
minuts, depending on the amount of data being retrieved. Doing it in JBoss is
something of a showstopper (3+ minuts).
During executing, JBoss insists on calling
ejbStore() contantly, where WLS just calls ejbStore() when the transaction is
about to end.
Without actually counting the number of times JBoss
makes these calls, my best guess is more than 100!!, although the number a
entity beans being accessed is around 10-15.
Further info:
We are using BMP for the entity beans. Every bean
has its own record class the implements the Serializable interface. The record
class acts as data-container between the server and client.
JBoss2.4.4_Tomcat4.0.1
-Kris
|
- Re: [JBoss-user] calling ejbStore() too many times Kris Kristensen
- Re: [JBoss-user] calling ejbStore() too many times Kris Kristensen
- Re: [JBoss-user] calling ejbStore() too many time... Michael Jara
- Re: [JBoss-user] calling ejbStore() too many ... Kris Kristensen
- Re: [JBoss-user] calling ejbStore() too m... Michael Jara
- Re: [JBoss-user] calling ejbStore() too many time... David Jencks
- Re: [JBoss-user] calling ejbStore() too many ... Kris Kristensen
- Re: [JBoss-user] calling ejbStore() too m... David Jencks
- Re: [JBoss-user] calling ejbStore() ... Kris Kristensen
