TK> If your EJB is not the only thing that will be updating a table then you TK> have to deploy the ejb with "exclusive-write-access=false" in the TK> orion-ejb-jar.xml. Checkout the documentation on the orion-ejb-jar.xml at TK> http://www.orionserver.com/docs/orion-ejb-jar.xml.html TK> <http://www.orionserver.com/docs/orion-ejb-jar.xml.html> . This basically TK> turns off caching off the EJB.
Thank you for answer, but I don't want to turn off caching. I need exactly to manage it. EJB caching is rather usefull feature and I don't want to refuse completely from using it. TK> -----Original Message----- TK> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] TK> Sent: Friday, November 16, 2001 11:07 AM TK> To: Orion-Interest TK> Subject: RE: EJB pool management TK> I am sure there is a way, it is just not documented as the orionconsole.jar TK> has provisions for invalidating the pools, and adjusting their sizes. TK> it will probably be an ormi: call of some sort? TK> -----Original Message----- TK> From: Sergey G. Aslanov [ mailto:[EMAIL PROTECTED] TK> <mailto:[EMAIL PROTECTED]> ] TK> Sent: Friday, November 16, 2001 6:38 AM TK> To: Orion-Interest TK> Subject: EJB pool management TK> Hi all TK> Who knows, can I manage Orion's EJB instances pool from code? For example, TK> if data in DBMS was changed without help of EJB and I want to update TK> it in pool. What have I to do? -- Sergey G. Aslanov CBOSS Group, Web-technologies department mailto:[EMAIL PROTECTED] tel: +7 095 7555655
