Does anyone at JBoss want to comment on this bug?
I can supply a test case that replicates it.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3875260#3875260
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3875260
--
http://jira.jboss.com/jira/browse/JBAS
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3875277#3875277
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3875277
---
SF em
OK,
I've have managed to write a generic test case that can be used to prove that a
CMP entity's attributes are rendered empty by the Commit Option D refresh
thread even if you do not call the a find() method a second time.
Using a simple servlet (for want of a better way to talk to the EJBs) I
Actually I managed to reproduce the problem even after removing the
relationship (i.e. only setting fields that were not part of the relationship),
so this is not the reason at all. Please ignore my last post.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=387
I've reviewed our code and the problem is occuring because we are defining the
properties of an Entity as a one-to-many relationship between the Entity CMP
bean and EntityProperty CMP beans:
|
|
| Order-OrderProperty
|
|
property-associated-with-order
Brilliant, thankyou!
I will go and examine our code and find out if & where the finder is being
called again within the transaction that is persisting to the database.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3874057#3874057
Reply to the post :
http:/
I guess, your problem is this
http://jira.jboss.com/jira/browse/JBAS-979
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3873942#3873942
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3873942
Yes.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3873936#3873936
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3873936
---
SF email is sponsored by - The IT Produc
Does anyone from JBoss actually read these forums?
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3873901#3873901
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3873901
-
I too am having this problem.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3845071#3845071
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3845071
---
SF.Net email i
I don't see it in a simple testcase. Any more info/instructions?
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3843148#3843148
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3843148
Numerous posts about this. Even a bug report regarding memory leaks, fixed in 3.2.4.
I have upgrade from 3.2.2 to 3.2.5 Using the same config as davidmboon. CMP1.1 EJBs
with commit option C. Jboss continues to report "Unable to passivate due to ctx
lock". I have found little help in the do
We only get these warnings when we extend a container, if we leave the container
configuration blank the jboss.xml, which means we're using 'Standard CMP EntityBean'
container, we don't get these warnings.
However when I extend the 'Standard CMP EntityBean' container, I also get these
wranings.
Hi..
Same problem CTX lock is occuring when working with jboss3.2.1..
Did anybody find any solution to this ..
any solution .. for this please let me know..
thanks..
Madhu
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3825627#3825627";>View
the original post
http://www.jboss.org/
14 matches
Mail list logo
