MinimWatch Runtime Exception

[DavidHB]

On my main Windows 10 computer, both MinimServer and MinimWatch are installed; MinimServer relates to the local music library and MinimWatch to the 'normal use' library on my NAS.

Separately, both applications work normally. However, if I have both open together, and try to initiate a rescan in MinimServer (with the MinimServer log open), MinimWatch crashes. The error message is:

An unexpected exception has occurred:
org.jminim.RuntimeErrorException: Error 1 [Unknown] invoking GetProperty on remote runtime monitor

I attach the crash log

David


  minimwatch-crash-20160524-165039.log (Size: 7.74 KB / Downloads: 6)

[simoncn]

Were you doing the rescan on the Windows 10 instance of MinimServer or on some other instance of MinimServer (e.g., a NAS)?

After this crash dump was produced, was there still a MinimWatch icon in the system tray?

[DavidHB]

(24-05-2016 20:24)simoncn Wrote:  Were you doing the rescan on the Windows 10 instance of MinimServer or on some other instance of MinimServer (e.g., a NAS)?

The former, so related to the Music folder on my PC.

(24-05-2016 20:24)simoncn Wrote:  After this crash dump was produced, was there still a MinimWatch icon in the system tray?

Yes.

Hope that helps.

David

[simoncn]

(24-05-2016 21:09)DavidHB Wrote:  

(24-05-2016 20:24)simoncn Wrote:  Were you doing the rescan on the Windows 10 instance of MinimServer or on some other instance of MinimServer (e.g., a NAS)?

The former, so related to the Music folder on my PC.

This is very surprising because MinimWatch should not be monitoring a local instance of MinimServer running on the same PC. This is because a local instance of MinimServer would display a minim icon in the system tray and it would be redundant and confusing for MinimWatch to display an additional system tray icon with the same appearance and functionality.

(24-05-2016 21:09)DavidHB Wrote:  

(24-05-2016 20:24)simoncn Wrote:  After this crash dump was produced, was there still a MinimWatch icon in the system tray?

Yes.

This means that MinimWatch has not crashed (terminated), even though it has produced a crash dump file. The message means that MinimWatch has lost contact with MinimServer while MinimServer is restarting as part of the rescan. I will investigate how I can change the way this is reported by MinimWatch so that a crash dump file is not produced.

[DavidHB]

Sorry to be a bit late responding. I've been away from home for most of the last two days.

(24-05-2016 21:43)simoncn Wrote:  This is very surprising because MinimWatch should not be monitoring a local instance of MinimServer running on the same PC. This is because a local instance of MinimServer would display a minim icon in the system tray and it would be redundant and confusing for MinimWatch to display an additional system tray icon with the same appearance and functionality.

There is no evidence, other than the 'crash', that MinimWatch and MinimServer were monitoring anything other than their respective instances (of MinimServer on the NAS and the music library on the PC). I have run them together many times, and never previously had this result. To be quite sure, I have just run the sequence of steps again, and the 'crash' occurred again. Incidentally, the issue does not run both ways; initiating a rescan in MinimWatch simply produces a rescan on the NAS, and does not seem to affect MinimServer in any way.

(24-05-2016 20:24)simoncn Wrote:  This means that MinimWatch has not crashed (terminated), even though it has produced a crash dump file. The message means that MinimWatch has lost contact with MinimServer while MinimServer is restarting as part of the rescan. I will investigate how I can change the way this is reported by MinimWatch so that a crash dump file is not produced.

MinimWatch has not terminated, but has produced the runtime error dialog which invites me to relaunch MinimWatch (or exit). This dialog is modal, and no action is possible in MinimWatch until it is cleared. So it is also a matter of preventing this dialog from appearing. In any event, it does seem a bit odd that any action in MinimServer should affect the running instance of MinimWatch in any way. Please forgive me if this question is out of order, but have there been any recent code changes in MinimServer in which code has been brought in from MinimWatch, such that a reference to Minimwatch could have been left in accidentally?

David

[simoncn]

I have followed your instructions carefully but I have not been able to reproduce this problem.

There have not been any recent code changes in MinimServer in which code has been brought in from MinimWatch, such that a reference to Minimwatch could have been left in accidentally.

The problem occurs because MinimWatch receives a UPnP notification that the local instance of MinimServer has been restarted and MinimWatch then sends a request to the local instance of MinimServer to obtain a property value. For some reason, this request is not accepted by the local instance of MinimServer.

Please perform the following steps to help me diagnose the cause of the problem:

1) From the MinimWatch minim icon, select Options > Properties (watch)
2) In the Properties tab that is displayed, set the ohnet.debug property to All-Timer
3) From the MinimWatch minim icon, select Options > Show log (watch)
4) In the MinimWatch log window that is displayed, set the logging level to Debug
5) From the MinimWatch minim icon, select Exit
6) From the MinimWatch desktop launch icon, relaunch MinimWatch
7) Reproduce the problem by doing a rescan on the local instance of MinimServer
8) With MinimWatch still displaying the runtime error dialog, copy the minimwatch.log file from the C:\Users\your-user-name\AppData\Roaming\MinimWatch\data folder to another location. This folder is hidden by default in Windows Explorer and you can view it by typing the full path into the Explorer address bar.
9) Zip the minimwatch.log file and attach it to a post here

Many thanks for your help with this!

[DavidHB]

Thanks, Simon. Your support is, as always, much appreciated.

I attach the .zip file as requested

David


  minimwatch.zip (Size: 16.69 KB / Downloads: 2)

[simoncn]

(29-05-2016 00:13)DavidHB Wrote:  Thanks, Simon. Your support is, as always, much appreciated.

I attach the .zip file as requested

David

Thanks for this log. I have spent some time looking at it and I don't understand why the GetProperty request is failing.

Please can you produce a similar log for your Windows 10 MinimServer instance by doing the following:

1) From the MinimServer minim icon, select Properties
2) In the System tab, set the ohnet.debug property to All-Timer
3) From the MinimServer minim icon, select Exit
4) From the MinimServer desktop launch icon, relaunch MinimServer
5) Wait for MinimServer to finish scanning the library
6) From the MinimServer minim icon, select 'Show log'
7) In the MinimServer log window that is displayed, set the logging level to Debug
8) Close the log window
9) Reproduce the problem by doing a rescan on the local instance of MinimServer
10) With MinimWatch still displaying the runtime error dialog, copy the minimserver.log file from the C:\Users\your-user-name\AppData\Roaming\MinimServer\data folder to another location. This folder is hidden by default in Windows Explorer and you can view it by typing the full path into the Explorer address bar.
11) Zip the minimserver.log file and attach it to a post here. If it is too large to attach, please contact me by PM.

Many thanks for your help with this!

Edit: modified above instructions to make the log file smaller.

[DavidHB]

Thanks again Simon. New log attached as requested.

The procedure I followed was just to right-click on the MinimServer icon and select 'Properties' or whatever. There seems to be no 'Options' step. I hope that this is correct.

An alternative to the procedure you recommend (correctly) for finding the MinimServer log file is (1) to set the option to make hidden files and folders visible (in Windows 10, Control Panel>File Explorer Options>View tab) and (2) to have a user icon on the desktop. This is useful for users like me who access AppData fairly frequently.

Also (and we may have discussed this before) is there any way of making the MinimServer tray icon visually distinct (e.g. with a border) from the MinimWatch icon? In the course of this exercise, I found that I was confusing the two, though the tool tips help of course. I do accept that, where MinimWatch is monitoring more than one remote server, the icons would have to be the same.

David


  minimserver.zip (Size: 43.96 KB / Downloads: 1)

[simoncn]

(30-05-2016 09:35)DavidHB Wrote:  The procedure I followed was just to right-click on the MinimServer icon and select 'Properties' or whatever. There seems to be no 'Options' step. I hope that this is correct.

It is correct and the reference to Options (now corrected) was a copy-and-paste error from the instructions in my previous post.

Quote:Also (and we may have discussed this before) is there any way of making the MinimServer tray icon visually distinct (e.g. with a border) from the MinimWatch icon? In the course of this exercise, I found that I was confusing the two, though the tool tips help of course. I do accept that, where MinimWatch is monitoring more than one remote server, the icons would have to be the same.

I believe we have already had this discussion. The use of the same icon is intentional because in both cases the icon represents a unique running instance of MinimServer.