weblogic.management.DeploymentException: [J2EE:160177]The application at "D:\Oracle\Middleware\wlserver_10.3\server\lib\jms-notran-adp.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 | 1 year ago
tip
Your exception is missing from the Samebug knowledge base.
Here are the best solutions we found on the Internet.
Click on the to mark the helpful solution and get rewards for you help.
  1. 0

    Failed to start 'soa-infra'

    Oracle Community | 1 year ago | SivaBalan19
    weblogic.management.DeploymentException: [J2EE:160177]The application at "D:\Oracle\Middleware\wlserver_10.3\server\lib\jms-notran-adp.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

    War file Deployment Exception

    Oracle Community | 1 decade ago | 666705
    weblogic.management.DeploymentException: [J2EE:160177]The application at "D:\bea\user_projects\domains\reporter\.\autodeploy\CAReporterEnabler.war" 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. WAR files require a WEB-INF/web.xml, and 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

    EPM 11.1.2.3 - Foundation Services going to ADMIN state

    Oracle Community | 3 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.
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    Upgrade Issue - Hyperion 11.1.2.1 to 11.1.2.4

    Oracle Community | 2 years ago | dwhpc
    weblogic.management.DeploymentException: [J2EE:160177]The application at "C:\Oracle\Middleware\user_projects\domains\EPMSystem\servers\FoundationServices0\stage\proxyservlet\11.1.2.2\proxyservlet" 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

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

    oracle.com | 1 year 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.

    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\wlserver_10.3\server\lib\jms-notran-adp.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
      AppDeployment.prepare
      1. weblogic.deploy.internal.targetserver.BasicDeployment.createDeployment(BasicDeployment.java:149)
      2. weblogic.deploy.internal.targetserver.AppDeployment.prepare(AppDeployment.java:114)
      2 frames
    4. weblogic.management.deploy
      DeploymentServerService.start
      1. weblogic.management.deploy.internal.DeploymentAdapter$1.doPrepare(DeploymentAdapter.java:39)
      2. weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:191)
      3. weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
      4. weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:240)
      5. weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:165)
      6. weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
      7. weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:180)
      8. weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:96)
      8 frames
    5. weblogic.t3.srvr
      SubsystemRequest.run
      1. weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
      1 frame
    6. weblogic.work
      ExecuteThread.run
      1. weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
      2. weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
      2 frames