Jetty Web Server (status update)

[Taddeusz]

Originally Posted by fresnoboy

Nope. Returns the list of possible parameters, etc...

Thx
Mike

Same here.

[stuckless]

Originally Posted by Taddeusz

Same here.

Ok... i added c=GetMediaFiles and I get the error on my site as well... My initial understanding was that you service wasn't available, but this is something different... looks like a new API maybe causing an endless loop in the serialization... Could take a little longer to troubleshoot... but they fact that I can reproduce it, gives hope

[stuckless]

In looking at the Airing api I see a new method GetPlayableAiring (added in 8.0) that is likely causing the endless loop... I'm at work and then I have an appointment later... so not sure if I can get this fixed today, or not... doesn't look like a big task.

[fresnoboy]

Thanks Stuckless! We really appreciate all the work!

Mike

[stuckless]

FYI... I updated the sagex-apis again this morning... i didn't have time to test if my change fixes the issue... so if someone wants to test, that would be great

[Taddeusz]

Originally Posted by stuckless

FYI... I updated the sagex-apis again this morning... i didn't have time to test if my change fixes the issue... so if someone wants to test, that would be great

I'm still getting the error. I'm just manually running the example on the main api page,

?c=GetMediaFiles&1=T

Here is the log file. BTW, I'm now running this off unRAID.

[stuckless]

Originally Posted by Taddeusz

I'm still getting the error. I'm just manually running the example on the main api page,

?c=GetMediaFiles&1=T

Here is the log file. BTW, I'm now running this off unRAID.

Thanks... i was hoping this would fix it... but as I said I didn't have time to test it Looks like I won't get to this now until the weekend (I have a small window on thursday evening... it might get done then).

[KarylFStein]

I will say that the Android mini client wouldn't play anything on 9.0.0.1, (I forget the error message and just switched to Phoenix Remote), but after loading the new version this morning it's working again. Not sure if that's related, but that's the only change I made between last night and this morning.

[stuckless]

Originally Posted by KarylFStein

I will say that the Android mini client wouldn't play anything on 9.0.0.1, (I forget the error message and just switched to Phoenix Remote), but after loading the new version this morning it's working again. Not sure if that's related, but that's the only change I made between last night and this morning.

The Android MiniClient doesn't use/depend on sagex apis, at all. Phoenix Remote does, and I can see where it would fail, when sagex isn't working (like is now).

[stuckless]

Originally Posted by Taddeusz

I'm still getting the error. I'm just manually running the example on the main api page,

?c=GetMediaFiles&1=T

Here is the log file. BTW, I'm now running this off unRAID.

I just tested that against my test machine (with the update sagex-api installed) and it worked ok. I must be missing something else

[Taddeusz]

Originally Posted by stuckless

I just tested that against my test machine (with the update sagex-api installed) and it worked ok. I must be missing something else

I'm not sure. It might be something in my wiz.bin. I remember it was working on unRAID prior to introducing my wiz.bin from Windows. But it was also working on Windows prior to the sagex upgrade.

[stuckless]

Originally Posted by Taddeusz

I'm not sure. It might be something in my wiz.bin. I remember it was working on unRAID prior to introducing my wiz.bin from Windows. But it was also working on Windows prior to the sagex upgrade.

It's likely something in the data. I'm going to put out a build with some debugging so that when it dies, I can see what field/method it was trying to process... that should help me narrow down where to look.

[Taddeusz]

Originally Posted by stuckless

It's likely something in the data. I'm going to put out a build with some debugging so that when it dies, I can see what field/method it was trying to process... that should help me narrow down where to look.

Feel free to send me test JAR's.

[stuckless]

Originally Posted by Taddeusz

Feel free to send me test JAR's.

This jar file has some extra debugging, feel free to update your jar with this and then test your /sagex/api url again and post the logs.. thx.

https://bintray.com/opensagetv/saget...ex-api/9.0.0.3

[Taddeusz]

Originally Posted by stuckless

This jar file has some extra debugging, feel free to update your jar with this and then test your /sagex/api url again and post the logs.. thx.

https://bintray.com/opensagetv/saget...ex-api/9.0.0.3

This version seems to have worked fine. I did all the sample queries and they all came back with data.

[stuckless]

Originally Posted by Taddeusz

This version seems to have worked fine. I did all the sample queries and they all came back with data.

The only thing different in this version is a "println" statement So either my previous plugin build didn't include the fix... or the previous plugin build didn't install correctly on your system.

Thanks for testing... at least I know that the problem was in fact the new 8.x API that was added.

I'll update the plugins repo tonight to a 9.0.0.4.

[Taddeusz]

Originally Posted by stuckless

The only thing different in this version is a "println" statement So either my previous plugin build didn't include the fix... or the previous plugin build didn't install correctly on your system.

Thanks for testing... at least I know that the problem was in fact the new 8.x API that was added.

I'll update the plugins repo tonight to a 9.0.0.4.

Yeah, it appears it didn't upgrade correctly for some reason. The manifest on the old JAR shows 9.0.0.0.

[fresnoboy]

I updated to 9.0.0.6 tonight, but am seeing the same errors.:

at sagex.remote.builder.SageAPIBuilder.build(SageAPIBuilder.java:57)
at sagex.remote.builder.SageAPIBuilder.buildObject(SageAPIBuilder.java:156)
at sagex.remote.builder.SageAPIBuilder.buildAiring(SageAPIBuilder.java:120)
at sagex.remote.builder.SageAPIBuilder.build(SageAPIBuilder.java:57)
at sagex.remote.builder.SageAPIBuilder.buildObject(SageAPIBuilder.java:156)
at sagex.remote.builder.SageAPIBuilder.buildAiring(SageAPIBuilder.java:120)
at sagex.remote.builder.SageAPIBuilder.build(SageAPIBuilder.java:57)
at sagex.remote.builder.SageAPIBuilder.buildObject(SageAPIBuilder.java:156)
at sagex.remote.builder.SageAPIBuilder.buildAiring(SageAPIBuilder.java:120)
at sagex.remote.builder.SageAPIBuilder.build(SageAPIBuilder.java:57)
at sagex.remote.builder.SageAPIBuilder.buildObject(SageAPIBuilder.java:156)
at sagex.remote.builder.SageAPIBuilder.buildAiring(SageAPIBuilder.java:120)
at sagex.remote.builder.SageAPIBuilder.build(SageAPIBuilder.java:57)
at sagex.remote.builder.SageAPIBuilder.buildObject(SageAPIBuilder.java:156)

The weird thing is just after I installed it, it pex seemed to get one show referenced that worked right, but nothing after that.

And When I did a manual query via a browser , I got differing responses at times.

Most of the time, it returns:

HTTP ERROR 500

Problem accessing /sagex/api. Reason:

Sage Servlet Failed: null
Powered by Jetty://


But rarely it returns:

{false}

The query I am doing is:

http://10.0.8.130:8080/sagex/api?c=p...s&encoder=json

[fresnoboy]

PS I deleted the plugin and reinstalled it, and then rebooted the system to restart sage (linux is so fast doing a reboot!).

Then when I did the same query before in chrome, I got this:

{"sagexVersion":"9.0.0","exception":"java.lang.RuntimeException: java.lang.ArrayIndexOutOfBoundsException: Array index out of range: 1.0\n\tat sagex.remote.api.ApiHandler.callService(ApiHandler.java:200)\n\tat sagex.remote.api.ApiHandler.handleRequest(ApiHandler.java:140)\n\tat sagex.remote.SagexServlet.doPost(SagexServlet.java:87)\n\tat sagex.remote.SagexServlet.doGet(SagexServlet.java:41)\n\tat javax.servlet.http.HttpServlet.service(HttpServlet.java:707)\n\tat javax.servlet.http.HttpServlet.service(HttpServlet.java:820)\n\tat org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:502)\n\tat org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:389)\n\tat org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)\n\tat org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:765)\n\tat org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:230)\n\tat org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114)\n\tat org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)\n\tat org.mortbay.jetty.handler.rewrite.RewriteHandler.handle(RewriteHandler.java:230)\n\tat org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)\n\tat org.mortbay.jetty.Server.handle(Server.java:326)\n\tat org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:534)\n\tat org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:864)\n\tat org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:539)\n\tat org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:212)\n\tat org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404)\n\tat org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:409)\n\tat org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:520)\nCaused by: java.lang.ArrayIndexOutOfBoundsException: Array index out of range: 1.0\n\tat jdk.internal.dynalink.beans.BeanLinker.rangeCheck(BeanLinker.java:369)\n\tat jdk.nashorn.internal.scripts.Script$Recompilation$4$1499A$\\^eval\\_.GetMediaFileForName(<eval>:79)\n\tat jdk.nashorn.internal.runtime.ScriptFunctionData.invoke(ScriptFunctionData.java:639)\n\tat jdk.nashorn.internal.runtime.ScriptFunction.invoke(ScriptFunction.java:494)\n\tat jdk.nashorn.internal.runtime.ScriptRuntime.apply(ScriptRuntime.java:393)\n\tat jdk.nashorn.api.scripting.ScriptObjectMirror.callMember(ScriptObjectMirror.java:199)\n\tat jdk.nashorn.api.scripting.NashornScriptEngine.invokeImpl(NashornScriptEngine.java:383)\n\tat jdk.nashorn.api.scripting.NashornScriptEngine.invokeFunction(NashornScriptEngine.java:190)\n\tat sagex.remote.api.ServiceFactory.callService(ServiceFactory.java:86)\n\tat sagex.remote.api.ApiHandler.callService(ApiHandler.java:198)\n\t... 22 more\n","error":"java.lang.ArrayIndexOutOfBoundsException: Array index out of range: 1.0"}

Followed by:

HTTP ERROR 500

Problem accessing /sagex/api. Reason:

Sage Servlet Failed: null
Powered by Jetty://


And then this again:

{"sagexVersion":"9.0.0","exception":"java.lang.RuntimeException: java.lang.ArrayIndexOutOfBoundsException: Array index out of range: 1.0\n\tat sagex.remote.api.ApiHandler.callService(ApiHandler.java:200)\n\tat sagex.remote.api.ApiHandler.handleRequest(ApiHandler.java:140)\n\tat sagex.remote.SagexServlet.doPost(SagexServlet.java:87)\n\tat sagex.remote.SagexServlet.doGet(SagexServlet.java:41)\n\tat javax.servlet.http.HttpServlet.service(HttpServlet.java:707)\n\tat javax.servlet.http.HttpServlet.service(HttpServlet.java:820)\n\tat org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:502)\n\tat org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:389)\n\tat org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)\n\tat org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:765)\n\tat org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:230)\n\tat org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114)\n\tat org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)\n\tat org.mortbay.jetty.handler.rewrite.RewriteHandler.handle(RewriteHandler.java:230)\n\tat org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)\n\tat org.mortbay.jetty.Server.handle(Server.java:326)\n\tat org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:534)\n\tat org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:864)\n\tat org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:539)\n\tat org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:212)\n\tat org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404)\n\tat org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:409)\n\tat org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:520)\nCaused by: java.lang.ArrayIndexOutOfBoundsException: Array index out of range: 1.0\n\tat jdk.internal.dynalink.beans.BeanLinker.rangeCheck(BeanLinker.java:369)\n\tat jdk.nashorn.internal.scripts.Script$Recompilation$4$1499A$\\^eval\\_.GetMediaFileForName(<eval>:79)\n\tat jdk.nashorn.internal.runtime.ScriptFunctionData.invoke(ScriptFunctionData.java:639)\n\tat jdk.nashorn.internal.runtime.ScriptFunction.invoke(ScriptFunction.java:494)\n\tat jdk.nashorn.internal.runtime.ScriptRuntime.apply(ScriptRuntime.java:393)\n\tat jdk.nashorn.api.scripting.ScriptObjectMirror.callMember(ScriptObjectMirror.java:199)\n\tat jdk.nashorn.api.scripting.NashornScriptEngine.invokeImpl(NashornScriptEngine.java:383)\n\tat jdk.nashorn.api.scripting.NashornScriptEngine.invokeFunction(NashornScriptEngine.java:190)\n\tat sagex.remote.api.ServiceFactory.callService(ServiceFactory.java:86)\n\tat sagex.remote.api.ApiHandler.callService(ApiHandler.java:198)\n\t... 22 more\n","error":"java.lang.ArrayIndexOutOfBoundsException: Array index out of range: 1.0"}


Very odd.

Thanks!
Mike

[JREkiwi]

Stuckless, running the 9.0.0.6 version and getting this error

java.lang.NoSuchMethodError: sagex.api.FavoriteAPI.GetFavoritePerson

when the Favorite Excluder plugin is initialized. It's only GetFavoritePerson that's having an issue. It's not complaing about GetFavoriteKeyword, GetFavoriteTitle or GetFavoriteCategory

John