JDev 10.1.3: Problem deploying a session bean to embedded OC4J

JDeveloper 10.1.3, TopLink, OC4J, WinXP, java 1.4.2_05.
I used TopLink to create a set of Java objects from a DB Schema, then created a simple Session Bean to read some of the objects. Everything compiles fine.
JAVA_HOME points to the JDK (not JRE) and CLASSPATH is empty (undefined).
When I try to Run my session bean in the jdeveloper embedded oc4j, I get this message. Thanks in advance for your help.
Milind
===============
[Starting OC4J using the following ports: HTTP=8988, RMI=23891, JMS=9227.]
C:\Tools\jdev_10_1_3\jdev\system\oracle.j2ee.10.1.3.3.51\oc4j-config>
C:\Tools\jdev_10_1_3\jdk\bin\javaw.exe -ojvm -classpath C:\Tools\jdev_10_1_3\j2ee\home\oc4j.jar;C:\Tools\jdev_10_1_3\jdev\lib\jdev-oc4j-embedded.jar -Xverify:none -DcheckForUpdates=adminClientOnly -Doracle.j2ee.dont.use.memory.archive=true -Doracle.j2ee.http.socket.timeout=500 -Doracle.dms.sensors=NONE -Doc4j.jms.usePersistenceLockFiles=false oracle.oc4j.loader.boot.BootStrap -config C:\Tools\jdev_10_1_3\jdev\system\oracle.j2ee.10.1.3.3.51\oc4j-config\server.xml
[waiting for the server to complete its initialization...]
05/03/22 14:43:50 Node started with id=127765687050882
05/03/22 14:43:52 Auto-deploying - applications/admin_ejb.jar (orion-ejb-jar.xml had been updated since the previous deployment)...
05/03/22 14:43:52 Error initializing server: Error initializing ejb-module; Exception null
05/03/22 14:43:53 Fatal error: server exiting
Process exited with exit code 1.

Error initializing ejb-module;
Is the EJB Jar structured as
META-INF/
ejb-jar.xml
Bean Class
Home interface Class
Remote interface Class
Does the EJBdeploy in some other server?

Similar Messages

  • A simple problem with sateful Session beans

    Hi,
    I have a really novice problem with stateful session bean in Java EE 5.
    I have written a simple session bean which has a counter inside it and every time a client call this bean it must increment the count value and return it back.
    I have also created a simple servlet to call this session bean.
    Everything seemed fine I opened a firefox window and tried to load the page, the counter incremented from 1 to 3 for the 3 times that I reloaded the page then I opened an IE window (which I think is actually a new client) but the page counter started from 4 not 1 for the new client and it means that the new client has access to the old client session bean.
    Am I missing anything here???
    Isn�t it the way that a stateful session bean must react?
    This is my stateful session bean source.
    package test;
    import javax.ejb.Stateful;
    @Stateful
    public class SecondSessionBean implements SecondSessionRemote
    private int cnt;
    /** Creates a new instance of SecondSessionBean */
    public SecondSessionBean ()
    cnt=1;
    public int getCnt()
    return cnt++;
    And this is my simple client site servlet
    package rezaServlets;
    import java.io.*;
    import java.net.*;
    import javax.ejb.EJB;
    import javax.servlet.*;
    import javax.servlet.http.*;
    import test.SecondSessionRemote;
    public class main extends HttpServlet
    @EJB
    private SecondSessionRemote secondSessionBean;
    protected void processRequest (HttpServletRequest request, HttpServletResponse response)
    throws ServletException, IOException
    response.setContentType ("text/html;charset=UTF-8");
    PrintWriter out = response.getWriter ();
    out.println("<html>");
    out.println("<head>");
    out.println("<title>Servlet main</title>");
    out.println("</head>");
    out.println("<body>");
    out.println("<h1>Our count is " + Integer.toString (secondSessionBean.getCnt ()) + "</h1>");
    out.println("</body>");
    out.println("</html>");
    out.close ();
    protected void doGet (HttpServletRequest request, HttpServletResponse response)
    throws ServletException, IOException
    processRequest (request, response);
    protected void doPost (HttpServletRequest request, HttpServletResponse response)
    throws ServletException, IOException
    processRequest (request, response);
    }

    You are injecting a reference to a stateful session bean to an instance variable in the servlet. This bean instance is shared by all servlet request, and that's why you are seeing this odd behavior.
    You can use type-leve injection for the stateful bean, and then lookup the bean inside your request-processing method. You may also save this bean ref in HttpSession.
    @EJB(name="ejb/foo", beanName="SecondBean", beanInterface="com.foo.foo.SecondBeanRemote")
    public MyServlet extends HttpServlet {
    ic.lookup("java:comp/env/ejb/foo");
    }

  • Can I deploy the session bean to 9i in the JDeveloper3.2

    dear ONT
    My JDeveloper3.2 can't find the method to deploy the session bean to 9i.
    sk

    I'm not sure that's entirely correct.
    Personally I run both EJBs and servlets/JSP in OC4J. OC4J has all the 'web' features of IAS, including full SSL support.
    From a speed perspective, running the EJBs and web components in the same container will give you a huge benefit.
    Also I'm not sure what you mean by "you can't deploy EJBs into OC4J yet" - I do it daily? ;)
    -mike
    Atlassian - Supporting Your 'Orion/OC4J' World
    http://www.atlassian.com

  • Mail Session configuration with embedded oc4j in jdeveloper 10g 10.1.3.1

    Hello all:
    I'd tried to use javamail in a j2ee application. I´d defined an resource reference with the EJB Module Editor but when i run the application it throws:
    java.lang.InstantiationException: Error initializing ejb-modules: No Mail Session configured for the resource MailSession
    How can i configure a Mail Session with the embedded oc4j of jdeveloper 10g 10.1.3.1?
    Thanks a lot.

    Hi,
    You need to add following configuration in $ORACLE_HOME/j2ee/home/config/application.xml & restart your OC4J :-
    <mail-session location="EMailSession" smtp-host="mail.cdsc.com">       <property name="mail.transport.protocol" value="smtp"/>       <property name="mail.debug" value="true"/>    </mail-session>Regards,
    Sandeep

  • NullPointerException when deploying sateless session bean

    I'm deploying a simple Stateless Session Bean, my deployment descriptors are
    being generated with xdoclet. I'm getting the following exception:
    weblogic.management.ApplicationException:
    Exception:weblogic.management.ApplicationException: prepare failed for
    formulacionEJB.jar
    Module: formulacionEJB.jar Error: Exception preparing module:
    EJBModule(formulacionEJB.jar,status=NEW)
    Unable to deploy EJB:
    C:\bea\user_projects\domains\formulacion\myserver\stage\_appsdir_formulacion
    _ear\formulacionEJB.jar from formulacionEJB.jar:
    java.lang.NullPointerException
    at
    weblogic.ejb20.deployer.SessionBeanInfoImpl.assignDefaultTXAttributesIfNeces
    sary(SessionBeanInfoImpl.java:291)
    at
    weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.initializeTransactionAttribu
    te(MBeanDeploymentInfoImpl.java:807)
    at
    weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.<init>(MBeanDeploymentInfoIm
    pl.java:240)
    at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1262)
    at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:477)
    at
    weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContaine
    r.java:2962)
    at
    weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContain
    er.java:1534)
    at
    weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java
    :1188)
    at
    weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java
    :1031)
    at
    weblogic.management.deploy.slave.SlaveDeployer$ComponentActivateTask.prepare
    Container(SlaveDeployer.java:2602)
    at
    weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.createContainer(
    SlaveDeployer.java:2552)
    at
    weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(SlaveDep
    loyer.java:2474)
    at
    weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeplo
    yer.java:798)
    at
    weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer.ja
    va:507)
    at
    weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.j
    ava:465)
    at
    weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.ja
    va:25)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
    Do you have any idea of why is this happening?
    Thanks in advance,
    Alejandro Escalante Medina

    Im having what appears to be the same exact problem (Im getting a NPE and same error message). Did this get resolved? Im using xdoclet as well ... Here are the respective deployment descriptors that are getting created via xdoclet ...
    Thanks,
    Scott :)
    ejb-jar.xml:
    <?xml version="1.0" encoding="UTF-8"?>
    <!DOCTYPE ejb-jar PUBLIC "-//Sun Microsystems, Inc.//DTD Enterprise JavaBeans 2.0//EN" "http://java.sun.com/dtd/ejb-jar_2_0.dtd">
    <ejb-jar >
    <description><![CDATA[No Description.]]></description>
    <display-name>Generated by XDoclet</display-name>
    <enterprise-beans>
    <!-- Session Beans -->
    <session >
    <description><![CDATA[AdministrationManager EJB]]></description>
    <display-name>AdministrationManager</display-name>
    <ejb-name>AdministrationManager</ejb-name>
    <home>com.jnj.depuy.wwl.ejb.administrationmanager.AdministrationManagerHome</home>
    <remote>com.jnj.depuy.wwl.ejb.administrationmanager.AdministrationManager</remote>
    <local-home>com.jnj.depuy.wwl.ejb.administrationmanager.AdministrationManagerLocalHome</local-home>
    <local>com.jnj.depuy.wwl.ejb.administrationmanager.AdministrationManagerLocal</local>
    <ejb-class>com.jnj.depuy.wwl.ejb.administrationmanager.AdministrationManagerSession</ejb-class>
    <session-type>Stateless</session-type>
    <transaction-type>Container</transaction-type>
    </session>
    <session >
    <description><![CDATA[SequenceManager EJB]]></description>
    <display-name>SequenceManager</display-name>
    <ejb-name>SequenceManager</ejb-name>
    <home>com.jnj.depuy.wwl.ejb.sequencemanager.SequenceManagerHome</home>
    <remote>com.jnj.depuy.wwl.ejb.sequencemanager.SequenceManager</remote>
    <local-home>com.jnj.depuy.wwl.ejb.sequencemanager.SequenceManagerLocalHome</local-home>
    <local>com.jnj.depuy.wwl.ejb.sequencemanager.SequenceManagerLocal</local>
    <ejb-class>com.jnj.depuy.wwl.ejb.sequencemanager.SequenceManagerSession</ejb-class>
    <session-type>Stateless</session-type>
    <transaction-type>Container</transaction-type>
    </session>
    <!--
    To add session beans that you have deployment descriptor info for, add
    a file to your XDoclet merge directory called session-beans.xml that contains
    the <session></session> markup for those beans.
    -->
    <!-- Entity Beans -->
    <!--
    To add entity beans that you have deployment descriptor info for, add
    a file to your XDoclet merge directory called entity-beans.xml that contains
    the <entity></entity> markup for those beans.
    -->
    <!-- Message Driven Beans -->
    <!--
    To add message driven beans that you have deployment descriptor info for, add
    a file to your XDoclet merge directory called message-driven-beans.xml that contains
    the <message-driven></message-driven> markup for those beans.
    -->
    </enterprise-beans>
    <!-- Relationships -->
    <!-- Assembly Descriptor -->
    <assembly-descriptor >
    <!--
    To add additional assembly descriptor info here, add a file to your
    XDoclet merge directory called assembly-descriptor.xml that contains
    the <assembly-descriptor></assembly-descriptor> markup.
    -->
    <!-- finder permissions -->
    <!-- finder permissions -->
    <!-- transactions -->
    <!-- finder transactions -->
    </assembly-descriptor>
    </ejb-jar>
    weblogic-ejb-jar.xml:
    <!DOCTYPE weblogic-ejb-jar PUBLIC '-//BEA Systems, Inc.//DTD WebLogic 8.1.0 EJB//EN' 'http://www.bea.com/servers/wls810/dtd/weblogic-ejb-jar.dtd'>
    <!-- Generated XML! -->
    <weblogic-ejb-jar>
    <weblogic-enterprise-bean>
    <ejb-name>AdministrationManager</ejb-name>
    <stateless-session-descriptor>
    <pool>
    </pool>
    <stateless-clustering>
    </stateless-clustering>
    </stateless-session-descriptor>
    <transaction-descriptor>
    </transaction-descriptor>
    <jndi-name>AdministrationManager</jndi-name>
    </weblogic-enterprise-bean>
    <weblogic-enterprise-bean>
    <ejb-name>SequenceManager</ejb-name>
    <stateless-session-descriptor>
    <pool>
    </pool>
    <stateless-clustering>
    </stateless-clustering>
    </stateless-session-descriptor>
    <transaction-descriptor>
    </transaction-descriptor>
    <jndi-name>SequenceManager</jndi-name>
    </weblogic-enterprise-bean>
    </weblogic-ejb-jar>
    And for reference the error:
    BUILD FAILED
    file:C:/My Sources/WWL/wwlear/build.xml:201: weblogic.utils.compiler.ToolFailureException: [J2EE:160119]Appc is unable to process the file 'C:\My Buil
    java.lang.NullPointerException
    at weblogic.ejb20.deployer.SessionBeanInfoImpl.assignDefaultTXAttributesIfNecessary(SessionBeanInfoImpl.java:291)
    at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.initializeTransactionAttribute(MBeanDeploymentInfoImpl.java:807)
    at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.<init>(MBeanDeploymentInfoImpl.java:240)
    at weblogic.ejb20.ejbc.EJBCompiler.setupEJB(EJBCompiler.java:155)
    at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:415)
    at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:387)
    at weblogic.appc.compileEJB(appc.java:802)
    at weblogic.appc.compileModules(appc.java:621)
    at weblogic.appc.compileEAR(appc.java:733)
    at weblogic.appc.compileInput(appc.java:458)
    at weblogic.appc.runBody(appc.java:184)
    at weblogic.utils.compiler.Tool.run(Tool.java:146)
    at weblogic.utils.compiler.Tool.run(Tool.java:103)
    at weblogic.appc.main(appc.java:1028)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:324)
    at weblogic.ant.taskdefs.j2ee.CompilerTask.invokeMain(CompilerTask.java:278)
    at weblogic.ant.taskdefs.j2ee.Appc.execute(Appc.java:179)
    at org.apache.tools.ant.Task.perform(Task.java:341)
    at org.apache.tools.ant.Target.execute(Target.java:309)
    at org.apache.tools.ant.Target.performTasks(Target.java:336)
    at org.apache.tools.ant.Project.executeTarget(Project.java:1339)
    at org.apache.tools.ant.Project.executeTargets(Project.java:1255)
    at org.apache.tools.ant.Main.runBuild(Main.java:609)
    at org.apache.tools.ant.Main.start(Main.java:196)
    at org.apache.tools.ant.Main.main(Main.java:235)
    at weblogic.ejb20.ejbc.EJBCompiler.setupEJB(EJBCompiler.java:164)
    at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:415)
    at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:387)
    at weblogic.appc.compileEJB(appc.java:802)
    at weblogic.appc.compileModules(appc.java:621)
    at weblogic.appc.compileEAR(appc.java:733)
    at weblogic.appc.compileInput(appc.java:458)
    at weblogic.appc.runBody(appc.java:184)
    at weblogic.utils.compiler.Tool.run(Tool.java:146)
    at weblogic.utils.compiler.Tool.run(Tool.java:103)
    at weblogic.appc.main(appc.java:1028)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:324)
    at weblogic.ant.taskdefs.j2ee.CompilerTask.invokeMain(CompilerTask.java:278)
    at weblogic.ant.taskdefs.j2ee.Appc.execute(Appc.java:179)
    at org.apache.tools.ant.Task.perform(Task.java:341)
    at org.apache.tools.ant.Target.execute(Target.java:309)
    at org.apache.tools.ant.Target.performTasks(Target.java:336)
    at org.apache.tools.ant.Project.executeTarget(Project.java:1339)
    at org.apache.tools.ant.Project.executeTargets(Project.java:1255)
    at org.apache.tools.ant.Main.runBuild(Main.java:609)
    at org.apache.tools.ant.Main.start(Main.java:196)
    at org.apache.tools.ant.Main.main(Main.java:235)

  • Problem when running session bean

    Hi all,
    I am a new comer to jdeveloper11g and weblogic10.In these days i am trying to create session bean in jdeveloper. but i got this error when i am try to run the program using new sample client.
    mapped name=New-SessionEJB
    package=project1
    Remote interface=NewSession
    SessionBean=NewSessionBean
    javax.naming.NameNotFoundException: While trying to lookup 'New-SessionEJB#project1.NewSession' didn't find subcontext 'New-SessionEJB#project1'. Resolved '' [Root exception is javax.naming.NameNotFoundException: While trying to lookup 'New-SessionEJB#project1.NewSession' didn't find subcontext 'New-SessionEJB#project1'. Resolved '']; remaining name 'New-SessionEJB#project1/NewSession'
         at weblogic.rjvm.ResponseImpl.unmarshalReturn(ResponseImpl.java:234)
         at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:348)
         at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:259)
         at weblogic.jndi.internal.ServerNamingNode_1030_WLStub.lookup(Unknown Source)
         at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:392)
         at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:380)
         at javax.naming.InitialContext.lookup(InitialContext.java:392)
         at project1.NewSessionClient.main(NewSessionClient.java:16)
    Caused by: javax.naming.NameNotFoundException: While trying to lookup 'New-SessionEJB#project1.NewSession' didn't find subcontext 'New-SessionEJB#project1'. Resolved ''
         at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:1139)
         at weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:247)
         at weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:182)
         at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:206)
         at weblogic.jndi.internal.RootNamingNode_WLSkel.invoke(Unknown Source)
         at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:589)
         at weblogic.rmi.cluster.ClusterableServerRef.invoke(ClusterableServerRef.java:230)
         at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:477)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
         at weblogic.security.service.SecurityManager.runAs(Unknown Source)
         at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:473)
         at weblogic.rmi.internal.wls.WLSExecuteRequest.run(WLSExecuteRequest.java:118)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    Process exited with exit code 0.
    Here is my client program
    public class NewSessionClient {
    public static void main(String [] args) {
    try {
    final Context context = getInitialContext();
    NewSession newSession = (NewSession)context.lookup("New-SessionEJB#project1.NewSession");
    } catch (Exception ex) {
    ex.printStackTrace();
    private static Context getInitialContext() throws NamingException {
    Hashtable env = new Hashtable();
    // WebLogic Server 10.x connection details
    env.put( Context.INITIAL_CONTEXT_FACTORY, "weblogic.jndi.WLInitialContextFactory" );
    env.put(Context.PROVIDER_URL, "t3://localhost:7101");
    return new InitialContext( env );
    If anybody know what the problem is please tell me.
    thanks.......
    (tcr)

    I ran into the EXACT same problem described by Tracy, and I assembled my .ear file manually.
    According the error message, it would appear that the server is looking for the EJB remote interface in the ../temp/__session_bean_rpc directory when it is trying to generate its session bean wrapper class. As Tracy notes, when the file Hello.class is copied into the directory, the problem goes away. Furthermore, once the wrapper class has been generated, Hello.class is no longer needed and can be deleted from the directory.
    Better still, I found a way to deploy the web services web module and make the error go away. I created the ejbws.war file with a copy of the remote interface Hello.class in the WEB-INF/classes directory. This makes the class available when the wrapper class is generated.
    The WebServicesAssembler tool doesn't copy the EJB remote interfaces into the .war web module, which would appear to be
    necessary.
    Hope this helps.

  • Enable to Deploy Stateful session Bean

    Hello EveryBody,
    I have problem to deploy the stateful session bean.i have attached the error shown in server screen.Please give me the suggestion.when ever i create .ear file and paste in application directory it shows following errors.
    weblogic.management.ApplicationException:
    Exception:weblogic.management.ApplicationException: Prepare failed. Task Id = 0
    Module: Cart.war Error: [HTTP:101179][HTTP] Error occurred while
    parsing descriptor in Web application "C:\bea\user_projects\domains\mydomain\.\m
    yserver\stage\_appsdir_Cart_ear\Cart.war" [Path="C:\bea\user_projects\domains\my
    domain\applications\Cart.ear", URI="Cart.war"
    weblogic.xml.dom.DOMProcessingException: Neither principal-names nor externall
    -defined element specified for security-role-assignment
    weblogic.xml.dom.DOMProcessingException: Neither principal-names nor externall
    -defined element specified for security-role-assignment
    at weblogic.servlet.internal.dd.SecurityRoleAssignment.<init>(Lweblogic
    servlet.internal.dd.WebAppDescriptor;Lorg.w3c.dom.Element;)V(SecurityRoleAssign
    ent.java:73)
    at weblogic.servlet.internal.dd.WLWebAppDescriptor.<init>(Lweblogic.ser
    let.internal.dd.WebAppDescriptor;Lorg.w3c.dom.Element;)V(WLWebAppDescriptor.jav
    :147)
    at weblogic.servlet.internal.dd.DescriptorLoader.initializeWebLogicXml(
    org.xml.sax.InputSource;Ljava.lang.String;)V(DescriptorLoader.java:742)
    at weblogic.servlet.internal.dd.DescriptorLoader.<init>(Ljava.util.jar.
    arFile;Ljava.io.File;Ljava.lang.String;)V(DescriptorLoader.java:303)
    at weblogic.servlet.internal.dd.DescriptorLoader.<init>(Ljava.util.jar.
    arFile;Ljava.lang.String;)V(DescriptorLoader.java:235)
    at weblogic.servlet.internal.WebAppModule.loadDescriptor()Lweblogic.man
    Thanks in Advance.
    Riaz

    Thank u for user suggestion.but can u specifiy the which type of error is this.I am using Weblogic Builder for generating xml file.
    in the j2ee reference-->EJBRefs-->ADD
    RefName:--ejb/Cart
    JNDI Name:CartBean
    EJBTYPE:session
    REMOTE INTERFACE:statedemo.Cart
    HomeInterface:statedemo.CartHome
    I have add these parameters.but don't write anything in
    link & Description field
    Thanks a lot
    Riaz

  • Problem Calling Remote Session Bean Method

    Need help. I am trying to call a method in a remote stateless session bean in an EJB in my web application from a stateless session bean in a different EJB in the web application. I am getting a run-time error that says,
    "java.lang.NoClassDefFoundError: dtpitb.common.sb.reports.CommonReportsHome"
    ref = ctx.lookup( jndiName );
    // Cast to Local Home Interface using RMI-IIOP
    commonReportsHome = (CommonReportsHome)
    PortableRemoteObject.narrow(ref, CommonReportsHome.class);
    If while in a session bean of an EJB, I want to call a public method in the session bean of a totally different EJB, is there something in particular I am missing. I can make the call from the web application code. I can make a remote call from this session bean to itself in the exact same fashion. I just can't call a session bean in another EJB. All thoughts are welcome.
    Thanks,
    Pete

    Thanks for replying. That could very well be the case I suppose. I'm using JBuilder and WebLogic, and JBuilder pretty much does all of the deployment descriptor code for me. However, maybe this is something I need to incorporate manually.
    One EJB is in the same project as the web application code. The other EJB (common_ejb) is in another project. The calling session bean is in the project with the web app, and the remote session bean method that I'm targeting is in the common EJB session bean. Both EJBs are included in the web app's WEB-INF\lib dir and in the war file.
    So theoretically, this isn't an unconventional practice I assume?
    Thanks,
    Pete

  • 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

  • I have got problem to create Session Bean

    Hi
    I am new in j2ee. I have installed the eclipse 3.1, j2sdk1.4.2_07 and tomcat 5.0. I have created a ejb with a session bean and it gives me a error the program doesn't find the class javax.ejb.SessionBean. My question is Can this error happen because I don't have installed J2EE 1.4 SDK and Sun Java System Application Server Platform Edition 8.1?
    thank you

    Hi
    I have tried to put the classpath with j2ee in eclipse but it happens the same. it doesn't find the package javax.ejb.SessionBean.
    I am going to explain i have done from the beginning. Maybe I am wrong in something. I think which is that.
    I have create a proyect with Dynamic Web Proyect after i create a proyect with ejbModule. I attempt to create a file with session bean. In last proyect acceded to Run->Run here i select Apache Tomcat and Tomcat v5.0 Server _ localhost and i select the classpath in "bootstrap entries" i insert the file j2ee.jar. And I' ve got the same error.
    is it fine? I am bored trying to find the problem.
    thanks in advanced

  • How to deploy a session bean in Weblogic 9.2

    Hi,
    Can anyone please point me to the procedure of deploying session bean on weblogic 9.2. My operating system is Fedora 5. Please let me know the steps as i am very new to EJB.
    Regards,
    Sanjeev

    I looked for this information in ServletConfig, in ServletContext, in JVMID
    ServletConfig or ServletContext do not have anything (at least I do not see anything),
    The newsgroups recommend the following code
    public static String getLocalUrlString()
    String urlString;
    JVMID jvmid = JVMID.localID();
    urlString = jvmid.getHostAddress();
    weblogic.rjvm.Protocol proto
    =weblogic.rjvm.Protocol.getDefaultProtocol();
    int port = jvmid.getPort(proto);
    return urlString + ISoapConstants.SCHEME_DELIMITER + port;
    I also tried
    weblogic.rjvm.Protocol does not exist in current version, and I did not get any real information inside JVMID
    Also tried JVMID.localID().ports(), which returns null
    System.getProperty("weblogic.system.bindAddr"); or weblogic.system.listenPort property,
    getProperty returns null
    Tried also another approach from the newsgroups - JwsContext.
    /** @common:context */
    JwsContext context;
    String myPort = context.getService().getURL().getPort();
    String myUrl = context.getService().getURL().toString();
    context is null
    None of them worked.
    Do you have any other ideas?
    All those ideas I found in the newsgroups were to the previos version(s) of weblogic - up to 8.1. I have not found anything specific to 9.2

  • Problem calling a session bean (EJB 3.0)

    Hello,
    I'm new to netbeans and J2EE. I'm using NetBeans 5.5 Beta 2 and sun application server 9 pe.
    I created a new enterprise application and i'm trying to access a Session Bean (Remote and Stateless)
    from the app-client (outside the main class).
    This is the loockup method that was generated by the IDE (Enterprise Resources > Call enterprise bean):
    private ejb.SessionBeanDoenteRemote lookupSessionBeanDoenteBean() {
    try {
    javax.naming.Context c = new javax.naming.InitialContext();
    return (ejb.SessionBeanDoenteRemote) c.lookup("java:comp/env/ejb/SessionBeanDoenteBean");
    catch(javax.naming.NamingException ne) {
    java.util.logging.Logger.getLogger(getClass().getName()).log(java.util.logging.Level.SEVERE,"exception caught" ,ne);
    throw new RuntimeException(ne);
    When I run the application and try to invoke the lookup method my application gets the following exception:
    SEVERE: exception caught
    javax.naming.NameNotFoundException: No object bound to name java:comp/env/ejb/Se
    ssionBeanDoenteBean
    at com.sun.enterprise.naming.NamingManagerImpl.lookup(NamingManagerImpl.
    java:751)
    at com.sun.enterprise.naming.java.javaURLContext.lookup(javaURLContext.j
    ava:156)
    at com.sun.enterprise.naming.SerialContext.lookup(SerialContext.java:307
    at javax.naming.InitialContext.lookup(InitialContext.java:351)
    at intensivecare.entrada.JDialogEntrada.lookupSessionBeanDoenteBean(JDia
    logEntrada.java:219)
    at intensivecare.entrada.JDialogEntrada.buttonMenuGravarActionPerformed(
    JDialogEntrada.java:79)
    at intensivecare.JDialogWizzard$2.jButtonGravarActionPerformed(JDialogWi
    zzard.java:178)
    at componentes.JTaskPanelMenu$3.actionPerformed(JTaskPanelMenu.java:54)
    at javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:18
    49)
    at javax.swing.AbstractButton$Handler.actionPerformed(AbstractButton.jav
    a:2169)
    Please... can someone help me?

    The portable way to acquire the dependency is through java:comp/env or @EJB. Accessing the
    global namespace directly is not recommended. If you use an ejb-ref, you need to define it
    in the component environment within which you'll be looking up the dependency. So if you're
    looking it up from an Application Client, you'll need to define the ejb-ref in application-client.xml.
    Also, the ejb-ref-name is the portion of the string after java:comp/env. There is no automatic
    "ejb" appended to it. If you do ic.lookup("java:comp/env/foo"), your ejb-ref-name would be "foo".
    You can use @EJB but it can only be defined in certain managed classes such as the
    Application Client main class.
    You can find additional info in our EJB FAQ :
    https://glassfish.dev.java.net/javaee5/ejb/EJB_FAQ.html
    --ken                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   

  • Setting a deployment context when using the embedded OC4J

    I'm trying to debug a servlet using the embedded OC4J server. I have a simple project that includes a servlet source file and and a web.xml file. The web.xml file defines context
    parameters that I want the servlet to read and use when it is deployed. However I don't know
    how to get JDeveloper to set up the servlet context on the debugging environment to use the
    contents of the web.xml file. Could anyone tell me how to do this? I cannot see how to
    do this from the help files.
    Many thanks in advance

    The trick is to ensure that you use a 'Project with Web Module' rather than
    'Empty Project' and then add a new 'HTTP Servlet'. When you do this
    JDeveloper automatically creates a web.xml file. You can add context
    parameters, or practically any other configuration items by right clicking
    on the web.xml tree node inthe system navigator and selecting settings.
    The web.xml file is saved into the directory specified by the 'HTML Root Directory' on the 'Input Paths' panel in the project settings dialog.

  • Deploying Stateful Session Bean

    hi!
    I've got a problem when deploying a Stateful SessionBean. It worked well for about 1 week. I changed a little thing in the BeanClass, and afterwards only got deployment errors. taking back the changes had no effect.
    Furthermor the Error seems to be nonsens, because I deploy from a EAR, and this ear contains all Files of the Stateful SessionBean. The container seems to have problems to read the jar file within the ear file ...???
    cu
    ed
    C:\jdev\jdk\jre\bin\javaw.exe -jar C:\jdev\j2ee\home\admin.jar ormi://localhost/ admin **** -deploy -file D:\DATEN\CVS\revdb\Implementierung\Java\ejbsession\EJBSession.ear -deploymentName revdb_ejb
    Fatal Error: Error loading class 'at.gv.brz.revdb.ejb.ejbsession.session.impl.EJBSessionBean': java.lang.NoClassDefFoundError: at.gv.brz.revdb.ejb.ejbsession.session.impl.EJBSessionBean
    Auto-unpacking C:\jdev\j2ee\home\applications\EJBSession.ear... done.
    Copying default deployment descriptor from archive at C:\jdev\j2ee\home\applications\EJBSession/META-INF/orion-application.xml to deployment directory C:\jdev\j2ee\home\application-deployments\revdb_ejb...
    Auto-deploying revdb_ejb (New server version detected)...
    java.lang.InstantiationException: Error loading class 'at.gv.brz.revdb.ejb.ejbsession.session.impl.EJBSessionBean': java.lang.NoClassDefFoundError: at.gv.brz.revdb.ejb.ejbsession.session.impl.EJBSessionBean
         void com.evermind.server.ejb.deployment.BeanDescriptor.initialize(com.evermind.server.ejb.deployment.EJBDeploymentContext)
              BeanDescriptor.java:294
         void com.evermind.server.ejb.deployment.ExposableBeanDescriptor.initialize(com.evermind.server.ejb.deployment.EJBDeploymentContext)
              ExposableBeanDescriptor.java:131
         void com.evermind.server.ejb.deployment.SessionBeanDescriptor.initialize(com.evermind.server.ejb.deployment.EJBDeploymentContext)
              SessionBeanDescriptor.java:360
         void com.evermind.server.ejb.deployment.EJBPackage.initialize(com.evermind.server.ejb.EJBContainer, com.evermind.server.administration.ApplicationInstallation)
              EJBPackage.java:650
         com.evermind.server.ejb.deployment.EJBPackage com.evermind.server.ejb.EJBPackageDeployment.getPackage()
              EJBPackageDeployment.java:673
         java.util.Map com.evermind.server.administration.ServerApplicationInstallation.finish(java.util.Map)
              ServerApplicationInstallation.java:517
         java.lang.Object java.lang.reflect.Method.invoke(java.lang.Object, java.lang.Object[])
              native code
         void com.evermind.server.rmi.RMICallHandler.run(java.lang.Thread)
              RMICallHandler.java:119
         void com.evermind.server.rmi.RMICallHandler.run()
              RMICallHandler.java:48
         void EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run()
              PooledExecutor.java:803
         void java.lang.Thread.run()
              Thread.java:484

    hi Jeff!
    I tried some different tasks.
    1.) removing all deployments (incl. app in server.xml) -> still error
    2.) manually deploying to a "virgin" container -> still error
    3.) manually deploying an old and stable version (runs on a colleages oc4j instance) -> still error
    4.) copying app-dirs + config-dir from a colleage (its his running instance) -> STILL ERROR!!
    5.) copying his whole J2EE-dir -> deployment works!
    It looks like, that one of my deployments (out of Jdeveloper with admin.jar) has kicked my container and the container kept in tilt mode (to use a little flippermachine slang ;o)
    Besides from joking, I still think it's a serious thing. I'm now going to install a whole fresh instance of Jdeveloper and OC4J. Hopefully afterwards I won't have these probs again.
    If someone @ Oracle wants to take a look at these instance (like bugsearching) dont hesitate to contact me (I'll keep both version of the OC4J, running and tilt one).
    cu
    ed

  • Problem accessing a session bean running on a different port

    Hi,
    I am using weblogic7.0 as the application server. I craeted two EJB's and
    deployed them in two ports, port 7001 and 7378. I can access the beans when I
    deploy them in the same port. But, I am having problem when EJB1 'server1' accesses
    EJB2 'server2' deployed in port 7378. Below is the code I am using to lookup the
    bean.
    Properties prop = new Properties();
    prop.put(Context.INITIAL_CONTEXT_FACTORY,
    "weblogic.jndi.WLInitialContextFactory");
    prop.put(Context.PROVIDER_URL, "t3://localhost:7378");
    Context ctx = new InitialContext(prop);
    Object objref = ctx.lookup("java:comp/env/server2");
    System.out.println("Inside the Object method "+objref);
    iHome = (server2.InsertHome) objref;
    System.out.println("Inside the iHome method "+iHome);
    mInsert=iHome.create();
    I am getting the following exception when I run the client. Can any one plaes
    help me with the problem I am facing.
    Thanks,
    Ramya.
    java.rmi.RemoteException: EJB Exception: ; nested exception is:
    java.lang.NullPointerException
    Start server side stack trace:
    java.rmi.RemoteException: EJB Exception: ; nested exception is:
    java.lang.NullPointerException
    java.lang.NullPointerException
    at server1.ConnectBean.insertName(ConnectBean.java:133)
    at server1.ConnectBean_wtb7ta_EOImpl.insertName(ConnectBean_wtb7ta_EOIm
    pl.java:45)
    at server1.ConnectBean_wtb7ta_EOImpl_WLSkel.invoke(Unknown Source)
    at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:362)
    at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServer
    Ref.java:114)
    at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:313)
    at weblogic.security.service.SecurityServiceManager.runAs(SecurityServi
    ceManager.java:785)
    at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.ja
    va:308)
    at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteReques
    t.java:30)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:153)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:134)
    End server side stack trace
    ; nested exception is:
    java.lang.NullPointerException:
    Start server side stack trace:
    java.lang.NullPointerException
    at server1.ConnectBean.insertName(ConnectBean.java:133)
    at server1.ConnectBean_wtb7ta_EOImpl.insertName(ConnectBean_wtb7ta_EOIm
    pl.java:45)
    at server1.ConnectBean_wtb7ta_EOImpl_WLSkel.invoke(Unknown Source)
    at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:362)
    at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServer
    Ref.java:114)
    at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:313)
    at weblogic.security.service.SecurityServiceManager.runAs(SecurityServi
    ceManager.java:785)
    at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.ja
    va:308)
    at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteReques
    t.java:30)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:153)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:134)
    End server side stack trace
    at weblogic.rmi.internal.BasicOutboundRequest.sendReceive(BasicOutbound
    Request.java:109)
    at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemote
    Ref.java:262)
    at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemote
    Ref.java:229)
    at server1.ConnectBean_wtb7ta_EOImpl_WLStub.insertName(Unknown Source)
    at server1.Client.example(Client.java:156)
    at server1.Client.main(Client.java:168)
    Caused by: java.lang.NullPointerException:
    Start server side stack trace:
    java.lang.NullPointerException
    at server1.ConnectBean.insertName(ConnectBean.java:133)
    at server1.ConnectBean_wtb7ta_EOImpl.insertName(ConnectBean_wtb7ta_EOIm
    pl.java:45)
    at server1.ConnectBean_wtb7ta_EOImpl_WLSkel.invoke(Unknown Source)
    at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:362)
    at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServer
    Ref.java:114)
    at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:313)
    at weblogic.security.service.SecurityServiceManager.runAs(SecurityServi
    ceManager.java:785)
    at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.ja
    va:308)
    at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteReques
    t.java:30)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:153)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:134)
    End server side stack trace

    So it looks like mInsert is null causing the NPE. I think you'll have
    to debug this one.
    -- Rob
    Ramya wrote:
    Hi Rob,
    Thanks for your relpy. Below is the method which calls methods from the EJB2.
    public void insertName(String name) throws Exception {
    Connection con = null;
    String name2="raj";
    int num=30;
    PreparedStatement ps = null;
    CallableStatement cs=null;
    String fName=null;
    try {
    System.out.println("In the insertName() before calling this.lookup()");
    this.lookUp();
    System.out.println("In the insertName() after calling this.lookup()");
    con=mInsert.getConnection();
    System.out.println("Inside the InsertName() in connectbean the value
    of connect is"+con);
    ps = con.prepareStatement("Insert into My_info values (?,?,?) ");
    ps.setString(1, name);
    ps.setString(2, "RamyaRAJ");
    ps.setInt(3,30);
    if (!(ps.executeUpdate() > 0)) {
    String error = "insertName: MyInfoBean (" + fName + ") not updated";
    throw new NoSuchEntityException (error);
    else{
    System.out.println("After calling execute upadte");
    } catch(Exception e) {
    System.out.println("There is an SQL insert exception in insertName()
    method");
    e.printStackTrace();
    throw new EJBException (e);
    } finally {
    mInsert.cleanup(con, ps);//LINE NO 133
    Line 133 (mInsert.cleanup(con, ps);) is the call to close up the SQL connection
    that is from EJB2. mInsert is the member variable of the Remote class from EJB2.
    Thanks,
    Ramya.
    Rob Woollen <[email protected]> wrote:
    That looks like a NullPointerException in your code. You'd have to show
    us line 133 of ConnectBean if you need help debugging it.
    -- Rob
    Ramya wrote:
    Hi,
    I am using weblogic7.0 as the application server. I craeted twoEJB's and
    deployed them in two ports, port 7001 and 7378. I can access the beanswhen I
    deploy them in the same port. But, I am having problem when EJB1 'server1'accesses
    EJB2 'server2' deployed in port 7378. Below is the code I am usingto lookup the
    bean.
    Properties prop = new Properties();
    prop.put(Context.INITIAL_CONTEXT_FACTORY,
    "weblogic.jndi.WLInitialContextFactory");
    prop.put(Context.PROVIDER_URL, "t3://localhost:7378");
    Context ctx = new InitialContext(prop);
    Object objref = ctx.lookup("java:comp/env/server2");
    System.out.println("Inside the Object method "+objref);
    iHome = (server2.InsertHome) objref;
    System.out.println("Inside the iHome method "+iHome);
    mInsert=iHome.create();
    I am getting the following exception when I run the client. Can anyone plaes
    help me with the problem I am facing.
    Thanks,
    Ramya.
    java.rmi.RemoteException: EJB Exception: ; nested exception is:
    java.lang.NullPointerException
    Start server side stack trace:
    java.rmi.RemoteException: EJB Exception: ; nested exception is:
    java.lang.NullPointerException
    java.lang.NullPointerException
    at server1.ConnectBean.insertName(ConnectBean.java:133)
    at server1.ConnectBean_wtb7ta_EOImpl.insertName(ConnectBean_wtb7ta_EOIm
    pl.java:45)
    at server1.ConnectBean_wtb7ta_EOImpl_WLSkel.invoke(UnknownSource)
    at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:362)
    at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServer
    Ref.java:114)
    at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:313)
    at weblogic.security.service.SecurityServiceManager.runAs(SecurityServi
    ceManager.java:785)
    at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.ja
    va:308)
    at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteReques
    t.java:30)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:153)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:134)
    End server side stack trace
    ; nested exception is:
    java.lang.NullPointerException:
    Start server side stack trace:
    java.lang.NullPointerException
    at server1.ConnectBean.insertName(ConnectBean.java:133)
    at server1.ConnectBean_wtb7ta_EOImpl.insertName(ConnectBean_wtb7ta_EOIm
    pl.java:45)
    at server1.ConnectBean_wtb7ta_EOImpl_WLSkel.invoke(UnknownSource)
    at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:362)
    at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServer
    Ref.java:114)
    at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:313)
    at weblogic.security.service.SecurityServiceManager.runAs(SecurityServi
    ceManager.java:785)
    at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.ja
    va:308)
    at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteReques
    t.java:30)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:153)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:134)
    End server side stack trace
    at weblogic.rmi.internal.BasicOutboundRequest.sendReceive(BasicOutbound
    Request.java:109)
    at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemote
    Ref.java:262)
    at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemote
    Ref.java:229)
    at server1.ConnectBean_wtb7ta_EOImpl_WLStub.insertName(UnknownSource)
    at server1.Client.example(Client.java:156)
    at server1.Client.main(Client.java:168)
    Caused by: java.lang.NullPointerException:
    Start server side stack trace:
    java.lang.NullPointerException
    at server1.ConnectBean.insertName(ConnectBean.java:133)
    at server1.ConnectBean_wtb7ta_EOImpl.insertName(ConnectBean_wtb7ta_EOIm
    pl.java:45)
    at server1.ConnectBean_wtb7ta_EOImpl_WLSkel.invoke(UnknownSource)
    at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:362)
    at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServer
    Ref.java:114)
    at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:313)
    at weblogic.security.service.SecurityServiceManager.runAs(SecurityServi
    ceManager.java:785)
    at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.ja
    va:308)
    at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteReques
    t.java:30)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:153)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:134)
    End server side stack trace

Maybe you are looking for

  • Calling report application from jsp

    Hi, I am designing a JSP that captures search parameters. The user will enter words contained in a company name and product codes. This triggers the jsp to display all matches on the same page. My question is how do I call a portal report application

  • How to open word document form html container url iam getting internal_error while opening file

    Hi all, By using below code i am able to download word document file from html container. But before downloading i need edit these document to add Macro. I am unable to open word document. CREATE OBJECT G_HTML_CONTAINER       EXPORTING         CONTAI

  • Boot-up & BIOS probs - H-P Pavilion P6 2130ef - Windows 7 Home Premium 64 bit

    Starting up my PC has become an exercise in frustration.. I press the start on/off button and the screen stays black - nothing happens. It's unresponsive to ESC or F11 (to try and get into Recovery manager) or Cont/Alt/Del. It's only by pressing the

  • JDialog on top of full screen JFrame disappears

    I have a problem with a JDialog on top of a full screen JFrame, namely the JDialog kind of disappears when displayed (it bleeds through). I use JRE 1.6.0_03 on Windows. This does not happen under the same version on Linux. I'm attaching the code belo

  • Hard drive recommendation

    I have a 27' iMac (Late 2009) 2.8 Ghz i7 running Lion 10.7.4 with 1 TB hard drive. I am running out of hard drive space mostly because of movies and music I have on iTunes.  I am wanting to put all my iTunes media on an external hard drive to free up