glassfish
  1. glassfish
  2. GLASSFISH-16954

asadmin complains about "Unknown plain text format" when deployment fails

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 3.1
    • Fix Version/s: None
    • Component/s: admin
    • Labels:
      None
    • Environment:

      Win7 Pro SP1 64 Bit de_DE

      Description

      I am trying to deploy an application using "asadmin deploy --retrieve . SuperSimple.ear". Due to a bug in that EAR, deployment fails. This is a typical situation when still in development, so asadmin should be clever enough to handle this with a message like "Deployment failed due to...".

      But what it actually says is "Unknown plain text format.". Least programmers will understand that this actually means: "Everything is OK, you just have a typo in your EAR"...!

      c:\Users\Karg\workspace\CreateComplaintsRS\dist>C:\glassfish3\bin\asadmin deploy --retrieve . SuperSimple.ear
      remote failure: Unknown plain text format. A properly formatted response from a PlainTextActionReporter
      always starts with one of these 2 strings: PlainTextActionReporterSUCCESS or PlainTextActionReporterFAILURE. The response we re
      ceived from the server was not understood: Signature-Version: 1.0
      message: Error occurred during deployment: Exception while preparing t
      he app : Exception [EclipseLink-28018] (Eclipse Persistence Services

      • 2.2.0.v20110202-r8913): org.eclipse.persistence.exceptions.EntityMa
        nagerSetupException
        Exception Description: Predeployment of
        PersistenceUnit [QUIPSY] failed.
        Internal Exception: Excepti
        on [EclipseLink-7163] (Eclipse Persistence Services - 2.2.0.v20110202
        %%%EO13): org.eclipse.persistence.exceptions.ValidationException
        L%%%Exception Description: Entity class [class de.quipsy.persistency.
        suppliedPart.SuppliedPartPk] has both an @EmbdeddedId (on attribute [
        pk]) and an @Id (on attribute [customerId]. Both ID types cannot be s
        pecified on the same entity.. Please see server.log for more details.

      Exception while invoking class org.glassfish.persistence.jpa
      .JPADeployer prepare method : javax.persistence.PersistenceException:
      Exception [EclipseLink-28018] (Eclipse Persistence Services - 2.2.0.
      v20110202-r8913): org.eclipse.persistence.exceptions.EntityManagerSet
      upException
      Exception Description: Predeployment of Persiste
      nceUnit [QUIPSY] failed.
      Internal Exception: Exception [Ecli
      pseLink-7163] (Eclipse Persistence Services - 2.2.0.v20110202-r8913):
      org.eclipse.persistence.exceptions.ValidationException
      Exce
      ption Description: Entity class [class de.quipsy.persistency.supplied
      Part.SuppliedPartPk] has both an @EmbdeddedId (on attribute [pk]) and
      an @Id (on attribute [customerId]. Both ID types cannot be specified
      on the same entity.
      Exception [EclipseLink-28018] (Eclipse P
      ersistence Services - 2.2.0.v20110202-r8913): org.eclipse.persistence
      .exceptions.EntityManagerSetupException
      Exception Description: Prede
      ployment of PersistenceUnit [QUIPSY] failed.
      Internal Exception: Exc
      eption [EclipseLink-7163] (Eclipse Persistence Services - 2.2.0.v2011
      0202-r8913): org.eclipse.persistence.exceptions.ValidationException

      Exception Description: Entity class [class de.quipsy.persistency.supp
      liedPart.SuppliedPartPk] has both an @EmbdeddedId (on attribute [pk])
      and an @Id (on attribute [customerId]. Both ID types cannot be speci
      fied on the same entity.
      name_value: SuperSimple
      name_name: name
      keys: name
      use-main-children-attribute: false
      exit-code: FAILURE

      Command deploy failed.

      c:\Users\Karg\workspace\CreateComplaintsRS\dist>

        Activity

          People

          • Assignee:
            Byron Nevins
            Reporter:
            mkarg
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: