Unable to list virtual services in vscatalog when using custom ports

Document ID : KB000095856
Last Modified Date : 23/05/2018
Show Technical Document Details
Issue:
VSCatalog is unable to list the virtual services when custom port numbers are used for all the DevTest Solutions components.
For example: In the dradis.properties, local.properties and site.properties  added custom port numbers. 
dradis.webserver.port=2506
lisa.webserver.port=2505

ED  URL shows - http://localhost:2506 
Connect  VSCatalog to  http://localhost:2506    and it says connected. But, in the logs  we see that it is still reverting to default Ports 1505 and 1506. 
`2018-04-17 14:40:40.891 INFO 897841 --- [onPool-worker-1] c.c.a.s.b.s.v.l.DefaultFetchVsesService : Registry url: http://ABC-15-131-117:1505/` in the logs 
2018-04-17 15:23:55.269  INFO 897841 --- [onPool-worker-1] okhttp3.OkHttpClient                     : --> GET http://ABC-15-131-117:1505/lisa-virtualize-invoke/api/v2/vses
2018-04-17 15:23:55.270  INFO 897841 --- [onPool-worker-1] okhttp3.OkHttpClient                     : Authorization: Bearer eyJhbGciOiJIUzI1NiJ9.ewogICJqdGkiOiAiM2YyOTk4MjgtOGM3Mi00MGViLTllZWUtMzk2ZjI5MWJiMmJlIiwKICAiZXhwIjo
 
 
 
 
Environment:
DevTest 10.3
Cause:
All  Invoke calls are still trying to connect to the default port…
 --> GET ABC-15-131-117:1505/lisa-virtualize-invoke/api/v2/vses
 : <-- HTTP FAILED: java.net.ConnectException: Failed to connect to ABC-15-131-117:1505/
Resolution:
Please open a ticket with CA Support and refer to DE359593, We have a patch for this issue