RE: [jBoss-User] Finder Methods are slower when nothing is returnedYou can
still view the jboss site using google's caching features, just go to
www.google.com, select advanced search and put jboss.org in the domains
field. When your search returns, select the link named cached instead of
the direct link.
I am also doing BMP (because of 1 to many relations) with Oracle but am not
yet far enough along in the project to have run into this problem.
----- Original Message -----
From: Bolt, Dave
To: jBoss
Sent: Thursday, January 18, 2001 11:10 AM
Subject: RE: [jBoss-User] BMP and Container Managed Transactions was"Find er
Methods are sl ower when nothing is returned"
I tried changing the beans to reentrant = true. I did have them marked as
non-reentrant. Unfortunately it did not fix the problem. My create methods
are setting all of the attribute data.
Here's the basic issue. It looks like the connection pool is giving me
different connections for each of my beans. As a result the SQL in the beans
is isolated transactionally from the other beans. I guess the basic question
is this. If I have BMP entity beans, running under container-managed
transactions. And if I have beans that have dependency relationships (For
example a foreign-key relationship in the DB) in the back-end database. How
do I write my SQL and connection pool code so that the beans work properly
in the EJB transaction context. Is my only option to choose a isolation
level that allows dirty reads?
How do I set the isolation level in my jboss configuration? (Since the JBOSS
web site is down, I can't look at the docs)
Do I have to do it manually via the Connection setTransactionIsolation
method any time I lookup a connection?
What if I have a mix of BMP, CMP, and (horror) SQL in a SessionBean?
Thanks
Dave
-----Original Message-----
From: Nortje, Andrew [mailto:[EMAIL PROTECTED]]
Sent: Thursday, January 18, 2001 10:20 AM
To: 'jBoss'
Subject: RE: [jBoss-User] BMP and Container Managed Transactions was "Find
er Methods are sl ower when nothing is returned"
Dave
I am doing something similar to what you are and it works after much
struggling i.e. I create and use beans under a single transaction context.
If something fails created rows are rolled back etc.
Anyway I recognize the timeout error, I also had this error. It turned out I
was making reentrant calls to my entity beans and they were not marked
reentrant. You may have a similar problem. Try make your entity beans
reentrant (ejb-jar.xml) then test your code. If it then works then you are
making reentrant calls, you can then take it from there.
Also make sure your create() method correctly populates all the bean data
(attributes), i.e. after create() the bean instance is taken out the pool
and is assigned.
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
List Help?: [EMAIL PROTECTED]
