Uploaded image for project: 'ServiceMix'
  1. ServiceMix
  2. SM-1784

Impossible to re-deploy SA in case of SA contain http SU with incorrect http component "locationURI" parameter value.

VotersWatch issueWatchersLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Won't Fix
    • 3.3
    • None
    • servicemix-assembly
    • None
    • Windows XP SP 2

    Description

      Create some SA that contains http SU with following xbean.xml file content:
      <?xml version="1.0" encoding="UTF-8" standalone="no"?>
      <beans xmlns:ns="http://servicemix.apache.org/http/1.0" xmlns:sa="FakeWS" xmlns:sm="http://servicemix.apache.org/config/1.0">
      <classpath>
      <location>.</location>
      </classpath>
      <ns:endpoint defaultMep="http://www.w3.org/2004/08/wsdl/in-out" endpoint="FakeWS_http" locationURI="http:dshfhsdkhkj" role="consumer" service="sa:http_1" soap="true" targetEndpoint="FakeWS_eip_2" targetService="sa:eip_2"/>
      </beans>

      Pay attention to locationURI="http:dshfhsdkhkj" value.
      Place this SA to "hotdeploy" folder and start SM.
      SM started, but exception appeared when try to deploy SA:
      <stack-trace><![CDATA[java.lang.IllegalArgumentException: port out of range:-1
      Delete this SA from "hotdeploy" folder, change "locationURI" to correct (e.g. "locationURI="http://localhost:5005/httpserver/") and copy SA to "hotdeploy" folder
      Problem:
      SA can't be deployed, exception appeared:
      <loc-message>An external endpoint for service

      {FakeWS}

      http_1 and endpoint FakeWS_http_1 is already registered
      So it is impossible re-deploy SA with incorrect http "locationURI" without restarting SM

      Attachments

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            Unassigned Unassigned
            evise Max Varganovskyy
            Votes:
            1 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment