You can call the MBean from the JMX Console. Look in
the domain jboss.j2ee and look for the mbean that is
named something like jndiName=,plugin=cache,service=EJB. Click on it and there
is an operation called flush().
You can do it programatically using the RMIAdaptor as
well.
This strategy has worked really well for us. We have
our app server aggresively caching in EJBs, but we
have one app where reference data is maintianed,
directly to the database. After each operation in the
app, we flush the cache for the specific bean.
//Nicholas
--- Frank Morton <[EMAIL PROTECTED]> wrote:
> I'm using 3.2.2 in production with commit option A.
> Every now
> and then I'd like to do some SQL directly on the
> database,
> but doing so would get the cached entity bean
> content
> out of sync with the data.
>
> Usually it is with database content that I know is
> not being
> modified elsewhere (or I'm willing to take the
> risk). So, what
> I'd like to do is run the SQL and then somehow flush
> the
> caches, forcing the change to be loaded next time it
> is
> needed.
>
> Any way to do this with commit option A?
>
>
>
>
---
> This SF.net email is sponsored by OSDN's Audience
> Survey.
> Help shape OSDN's sites and tell us what you think.
> Take this
> five minute survey and you could win a $250 Gift
> Certificate.
> http://www.wrgsurveys.com/2003/osdntech03.php?site=8
> ___
> JBoss-user mailing list
> [EMAIL PROTECTED]
>
https://lists.sourceforge.net/lists/listinfo/jboss-user
=
Nicholas Whitehead
Home: (973) 377 9335
Cell: (201) 615 2716
[EMAIL PROTECTED]
Get Your News From The Crowbar: http://crowbar.dnsalias.com:443/crowbar/
---
This SF.net email is sponsored by OSDN's Audience Survey.
Help shape OSDN's sites and tell us what you think. Take this
five minute survey and you could win a $250 Gift Certificate.
http://www.wrgsurveys.com/2003/osdntech03.php?site=8
___
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user
