Bugs item #889312, was opened at 2004-02-02 13:45 Message generated for change (Settings changed) made by starksm You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=889312&group_id=22866
Category: JBossServer Group: v3.2 >Status: Closed >Resolution: Invalid Priority: 5 Submitted By: Steve Wolfangel (swolfangel) >Assigned to: Scott M Stark (starksm) Summary: Error looking up bean from war file. Initial Comment: I am getting the following exception when I try to lookup a bean from a separately deployed ear file. 15:28:26,359 ERROR [LogInterceptor] EJBException: javax.ejb.EJBException: Invalid invocation, check your deployment packaging, method=public abstract com.metamatrix.platform.security.api.LogonAPI com.metamatrix .platform.security.api.LogonAPIHome.create() throws javax.ejb.CreateException,java.rmi.RemoteException I am able to lookup and communicate with the bean from an external client but get this exception when looking up from a servlet. I have searched the newsgroups and found others with a similar problem but have not found a solution. Is this a bug or a packaging issue? I can send my ear and war files if need be. They are too big to attache. Regards, Steve Wolfangel Starting JBoss (MX MicroKernel)... Release ID: JBoss [WonderLand] 3.2.3 (build: CVSTag=JBoss_3_2_3 date=200311301445) Home Dir: D:\jb32\server\jboss Home URL: file:/D:/jb32/server/jboss/ Library URL: file:/D:/jb32/server/jboss/lib/ Patch URL: null Server Name: metamatrix Server Home Dir: D:\jb32\server\jboss\server\metamatrix Server Home URL: file:/D:/jb32/server/jboss/server/metamatrix/ Server Data Dir: D:\jb32 \server\jboss\server\metamatrix\data Server Temp Dir: D:\jb32 \server\jboss\server\metamatrix\tmp Server Config URL: file:/D:/jb32/server/jboss/server/metamatrix/conf/ Server Library URL: file:/D:/jb32/server/jboss/server/metamatrix/lib/ Root Deployment Filename: jboss-service.xml Starting General Purpose Architecture (GPA)... Java version: 1.4.2,Sun Microsystems Inc. Java VM: Java HotSpot(TM) Client VM 1.4.2-b28,Sun Microsystems Inc. OS-System: Windows XP 5.1,x86 ---------------------------------------------------------------------- >Comment By: Scott M Stark (starksm) Date: 2004-02-08 15:03 Message: Logged In: YES user_id=175228 This occurs when the cleint ear has the ejb-classes duplicated within its deployment and is doing call be reference into the second ear ejb layer. Your work around has isolated the two deployment class loaders using call by value semantics and will incur the overhead of marshalling the call between the two containers. The common client interfaces would have to factored out to a shared class loader (for example default/lib) to use call by reference. ---------------------------------------------------------------------- Comment By: Steve Wolfangel (swolfangel) Date: 2004-02-04 11:15 Message: Logged In: YES user_id=541224 I was able to get around this problem by replacing org.jboss.invocation.InvokerInterceptor with org.jboss.invocation.ByValueInvokerInterceptor in standardjboss.xml in the conf dir. My question now is, is this the correct fix? Will this affect performance when connecting from outside the appserver? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=889312&group_id=22866 ------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn _______________________________________________ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
