Wanted: Developer for Web Interface Mobile

[lovingHDTV]

Originally Posted by jreichen

Hmmm.... The files look good. I'm logging off soon, but I'll try them on my machine tomorrow. One other thing, did you make any changes to SAGE_HOME/jetty/etc/realm.properties?

No it is the same. I did wonder about this file as I read that you needed the line:

user: password,user

and what I have in mine is:

sage: frey,user

at one time I did add

user: password,user

but that did not make any difference so I commented it out and returned the original.

thanks,

[jreichen]

Originally Posted by lovingHDTV

No it is the same. I did wonder about this file as I read that you needed the line:

user: password,user

and what I have in mine is:

sage: frey,user

at one time I did add

user: password,user

but that did not make any difference so I commented it out and returned the original.

thanks,

I updated post #17 to hopefully eliminate any confusion about that..

[jreichen]

Add the following to JettyStarter.properties and restart Sage.

DEBUG=true

Try to access a page (it will still fail), then post the sagetv_0.txt here.

[lovingHDTV]

Originally Posted by jreichen

Add the following to JettyStarter.properties and restart Sage.

DEBUG=true

Try to access a page (it will still fail), then post the sagetv_0.txt here.

I see the DEBUG=true show up in the log file, but thats it. I attached it

[jreichen]

Originally Posted by lovingHDTV

I see the DEBUG=true show up in the log file, but thats it. I attached it

That's weird. My log has a lot of messages from Jetty about its startup and configuration.

I also tried your config files and it started up normally.

If I remove the webapp's files from jetty/contexts and jetty/webapps I get a 404 error, so that's not it either.

You could try Rick's workaround for the jetty.configfiles setting in post #15, but as far as I know it was fixed and nobody else has reported it since then.

What do you get when you go to http://server:8088/ ?

And lastly, could this be caused something in Windows, maybe Windows firewall?

[bcjenkins]

Don't know if it matters, my jetty launches after nielm's web server. You could also try specifying the full path to the jetty files yourself. The paths look weird. One has quotes, the other does not.

I run in linux though, so I don't know what it should look like on windows.

B

[lovingHDTV]

Originally Posted by jreichen

That's weird. My log has a lot of messages from Jetty about its startup and configuration.

I also tried your config files and it started up normally.

If I remove the webapp's files from jetty/contexts and jetty/webapps I get a 404 error, so that's not it either.

You could try Rick's workaround for the jetty.configfiles setting in post #15, but as far as I know it was fixed and nobody else has reported it since then.

What do you get when you go to http://server:8088/ ?

And lastly, could this be caused something in Windows, maybe Windows firewall?

We might be getting somewhere. If I go to htt://server:8088/ I get:

Error 404 - Not Found.
No context on this server matched or handled this request.
Contexts known to this server are:
/sage ---> org.mortbay.jetty.webapp.WebAppConte...SageWebApp.war!/}
/SageWebApp ---> org.mortbay.jetty.webapp.WebAppContext@164b55b{/SageWebApp,file:/C:/Program%20Files/SageTV/SageTV/jetty/webapps/SageWebApp/}

If I click on the first link, then one that ends with SageWebApp.war!. I get the 503 error.

If I click on the second link I can traverse through the directory structure and find the m/menu.jsp file. Clicking on that brings up a broken looking SageTV webpage.

dave

[jreichen]

The /SageWebApp context should not be there. Delete the C:\Program Files\SageTV\SageTV\jetty\webapps\SageWebApp folder and 'touch' jetty/contexts/sagewebapp.xml to get Jetty to reload the context. Wait a few seconds then go to the browser and see if it works.

[lovingHDTV]

This is odd.

I could not delete the folder when sage was running because a process was using one of the files. So I stopped sage, and deleted it.

When I restart Sage this directory gets created again when Jetty starts.

So I stopped sage deleted, and restarted to the same results.

[jreichen]

Jetty extracts the war file to that directory and uses it as a working copy.

It's strange that there are two contexts listed at http://server:8088/. How many files are in your jetty/contexts directory?

[lovingHDTV]

there is one:

sagewebapp.xml

[jreichen]

Here's a new sagewebapp.xml. I changed the context root to sagetest and the temp dir to SageWebAppTest. Overwrite (or backup to another folder) the existing file in jetty/contexts. Then try http://server:8088/ and http://server:8088/sagetest/m/menu.jsp

[lovingHDTV]

Originally Posted by jreichen

Here's a new sagewebapp.xml. I changed the context root to sagetest and the temp dir to SageWebAppTest. Overwrite (or backup to another folder) the existing file in jetty/contexts. Then try http://server:8088/ and http://server:8088/sagetest/m/menu.jsp

Here is the response:

HTTP ERROR: 503
SERVICE_UNAVAILABLE
RequestURI=/sagetest/m/menu.jsp

Powered by jetty://

I see a new SageWebAppTest area under webapps.

[jreichen]

I reinstalled it on my server and was able to reproduce your problem. Turns out I was missing the JARs from nielm's webserver. Once I copied them to the JARs folder the mobile version worked.

- Do you have his webserver installed?

- Does your sagetv_0.txt file have any exceptions in it? I had a lot of messages about missing servlets.

[lovingHDTV]

For me nielm's webserver is working fine, but they are not in the jetty/lib area, but in the sagetv/jars directory. The same place as the jetty libraries you asked me to check.

Looks like I'm running version 2.11

[jreichen]

The old version might be the problem. It may not have all the servlets the mobile web server depends on. You could upgrade nielm's web server or just get the latest jars and put them in jetty/lib. Sage itself doesn't know anything about the jars in there.

[lovingHDTV]

boy do I feel dumb. Let's add the requirement that your running version 2.22 of the nielm webserver

So I installed the new version and retried the mobile server and got a user/password request! Yea!!!

I put in the user/passord and hit the stupid Error 404 args!!

HTTP ERROR: 404
NOT_FOUND
RequestURI=/sage/m/menu.jsp

Powered by Jetty://


This thing just wont go away, but I guess being authenticated is better?

[jreichen]

Finally! I never thought of it having problems with an older version of nielm's web server. Hopefully I can get rid of those dependencies. Brent, could you update your instructions?

I think your problem now is that I gave you that other sagewebapp.xml to try out. If you're using that, the url is http://server:8088/sagetest/m/menu.jsp.

[lovingHDTV]

YEAH!!!

I deleted the "test" build, remove the debug from the properties file and restarted. Initially it did not work, but now it is. Maybe it took a little while to get up and running.

But I can now see it and it works on my Razr


Thanks so much to all of you for helping me out.

[btrcp2000]

I too am up and running on almost all devices, except for my wife's cellphone, which is a wap-running (polaris browser?) lx260 LG Rumor. I was able to connect one time, and got a memory error after it had displayed most of the page. The next time, I unchecked "show images". Since then, I get Internal Server 500 errors after i log in. I'm thikning it may be a proxy thing at sprint? My Mogul logs in just fine, both on my local wifi and from sprint's network.

Any ideas?