RE: Where is the log file?
How about the log for EntityBean container to the SQL database? Is there any log containing the SQL statement that orion container sends to teh database? Thanks Andrew -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Markus Holmberg Sent: Friday, April 06, 2001 8:05 AM To: Orion-Interest Cc: Orion-Interest Subject: Re: Where is the log file? In "orion/application-deployments/yourapp/application.log". Regards, Markus. On Thu, Apr 05, 2001 at 06:33:21PM +0200, Muly Oved wrote: > Hi > > My Servlet raise an exception during the init() where can I find the log > file containing the call stack? do I need to turn on some parameter? -- Markus Holmberg | Give me Unix or give me a typewriter. [EMAIL PROTECTED] | http://www.freebsd.org/
schema-clustering
I am in the process of implementing our CMP EJB cluster using Orion 1.5.2. However, I couldn't find any documentation detailing how to do this. Orion 1.5.2 claims support for EJB clustering, I think it is primary aimed to solve the CMP Entity EJB cache sync problem. Howeve, as you might have noticed, there is no documentation whatsoever. There is a new feature called schema-clustering, and searching thru their entire document tree, their support website and the whole net only turns back one sentence... clustering-schema - The name of the data-source used if using container-managed persistence. This is a new tag used in the orion-ejb.jar.xml at deployment time. I think it is used to tell all the CMP Entity EJB server to map to the same data source and the whenever their data in cache change, a async message is broadcast to everyone in the cluster. Any server receiving the message should invalidate that data in their cache and reload it fresh from the database the next time that data is referenced. Please correct me if my assumption here is wrong. Does anyone have more info on this? Thank you very much in advance. Andrew
RE: problem with looking up the same EJB from different servers
There is a flag you need to set to make it look up from remote server. It is hidden somewhere in the javadoc... -Original Message-From: Ville Rinne [mailto:[EMAIL PROTECTED]]Sent: Thursday, July 26, 2001 1:17 AMTo: Orion-InterestSubject: problem with looking up the same EJB from different servers Hi, We've recently changed to orion and my problem now is that I have an application that looks up an EJB from one of our orion servers and does some things with it. Everything works fine whilst I'm using a single server, but I am unable to fetch the same EJB from a different server. I have a method that creates an InitialContext and does all the work and then just returns. Now this method works fine the first time for example for server A, but then when I call it again to do the same work for server B I still get the handle to the EJB on server A even though I've created a new InitalContext and set all the parameters to match server B. So obviously the properties I am giving to my InitialContext are not getting flushed between calls to my method or something, any ideas about this ? If I quit my program in between the EJB-lookups everything works fine naturally. cheers, Ville Rinne
porting from orion to oc4j, error message with CMP EJB
We have an J2EE application written originally to run on Orion 1.4.5. We have decided to try to port this to oc4j and the version we are using is 1.0.2.2 There is some minor reconfiguration issue but nothing really major. All the servlet, jsp, and stateless session EJB runs without any problem. However, all the CMP EntityBean doesn't seem to like their new home. During deployment, the container will complaints about every single EntityBean with error message like the following: JavaApplication_EntityBeanWrapper33.java:358: Exception java.sql.SQLException is never thrown in the body of the corresponding try statement. catch(java.sql.SQLException e) JavaApplication is one of our CMP EntityBean and the Wrapper is supposingly created automatically by the container at deployment time. Has anyone encountered this before? Any work around/solutions? Thanks in advance Andrew
RE: porting from orion to oc4j, error message with CMP EJB
It turns out there are some compatibility issues with the old orion-ejb-jar.xml and the new one and once we fixed those, the error went away. -Original Message- From: Andrew Chau Sent: Tuesday, August 21, 2001 3:41 PM To: Orion-Interest Subject: porting from orion to oc4j, error message with CMP EJB We have an J2EE application written originally to run on Orion 1.4.5. We have decided to try to port this to oc4j and the version we are using is 1.0.2.2 There is some minor reconfiguration issue but nothing really major. All the servlet, jsp, and stateless session EJB runs without any problem. However, all the CMP EntityBean doesn't seem to like their new home. During deployment, the container will complaints about every single EntityBean with error message like the following: JavaApplication_EntityBeanWrapper33.java:358: Exception java.sql.SQLException is never thrown in the body of the corresponding try statement. catch(java.sql.SQLException e) JavaApplication is one of our CMP EntityBean and the Wrapper is supposingly created automatically by the container at deployment time. Has anyone encountered this before? Any work around/solutions? Thanks in advance Andrew
RE: CMP 2.0 vs BMP - Which performes better?
If performance is the only factor, BMP performs a million times faster than CMP. Well, may be not that much faster, but you get the point. CMP is for ease of development, basically the container does all the work for you, but it is not as flexible and you cannot fine tune the query like you can do in BMP. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Orion Newsgroup Sent: Thursday, March 28, 2002 2:40 PM To: Orion-Interest Subject: CMP 2.0 vs BMP - Which performes better? Subject: CMP 2.0 vs BMP - Which performes better? From: "alt.cybercafes" <[EMAIL PROTECTED]> === I am in the process of building a database intensive app and wanted to know whether to use container manage persistance versus bean manage persistence for this database instensive application. What are the pros and cons of CMP and BMP.? thanks
