Does your bean's ejbCreate return a proper primary key?
Richard Conway wrote:
> I too am experiencing this problem. I get...
>
> [DelegateAccountEJBean] java.lang.IllegalStateException: INSERTING AN
> ALREADY EXISTING BEAN, ID = o18 a0
> pa16087
>
> ... when the EJBs create method is called.
>
> The third parameter in the primary key (pa=16087) is obtained as the nextval
> from an Oracle sequence before each call to create. Therefore I cannot
> conceive how a bean with that id already exists. Also I checked the Oracle
> sequence by hand and the values being used are as expected.
>
> Also the problem only occurs after the container has been running for a few
> hours. If I stop and restart the container then I can successfully execute
> the create method of the EJB.
>
> Since I am not the only one seeing this problem (there are quite a few
> messages on this subject in the archive) - can someone confirm that this is
> a bug.
>
> I have recently upgraded from 2.0 FINAL to 2.2.1 and have only noticed the
> problem since the upgrade.
>
> Is 2.2.1 a stable release since there seem to be a number of serious issues
> with it.
>
> Any help/advice much appreciated.
>
> Richard.
>
> _______________________________________________
> JBoss-user mailing list
> [EMAIL PROTECTED]
> http://lists.sourceforge.net/lists/listinfo/jboss-user
>
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user
