Thanks Burkhard!
I changed all every setting in the <cache-policy-conf> to 1 (except for
cache-load-factor...I left it at 0.75) and my beans are now being refreshed
(close-to-real-time). I know this will be bad performance, but I get the
desired effect for integrating a J2EE application with a VB application.
What's curious is that simply setting commit-option to 'C' did not work. By
definition, I thought that would bypass caching for my CMP-entity bean. The
definition for option 'C' states:
Option C: The container does not cache bean instances and instances memory
state is synchronized on every transaction start (via ejbLoad). For business
methods executing outside a transaction the synchronization is done too, but
as the ejbLoad executes in the same transaction context as the triggering
business method, the state must still be considered invalid and might
already have changed in the persistent storage when the business method
executes.
I'm using the LRUEnterpriseContextCachePolicy and I also set all my
session-bean cache parameters equal to 1. Just a heads up for anyone else
out there thinking about doing something like this.
-Frank
> -----Original Message-----
> From: Burkhard Vogel [mailto:[EMAIL PROTECTED]]
> Sent: Monday, June 18, 2001 10:52 AM
> To: [EMAIL PROTECTED]
> Subject: Re: [JBoss-user] HOW TO DISABLE ENTITY-BEAN CACHING?
>
>
> Use 1.
> ----- Original Message -----
> From: "Frank Villarreal" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Friday, June 15, 2001 4:52 PM
> Subject: RE: [JBoss-user] HOW TO DISABLE ENTITY-BEAN CACHING?
>
>
> > K.V. Vinay Menon [mailto:[EMAIL PROTECTED]] wrote :
> > > For what its worth did you try changing the following section in
> > > standardjboss.xml
> > >
> > > <cache-policy-conf>
> > > <min-capacity>50</min-capacity>
> > > <max-capacity>1000</max-capacity>
> > > <overager-period>300</overager-period>
> > > <max-bean-age>600</max-bean-age>
> > > <resizer-period>400</resizer-period>
> > >
> > <max-cache-miss-period>60</max-cache-miss-period>
> > >
> > <min-cache-miss-period>1</min-cache-miss-period>
> > > <cache-load-factor>0.75</cache-load-factor>
> > > </cache-policy-conf>
> > >
> > > to set min/max-capacity to 0?
> > >
> > > Vinay
> >
> > Thanks Vinay, but I tried setting the min/max capacity to 0 and it
> resulted
> > in the following jboss startup exception...
> >
> > <exception>
> > [Container factory] org.jboss.ejb.DeploymentException:
> Can't import policy
> > configuration, Cause:org.jboss.ejb.DeploymentException: Min
> cache capacity
> > can't be <= 0
> > [Container factory] at
> >
> org.jboss.ejb.plugins.AbstractInstanceCache.importXml(Abstract
> InstanceCache.
> > java:311)
> > [Container factory] at
> >
> org.jboss.ejb.ContainerFactory.createInstanceCache(ContainerFa
> ctory.java:762
> > )
> > [Container factory]
> > </exception>
> >
> > Any other ideas?
> >
> > - Frank
> >
> > _______________________________________________
> > 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
>
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user
