: RE: [JBoss-user] INSERTING AN ALREADY EXISTING BEAN
We're calling remove on the bean itself. As for the hashCode and equals,
I thought that might be part of the problem, but they seem to be ok.
Although, I modified hashCode() in my primary key to print something out
when called and we don't
-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]
Sent: Wednesday, May 29, 2002 11:24 AM
To: [EMAIL PROTECTED]
Subject: RE: [JBoss-user] INSERTING AN ALREADY EXISTING BEAN
OK, mea culpa. All of our primary keys inherit from an abstract class
that deals with cacheing
Burke [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Wednesday, May 29, 2002 9:45 AM
Subject: RE: [JBoss-user] INSERTING AN ALREADY EXISTING BEAN
That's because JBoss used to handle primary keys differently. Before, PKs
were wrapped in a JBoss object called CacheKey. The CacheKey helped out
when
I can't remember, but I think there was a bug fixed in 2.4.6 regarding
home.remove.
I've also debugged problems from people where they have implemented their
primary key's wrong. Are you sure you have implemented hashCode and equals
correctly on your PrimaryKey class?
-Original
There are known problems with xdoclet generating invalid hashCode
methods in primary keys. Validate that your keys are correctly
implementing hashCode and equals and that they serialize and
unserialize correctly.
Scott Stark
Chief Technology Officer
JBoss Group, LLC
thanks
eric
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]
Sent: Tuesday, May 28, 2002 6:57 PM
To: [EMAIL PROTECTED]
Subject: RE: [JBoss-user] INSERTING AN ALREADY EXISTING BEAN
I can't remember, but I think there was a bug fixed in 2.4.6
: Tuesday, July 10, 2001 6:13 PM
To: '[EMAIL PROTECTED]'
Subject: RE: [JBoss-user] INSERTING AN ALREADY EXISTING BEAN.
problem
Thanks for replying, Bill.
I'm using JBoss 2.2.2 and the Entity Bean is configured as a
Standard BMP EntityBean (see jboss.xml below) -- I don't know
: Bill Burke[SMTP:[EMAIL PROTECTED]]
Sent: Wednesday, July 11, 2001 10:34 AM
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: RE: [JBoss-user] INSERTING AN ALREADY EXISTING BEAN.
problem
Michael,
In your jboss conf directory where your jboss.jcml file is in, i.e
-Original Message-
From: Maraya Michael [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, July 11, 2001 12:10 PM
To: [EMAIL PROTECTED]; 'Bill Burke'
Subject: RE: [JBoss-user] INSERTING AN ALREADY EXISTING BEAN.
problem
Thanks for the suggestions, Bill. Here's what happened
Bill,
I tried increasing the resizer-period to 6000 (10 minutes) so that
the cache wouldn't resize during the load and that seems to have sidestepped
the problem. I was able to load a total of 9919 records with no INSERTING
AN ALREADY EXISTING BEAN errors.
I think it's
Michael,
What version of JBoss are you running? 2.2.x, 2.4Beta, or 2.5 mainline?
What commit Option? A, B, or C?
Also what kind of things are you doing(get/sets, creates, removes)? And are
you doing them in one transaction? You definately have a corrupted cache
here and I need more
: Bill Burke[SMTP:[EMAIL PROTECTED]]
Reply To: [EMAIL PROTECTED]
Sent: Tuesday, July 10, 2001 5:42 PM
To: [EMAIL PROTECTED]
Subject: RE: [JBoss-user] INSERTING AN ALREADY EXISTING BEAN.
problem
Michael,
What version of JBoss are you running? 2.2.x, 2.4Beta, or 2.5
Ulp !
yes, the problem exists and no, iv'e no fix on it yet.
What is exactly the problem ? I probably missed it...
Do you have a simple test that fails ?
Simon
I said for some weeks ago that i would take on it but there
hasn't been any time for it yet :-(
/Lennart
Hey Martin
Hi,
I recently upgraded from JBoss 2.0 Final to Jboss 2.2.1.
Everything works as
expected but now I get a IllegalStateException when creating
entity beans.
If I wait some minutes after creation and try to create the next bean
everything works. I searched the mailing list
14 matches
Mail list logo
