NoClassDefFoundError during deployment & accessing EJBs in ear

Platform - Redhat Linux 7.2 weblogic6.0 ant 1.3 for compilation and creation of ear.
I get a NoClassDefFoundError when I try to access some of the EJBs in my deployed
ear file.
Previously, I faced a NoClassDefFoundError problem in deployment and I put the jar
containing
the classes that it was asking for, in the classpath in startWeblogic.sh.
The ear got deployed after that.
Error I am getting now...
2002-04-29 18-05-18 - bang - <INFO> - Type :Operation Groups
2002-04-29 18-05-18 - bang - <INFO> - SELECT member FROM s_access_group WHERE site
= ? AND facility
= ? AND type = ? AND name in('null')
2002-04-29 18-05-18 - bang - <DEBUG> - DB Connection closed
2002-04-29 18-05-18 - bang - <DEBUG> - DB Connection closed
2002-04-29 18-05-18 - bang - <ERROR> - Controller: createSessionForTheUser: Caught
Remote exception
while creating SessionMgrEJB
java.rmi.RemoteException: EJB Exception:; nested exception is:
java.lang.NoClassDefFoundError: com/seagate/edcs/server/system/sysmgr/GroupDetails
java.lang.NoClassDefFoundError: com/seagate/edcs/server/system/sysmgr/GroupDetails
at com.seagate.edcs.util.system.SecurityUtils.getMembersOfGroups(SecurityUtils.java:205)
at com.seagate.edcs.util.system.SecurityUtils.getGuestPrivileges(SecurityUtils.java:376)
at com.seagate.edcs.server.system.sessionmgr.SessionMgrEJB.ejbCreate(SessionMgrEJB.java:127)
I have done the same compilation and creation of ear and deployment in a Solaris
server, using the
same source code and build.xml ( ant build file) and ant properties file; never saw
any errors like this.
I unjared the ear lying in the solaris machine that I was using previously and the
ear that
I created now in the linux server, and saw a difference in the manifest files...
the manifest files remains same as what I decribe with the EJB source in the previous
(solaris)
case...
Manifest-Version: 1.0
Created-By: 1.3.0 (Sun Microsystems Inc.)
Class-Path: edcs2000_utility.jar edcsreportmgr.jar wipgrpmgr.jar resourcegrpmgr.jar
systemgrpmgr.jar
notificationmgr.jar role.jar user.jar
The manifest file in the ear created now in the linux machine is something like this;
different
from what I describe together with the EJB.
Manifest-Version: 1.0
Name: com/seagate/edcs/server/system/role/RoleEJBHomeImpl_WLStub.class
Name: com/seagate/edcs/server/system/role/ACLDetails.class
Name: WLGENERATED
Name: com/seagate/edcs/server/system/role/RolePK.class
Name: com/seagate/edcs/server/system/role/RoleEJBHomeImplAD.ser
Name: com/seagate/edcs/server/system/role/RoleEJBEOImpl_WLStub.class
Name: com/seagate/edcs/server/system/role/RoleEJBEOImpl.class
Name: META-INF/ejb-jar.xml
what might be the issue here ? Please do have a look and help!
Thanks in advance
Prabin.

Hi Kevin,
Use remote EJB method calls. For details, look for "Parent application" topic in this forum or Servlet development guide in Oracle Documentation Library. I know, it does not seem to be the right source when looking for EJB documentation, however, it is.
Daniel.

Similar Messages

  • WL8.1 crashed during deployment of EJB from ear file

    Hello,
    WL8.1 crashed during deployment of EJB from ear file on SunOs 5.8:
    error: Invalid class file format in /export/home/bea/j2sdk1.4.1_03/jre/lib/rt.jar(java/lang/AssertionError.class).
    The major.minor version '48.0' is too recent for this tool to understand.
    /export/home/mydomain/./ep1/.wlnotdelete/EJBCompilerCache/1xd25ws3hwp86/mydomain/facade/payroll/PayrollFL_vww01c_HomeImpl.java:83:
    Class java.lang.AssertionError not found.
    throw new AssertionError("Unable to find expected "+
    Thanks,
    Oleg.

    Thank you Mark,
    It works now.
    Oleg.
    "Mark Griffith" <[email protected]> wrote:
    I don't think though that _03 is the problem, you should have compatability
    between minor versions of a VM release. How did you deploy the ear?
    Did
    you copy over from a 7.0 domain? It looks like the EJB was built on
    a
    previous version of WLS, or has not had "ejbc" run on it prior to
    deployment. Try running weblogic.appc foo.ear or fooExplodedEar. And
    then
    try redeploying. To be sure everything is clean rm -rf .wldonotdelete
    after
    you shut the server down.
    cheers
    mbg
    "Oleg" <[email protected]> wrote in message
    news:3ef54653$[email protected]..
    Hello,
    WL8.1 crashed during deployment of EJB from ear file on SunOs 5.8:
    error: Invalid class file format in/export/home/bea/j2sdk1.4.1_03/jre/lib/rt.jar(java/lang/AssertionError.class
    The major.minor version '48.0' is too recent for this tool to understand.
    /export/home/mydomain/./ep1/.wlnotdelete/EJBCompilerCache/1xd25ws3hwp86/mydo
    main/facade/payroll/PayrollFL_vww01c_HomeImpl.java:83:
    Class java.lang.AssertionError not found.
    throw new AssertionError("Unable to find expected "+
    Thanks,
    Oleg.

  • Exception during deployment of EJB application

    Hi Experts,
    I'm deploying one EJB application which is giving following warning.
    What's the cause of it?
    Caught exception during application startup from SAP J2EE Engine's deploy service:
    java.rmi.RemoteException: Error occurred while starting application asianpaints.com/bsApp and wait.
    Reason: Clusterwide exception: server ID 8216350:com.sap.engine.services.ejb.exceptions.deployment.EJBDeploymentException: The DataSource for PersistenceManager J2EDB is not created.
         at com.sap.engine.services.ejb.entity.pm.PersistenceManager.initDataSource(PersistenceManager.java:217)
         at com.sap.engine.services.ejb.EJBAdmin.commitLoad(EJBAdmin.java:1112)
         at com.sap.engine.services.ejb.EJBAdmin.prepareStart(EJBAdmin.java:2428)
         at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:239)
         at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:187)
         at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:301)
         at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesImpl(ParallelAdapter.java:327)
         at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:111)
         at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:230)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:4700)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:4605)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:4578)
         at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:1163)
         at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:304)
         at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:193)
         at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:122)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
    Caused by: com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception during lookup operation of object with name ejbContainer/cmp/tx/asianpaints.com/bsApp/J2EDB, cannot resolve object reference. [Root exception is com.sap.engine.services.connector.exceptions.BaseResourceException: ConnectionFactory "J2EDB" does not exist. Possible reasons: the connector in which ConnectionFactory "J2EDB" is defined is not deployed or not started.]
         at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:529)
         at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:639)
         at javax.naming.InitialContext.lookup(InitialContext.java:347)
         at javax.naming.InitialContext.lookup(InitialContext.java:347)
         at com.sap.engine.services.ejb.entity.pm.PersistenceManager.initDataSource(PersistenceManager.java:185)
         ... 21 more
    Caused by: com.sap.engine.services.connector.exceptions.BaseResourceException: ConnectionFactory "J2EDB" does not exist. Possible reasons: the connector in which ConnectionFactory "J2EDB" is defined is not deployed or not started.
         at com.sap.engine.services.connector.ResourceObjectFactory.getObjectInstance(ResourceObjectFactory.java:207)
         at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl._getObjectInstance(ObjectFactoryBuilderImpl.java:72)
         at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl.access$100(ObjectFactoryBuilderImpl.java:31)
         at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl$DispatchObjectFactory.getObjectInstance(ObjectFactoryBuilderImpl.java:210)
         at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:280)
         at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:414)
         ... 25 more
    Pls help as im waiting for your reply...
    regards,
    Amey

    Hi Yordan,
    This is where im specifying my datasource in persistent.xml file(that is  in "General tab"  of EJB DC)
    <?xml version="1.0" encoding="UTF-8"?>
    <!DOCTYPE persistent-ejb-map SYSTEM "persistent.dtd">
    <persistent-ejb-map>
         <locking
              type="Table"/>
         <db-properties>
              <data-source-name>J2EDB</data-source-name>
         </db-properties>
         <entity-beans>
              <entity-bean>
                   <ejb-name>OEMBean</ejb-name>

  • FileNotFoundException thrown during deployment of EJB onto OAS

    During the deployment of an EJB onto OAS, I got the following error messages:
    <snipped>
    Processing jar...
    Analyzing Beans...
    AppTierEJBClass
    Code generation for E:\\Oracle\\OASHome\\ows\\upload\\242TestOASAppSource.jar has been completed.
    Compiling generated code...
    Creating client jar...
    java.io.FileNotFoundException: E:\Oracle\OASHome\ows\4.0\..\apps\ejb\TestOASApp\_client.jar
    at java.lang.Throwable.<init>(Compiled Code)
    at java.io.FileNotFoundException.<init>(Compiled Code)
    at java.io.FileOutputStream.<init>(FileOutputStream.java:69)
    at sun.tools.jar.Main.run(Main.java:76)
    at sun.tools.jar.Main.main(Main.java:524)
    at oracle.oas.tools.util.JarGenerator.createJar(Compiled Code)
    at oracle.oas.tools.util.CreateJars.main(Compiled Code)
    Creation of client jar for E:\\Oracle\\OASHome\\ows\\upload\\242TestOASAppSource.jar failed!
    Creating registration files...
    Deployment information for application successfully generated.
    <snipped>
    Just wondering what is that file not found error? And what is the cause of that?
    null

    I guess that might be trying to redeploy the same EJB again onto OAS.
    If that is the case you can try the following
    cd to OAS_HOME/ows/admin/website40/httpd_machinename/admin/svadmin.cfg
    and turn "FileCaching = OFF"
    OAS_HOME/ows/admin/website40/httpd_machinename/www/svadmin.cfg
    and turn "FileCaching = OFF"
    Once you change the settings , you would need to shutdown OAS and restart it again.
    the other workaroung would be to restart the appserver before the redeployment so that it would release the lock.
    raghu

  • Ejb-link not working when i access ejb in different ear

    Hi All
    I am here trying to access ejb's which is in different ear, I am providing ejb-link inside web.xml of war file deployed inside deffirent ear file.
    I am using wls8.1sp5. I tried different combination with elb-link name , but its not working . <ejb-ref>
    <ejb-ref-name>ejb/AuditService</ejb-ref-name>
    <ejb-ref-type>Session</ejb-ref-type>
    <home>com.onstar.audit.ejb.AuditServiceHome</home>
    <remote>com.onstar.audit.ejb.AuditService</remote>
    <ejb-link>ccarenewal.jar#AuditService</ejb-link>
    </ejb-ref>
    <ejb-ref>
         <ejb-ref-name>ejb/AccountService</ejb-ref-name>
         <ejb-ref-type>Session</ejb-ref-type>
         <home>com.onstar.account.ejb.AccountServiceHome</home>
         <remote>com.onstar.account.ejb.AccountService</remote>
         <ejb-link>ccarenewal.jar#AccountService</ejb-link>
         </ejb-ref>
    Exception:weblogic.management.ApplicationException: activate failed for sbwo Module: sbwo Error: weblogic.management.DeploymentException: Could not setup environment - with nested exception: [weblogic.deployment.EnvironmentException: [J2EE:160101]Error: The ejb-link 'ccarenewal.jar#AuditService' declared in the ejb-ref or ejb-local-ref 'ejb/AuditService' in the application module 'accountadj.war' could not be resolved. The target EJB for the ejb-ref could not be found. Please ensure the link is correct.] weblogic.deployment.EnvironmentException: [J2EE:160101]Error: The ejb-link 'ccarenewal.jar#AuditService' declared in the ejb-ref or ejb-local-ref 'ejb/AuditService' in the application module 'accountadj.war' could not be resolved. The target EJB for the ejb-ref could not be found. Please ensure the link is correct. at weblogic.deployment.EnvironmentBuilder.addEJBLinkRef(EnvironmentBuilder.java:658) at weblogic.deployment.EnvironmentBuilder.addEJBReferences(EnvironmentBuilder.java:467) at weblogic.servlet.internal.CompEnv.init(CompEnv.java:123) at weblogic.servlet.internal.WebAppServletContext.activate
    I will appreciate any help.
    Rajiv

    Rob,
    Thanks for your reply.
    Below is all deployment descriptor entries i have(ejb-jar.xml, weblogic-ejb-jar.xml, web.xml, weblogic.xml)
    please correct me if i have wrong entries any where.
    ejb-jar.xml
    ejb-ref>
    <description />
    <ejb-ref-name>ejb/AccountService</ejb-ref-name>
    <ejb-ref-type>Session</ejb-ref-type>
    <home>com.onstar.account.ejb.AccountServiceHome</home>
    <remote>com.onstar.account.ejb.AccountService</remote>
    <ejb-link>AccountService</ejb-link>
    </ejb-ref>
    weblogic-ejb-jar.xml
    <ejb-reference-description>
    <ejb-ref-name>ejb/AccountService</ejb-ref-name>
    <jndi-name>cca/AccountService</jndi-name>
    </ejb-reference-description>
    web.xml
    <ejb-ref>
    <ejb-ref-name>ejb/AccountService</ejb-ref-name>
    <ejb-ref-type>Session</ejb-ref-type>
    <home>com.onstar.account.ejb.AccountServiceHome</home>
    <remote>com.onstar.account.ejb.AccountService</remote>
    <ejb-link>ccarenewal.jar#AccountService</ejb-link>
    </ejb-ref>
    weblogic.xml
    <ejb-reference-description>
    <ejb-ref-name>ejb/AccountService</ejb-ref-name>
    <jndi-name>cca/AccountService</jndi-name>
    </ejb-reference-description>
    I appreciate your help.
    Thanks
    Rajiv

  • Ruleset webservice: error during deployment EAR file on the java server

    Hi,
    I want to create a webservices for a ruleset which i have created with the rules composer (NWDS).
    During this proces, the following problem occurs: after creating a ruleset and the EAR file with the Web Service Generation Tool, i wanted to deploy this file on the java server for creating a webservices. During deployment, I get the following warning with no results:
    <h5>
                S U M M A R Y
    ~~~~~~~~~~~~~~~~~~~
    Successfully deployed:           0
    Deployed with warnings:           1
    Failed deployments:                0
    ~~~~~~~~~~~~~~~~~~~
    1. File:C:\Documents and Settings\Martin Gerritsen\Desktop\Webservices\DeclaratieCheckRulesetEAR.ear
         Name:DeclaratieCheckRulesetEAR
         Vendor:sap.com
         Location:localhost
         Version:2008.03.12.12.02.09
         Deploy status:Warning
         Version:NEW
         Description:
              1. Warning occurred on server 1573750 during deploy sap.com/DeclaratieCheckRulesetEAR : Web Class Existence Test: The servlet "GenericWS" must implement "javax.servlet.Servlet"., file: DeclaratieCheckRulesetWEB.war#WEB-INF/web.xml, column 0, line 0, severity: warning
              2. Exception has been returned while the [sap.com/DeclaratieCheckRulesetEAR] was starting. Warning/Exception :[
    ][[ERROR CODE DPL.DS.6193] Error while ; nested exception is:
         com.sap.engine.services.deploy.exceptions.ServerDeploymentException: [ERROR CODE DPL.DS.5030] Clusterwide exception: [server ID 1573750:[ERROR CODE DPL.DS.5035] Application [sap.com/DeclaratieCheckRulesetEAR] cannot be started. Reason: it has hard reference to resource [tcbrmsfacade] with type [application], which is not active on the server.
    Hint: 1) Is referred resource deployed? 2) Is referred resource able to start?
               -> [ERROR CODE DPL.DS.5082] Exception while [validating application sap.com/tcbrmsfacade.
         The sap.com/tcbrmsfacade application was processed from [EJBContainer] containers, but none of them returned information about deployed components.
         The registered containers in this moment were [CTCContainer, MDRContainer, com.sap.security.ume, developmentserver, SCA Composites Container, com.sap.security.login-modules, app_libraries_container, Cache Configuration Upload, servlet_jsp, dbcontentcontainer, connector, Cluster File System, BRMS_Content_Archive, JMSConnector, MigrationContainer, Galaxy_Content_Archive, Monitoring Configurator, dbschemacontainer, appclient, orpersistence, PortalRuntimeContainer, JDBCConnector, EJBContainer, metamodelrepository, webservices_container, scheduler~container, ConfigurationsContainer, Content Container].
         Possible reasons :
         1.Empty or incorrect application, which is not recognized by registered containers.
         2.An AS Java service, which is providing a container, is stopped or not deployed.
         3.The containers, which processed it, are not implemented correctly, because the application was deployed or started initially, but containers didn't return information about deployed components in the application deployment info].
    server ID 1573750:com.sap.engine.services.deploy.exceptions.ServerDeploymentException: [ERROR CODE DPL.DS.5035] Application [sap.com/DeclaratieCheckRulesetEAR] cannot be started. Reason: it has hard reference to resource [tcbrmsfacade] with type [application], which is not active on the server.
    Hint: 1) Is referred resource deployed? 2) Is referred resource able to start?
         at com.sap.engine.services.deploy.server.ReferenceResolver.checkApplicationStatus(ReferenceResolver.java:871)
         at com.sap.engine.services.deploy.server.ReferenceResolver.processReferenceToApplication(ReferenceResolver.java:848)
         at com.sap.engine.services.deploy.server.ReferenceResolver.processMakeReference(ReferenceResolver.java:575)
         at com.sap.engine.services.deploy.server.ReferenceResolver.beforeStartingApplication(ReferenceResolver.java:489)
         at com.sap.engine.services.deploy.server.application.StartTransaction.beginCommon(StartTransaction.java:169)
         at com.sap.engine.services.deploy.server.application.StartTransaction.begin(StartTransaction.java:134)
         at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:493)
         at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:544)
         at com.sap.engine.services.deploy.server.application.ParallelAdapter.super_MakeAllPhases(ParallelAdapter.java:286)
         at com.sap.engine.services.deploy.server.application.StartTransaction.makeAllPhasesImpl(StartTransaction.java:555)
         at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:197)
         at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:358)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3421)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3407)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3297)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3269)
         at com.sap.engine.services.dc.lcm.impl.J2EELCMProcessor.doStart(J2EELCMProcessor.java:105)
         at com.sap.engine.services.dc.lcm.impl.LifeCycleManagerImpl.start(LifeCycleManagerImpl.java:78)
         at com.sap.engine.services.dc.cm.deploy.impl.LifeCycleManagerStartVisitor.visit(LifeCycleManagerStartVisitor.java:34)
         at com.sap.engine.services.dc.cm.deploy.impl.DeploymentItemImpl.accept(DeploymentItemImpl.java:83)
         at com.sap.engine.services.dc.cm.deploy.impl.DefaultDeployPostProcessor.postProcessLCMDeplItem(DefaultDeployPostProcessor.java:91)
         at com.sap.engine.services.dc.cm.deploy.impl.DefaultDeployPostProcessor.postProcess(DefaultDeployPostProcessor.java:61)
         at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.doPostProcessing(DeployerImpl.java:862)
         at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.performDeploy(DeployerImpl.java:810)
         at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.doDeploy(DeployerImpl.java:640)
         at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.deploy(DeployerImpl.java:359)
         at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.deploy(DeployerImpl.java:248)
         at com.sap.engine.services.dc.cm.deploy.impl.DeployerImplp4_Skel.dispatch(DeployerImplp4_Skel.java:897)
         at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:355)
         at com.sap.engine.services.rmi_p4.server.ServerDispatchImpl.run(ServerDispatchImpl.java:69)
         at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:67)
         at com.sap.engine.services.rmi_p4.P4Message.execute(P4Message.java:41)
         at com.sap.engine.services.cross.fca.FCAConnectorImpl.executeRequest(FCAConnectorImpl.java:971)
         at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:57)
         at com.sap.engine.services.cross.fca.MessageReader.run(MessageReader.java:55)
         at com.sap.engine.core.thread.execution.Executable.run(Executable.java:109)
         at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:314)
    Caused by: com.sap.engine.services.deploy.exceptions.ServerDeploymentException: [ERROR CODE DPL.DS.5082] Exception while [validating application sap.com/tcbrmsfacade.
         The sap.com/tcbrmsfacade application was processed from [EJBContainer] containers, but none of them returned information about deployed components.
         The registered containers in this moment were [CTCContainer, MDRContainer, com.sap.security.ume, developmentserver, SCA Composites Container, com.sap.security.login-modules, app_libraries_container, Cache Configuration Upload, servlet_jsp, dbcontentcontainer, connector, Cluster File System, BRMS_Content_Archive, JMSConnector, MigrationContainer, Galaxy_Content_Archive, Monitoring Configurator, dbschemacontainer, appclient, orpersistence, PortalRuntimeContainer, JDBCConnector, EJBContainer, metamodelrepository, webservices_container, scheduler~container, ConfigurationsContainer, Content Container].
         Possible reasons :
         1.Empty or incorrect application, which is not recognized by registered containers.
         2.An AS Java service, which is providing a container, is stopped or not deployed.
         3.The containers, which processed it, are not implemented correctly, because the application was deployed or started initially, but containers didn't return information about deployed components in the application deployment info].
         at com.sap.engine.services.deploy.server.utils.ValidateUtils.missingDCinDIValidator(ValidateUtils.java:80)
         at com.sap.engine.services.deploy.server.application.StartInitiallyTransaction.prepare(StartInitiallyTransaction.java:158)
         at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:502)
         at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:544)
         at com.sap.engine.services.deploy.server.application.StartTransaction.doStartInitiallyLocal(StartTransaction.java:477)
         at com.sap.engine.services.deploy.server.application.StartTransaction.doStartInitially(StartTransaction.java:433)
         at com.sap.engine.services.deploy.server.application.StartTransaction.prepareLocal(StartTransaction.java:193)
         at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesLocal(ApplicationTransaction.java:591)
         at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:202)
         at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesLocalAndWait(ParallelAdapter.java:367)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.regularStartApplicationLocalAndWait(DeployServiceImpl.java:3218)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationLocalAndWait(DeployServiceImpl.java:3210)
         at com.sap.engine.services.deploy.server.ReferenceResolver.checkApplicationStatus(ReferenceResolver.java:863)
         ... 36 more
    Result
    Status:Warning
    </h5>
    Development Infrastructure:
    - development configuration: local development
    - development configuration: saptest (SAP NetWeaver CE 7.1 EHP1)
    Before I created the EAR file with the Web Service Generation Tool, I have carried out the following steps:
    - Created a ruleset (including two rules and one decision table) (development configuration: saptest)
    - Build and deploy the ruleset on the java server...
    - Created a dummy web module (development configuration: local development)
    - Added 3 dependencies (references) to the dummy web module:
    - References 1: enginee.jee5.facade (no selection on design time, deploy time or runtime)
    - References 2: tc/bl/logging/api (selection on design time, deploy time and runtime)
    - References 3: tc/brms/ facade (selection on design time, deploy time and runtime)
    - Dummy web module -> sync used DC's
    - Build dummy web module
    After that I started the Web Service Generation Tool and created the EAR file....
    1) NWDS -> window -> show view -> others -> deploy view -> deploy view
    2) Added the EAR file to External Deployable Archives
    3) deployed the file to the java server... then the warning occurs...
    How can I resolve this error?
    <h5>Application [sap.com/DeclaratieCheckRulesetEAR] cannot be started. Reason: it has hard reference to resource [tcbrmsfacade] with type [application], which is not active on the server.
    Hint: 1) Is referred resource deployed? 2) Is referred resource able to start...</h5>
    And...
    <h5>[ERROR CODE DPL.DS.5082] Exception while [validating application sap.com/tcbrmsfacade.
         The sap.com/tcbrmsfacade application was processed from [EJBContainer] containers, but none of them returned information about deployed components.</h5>
    Can somebody help me with this problem?
    Kind regards,
    Martin Gerritsen

    Hello Martin Gerritsen,
    This is Arti from the PM team.
    It seems to me that the brms facade has not yet started in your application server. You can check whether it has started or not by doing the following -
    You need to access the JavaEE Applications running on your AS. To do this -
    1. Open the nwa portal
    2. Navigate to Operations Management > Systems > Start & Stop > Java EE Applications
    3. Search for the brms related applications available on the server.
    In case the applications have not yet been started, please try to manually start them. If you still have problem in starting the BRMS facade please contact me.
    I will send across to you a fresh set of SCAs which you can deploy into your server to resolve this issue.
    Regards,
    Arti

  • Access EJB 3.0 (deployed on Glassfish v3) from Tomcat 6.0.20 (Netbeans 6.8)

    Hi all,
    I'm a newbie (of java EE and Sun forum).
    I have a problem.
    I followed this tutorial: http://technology.amis.nl/blog/1368/connecting-to-an-ejb-30-remote-sessionbean-from-tomcat
    using Netbeans 6.8, Tomcat 6.0.20, Glassfish v3.
    The deploy of EJB on Glassfish is OK.
    The deploy of WebApp on Tomcat is OK.
    But when I access to the servlet using the browser I receive this exception.
    javax.naming.NoInitialContextException: Cannot instantiate class: com.sun.enterprise.naming.SerialInitContextFactory [Root exception is java.lang.ClassNotFoundException: com.sun.enterprise.naming.SerialInitContextFactory]
    at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:657)
    at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)
    at javax.naming.InitialContext.init(InitialContext.java:223)
    at javax.naming.InitialContext.<init>(InitialContext.java:197)
    at web.MyServlet.processRequest(MyServlet.java:51)
    at web.MyServlet.doGet(MyServlet.java:75)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
    at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
    at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
    at org.netbeans.modules.web.monitor.server.MonitorFilter.doFilter(MonitorFilter.java:390)
    at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
    at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
    at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
    at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
    at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
    at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
    at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
    at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:293)
    at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:849)
    at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583)
    at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:454)
    at java.lang.Thread.run(Thread.java:619)
    I know that I must copy *.jar files in Tomcat dir and App libraries (https://glassfish.dev.java.net/javaee5/ejb/EJB_FAQ.html#Step_3._Include_appserv-rt.jar_and), but it doesn't work.
    What are my mistakes?
    Thank you for your help.
    Servlet code:
    package web;
    import java.io.IOException;
    import java.io.PrintWriter;
    import javax.servlet.ServletException;
    import javax.servlet.http.HttpServlet;
    import javax.servlet.http.HttpServletRequest;
    import javax.servlet.http.HttpServletResponse;
    import java.util.Properties;
    import javax.naming.InitialContext;
    import javax.naming.NamingException;
    import testbean.MySessionBeanRemote;
    * @author Stefano
    public class MyServlet extends HttpServlet {
    * Processes requests for both HTTP <code>GET</code> and <code>POST</code> methods.
    * @param request servlet request
    * @param response servlet response
    * @throws ServletException if a servlet-specific error occurs
    * @throws IOException if an I/O error occurs
    protected void processRequest(HttpServletRequest request, HttpServletResponse response)
    throws ServletException, IOException {
    response.setContentType("text/html;charset=UTF-8");
    PrintWriter out = response.getWriter();
    Properties props = new Properties();
    props.setProperty("java.naming.factory.initial", "com.sun.enterprise.naming.SerialInitContextFactory");
    props.setProperty("java.naming.factory.url.pkgs", "com.sun.enterprise.naming");
    props.setProperty("java.naming.factory.state", "com.sun.corba.ee.impl.presentation.rmi.JNDIStateFactoryImpl");
    props.setProperty("org.omg.CORBA.ORBInitialHost", "localhost");
    props.setProperty("org.omg.CORBA.ORBInitialPort", "3700");
    try {
    out.println("<html>");
    out.println("<head>");
    out.println("<title>Servlet MyServlet</title>");
    out.println("</head>");
    out.println("<body>");
    out.println(MySessionBeanRemote.class.getName());
    try {
    InitialContext ic = new InitialContext(props);
    MySessionBeanRemote mySessionRemote = (MySessionBeanRemote) ic.lookup("pippo");
    out.println(mySessionRemote.getOK());
    } catch (NamingException ex) {
    ex.printStackTrace();
    out.println("</body>");
    out.println("</html>");
    } finally {
    out.close();

    Yes, I did.
    I'm not sure about the right actions to do.
    For example: the Glassfish FAQ told me to add gf-client*.jar to the Tomcat folder, not appserv-rt.jar , with v3.
    I tried with both files. I restarted Tomcat, but nothing work :-(

  • How to access EJB deployed in JBOSS 4 from Creator

    Hello.
    I am trying to access EJBs deployed on JBOSS in order to develop a web app client, when I import the EJB set from Creator (sessions and entities packages in a jar file) I got the following error message....."No EJB set found in file....." .
    I presume there is an kind of xml file description specific for Sun App Server missing. I would like to know if there is other way to expose EJB in creator?....maybe write a config file by hand.
    I already read the tutorials related to EJB but those only use pre build EJB jars for Sun App Sserver.
    Also I read all the posted about JBoos and EJB in this forum but those are pretty general.
    By the way I have Delegate classes to access the EJB. How do I register my delegates in Creator in order to expose their methods?
    I�ll really appreciate some light in this matter.
    Thanks in advance!!!

    Hi,
    The below forum thread may help you :
    http://swforum.sun.com/jive/thread.jspa?forumID=123&threadID=51321
    Thanks,
    Runa.

  • How to access ejb jar in ear package from other war web package?

    How to access ejb in jar packed in ear package from other war web package?

    Typically you would just look the EJB Home up in JNDI. If you're
    looking for example code, the medrec example in WLS 8.1 or petstore has
    plenty of webapps calling EJBs.
    -- Rob
    CottonXu wrote:
    How to access ejb in jar packed in ear package from other war web package?

  • EJB deployment/access from the Client Machine

    I want to deploy/access the EJB on the Oracle 8i server from the
    Client Machine. From the Oracle 8i server machine i am able to
    deploy and access the EJB
    When i am trying to deploy/access the EJB i am getting the
    following message
    javax.naming.CommunicationException: Unknown service : sess_iopp
    url
    Please tell me what to do ?
    Thanks in advance
    null

    Are you using JDeveloper? If yes then go to File|New->Snippets
    and select 'Example JServer EJB Client' to create an EJB client.
    : javax.naming.CommunicationException: Unknown service :
    sess_iopp
    It's sess_iiop not iopp ;-)
    Regards,
    Arun
    Manish Patel (guest) wrote:
    : I want to deploy/access the EJB on the Oracle 8i server from
    the
    : Client Machine. From the Oracle 8i server machine i am able to
    : deploy and access the EJB
    : When i am trying to deploy/access the EJB i am getting the
    : following message
    : javax.naming.CommunicationException: Unknown service :
    sess_iopp
    : url
    : Please tell me what to do ?
    : Thanks in advance
    null

  • EJB recompile during deployment

    Hi,
    What are the criteria for the WebLogic Server (we use 9.1) for recompiling
    EJBs? I have build an Application with several EJB.jar files in a directoy
    structure that is something like this:
    Application
    |- deploy
    | |- foo-EJB.jar
    | |- bar-EJB.jar
    |- libraries
    | |- commons-lang-2.1.jar
    |- META-INF
    | |- MANIFEST.MF
    | |- application.xml
    | |- weblogic-application.xml
    |- other-stuff
    When I deploy this application directly from this directory on a Windows PC,
    erverything works fine, but after packing it into an ear file, putting it
    on a SUN machine and deploying the ear file, the server starts recompiling
    several of the EJB.jar files. Why is it doing this?
    Greetings,
    Chris

    Olav,
    <load-on-startup> in web.xml will work only when you have load-on-startup="true" in your http-web-site.xml for your web module.
    for example <web-app application="work" name="work" root="/work" load-on-startup="true"/>
    This is documented in http://otn.oracle.com/tech/java/oc4j/htdocs/OC4J-WEB-FAQ.html#1
    regards
    Debu
    Hi!
    Currently I am working on an application that we are deploying on the oc4j-server and simultaneously on the SUN reference-implementation. Using the deployment descriptor I define the order of instantiation of the servlets (<load-on-startup>). This works fine using the SUN server. Deploying the application on the oc4j-server does not get to the servlet-initialization since the server tries to create the EJBs first. I would gladly tell the server somehow that this is both not necessary and even rather problematic to the application. Does anybody know how to achive this?
    Thanks in advance!
    Cheers,
    Olav

  • Accessing ejb classes directly on J2EE server (no EARs)

    Hi everyone,
    I was wondering how to run EJBs directly from their
    class directories for development purposes, without deploying them as an ear file.
    I'm running Sun's J2EE server.
    Any help would be much appreciated.
    cheers,
    Paul.

    We are doing that all the time with WebLogic 6.1
    Add the classes to the default class loader by making sure they are in the classpath given to the JVM that starts the application server.
    Put the ejb.jar XML file and the app. server specific XMl file if your app. server requires one in the appropriate META-INF directory at the application server.

  • Access EJB's deployed in WL 61 from Tomcat 4.0.3

    Question -
    Can anyone point me at documentation that will help me understand what jar files
    are required to allow access EJB's that are deployed in Weblogic 6.1 from a Servlet
    that is running under Tomcat.
    I am currently getting the following exception:
    javax.naming.NoInitialContextException: Cannot instantiate class: weblogic.jndi.WLInitialContextFactory.
    Root exception is java.lang.ClassNotFoundException: weblogic.jndi.WLInitialContextFactory
    at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1394)
    Thanks,
    Gary Bartlett

    I got the same problem.
    Some posts here suggest you should put weblogic.jar under /common/lib,
    I tried it but it didn't work. I also tried to put it under
    webapps/yourweb/web-inf/lib
    but it didn't work too. At last I had to unpack the weblogic.jar and put
    them under
    webapps/yourweb/web-inf/classes. This at least solved the problem you
    mentioned.
    I got other problem like ClassCastException that might be due to my own
    code.
    Anyway you can try the above approach. And please post your results here
    just let
    others know.
    Thanks.
    "Gary Bartlett" <[email protected]> wrote in message
    news:3ce3fdf1$[email protected]..
    >
    Question -
    Can anyone point me at documentation that will help me understand what jarfiles
    are required to allow access EJB's that are deployed in Weblogic 6.1 froma Servlet
    that is running under Tomcat.
    I am currently getting the following exception:
    javax.naming.NoInitialContextException: Cannot instantiate class:weblogic.jndi.WLInitialContextFactory.
    >
    >
    >
    Root exception is java.lang.ClassNotFoundException:weblogic.jndi.WLInitialContextFactory
    atorg.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.jav
    a:1394)
    >
    >
    Thanks,
    Gary Bartlett

  • Problems during deploy of an EAR with MDS enabled

    I am trying to deploy an EAR with MDS enabled (file-repository) to a WLS cluster, but I get this error:
    weblogic.application.ModuleException: :oracle.mds.config.MDSConfigurationException:MDS-01335: namespace "/xliffBundles" mapped to metadata-store-usage "MAR_TargetRepos" but its definition was not found in MDS configuration.
    Why does it happen? What should I check/do to solve the problem?
    Note that the deploy of the same EAR to the integrated WLS in Jdev works without exceptions.
    Thanks
    Edited by: user10047839 on 23-giu-2011 5.53

    When i tried to deploy the application using Jdeveloper Deployment Wizard, it prompts me a popup for 'Deployment Configuration' where we need to specify Respository Name, Respository Type, Partition Name, path/JNDI Info. I selected proper values and deployed, the applcation is deployed perfectly and works fine.
    But when i try to deploy the application using build.xml file, its error out as show below
    weblogic.application.ModuleException: :oracle.mds.config.MDSConfigurationException:MDS-01335: namespace "/xliffBundles" mapped to metadata-store-usage "MAR_TargetRepos" but its definition was not found in MDS configuration.
    I have provided the adf-config.xml below.
    ********************************adf-config.xml******************
    <?xml version="1.0" encoding="windows-1252" ?>
    <adf-config xmlns="http://xmlns.oracle.com/adf/config"
    xmlns:adf="http://xmlns.oracle.com/adf/config/properties"
    xmlns:sec="http://xmlns.oracle.com/adf/security/config">
    <adf:adf-properties-child xmlns="http://xmlns.oracle.com/adf/config/properties">
    <adf-property name="adfAppUID" value="Tenders-2723"/>
    </adf:adf-properties-child>
    <sec:adf-security-child xmlns="http://xmlns.oracle.com/adf/security/config">
    <CredentialStoreContext credentialStoreClass="oracle.adf.share.security.providers.jps.CSFCredentialStore"
    credentialStoreLocation="../../src/META-INF/jps-config.xml"/>
    <sec:JaasSecurityContext initialContextFactoryClass="oracle.adf.share.security.JAASInitialContextFactory"
    jaasProviderClass="oracle.adf.share.security.providers.jps.JpsSecurityContext"
    authorizationEnforce="true"
    authenticationRequire="true"/>
    </sec:adf-security-child>
    <adf-mds-config xmlns="http://xmlns.oracle.com/adf/mds/config">
    <mds-config xmlns="http://xmlns.oracle.com/mds/config" version="11.1.1.000">
    <cust-config>
    <match path="/">
    <customization-class name="oracle.adf.share.config.ADFUserCC"/>
    </match>
    </cust-config>
    <persistence-config>
    <metadata-namespaces>
    <namespace path="/persdef" metadata-store-usage="MAR_TargetRepos"/>
    </metadata-namespaces>
    <metadata-store-usages>
    <metadata-store-usage id="MAR_TargetRepos" deploy-target="true"
    default-cust-store="true">
    <metadata-store class-name="oracle.mds.persistence.stores.db.DBMetadataStore">
    <property value="mds-ADF_MDS" name="repository-name"/>
    <property value="jdbc/mds/ADF_MDS"
    name="jndi-datasource"/>
    <property value="TendersAviation" name="partition-name"/>
    </metadata-store>
    </metadata-store-usage>
    </metadata-store-usages>
    </persistence-config>
    </mds-config>
    </adf-mds-config>
    <adf-faces-config xmlns="http://xmlns.oracle.com/adf/faces/config">
    <taglib-config>
    <taglib uri="http://xmlns.oracle.com/adf/faces/rich">
    <tag name="table">
    <attribute name="filterVisible">
    <persist-changes>
    true
    </persist-changes>
    </attribute>
    </tag>
    <tag name="column">
    <attribute name="displayIndex">
    <persist-changes>
    false
    </persist-changes>
    </attribute>
    <attribute name="frozen">
    <persist-changes>
    true
    </persist-changes>
    </attribute>
    <attribute name="noWrap">
    <persist-changes>
    true
    </persist-changes>
    </attribute>
    <attribute name="selected">
    <persist-changes>
    true
    </persist-changes>
    </attribute>
    <attribute name="visible">
    <persist-changes>
    true
    </persist-changes>
    </attribute>
    <attribute name="width">
    <persist-changes>
    false
    </persist-changes>
    </attribute>
    </tag>
    <tag name="panelBox">
    <attribute name="disclosed">
    <persist-changes>
    true
    </persist-changes>
    </attribute>
    </tag>
    <tag name="panelSplitter">
    <attribute name="collapsed">
    <persist-changes>
    true
    </persist-changes>
    </attribute>
    <attribute name="splitterPosition">
    <persist-changes>
    true
    </persist-changes>
    </attribute>
    </tag>
    </taglib>
    </taglib-config>
    <persistent-change-manager>
    <persistent-change-manager-class>
    oracle.adf.view.rich.change.MDSDocumentChangeManager
    </persistent-change-manager-class>
    </persistent-change-manager>
    </adf-faces-config>
    </adf-config>

  • [EJB:015001] error while deploying an ejb on weblogic app server

    Hi,
    I'm trying to deploy an ear which has lot of modules and it is failing for one of the ejb module. The exception is as follows:
    <Mar 22, 2011 7:47:01 PM GMT+05:30> <Error> <Deployer> <WL-149265> <Failure occurred in the execution of deployment request with ID '1300803398704' for task '0'. Error is: 'weblogic.application.ModuleException: Exception preparing module: EJBModule(triv.product.jar)
    [EJB:011023]An error occurred while reading the deployment descriptor. The error was:
    Error processing annotations: .'
    weblogic.application.ModuleException: Exception preparing module: EJBModule(triv.product.jar)
    [EJB:011023]An error occurred while reading the deployment descriptor. The error was:
    Error processing annotations: .
         at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:469)
         at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:199)
         at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:517)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
         at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:159)
         Truncated. see log file for complete stacktrace
    Caused By: weblogic.utils.ErrorCollectionException:
    There are 1 nested errors:
    weblogic.j2ee.dd.xml.AnnotationProcessException: [EJB:015001]Unable to link class trivnet.product.services.svams.ProjSVAMServiceBean in Jar D:\ccm_wa\TICP-yogesh_3.4.0\TICP\product\classes : java.lang.NoClassDefFoundError: trivnet/service/svams/SVAMService
         at weblogic.j2ee.dd.xml.BaseJ2eeAnnotationProcessor.addProcessingError(BaseJ2eeAnnotationProcessor.java:1323)
         at weblogic.j2ee.dd.xml.BaseJ2eeAnnotationProcessor.addFatalProcessingError(BaseJ2eeAnnotationProcessor.java:1328)
         at weblogic.ejb.container.dd.xml.EjbAnnotationProcessor.processAnnotations(EjbAnnotationProcessor.java:161)
         at weblogic.ejb.container.dd.xml.EjbDescriptorReaderImpl.processStandardAnnotations(EjbDescriptorReaderImpl.java:344)
         at weblogic.ejb.container.dd.xml.EjbDescriptorReaderImpl.createReadOnlyDescriptorFromJarFile(EjbDescriptorReaderImpl.java:204)
         at weblogic.ejb.spi.EjbDescriptorFactory.createReadOnlyDescriptorFromJarFile(EjbDescriptorFactory.java:93)
         at weblogic.ejb.container.deployer.EJBModule.loadEJBDescriptor(EJBModule.java:1245)
         at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:397)
         at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:199)
         at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:517)
         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:45)
         at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:613)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
         at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:184)
         at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:58)
         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:207)
         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:747)
         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:159)
         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:46)
         at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:176)
         at weblogic.j2ee.dd.xml.BaseJ2eeAnnotationProcessor.addProcessingError(BaseJ2eeAnnotationProcessor.java:1322)
         at weblogic.j2ee.dd.xml.BaseJ2eeAnnotationProcessor.addFatalProcessingError(BaseJ2eeAnnotationProcessor.java:1328)
         at weblogic.ejb.container.dd.xml.EjbAnnotationProcessor.processAnnotations(EjbAnnotationProcessor.java:161)
         at weblogic.ejb.container.dd.xml.EjbDescriptorReaderImpl.processStandardAnnotations(EjbDescriptorReaderImpl.java:344)
         at weblogic.ejb.container.dd.xml.EjbDescriptorReaderImpl.createReadOnlyDescriptorFromJarFile(EjbDescriptorReaderImpl.java:204)
         Truncated. see log file for complete stacktrace
    >
    <Mar 22, 2011 7:47:01 PM GMT+05:30> <Warning> <Deployer> <WL-149004> <Failures were detected while initiating deploy task for application 'ear'.>
    <Mar 22, 2011 7:47:01 PM GMT+05:30> <Warning> <Deployer> <WL-149078> <Stack trace for message 149004
    weblogic.application.ModuleException: Exception preparing module: EJBModule(triv.product.jar)
    [EJB:011023]An error occurred while reading the deployment descriptor. The error was:
    Error processing annotations: .
         at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:469)
         at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:199)
         at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:517)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
         at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:159)
         Truncated. see log file for complete stacktrace
    Caused By: weblogic.utils.ErrorCollectionException:
    There are 1 nested errors:
    weblogic.j2ee.dd.xml.AnnotationProcessException: [EJB:015001]Unable to link class trivnet.product.services.svams.ProjSVAMServiceBean in Jar D:\ccm_wa\TICP-yogesh_3.4.0\TICP\product\classes : java.lang.NoClassDefFoundError: trivnet/service/svams/SVAMService
         at weblogic.j2ee.dd.xml.BaseJ2eeAnnotationProcessor.addProcessingError(BaseJ2eeAnnotationProcessor.java:1323)
         at weblogic.j2ee.dd.xml.BaseJ2eeAnnotationProcessor.addFatalProcessingError(BaseJ2eeAnnotationProcessor.java:1328)
         at weblogic.ejb.container.dd.xml.EjbAnnotationProcessor.processAnnotations(EjbAnnotationProcessor.java:161)
         at weblogic.ejb.container.dd.xml.EjbDescriptorReaderImpl.processStandardAnnotations(EjbDescriptorReaderImpl.java:344)
         at weblogic.ejb.container.dd.xml.EjbDescriptorReaderImpl.createReadOnlyDescriptorFromJarFile(EjbDescriptorReaderImpl.java:204)
         at weblogic.ejb.spi.EjbDescriptorFactory.createReadOnlyDescriptorFromJarFile(EjbDescriptorFactory.java:93)
         at weblogic.ejb.container.deployer.EJBModule.loadEJBDescriptor(EJBModule.java:1245)
         at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:397)
         at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:199)
         at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:517)
         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:45)
         at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:613)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
         at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:184)
         at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:58)
         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:207)
         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:747)
         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:159)
         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:46)
         at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:176)
         at weblogic.j2ee.dd.xml.BaseJ2eeAnnotationProcessor.addProcessingError(BaseJ2eeAnnotationProcessor.java:1322)
         at weblogic.j2ee.dd.xml.BaseJ2eeAnnotationProcessor.addFatalProcessingError(BaseJ2eeAnnotationProcessor.java:1328)
         at weblogic.ejb.container.dd.xml.EjbAnnotationProcessor.processAnnotations(EjbAnnotationProcessor.java:161)
         at weblogic.ejb.container.dd.xml.EjbDescriptorReaderImpl.processStandardAnnotations(EjbDescriptorReaderImpl.java:344)
         at weblogic.ejb.container.dd.xml.EjbDescriptorReaderImpl.createReadOnlyDescriptorFromJarFile(EjbDescriptorReaderImpl.java:204)
         Truncated. see log file for complete stacktrace
    >
    There are two scenarios one of which is working and the other is not. The details are below:
    Scenario 1: (Working)
    There is an ejb module in the ear (say ModA) which has two session beans (SessionA and SessionB having Remote interfcaes RemoteIntA and RemoteIntB).
    There is another ejb module in the ear (say ModB) which has few more session beans.
    Now I want to add an ejb which will extend from SessionA.
    So, I did following changes:
    i. added a remote interface in ModB - RemoteIntPA implements RemoteIntA
    ii. added session bean SessionPA extends SessionA implements RemoteIntPA
    iii. added ejb related annotations in SessionPA and removed the annotations from SessionA (i.e., SessionA is just a normal class by itself)
    Now in the application.xml I declare both modules (ModA and ModB) as ejb modules.
    I deploy the application everything works fine.
    Scenario 2: (Not Working)
    For some reason, I didn't required SessionB in ModA (which was the only ejb bean left in that module as SessionA was converted to normal java class). So I removed SessionB and RemoteIntB.
    Now as there are no ejb beans in ModA, I cannot define this as ejb module in application.xml and hence I defined it as java module.
    Now if I deploy the same application, I get the exception mentioned above.
    I think it has to do with the classpath issue. But how is that the classpath issue is arising when I declaring a module as java and not when I declare it as ejb. I have this module in classpath of ModB. So it doesn't matter what type of module it is.
    Am I missing something?
    Please help me in this regards.

    java.lang.NoClassDefFoundError: trivnet/service/svams/SVAMService
    The JAR with the class trivnet/service/svams/SVAMService is not in the classpath.

Maybe you are looking for