Failed to Deploy orchestration

Experts,
I am importing an MSI on server and getting following error. same MSI I imported on my local machine and imported successfully without any issues.
Thanks in adv.
2Venture2

Seems like this guy experienced something somewhat similar:
Link
Morten la Cour

Similar Messages

  • SDM failed when deploying a Web Dynpro application

    SDM failed when deploying a Web Dynpro application - I get the following error message:
    Sep 19, 2006 2:25:34 PM /userOut/deploy (com.sap.ide.eclipse.sdm.threading.DeployThreadManager) [Thread[Deploy Thread,5,main]] ERROR:
    [001]Deployment aborted
    Settings
    SDM host : eix-blade-011
    SDM port : 50118
    URL to deploy : file:/D:/DOCUME1/AMRM1.AZI/LOCALS1/Temp/temp43621sap.comwelcome.ear
    Deployment exception : Server eix-blade-011 did not accept login request as admin on port 50118. Details: ERROR: Could not establish connection to server eix-blade-011 at port 50118: eix-blade-011
    Inner exception was :
    Server eix-blade-011 did not accept login request as admin on port 50118. Details: ERROR: Could not establish connection to server eix-blade-011 at port 50118: eix-blade-011

    Amr Azim,
    You must have logged in thru a dedicated connection to any server through say VPN before deploying.This way the sdm uses the same login as that of already establised connection.
    So 'sign of'  all connections to any servers before deploying and redeploy your application.Here you will be prompted to supply the sdm password and deployment shall proceed.

  • Web services randomly fail to deploy properly in OC4J

    I have an ear with around 15 services, and sometimes (today, all the time, other times, not at all) some of the services fail to deploy correctly in that when I come to access them I get one of the following (the service that fails is generally different so the below is just an example):
    2009-07-07 15:06:16.633 WARNING OWS-03005 Unable to connect to URL: http://local
    host:8888/democustomer/CimsImageService due to java.security.PrivilegedActionExc
    eption: oracle.j2ee.ws.saaj.ContentTypeException: Not a valid SOAP Content-Type:
    text/html
    OR
    2009-07-07 15:06:16.711 ERROR OWS-04005 An error occurred for port: {http://serv
    ices.cims.prologic.com/}CimsCategoryService: javax.xml.rpc.JAXRPCException: Erro
    r loading Tie: com.prologic.cims.services.runtime.CimsCategoryWebServiceSoapHttp
    _Tie.
    Missing class: com.prologic.cims.services.runtime.CimsCategoryWebServi
    ceSoapHttp_Tie
    Dependent class: oracle.j2ee.ws.server.J2EEImplementor
    Loader: oc4j:10.1.3
    Code-Source: /C:/oc4j/webservices/lib/wsserver.jar
    Configuration: <code-source> in META-INF/boot.xml in C:\oc4j\j2ee\home
    \oc4j.jar
    This load was initiated at democustomer.web.democustomer:0.0.0 using the loadCla
    ss() method.
    The missing class is not available from any code-source or loader in the system.
    If I redeploy it often, but not always, sorts the problem out so it is not a source code issue and I guess, possibly not a deployment descriptor problem for the same reason.
    I'm running on OC4J 10.1.3.1 (we need to run with this version for now).
    I get the same problem very occasionally on Linux 10.1.3.n but it's rare.
    Anyone out there seen this before ? It's becoming very irritating.

    idris, the only workaround I have found is to check at container startup that each service was deployed ok, by making a call to a serviceAvailable method. That way, if I restart OC4J after a deployment I see log messages if all was not well (and in fact I can specify that the container shouldn't start if the service failed)
    Class oracle.j2ee.server.OC4JStartup is the one you want and insert something like into server.xml after the cluster element (the jar conmtaining your code needs to be in the applib directory too):
         <init-library path="../applib/startupshutdown.jar" /> <!-- or wherever we put it -->
    <startup-classes>
    <startup-class classname="com.prologic.cms.services.StartupServer" failure-is-fatal="true" >
    <execution-order>0</execution-order>
                   <init-param>
                        <param-name>TestServices</param-name>
                        <param-value>true</param-value>
                   </init-param>
                   <init-param>
                        <param-name>deployment.port</param-name>
                        <param-value>7777</param-value>
                   </init-param>
                   <init-param>
                        <param-name>ASwitchToPassIn</param-name>
                        <param-value>true</param-value>
                   </init-param>
                   <init-param>
                        <param-name>SearchIndexRebuild</param-name>
                        <param-value>true</param-value>
                   </init-param>
                   <init-param>
                        <param-name>waitfor</param-name>
                        <param-value>50000</param-value>
                   </init-param>
                   <init-param>
                        <param-name>language</param-name>
                        <param-value>en</param-value>
                   </init-param>
                   <init-param>
                        <param-name>locale</param-name>
                        <param-value>UK</param-value>
                   </init-param>
    </startup-class>
    </startup-classes>

  • Fail to deploy the "Virtual Shop Lite " Sample

    Fail to deploy the "Virtual Shop Lite " Sample in
    SAP Netweaver J2EE Preview (Release SAP NetWeaver™ 2007).
    I select the SAP Server node and choose Publish from the context menu. The SAP NetWeaver Developer Studio switches to the Deploy View Console view.
    At this time, the "Logon to SAP J2EE Engine" window appear.
    I enter the below user and password.
    user : Administrator
    password : <master-password>
    In the Deploy View Console, the below messages appear:
    com.sap.ide.eclipse.deployer.api.AuthenticationException:
    [#1]:Session::checkForTicketException:[Base Login Exception], cause=The user account is expired,or not valid yet.[more]
    [#1]:DC API is trying to connect to "localhost:50004".
    What should I do ?
    (I try the 10th time but the result is the same.)

    Same problem:
    Fail to deploy the "Virtual Shop Lite " Sample
    Is it a BUG ???

  • Fail to deploy the "Virtual Shop Lite " Sample in

    Fail to deploy the "Virtual Shop Lite " Sample in
    SAP Netweaver J2EE Preview (Release SAP NetWeaver™ 2007).
    I select the SAP Server node and choose Publish from the context menu. The SAP NetWeaver Developer Studio switches to the Deploy View Console view.
    At this time, the "Logon to SAP J2EE Engine" window appear.
    I enter the below user and password.
    user : Administrator
    password : <master-password>
    In the Deploy View Console, the below messages appear:
    com.sap.ide.eclipse.deployer.api.AuthenticationException:
    [#1]:Session::checkForTicketException:[Base Login Exception], cause=The user account is expired,or not valid yet.[more]
    [#1]:DC API is trying to connect to "localhost:50004".
    What should I do ?
    (I try the 10th time but the result is the same.)

    see the below link (same problem):
    Deploying Virtual Shop Lite
    I think it may be a BIG BUG.
    You can see it by yourself.

  • Failed to deploy web application with same name twice

    Hello-
    On Oracle 10g Application server I deployed an WAR file called "anbadmin", then undeployed it. The undepoloyment failed from the OEM so I undeployed it manually via removing its entries from server.xml.
    When I tried to deploy it again with the same name I got this:
    Failed to deploy web application "anbadmin". Failed to deploy web application "anbadmin". . The evaluate phase failed. The Adapter used in the evaluate may have thrown an exception.
    Resolution:
    Please call Oracle support.
    Base Exception:
    java.lang.NoSuchMethodError
    null. java.lang.NoSuchMethodError
    Is there a solution for this?
    Regards

    I think I know the solution. We encountered exactly same message and no further deployment could be made. It appeared message in "dcmctl" utility was much more helpfull than the one in EM (though you still have to use "getError" command...)
    If you are using file-based repository, you have to issue command in dcmctl utility "resetFileTransaction". This closes repository and opens it again.
    Myrra

  • Essbase Studio: Failed to deploy Essbase cube

    Hi
    I have started working with Essbase studio sometime back and I am able to deploy BSO cube with success using the TBCSample Database which comes along with Essbase. Now I wanted to deploy ASO cube, as no sample database is available I thought to create one, I extracted ASOSamp using ODI to CSV files. Then I bulk inserted the csv extracts into MSSQL 2003 server which created 11 tables (Age, Geography, IncomeLevel, Measures, PaymentType, Product, Stores, Time TransactionType, Year). The above mentioned table does not have any keys(Primary, Foreign) as it is an Essbase export.
    I then successful created ASO Cube Schema using the newly created sample database in MSSQL, validated cube schema without any errors.
    Essbase Property Setting:
    Measures Hierarchy is tagged as Dynamic Compression at dimension level
    Time, Product and Year Hierarchy is tagged as Multiple Hierarchies Enabled, Year does not have multiple hierarchies but it has formulas for Variance and Variance % member. Is there a way to tag Year as Dynamic hierarchy?
    But when I try to deploy the cube to Essbase I receive following errors:
    Failed to deploy Essbase cube
    Caused By: Cannot end incremental build. Essbase Error(1060053): Outline has errors
    \\Record #1 - Member name (Time) already used
    + S Time + S
    \\Record #6 - Member name (1st Half) already used
    MTD + S 1st Half + S
    \\Record #7 - Member name (2nd Half) already used
    MTD + S 2nd Half + S
    \\Record #21 - Member name (Qtr1) already used
    Qtr1 + S Feb + S
    \\Record #22 - Member name (Qtr1) already used
    Qtr1 + S Jan + S
    \\Record #23 - Member name (Qtr1) already used
    Qtr1 + S Mar + S
    \\Record #24 - Member name (Qtr2) already used
    Qtr2 + S Apr + S
    \\Record #25 - Member name (Qtr2) already used
    Qtr2 + S Jun + S
    \\Record #26 - Member name (Qtr2) already used
    Qtr2 + S May + S
    \\Record #27 - Member name (Qtr3) already used
    Qtr3 + S Aug + S
    \\Record #28 - Member name (Qtr3) already used
    Qtr3 + S Jul + S
    \\Record #29 - Member name (Qtr3) already used
    Qtr3 + S Sep + S
    \\Record #30 - Member name (Qtr4) already used
    Qtr4 + S Dec + S
    \\Record #31 - Member name (Qtr4) already used
    Qtr4 + S Nov + S
    \\Record #32 - Member name (Qtr4) already used
    Qtr4 + S Oct + S
    \\Record #33 - Member name (Time) already used
    Time + S MTD + S
    \\Record #34 - Member name (Time) already used
    Time ~ S QTD ~ S
    \\Record #35 - Member name (Time) already used
    Time ~ S YTD ~ S
    \\Record #9 - Error adding Attribute to member QTD(Jan) (3320)
    \\Record #9 - Aggregate storage outlines only allow formulas in compression dimension or dynamic hierarchies.
    QTD + S QTD(Jan) + S [Jan]
    \\Record #10 - Error adding Attribute to member QTD(Apr) (3320)
    \\Record #10 - Aggregate storage outlines only allow formulas in compression dimension or dynamic hierarchies.
    QTD ~ S QTD(Apr) ~ S [Apr]
    \\Record #11 - Error adding Attribute to member QTD(Aug) (3320)
    \\Record #11 - Aggregate storage outlines only allow formulas in compression dimension or dynamic hierarchies.
    QTD ~ S QTD(Aug) ~ S [Jul]+[Aug]
    \\Record #12 - Error adding Attribute to member QTD(Dec) (3320)
    \\Record #12 - Aggregate storage outlines only allow formulas in compression dimension or dynamic hierarchies.
    QTD ~ S QTD(Dec) ~ S [Oct]+[Nov]+[Dec]
    \\Record #13 - Error adding Attribute to member QTD(Feb) (3320)
    \\Record #13 - Aggregate storage outlines only allow formulas in compression dimension or dynamic hierarchies.
    QTD ~ S QTD(Feb) ~ S [Jan]+[Feb]
    \\Record #14 - Error adding Attribute to member QTD(Jul) (3320)
    \\Record #14 - Aggregate storage outlines only allow formulas in compression dimension or dynamic hierarchies.
    QTD ~ S QTD(Jul) ~ S [Jul]
    \\Record #15 - Error adding Attribute to member QTD(Jun) (3320)
    \\Record #15 - Aggregate storage outlines only allow formulas in compression dimension or dynamic hierarchies.
    QTD ~ S QTD(Jun) ~ S [Apr]+[May]+[Jun]
    \\Record #16 - Error adding Attribute to member QTD(Mar) (3320)
    \\Record #16 - Aggregate storage outlines only allow formulas in compression dimension or dynamic hierarchies.
    QTD ~ S QTD(Mar) ~ S [Jan]+[Feb]+[Mar]
    \\Record #17 - Error adding Attribute to member QTD(May) (3320)
    \\Record #17 - Aggregate storage outlines only allow formulas in compression dimension or dynamic hierarchies.
    QTD ~ S QTD(May) ~ S [Apr]+[May]
    \\Record #18 - Error adding Attribute to member QTD(Nov) (3320)
    \\Record #18 - Aggregate storage outlines only allow formulas in compression dimension or dynamic hierarchies.
    QTD ~ S QTD(Nov) ~ S [Oct]+[Nov]
    \\Record #19 - Error adding Attribute to member QTD(Oct) (3320)
    \\Record #19 - Aggregate storage outlines only allow formulas in compression dimension or dynamic hierarchies.
    QTD ~ S QTD(Oct) ~ S [Oct]
    \\Record #20 - Error adding Attribute to member QTD(Sep) (3320)
    \\Record #20 - Aggregate storage outlines only allow formulas in compression dimension or dynamic hierarchies.
    QTD ~ S QTD(Sep) ~ S [Jul]+[Aug]+[Sep]
    \\Record #36 - Error adding Attribute to member YTD(Jan) (3320)
    \\Record #36 - Aggregate storage outlines only allow formulas in compression dimension or dynamic hierarchies.
    YTD + S YTD(Jan) + S [Jan]
    \\Record #37 - Error adding Attribute to member YTD(Apr) (3320)
    \\Record #37 - Aggregate storage outlines only allow formulas in compression dimension or dynamic hierarchies.
    YTD ~ S YTD(Apr) ~ S [Qtr1]+[Apr]
    \\Record #38 - Error adding Attribute to member YTD(Aug) (3320)
    \\Record #38 - Aggregate storage outlines only allow formulas in compression dimension or dynamic hierarchies.
    YTD ~ S YTD(Aug) ~ S [1st Half]+[Jul]+[Aug]
    \\Record #39 - Error adding Attribute to member YTD(Dec) (3320)
    \\Record #39 - Aggregate storage outlines only allow formulas in compression dimension or dynamic hierarchies.
    YTD ~ S YTD(Dec) ~ S [1st Half]+[Qtr3]+[Qtr4]
    \\Record #40 - Error adding Attribute to member YTD(Feb) (3320)
    \\Record #40 - Aggregate storage outlines only allow formulas in compression dimension or dynamic hierarchies.
    YTD ~ S YTD(Feb) ~ S [Jan]+[Feb]
    \\Record #41 - Error adding Attribute to member YTD(Jul) (3320)
    \\Record #41 - Aggregate storage outlines only allow formulas in compression dimension or dynamic hierarchies.
    YTD ~ S YTD(Jul) ~ S [1st Half]+[Jul]
    \\Record #42 - Error adding Attribute to member YTD(Jun) (3320)
    \\Record #42 - Aggregate storage outlines only allow formulas in compression dimension or dynamic hierarchies.
    YTD ~ S YTD(Jun) ~ S [1st Half]
    \\Record #43 - Error adding Attribute to member YTD(Mar) (3320)
    \\Record #43 - Aggregate storage outlines only allow formulas in compression dimension or dynamic hierarchies.
    YTD ~ S YTD(Mar) ~ S [Qtr1]
    \\Record #44 - Error adding Attribute to member YTD(May) (3320)
    \\Record #44 - Aggregate storage outlines only allow formulas in compression dimension or dynamic hierarchies.
    YTD ~ S YTD(May) ~ S [Qtr1]+[Apr]+[May]
    \\Record #45 - Error adding Attribute to member YTD(Nov) (3320)
    \\Record #45 - Aggregate storage outlines only allow formulas in compression dimension or dynamic hierarchies.
    YTD ~ S YTD(Nov) ~ S [1st Half]+[Qtr3]+[Oct]+[Nov]
    \\Record #46 - Error adding Attribute to member YTD(Oct) (3320)
    \\Record #46 - Aggregate storage outlines only allow formulas in compression dimension or dynamic hierarchies.
    YTD ~ S YTD(Oct) ~ S [1st Half]+[Qtr3]+[Oct]
    \\Record #47 - Error adding Attribute to member YTD(Sep) (3320)
    \\Record #47 - Aggregate storage outlines only allow formulas in compression dimension or dynamic hierarchies.
    YTD ~ S YTD(Sep) ~ S [1st Half]+[Qtr3]
    \\Record #2 - Incorrect Dimension [Year] For Member [ParentName] (3308)
    ParentName Consolidation DataStorage MemberName Consolidation DataStorage Formula
    \\Record #1 - Member name (Promotions) already used
    S Promotions S
    \\Record #2 - Incorrect Dimension [Promotions] For Member [ParentName] (3308)
    ParentName DataStorage MemberName DataStorage
    \\Record #3 - Member name (Promotions) already used
    Promotions S Coupon S
    \\Record #4 - Member name (Promotions) already used
    Promotions S Newspaper Ad S
    \\Record #5 - Member name (Promotions) already used
    Promotions S No Promotion S
    \\Record #6 - Member name (Promotions) already used
    Promotions S Temporary Price Reduction S
    \\Record #7 - Member name (Promotions) already used
    Promotions S Year End Sale S
    \\Record #2 - Incorrect Dimension [Payment Type] For Member [ParentName] (3308)
    ParentName DataStorage MemberName DataStorage
    \\Record #2 - Incorrect Dimension [Transation Type] For Member [ParentName] (3308)
    ParentName DataStorage MemberName DataStorage
    \\Record #22 - Member name (Home Entertainment) already used
    Home Entertainment + S Home Audio/Video + S
    \\Record #23 - Member name (Home Entertainment) already used
    Home Entertainment + S Televisions + S
    \\Record #24 - Member name (Other) already used
    Other + S Computers and Peripherals + S
    \\Record #25 - Incorrect Dimension [Product] For Member [ParentName] (3308)
    ParentName Consolidation DataStorage MemberName Consolidation DataStorage
    \\Record #26 - Member name (Personal Electronics) already used
    Personal Electronics + S Digital Cameras/Camcorders + S
    \\Record #27 - Member name (Personal Electronics) already used
    Personal Electronics + S Handhelds/PDAs + S
    \\Record #28 - Member name (Personal Electronics) already used
    Personal Electronics + S Portable Audio + S
    \\Record #31 - Member name (All Merchandise) already used
    Products + S All Merchandise + S
    \\Record #32 - Member name (High End Merchandise) already used
    Products ~ S High End Merchandise ~ S
    \\Record #33 - Member name (Systems) already used
    Systems + S Desktops + S
    \\Record #34 - Member name (Systems) already used
    Systems + S Notebooks + S
    \\Record #18 - Error adding Attribute to member Digital Recorders (3320)
    Home Audio/Video + S Digital Recorders + S
    \\Record #36 - Error adding Attribute to member Flat Panel (3320)
    Televisions + S Flat Panel + S
    \\Record #37 - Error adding Attribute to member HDTV (3320)
    Televisions + S HDTV + S
    \\Record #8 - Incorrect Dimension [Income Level] For Member [ParentName] (3308)
    ParentName DataStorage MemberName DataStorage
    \\Record #1 - Member name (Geography) already used
    S Geography S
    \\Record #2 - Error adding member 27425 (3317)
    \\Record #2 - Aggregate storage outlines only allow any shared member once in a stored hierarchy, including prototype.
    A M F GREENSBORO - NC S 27425 S 336
    \\Record #3 - Error adding member 36310 (3317)
    \\Record #3 - Aggregate storage outlines only allow any shared member once in a stored hierarchy, including prototype.
    ABBEVILLE - AL S 36310 S 334
    \\Record #4 - Error adding member 29620 (3317)
    \\Record #4 - Aggregate storage outlines only allow any shared member once in a stored hierarchy, including prototype.
    ABBEVILLE - SC S 29620 S 864
    \\Record #5 - Error adding member 67510 (3317)
    \\Record #5 - Aggregate storage outlines only allow any shared member once in a stored hierarchy, including prototype.
    ABBYVILLE - KS S 67510 S 316
    \\Record #6 - Error adding member 58001 (3317)
    \\Record #6 - Aggregate storage outlines only allow any shared member once in a stored hierarchy, including prototype.
    ABERCROMBIE - ND S 58001 S 701
    \\Record #7 - Error adding member 42201 (3317)
    \\Record #7 - Aggregate storage outlines only allow any shared member once in a stored hierarchy, including prototype.
    ABERDEEN - KY S 42201 S 502
    \\Record #8 - Error adding member 21001 (3317)
    \\Record #8 - Aggregate storage outlines only allow any shared member once in a stored hierarchy, including prototype.
    ABERDEEN - MD S 21001 S 410
    \\Record #9 - Error adding member 39730 (3317)
    \\Record #9 - Aggregate storage outlines only allow any shared member once in a stored hierarchy, including prototype.
    ABERDEEN - MS S 39730 S 601
    \\Record #10 - Error adding member 28315 (3317)
    \\Record #10 - Aggregate storage outlines only allow any shared member once in a stored hierarchy, including prototype.
    ABERDEEN - NC S 28315 S 910
    \\Record #11 - Error adding member 79311 (3317)
    \\Record #11 - Aggregate storage outlines only allow any shared member once in a stored hierarchy, including prototype.
    ABERNATHY - TX S 79311 S 806
    \\Record #12 - Error adding member 79601 (3317)
    \\Record #12 - Aggregate storage outlines only allow any shared member once in a stored hierarchy, including prototype.
    ABILENE - TX S 79601 S 915
    \\Record #13 - Error adding member 79608 (3317)
    \\Record #13 - Aggregate storage outlines only allow any shared member once in a stored hierarchy, including prototype.
    ABILENE - TX S 79608 S 915
    \\Record #14 - Error adding member 79698 (3317)
    \\Record #14 - Aggregate storage outlines only allow any shared member once in a stored hierarchy, including prototype.
    Are these errors due to data source, if yes what could be possible work around?
    Is there any problem with Essbase properties which I have set if so then when I validate cube schema why I dn't get any errors?
    Please help me, I am stuck here not able to deploy ASO Cube.
    Thanks in advance

    Hii
    I have the same problem , you have.
    did you manage to solve it ??
    Thanks in advance

  • WebLogic 12.1.2 fails when deploying ear with injecting extension and bean with injection of this extension in ejb

    WebLogic 12.1.2 fails when deploying an enterprise application(ear) that contains a ejb in which injected 1) an extension 2)bean with injection of this extension.
    The following exception is thrown:
    Caused By: org.jboss.weld.exceptions.DeploymentException: WELD-001409 Ambiguous dependencies for type [CdiExtension] with qualifiers [@Default] at injection point [[field] @Inject private test.extension.Bean1.extension].
    Possible dependencies [
    [Extension [class test.extension.CdiExtension] with qualifiers [@Default]; zip:/domain1/servers/AdminServer/tmp/_WL_user/test/7x6roh/lib/test-extension-0.0.1-SNAPSHOT.jar!/META-INF/services/javax.enterprise.inject.spi.Extension@1[test.extension.CdiExtension@1115deb],
    Extension [class test.extension.CdiExtension] with qualifiers [@Default]; zip:/domain1/servers/AdminServer/tmp/_WL_user/test/7x6roh/lib/test-extension-0.0.1-SNAPSHOT.jar!/META-INF/services/javax.enterprise.inject.spi.Extension@1[test.extension.CdiExtension@ed791f]]]
        at org.jboss.weld.bootstrap.Validator.validateInjectionPoint(Validator.java:314)
        at org.jboss.weld.bootstrap.Validator.validateInjectionPoint(Validator.java:280)
        at org.jboss.weld.bootstrap.Validator.validateBean(Validator.java:143)
        at org.jboss.weld.bootstrap.Validator.validateRIBean(Validator.java:163)
        at org.jboss.weld.bootstrap.Validator.validateBeans(Validator.java:382)
        at org.jboss.weld.bootstrap.Validator.validateDeployment(Validator.java:367)
        at org.jboss.weld.bootstrap.WeldBootstrap.validateBeans(WeldBootstrap.java:379)
        at com.oracle.injection.provider.weld.WeldInjectionContainer.start(WeldInjectionContainer.java:106)
        at com.oracle.injection.integration.CDIAppDeploymentExtension.initCdi(CDIAppDeploymentExtension.java:70)
        at com.oracle.injection.integration.CDIAppDeploymentExtension.activate(CDIAppDeploymentExtension.java:47)
        at weblogic.application.internal.flow.AppDeploymentExtensionFlow.activate(AppDeploymentExtensionFlow.java:37)
        at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:729)
        at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:42)
        at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:258)
        at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:61)
        at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:165)
        at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:80)
    Problem can be easily reproduced by a minimal case:
    test.ear:
    \lib\test-extension-0.0.1-SNAPSHOT.jar
    test-ejb-0.0.1-SNAPSHOT.jar
    where
    test-extension-0.0.1-SNAPSHOT.jar contains:
    CdiExtension.java:
    package test.extension;
    import javax.enterprise.inject.spi.Extension;
    public class CdiExtension implements Extension {
        private String someString = "Some String";
        public String getSomeString() {
            return someString;
    Bean1.java:
    package test.extension;
    import javax.enterprise.context.ApplicationScoped;
    import javax.inject.Inject;
    @ApplicationScoped
    public class Bean1 {
        @Inject
        private CdiExtension extension;
        public String get() {
            return extension.getSomeString();
    test-ejb-0.0.1-SNAPSHOT.jar contains:
    EjbBean.java:
    package test;
    import test.extension.Bean1;
    import test.extension.CdiExtension;
    import javax.ejb.Stateless;
    import javax.inject.Inject;
    @Stateless
    public class EjbBean {
        @Inject
        private CdiExtension extension;
        @Inject
        private Bean1 bean1;
        public String getSomeString() {
            return extension.getSomeString() + "\n" + bean1.get();
    p.s. i seen same problem in community.oracle.com/thread/2577403 , but it happen in "war", not "ear", and seems successfully patched with patch №17424706

    Hi,
    It looks like there is patch exists for this issue.
    Patch 17198187
    Please try to download from the MOS or try to open a ticket with support.
    Regards,
    Kal

  • Should not happen unless default context failed to deploy

              Can somebody please throw some light on this error?
              <Mar 5, 2001 10:07:26 AM EST> <Error> <HTTP> <HttpServer5173817,null
              default ctx,POSDev01) found no context for "GET /classes/ringout_statelessSession3@/RingoutSessionBeanHomeImpl_WLStub.class
              HTTP/1.0". This should not happen unless the default context failed
              to deploy.>
              Myself and lot of other people in my team are getting this error
              when using beans in a cluster.
              I am getting this error consistently whenever I make some code
              changes in my bean class (not interface changes) and redeploy it
              and try to lookup through a stand-alone client.
              The only way I could find to overcome this problem is:
              1) edit config.xml to remove the Application element completely
              corresponding to the bean
              2) remove jar files from the applications directory
              3) re-deploy and run the client again.
              Thanks a lot
              Kiran Ganuthula
              

    Partly it could be WLS problem also. Under any circumstances default webapp should be able
              to deploy. I have seen somebody else also reported the same problem. The current problem is
              if you delete anything from apps dir, the corresponding entry is not being deleted from config.xml
              So next time when you boot the server, it tries to deploy the webapp and eventually it fails.
              I 'm not sure if this is the situation in your case.
              In anycase somehow Targets tag is not being picking up. That's why i asked you add
              "WebServers" tag. I think we have done some major changes in SP1, to make sure that
              default webapp deploys all the times.
              If you still have problems, post it to servlet or management group, we will discuss there.
              Kumar
              Kiran G wrote:
              > I edited the config.xml ONLY after getting this error. And, it worked.
              >
              > BTW, can you please be more specific about the changes to config.xml
              > to solve the problem?
              > If possible, can you give pertinent portion(s) of config.xml, highlighting
              > the changes.
              >
              > Thanks
              > Kiran G
              >
              > Kumar Allamraju <[email protected]> wrote:
              > >
              > >
              > >It appears your "default webapp" failed to deploy.
              > >Did you messed up with the config.xml?.
              > >
              > >Add the following to your default webapp tag?
              > >
              > ><Application
              > > Deployed="true"
              > > Name="DefaultWebApp_vindev1"
              > > Path="./config/vindev1/applications"
              > > >
              > > <WebAppComponent
              > > Name="DefaultWebApp_vindev1"
              > > Targets="vindev1"
              > > WebServers="vindev1"
              > > URI="DefaultWebApp_vindev1"
              > > />
              > > </Application>
              > >
              > >
              > >Here vindev1 is my domain's name..
              > >
              > >BTW, this is not a clustering question. So you better
              > >post it to servlet newsgroup where you get much
              > >better answers..
              > >
              > >Kiran G wrote:
              > >
              > >> I forgot to give these details about the problem.
              > >> I am running this cluster using WebLogic 6.0 on a SUN
              > >sparc machine.
              > >>
              > >> The error text given in my original posting appears
              > >in the managed
              > >> weblogic server's log. The exception that the client
              > >receives while
              > >> lookup is :
              > >>
              > >> javax.naming.CommunicationException. Root exception
              > >is java.rmi.UnmarshalException:
              > >> failed to unmarshal class java.lang.Object; nested exception
              > >is:
              > >> java.lang.ClassNotFoundException: RingoutSessionBeanHomeImpl_WLStub
              > >> java.lang.ClassNotFoundException: RingoutSessionBeanHomeImpl_WLStub
              > >>
              > >> "Kiran G" <[email protected]> wrote:
              > >> >
              > >> >Can somebody please throw some light on this error?
              > >> >
              > >> ><Mar 5, 2001 10:07:26 AM EST> <Error> <HTTP> <HttpServer5173817,null
              > >> >default ctx,POSDev01) found no context for "GET /classes/ringout_statelessSession3@/RingoutSessionBeanHomeImpl_WLStub.class
              > >> >HTTP/1.0". This should not happen unless the default
              > >context
              > >> >failed
              > >> >to deploy.>
              > >> >
              > >> >Myself and lot of other people in my team are getting
              > >> >this error
              > >> >when using beans in a cluster.
              > >> >
              > >> >I am getting this error consistently whenever I make
              > >some
              > >> >code
              > >> >changes in my bean class (not interface changes) and
              > >redeploy
              > >> >it
              > >> >and try to lookup through a stand-alone client.
              > >> >
              > >> >The only way I could find to overcome this problem
              > >is:
              > >> >1) edit config.xml to remove the Application element
              > >completely
              > >> >corresponding to the bean
              > >> >2) remove jar files from the applications directory
              > >> >3) re-deploy and run the client again.
              > >> >
              > >> >Thanks a lot
              > >> >Kiran Ganuthula
              > >> >
              > >> >
              > >> >
              > >> >
              > >> >
              > >
              > >
              > ><!doctype html public "-//w3c//dtd html 4.0 transitional//en">
              > ><html>
              > >It appears your "default webapp" failed to deploy.
              > ><br>Did you messed up with the config.xml?.
              > ><p>Add the following to your default webapp tag?
              > ><p><Application
              > ><br> Deployed="true"
              > ><br> Name="DefaultWebApp_vindev1"
              > ><br> Path="./config/vindev1/applications"
              > ><br> >
              > ><br> <WebAppComponent
              > ><br> Name="DefaultWebApp_vindev1"
              > ><br> Targets="vindev1"
              > ><br> <b><font color="#CC0000">
              > >WebServers="vindev1"</font></b>
              > ><br> URI="DefaultWebApp_vindev1"
              > ><br> />
              > ><br> </Application>
              > ><br>
              > ><p>Here vindev1 is my domain's name..
              > ><br><br>
              > >BTW, this is not a clustering question. So you better
              > >post it to servlet
              > >newsgroup where you get much
              > ><br>better answers..
              > ><p>Kiran G wrote:
              > ><blockquote TYPE=CITE>I forgot to give these details about
              > >the problem.
              > ><br>I am running this cluster using WebLogic 6.0 on a
              > >SUN sparc machine.
              > ><p>The error text given in my original posting appears
              > >in the managed
              > ><br>weblogic server's log. The exception that the client
              > >receives while
              > ><br>lookup is :
              > ><p>javax.naming.CommunicationException. Root exception
              > >is java.rmi.UnmarshalException:
              > ><br>failed to unmarshal class java.lang.Object; nested
              > >exception is:
              > ><br> java.lang.ClassNotFoundException:
              > >RingoutSessionBeanHomeImpl_WLStub
              > ><br>java.lang.ClassNotFoundException: RingoutSessionBeanHomeImpl_WLStub
              > ><p>"Kiran G" <[email protected]> wrote:
              > ><br>>
              > ><br>>Can somebody please throw some light on this error?
              > ><br>>
              > ><br>><Mar 5, 2001 10:07:26 AM EST> <Error> <HTTP>
              > ><HttpServer5173817,null
              > ><br>>default ctx,POSDev01) found no context for "GET /classes/ringout_statelessSession3@/RingoutSessionBeanHomeImpl_WLStub.class
              > ><br>>HTTP/1.0". This should not happen unless the default
              > >context
              > ><br>>failed
              > ><br>>to deploy.>
              > ><br>>
              > ><br>>Myself and lot of other people in my team are getting
              > ><br>>this error
              > ><br>>when using beans in a cluster.
              > ><br>>
              > ><br>>I am getting this error consistently whenever I make
              > >some
              > ><br>>code
              > ><br>>changes in my bean class (not interface changes)
              > >and redeploy
              > ><br>>it
              > ><br>>and try to lookup through a stand-alone client.
              > ><br>>
              > ><br>>The only way I could find to overcome this problem
              > >is:
              > ><br>>1) edit config.xml to remove the Application element
              > >completely
              > ><br>>corresponding to the bean
              > ><br>>2) remove jar files from the applications directory
              > ><br>>3) re-deploy and run the client again.
              > ><br>>
              > ><br>>Thanks a lot
              > ><br>>Kiran Ganuthula
              > ><br>>
              > ><br>>
              > ><br>>
              > ><br>>
              > ><br>></blockquote>
              > ></html>
              > >
              > >
              [att1.html]
              

  • 6.0 Newbie default context failed to deploy error

              I'm using WLS 6.0 SP2 and my servlets stopped working. They were working, but
              now only the console will work. I get an Error 400--Bad Request
              "The request could not be understood by the server due to malformed syntax. The
              client SHOULD NOT repeat the request without modifications."
              The following corresponding error shows up:
              <Jun 20, 2001 12:40:05 PM CDT> <Error> <HTTP> <HttpServer(3277721,null default
              ctx,myserve
              r) found no context for "GET /HelloWorld.jsp HTTP/1.1". This should not happen
              unless the
              default context failed to deploy.>
              I've attached my config.xml. Any suggestions?
              [config.xml]
              

              "Conor" <[email protected]> wrote in message
              news:3b30ef88$[email protected]..
              >
              > I'm using WLS 6.0 SP2 and my servlets stopped working. They were working,
              but
              > now only the console will work. I get an Error 400--Bad Request
              > "The request could not be understood by the server due to malformed
              syntax. The
              > client SHOULD NOT repeat the request without modifications."
              >
              > The following corresponding error shows up:
              >
              > <Jun 20, 2001 12:40:05 PM CDT> <Error> <HTTP> <HttpServer(3277721,null
              default
              > ctx,myserve
              > r) found no context for "GET /HelloWorld.jsp HTTP/1.1". This should not
              happen
              > unless the
              > default context failed to deploy.>
              >
              > I've attached my config.xml. Any suggestions?
              Bounce the server, try to redeploy app watch the console for errors if you
              are doing a hot deploy or when the server comes back up. Post the errors to
              the NG if you still have trouble.
              

  • Profitablility application failed to deploy into Essbase

    Hi,
    We have created one Profitability application in workspace application library. It is failed to deploy into the Essbase.
    Its showing essbase application names in Essbase but when we open outline, its empty.
    Here is what profitability logs say...
    <Mar 18, 2013 1:58:35 PM IST> <Info> <Common> <localhost> <Profitability0> <Thread-38> <<anonymous>> <> <0000JpwbJR86eLMpIKXBif1HHOK800002U> <1363595315826> <BEA-000628> <Created "1" resources for pool "EPMSystemRegistry", out of which "1" are available and "0" are unavailable.>
    <Mar 18, 2013 1:58:38 PM IST> <Info> <JDBC> <localhost> <Profitability0> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1363595318364> <BEA-001128> <Connection for pool "EPMSystemRegistry" has been closed.>
    <Mar 18, 2013 2:02:56 PM IST> <Info> <Common> <localhost> <Profitability0> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <0000JpwcKIH6eLMpIKXBif1HHOK800002q> <1363595576476> <BEA-000628> <Created "1" resources for pool "EPMSystemRegistry", out of which "1" are available and "0" are unavailable.>
    <Mar 18, 2013 2:02:56 PM IST> <Info> <Common> <localhost> <Profitability0> <[ACTIVE] ExecuteThread: '22' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <0000JpwcKIF6eLMpIKXBif1HHOK800002p> <1363595576695> <BEA-000628> <Created "1" resources for pool "profitability_datasource", out of which "1" are available and "0" are unavailable.>
    <Mar 18, 2013 2:02:59 PM IST> <Info> <JDBC> <localhost> <Profitability0> <[ACTIVE] ExecuteThread: '13' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1363595579415> <BEA-001128> <Connection for pool "profitability_datasource" has been closed.>
    <Mar 18, 2013 2:09:50 PM IST> <Info> <Common> <localhost> <Profitability0> <[ACTIVE] ExecuteThread: '4' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <0000JpwdtIR6eLMpIKXBif1HHOK8000030> <1363595990195> <BEA-000628> <Created "1" resources for pool "profitability_datasource", out of which "1" are available and "0" are unavailable.>
    <Mar 18, 2013 2:13:38 PM IST> <Info> <JDBC> <localhost> <Profitability0> <[ACTIVE] ExecuteThread: '6' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1363596218354> <BEA-001128> <Connection for pool "EPMSystemRegistry" has been closed.>
    <Mar 18, 2013 2:17:59 PM IST> <Info> <JDBC> <localhost> <Profitability0> <[ACTIVE] ExecuteThread: '11' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1363596479402> <BEA-001128> <Connection for pool "profitability_datasource" has been closed.>..
    Please help on it.

    EPMA uses studio to create Essbase cube. To narrow down the issue
    Can you connect to Essbase from EAS? (I'm not expecting any issues here)
    Try adding the same Essbase connection in Studio and create an application?
    Is this on static IP? Did anything change on the server side (IP change...)
    Regards
    Celvin

  • Failed DMP Deployment

    Failed DMP deployment of a video presentation containing 3 videos less than 50mb total.
    DMM 5.2.2
    DMP 4400  5.2.2.1
    Error Message:
    Not able to set FTP permissions.  Exception message is The IFMS DMP MIB utility could not connect to the DMP to  fetch the DMP's MIB.
    I tried to ftp videos directly to the DMP and was unable to. The first video appeared to transfer. Then disappeared from the directory.
    "ftp server" and "read and write" are on.
    Anyone have any ideas what I'm doing wrong?

    I am having a similar problem. Odd thing is that when I repeat the deployment steps manually it has not problem. This error only seems to work when I use the 'Play In Future' function.
    You also mentioned setting FTP - since I can send manually would that confirm that the FPT setting are correct? The DMP management account and the FTP service use the same password but different user ids.

  • Deployment error - Module failed to deploy - WLS 9.2

    I am attempting to deploy an EAR project from Workshop and it keeps failing. The error I keep getting is "referenced library module [email protected] failed to deploy". When I tried a different EAR project that I know I have deployed previously without a problem I get a similar error: "referenced library module [email protected] failed to deploy". Anyone have any idea what this problem could be? Is it a problem with the server or the project? Thanks.

    Hi,
    I am experiencing the same problem. Did you ever recieve a solution?
    Any help would be great!
    Thanks

  • Persistance layer failed to deploy

    Hi,
    When I try to build using ant file I am getting the following exception in WLS8.1
    [java] [EJB:011016]The persistence layer of the Entity EJB failed to deploy.
    [java] [EJB:011018]The file weblogic-cmp-rdbms-jar.xml, specified in a type-storage
    element of your weblogic-ejb-jar.xml descriptor, does not exi
    the JAR file.
    [java] at weblogic.ejb20.persistence.PersistenceType.setTypeSpecificFile(PersistenceType.java:469)
    My weblogic-ejb-jar.xml file is :
    <?xml version="1.0"?>
    <!DOCTYPE weblogic-ejb-jar PUBLIC "-//BEA Systems, Inc.//DTD WebLogic 8.1.0 EJB//EN"
    "http://www.bea.com/servers/wls810/dtd/weblogic-ejb-jar.dtd" >
    <weblogic-ejb-jar>
    <weblogic-enterprise-bean>
    <ejb-name>UserCheck</ejb-name>
    <jndi-name>Gateway_UC_Home</jndi-name>
    </weblogic-enterprise-bean>
    <weblogic-enterprise-bean>
    <ejb-name>Log</ejb-name>
    <message-driven-descriptor>
    <destination-jndi-name>ramtopic1</destination-jndi-name>
    </message-driven-descriptor>
    <jndi-name>Log</jndi-name>
    </weblogic-enterprise-bean>
    <weblogic-enterprise-bean>
    <ejb-name>GatewayUpdate</ejb-name>
    <entity-descriptor>
    <entity-cache>
    <max-beans-in-cache>1000</max-beans-in-cache>
    </entity-cache>
    <persistence>
    <persistence-use>
    <type-identifier>WebLogic_CMP_RDBMS</type-identifier>
    <type-version>7.0</type-version>
    <type-storage>weblogic-cmp-rdbms-jar.xml</type-storage>
    </persistence-use>
    </persistence>
    </entity-descriptor>
    <jndi-name>RemoteMsg_Update_Home</jndi-name>
    </weblogic-enterprise-bean>
    </weblogic-ejb-jar>
    My weblogic-cmp-rdbms-jar.xml file is:
    <!DOCTYPE weblogic-rdbms-jar PUBLIC
    '-//BEA Systems, Inc.//DTD WebLogic 8.1.0 EJB RDBMS Persistence//EN'
    'http://www.bea.com/servers/wls810/dtd/weblogic-rdbms20-persistence-810.dtd'>
    <weblogic-rdbms-jar>
    <weblogic-rdbms-bean>
    <ejb-name>GatewayUpdate</ejb-name>
    <data-source-name>gatewayPool</data-source-name>
    <table-name>textsms</table-name>
    <field-map>
    <cmp-field>user</cmp-field>
    <dbms-column>user</dbms-column>
    </field-map>
    <field-map>
    <cmp-field>msgid</cmp-field>
    <dbms-column>msgid</dbms-column>
    </field-map>
    <field-map>
    <cmp-field>msg</cmp-field>
    <dbms-column>msg</dbms-column>
    </field-map>
    <field-map>
    <cmp-field>org</cmp-field>
    <dbms-column>org</dbms-column>
    </field-map>
    <field-map>
    <cmp-field>mno</cmp-field>
    <dbms-column>mno</dbms-column>
    </field-map>
    <field-map>
    <cmp-field>status</cmp-field>
    <dbms-column>status</dbms-column>
    </field-map>
    </weblogic-rdbms-bean>
    <create-default-dbms-tables>False</create-default-dbms-tables>
    </weblogic-rdbms-jar>
    Pl.suggest.
    Ram

    Hi,
    I hv found out the issue.I hv not added one element tag in weblogic-cmp-rdbms-xml.jar.After
    adding the same the above error did not come.But when I create ear file I hv got
    another exception saying the jar file mentioned is not aval in the ear file.
    Below is the console output:
    Gateway.jar:
    [echo] creating basic ejb jar file ...
    [jar] Building jar: E:\myejb\staging\Gateway.jar
    [echo] ... done.
    [echo] appc'ing the ejb jar file ...
    [echo] appc'ing the ejb jar file ...
    [java] [appc] Created working directory: C:\DOCUME~1\ram\LOCALS~1\Temp\appcgen
    [java] [J2EE:160120]Error: The module, 'Gateway.jar', is declared in the
    application.xml descriptor but cannot be found in the ear file.
    BUILD FAILED
    file:E:/myejb/build.xml:95: Java returned: 1
    My build file is :
    <!--
    This file builds the EAR file for the SessBean.
    Invoke this file by providing the base directory of the weblogic
    installation. This can be done by using the following command
    line:
    ant -f build.xml -Dwlhome=f:\bea\weblogic81
    Before invoking ant, make sure that the optional.jar file
    has been copied into the lib directory of your ant installation.
    -->
    <project name="GatewayBean" default="all">
         <target name="init">
              <property name="srcdir" value="."/>
              <property name="java.classpath"
                   value="${wlhome}${file.separator}server${file.separator}lib${file.separator}weblogic.jar"/>
              <delete dir="classes"
                   includeEmptyDirs="true"
                   failonerror="false" />
              <delete dir="staging"
                   includeEmptyDirs="true"
                   failonerror="false"/>
              <echo message="creating staging area ..."/>
              <mkdir dir="staging"/>
              <echo message=" ... done."/>
              <!-- Define the WebLogic appc task -->
              <echo message="defining weblogic appc task ..."/>
              <taskdef name="appc"
                   classname="weblogic.ant.taskdefs.j2ee.Appc"
                   classpath="${java.classpath}"/>
              <echo message=" ... done."/>
         </target>
    <!-- target compiles all required classes -->
         <target name="compile" depends="init">
              <mkdir dir="classes"/>
              <echo message="compiling all sources ... "/>
              <javac srcdir="${srcdir}"
                   destdir="classes"
                   verbose="no"
                   classpath="${java.classpath}" />
              <echo message=" ... done."/>
         </target>
    <!-- target builds the jar file containing JSP helper classes -->
         <target name="JSPClasses.jar" depends="compile">
              <echo message="creating JSPClasses.jar ... "/>
              <jar jarfile="staging${file.separator}JSPClasses.jar">
                   <fileset dir="classes" includes="**/JSP*.class"/>
              </jar>
              <echo message=" ... done."/>
         </target>
    <!-- target builds the war file containing the web application -->
         <target name="Gateway.war" depends="init,JSPClasses.jar">
              <echo message="creating web archive ... "/>
              <war destfile="staging${file.separator}Gateway.war"
                        webxml="web.xml" >
                   <fileset dir="${srcdir}">
                        <include name="*.jsp"/>
                        <include name="*.html"/>
                   </fileset>
                   <lib dir="staging" includes="JSPClasses.jar"/>
              </war>
              <echo message=" ... done."/>
         </target>
    <!-- target builds the jar file containing all the EJBs -->
         <target name="Gateway.jar" depends="compile">
              <!-- First jar up the basic classes required for the EJBs -->
              <echo message="creating basic ejb jar file ... "/>
              <jar jarfile="staging${file.separator}Gateway.jar">
                   <zipfileset dir="."
                        prefix="META-INF"
                        includes="*.xml"/>
                   <fileset dir="classes"
                        excludes="**/JSP*.class"/>
              </jar>
              <echo message=" ... done."/>
              <!-- Next appc the jar file to ejb compile the ejbs-->
              <echo message="appc'ing the ejb jar file ... "/>
              <!-- Next appc the jar file to ejb compile the ejbs-->
              <echo message="appc'ing the ejb jar file ... "/>
              <java classname="weblogic.appc"
              failonerror="true"
              fork="true"
              classpath="${java.classpath}">
              <arg line="-basicClientJar -verbose -forceGeneration -classpath ${java.classpath}
    staging${file.separator}Gateway.jar"/>
              </java>
    <echo message=" ... done."/>
              <!--
              <java classname="weblogic.appc"
                   failonerror="true"
                   fork="true"
                   classpath="${java.classpath}">
                   <arg line="-basicClientJar -verbose -forceGeneration -classpath ${java.classpath}
    staging${file.separator}Gateway.jar"/>
              </java>
              -->
              <echo message=" ... done."/>
         </target>
    <!-- target builds the EAR file -->
         <target name="Gateway.ear"
              depends="init,Gateway.war,Gateway.jar">
              <echo message="creating enterprise archive ... "/>
              <jar jarfile="Gateway.ear">
                   <zipfileset dir="."
                        prefix="META-INF"
                        includes="application.xml"/>
                   <fileset dir="staging"
                        includes="Gateway.war,Gateway.jar"/>
              </jar>
              <echo message=" ... done."/>
         </target>
    <!--
         <target name="cleanup">
              <echo message="cleaning up ... "/>
              <delete dir="staging"
                   includeEmptyDirs="true"
                   failonerror="false"/>
              <delete dir="classes"
                   includeEmptyDirs="true"
                   failonerror="false"/>
              <echo message=" ... done."/>
         </target>
    -->
         <target name="all" depends="init, Gateway.ear">
              <echo message="Done building ./Gateway.ear"/>
         </target>
    </project>
    My application.xml file is :
    <?xml version="1.0" encoding="UTF-8"?>
    <!DOCTYPE application PUBLIC '-//Sun Microsystems, Inc.//DTD J2EE Application
    1.3//EN' 'http://java.sun.com/dtd/application_1_3.dtd'>
    <application>
    <display-name>Gateway</display-name>
    <description>Gateway</description>
    <module>
    <ejb>Gateway.jar</ejb>
    </module>
    </application>
    After doing jar tvf :
    GMT+05:30 2004 META-INF/
    GMT+05:30 2004 META-INF/MANIFEST.MF
    GMT+05:30 2004 META-INF/Copy of build.xml
    GMT+05:30 2004 META-INF/ejb-jar.xml
    GMT+05:30 2004 META-INF/build.xml
    GMT+05:30 2004 META-INF/application.xml
    GMT+05:30 2004 META-INF/web.xml
    GMT+05:30 2004 META-INF/weblogic-cmp-rdbms-jar.xml
    GMT+05:30 2004 META-INF/weblogic-ejb-jar.xml
    GMT+05:30 2004 gateway/
    GMT+05:30 2004 gateway/LogBean.class
    GMT+05:30 2004 gateway/Gateway_UC.class
    GMT+05:30 2004 gateway/Gateway_UC_Home.class
    GMT+05:30 2004 gateway/Gateway_UC_Bean.class
    GMT+05:30 2004 gateway/Msg_Update.class
    GMT+05:30 2004 gateway/Msg_Update_Home.class
    GMT+05:30 2004 gateway/Msg_Update_Bean.class
    GMT+05:30 2004 gateway/UpdatePK.class
    Pl.advise.
    Ram
    Rob Woollen <[email protected]> wrote:
    I'd suggest you build the CMP example that ships with WLS. Then compare
    the structure of its ejb-jar with your application.
    If you're still having problems, can you show me the output of jar tvf
    on your ejb-jar file? It's looking for the CMP descriptor in the
    META-INF directory.
    -- Rob
    Ram wrote:
    Hi,
    When I try to build using ant file I am getting the following exceptionin WLS8.1
    [java] [EJB:011016]The persistence layer of the Entity EJB failedto deploy.
    [java] [EJB:011018]The file weblogic-cmp-rdbms-jar.xml, specified ina type-storage
    element of your weblogic-ejb-jar.xml descriptor, does not exi
    the JAR file.
    [java] at weblogic.ejb20.persistence.PersistenceType.setTypeSpecificFile(PersistenceType.java:469)
    My weblogic-ejb-jar.xml file is :
    <?xml version="1.0"?>
    <!DOCTYPE weblogic-ejb-jar PUBLIC "-//BEA Systems, Inc.//DTD WebLogic8.1.0 EJB//EN"
    "http://www.bea.com/servers/wls810/dtd/weblogic-ejb-jar.dtd" >
    <weblogic-ejb-jar>
    <weblogic-enterprise-bean>
    <ejb-name>UserCheck</ejb-name>
    <jndi-name>Gateway_UC_Home</jndi-name>
    </weblogic-enterprise-bean>
    <weblogic-enterprise-bean>
    <ejb-name>Log</ejb-name>
    <message-driven-descriptor>
    <destination-jndi-name>ramtopic1</destination-jndi-name>
    </message-driven-descriptor>
    <jndi-name>Log</jndi-name>
    </weblogic-enterprise-bean>
    <weblogic-enterprise-bean>
    <ejb-name>GatewayUpdate</ejb-name>
    <entity-descriptor>
    <entity-cache>
    <max-beans-in-cache>1000</max-beans-in-cache>
    </entity-cache>
    <persistence>
    <persistence-use>
    <type-identifier>WebLogic_CMP_RDBMS</type-identifier>
    <type-version>7.0</type-version>
    <type-storage>weblogic-cmp-rdbms-jar.xml</type-storage>
    </persistence-use>
    </persistence>
    </entity-descriptor>
    <jndi-name>RemoteMsg_Update_Home</jndi-name>
    </weblogic-enterprise-bean>
    </weblogic-ejb-jar>
    My weblogic-cmp-rdbms-jar.xml file is:
    <!DOCTYPE weblogic-rdbms-jar PUBLIC
    '-//BEA Systems, Inc.//DTD WebLogic 8.1.0 EJB RDBMS Persistence//EN'
    'http://www.bea.com/servers/wls810/dtd/weblogic-rdbms20-persistence-810.dtd'>
    <weblogic-rdbms-jar>
    <weblogic-rdbms-bean>
    <ejb-name>GatewayUpdate</ejb-name>
    <data-source-name>gatewayPool</data-source-name>
    <table-name>textsms</table-name>
    <field-map>
    <cmp-field>user</cmp-field>
    <dbms-column>user</dbms-column>
    </field-map>
    <field-map>
    <cmp-field>msgid</cmp-field>
    <dbms-column>msgid</dbms-column>
    </field-map>
    <field-map>
    <cmp-field>msg</cmp-field>
    <dbms-column>msg</dbms-column>
    </field-map>
    <field-map>
    <cmp-field>org</cmp-field>
    <dbms-column>org</dbms-column>
    </field-map>
    <field-map>
    <cmp-field>mno</cmp-field>
    <dbms-column>mno</dbms-column>
    </field-map>
    <field-map>
    <cmp-field>status</cmp-field>
    <dbms-column>status</dbms-column>
    </field-map>
    </weblogic-rdbms-bean>
    <create-default-dbms-tables>False</create-default-dbms-tables>
    </weblogic-rdbms-jar>
    Pl.suggest.
    Ram

  • NT4.0 - Default Contect Failed To Deploy - where should I look to find out why ?

    Hi All,
    I'm attempting a first install of weblogic 6.0 on nt4.0.
    The console starts, but when I try to display an html file I get the message on the log
    'default contect failed to deploy'.
    Any idea's
    TIA
    Bill

    Hi All,
    I'm attempting a first install of weblogic 6.0 on nt4.0.
    The console starts, but when I try to display an html file I get the message on the log
    'default contect failed to deploy'.
    Any idea's
    TIA
    Bill

Maybe you are looking for

  • HT1551 Apple TV and iPad 2 very low resolution pictures - how to resolve please?

    Hi We've just bought Apple TV and it works fine with Netflix, with good resolution etc. However resolution is really poor and blurred when using iPad 2. What's more when iPad 2 is near the TV Netflix also goes low resolution and fuzzy. I've been havi

  • Can we connect 2 ECC to a single PI system.

    hi , can we connect 2 ECC to a single PI system. here we would be using proxies in the 2 ECC. Is it possible to enable the SProxy for both systems. EG: ECC1< -> PI (A)<-.>APO        ECC2<-->PI (A)<-.>APO Regards, Praveen K Edited by: praveen kalwa on

  • Error from appleSyncNotifier.exe : ista pc . how can i solve this problem?

    cannot find procedure xmlTextreaderConst in DDL-bestand libxml2.dll . get this always after i start up mu windows vista pc . how can i solve this problem?

  • Pages won"t open after upgrade to Snow

    Should"ve known there were going to be problems...now after installing snow leopard, my pages will not open, my mail will not open, keynote, numbers. ical...a huge number of issues, and now with schol starting I cannot use my computer to do any work.

  • Can not login app store

    I got some problem for loging in to app store. The screen shown as the attachment image. Could some once please help me how can I solve it??