Uploaded image for project: 'AeroGear'
  1. AeroGear
  2. AEROGEAR-6028

Unified Push Server Wildfly 8 Final installation registration exception

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • None
    • None
    • None

    • Container used is Wildfly 8.0.0.Final

    • Hide

      Deploy the latest Aerogear Unified Push Server version (from branch master, 0.10.0) on a Wildfly 8.0.0.Final server.
      After trying to register an (android app) installation, the reported exception is thrown.

      Show
      Deploy the latest Aerogear Unified Push Server version (from branch master, 0.10.0) on a Wildfly 8.0.0.Final server. After trying to register an (android app) installation, the reported exception is thrown.

    Description

      I have deployed the Unified push server (latest version, from master branch)
      on wildfly 8 final. Everything seems to be normal,
      except than when an app makes a registration (an android app installation),
      there is the following exception thrown:

      WARN [org.jboss.resteasy.core.ExceptionHandler] (default task-3) Failed
      executing POST /registry/device:
      org.jboss.resteasy.core.NoMessageBodyWriterFoundFailure: Could not find
      MessageBodyWriter for response object of type:
      org.jboss.aerogear.unifiedpush.model.InstallationImpl of media type:
      application/octet-stream

      Attachments

        Issue Links

          blocks

          Bug - A problem that impairs or prevents the functions of the product. AEROGEAR-4739 Error while register IOS device through cordova push plugin

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved
          is blocked by

          Sub-task - The sub-task of the issue AEROGEAR-7045 Deployment fails on WildFly 8.0.0.Final

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved

          Activity

            People

              mwessend@redhat.com Matthias Wessendorf
              jchrist7_jira Ioannis Christodoulou (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: