On Sat, Mar 20, 2004 at 01:59:02PM -0600, [EMAIL PROTECTED] wrote: > ----- Forwarded message from Michael Forster <[EMAIL PROTECTED]> ----- > > I am ripping my hair out here,
Hopefully we can put a stop to that :) > I have a jar file full of ejb's deployed on a test server fine, everything > works as it should. > > I now want to deploy it to the live server - Everything is configured the > same - the same JVM installed mysql in the background and I literally copy > en toto the whole openejb stricture to the live server, You should be good, but the comment you make later about log4j complaining makes me think maybe your OPENEJB_HOME variable is buggy on the second machine. Something to check. > I run the server up, the system activates and comes to full readiness. > It does not respond to requests from the Tomcat server on another machine. > I have several small errors that occur even on the old jar file (the same sw > basically but with some new files added in the appropriate areas but not > currently called) > > With the first one when tomcat calls it calls for an instance of the > SessionManagerBean > a Stateless Session bean which acts as a facade to the rest of the beans. > > When I try to get the session bean Tomcat complains with a Cannot get > /SessionManagerBean > > Open EJB complains with > > WARN : The following method doesn't have a transaction policy assigned: > public abstract com.ingotz.j2ee.ejb.SessionManager > com.ingotz.j2ee.ejb.SessionManagerHome.create() throws > java.rmi.RemoteException,javax.ejb.CreateException This is ok, not specifying a tx attribute is fine. Whenever you see one of these, OpenEJB should default to Supports. > ERROR: The bean instances business method encountered a system > exception:object is not an instance of declaring class > java.lang.IllegalArgumentException: object is not an instance of declaring > class > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [snip] > org.openejb.alt.containers.castor_cmp11.CastorCMP11_EntityContainer.createEJ > BObject(CastorCMP11_EntityContainer.java:803) This is the part that is really crazy. It looks like somehow the SessionManager is getting deployed as a CMP bean. If this is true, fixing this should be easy. When the server starts up, it prints a bunch of messages to the openejb.log file followed by "OpenEJB ready." Post all that text. -David
