Java error on restart

[WigglyWoo]

Hello,

I've been using MinimServer with a Melco N1ZS40 for quite a while; after turning the Melco off and back on again today, I'm now getting this error message from MinimServer:

Media server status for MinimServer[N1ZS40]: Error

Unexpected exception java.lang.StringIndexOutOfBoundsException: begin -1, end 5, length 5

Any ideas? I've tried turning the Melco off, then on again, and also initiating a Restart in MinimServer scan, but still getting the same error. The Melco seems to be fine.

More info on the build in use:
MinimWatch 2.2 update 119
Java™ SE Runtime Environment (build 20.0.1+9-29)
Java HotSpot™ 64-Bit Server VM (build 20.0.1+9-29, mixed mode, sharing)
Java runtime options: -Dfile.encoding=UTF-8

Thanks

[simoncn]

A fix for this has been released in MinimServer update 262. This update should install automatically when you power the Melco off and on with MinimServer enabled. Alternatively, you can disable MinimServer from the Melco front panel and then enable it again.

[WigglyWoo]

Hi Simon, many thanks for the super-fast response as always... I've upgraded MinimServer to 262 but still getting the same error.

MinimServer 2.2 update 262, Copyright © 2012-2025 Simon Nash. All rights reserved.
Media server status for MinimServer[N1ZS40]: Error
Unexpected exception java.lang.StringIndexOutOfBoundsException: begin -1, end 5, length 5

Is this a metadata issue, or system? I've got a few of these errors when rescanning:
Error: incorrect STREAMINFO block length at offset 42 in file Pink Floyd/Meddle HD [HFC]/01 - One Of These Days.flac (length 116636430)

Thanks

[simoncn]

Please post the full stack trace for this StringIndexOutOfBoundsException error. You can find this in the MinimServer log.

The STREAMINFO message indicates corrupt tagging in the referenced file. Please try editing the file with a tag editor to make a small change, then save the change and rescan. This might fix the corruption.

[WigglyWoo]

(11-09-2025 20:53)simoncn Wrote:  Please post the full stack trace for this StringIndexOutOfBoundsException error. You can find this in the MinimServer log.

Thanks Simon, see below:

21:06:48.009 AWT-EventQueue-0: TrayView: restart action
21:06:48.013 AWT-EventQueue-0: TrayView: restart selected

*** (simoncn) deleted redundant data from this post to save space ***

21:10:23.457 AWT-EventQueue-0: ComponentClassLoader: using parent class loader for class java.awt.event.WindowEvent

[simoncn]

There is no stack trace or StringIndexOutOfBoundsException message in your post. Please don't attempt to post the complete log. Just post the StringIndexOutOfBoundsException message and the stack trace that immediately follows it.

[WigglyWoo]

(11-09-2025 21:32)simoncn Wrote:  There is no stack trace or StringIndexOutOfBoundsException message in your post. Please don't attempt to post the complete log. Just post the StringIndexOutOfBoundsException message and the stack trace that immediately follows it.

OK, does this help:


java.lang.StringIndexOutOfBoundsException: begin -1, end 5, length 5
at java.base/java.lang.String.checkBoundsBeginEnd(String.java:3756)
at java.base/java.lang.String.substring(String.java:1902)
at java.base/java.lang.String.substring(String.java:1875)
at com.minimserver.Server$Directory.postVisit(Server.java:18601)
at com.minimserver.Server$Visitor.postVisitDirectory(Server.java:18858)
at com.minimserver.Server$Visitor.postVisitDirectory(Server.java:18723)
at java.base/java.nio.file.Files.walkFileTree(Files.java:2822)
at java.base/java.nio.file.Files.walkFileTree(Files.java:2876)
at com.minimserver.Server.readFiles(Server.java:9276)
at com.minimserver.Server.doStart(Server.java:3952)
at com.minimserver.Server.start(Server.java:1405)
at org.jminim.core.ContextImpl.startComponent(ContextImpl.java:215)
at org.jminim.core.ContextImpl.start(ContextImpl.java:140)
at org.jminim.core.RuntimeImpl.run(RuntimeImpl.java:2928)
at org.jminim.core.LauncherImpl.run(LauncherImpl.java:1327)
at org.jminim.core.LauncherImpl.launch(LauncherImpl.java:126)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.ja​va:62)
at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccesso​rImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:564)
at org.jminim.mlaunch.MinimLaunch.doLaunch(MinimLaunch.java:525)
at org.jminim.mlaunch.MinimLaunch.launch(MinimLaunch.java:150)
at org.jminim.mlaunch.MinimLaunch.launch(MinimLaunch.java:90)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.ja​va:62)
at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccesso​rImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:564)
at org.jminim.launch.Launcher.launch(Launcher.java:88)
at com.minimserver.launch.LaunchServer.main(LaunchServer.java:38)
21:38:10.120 main: exception while starting component minimserver in context context0
21:38:10.121 main: >>> EVENT >>> componentError: minimserver
21:38:10.121 main: ServerControl: componentError event for minimserver

*** (simoncn) deleted redundant data from this post to save space ***

[simoncn]

Thanks for posting the stack trace. From this I have found the problem and fixed it in MinimServer update 263, now available.

[WigglyWoo]

Fantastic, that fixed it. As always Simon, I'm so impressed and grateful for your level of support.

Many thanks!