weblogic.management.DeploymentException: [J2EE:160177]The application at "D:\Oracle\Middleware\Oracle_SOA1\soa\connectors\DbAdapter.rar" was not recognized as a valid application type. If this is an EAR file, please ensure the META-INF/application.xml exists. EJB-JARs should have a META-INF/ejb-jar.xml or corresponding annotations exist. If this is an exploded WAR, the name of directory must be end with ".war". RARs require a META-INF/ra.xml. A JMS deployment should be an XML file whose name ends with "-jms.xml". A JDBC deployment should be an XML file whose name ends with "-jdbc.xml". For other application types, please consult the WebLogic Server documentation.

Oracle Community | SivaBalan19 | 8 months ago
  1. 0

    Failed to start 'soa-infra'

    Oracle Community | 8 months ago | SivaBalan19
    weblogic.management.DeploymentException: [J2EE:160177]The application at "D:\Oracle\Middleware\Oracle_SOA1\soa\connectors\DbAdapter.rar" was not recognized as a valid application type. If this is an EAR file, please ensure the META-INF/application.xml exists. EJB-JARs should have a META-INF/ejb-jar.xml or corresponding annotations exist. If this is an exploded WAR, the name of directory must be end with ".war". RARs require a META-INF/ra.xml. A JMS deployment should be an XML file whose name ends with "-jms.xml". A JDBC deployment should be an XML file whose name ends with "-jdbc.xml". For other application types, please consult the WebLogic Server documentation.
  2. 0

    Cluster deployment of taskform

    Oracle Community | 5 years ago | RobertMetcalf
    weblogic.management.DeploymentException: [J2EE:160177]The application at "/export/home/awlsdev/admin/soadomain/mserver/soa_domain/servers/WLS_SOA1/stage/RJMTest_HumanTask002_Form" was not recognized as a valid application type. If this is an EAR file, please ensure the META-INF/application.xml exists. EJB-JARs should have a META-INF/ejb-jar.xml or corresponding annotations exist. If this is an exploded WAR, the name of directory must be end with ".war". RARs require a META-INF/ra.xml. A JMS deployment should be an XML file whose name ends with "-jms.xml". A JDBC deployment should be an XML file whose name ends with "-jdbc.xml". For other application types, please consult the WebLogic Server documentation.
  3. 0

    Unable to deploy Mediator to soa_server

    Oracle Community | 2 years ago | Justin_Michael_Raj
    weblogic.management.DeploymentException: [J2EE:160177] The application at "C:\Oracle\orasoa11g\wls\Middleware\user_projects\domains\soa_domain\servers\soa_server1\stage\sca_mediator1_rev1\sca_mediator1_rev1.0.jar" was not recognized as a valid application type. If this is an EAR file, please ensure the META-INF/application.xml exists. EJB-JARs should have a META-INF/ejb-jar.xml or corresponding annotations exist. If this is an exploded WAR, the name of directory must be end with ".war". RARs require a META-INF/ra.xml. A JMS deployment should be an XML file whose name ends with "-jms.xml". A JDBC deployment should be an XML file whose name ends with "-jdbc.xml". For other application types, please consult the WebLogic Server documentation.
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    weblogic.descriptor.BeanAlreadyExistsException:... | Oracle Community

    oracle.com | 11 months ago
    weblogic.management.DeploymentException: [J2EE:160177]The application at "C:\Users\10017134\AppData\Roaming\JDeveloper\system11.1.1.6.38.61.92\o.j2ee\drs\SaiApp" was not recognized as a valid application type. If this is an EAR file, please ensure the META-INF/application.xml exists. EJB-JARs should have a META-INF/ejb-jar.xml or corresponding annotations exist. If this is an exploded WAR, the name of directory must be end with ".war". RARs require a META-INF/ra.xml. A JMS deployment should be an XML file whose name ends with "-jms.xml". A JDBC deployment should be an XML file whose name ends with "-jdbc.xml". For other application types, please consult the WebLogic Server documentation.
  6. 0

    EPM 11.1.2.3 - Foundation Services going to ADMIN state

    Oracle Community | 2 years ago | $anty
    weblogic.management.DeploymentException: [J2EE:160177]The application at "/opt/app/Oracle/Middleware/EPMSystem11R1/common/epmstatic" was not recognized as a valid application type. If this is an EAR file, please ensure the META-INF/application.xml exists. EJB-JARs should have a META-INF/ejb-jar.xml or corresponding annotations exist. If this is an exploded WAR, the name of directory must be end with ".war". RARs require a META-INF/ra.xml. A JMS deployment should be an XML file whose name ends with "-jms.xml". A JDBC deployment should be an XML file whose name ends with "-jdbc.xml". For other application types, please consult the WebLogic Server documentation.

    Not finding the right solution?
    Take a tour to get the most out of Samebug.

    Tired of useless tips?

    Automated exception search integrated into your IDE

    Root Cause Analysis

    1. weblogic.management.DeploymentException

      [J2EE:160177]The application at "D:\Oracle\Middleware\Oracle_SOA1\soa\connectors\DbAdapter.rar" was not recognized as a valid application type. If this is an EAR file, please ensure the META-INF/application.xml exists. EJB-JARs should have a META-INF/ejb-jar.xml or corresponding annotations exist. If this is an exploded WAR, the name of directory must be end with ".war". RARs require a META-INF/ra.xml. A JMS deployment should be an XML file whose name ends with "-jms.xml". A JDBC deployment should be an XML file whose name ends with "-jdbc.xml". For other application types, please consult the WebLogic Server documentation.

      at weblogic.application.internal.DeploymentManagerImpl.createDeployment()
    2. weblogic.application.internal
      DeploymentManagerImpl.createDeployment
      1. weblogic.application.internal.DeploymentManagerImpl.createDeployment(DeploymentManagerImpl.java:106)
      1 frame
    3. weblogic.deploy.internal
      DeploymentServiceDispatcher.prepare
      1. weblogic.deploy.internal.targetserver.BasicDeployment.createDeployment(BasicDeployment.java:149)
      2. weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:203)
      3. weblogic.deploy.internal.targetserver.operations.StartOperation.createAndPrepareContainer(StartOperation.java:94)
      4. weblogic.deploy.internal.targetserver.operations.StartOperation.doPrepare(StartOperation.java:107)
      5. weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
      6. weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:747)
      7. weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1216)
      8. weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:250)
      9. weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:159)
      9 frames
    4. weblogic.deploy.service
      DeploymentReceiverCallbackDeliverer$1.run
      1. weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:171)
      2. weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:13)
      3. weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:46)
      3 frames
    5. weblogic.work
      ExecuteThread.run
      1. weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:545)
      2. weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
      3. weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
      3 frames