Hi everyone, I have successfully installed JBoss 3.2.1/Tomcat 4.1.24. on windows 2000. I start Jboss from the command prompt by using the run.bat. The following is displayed after a series of messages. "14:59:12,500 INFO [Server] JBoss (MX MicroKernel) [3.2.1 (build: CVSTag=JBoss_3 _2_1 date=200305041533)] Started in 1m:6s:282ms" I have got an EAR file that is to be deployed. I created a folder, xyz.ear under the deploy folder and placed the ear file in that folder. On entering the url http://localhost:8080/xyz, I get a directory listing. On trying http://localhost:8080/jmx-console/, I get the following error "The server encountered an internal error () that prevented it from fulfilling this request. exception org.apache.jasper.JasperException: Unable to compile class for JSP An error occurred at line: -1 in the jsp file: null Generated servlet error: [javac] Compiling 1 source file [javac] javac: invalid flag: -sourcepath" Can someone help me resolve this? TIA Ravi
Andres Gonzalez
Ranch Hand
Joined: Nov 27, 2001
Posts: 1561
posted
0
Originally posted by Ravindran Ramiah: Hi everyone, ...I created a folder, xyz.ear under the deploy folder and placed the ear file in that folder.
I usually do not create any folder under my deploy directory in JBoss.. I just drop the ear file there and check what the log file tells me (whether deploys successfully or not). Do you get any error when deploying your EAR file?
I'm not going to be a Rock Star. I'm going to be a LEGEND! --Freddie Mercury
Ravindran Ramiah
Greenhorn
Joined: May 26, 2003
Posts: 2
posted
0
Hi Andres.. Following is the section of the log file that indicates a successful deployment. <--------------- 17:28:24,734 INFO [MainDeployer] Deployed package: file:/C:/JBoss/jboss-3.2.1_t omcat-4.1.24/server/default/deploy/xyz.war/ 17:28:24,734 INFO [MainDeployer] Starting deployment of package: file:/C:/JBoss /jboss-3.2.1_tomcat-4.1.24/server/default/deploy/jms/ 17:28:24,765 INFO [JARDeployer] nested deployment: file:/C:/JBoss/jboss-3.2.1_t omcat-4.1.24/server/default/deploy/jms/jbossmq-destinations-service.xml 17:28:24,765 INFO [JARDeployer] nested deployment: file:/C:/JBoss/jboss-3.2.1_t omcat-4.1.24/server/default/deploy/jms/jbossmq-httpil.sar/ 17:28:24,765 INFO [JARDeployer] nested deployment: file:/C:/JBoss/jboss-3.2.1_t omcat-4.1.24/server/default/deploy/jms/jbossmq-service.xml 17:28:24,765 INFO [JARDeployer] nested deployment: file:/C:/JBoss/jboss-3.2.1_t omcat-4.1.24/server/default/deploy/jms/jms-ds.xml 17:28:24,765 INFO [JARDeployer] nested deployment: file:/C:/JBoss/jboss-3.2.1_t omcat-4.1.24/server/default/deploy/jms/jms-ra.rar 17:28:24,828 INFO [SARDeployer] nested deployment: file:/C:/JBoss/jboss-3.2.1_t omcat-4.1.24/server/default/deploy/jms/jbossmq-httpil.sar/jbossmq-httpil.war/ 17:28:24,953 INFO [RARDeployer] nested deployment: file:/C:/JBoss/jboss-3.2.1_t omcat-4.1.24/server/default/tmp/deploy/server/default/deploy/jms/jms-ra.rar/39.j ms-ra.rar-contents/jms-ra.jar ---------> I tried removing the folder and dropping the ear file...the log file again indicates a successful deployment but the http://localhost:8080/xyz displays the directory listing. Would you like me to provide any other input? TIA Ravi
Darryl A. J. Staflund
Ranch Hand
Joined: Oct 06, 2002
Posts: 303
posted
0
Hi Ravindran, I get this error too -- but only with JBoss 3.2.1 -- and it is accompanied with a lot of socket errors as well. My only fix is to downgrade to 3.2.0 or to rebuild my test database and then restart JBoss. Normally I'd think there was a coding error on my part except that I haven't coded database stuff in my current app for a month now and the problem only started occurring with 3.2.1. It will be interesting to see if this goes away with 3.2.2. Darryl
Andres Gonzalez
Ranch Hand
Joined: Nov 27, 2001
Posts: 1561
posted
0
what exactly is xyz? From your first post I assumed is your ear file name itself.. hmm.. If that's the case you do not access your application that way. you usually have a context in which your application will be running..so it'll be something like: http://localhost:8080/myContext/index.jsp for example...
I used Jboss 3.0.x... hope this helps
I agree. Here's the link: http://ej-technologies/jprofiler - if it wasn't for jprofiler, we would need to
run our stuff on 16 servers instead of 3.