[Gary Gaggiani]

Got MyEclipse, JRUN4 installed and working OK. Made Oracle DB connection just fine. Debug under MyEclipse/JRUN4 is working fine, and used it to debug the startup code in my application.

Now I am trying to connect to my application using a browser. No luck. I get the “Welcome to JRUN” screen, and that is it. It does not matter what I have after the URL “localhost:8100/xxx”, nothing is found. My application should be under the directory “default/REDWeb/index.jsp”. I have tried every variation of that directory, but no luck.

[Riyad Kalla]

Have you tried:

http://localhost:8100/REDWeb

Don’t forget when specifying a port, you must start with http://

[Gary Gaggiani]

Yes. That is exactly what I tried. I left off the “http://” because it was obvious.

I have gotten a bit further: I found the “<context-root>” was wrong in the “jrun-web.xml” so I changed it. Now, I get the following errors:

02/04 14:30:24 error Translator.WrongCase/index.jspindex.jspIndex.jsp
javax.servlet.ServletException: Translator.WrongCase/index.jspindex.jspIndex.jsp
at jrun.jsp.Translator.checkServletPath(Translator.java:400)
at jrun.jsp.Translator.translate(Translator.java:245)
at jrun.jsp.Translator.translate(Translator.java:101)
at jrun.jsp.JSPEngine.translateJSP(JSPEngine.java:693)
at jrun.jsp.JSPServlet.translate(JSPServlet.java:125)
at jrun.jsp.JSPServlet.service(JSPServlet.java:113)
at jrun.servlet.ServletInvoker.invoke(ServletInvoker.java:91)
at jrun.servlet.JRunInvokerChain.invokeNext(JRunInvokerChain.java:42)
at jrun.servlet.JRunRequestDispatcher.invoke(JRunRequestDispatcher.java:252)
at jrun.servlet.ServletEngineService.dispatch(ServletEngineService.java:527)
at jrun.servlet.http.WebService.invokeRunnable(WebService.java:168)
at jrunx.scheduler.ThreadPool$ThreadThrottle.invokeRunnable(ThreadPool.java:451)
at jrunx.scheduler.WorkerThread.run(WorkerThread.java:66)

Any other suggestions?

[support-michael]

Hmmm!

I know our testcases for JRun are pretty basic and don’t involve use of jrun-web.xml since MyEclipse doesn’t create or modify that file directly (except maybe by XDoclet). Inspect the jrun-web.xml file for configuration details that are inconsistent with the physical deployment. For example when using exploded archive deployment your project will be deployed into JRun’s auto-deployment area under a folder named after the project. See if this is giving you problems.

[Gary Gaggiani]

Michael,

That was exactly the problem, in the <context-root> parameter.

Once I corrected that, the other problem above (wrong case) was that windows changed my index.jsp to Index.jsp. Something so simple….

Thanks,
Gary

[support-michael]

Great! Thanks for closing the loop with us.

[Author]

Posts