Java Exception

[gnomus]

Over the last few weeks - since upgrading to v2.1 - I've noticed that MinimServer will stop running on my QNAP NAS. The system tray icon is red and it reports an 'Exception while processing action request: java.util.ConcurrentModificationException' message.

The NAS is a QNAP HS-210 running the latest firmware (4.3.3.1945).

In 'Show Log', I see the following:

MinimServer: exception while processing action request: java.util.ConcurrentModificationException
java.util.ConcurrentModificationException
at java.util.ArrayList.sort(ArrayList.java:1462)
at java.util.Collections.sort(Collections.java:175)
at com.minimserver.Server$ValueContainer.sortFilters(Server.java:27365)
at com.minimserver.Server$ValueContainer.doPopulate(Server.java:27357)
at com.minimserver.Server$ValueContainer.populate(Server.java:27289)
at com.minimserver.Server.populateContainer(Server.java:11536)
at com.minimserver.Server.getContainer(Server.java:11461)
at com.minimserver.Server.populateContainer(Server.java:11535)
at com.minimserver.Server.getContainer(Server.java:11461)
at com.minimserver.Server.populateContainer(Server.java:11535)
at com.minimserver.Server.access$40600(Server.java:181)
at com.minimserver.Server$ContentDirectoryProvider.doBrowse(Server.java:31384)
at com.minimserver.Server$ContentDirectoryProvider.browse(Server.java:31328)
at org.openhome.net.device.providers.DvProviderUpnpOrgContentDirectory1$DoBrowse.ac​tionInvoked(DvProviderUpnpOrgContentDirectory1.java:978)

Any ideas what might be happening? Minimserver used to run without issue, but I've had this a handful of times now in the last few weeks.

Steve

[simoncn]

Thanks for letting me know about this. This error should produce a crash log file in the MinimServer/data shared folder on your QNAP. This file will have a filename like minimserver-crash-yyyymmdd-hhmmss.log. Please attach this file to a post (as a file attachment, not inline). Also, what is your setting for the alphaGroup property?

[gnomus]

(23-05-2022 16:17)simoncn Wrote:  Thanks for letting me know about this. This error should produce a crash log file in the MinimServer/data shared folder on your QNAP. This file will have a filename like minimserver-crash-yyyymmdd-hhmmss.log. Please attach this file to a post (as a file attachment, not inline). Also, what is your setting for the alphaGroup property?

Hi Simon and thanks again.

The crash logs were in my QNAP/Minimserver/ folder. I do have a 'data' sub-folder in the 'Minimserver' folder, but that isn't where I found the crash logs. I don't suppose that matters, but thought I should mention it, just in case. I've attached two logs from 22 May. There are a handful of other crash logs (10 in total) if you need to see them.

My alphaGroup property reads: Artist=100, albums=100, Composer=100, All Artists=100, Conductor=100, Orchestra=100

[simoncn]

Thanks very much for these logs. I am getting close but not quite there yet. I am hoping the answers to the following will enable me to pinpoint exactly what is going wrong.

Which control point were you using?

What were you doing when this happened?

[gnomus]

(24-05-2022 21:59)simoncn Wrote:  Thanks very much for these logs. I am getting close but not quite there yet. I am hoping the answers to the following will enable me to pinpoint exactly what is going wrong.

Which control point were you using?

What were you doing when this happened?

I use Linn Kazoo to operate my Akkurate.

As to question 2, it wasn't the case that it was working and then stopped working whilst I was playing music. I only discovered the crash when I tried to play something and found I had no music library.

[simoncn]

I have been looking into this problem in some detail. I now need to understand what sequence of events has caused this so that I can reproduce the problem here and test a fix. Please do the following:

1) From MinimWatch, select Show log
2) In the log window, change the logging level from Info to Debug
3) Close the log window
4) Run MinimServer until the problem occcurs
5) From the MinimWatch red icon, select Show log
6) In the log window, click Save as to save a log file
7) Zip the saved log file to save space and attach the zipped log file to a post here
8) In the log window, change the logging level back to Info

Thanks very much for your help with this.

[gnomus]

(30-05-2022 11:33)simoncn Wrote:  I have been looking into this problem in some detail. I now need to understand what sequence of events has caused this so that I can reproduce the problem here and test a fix. Please do the following:

1) From MinimWatch, select Show log
2) In the log window, change the logging level from Info to Debug
3) Close the log window
4) Run MinimServer until the problem occcurs
5) From the MinimWatch red icon, select Show log
6) In the log window, click Save as to save a log file
7) Zip the saved log file to save space and attach the zipped log file to a post here
8) In the log window, change the logging level back to Info

Thanks very much for your help with this.

Thank you Simon. I’m away at the moment and so it will be a week or so before I can do any of the above.

Steve

[simoncn]

No problem and thanks again.

[simoncn]

This problem is fixed now in MinimServer update 220.

[gnomus]

(21-12-2022 10:33)simoncn Wrote:  This problem is fixed now in MinimServer update 220.

Thanks Simon. For some reason the problem never recurred. Glad to hear it's fixed though.