Universal Media Server | Forum

Anyone else ran into this issue ?

I've been running subsonic as music media server, though since that doesn't support other "targets" or renders, I had to start using UMS
to be able to play music via DLNA to my Pioneer wireless speaker.

Only problem I have, If I add a path to the music storage in UMS, then the server hangs 100% of the time anytime between 15-30mins.
Server screen's still there, though not accessible. Only possible to kill via taskmanager where it's hogging 1 cpu fully (25%)

Got a mix of mp3, flac and flac 24/96 files. All files stored locally. Number of files (the music side)is quite large though, approx 30000 or so seperated
into subdir per artist / album. Maybe worth enabling the verbose/debug and see if anything's catched while doing that.

With that huge number of files you have to be be patient. For the first time the UMS is storing all information in the database so untill it is finished you have to wait. To kill it in that time may make it worse. I recommend to go to the Navigation/Share setting page hit the Scan all shared folders button and you will see the progress of scanning and wait untill it is finished. Next time browsing should be fast.

Thanks.... might be it;

Manage to have it on trace and having in on for a couple of days.... in the end, had to kill it. Might very well be that it wasn't done with going through the files yes.
Could see the "java.lang.OutOfMemoryError: Java heap space".
Also, which looks interesting is another line;
org.h2.jdbc.JdbcSQLException: The database has been closed [90098-187]
at org.h2.message.DbException.getJdbcSQLException(DbException.java:345) ~[ums.jar:5.1.2]


This again, only occurs if/when adding my music library to UMS, without it, amost everything works I throw at it.

This is the main problem

emerson8 wrote: Could see the "java.lang.OutOfMemoryError: Java heap space".

The

org.h2.jdbc.JdbcSQLException: The database has been closed [90098-187]
at org.h2.message.DbException.getJdbcSQLException(DbException.java:345) ~[ums.jar:5.1.2]

is triggered by the java.lang.OutOfMemoryError.

EDIT: you can try to set more memory for Java to avoid the OutOfMemoryError because UMS stores in the cache (in memory) info about your 30000 audio files. That is why Java crashes.

Thanks for the pointer.

I'll give it a short with 1300mb to start with. Adding it to reg and the .bat file and see how that goes.

Well, memory tests to no avail unfortunately. Seems that my music collection simply isn't supported in those numbers....
Pity, UMS is my first choice as a server, but doesn't seem to be any way around above error. Might have to go 64bit to make larger Java memory assignments possible.