weblogic.management.DeploymentException: Application Jonathan-rmi-server is a WAR file, but it contains > 1 component.

free.fr | 3 months ago
  1. 0

    2011 July

    free.fr | 7 months ago
    weblogic.management.DeploymentException: Application Jonathan-rmi-server is a WAR file, but it contains > 1 component.
  2. 0

    weblogic.management.DeploymentException: Application XYZ is a WAR file, but it contains > 1 component

    free.fr | 3 months ago
    weblogic.management.DeploymentException: Application Jonathan-rmi-server is a WAR file, but it contains > 1 component.
  3. 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\AqAdapter.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.
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 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\JmsAdapter.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.
  6. 0

    Failed to start 'soa-infra'

    Oracle Community | 8 months 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.

    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

      Application Jonathan-rmi-server is a WAR file, but it contains > 1 component.

      at weblogic.servlet.internal.WarDeployment.createModule()
    2. Atmosphere weblogic
      WarDeploymentFactory.createDeployment
      1. weblogic.servlet.internal.WarDeployment.createModule(WarDeployment.java:40)
      2. weblogic.servlet.internal.WarDeployment.<init>(WarDeployment.java:27)
      3. weblogic.servlet.internal.WarDeploymentFactory.createDeployment(WarDeploymentFactory.java:36)
      3 frames
    3. weblogic.application.internal
      DeploymentManagerImpl.createDeployment
      1. weblogic.application.internal.DeploymentManagerImpl.createDeployment(DeploymentManagerImpl.java:84)
      1 frame
    4. 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:202)
      3. weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:98)
      4. weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
      5. weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:747)
      6. weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1216)
      7. weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:250)
      8. weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:159)
      8 frames
    5. 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
    6. weblogic.work
      ExecuteThread.run
      1. weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
      2. weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
      3. weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
      3 frames