Michael,
In your jboss conf directory where your jboss.jcml file is in, i.e.
.../jboss/conf/default edit standardjboss.xml
Search for Standard BMP EntityBean.
Under that selection set <resizer-period> to 0. Also make sure that the
<max-capacity> is much over 106. If you want to know what that is, go check
it out in the docs. Basically I'm trying to figure out if the cache size
has anything to do with this problem.
Can you send me the loop that creates the beans? Can you reproduce this in
a simpler example so I can run and test this on my machine? Are you
positively sure that you're not trying to create a bean with the same
primary key? Are you doing all these creates inside 1 transaction(i.e.
Inside a Statefull/less session bean method?)
I need more info.
Bill
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Maraya
> Michael
> Sent: 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 which
> commit-option that is resolved as. I guess as a last resort, I can use a
> custom configuration but I'd like to make this work if I can.
>
> No other actions are performed during the creates, it's just one
> long series (1242 to be exact) of create calls inside a ResultSet
> loop. And
> the funny thing is, it always fails at 106 (I've sorted the input data in
> the hopes that it's bad data but I still get the problem).
>
> <jboss>
> <resource-managers>
> <resource-manager res-class="org.jboss.ejb.deployment.JDBCResource">
> <res-name>jdbc/Emps</res-name>
> <res-jndi-name>java:/Common</res-jndi-name>
> </resource-manager>
> </resource-managers>
> <enterprise-beans>
> <entity>
> <ejb-name>Account</ejb-name>
> <jndi-name>emps/account</jndi-name>
> <configuration-name>Standard BMP EntityBean</configuration-name>
> <resource-ref>
> <res-ref-name>jdbc/Emps</res-ref-name>
> <resource-name>jdbc/Emps</resource-name>
> </resource-ref>
> </entity>
> </enterprise-beans>
> </jboss>
>
> ---
> Michael R. Maraya
>
> > ----------
> > From: 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 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 information before I can help. The stack
> trace below
> > is only an effect, not a cause. Are you doing the same sort of thing in
> > the
> > message you posted?
> >
> > Regards,
> > Bill
> >
> >
>
> _______________________________________________
> 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
