EJB-WEBLOGIC

we are migration our EJB from JBOSS to Weblogic 10.3.5
in JBOSS application context is set to ServiceBean as followi
WEBLOGIC-EJB
But the same is not working in Weblogic and throwning an exception No Unique Bean found ApplicationContext.
how to resolve this issue in weblogic server. My question is how to inject Application Context to service bean object in EJB for weblogic 10.3.5
my EAR has a WAR, service.ejb3 ,META-INF/weblogic-ebj-jar.xml META-INF/applicationContext-Spring.xml META-INF/applicatioinContext.xml

what if your lookup is for java:comp/env/ejb/Hello?

Similar Messages

  • Is it possible to run  EJB (  Weblogic server 7.0) on win XP professional

    Hi,
    i am using win XP Professional platform. Is it possible to run EJB (WEBLOGIC SERVER 7.0) on this platform. IF not what are the other plug in needed to run WEBLOGIC SERVER on WIN XP Prof ?.

    Yes, though currently BEA hasn't certified it for XP.

  • Trying to look up a LOCAL EJB (Weblogic 8.1)

    Hi,
    I'm trying to look up a LOCAL EJB (Weblogic 8.1):
    try
    Context ct = new InitialContext();
    Object o = ct.lookup("*ejbSecurityDataLocalHelper*");
    catch(...)
    I systematically get the following exception:
    Caused by: javax.naming.LinkException: Root exception is javax.naming.NameNotFoundException: While trying to look up /app/ejb/AEX_JRK_security_EJB.jar#SecurityDataHelper/local-home in /app/ejb/ISL_MSD_mktdata_general_EJB.jar#MarketDataGeneralManager.; remaining name '/app/ejb/AEX_JRK_security_EJB/jar#SecurityDataHelper/local-home'; Link Remaining Name: 'java:app/ejb/AEX_JRK_security_EJB.jar#SecurityDataHelper/local-home'
    Where SecurityDataHelper is the Local EJB, who's called from MarketDataGeneralManager EJB.
    I realized that the Weblogic JNDI tree shows a red dot next to the name SecurityDataHelperLocalHome: as the other names are not red, I could guess there was something wrong at deployment... buy deployment logs are OK. When I tryied to test the EJB via the Weblogic console there was a message "The EJB SecurityDataHelper has not been tested successfully. There was a problem determining the JNDI Name of the given bean. "
    My ejb-jar.xml looks like this:
    <session>
    <ejb-name>SecurityDataHelper</ejb-name>
    <local-home>com.MyLocalHome</local-home>
    <local>com.MyLocalObject</local>
    <ejb-class>com.MyBean</ejb-class>
    <session-type>Stateless</session-type>
    <transaction-type>Container</transaction-type>
    </session>
    and my weblogic-ejb-jar.xml:
    <weblogic-enterprise-bean>
    <ejb-name>SecurityDataHelper</ejb-name>
    <stateless-session-descriptor>
    </stateless-session-descriptor>
    <enable-call-by-reference>True</enable-call-by-reference>
    <local-jndi-name>ejbSecurityDataLocalHelper</local-jndi-name>
    </weblogic-enterprise-bean>
    What I am doing wrong???

    Hi Dan,
    As u have targeted the ConnectionFactory to "soa_server1" which is running on "realHostName:7001" ....Can u please check from the AdminConsole that the JNDI name ""jms/b2b/B2BQueueConnectionFactory" is present in the JNDI Tree?
    AdminConsole---->Servers---soa_server1 (click) ---> in this general configuration page you will see a link "View JNDI Tree" please ckick on that link to see the JNDI tree entries.
    If you dont see any JNDI entry there then it means there is something wrong while setting up the Connection Factory in that case please refer to the Screenshots of Creating and Targeting the Connection Factory: *http://middlewaremagic.com/weblogic/?p=1987*
    Thanks
    Jay SenSharma
    *http://middlewaremagic.com/weblogic (Middleware magic Is Here)*

  • Java Generics in Ejbs WebLogic 9.2 MP1 WindowsXP Sun JDK

    Hi guys,
    I tried to deploy our application on Weblogic Server 9.2 MP1 (Windows, Sun JDK) and during deployment I have this error see bellow.
    Can somebody tell me what is the problem with generics and EJB compiler?
    Is necessary to add any path or change any server settings?
    Thanks for help
    Robert
    location: interface
    ...daoadapter_DaoAdapter_rge4uk_Intf
    public void batchPersist(java.util.List<T> arg0);
    ^
    ...daoadapter_DaoAdapter_rge4uk_Intf.java:20: cannot find symbol
    symbol : class T
    location: interface
    2 errors
    at weblogic.utils.compiler.CompilerInvoker.compileMaybeExit(CompilerInvoker.java:435)
    at weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:295)
    at weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:303)
    at weblogic.ejb.container.ejbc.EJBCompiler.doCompile(EJBCompiler.java:309)
    at weblogic.ejb.container.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:497)
    at weblogic.ejb.container.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:464)
    at weblogic.ejb.container.deployer.EJBDeployer.runEJBC(EJBDeployer.java:430)
    at weblogic.ejb.container.deployer.EJBDeployer.compileJar(EJBDeployer.java:752)
    at weblogic.ejb.container.deployer.EJBDeployer.compileIfNecessary(EJBDeployer.java:655)
    at weblogic.ejb.container.deployer.EJBDeployer.prepare(EJBDeployer.java:1199)
    at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:354)
    at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93)
    at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:360)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
    at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:56)
    at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:46)
    at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:615)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
    at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191)
    at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:147)
    at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:61)
    at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperatio
    n.java:189)
    at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:87)
    at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
    at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:718)
    at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1185)
    at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:247)
    at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:15
    7)
    at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(Deploymen
    tReceiverCallbackDeliverer.java:157)
    at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiv
    erCallbackDeliverer.java:12)
    at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCal
    lbackDeliverer.java:45)
    at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)

    Thanks Matt for your answer.
    But I don't finish my testing :)
    I tried to deploy the same application on Weblogic 9.2 MP2 and then MP3 (sun jdk domain) and I didn't have problem with generics (application was correctly deployed and running).
    Then something was fixed in newer versions or may be bea guys support more then is in EJB 2.x specification.
    My next step, I'll try to deploy it on Jrockit domain and I give a note to conference what happen, may be it can help to somebody else.
    Thanks
    Robert

  • Java Mail/EJB/WebLogic/weblogicSP6 "No Such Provider Exception"

    Hi,
    My application that is coded to send e-mail is not performing at all.
    Application architecture is as follows:
    1)JSP-EJB on Web Logic App server and
    2)SMTP Host is IIS server and its SMTP service.
    3)Using Java Mail API and installed Service Pack 6 of WebLogic that supports Java Mail API
    4)EJB Programs coded as per the Sun JavaMail API documentation.
    5)Send Mail occuring in the EJB.
    Runtime Error: "No such provider exception"
    Could u help me by instructing me about:
    1)weblogic service pack installation.
    2)sample ejb
    PS:Same code on a simple java class fired on command line is executing without any exception. Wheras in an EJB on Weblogic is throwing the exception.

    That error you are seeing typically comes from JavaMail being unable to
    contact the SMTP host. Are you sure that you are a valid user/permitted to
    access the mailer?
    Thanks,
    Michael
    Michael Girdley
    BEA Systems Inc
    "Omm" <[email protected]> wrote in message
    news:3a3cd390$[email protected]..
    >
    Hi,
    My application that is coded to send e-mail is not performing at all.
    Application architecture is as follows:
    1)JSP-EJB on Web Logic App server and
    2)SMTP Host is IIS server and its SMTP service.
    3)Using Java Mail API and installed Service Pack 6 of WebLogic thatsupports Java Mail API
    4)EJB Programs coded as per the Sun JavaMail API documentation.
    5)Send Mail occuring in the EJB.
    Runtime Error: "No such provider exception"
    Could u help me by instructing me about:
    1)weblogic service pack installation.
    2)sample ejb
    PS:Same code on a simple java class fired on command line is executingwithout any exception. Wheras in an EJB on Weblogic is throwing the
    exception.
    >
    >

  • Using SQLJ in Session EJB  (WebLogic 6.1) - connection giving ClassCastError

    Hi All
    I have one SQLJ file which i have translated to a .java file and , its contents ( methods) have ben pasted in a Session bean , which is deployed in Weblogic 6.1 App Server .
    Now in Session bean i am using the jndi lookup of my datasource in Weblogic and creating a conection to the database .
    with this connection the normal jdbc methods connects to the databse , but the sqlj method gives a class cast error when i try to allocate the Connection Object to the DefaultContext .
    *********************** CODE SNIP ********************
    new sqlj.runtime.ref.DefaultContext m_dx = new sqlj.runtime.ref.DefaultContext(conn);
    sqlj.runtime.ref.DefaultContext.setDefaultContext(m_dx);
    "conn"is the jndi dsn's
    DataSourse.getConnection ();
    /*In the Method */
    sqlj.runtime.ConnectionContext __sJT_connCtx = sqlj.runtime.ref.DefaultContext.getDefaultContext();
    the bean compiles , and is deployed sucessfully , and after lookup the conn and m_dx objects are created sucessfully , but when the sqlj method runs it gives a class cast exception .
    java.lang.ClassCastException: weblogic.jdbc.rmi.SerialConnection
    Is it that Weblogic will not support SQLJ translated code ?
    Please help me out , Will i be able to use the Good features of SQLJ in my EJB beans to be Deployed in Weblogic 6.1 Application Server .
    Thanks

    Hi Nicolas,
    Have you tried to turn on testOnReserve setting of the coneection pool?
    Regards,
    "Nicolas Devos" <[email protected]> wrote in message
    news:3c5fa916$[email protected]..
    >
    Hi,
    I am using weblogic 6.1 and oracle 8.1.6, and experiences
    problems with connections pools and database crash.
    When the database server crashes during an EJB transactions,
    the connection used by that transaction seems to be lost and
    is never rebuilt when the database server restarts, therefore
    the number of connections within the pool shrinks thoroughly
    if I have several connections used while the database crashes
    or is shutdown for maintenance.
    If this db crash takes time to recover, all connections
    are destroyed and the pool become unusable.
    As soon as all connections have been 'destroyed' I have
    the following exception:
    'connection pool - none available' when trying to get
    a connection.
    When I restart the database server, the pool does not rebuilt
    itself.
    (I am using a test table to test the presence of the database
    with a frequency set to 60s)
    I did the same operation without EJB transactions and the pool
    could rebuilt itself after the database has been restarted.
    I had that problem with weblogic 6.0 already and in the
    release notes of 6.0_sp2, 2 issues are fixed concerning
    the pool fail-over: 044223 and 041793.
    I would like to know if these issues are fixed in 6.1 as well,
    and if they are related to my problem (Their description is
    quite short).
    Thank you
    Nicolas

  • Unable to deploy EJB - weblogic,management.ApplicationException

    I am getting the following error when i deploy an ear file in WL 7.0 with MySQL
    at the backend
    There is one entity bean and one servlet in the application.
    can any body tell what mistake i could be making ?
    thanks in advance
    -vasanth
    error log
    =====
    weblogic.management.ApplicationException: Prepare failed. Task Id = null
    Module Name: titan_ejbs.jar, Error: Exception preparing module: EJBModule(titan_ejbs.jar,status=NEW)
    Unable to deploy EJB: titan_ejbs.jar from titan_ejbs.jar:
    java.lang.NullPointerException
         at weblogic.ejb20.deployer.CompositeMBeanDescriptor.getPersistenceUseIdentifier(CompositeMBeanDescriptor.java:1446)
         at weblogic.ejb20.deployer.CMPInfoImpl.<init>(CMPInfoImpl.java:104)
         at weblogic.ejb20.deployer.EntityBeanInfoImpl.<init>(EntityBeanInfoImpl.java:135)
         at weblogic.ejb20.deployer.BeanInfoImpl.createBeanInfoImpl(BeanInfoImpl.java:349)
         at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.initializeBeanInfos(MBeanDeploymentInfoImpl.java:438)
         at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.<init>(MBeanDeploymentInfoImpl.java:165)
         at weblogic.ejb20.ejbc.EJBCompiler.setupEJB(EJBCompiler.java:151)
         at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:332)
         at weblogic.ejb20.deployer.EJBDeployer.runEJBC(EJBDeployer.java:489)
         at weblogic.ejb20.deployer.EJBDeployer.compileEJB(EJBDeployer.java:819)
         at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1268)
         at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:232)
         at weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContainer.java:1570)
         at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:737)
         at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:555)
         at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:458)
         at weblogic.management.deploy.slave.SlaveDeployer.prepareAllStagedApplications(SlaveDeployer.java:490)
         at weblogic.management.deploy.slave.SlaveDeployer.initialize(SlaveDeployer.java:253)
         at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.initialize(DeploymentManagerServerLifeCycleImpl.java:150)
         at weblogic.t3.srvr.ServerLifeCycleList.initialize(ServerLifeCycleList.java:54)
         at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:782)
         at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:594)
         at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:282)
         at weblogic.Server.main(Server.java:32)
         at weblogic.ejb20.ejbc.EJBCompiler.setupEJB(EJBCompiler.java:155)
         at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:332)
         at weblogic.ejb20.deployer.EJBDeployer.runEJBC(EJBDeployer.java:489)
         at weblogic.ejb20.deployer.EJBDeployer.compileEJB(EJBDeployer.java:819)
         at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1268)
         at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:232)
         at weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContainer.java:1570)
         at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:737)
         at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:555)
         at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:458)
         at weblogic.management.deploy.slave.SlaveDeployer.prepareAllStagedApplications(SlaveDeployer.java:490)
         at weblogic.management.deploy.slave.SlaveDeployer.initialize(SlaveDeployer.java:253)
         at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.initialize(DeploymentManagerServerLifeCycleImpl.java:150)
         at weblogic.t3.srvr.ServerLifeCycleList.initialize(ServerLifeCycleList.java:54)
         at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:782)
         at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:594)
         at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:282)
         at weblogic.Server.main(Server.java:32)
    TargetException:
    Unable to deploy EJB: titan_ejbs.jar from titan_ejbs.jar:
    java.lang.NullPointerException
         at weblogic.ejb20.deployer.CompositeMBeanDescriptor.getPersistenceUseIdentifier(CompositeMBeanDescriptor.java:1446)
         at weblogic.ejb20.deployer.CMPInfoImpl.<init>(CMPInfoImpl.java:104)
         at weblogic.ejb20.deployer.EntityBeanInfoImpl.<init>(EntityBeanInfoImpl.java:135)
         at weblogic.ejb20.deployer.BeanInfoImpl.createBeanInfoImpl(BeanInfoImpl.java:349)
         at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.initializeBeanInfos(MBeanDeploymentInfoImpl.java:438)
         at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.<init>(MBeanDeploymentInfoImpl.java:165)
         at weblogic.ejb20.ejbc.EJBCompiler.setupEJB(EJBCompiler.java:151)
         at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:332)
         at weblogic.ejb20.deployer.EJBDeployer.runEJBC(EJBDeployer.java:489)
         at weblogic.ejb20.deployer.EJBDeployer.compileEJB(EJBDeployer.java:819)
         at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1268)
         at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:232)
         at weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContainer.java:1570)
         at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:737)
         at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:555)
         at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:458)
         at weblogic.management.deploy.slave.SlaveDeployer.prepareAllStagedApplications(SlaveDeployer.java:490)
         at weblogic.management.deploy.slave.SlaveDeployer.initialize(SlaveDeployer.java:253)
         at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.initialize(DeploymentManagerServerLifeCycleImpl.java:150)
         at weblogic.t3.srvr.ServerLifeCycleList.initialize(ServerLifeCycleList.java:54)
         at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:782)
         at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:594)
         at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:282)
         at weblogic.Server.main(Server.java:32)
         at weblogic.ejb20.ejbc.EJBCompiler.setupEJB(EJBCompiler.java:155)
         at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:332)
         at weblogic.ejb20.deployer.EJBDeployer.runEJBC(EJBDeployer.java:489)
         at weblogic.ejb20.deployer.EJBDeployer.compileEJB(EJBDeployer.java:819)
         at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1268)
         at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:232)
         at weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContainer.java:1570)
         at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:737)
         at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:555)
         at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:458)
         at weblogic.management.deploy.slave.SlaveDeployer.prepareAllStagedApplications(SlaveDeployer.java:490)
         at weblogic.management.deploy.slave.SlaveDeployer.initialize(SlaveDeployer.java:253)
         at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.initialize(DeploymentManagerServerLifeCycleImpl.java:150)
         at weblogic.t3.srvr.ServerLifeCycleList.initialize(ServerLifeCycleList.java:54)
         at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:782)
         at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:594)
         at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:282)
         at weblogic.Server.main(Server.java:32)
         at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:744)
         at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:555)
         at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:458)
         at weblogic.management.deploy.slave.SlaveDeployer.prepareAllStagedApplications(SlaveDeployer.java:490)
         at weblogic.management.deploy.slave.SlaveDeployer.initialize(SlaveDeployer.java:253)
         at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.initialize(DeploymentManagerServerLifeCycleImpl.java:150)
         at weblogic.t3.srvr.ServerLifeCycleList.initialize(ServerLifeCycleList.java:54)
         at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:782)
         at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:594)
         at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:282)

    Add a <persistence-use> element to weblogic-ejb-jar.xml deployment descriptor.
    <persistence>
    <persistence-use>     
    <type-identifier>WebLogic_CMP_RDBMS</type-identifier>     
    <type-version>5.1.0</type-version>     
    <type-storage>META-INF/weblogic-cmp-jar.xml</type-storage>
    </persistence-use>
    </persistence>
    "vasanth" <[email protected]> wrote:
    >
    I am getting the following error when i deploy an ear file in WL 7.0
    with MySQL
    at the backend
    There is one entity bean and one servlet in the application.
    can any body tell what mistake i could be making ?
    thanks in advance
    -vasanth
    error log
    =====
    weblogic.management.ApplicationException: Prepare failed. Task Id = null
    Module Name: titan_ejbs.jar, Error: Exception preparing module: EJBModule(titan_ejbs.jar,status=NEW)
    Unable to deploy EJB: titan_ejbs.jar from titan_ejbs.jar:
    java.lang.NullPointerException
         at weblogic.ejb20.deployer.CompositeMBeanDescriptor.getPersistenceUseIdentifier(CompositeMBeanDescriptor.java:1446)
         at weblogic.ejb20.deployer.CMPInfoImpl.<init>(CMPInfoImpl.java:104)
         at weblogic.ejb20.deployer.EntityBeanInfoImpl.<init>(EntityBeanInfoImpl.java:135)
         at weblogic.ejb20.deployer.BeanInfoImpl.createBeanInfoImpl(BeanInfoImpl.java:349)
         at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.initializeBeanInfos(MBeanDeploymentInfoImpl.java:438)
         at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.<init>(MBeanDeploymentInfoImpl.java:165)
         at weblogic.ejb20.ejbc.EJBCompiler.setupEJB(EJBCompiler.java:151)
         at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:332)
         at weblogic.ejb20.deployer.EJBDeployer.runEJBC(EJBDeployer.java:489)
         at weblogic.ejb20.deployer.EJBDeployer.compileEJB(EJBDeployer.java:819)
         at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1268)
         at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:232)
         at weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContainer.java:1570)
         at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:737)
         at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:555)
         at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:458)
         at weblogic.management.deploy.slave.SlaveDeployer.prepareAllStagedApplications(SlaveDeployer.java:490)
         at weblogic.management.deploy.slave.SlaveDeployer.initialize(SlaveDeployer.java:253)
         at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.initialize(DeploymentManagerServerLifeCycleImpl.java:150)
         at weblogic.t3.srvr.ServerLifeCycleList.initialize(ServerLifeCycleList.java:54)
         at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:782)
         at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:594)
         at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:282)
         at weblogic.Server.main(Server.java:32)
         at weblogic.ejb20.ejbc.EJBCompiler.setupEJB(EJBCompiler.java:155)
         at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:332)
         at weblogic.ejb20.deployer.EJBDeployer.runEJBC(EJBDeployer.java:489)
         at weblogic.ejb20.deployer.EJBDeployer.compileEJB(EJBDeployer.java:819)
         at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1268)
         at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:232)
         at weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContainer.java:1570)
         at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:737)
         at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:555)
         at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:458)
         at weblogic.management.deploy.slave.SlaveDeployer.prepareAllStagedApplications(SlaveDeployer.java:490)
         at weblogic.management.deploy.slave.SlaveDeployer.initialize(SlaveDeployer.java:253)
         at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.initialize(DeploymentManagerServerLifeCycleImpl.java:150)
         at weblogic.t3.srvr.ServerLifeCycleList.initialize(ServerLifeCycleList.java:54)
         at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:782)
         at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:594)
         at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:282)
         at weblogic.Server.main(Server.java:32)
    TargetException:
    Unable to deploy EJB: titan_ejbs.jar from titan_ejbs.jar:
    java.lang.NullPointerException
         at weblogic.ejb20.deployer.CompositeMBeanDescriptor.getPersistenceUseIdentifier(CompositeMBeanDescriptor.java:1446)
         at weblogic.ejb20.deployer.CMPInfoImpl.<init>(CMPInfoImpl.java:104)
         at weblogic.ejb20.deployer.EntityBeanInfoImpl.<init>(EntityBeanInfoImpl.java:135)
         at weblogic.ejb20.deployer.BeanInfoImpl.createBeanInfoImpl(BeanInfoImpl.java:349)
         at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.initializeBeanInfos(MBeanDeploymentInfoImpl.java:438)
         at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.<init>(MBeanDeploymentInfoImpl.java:165)
         at weblogic.ejb20.ejbc.EJBCompiler.setupEJB(EJBCompiler.java:151)
         at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:332)
         at weblogic.ejb20.deployer.EJBDeployer.runEJBC(EJBDeployer.java:489)
         at weblogic.ejb20.deployer.EJBDeployer.compileEJB(EJBDeployer.java:819)
         at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1268)
         at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:232)
         at weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContainer.java:1570)
         at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:737)
         at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:555)
         at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:458)
         at weblogic.management.deploy.slave.SlaveDeployer.prepareAllStagedApplications(SlaveDeployer.java:490)
         at weblogic.management.deploy.slave.SlaveDeployer.initialize(SlaveDeployer.java:253)
         at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.initialize(DeploymentManagerServerLifeCycleImpl.java:150)
         at weblogic.t3.srvr.ServerLifeCycleList.initialize(ServerLifeCycleList.java:54)
         at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:782)
         at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:594)
         at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:282)
         at weblogic.Server.main(Server.java:32)
         at weblogic.ejb20.ejbc.EJBCompiler.setupEJB(EJBCompiler.java:155)
         at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:332)
         at weblogic.ejb20.deployer.EJBDeployer.runEJBC(EJBDeployer.java:489)
         at weblogic.ejb20.deployer.EJBDeployer.compileEJB(EJBDeployer.java:819)
         at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1268)
         at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:232)
         at weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContainer.java:1570)
         at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:737)
         at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:555)
         at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:458)
         at weblogic.management.deploy.slave.SlaveDeployer.prepareAllStagedApplications(SlaveDeployer.java:490)
         at weblogic.management.deploy.slave.SlaveDeployer.initialize(SlaveDeployer.java:253)
         at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.initialize(DeploymentManagerServerLifeCycleImpl.java:150)
         at weblogic.t3.srvr.ServerLifeCycleList.initialize(ServerLifeCycleList.java:54)
         at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:782)
         at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:594)
         at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:282)
         at weblogic.Server.main(Server.java:32)
         at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:744)
         at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:555)
         at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:458)
         at weblogic.management.deploy.slave.SlaveDeployer.prepareAllStagedApplications(SlaveDeployer.java:490)
         at weblogic.management.deploy.slave.SlaveDeployer.initialize(SlaveDeployer.java:253)
         at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.initialize(DeploymentManagerServerLifeCycleImpl.java:150)
         at weblogic.t3.srvr.ServerLifeCycleList.initialize(ServerLifeCycleList.java:54)
         at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:782)
         at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:594)
         at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:282)

  • Applet -ejb ; weblogic.jar

    Hi,
    <b>I am trying to access EJB from an applet thro' ejb-client.jar. It works fine if I include weblogic.jar in the applet archive but it throws a corba exception if I use wlclient.jar and wljmsclient.jar instead of weblogic.jar in the archive. As weblogic.jar is too huge <b>I want to use thin clients</b>. Could someone help me with this exception. I am using WLS8.1_sp4; jdk 1.4.2_05 and ie6 with latest jvm. Both applet and ejb are deployed in same localhost</b>
    com.sun.corba.se.internal.iiop.ConnectionTable(Thread[thread applet-informatics.inventory.plates.editor.PlateMapEditor.class,
    4,file:/C:/projects/perforce/java/PlateMapViewer/-threadGroup]): Client get called: host = localhost port = 7001
    com.sun.corba.se.internal.iiop.ConnectionTable(Thread[thread applet-informatics.inventory.plates.editor.PlateMapEditor.class,
    4,file:/C:/projects/perforce/java/PlateMapViewer/-threadGroup]): Creating new connection Connection[type=IIOP_CLEAR_TEXT remo
    te_host=localhost remote_port=7001 state=ESTABLISHED]
    com.sun.corba.se.internal.iiop.MessageMediator(Thread[JavaIDL Reader for localhost:7001,4,ORB ThreadGroup]): Creating message
    from stream
    com.sun.corba.se.internal.iiop.ConnectionTable(Thread[thread applet-informatics.inventory.plates.editor.PlateMapEditor.class,
    4,file:/C:/projects/perforce/java/PlateMapViewer/-threadGroup]): Succesfully created socket for new connection
    com.sun.corba.se.internal.iiop.MessageMediator(Thread[JavaIDL Reader for localhost:7001,4,ORB ThreadGroup]): Reading the mess
    age fully, size =1204
    com.sun.corba.se.internal.iiop.MessageMediator(Thread[JavaIDL Reader for localhost:7001,4,ORB ThreadGroup]): Handling GIOP 1.
    0 LocateReply
    com.sun.corba.se.internal.iiop.IIOPInputStream(Thread[JavaIDL Reader for localhost:7001,4,ORB ThreadGroup]): Constructing IIO
    PInputStream object
    com.sun.corba.se.internal.iiop.IIOPInputStream(Thread[JavaIDL Reader for localhost:7001,4,ORB ThreadGroup]): Setting the time
    stamp
    com.sun.corba.se.internal.iiop.MessageMediator(Thread[JavaIDL Reader for localhost:7001,4,ORB ThreadGroup]): Creating message
    from stream
    com.sun.corba.se.internal.iiop.ConnectionTable(Thread[thread applet-informatics.inventory.plates.editor.PlateMapEditor.class,
    4,file:/C:/projects/perforce/java/PlateMapViewer/-threadGroup]): Client get called: host = 172.16.65.14 port = 7001
    com.sun.corba.se.internal.iiop.ConnectionTable(Thread[thread applet-informatics.inventory.plates.editor.PlateMapEditor.class,
    4,file:/C:/projects/perforce/java/PlateMapViewer/-threadGroup]): Creating new connection Connection[type=IIOP_CLEAR_TEXT remo
    te_host=172.16.65.14 remote_port=7001 state=ESTABLISHED]
    com.sun.corba.se.internal.iiop.MessageMediator(Thread[JavaIDL Reader for 172.16.65.14:7001,4,ORB ThreadGroup]): Creating mess
    age from stream
    com.sun.corba.se.internal.iiop.ConnectionTable(Thread[thread applet-informatics.inventory.plates.editor.PlateMapEditor.class,
    4,file:/C:/projects/perforce/java/PlateMapViewer/-threadGroup]): Succesfully created socket for new connection
    com.sun.corba.se.internal.iiop.GIOPImpl(Thread[thread applet-informatics.inventory.plates.editor.PlateMapEditor.class,4,file:
    /C:/projects/perforce/java/PlateMapViewer/-threadGroup]): getEndpoint(IIOP_CLEAR_TEXT, 0, null)
    com.sun.corba.se.internal.iiop.GIOPImpl(Thread[thread applet-informatics.inventory.plates.editor.PlateMapEditor.class,4,file:
    /C:/projects/perforce/java/PlateMapViewer/-threadGroup]): createListener( socketType = IIOP_CLEAR_TEXT port = 0 )
    javax.naming.NamingException: Unhandled exception in lookup [Root exception is org.omg.CORBA.MARSHAL:   vmcid: SUN  minor cod
    e: 217 completed: Maybe]
    at weblogic.corba.j2ee.naming.Utils.wrapNamingException(Utils.java:81)
    at weblogic.corba.j2ee.naming.ContextImpl.lookup(ContextImpl.java:237)
    at weblogic.corba.j2ee.naming.ContextImpl.lookup(ContextImpl.java:171)
    at javax.naming.InitialContext.lookup(InitialContext.java:347)
    at informatics.inventory.plates.editor.EJBPlateMapDAO.<init>(Unknown Source)
    at informatics.inventory.plates.editor.PlateMapEditor.init(Unknown Source)
    at sun.applet.AppletPanel.run(AppletPanel.java:353)
    at java.lang.Thread.run(Thread.java:534)
    Caused by: org.omg.CORBA.MARSHAL: vmcid: SUN minor code: 217 completed: Maybe
    at com.sun.corba.se.internal.iiop.CDROutputStream_1_0.write_wstring(CDROutputStream_1_0.java:464)
    at com.sun.corba.se.internal.iiop.CDROutputStream.write_wstring(CDROutputStream.java:189)
    at weblogic.corba.cos.naming.NamingContextAnyPackage.WNameComponentHelper.write(WNameComponentHelper.java:79)
    at weblogic.corba.cos.naming.NamingContextAnyPackage.WNameHelper.write(WNameHelper.java:59)
    at weblogic.corba.cos.naming._NamingContextAnyStub.resolve_any(_NamingContextAnyStub.java:79)
    at weblogic.corba.j2ee.naming.ContextImpl.lookup(ContextImpl.java:213)
    ... 6 more

    Hi,
    <b>I am trying to access EJB from an applet thro' ejb-client.jar. It works fine if I include weblogic.jar in the applet archive but it throws a corba exception if I use wlclient.jar and wljmsclient.jar instead of weblogic.jar in the archive. As weblogic.jar is too huge <b>I want to use thin clients</b>. Could someone help me with this exception. I am using WLS8.1_sp4; jdk 1.4.2_05 and ie6 with latest jvm. Both applet and ejb are deployed in same localhost</b>
    com.sun.corba.se.internal.iiop.ConnectionTable(Thread[thread applet-informatics.inventory.plates.editor.PlateMapEditor.class,
    4,file:/C:/projects/perforce/java/PlateMapViewer/-threadGroup]): Client get called: host = localhost port = 7001
    com.sun.corba.se.internal.iiop.ConnectionTable(Thread[thread applet-informatics.inventory.plates.editor.PlateMapEditor.class,
    4,file:/C:/projects/perforce/java/PlateMapViewer/-threadGroup]): Creating new connection Connection[type=IIOP_CLEAR_TEXT remo
    te_host=localhost remote_port=7001 state=ESTABLISHED]
    com.sun.corba.se.internal.iiop.MessageMediator(Thread[JavaIDL Reader for localhost:7001,4,ORB ThreadGroup]): Creating message
    from stream
    com.sun.corba.se.internal.iiop.ConnectionTable(Thread[thread applet-informatics.inventory.plates.editor.PlateMapEditor.class,
    4,file:/C:/projects/perforce/java/PlateMapViewer/-threadGroup]): Succesfully created socket for new connection
    com.sun.corba.se.internal.iiop.MessageMediator(Thread[JavaIDL Reader for localhost:7001,4,ORB ThreadGroup]): Reading the mess
    age fully, size =1204
    com.sun.corba.se.internal.iiop.MessageMediator(Thread[JavaIDL Reader for localhost:7001,4,ORB ThreadGroup]): Handling GIOP 1.
    0 LocateReply
    com.sun.corba.se.internal.iiop.IIOPInputStream(Thread[JavaIDL Reader for localhost:7001,4,ORB ThreadGroup]): Constructing IIO
    PInputStream object
    com.sun.corba.se.internal.iiop.IIOPInputStream(Thread[JavaIDL Reader for localhost:7001,4,ORB ThreadGroup]): Setting the time
    stamp
    com.sun.corba.se.internal.iiop.MessageMediator(Thread[JavaIDL Reader for localhost:7001,4,ORB ThreadGroup]): Creating message
    from stream
    com.sun.corba.se.internal.iiop.ConnectionTable(Thread[thread applet-informatics.inventory.plates.editor.PlateMapEditor.class,
    4,file:/C:/projects/perforce/java/PlateMapViewer/-threadGroup]): Client get called: host = 172.16.65.14 port = 7001
    com.sun.corba.se.internal.iiop.ConnectionTable(Thread[thread applet-informatics.inventory.plates.editor.PlateMapEditor.class,
    4,file:/C:/projects/perforce/java/PlateMapViewer/-threadGroup]): Creating new connection Connection[type=IIOP_CLEAR_TEXT remo
    te_host=172.16.65.14 remote_port=7001 state=ESTABLISHED]
    com.sun.corba.se.internal.iiop.MessageMediator(Thread[JavaIDL Reader for 172.16.65.14:7001,4,ORB ThreadGroup]): Creating mess
    age from stream
    com.sun.corba.se.internal.iiop.ConnectionTable(Thread[thread applet-informatics.inventory.plates.editor.PlateMapEditor.class,
    4,file:/C:/projects/perforce/java/PlateMapViewer/-threadGroup]): Succesfully created socket for new connection
    com.sun.corba.se.internal.iiop.GIOPImpl(Thread[thread applet-informatics.inventory.plates.editor.PlateMapEditor.class,4,file:
    /C:/projects/perforce/java/PlateMapViewer/-threadGroup]): getEndpoint(IIOP_CLEAR_TEXT, 0, null)
    com.sun.corba.se.internal.iiop.GIOPImpl(Thread[thread applet-informatics.inventory.plates.editor.PlateMapEditor.class,4,file:
    /C:/projects/perforce/java/PlateMapViewer/-threadGroup]): createListener( socketType = IIOP_CLEAR_TEXT port = 0 )
    javax.naming.NamingException: Unhandled exception in lookup [Root exception is org.omg.CORBA.MARSHAL:   vmcid: SUN  minor cod
    e: 217 completed: Maybe]
    at weblogic.corba.j2ee.naming.Utils.wrapNamingException(Utils.java:81)
    at weblogic.corba.j2ee.naming.ContextImpl.lookup(ContextImpl.java:237)
    at weblogic.corba.j2ee.naming.ContextImpl.lookup(ContextImpl.java:171)
    at javax.naming.InitialContext.lookup(InitialContext.java:347)
    at informatics.inventory.plates.editor.EJBPlateMapDAO.<init>(Unknown Source)
    at informatics.inventory.plates.editor.PlateMapEditor.init(Unknown Source)
    at sun.applet.AppletPanel.run(AppletPanel.java:353)
    at java.lang.Thread.run(Thread.java:534)
    Caused by: org.omg.CORBA.MARSHAL: vmcid: SUN minor code: 217 completed: Maybe
    at com.sun.corba.se.internal.iiop.CDROutputStream_1_0.write_wstring(CDROutputStream_1_0.java:464)
    at com.sun.corba.se.internal.iiop.CDROutputStream.write_wstring(CDROutputStream.java:189)
    at weblogic.corba.cos.naming.NamingContextAnyPackage.WNameComponentHelper.write(WNameComponentHelper.java:79)
    at weblogic.corba.cos.naming.NamingContextAnyPackage.WNameHelper.write(WNameHelper.java:59)
    at weblogic.corba.cos.naming._NamingContextAnyStub.resolve_any(_NamingContextAnyStub.java:79)
    at weblogic.corba.j2ee.naming.ContextImpl.lookup(ContextImpl.java:213)
    ... 6 more

  • Error ejb weblogic 11g - method remove

    Hi,
    When trying to deploy an ejb in weblogic 11g me the following error.
    Unable to deploy EJB: ConceptType from ejb-admin.jar:
    [EJB:010101]A mismatch exists between the bean code and generated code.Clase(Application: ejb-jar, EJBComponent: ejb-jar) . Please rerun appc on the bean code. The error was java.lang.NoSuchFieldException: md_ejbRemoveClaseTipo_L
         at java.lang.Class.getField(Class.java:1520)
         at weblogic.ejb.container.deployer.BeanInfoImpl.setHomeMDField(BeanInfoImpl.java:896)
         at weblogic.ejb.container.deployer.BeanInfoImpl.setMDField(BeanInfoImpl.java:861)
         at weblogic.ejb.container.deployer.BeanInfoImpl.setMethodDescriptor(BeanInfoImpl.java:794)
         at weblogic.ejb.container.deployer.ClientDrivenBeanInfoImpl.setMethodDescriptor(ClientDrivenBeanInfoImpl.java:784)
         at weblogic.ejb.container.deployer.ClientDrivenBeanInfoImpl.setMethodDescriptors(ClientDrivenBeanInfoImpl.java:758)
         at weblogic.ejb.container.deployer.ClientDrivenBeanInfoImpl.setMethodDescriptors(ClientDrivenBeanInfoImpl.java:657)
         at weblogic.ejb.container.deployer.ClientDrivenBeanInfoImpl.prepare(ClientDrivenBeanInfoImpl.java:1072)
         at weblogic.ejb.container.deployer.EntityBeanInfoImpl.prepare(EntityBeanInfoImpl.java:67)
         at weblogic.ejb.container.deployer.EJBDeployer.setupBeanInfos(EJBDeployer.java:1031)
         at weblogic.ejb.container.deployer.EJBDeployer.prepare(EJBDeployer.java:1288)
         at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:442)
         at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:199)
         at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:518)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
         at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:159)
         at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:47)
         at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:649)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
         at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191)
         at weblogic.application.internal.SingleModuleDeployment.prepare(SingleModuleDeployment.java:44)
         at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:154)
         at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60)
         at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:209)
         at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:98)
         at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
         at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:749)
         at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1216)
         at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:250)
         at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:160)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:171)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:13)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:47)
         at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:545)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
    . NestedException Message is :md_ejbRemoveClaseTipo_L
    Anyone know why?

    There's a null pointer at:
    mil.ahrs.emilpo.ejb.entity.personnelaccounting.SoldrasgtPK.equals(SoldrasgtPK.java:24)
    If you need more help debugging this, you'll have to show me the source code for that class.
    -- Rob
    Vy Nguyen wrote:
    I'm using WLS 6.1SP2. When I called ejbRemove() method passing the PK, and I got the following error:
    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 mil.ahrs.emilpo.ejb.entity.personnelaccounting.SoldrasgtPK.equals(SoldrasgtPK.java:24) at java.util.HashMap.remove(HashMap.java:380) at weblogic.utils.SoftHashMap.remove(SoftHashMap.java:242) at java.util.Collections$SynchronizedMap.remove(Collections.java:1440) at weblogic.ejb20.internal.EntityEJBLocalHome.releaseEO(EntityEJBLocalHome.java:406) at weblogic.ejb20.internal.EntityEJBLocalHome.remove(EntityEJBLocalHome.java:233) at mil.ahrs.emilpo.ejb.entity.personnelaccounting.SoldrasgtBean_8m4rrx_LocalHomeImpl.remove(SoldrasgtBean_8m4rrx_LocalHomeImpl.java:169) at mil.ahrs.emilpo.ejb.session.personnelaccounting.AssignmentServicesBean.removeCurrentAssignment
    I saw someone on-line had a similar issue and about CR044294_600sp2rp12.jar causing the error. How do I overcome this problem?
    THANK YOU.
    Vy--
    AVAILABLE NOW!: Building J2EE Applications & BEA WebLogic Server
    by Michael Girdley, Rob Woollen, and Sandra Emerson
    http://learnWebLogic.com
    [att1.html]

  • Please Help me Xdoclet CMP EJBs weblogic 8.1

    Hi all,
    I am new to both xdoclet and weblogic.
    I have confusion about foriegn-key-column and key-column in @weblogic.column-map tag for many to many relationship
    I have many to many relationship between Order EJB and Item EJB. join table name is OrderLine.
    In Order EJB I have cmr method
    public abstract java.util.Collection getItems();
    which one @weblogic.column-map tag is correct? is foriegn-key reference from Order table to OrderLine table or OrderLine table to Order table. My impression is it is from OrderLine table to Order table. Just want to confirm it.
    1)
    public abstract class OrderEJB implements EntityBean {
    * @ejb.interface-method
    * view-type="local"
    * @ejb.relation
    * name="OrdersItems"
    * role-name="Order"
    * @weblogic.relation
    * join-table-name="OrderLine"
    * generate="false"
    * @weblogic.column-map
    * foriegn-key-column="order_itemId"
    * key-column="orderline_item_id"*
    public abstract Collection getItems();
    Or
    2)
    public abstract class OrderEJB implements EntityBean {
    * @ejb.interface-method
    * view-type="local"
    * @ejb.relation
    * name="OrdersItems"
    * role-name="Order"
    * @weblogic.relation
    * join-table-name="OrderLine"
    * generate="false"
    * @weblogic.column-map
    * foriegn-key-column="orderline_itemId"
    * key-column="order_item_id"*
    public abstract Collection getItems();
    My second question is suppose I have composite foriegn-key, in that case how will I define @weblogic.column-map tags,
    will it be something like this?
    public abstract class OrderEJB implements EntityBean {
    * @ejb.interface-method
    * view-type="local"
    * @ejb.relation
    * name="OrdersItems"
    * role-name="Order"
    * @weblogic.relation
    * join-table-name="OrderLine"
    * generate="false"
    * @weblogic.column-map
    * foriegn-key-column="fk_col1"
    * key-column="pk_col1"*
    * @weblogic.column-map
    * foriegn-key-column="fk_col2"
    * key-column="pk_col2"
    public abstract Collection getItems();
    Thanks in advance

    Create a web application, put you JSP in the web application, put the web application in the server. And Robert is you Father's Brother.

  • Log4j ejb weblogic

    Hi all,
    I am using weblogic workshop 8.1 and I have created an EJB. I want to put logging statements in that using log4j.
    I modified "workshopLogCfg.xml" and I am able to log the statements. But as this is server configuration file I wont be able to put this in my .ear file.
    I want one log4j.xml file in my .ear so that when I ship .ear file, logging is not affected.
    I have put log4j.xml in classes and log4j.jar in lib folders of APP-INF of weblogic application. And added following line in META-INF/MANIFEST.MF file
    "Class-Path: APP-INF/lib/log4j.jar APP-INF/lib/ APP-INF/classes/"
    and also tried
    "Class-Path: lib/log4j.jar lib/ classes/"
    but both of these approach not working.
    Please help me in this.. ITS REALLY URGENT.
    Thanks.

    It won't work by specifying the classpath in the manifest file of the ear itself.
    You will have to specify these files in the Class-Path attribute of manifest files of all the modules (EJB, web, etc.) in your ear file.

  • C client calls EJB weblogic 6.1 - Do I need to purchase ORB

    My client is in C.
    The clint calls beans in weblogic 6.1 through IDL corba.
    Does weblogic 6.1 gives all the tools / software needed while developing ?
    while running ?
    Do I need to buy except of the weblogic also an ORB ?
    Thanks,
    Dalia

    Hi,
    You dont need to buy anothere orb untill it meets your requirements. Most of the app server supports rmi-iiop sementics. You should check this with Weblogic instead for more accurate info.
    Cheers
    Ashwani Kalra
    http://www.geocities.com/ashwani_kalra/
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

  • Building weblogic ejbs with ant...

    Hi, it may be not the proper place, but I haven't found a better one...
    Here comes my question:
    I have an ant build.xml file where I have the following tasks defined:
    <property name="ejb.dtd.location" value="weblogic/ejb/deployment/xml/ejb-jar.dtd"/>
        <condition property="ejb.dtd.location" value="weblogic/ejb20/dd/xml/ejb11-jar.dtd">
          <equals arg1="${weblogic.major.version}" arg2="6"/>
        </condition>
        <property name="weblogic.ejb.dtd.location" value="weblogic/ejb/deployment/xml/weblogic-ejb-jar.dtd"/>
        <condition property="ejb.dtd.location" value="weblogic/ejb20/dd/xml/weblogic510-ejb-jar.dtd">
          <equals arg1="${weblogic.major.version}" arg2="6"/>
        </condition>
    <!-- compiles EJBs -->
      <target name="compile.ejb" depends="init">
        <javac srcdir="${srcDir.ejb}"
              destdir="${srcDir.ejb}"
                debug="${npm.debug}">
          <classpath id="ejb.cpath">
             <pathelement path="${weblogic.sp.path}"/>
             <pathelement path="${weblogic.core.path}"/>
             <pathelement location="${outDir.core}${file.separator}npm.jar"/>
             <pathelement location="${srcDir.ejb}"/>
           </classpath>
        </javac>
      </target>
      <!-- delivers EJBs -->
      <target name="make.ejb" depends="prepare, compile.ejb">
        <!-- ejbc 'n jar 'em -->
        <ejbjar srcdir="${srcDir.ejb}">
           <weblogic destdir="${outDir.ejb}"
                     compiler="${compiler.ejb}"
                     keepgeneric="false"
                     suffix=".jar"
                     args="-g -nowarn"
                     oldCMP="false">
             <classpath refid="ejb.cpath"/>
           </weblogic>
           <include name="**/*-ejb-jar.xml"/>
           <exclude name="**/*-weblogic-ejb-jar.xml"/>
           <!-- WLS v5 DTDs!!! -->
           <dtd publicId="-//Sun Microsystems, Inc.//DTD Enterprise JavaBeans 1.1//EN"
                location="${ejb.dtd.location}"/>
           <dtd publicId="-//BEA Systems, Inc.//DTD WebLogic 5.1.0 EJB//EN"
                location="${weblogic.ejb.dtd.location}"/>
        </ejbjar>
      </target>This should build my ejbs with either the wls61 ejbc or the wls51 one. Anyway ant seems to have problems finding the local dtds in the classpath, although this is specified in the documentation. When I set both location attributes to point to files it works perfect. The problem is that these are in weblogic.jar for the wls61 release. This has two solutions, but either are bad in my opinion:
    1. extract the needed dtds to a temp dir with a jar task and then delete em...
    2. put the proper wls.jar in the classpath so ejbc could automatically resolve the dtds
    Can anyone help or may be send his ant build file, where a <dtd> nested element is used for <ejbjar> for wls61?
    Thank you in advance
    Anton

    Anton,
    Your second solution is the correct one. If you look at dtd element description under ejbjar task in the Ant manual, you'll see that vendors jars are required in Ant's classpath in order for ejbjar task to resolve DTD dependencies, in which case you don't need to specify dtd elements. I don't particularly like it either. If you find a better way to solve this problem, let me know.
    -Dmitry

  • Error deploying EJB on weblogic: Unable to set the transaction attribute

    Hi,
    I'm trying to deploy an application in WL10.3.2 and an error occurred during activation of changes.
    Here is the error message from the log file:
    <Jun 6, 2011 1:28:27 PM MDT> <Error> <Deployer> <BEA-149205> <Failed to initialize the application 'serverEAR-2' due to error weblogic.application.ModuleException: Exception preparing module: EJBModule(serverEJB-2.8.0.jar)
    Unable to deploy EJB: C:\oracle\Middleware\user_projects\domains\base_domain\servers\Server_3\tmp\_WL_user\serverEAR-2\1zw7ao\serverEJB-2.8.0.jar from serverEJB-2.8.0.jar:
    Unable to set the transaction attribute for method 'saveActionGroup(EditableActionGroup)' on EJB 'ViewBean'. No matching method could be found. Please verify the method signature specified in the ejb-jar.xml file matches that of your Remote interface for this EJB.
    weblogic.application.ModuleException: Exception preparing module: EJBModule(serverEJB-2.8.0.jar)
    Unable to deploy EJB: C:\oracle\Middleware\user_projects\domains\base_domain\servers\Server_3\tmp\_WL_user\serverEAR-2\1zw7ao\serverEJB-2.8.0.jar from serverEJB-2.8.0.jar:
    Unable to set the transaction attribute for method 'saveActionGroup(EditableActionGroup)' on EJB 'ViewBean'. No matching method could be found. Please verify the method signature specified in the ejb-jar.xml file matches that of your Remote interface for this EJB.
         at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:454)
         at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:199)
         at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:391)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83)
         at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:59)
         Truncated. see log file for complete stacktrace
    Caused By: weblogic.ejb.container.deployer.DeploymentDescriptorException: Unable to set the transaction attribute for method 'saveActionGroup(EditableActionGroup)' on EJB 'ViewBean'. No matching method could be found. Please verify the method signature specified in the ejb-jar.xml file matches that of your Remote interface for this EJB.
         at weblogic.ejb.container.deployer.MBeanDeploymentInfoImpl.processCTs(MBeanDeploymentInfoImpl.java:1502)
         at weblogic.ejb.container.deployer.MBeanDeploymentInfoImpl.processSpecificMethodCTs(MBeanDeploymentInfoImpl.java:1472)
         at weblogic.ejb.container.deployer.MBeanDeploymentInfoImpl.initializeTransactionAttribute(MBeanDeploymentInfoImpl.java:773)
         at weblogic.ejb.container.deployer.MBeanDeploymentInfoImpl.<init>(MBeanDeploymentInfoImpl.java:259)
         at weblogic.ejb.container.deployer.EJBDeployer.prepare(EJBDeployer.java:1190)
         Truncated. see log file for complete stacktrace
    Please help me...Thanks.

    In your ejb-jar.xml you are referring to a method saveActionGroup(EditableActionGroup) which is not defined in your remote interface.
    Maybe you have made some typo in the configuration. Check your transaction section, i.e.,
    <container-transaction>
                <method>
                    <ejb-name>ViewBean</ejb-name>
                    <method-name>saveActionGroup</method-name>
                    <method-params>
                        <method-param>package.EditableActionGroup</method-param>
                    </method-params>
                </method>
                <trans-attribute>Required</trans-attribute>
    </container-transaction>or something similar. See if the defined methods are corresponding to the methods defined in the remote interface.

  • Weblogic redeploys EJB despite warning

    I have my EJB Home and Remote classes in Weblogic's classpath while the EJB Jar (which contains Home , Remote and Bean) in the "applications" directory. When I start up the server , Weblogic deploys the EJB but gives the warning :
    <Warning> <EJB> <EJB Deployment: ExampleBean cannot be redeployed while the server is running. ExampleHome is located in the server's classpath.>
    However , if I keep the server running and redeploy a new implementation of the EJB , Weblogic is able to pick up the new implementation.
    Somehow Weblogic's warning and behaviour do not tally. Can I count on the fact that I can redeploy the EJB even though the Home and Remote is in the classpath ?
    I am running Weblogic 6.1 on Win2k.
    Thanks.
    Kean

    Hi Kean,
    You can still redeploy the ejb-jar file but any changes made to your home and remote interfaces will not be reflected in the new deployment if those interfaces exist in the server classpath.
    - Matt
    Kean wrote:
    I have my EJB Home and Remote classes in Weblogic's classpath while the EJB Jar (which contains Home , Remote and Bean) in the "applications" directory. When I start up the server , Weblogic deploys the EJB but gives the warning :
    <Warning> <EJB> <EJB Deployment: ExampleBean cannot be redeployed while the server is running. ExampleHome is located in the server's classpath.>
    However , if I keep the server running and redeploy a new implementation of the EJB , Weblogic is able to pick up the new implementation.
    Somehow Weblogic's warning and behaviour do not tally. Can I count on the fact that I can redeploy the EJB even though the Home and Remote is in the classpath ?
    I am running Weblogic 6.1 on Win2k.
    Thanks.
    Kean

Maybe you are looking for