Uploaded image for project: 'Codehaus Cargo'
  1. CARGO-1301

WebSphere deployer should take into account the server name

    Details

    • Type: Bug
    • Status: Closed (View workflow)
    • Priority: Major
    • Resolution: Fixed
    • Affects versions: None
    • Fix versions: 1.4.13
    • Components: WebSphere
    • Labels:
      None

      Description

      The WebSphere deployer currently ignores the server name:

      [INFO] [talledLocalContainer] WASX7357I: By request, this scripting client is not connected to any server process. Certain configuration and application operations will be available in local mode.
      [INFO] [talledLocalContainer] ADMA5016I: Installation of cargo-deployable-px started.
      [INFO] [talledLocalContainer] ADMA5026E: No valid target is specified in ObjectName WebSphere:cell=cargoNodeCell,node=cargoNode,server=server1 for module px.war+WEB-INF/web.xml.
      

      Note that my profile was created with server name set to cargoServer. I'm not sure why, but it looks like server name is not given, and therefore defaults to server1.

        Attachments

          Activity

            People

            • Assignee:
              savasalitokmen Savas Ali Tokmen (Inactive)
              Reporter:
              savasalitokmen Savas Ali Tokmen (Inactive)
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: