MinimServer Forum

Full Version: Java Exception Error after Update
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Pages: 1 2 3 4 5 6
Hi Simon,
Still running minimserver on Qnap NAS but I have started getting an error message:-

Code:
Exception while processing action request: java.lang.NullPointerException

and my minimwatch is red.

This has only started happening, as far as I can recall, since the update to MinimServer 0.8.4.5 update 110.

If I select rescan on browser Status page all appears well again but after a while it goes wrong and the minimwatch icon goes red and minimserver is no longer visible on my control point

Is there something I need to change or update to cure this?
Please post the full stack trace that follows this exception in the MinimServer log.
(08-12-2017 16:15)simoncn Wrote: [ -> ]Please post the full stack trace that follows this exception in the MinimServer log.
Hi Simon,
I do not know how to access the log on NAS. I have cleared the log on minimwatch and set Logging Level to Trace. Hopefully (or not!) I will catch it all next time it happens and post here. Meanwhile if there is another log sitting on the NAS please tell me what to do to access it.
Regards,
Budge
To access the log, select 'Show log' from the MiimWatch minim icon. It is unfortunate that you cleared this log because this would have provided the stack trace information.

It isn't necessary to have the logging level set to Trace to see the stack trace and it is preferable to leave the logging level at the default Info setting because setting it to Trace produces a lot of output that makes it harder to see important error messages when problems occur.
(08-12-2017 17:30)simoncn Wrote: [ -> ]To access the log, select 'Show log' from the MiimWatch minim icon. It is unfortunate that you cleared this log because this would have provided the stack trace information.

It isn't necessary to have the logging level set to Trace to see the stack trace and it is preferable to leave the logging level at the default Info setting because setting it to Trace produces a lot of output that makes it harder to see important error messages when problems occur.
Hi Simon,
I am sorry I misunderstood your message but the problem has repeated. You are right about having the log set to Trace producing a lot of output. 475Kb in fact. Do you want this or shall I reset to default and wait for the next time? If you do want the file, how should I get it to you?
The part that I need to see is just the stack trace immediately following the NullPointerException message (the following 25 lines or so). Please extract this information from the 475kb file and post it here.
(09-12-2017 15:56)simoncn Wrote: [ -> ]The part that I need to see is just the stack trace immediately following the NullPointerException message (the following 25 lines or so). Please extract this information from the 475kb file and post it here.

OK Simon, this is an extract:-

Code:
MinimServer: exception while processing action request: java.lang.NullPointerException
java.lang.NullPointerException
    at com.minimserver.Server$GroupItem.getKeyString(Server.java:13833)
    at com.minimserver.Server$ItemSearchContainer.search(Server.java:19897)
    at com.minimserver.Server$ContentDirectoryProvider.doSearch(Server.java:20829)
    at com.minimserver.Server$ContentDirectoryProvider.search(Server.java:20740)
    at org.openhome.net.device.providers.DvProviderUpnpOrgContentDirectory1$DoSearch.ac​tionInvoked(DvProviderUpnpOrgContentDirectory1.java:1049)
23:13:28.555 Thread-11: >>> EVENT >>> componentError: minimserver
23:13:28.555 Thread-11: ServerControl: componentError event for minimserver
23:13:28.555 Thread-11: Monitor: componentError event for minimserver in context context0
23:13:28.555 Thread-11: Monitor: setting property AllComponentStatus
23:13:28.556 Thread-11:  previous value: console,org.jminim.lib.ConsoleService,consoleContext,Running,minimserver,com.min​imserver.Server,context0,Running,stream,com.minimstreamer.Streamer,context0,Runn​ing,runtime,org.jminim.lib.RuntimeService,runtimeContext,Running,watch,com.minim​server.lib.WatchService,watchContext,Running,monitor,org.jminim.lib.MonitorServi​ce,monitorContext,Running,ohnet,org.jminim.lib.OhNetService,ohnetContext,Running​,http,org.jminim.lib.HTTPService,httpContext,Running,recorder,com.minimstreamer.​Streamer$RecorderService,recorderContext,Running
23:13:28.556 Thread-11:  new value: console,org.jminim.lib.ConsoleService,consoleContext,Running,minimserver,com.min​imserver.Server,context0,Error,stream,com.minimstreamer.Streamer,context0,Runnin​g,runtime,org.jminim.lib.RuntimeService,runtimeContext,Running,watch,com.minimse​rver.lib.WatchService,watchContext,Running,monitor,org.jminim.lib.MonitorService​,monitorContext,Running,ohnet,org.jminim.lib.OhNetService,ohnetContext,Running,h​ttp,org.jminim.lib.HTTPService,httpContext,Running,recorder,com.minimstreamer.St​reamer$RecorderService,recorderContext,Running
23:13:28.556 main: stopping context context0
23:13:28.556 main: >>> EVENT >>> contextStopping: context0
23:13:28.556 main: ServerControl: contextStopping event for context0
23:13:28.556 main: Monitor: contextStopping event for context0
23:13:28.557 main: Monitor: setting property AllContextStatus
23:13:28.557 main:  previous value: consoleContext,Running,context0,Running,runtimeContext,Running,watchContext,Runn​ing,monitorContext,Running,ohnetContext,Running,httpContext,Running,recorderCont​ext,Running
23:13:28.557 main:  new value: consoleContext,Running,context0,Stopping,runtimeContext,Running,watchContext,Run​ning,monitorContext,Running,ohnetContext,Running,httpContext,Running,recorderCon​text,Running
23:13:28.557 main: stopping component minimserver in context context0
23:13:28.557 main: >>> EVENT >>> componentStopping: minimserver
23:13:28.557 main: ServerControl: componentStopping event for minimserver
23:13:28.558 main: Monitor: componentStopping event for minimserver in context context0
23:13:28.558 main: Monitor: setting property AllComponentStatus
23:13:28.558 main:  previous value: console,org.jminim.lib.ConsoleService,consoleContext,Running,minimserver,com.min​imserver.Server,context0,Error,stream,com.minimstreamer.Streamer,context0,Runnin​g,runtime,org.jminim.lib.RuntimeService,runtimeContext,Running,watch,com.minimse​rver.lib.WatchService,watchContext,Running,monitor,org.jminim.lib.MonitorService​,monitorContext,Running,ohnet,org.jminim.lib.OhNetService,ohnetContext,Running,h​ttp,org.jminim.lib.HTTPService,httpContext,Running,recorder,com.minimstreamer.St​reamer$RecorderService,recorderContext,Running
23:13:28.558 main:  new value: console,org.jminim.lib.ConsoleService,consoleContext,Running,minimserver,com.min​imserver.Server,context0,Error,stream,com.minimstreamer.Streamer,context0,Runnin​g,runtime,org.jminim.lib.RuntimeService,runtimeContext,Running,watch,com.minimse​rver.lib.WatchService,watchContext,Running,monitor,org.jminim.lib.MonitorService​,monitorContext,Running,ohnet,org.jminim.lib.OhNetService,ohnetContext,Running,h​ttp,org.jminim.lib.HTTPService,httpContext,Running,recorder,com.minimstreamer.St​reamer$RecorderService,recorderContext,Running
23:13:28.558 main: stopping MinimServer
23:13:28.559 main: disposing cdProvider
23:13:28.559 main: cdProvider disposed
23:13:28.559 main: disposing cmProvider
23:13:28.559 main: cmProvider disposed
23:13:28.560 main: destroying device
23:13:28.561 Thread-8: Monitor action: GetErrorInfo
23:13:28.561 Thread-8:  version=1, adapter=192.168.169.130, uriPrefix=http://192.168.169.130:9791/1cd1d0b8-534a-4565-a133-0f0015702bbb/Upnp/resource/, clientEndpoint=192.168.169.133:59397
23:13:28.562 Thread-8: Monitor response: GetErrorInfo
23:13:28.562 Thread-8:  ErrorInfo=MinimServer: exception while processing action request: java.lang.NullPointerException
23:13:28.601 main: disposing device
23:13:28.602 main: OhNetService: disposing device
23:13:28.602 main: OhNetService: device disposed
23:13:28.602 main: device disposed
23:13:28.602 main: disposing http service
23:13:28.602 main: disposing HTTPContext
23:13:28.602 main: removing contextRoot minimserver
23:13:28.602 main: HTTPService: removing path minimserver
23:13:28.602 main: HTTPService: found handler for minimserver
23:13:28.602 main: removing contextRoot minimstreamer
23:13:28.602 main: HTTPService: removing path minimstreamer
23:13:28.602 main: HTTPService: found handler for minimstreamer
23:13:28.602 main: http service disposed
23:13:28.602 main: closing cacheData[0]
23:13:28.603 main: cacheData[0] closed
23:13:28.603 main: Streamer: stop
23:13:28.603 main: disposing HTTPContext

Hope this helps.
Thanks very much. This does help and the problem will be fixed in the next update (hopefully later today).
The fix is now available in MinimServer update 111. Thanks very much for your help in finding and fixing this problem.
(09-12-2017 22:56)simoncn Wrote: [ -> ]The fix is now available in MinimServer update 111. Thanks very much for your help in finding and fixing this problem.
Hi Simon,
Very glad to help and many thanks for your immediate response.

I did the update which seemed to run as normal but sadly now I only have a grey minimwatch icon.

Went to NAS to try and restart there but minimserver is not running. Next instructions awaited!!!
Regards,
Budgie
Pages: 1 2 3 4 5 6
Reference URL's