com.sun.enterprise.admin.common.exception.DeploymentException: Unrecognized module type for /ssi/work/sample-code/EJBModulePersistence/build/jar; the archive may be incorrectly constructed, non-existent, or inaccessible from the server. > For example, an application client jar should include the proper manifest file entry, and an ejb jar should contain at least one EJB. >

Oracle Community | mstn | 8 years ago
tip
Do you know that we can give you better hits? Get more relevant results from Samebug’s stack trace search.
  1. 0

    Glassfish V2, deploying EJB module

    Oracle Community | 8 years ago | mstn
    com.sun.enterprise.admin.common.exception.DeploymentException: Unrecognized module type for /ssi/work/sample-code/EJBModulePersistence/build/jar; the archive may be incorrectly constructed, non-existent, or inaccessible from the server. > For example, an application client jar should include the proper manifest file entry, and an ejb jar should contain at least one EJB. >

    Root Cause Analysis

    1. com.sun.enterprise.admin.common.exception.DeploymentException

      Unrecognized module type for /ssi/work/sample-code/EJBModulePersistence/build/jar; the archive may be incorrectly constructed, non-existent, or inaccessible from the server. > For example, an application client jar should include the proper manifest file entry, and an ejb jar should contain at least one EJB. >

      at com.sun.enterprise.deployment.phasing.DeploymentServiceUtils.getTypeFromFile()
    2. com.sun.enterprise
      DeployThread.run
      1. com.sun.enterprise.deployment.phasing.DeploymentServiceUtils.getTypeFromFile(DeploymentServiceUtils.java:1273)
      2. com.sun.enterprise.deployment.phasing.PEDeploymentService.deploy(PEDeploymentService.java:752)
      3. com.sun.enterprise.management.deploy.DeployThread.deploy(DeployThread.java:187)
      4. com.sun.enterprise.management.deploy.DeployThread.run(DeployThread.java:225)
      4 frames