installing JBoss-3.0.4_Tomcat-4.1.12.zip Windows

[bstil]

Hi, I previously installed Tomcat 4.1.18 standalone Win 2000 and everything worked fine. Then I unistalled it, rebooted, and tried to get JBoss-3.0.4_Tomcat-4.1.12.zip up and running but no luck... :-(

(1) Do I start tomcat then jboss, or just jboss? If I start tomcat alone I can run the /examples servlets just fine.

(2) When I just start jboss, I get the following error for http://localhost:8080/
HTTP Status 500 - No Context configured to process this request

(3) Also, what Win2000 environmental variables do I need to set and where do they point?

HELP?! Thanks! :-)

[joelvogt]

(1) start jboss
(2) This is because there is no test page at that context. You have to dpeloy something first.
(3) Best not to set any

[vijayjboss]

JBoss3.0.x- Tomcat 4.0.x configuration

Any one can help me URGENT

Hi guys
MY OS:WINNT 4.0
i unzipped this jboss-3.0.x_tomcat-4.0.x.zip file to
jboss_tomcat directory.
then i set classpath to this as follows
JBOSS_DIST = d:\jboss_tomcat
PATH= %JBOSS_DIST %\bin

restarted the system after set the classpath.
now i started the JBossServer as follows

c:\run
the following msg shows while jboss server starting
19:23:23,227 ERROR [URLDeploymentScanner] Failed to deploy: org.jboss.deployment.scanner.URLDeploymentScanner$DeployedURL@21d
38f38{ url=file:/D:/jboss-3.0.4_tomcat-4.0.6/server/default/deploy/tomcat4-service.xml, deployedLastModified=0 }
org.jboss.deployment.DeploymentException: instantiating org.jboss.web.catalina.EmbeddedCatalinaServiceSX failed: java.lang.No
ClassDefFoundError: org/apache/catalina/Context; - nested throwable: (RuntimeErrorException: instantiating org.jboss.web.cata
lina.EmbeddedCatalinaServiceSX failed: java.lang.NoClassDefFoundError: org/apache/catalina/Context

finally
INFO [MainDeployer] Deployed package: file:/D:/jboss-3.0.2/server/default/deploy/jmx-console.war/
INFO [URLDeploymentScanner] Started
INFO [MainDeployer] Deployed package: file:/D:/jboss-3.0.2/server/default/conf/jboss-service.xml
INFO [Server] JBoss (MX MicroKernel) [3.0.2 Date:200208271339] Started in 0m:15s:62ms

now i used to run via browser as follows
http://localhost:8080/
Message displayed at browser

HTTP ERROR: 404 / Not Found
RequestURI=/
In JBoss server runnig prompt shows this message

[jbossweb] Registered jboss.web:Jetty=0,HttpContext=0,context=/
[jbossweb] Started HttpContext[/]

What i am asking is,how to configure after unzipped to 'jboss_tomcat' directory.
what is default port for JBOss Server?.
for my JBOSS-TOMCAT embedded version,where i have to start configuration(which files/where those files/folders)?

it is tedious process to configure and run this server.
most of the people who are loss of confidence to work with JBOss/tomcat due this.

with
vijay

[pohsoontan]

According to the documentation, it is normal to see an error page when accessing http://localhost:8080, as no custom application deployed.

According to documentation, to check whether JBoss is running, we should open a browser and point it to http://localhost:8082, which is the html based admin of JBoss. However, when i access that URL, a message saying page cannot be displayed is showing. At the same time, error log report as following:

03:41:24,216 INFO [Engine] StandardHost[localhost]: MAPPING configuration error
for request URI /

how to solve this?

[jpro2003]

I am getting the same error too. But what is the solution for getting rid of that.

anybody please help to configure jboss_tomcat.

thanks.

[giacomo]

I ran into problems using the IBM JVM (1.3.1). If you're not already, try using the SUN JVM (1.4.1). Once I switched, things worked fine. Also, I noticed someone else suggested using the following URL to test your installation: http://localhost:8080/jmx-console

I'm guessing that this replaces the previous URL of http://localhost:8082 which does not work for me either.

Can anyone confirm this?

[jpro2003]

that is working for me.. by giving this URL
http://localhost:8080/jmx-console i can see that my server is installed and i can see some of the jsp's responses in the console window.