HowTo talk to a Session bean from an Applet sample app. problem

Hi!
When I push the "Call EJB" button in the sample application I get the following exception:
2005.02.20. 15:49:27 com.evermind.server.rmi.RMIClient createRemoteInvocationHandlerFactory
WARNING: com.evermind.server.ejb.EJBRemoteInvocationHandlerFactory
java.lang.ClassNotFoundException: com.evermind.server.ejb.EJBRemoteInvocationHandlerFactory
     at sun.applet.AppletClassLoader.findClass(Unknown Source)
     at java.lang.ClassLoader.loadClass(Unknown Source)
     at sun.applet.AppletClassLoader.loadClass(Unknown Source)
     at java.lang.ClassLoader.loadClass(Unknown Source)
     at java.lang.ClassLoader.loadClassInternal(Unknown Source)
     at java.lang.Class.forName0(Native Method)
     at java.lang.Class.forName(Unknown Source)
     at com.evermind.server.rmi.RMIClient.createRemoteInvocationHandlerFactory(RMIClient.java:427)
     at com.evermind.server.rmi.RMIClient.initHandlerFactories(RMIClient.java:415)
     at com.evermind.server.rmi.RMIClient.<init>(RMIClient.java:61)
     at com.evermind.server.rmi.RMIClient.getInstance(RMIClient.java:464)
     at com.evermind.server.rmi.RMIInitialContext.<clinit>(RMIInitialContext.java:48)
     at oracle.j2ee.rmi.RMIInitialContextFactory.getInitialContext(RMIInitialContextFactory.java:58)
     at javax.naming.spi.NamingManager.getInitialContext(Unknown Source)
     at javax.naming.InitialContext.getDefaultInitCtx(Unknown Source)
     at javax.naming.InitialContext.init(Unknown Source)
     at javax.naming.InitialContext.<init>(Unknown Source)
     at oracle.otnsamples.EJBCaller.getInitialContext(Unknown Source)
     at oracle.otnsamples.EJBCaller.callEjb(Unknown Source)
     at oracle.otnsamples.EJBCaller.access$000(Unknown Source)
     at oracle.otnsamples.EJBCaller$2.actionPerformed(Unknown Source)
     at javax.swing.AbstractButton.fireActionPerformed(Unknown Source)
     at javax.swing.AbstractButton$ForwardActionEvents.actionPerformed(Unknown Source)
     at javax.swing.DefaultButtonModel.fireActionPerformed(Unknown Source)
     at javax.swing.DefaultButtonModel.setPressed(Unknown Source)
     at javax.swing.plaf.basic.BasicButtonListener.mouseReleased(Unknown Source)
     at java.awt.Component.processMouseEvent(Unknown Source)
     at java.awt.Component.processEvent(Unknown Source)
     at java.awt.Container.processEvent(Unknown Source)
     at java.awt.Component.dispatchEventImpl(Unknown Source)
     at java.awt.Container.dispatchEventImpl(Unknown Source)
     at java.awt.Component.dispatchEvent(Unknown Source)
     at java.awt.LightweightDispatcher.retargetMouseEvent(Unknown Source)
     at java.awt.LightweightDispatcher.processMouseEvent(Unknown Source)
     at java.awt.LightweightDispatcher.dispatchEvent(Unknown Source)
     at java.awt.Container.dispatchEventImpl(Unknown Source)
     at java.awt.Component.dispatchEvent(Unknown Source)
     at java.awt.EventQueue.dispatchEvent(Unknown Source)
     at java.awt.EventDispatchThread.pumpOneEventForHierarchy(Unknown Source)
     at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)
     at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
     at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
     at java.awt.EventDispatchThread.run(Unknown Source)
Caused by: java.io.IOException: open HTTP connection failed.
     at sun.applet.AppletClassLoader.getBytes(Unknown Source)
     at sun.applet.AppletClassLoader.access$100(Unknown Source)
     at sun.applet.AppletClassLoader$1.run(Unknown Source)
     at java.security.AccessController.doPrivileged(Native Method)
     ... 43 more
javax.naming.NamingException: Lookup error: java.net.ConnectException: Connection refused: connect; nested exception is:
     java.net.ConnectException: Connection refused: connect [Root exception is java.net.ConnectException: Connection refused: connect]
     at com.evermind.server.rmi.RMIContext.lookup(RMIContext.java:183)
     at javax.naming.InitialContext.lookup(Unknown Source)
     at oracle.otnsamples.EJBCaller.callEjb(Unknown Source)
     at oracle.otnsamples.EJBCaller.access$000(Unknown Source)
     at oracle.otnsamples.EJBCaller$2.actionPerformed(Unknown Source)
     at javax.swing.AbstractButton.fireActionPerformed(Unknown Source)
     at javax.swing.AbstractButton$ForwardActionEvents.actionPerformed(Unknown Source)
     at javax.swing.DefaultButtonModel.fireActionPerformed(Unknown Source)
     at javax.swing.DefaultButtonModel.setPressed(Unknown Source)
     at javax.swing.plaf.basic.BasicButtonListener.mouseReleased(Unknown Source)
     at java.awt.Component.processMouseEvent(Unknown Source)
     at java.awt.Component.processEvent(Unknown Source)
     at java.awt.Container.processEvent(Unknown Source)
     at java.awt.Component.dispatchEventImpl(Unknown Source)
     at java.awt.Container.dispatchEventImpl(Unknown Source)
     at java.awt.Component.dispatchEvent(Unknown Source)
     at java.awt.LightweightDispatcher.retargetMouseEvent(Unknown Source)
     at java.awt.LightweightDispatcher.processMouseEvent(Unknown Source)
     at java.awt.LightweightDispatcher.dispatchEvent(Unknown Source)
     at java.awt.Container.dispatchEventImpl(Unknown Source)
     at java.awt.Component.dispatchEvent(Unknown Source)
     at java.awt.EventQueue.dispatchEvent(Unknown Source)
     at java.awt.EventDispatchThread.pumpOneEventForHierarchy(Unknown Source)
     at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)
     at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
     at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
     at java.awt.EventDispatchThread.run(Unknown Source)
Caused by: java.net.ConnectException: Connection refused: connect
     at java.net.PlainSocketImpl.socketConnect(Native Method)
     at java.net.PlainSocketImpl.doConnect(Unknown Source)
     at java.net.PlainSocketImpl.connectToAddress(Unknown Source)
     at java.net.PlainSocketImpl.connect(Unknown Source)
     at java.net.Socket.connect(Unknown Source)
     at java.net.Socket.connect(Unknown Source)
     at java.net.Socket.<init>(Unknown Source)
     at java.net.Socket.<init>(Unknown Source)
     at com.evermind.server.rmi.RMIClientConnection.connect(RMIClientConnection.java:394)
     at com.evermind.server.rmi.RMIClientConnection.lookup(RMIClientConnection.java:80)
     at com.evermind.server.rmi.RMIClient.lookup(RMIClient.java:250)
     at com.evermind.server.rmi.RMIContext.lookup(RMIContext.java:154)
     ... 26 more
javax.naming.NamingException: Lookup error: java.net.ConnectException: Connection refused: connect; nested exception is:
     java.net.ConnectException: Connection refused: connect [Root exception is java.net.ConnectException: Connection refused: connect]
     at com.evermind.server.rmi.RMIContext.lookup(RMIContext.java:183)
     at javax.naming.InitialContext.lookup(Unknown Source)
     at oracle.otnsamples.EJBCaller.callEjb(Unknown Source)
     at oracle.otnsamples.EJBCaller.access$000(Unknown Source)
     at oracle.otnsamples.EJBCaller$2.actionPerformed(Unknown Source)
     at javax.swing.AbstractButton.fireActionPerformed(Unknown Source)
     at javax.swing.AbstractButton$ForwardActionEvents.actionPerformed(Unknown Source)
     at javax.swing.DefaultButtonModel.fireActionPerformed(Unknown Source)
     at javax.swing.DefaultButtonModel.setPressed(Unknown Source)
     at javax.swing.plaf.basic.BasicButtonListener.mouseReleased(Unknown Source)
     at java.awt.Component.processMouseEvent(Unknown Source)
     at java.awt.Component.processEvent(Unknown Source)
     at java.awt.Container.processEvent(Unknown Source)
     at java.awt.Component.dispatchEventImpl(Unknown Source)
     at java.awt.Container.dispatchEventImpl(Unknown Source)
     at java.awt.Component.dispatchEvent(Unknown Source)
     at java.awt.LightweightDispatcher.retargetMouseEvent(Unknown Source)
     at java.awt.LightweightDispatcher.processMouseEvent(Unknown Source)
     at java.awt.LightweightDispatcher.dispatchEvent(Unknown Source)
     at java.awt.Container.dispatchEventImpl(Unknown Source)
     at java.awt.Component.dispatchEvent(Unknown Source)
     at java.awt.EventQueue.dispatchEvent(Unknown Source)
     at java.awt.EventDispatchThread.pumpOneEventForHierarchy(Unknown Source)
     at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)
     at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
     at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
     at java.awt.EventDispatchThread.run(Unknown Source)
Caused by: java.net.ConnectException: Connection refused: connect
     at java.net.PlainSocketImpl.socketConnect(Native Method)
     at java.net.PlainSocketImpl.doConnect(Unknown Source)
     at java.net.PlainSocketImpl.connectToAddress(Unknown Source)
     at java.net.PlainSocketImpl.connect(Unknown Source)
     at java.net.Socket.connect(Unknown Source)
     at java.net.Socket.connect(Unknown Source)
     at java.net.Socket.<init>(Unknown Source)
     at java.net.Socket.<init>(Unknown Source)
     at com.evermind.server.rmi.RMIClientConnection.connect(RMIClientConnection.java:394)
     at com.evermind.server.rmi.RMIClientConnection.lookup(RMIClientConnection.java:80)
     at com.evermind.server.rmi.RMIClient.lookup(RMIClient.java:250)
     at com.evermind.server.rmi.RMIContext.lookup(RMIContext.java:154)
     ... 26 more
Thanks!

Refer to the following link for a list of tutorials that will guide you through the steps you have queried about: http://www.oracle.com/technology/tech/java/ejb30.html
Also, if you are attempting to call a session bean from your applet code you may run into firewall issues depending on your corporate infrastructure. RMI does not run over the ever popular port 80 and therefore is not always open on company firewalls. If you run into trouble you may have to use HTTP Tunneling. A better alternative maybe to call your session bean as a web service which is provided to you by default in the EJB 3.0 spec.

Similar Messages

Accessing the same stateful session bean from multiple clients in a clustered environment

I am trying to access the same stateful session bean from multiple
          clients. I also want this bean to have failover support so we want to
          deploy it in a cluster. The following description is how we have tried
          to solve this problem, but it does not seem to be working. Any
          insight would be greatly appreciated!
          I have set up a cluster of three servers. I deployed a stateful
          session bean with in memory replication across the cluster. A client
          obtains a reference to an instance of one of these beans to handle a
          request. Subsequent requests will have to use the same bean and could
          come from various clients. So after using the bean the first client
          stores the handle to the bean (actually the replica aware stub) to be
          used by other clients to be able to obtain the bean. When another
          client retrieves the handle gets the replica aware stub and makes a
          call to the bean the request seems to unpredictably go to any of the
          three servers rather than the primary server hosting that bean. If the
          call goes to the primary server everything seems to work fine the
          session data is available and it gets backed up on the secondary
          server. If it happens to go to the secondary server a bean that has
          the correct session data services the request but gives the error
          <Failed to update the secondary copy of a stateful session bean from
          home:ejb20-statefulSession-TraderHome>. Then any subsequent requests
          to the primary server will not reflect changes made on the secondary
          and vice versa. If the request happens to go to the third server that
          is not hosting an instance of that bean then the client receives an
          error that the bean was not available. From my understanding I thought
          the replica aware stub would know which server is the primary host for
          that bean and send the request there.
          Thanks in advance,
          Justin


          If 'allow-concurrent-call' does exactly what you need, then you don't have a problem,
          do you?
          Except of course if you switch ejb containers. Oh well.
          Mike
          "FBenvadi" <[email protected]> wrote:
          >I've got the same problem.
          >I understand from you that concurrent access to a stateful session bean
          >is
          >not allowed but there is a
          >token is weblogic-ejb-jar.xml that is called 'allow-concurrent-call'
          >that
          >does exactly what I need.
          >What you mean 'you'll get a surprise when you go to production' ?
          >I need to understand becouse I can still change the design.
          >Thanks Francesco
          >[email protected]
          >
          >"Mike Reiche" <[email protected]> wrote in message
          >news:[email protected]...
          >>
          >> Get the fix immediately from BEA and test it. It would be a shame to
          >wait
          >until
          >> December only to get a fix - that doesn't work.
          >>
          >> As for stateful session bean use - just remember that concurrent access
          >to
          >a stateful
          >> session bean is not allowed. Things will work fine until you go to
          >production
          >> and encounter some real load - then you will get a surprise.
          >>
          >> Mike
          >>
          >> [email protected] (Justin Meyer) wrote:
          >> >I just heard back from WebLogic Tech Support and they have confirmed
          >> >that this is a bug. Here is their reply:
          >> >
          >> >There is some problem in failover of stateful session beans when its
          >> >run from a java client.However, it is fixed now.
          >> >
          >> >The fix will be in SP2 which will be out by december.
          >> >
          >> >
          >> >Mike,
          >> >Thanks for your reply. I do infact believe we are correctly using
          >a
          >> >stateful session bean however it may have been misleading from my
          >> >description of the problem. We are not accessing the bean
          >> >concurrently from 2 different clients. The second client will only
          >> >come into play if the first client fails. In this case we want to
          >be
          >> >able to reacquire the handle to our stateful session bean and call
          >it
          >> >from the secondary client.
          >> >
          >> >
          >> >Justin
          >> >
          >> >"Mike Reiche" <[email protected]> wrote in message
          >news:<[email protected]>...
          >> >> You should be using an entity bean, not a stateful session bean
          >for
          >> >this application.
          >> >>
          >> >> A stateful session bean is intended to be keep state (stateful)
          >for
          >> >the duration
          >> >> of a client's session (session).
          >> >>
          >> >> It is not meant to be shared by different clients - in fact, if
          >you
          >> >attempt to
          >> >> access the same stateful session bean concurrently - it will throw
          >> >an exception.
          >> >>
          >> >> We did your little trick (storing/retrieving handle) with a stateful
          >> >session bean
          >> >> on WLS 5.1 - and it did work properly - not as you describe. Our
          >sfsb's
          >> >were not
          >> >> replicated as yours are.
          >> >>
          >> >> Mike
          >> >>
          >> >> [email protected] (Justin Meyer) wrote:
          >> >> >I am trying to access the same stateful session bean from multiple
          >> >> >clients. I also want this bean to have failover support so we want
          >> >to
          >> >> >deploy it in a cluster. The following description is how we have
          >tried
          >> >> >to solve this problem, but it does not seem to be working. Any
          >> >> >insight would be greatly appreciated!
          >> >> >
          >> >> >I have set up a cluster of three servers. I deployed a stateful
          >> >> >session bean with in memory replication across the cluster. A client
          >> >> >obtains a reference to an instance of one of these beans to handle
          >> >a
          >> >> >request. Subsequent requests will have to use the same bean and
          >could
          >> >> >come from various clients. So after using the bean the first client
          >> >> >stores the handle to the bean (actually the replica aware stub)
          >to
          >> >be
          >> >> >used by other clients to be able to obtain the bean. When another
          >> >> >client retrieves the handle gets the replica aware stub and makes
          >> >a
          >> >> >call to the bean the request seems to unpredictably go to any of
          >the
          >> >> >three servers rather than the primary server hosting that bean.
          >If
          >> >the
          >> >> >call goes to the primary server everything seems to work fine the
          >> >> >session data is available and it gets backed up on the secondary
          >> >> >server. If it happens to go to the secondary server a bean that
          >has
          >> >> >the correct session data services the request but gives the error
          >> >> ><Failed to update the secondary copy of a stateful session bean
          >from
          >> >> >home:ejb20-statefulSession-TraderHome>. Then any subsequent requests
          >> >> >to the primary server will not reflect changes made on the secondary
          >> >> >and vice versa. If the request happens to go to the third server
          >that
          >> >> >is not hosting an instance of that bean then the client receives
          >an
          >> >> >error that the bean was not available. From my understanding I
          >thought
          >> >> >the replica aware stub would know which server is the primary host
          >> >for
          >> >> >that bean and send the request there.
          >> >> >
          >> >> >Thanks in advance,
          >> >> >Justin
          >>
          >
          >

JNDI Naming Problem accessing Session Bean from Message Driven Bean

Hi,
     I am facing a very strange problem in JNDI look up accessing a Session Bean from a Message Driven Bean. I have a session fa�ade bean(Remote Bean) which is being called from Struts Action class getting the home reference from the ServiceLocator (I have implemented ServiceLocator pattern to obtain JNDI reference for all EJBs). When I am calling the session fa�ade EJB from the Struts Action class everything is working fine.
     But when I am trying to call the same EJB from my Message Driven Bean, I am getting a JNDI exception (NameNotFoundException - No Object bound to name �java:comp/env/ejb/EJBJNDIName�). I am trying to get the remote reference from the same ServiceLocator which is successfully providing me a reference while calling from the struts action class. But the same ServiceLocator is not able to provide me a reference while calling from the Message Driven Bean. If I use the JNDI name directly like �EJBJNDIName� in the lookup it is working fine. The lookup for the name is working fine and I am able to call the Session Fa�ade bean with that reference.
     I am really not sure what exactly the problem is. If I have any problem in the ServiceLocator, it should have given me the same error while calling from Struts Action class. But it is working fine with the full name �java:comp/env/ejb/EJBJNDIName� calling from the struts action class. I am not sure whether Message Driven Bean has something to do with it. Why I am not able to get a reference of the EJB with the full name? Please Help.
Thanks
Amit

Hi Bhagya,
Thanks for your response. I think from EJB container we can call Local EJBs with the full JNDI name. The session facade bean which is being called is a remote bean. From the session facade bean I am calling a local stateless session bean for database access. I am getting the reference of the local EJB from my session facade bean with full JNDI name "java:comp/env/ejb/EJBJNDIName". It is working fine with out any problem. My servicelocator is able to provide me the reference of the local EJB from the session facade remote bean with Full JNDI name. I am only having this problem calling from the MDB. I am really not sure whether what is causing it?
Thanks
Amit

How can i lookup a session bean from the client side

how can i lookup a session bean from the client side...........i am using sun appserver..............
this is my code.................[B]
private final static String JNDI_NAME="ejb/LmsBean";
private static String url="ldap://localhost:4848";
Hashtable h=new Hashtable();
h.put(Context.INITIAL_CONTEXT_FACTORY,"com.sun.jndi.ldap.LdapCtxFactory");
h.put(Context.PROVIDER_URL,url);
System.out.println("Before Loading Context in Delegate");
Context ctx=new InitialContext(h);
System.out.println("Loaded Context in Delegate");
Object obj=ctx.lookup(JNDI_NAME);
System.out.println("Loaded Object in Delegate");
System.out.println("Before Loading Home in Delegate");
LmsHome home = (LmsHome )PortableRemoteObject.narrow(obj,com.parx.lms.controller.LmsHome.class);
System.out.println("Loaded Home in Delegate");
lms = home.create();
System.out.println("Loaded remote in Delegate");
[B]and i got the exception........
Inside Client before calling delegate
Before Loading Context in Delegate
javax.naming.CommunicationException: Request: 1 cancelled
javax.naming.CommunicationException: Request: 1 cancelled
at com.sun.jndi.ldap.LdapRequest.getReplyBer(LdapRequest.java:60)
at com.sun.jndi.ldap.Connection.readReply(Connection.java:405)
at com.sun.jndi.ldap.LdapClient.ldapBind(LdapClient.java:340)
at com.sun.jndi.ldap.LdapClient.authenticate(LdapClient.java:171)
at com.sun.jndi.ldap.LdapCtx.connect(LdapCtx.java:2640)
at com.sun.jndi.ldap.LdapCtx.<init>(LdapCtx.java:290)
at com.sun.jndi.ldap.LdapCtxFactory.getUsingURL(LdapCtxFactory.java:175)
at com.sun.jndi.ldap.LdapCtxFactory.getUsingURLs(LdapCtxFactory.java:193
at com.sun.jndi.ldap.LdapCtxFactory.getLdapCtxInstance(LdapCtxFactory.ja
va:136)
at com.sun.jndi.ldap.LdapCtxFactory.getInitialContext(LdapCtxFactory.jav
a:66)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:6
62)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243
at javax.naming.InitialContext.init(InitialContext.java:219)
at javax.naming.InitialContext.<init>(InitialContext.java:195)
at com.parx.lms.lmsdelegate.LmsDelegate.getController(LmsDelegate.java:3
0)
at com.parx.lms.lmsdelegate.LmsDelegate.addUserDelegate(LmsDelegate.java
:50)
at com.parx.lms.client.consoleClient.Client.main(Unknown Source)
pls go tru the exception and pls help.........

That url string should be having the server name or ip instead of localhost.

Initialize a stateful session bean from another

Hi,
I am trying to create and initialize a stateful session bean from another stateful session bean. The code is as follows
This method belongs to DefaultSessionBean where it creates the AdminSessionBean based on few checks and returns it to the client.
    public AdminSession getAdminSession() throws UnknownException, WarningException {
        checkSessionUser("getAdminSession");
        if (isAdmin()) {
            AdminSession adminSession;
            try {
                final Context context = IToolsUtil.getInitialContext();
                adminSession = (AdminSession)context.lookup("AdminSession");
                System.out.println("Successfully created the adminsession bean");
            } catch (NamingException ne) {
                ne.printStackTrace();
                throw new UnknownException (new CatalogHelper("ITOOLS_100019", new Object[]{"Admin", ne.getMessage()}));
            System.out.println("adminsession will be returned");
            return adminSession;
        } else {
            throw new WarningException (new CatalogHelper("ITOOLS_000042", sessionUser.getUserhandle()));
    }Another method in DefaultSessionBean, creates its local interface and returns it.
    public DefaultSessionLocal getDefaultSessionLocal() {
        DefaultSessionLocal dsl = (DefaultSessionLocal)context.getBusinessObject(DefaultSessionLocal.class);
        System.out.println("local created.");
        return dsl;
    }Client call initialize method of the AdminSessionBean which is mentioned below:
    public void initialize(DefaultSession ds) throws WarningException, UnknownException {
        this.ds = ds.getDefaultSessionLocal();
        this.rfl = ReadFieldList.getInstance();
        this.fm = new FinderMethods();
    }The client code where it gets the adminSession and initializes is
   public static AdminSession getAdminSession(DefaultSession ds) throws ViewException {
        AdminSession as;
        try {
            as = ds.getAdminSession();
            System.out.println("got admin session");
        } catch (WarningException we) {
             we.printStackTrace();
            throw new ViewException(we.getCatalogHelper());
        } catch (UnknownException ue) {
            ue.printStackTrace();
            throw new ViewException(ue.getCatalogHelper());
        } catch (OracleRemoteException ore) {
            ore.printStackTrace();
            throw new ViewException(new CatalogHelper("ITOOLS_050003", ore.getMessage()));
        // Initialize Admin Session
        try {
            System.out.println("before getting it.");
            as.initialize(ds);
            System.out.println("adminsession is initialized");
        } catch (WarningException we) {
            as.remove();
            as = null;
            throw new ViewException(we.getCatalogHelper());
        } catch (UnknownException ue) {
            as.remove();
            as = null;
            throw new ViewException(ue.getCatalogHelper());
        } catch (OracleRemoteException ore) {
            as.remove();
            as = null;
            throw new ViewException(new CatalogHelper("ITOOLS_050003", ore.getMessage()));
        System.out.println("got admin session");
        return as;
    }Apart from this I am using OC4J 10.1.3.1 tool test my application.
When I am calling initialize method of the AdminSession I am getting the following error.
06/10/24 12:26:08 Entered
06/10/24 12:26:08 got default session
06/10/24 12:26:08 Successfully created the adminsession bean
06/10/24 12:26:08 adminsession will be returned
06/10/24 12:26:08 got admin session
06/10/24 12:26:08 before getting it.
2006-10-24 12:26:08.156 WARNING J2EE RMI-00009 Exception returned by remote server: {0}
06/10/24 12:26:08 com.itools.vs.view.exception.ViewException
06/10/24 12:26:08      at com.itools.vs.view.util.ViewUtil.getAdminSession(ViewUtil.java:71)
06/10/24 12:26:08      at com.itools.vs.view.backing.Admin.CreateUser.submit_action(CreateUser.java:182)
06/10/24 12:26:08      at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
06/10/24 12:26:08      at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
06/10/24 12:26:08      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
06/10/24 12:26:08      at java.lang.reflect.Method.invoke(Method.java:585)
06/10/24 12:26:08      at com.sun.faces.el.MethodBindingImpl.invoke(MethodBindingImpl.java:146)
06/10/24 12:26:08      at com.sun.faces.application.ActionListenerImpl.processAction(ActionListenerImpl.java:92)
06/10/24 12:26:08      at org.ajax4jsf.framework.ajax.AjaxActionComponent.broadcast(AjaxActionComponent.java:88)
06/10/24 12:26:08      at org.ajax4jsf.framework.ajax.AjaxViewRoot.processEvents(AjaxViewRoot.java:274)
06/10/24 12:26:08      at org.ajax4jsf.framework.ajax.AjaxViewRoot.broadcastEvents(AjaxViewRoot.java:250)
06/10/24 12:26:08      at org.ajax4jsf.framework.ajax.AjaxViewRoot.processApplication(AjaxViewRoot.java:405)
06/10/24 12:26:08      at com.sun.faces.lifecycle.InvokeApplicationPhase.execute(InvokeApplicationPhase.java:95)
06/10/24 12:26:08      at com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:245)
06/10/24 12:26:08      at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:110)
06/10/24 12:26:08      at javax.faces.webapp.FacesServlet.service(FacesServlet.java:213)
06/10/24 12:26:08      at com.evermind.server.http.ResourceFilterChain.doFilter(ResourceFilterChain.java:64)
06/10/24 12:26:08      at org.ajax4jsf.framework.ajax.xmlfilter.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:67)
06/10/24 12:26:08      at org.ajax4jsf.framework.ajax.xmlfilter.BaseFilter.doFilter(BaseFilter.java:223)
06/10/24 12:26:08      at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:621)
06/10/24 12:26:08      at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:368)
06/10/24 12:26:08      at com.evermind.server.http.HttpRequestHandler.doProcessRequest(HttpRequestHandler.java:866)
06/10/24 12:26:08      at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:448)
06/10/24 12:26:08      at com.evermind.server.http.HttpRequestHandler.serveOneRequest(HttpRequestHandler.java:216)
06/10/24 12:26:08      at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:117)
06/10/24 12:26:08      at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:110)
06/10/24 12:26:08      at oracle.oc4j.network.ServerSocketReadHandler$SafeRunnable.run(ServerSocketReadHandler.java:260)
06/10/24 12:26:08      at oracle.oc4j.network.ServerSocketAcceptHandler.procClientSocket(ServerSocketAcceptHandler.java:239)
06/10/24 12:26:08      at oracle.oc4j.network.ServerSocketAcceptHandler.access$700(ServerSocketAcceptHandler.java:34)
06/10/24 12:26:08      at oracle.oc4j.network.ServerSocketAcceptHandler$AcceptHandlerHorse.run(ServerSocketAcceptHandler.java:880)
06/10/24 12:26:08      at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303)
06/10/24 12:26:08      at java.lang.Thread.run(Thread.java:595)
06/10/24 12:26:08 ITOOLS_050003: Failed to get Admin Session.
Exception is "Error marshalling objects, Not Serializable: java.io.NotSerializableException: DefaultSession_RemoteProxy_6nein01; nested exception is:
     java.io.NotSerializableException: DefaultSession_RemoteProxy_6nein01".
[b/

Your remote client passes a DefaultSession to AdminSession.initialize(..). This DefaultSession has to be a remote type. In your client, how does it get DefaultSession?
Did your client look up DefaultSession, and have it return a (sessionContext.getBusinessObject(DefaultSession.class))? If so, it should work.

How can I set the value to a session bean from backing bean

Hi Experts,
How can I set the value to a session bean from backing bean where I have created getter and setter
methods for that variable.
Basically I am using ADFUtils class where I am able to get the value from session bean
using following expression
String claimType =
(String)ADFUtil.invokeEL("#{ClaimValueObj.getClaimType}");
Thanks
Gayaz

Gayaz,
Wrong Post !!
Post in JDeveloper and ADF
Thanks
--Anil

Problem when calling session bean from main.

Hi everyone
I get the following error when calling a session bean from main(String args[]).
Sep 3, 2008 9:11:13 AM com.sun.enterprise.appclient.MainWithModuleSupport <init>
WARNING: ACC003: Application threw an exception.
java.lang.NullPointerException
at databasetest.Main.main(Main.java:26)
Here is my code beneath.
I'm using netbeans and glassfish application server.
Everything is in the same project, called DatabaseTest, I also have deployed the application before running the client.
I'm running the client as follows, right click on the DatabaseTest-app-client and select run.
The client:
package databasetest;
import com.test.UsersFacadeRemote;
import javax.ejb.EJB;
import com.test.Users;
public class Main {
    @EJB
    private static UsersFacadeRemote usersFacade;
    public static void main(String[] args) {
        Users users = new Users(12, 34);
        usersFacade.create(users);
}The remote facade I'm calling:
package com.test;
import java.util.List;
import javax.ejb.Remote;
@Remote
public interface UsersFacadeRemote {
    void create(Users users);
    void edit(Users users);
    void remove(Users users);
    Users find(Object id);
    List<Users> findAll();
}The stateless bean:
package com.test;
import java.util.List;
import javax.ejb.Stateless;
import javax.persistence.EntityManager;
import javax.persistence.PersistenceContext;
@Stateless
public class UsersFacade implements UsersFacadeRemote {
    @PersistenceContext
    private EntityManager em;
    public void create(Users users) {
        em.persist(users);
    public void edit(Users users) {
        em.merge(users);
    public void remove(Users users) {
        em.remove(em.merge(users));
    public Users find(Object id) {
        return em.find(com.test.Users.class, id);
    public List<Users> findAll() {
        return em.createQuery("select object(o) from Users as o").getResultList();
}

looks like you're banging your head against the same brick wall as [I have done|http://forums.sun.com/thread.jspa?forumID=13&threadID=5317110] and [others have in the past|http://forums.sun.com/thread.jspa?forumID=136&threadID=5259913] if that's any consolation.
Funny thing is, mine did actually work in the debugger but not when running!
Strange thing that.
I did initially interest someone from the developers but they couldn't really help, ended up saying : try instantiating your beans the EJB 2.1 way and see where that gets you. Yes that works but they promised us "hey no more dopey xml deployment descriptors just some cool annotations" didn't they?
I've got the feeling were' missing something really obvious!
Edited by: sebthebike on 03-Sep-2008 12:21

Looking up of a stateless session bean from an MDB

Hi,
I have been trying to invoke a method on a stateless session bean from an MDB on receipt of a message from a queue. The bean receives the message. Then it gets the initial context, but after this the following message appears:
javax.naming.NamingException: Error instantation environment context for Message DrivenBean MyMDB: No location specified and no suitable instance of the type 'MySessionRemote' found for the ejb-ref <mySessionBean> at com.evermind.server.ejb.MessageDrivenHome.getEnvironmentContext(MessageDrivenHome.java:559)
The session bean is in a seperate ear file. These are the deployment descriptors of the MDB:
ejb-jar:
<ejb-jar>
     <description>A Message-Driven Beans</description>
     <enterprise-beans>
     <message-driven>
          <description></description>
          <ejb-name>MyMDB</ejb-name>
          <ejbclass>MyMDB</ejb-class>
          <message-driven-destination>
          <jms-destination-type>javax.jms.Queue</jms-destination-type>
          </message-driven-destination>
          <ejb-ref>
          <ejb-ref-name>MySessionEJB</ejb-ref-name>
          <ejb-ref-type>Session</ejb-ref-type>
          <home>MySessionEJBHome</home>
          <remote>MySessionRemote</remote>
          </ejb-ref>
     </message-driven>
     </enterprise-beans>
     <assembly-descriptor>
     </assembly-descriptor>
</ejb-jar>
orion-ejb-jar
<orion-ejb-jar>
<enterprise-beans>
          <message-driven-deployment name="QueueProcessor" destination-location="jms/theQueue" connection-factory-location="jms/theQueueConnectionFactory">
          </message-driven-deployment>
     </enterprise-beans>
     <assembly-descriptor>
     </assembly-descriptor>
</orion-ejb-jar>
The lookup name which I give in MDB is:
java:comp/env/MySessionEJB

Hi,
    Thanks for your replies.I did as you had suggested.I added ejb-local-ref to the ejb-jar.xml and i provided ejb-ref as MyBean.
My lookup code uses the string
ctxt.lookup("localejbs\MyBean");
But still i get Naming Exception.
I tried something different yesterday.
I changed the code to use
InitialContext ctxt = new InitialContext();
ctxt.lookup("localejbs/"+ pathfromJNDIRegistry);
and this time i did not get Naming exception but i got RemoteException saying there was error loading the class.
Is there something i need to add somewhere for the classloader to be able to find and load this class in the second scenario.
Please suggest me which method to go for amongst the two and what is the missing information i need to add.
Thanks
Priya

Injecting session bean from different EAR

Dear all,
I am using ejb3. i have ejb.ear and web.ear. both deploy in same weblogic server.
i want to inject session bean from ejb.ear inside web.ear.
With Regards,
WP

hi,
Currently, we want to separate it. Because may be we will deploy in different server in the future.
So far, i can inject it using remote interface.
How about local interface? is it possible to use local interface? because so far both deploy on same server.
As far as i know, glassfish can't. isn't it?
it is j2ee standard or server specific?
With Regards,
WP

How call session bean from Client side

Hi
calling session bean from client side it gives Lookup erroe, it gives JNDI error
how we know session bean is working. in Admin tree bean statis is reb Flaf, and ID is "Down" how we activate it..
null

If you can make a connection using sess_sh, then you know that you have configured your database and listener properly. If it is not working, read the manuals that you can download from technet. They are pretty good, and if you follow the directions, you should see success.
Good Luck!
Brad

Trying to call stateless session bean from MDB

Folks,
Am working on RAD and WAS 8.
I have an MDB. And a stateless session bean (AOBean under EJB project).
While the listener listens to the messages from queue, it also tries to persist to db. I want to achieve this via a method of AOBean (through instantiating session bean or by injection).
I have been sucessful by invoking a method from AOBean class - that method just returns a string (without any objects being passed)
Problem:
I am getting IllegalStateException when I try to invoke a method of AOBean class, that has an object as a parameter
For eg:
MDB
@EJB(name="ejb/TransactionMgrAOBean", mappedName="ejb/TransactionMgrAOBean")
ITransactionMgrAO tranAO;
    public void onMessage(Message message) {
     TextMessage textMessage = (TextMessage) message;
     boolean status = false;
try {
   TransactionVO tranVO = getTransactionVO();//Here building the object to be passed to session bean
   String status1 = tranAO.getVersion(tranVO);
}catch(Exception e){
AOBean
@Stateless
@Remote({ ITransactionMgrAO.class })
@WebService
public class TransactionMgrAOBean {
public String getVersion(TransactionVO tranVO) throws Exception{
try{
//business logic
} catch(Exception e){
throw e;
return true;
TransactionVO implements Serializable has also inner static classes that are not Serializable.
EXCEPTION: At runtime we are getting exception saying that the inner classes are not serialized.
REASON why we are invoking session bean from MDB? We found that if we invoke any service from AOBean the transaction management was successful. We are using sessionContext.setRollBackonly when an exception occurs. Tranasactions are not rolled back when any db exception occurs if we invoke business logic methods from Model layer of another NON-EJB package.
Hope I have provided enough information!

My concret problem is that I want to call an ejb session contained in an ejb project from a session bean in a different web project. When I include the code in my web session bean I get the error adjunted:
- Code:
@EJB
private UserRemote userSessionBean;
- Error:
Exception Details: javax.naming.NameNotFoundException
pac.UserRemote#pac.UserRemote not found
Possible Source of Error:
Class Name: com.sun.enterprise.naming.TransientContext
File Name: TransientContext.java
Method Name: doLookup
Line Number: 216
Any suggestion?

HOWTO:Deploy BC4J as Session Bean in Weblogic

This document describes Howto deploy a BC4J Appmodule as EJB Session Bean to Weblogic and
test the appmodule through the BC4J tester.
=>create a BC4J Application using Business Components Wizard.
=>test it using BC4J tester
=>make the Application Module Remotable [list]
[*]Select Appmodule and right mouse on it to select the edit option
[*]Select Remote tab
[*]Select the check box for Remotable Application Module
[*]Select EJB Session Bean and shuttle it from Available list to Selected list
[*]Click on the finish button[list]
=> Do File| Save All and a Rebuild on the project
=> create the weblogic XML Deployment Descriptor[list]
[*]Choose File|New
[*]Select the web objects tab
[*]Select XML and click ok
[*]Rename the file as ejb-jar.xml using File|Rename
[*]Save it in the JDEV_HOME/myclasses/META-INF directory.
[*]Open the xml file by double clicking on it.
[*]Paste the following into the file
<!DOCTYPE ejb-jar PUBLIC '-//Sun Microsystems, Inc.//DTD Enterprise JavaBeans 1.1//EN' 'http://java.sun.com/j2ee/dtds/ejb-jar_1_1.dtd'>
<ejb-jar>
<enterprise-beans>
<session>
<ejb-name>wl.WlModule</ejb-name>
<home>wl.common.ejb.WlModuleHome</home>
<remote>wl.common.ejb.RemoteWlModule</remote>
<ejb-class>wl.server.ejb.WlModuleServerEJB</ejb-class>
<session-type>Stateful</session-type>
<transaction-type>Bean</transaction-type>
</session>
</enterprise-beans>
<assembly-descriptor>
</assembly-descriptor>
</ejb-jar>
[*]Choose File|New
[*]Select the web objects tab
[*]Select XML and click ok
[*]Rename the file as weblogic-ejb-jar.xml using File|Rename
[*]Save it in the JDEV_HOME/myclasses/META-INF directory.
[*]Open the xml file by double clicking on it.
[*]Paste the following into the file
<!DOCTYPE weblogic-ejb-jar PUBLIC '-//BEA Systems, Inc.//DTD WebLogic 5.1.0 EJB//EN' 'http://www.bea.com/servers/wls510/dtd/weblogic-ejb-jar.dtd'>
<weblogic-ejb-jar>
<weblogic-enterprise-bean>
<ejb-name>wl.WlModule</ejb-name>
<caching-descriptor>
<max-beans-in-free-pool>100</max-beans-in-free-pool>
<max-beans-in-cache>100</max-beans-in-cache>
<idle-timeout-seconds>60</idle-timeout-seconds>
</caching-descriptor>
<jndi-name>wl.WlModule</jndi-name>
</weblogic-enterprise-bean>
</weblogic-ejb-jar>
In this example "wl" is the package name and "WlModule" is the Appmodule name.[list]
=> generate the jar file for appmodule along with xml deployment descriptors[list]
[*]from the command line in JDEV_HOME/myclasses directory run
[*]jar cvf0 wlappmodule.jar wl META-INF[list]
=> edit the setenv.cmd file in WEBLOGIC_HOME directory[list]
[*]set JAVA_HOME=f:\jdev32\java1.2
[*]set JBOLIB=f:\jdev32\lib
[*]set JDBC_CLASSES=f:\jdev32\jdbc\lib\oracle8.1.7\classes12.zip
[*]set JBO_RUNTIME=%JBOLIB%\jboorasql.zip;%JDBC_CLASSES%;%JBOLIB%\jbodatum12.zip;%JBOLIB%\xmlparserv2.jar;%JBOLIB%\jbomt.zip;%JBOLIB%\jboejb.jar
[*]add JBO_RUNTIME in the set CLASSPATH variable[list]
=> create a bc4j deploy batch file "Deploybc4j.cmd" in the WEB_LOGIC HOME
which will generate the server side jar files
@setlocal
set JAVA=java
set JAVAC=javac
set BEAN_JAR=%1
set EJB_TEMP=f:\jdev32\myclasses\wl
set XMLPARSERV2=f:\jdev32\lib\xmlparserv2.jar;
set JDBC_LIBS=f:\jdev32\jdbc\oracle8.1.7\lib\classes12.zip
set JBO_EJB_RUNTIME=f:\jdev32\lib\jbomt.zip;f:\jdev32\lib\jboejb.jar;%XMLPARSERV2%;%JDBC_LIBS%
set CLASSPATH=%CLASSPATH%;%JBO_EJB_RUNTIME%;%BEAN_JAR%;%EJB_TEMP%
%JAVA% weblogic.ejbc -compiler javac f:\jdev32\myclasses\wlappmodule.jar f:\jdev32\myclasses\wlAppModuleGenerated.jar;f:\jdev32\lib\jbodomorcl.zip
pushd %EJB_TEMP%
@endlocal
Note: substittue appropriate jar file and directory structure names
=> Run setenv.cmd
=> Run deploybc4j.cmd
=> Configure Weblogic server[list]
If your weblogic server is residing on a different machine then
[*]copy wlAppModuleGenerated.jar (generated jar file from deploybc4j.cmd)
[*]Copy classes12.zip from JDEV_HOME/jdbc/lib/oracle8.1.7/ directory
[*]Copy jbodomorcl.zip
[*]jbodatum12.zip
[*]xmlparserv2.jar
[*]jbomt.zip
[*]jboejb.jar from JDEV_HOME/lib directory
[*]edit weblogic.properties file in WEBLOGIC_HOME directory
[*]In the WEBLOGIC EJB DEMO PROPERTIES sectio
[*]add weblogic.ejb.deploy=E:/weblogic/myserver/wlAppModuleGenerated.jar
(generated jar file from deploybc4j.cmd file)
[*]edit startweblogic.cmd file in WEBLOGIC_HOME directory
[*]set POST_CLASSPATH=f:\jdev32\jdbc\oracle8.1.7\lib\classes12.zip;f:\jdev32\lib\jboorasql.zip;f:\jdev32\lib\jbodatum12.zip;f:\jdev32\lib\xmlparserv2.jar;f:\jdev32\lib\jbomt.zip;f:\jdev32 \lib\jboEJB.jar;f:\jdev32\lib\jbodomorcl.zip
[*]add E:/weblogic/myserver/wlAppModuleGenerated.jar
(generated jar file from deploybc4j.cmd file) in the weblogic_classpath setting[list]
Note: modify the directory structure of jar files as apporpriate
=> Run the BC4J tester to test the deployed BC4J Appmodule as session bean to Weblogic[list]
[*]Add a new library
[*]Select the Project in which you developed the BC4J Appmodule
[*]Project | Project Properties
[*]select libraries tab
[*]Click on Add
[*]Click on New
[*]Specify "JBO WL Client" in the NAME
[*]Click on ... button for adding the jar files
[*]Click on Add/Zip jar button to add the following files
weblogicaux.jar
jboremoteejb.zip
jboremote.zip
<Weblogic_home>/classes
[*]Click on OK
[*]Start the weblogic server
[*]Bring the BC4J Tester by doing a right mouse on the appmodule and selecting Test option
[*]In the Middle Tier Server Type Select "Weblogic"
[*]Specify Host name and port # of weblogic server
[*]Click on Connect[list]
raghu
null

Although this explains how to then deploy to Weblogic on another server, it still presumes that it is installed on the same computer as JDev. I moved the weblogic.jar file over to the computer and fudged a few things to get it to work.
Also, I am testing this with Weblogic 6.0, so some of the information does not work as prescribed. I edited the config.xml instead of the weblogic.properties file. I am trying to figure out where to put all of the *.jar and *.zip files that I copied over to the Solaris machine with Weblogic. Any suggestions?
And one of the steps in the section to create the deploybc4j.cmd file is wrong. It says
"%JAVA% weblogic.ejbc -compiler javac f:\jdev32\myclasses\wlappmodule.jar f:\jdev32\myclasses\wlAppModuleGenerated.jar;f:\jdev32\lib\jbodomorcl.zip"
Which does not work. I took off the last part:
"%JAVA% weblogic.ejbc -compiler javac f:\jdev32\myclasses\wlappmodule.jar f:\jdev32\myclasses\wlAppModuleGenerated.jar"
and it worked. It was getting that whole last part and trying to create a directory with that name and failing.
<BLOCKQUOTE><font size="1" face="Verdana, Arial">quote:</font><HR>Originally posted by David Shanes ([email protected]):
This seems to assume that JDev and Weblogic are installed on the same server (I refer to the section on setting the setenv.cmd file in the WEBLOGIC_HOME dir that includes the path to the JDev install.
I have JDev installed on a Win 2k box and Weblogic installed on a Solaris. Any suggestions? I got all the way up to the setenv.cmd step fine.<HR></BLOCKQUOTE>
null

How do you use one managed session bean from another?

Hello -
I am a complete newbie to JSF coming from Struts 1. My question is how do you use one managed bean from the method of another one? I think this would be a common senario. For example I put a bean in session scope when a user logs in and in a different method within a different bean I want to get some of this user's information. What is the correct way to retireve one bean from a method in another with session scope?
Also what would the code look like to retieve another bean from the method of a managed bean where the bean you want to retrieve has application scope?
Thank you in advance.

Sinplicity wrote:
Could you be a bit more specific? If a bean is configured in the faces config file then all of it's properties are managed, correct?Not necessarily.
What would the code look like to retireve the bean?You don't retrieve it, it has been injected.
Can I retrieve the whole bean or just a property of the bean. I would be really interested in seeing how this is done in code? And would really love a bit more information on what it means to be a managed property?Time to consult a JSF tutorial.

Calling Local Stateless session bean from Spring in weblogic 10.3

We are in the process of upgrading to Weblogic 10.3 from OC4J (OAS). We are using Spring and Stateless Session EJB 3 Local beans (Don't ask me why, it is decided before I came to the project).
Previously (OC4J):
-> There is no ejb-jar.xml. EJBs are configured with annotation @Stateless. No "name" or "mappedName" are defined.
Spring POJOs access EJBs by using "EJBMODULENAME_<<EJBBeanClass>>Local" as JNDI Name. I think this strange JNDI name is what OC4J assigns when there is no explicit JNDI name defined.
Sample Spring Bean configuration -
<bean name="securityEJB" class="org.springframework.ejb.access.LocalStatelessSessionProxyFactoryBean" lazy-init="true">
          <property name="jndiName">
               <value>myapp-ejb_SecurityEJBImplLocal</value>
          </property>
          <property name="resourceRef">
               <value>false</value>
          </property>
          <property name="businessInterface">
               <value>my.package.SecurityEJB</value>
          </property>
     </bean>
I understand that weblogic 10.x doesn't give any global JNDI name (JNDI tree is empty) and also looked at the blog, Link: [http://m-button.blogspot.com/2008/07/reminder-on-how-to-use-ejb3-with.html]
So far I have tried,
1. @EJB annotation works but, I don't want to add @EJB annotations in the entire application. Since we are using Spring and EJB3, I am trying to avoid mixing them -
2. java:comp/env is supposed to work (since it is a local session bean), but it doesn't for me.
I haven't added weblogic-ejb-jar.xml as I don't think it is going to help, as there is no global JNDI name defined. Am I missing some thing?
Thx

Hi,
if you don't want to use @EJB to inject the EJB, then you'll need declare the EJB reference in deployment descriptor.
Here is an example copied from EJB3 spec:
<ejb-local-ref>
<description>
This is a reference to the local business interface
of an EJB 3.0 session bean that provides a payroll
service.
</description>
<ejb-ref-name>ejb/Payroll</ejb-ref-name>
<local>com.aardvark.payroll.Payroll</local>
</ejb-local-ref>
then you can lookup the local ejb from "java:comp/env/ejb/Payroll".

Problem while invoking a Stateless Session bean from another bean

Hi,
I have a peculiar problem while coding with Stateless Session beans. Maybe you guys can help me out over here. The scenario is as follows
There are 3 Stateless Session beans. Let Us say Bean A, B and C. There are three methods, method1, method2, and method3 inside A, B and C respectively.
From A.method1(), B.method2(), and C.method3() are being invoked sequentially. Each of these methods does some JDBC operation and then returns.
The problem is this, if C.method3() throws and exception, then I am unable to rollback the changes made by B.method2(). Those changes get "Committed" to the database.
All the 3 beans have Bean managed persistence property set. I am using WebSphere 6.1.
Any insight on why this is happening would be greatly appreciated.
Thanks In Advance
Amardeep Verma

Hi,
This is a matter of calling all three methods in the same transaction context. Most easy way of doing this is having a 4th session bean containing a method calling the other 3. Make sure that the Transaction Attributes are REQUIRED, which is the default.
If the calls a to different backends/databases, you need global transactions and therefor XA complient database and drivers.
HTH Robert

HowTo talk to a Session bean from an Applet sample app. problem

Similar Messages

Maybe you are looking for