This is a migrated thread and some comments may be shown as answers.

JustMock and port conflict with Azure Storage Emulator

4 Answers 226 Views
General Discussions
This is a migrated thread and some comments may be shown as answers.
Mark
Top achievements
Rank 1
Mark asked on 11 Aug 2020, 03:30 PM

Both Azure Storage Emulator and JustMock use port 10001 and 10002 as default ports.

Is it possible to change the ports JustMock uses?

4 Answers, 1 is accepted

Sort by
0
Mihail
Telerik team
answered on 13 Aug 2020, 12:20 PM

Hi Mark,

The ports are used by the new DebugWindow feature of JustMock. There is a config file that you could alter.

Go to the JustMock installation folder, typically this is the path: "C:\Program Files (x86)\Progress\Telerik JustMock" and in the "Library\DebugWindow" you will find a file named "Telerik.JustMock.DebugWindow.Service.Host.exe.config". Open the file with a text editor and change the required ports.

An alternative approach is to disable the feature by setting a value of 0 to the registry DebugWindowEnabled under "Computer\HKEY_CURRENT_USER\Software\Telerik\JustMock"

I hope this information is helpful.

Regards,
Mihail
Progress Telerik

0
Mark
Top achievements
Rank 1
answered on 13 Aug 2020, 01:15 PM

I tried editing the Telerik.JustMock.DebugWindow.Service.Host.exe.config file.

I replaced the 10001 and 10002 port numbers with 10005 and 10006.

The port conflict still occurs.

When inspecting the process in SysInternals Process Explorer; it seems the Telerik.JustMock.DebugWindow.Service.Host.exe process has some startup parameters (--services TraceEventsPublishingService:10001;TraceEventsSubscriptionService:10002;MockRepositoryPublishingService:10003;MockRepositorySubscriptionService:10004).

Is it possible to change these startup parameters?

0
Mihail
Telerik team
answered on 13 Aug 2020, 02:39 PM

Hi Mark,

I managed to reproduce the issue and I have opened a new bug report in our feedback portal. You could subscribe to the item to receive status changes. We will update the item once we start working on it.

As a workaround, until we fix the issue, you could disable the feature. You can do that by setting a value of 0 to the registry DebugWindowEnabled under "Computer\HKEY_CURRENT_USER\Software\Telerik\JustMock" and restart Visual Studio. This way the DebugWindow host process won't be started.

Please excuse us for the caused inconvenience.

Regards,
Mihail
Progress Telerik

0
Mark
Top achievements
Rank 1
answered on 13 Aug 2020, 02:44 PM

Hi Mihail,

thanks a lot for your effort.

I will disable the feature untill the bug is fixed.

 

Regards, Mark

Tags
General Discussions
Asked by
Mark
Top achievements
Rank 1
Answers by
Mihail
Telerik team
Mark
Top achievements
Rank 1
Share this question
or