Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

WsTopology returns incorrect information

Description

Calling TpServiceQuery to locate the ws_ecl service returns this:

Should I expect the "Service" value to be "ws_ecl"?

Conclusion

None

blocks

Activity

Show:

Gordon Smith July 27, 2016 at 12:58 PM

Yes please.

Kanghua Wang July 25, 2016 at 9:16 PM

Looks like that the service type is also not a hard value. How about I give you the BuildSet (a new field in <TpBinding>)?

Gordon Smith July 25, 2016 at 8:30 PM

@kevin - I think the previous fix is putting "EspProcess" into the service type?

This is what I am getting on my 6.0.4 build:

Given "myws_ecl" is user configurable then there is no way to know its a ws_ecl service?

Ideally what I would like is:

Where "ws_ecl" is not user configurable (at least without the user going out of their way)?

Kanghua Wang July 25, 2016 at 5:10 PM

A user can edit it using ConfigMgr. I think you may use <ServiceType>ws_ecl</ServiceType> to get the port number (a fix in https://github.com/hpcc-systems/HPCC-Platform/pull/8253).

Gordon Smith July 25, 2016 at 4:25 PM

I saw you change in the config file - is that a "hard" value, or can the user edit it after the fact?

Fixed
Pinned fields
Click on the next to a field label to start pinning.

Details

Components

Assignee

Reporter

Priority

Compatibility

Point

Fix versions

Pull Request URL

Affects versions

Created July 22, 2016 at 10:44 AM
Updated July 29, 2016 at 9:31 AM
Resolved July 29, 2016 at 9:31 AM