I am not sure this is a Windows issue: Windows didn't care about the case
wrt to the folder name. The only one doing this difference was the Java code
on top of it that was making strict comparison (IMHO)
Cheers,
Sacha
> -----Message d'origine-----
> De : [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]De la part de
> Jonathan.O'[EMAIL PROTECTED]
> Envoye : lundi, 7 octobre 2002 11:39
> A : [EMAIL PROTECTED]
> Objet : Re: [JBoss-user] Sporadic problem starting up, effects Jasper
> compilation of JSP pages - Solution
>
>
> Folks,
> I found the source of my problem. I was running on Windows 2000. The
> server deployment was in a directory called "Traxbahn". I was starting it
> using "run -c traxbahn"
> Note the difference in case between Traxbahn and traxbahn. Silly me
> assumed that because windows is case insensitive with file names, that
> JBoss running on top of Windows would also be case insensitive.
> Not so. It
> is only partially case insensitive. Personally, this is worse than fully
> case sensitive or fully case insensitive.
>
> Ciao,
> Jonathan O'Connor
> Ph: +353 1 872 3305
> Mob: +353 86 824 9736
> Fax: +353 1 873 3612
>
>
>
>
> Jonathan.O'[EMAIL PROTECTED]
> Sent by: [EMAIL PROTECTED]
> 04.10.2002 17:53
> Please respond to jboss-user
>
>
> To: [EMAIL PROTECTED]
> cc:
> Subject: [JBoss-user] Sporadic problem starting
> up, effects Jasper compilation of
> JSP pages
>
>
> Guys,
> Here's a strange thing:
> If I take JBoss 3.0.1 straight out of the box and do run -c default,
> everything works wonderfully, and I can go to the JMX console web page
> without any problems.
>
> However, if I take a copy of the server/default and copy it to
> server/traxbahn
> 1. I add two libraries jpos-1.4.0.jar and classes12.jar (nothing strange
> here) to server/traxbahn/lib
> 2. I replace server/traxbahn/conf/login-config.xml with my own one which
> does auto-logon to the DB. This is also standard. It works fine.
> 3. I add an oracle-service.xml to server/traxbahn/deploy which knows how
> to connect to our Oracle DB. This also works fine.
>
> Now I start the JBoss server. I have seen what follows happen under 3.0.0
> and 3.0.1. After a while I get the following messages on the console:
>
> 17:24:07,413 INFO [jbossweb] Registered
> jboss.web:Jetty=0,JBossWebApplicationContext=0,context=/jmx-console
> 17:24:07,503 INFO [jbossweb] Checking Resource aliases
> 17:24:07,714 WARN [JBossWebApplicationContext#/jmx-console] bad
> classpath
>
> entry:
> file:/H:/server/traxbahn/tmp/deploy/server/Traxbahn/deploy/mail-se
> rvice.xml/54.mail-service.xml
> 17:24:07,734 WARN [JBossWebApplicationContext#/jmx-console] bad
> classpath
>
> entry:
> file:/H:/server/traxbahn/tmp/deploy/server/Traxbahn/lib/mail.jar/1
> 5.mail.jar
> 17:24:07,754 WARN [JBossWebApplicationContext#/jmx-console] bad
> classpath
>
> entry:
> file:/H:/server/traxbahn/tmp/deploy/server/Traxbahn/lib/jbossmx.ja
> r/8.jbossmx.jar
> 17:24:07,784 WARN [JBossWebApplicationContext#/jmx-console] bad
> classpath
>
> entry:
> file:/H:/server/traxbahn/tmp/deploy/server/traxbahn/lib/scheduler-
> plugin.jar/62.scheduler-plugin.jar
> 17:24:07,804 WARN [JBossWebApplicationContext#/jmx-console] bad
> classpath
>
> entry:
> file:/H:/server/traxbahn/tmp/deploy/server/Traxbahn/deploy/jbosswe
> b.sar/org.apache.jasper.jar/43.org.apache.jasper.jar
> 17:24:07,824 WARN [JBossWebApplicationContext#/jmx-console] bad
> classpath
>
> entry:
> file:/H:/server/traxbahn/tmp/deploy/server/Traxbahn/deploy/jbosswe
> b.sar/org.mortbay.jetty.jar/42.org.mortbay.jetty.jar
> 17:24:07,844 WARN [JBossWebApplicationContext#/jmx-console] bad
> classpath
>
> entry:
> file:/H:/server/traxbahn/tmp/deploy/server/Traxbahn/deploy/jbosswe
> b.sar/org.mortbay.j2ee.jar/40.org.mortbay.j2ee.jar
> 17:24:07,864 WARN [JBossWebApplicationContext#/jmx-console] bad
> classpath
>
> entry:
> file:/H:/server/traxbahn/tmp/deploy/server/Traxbahn/lib/process-pl
> ugin.jar/31.process-plugin.jar
> 17:24:07,884 WARN [JBossWebApplicationContext#/jmx-console] bad
> classpath
>
> entry:
> file:/H:/server/traxbahn/tmp/deploy/server/Traxbahn/lib/jboss.jar/
> 12.jboss.jar
> 17:24:07,904 WARN [JBossWebApplicationContext#/jmx-console] bad
> classpath
>
> entry:
> file:/H:/server/traxbahn/tmp/deploy/server/Traxbahn/deploy/hsqldb-
> service.xml/49.hsqldb-service.xml
> 17:24:07,934 WARN [JBossWebApplicationContext#/jmx-console] bad
> classpath
>
> entry:
> file:/H:/server/traxbahn/tmp/deploy/server/Traxbahn/deploy/jboss-x
> a.rar/66.jboss-xa.rar-contents/ra-xa-libs.jar
> 17:24:07,954 WARN [JBossWebApplicationContext#/jmx-console] bad
> classpath
>
> entry:
> file:/H:/server/traxbahn/tmp/deploy/server/Traxbahn/lib/xalan.jar/
> 24.xalan.jar
> 17:24:07,974 WARN [JBossWebApplicationContext#/jmx-console] bad
> classpath
>
> entry:
> file:/H:/server/traxbahn/tmp/deploy/server/Traxbahn/lib/mail-plugi
> n.jar/32.mail-plugin.jar
> 17:24:07,994 WARN [JBossWebApplicationContext#/jmx-console] bad
> classpath
>
> entry:
> file:/H:/server/traxbahn/tmp/deploy/server/Traxbahn/deploy/jca-ser
> vice.xml/52.jca-service.xml
> 17:24:08,014 WARN [JBossWebApplicationContext#/jmx-console] bad
> classpath
>
> entry:
> file:/H:/server/traxbahn/tmp/deploy/server/Traxbahn/lib/scheduler-
> plugin-example.jar/23.scheduler-plugin-example.jar
> 17:24:08,034 WARN [JBossWebApplicationContext#/jmx-console] bad
> classpath
>
> entry:
> file:/H:/server/traxbahn/tmp/deploy/server/Traxbahn/deploy/jbossmq
> -destinations-service.xml/50.jbossmq-destinations-service.xml
> 17:24:08,054 WARN [JBossWebApplicationContext#/jmx-console] bad
> classpath
>
> entry:
> file:/H:/server/traxbahn/tmp/deploy/server/Traxbahn/lib/scheduler-
> plugin.jar/27.scheduler-plugin.jar
> 17:24:08,074 WARN [JBossWebApplicationContext#/jmx-console] bad
> classpath
>
> entry:
> file:/H:/server/traxbahn/tmp/deploy/server/Traxbahn/lib/jboss-j2ee
> .jar/6.jboss-j2ee.jar
> 17:24:08,104 WARN [JBossWebApplicationContext#/jmx-console] bad
> classpath
>
> entry:
> file:/H:/server/traxbahn/tmp/deploy/server/Traxbahn/deploy/schedul
> er-service.xml/61.scheduler-service.xml
> 17:24:08,124 WARN [JBossWebApplicationContext#/jmx-console] bad
> classpath
>
> entry:
> file:/H:/server/traxbahn/tmp/deploy/server/Traxbahn/lib/autonumber
> -plugin.jar/16.autonumber-plugin.jar
>
> and so on for a while. Finally it deploys jetty.
>
> 17:24:14,433 INFO [jbossweb] Started
> WebApplicationContext[/jmx-console,file:/H:/server/Traxbahn/deploy
> /jmx-console.war/]
> 17:24:14,784 INFO [jbossweb] successfully deployed
> file:/H:/server/Traxbahn/deploy/jmx-console.war/ to /jmx-console
> 17:24:14,794 INFO [MainDeployer] Deployed package:
> file:/H:/server/Traxbahn/deploy/jmx-console.war/
> 17:24:14,814 INFO [URLDeploymentScanner] Started
> 17:24:14,824 INFO [MainDeployer] Deployed package:
> file:/H:/server/traxbahn/conf/jboss-service.xml
> 17:24:14,844 INFO [Server] JBoss (MX MicroKernel) [3.0.1
> Date:200208062340] Started in 0m:26s:648ms
>
> Now, if I open the console, or any other web application, it
> fails because
>
> of Jasper compilation problems:
>
> 17:26:59,761 WARN [jbossweb] WARNING: Exception for
> /jmx-console/org.apache.jasper.JasperException: Unable to compile class
> for JSPNote: sun.tools.javac.Main has been deprecated.
>
> C:\temp\Jetty__8080___jmx-console\index$jsp.java:3: Package javax.servlet
> not found in import.
> import javax.servlet.*;
> ^
>
> C:\temp\Jetty__8080___jmx-console\index$jsp.java:4: Package
> javax.servlet.http not found in import.
> import javax.servlet.http.*;
> ^
>
> C:\temp\Jetty__8080___jmx-console\index$jsp.java:5: Package
> javax.servlet.jsp not found in import.
> import javax.servlet.jsp.*;
> ^
>
> C:\temp\Jetty__8080___jmx-console\index$jsp.java:6: Package
> org.apache.jasper.runtime not found in import.
> import org.apache.jasper.runtime.*;
> ^
>
> C:\temp\Jetty__8080___jmx-console\index$jsp.java:9: Superclass
> org.apache.jsp.HttpJspBase of class org.apache.jsp.index$jsp not found.
> public class index$jsp extends HttpJspBase {
> ^
> 5 errors, 1 warning
>
> at org.apache.jasper.compiler.Compiler.compile(Compiler.java:289)
> at
> org.apache.jasper.servlet.JspServlet.loadJSP(JspServlet.java:548)
> at
> org.apache.jasper.servlet.JspServlet$JspServletWrapper.loadIfNeces
> sary(JspServlet.java:176)
> at
> org.apache.jasper.servlet.JspServlet$JspServletWrapper.service(Jsp
> Servlet.java:188)
> at
> org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:381)
> at
> org.apache.jasper.servlet.JspServlet.service(JspServlet.java:473)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
> at
> org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:344)
> at
> org.mortbay.jetty.servlet.WebApplicationHandler.dispatch(WebApplic
> ationHandler.java:313)
>
> Why is this happening? How can I stop it?
> Ciao,
> Jonathan O'Connor
> Ph: +353 1 872 3305
> Mob: +353 86 824 9736
> Fax: +353 1 873 3612
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> JBoss-user mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/jboss-user
>
>
>
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> JBoss-user mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/jboss-user
>
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user
