?
Solved

JBoss and Tomcat Configuration error "MAPPING configuration error for request URI /examples"

Posted on 2003-03-08
14
Medium Priority
?
7,960 Views
Last Modified: 2007-12-19
I'm trying out a new app server called JBoss which is bundled with Tomcat and all i'm trying to do is run the examples that come with Tomcat.
Here's exactly what i've done when configuring JBoss and Tomcat (if I didn't mention it below, you can assume I didn't do it):

I've installed JBoss on my Win2k machine at:
C:\jboss-3.0.6_tomcat-4.1.18

Set my environmental and system variables to:
CLASSPATH: C:\j2sdk1.4.0_02\lib\tools.jar;C:\jboss-3.0.6_tomcat-4.1.18\tomcat-4.1.x\common\lib\servlet.jar;

I also set up an environmental var as follows:
TOMCAT_HOME: C:\jboss-3.0.6_tomcat-4.1.18\tomcat-4.1.x

I started up JBoss just fine. No errors.

Then I tried to access the examples at:
http://localhost:8080/examples

That's when I get the following error:
MAPPING configuration error for request URI /examples

The Tomcat error page says:
HTTP Status 500 - No Context configured to process this request
----------------------------------------------------------
type Status report

message No Context configured to process this request

description The server encountered an internal error (No Context configured to process this request) that prevented it from fulfilling this request.


I hope someone can help me out and other people new to JBoss at the same time.

Thanks,
0
Comment
Question by:myuen
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 8
  • 6
14 Comments
 
LVL 14

Expert Comment

by:kennethxu
ID: 8095865
1st, check you default context: http://localhost:8080/
2nd, make sure this part is exist in tomcat-4.1.x/conf/server.xml and is not commented out:

        <Context path="/examples" docBase="examples" debug="0"
         ......
        </Context>
0
 
LVL 1

Author Comment

by:myuen
ID: 8095961
It's definitely there and not commented out.  I haven't done anything with the server.xml file but here it is.  Hopefully you can see something I don't:

*NOTE, this is the file that came with the distribution.  I haven't done anything with it:
<!-- Example Server Configuration File -->
<!-- Note that component elements are nested corresponding to their
     parent-child relationships with each other -->

<!-- A "Server" is a singleton element that represents the entire JVM,
     which may contain one or more "Service" instances.  The Server
     listens for a shutdown command on the indicated port.

     Note:  A "Server" is not itself a "Container", so you may not
     define subcomponents such as "Valves" or "Loggers" at this level.
 -->

<Server port="8005" shutdown="SHUTDOWN" debug="0">


  <!-- Comment these entries out to disable JMX MBeans support -->
  <!-- You may also configure custom components (e.g. Valves/Realms) by
       including your own mbean-descriptor file(s), and setting the
       "descriptors" attribute to point to a ';' seperated list of paths
       (in the ClassLoader sense) of files to add to the default list.
       e.g. descriptors="/com/myfirm/mypackage/mbean-descriptor.xml"
  -->
  <Listener className="org.apache.catalina.mbeans.ServerLifecycleListener"
            debug="0"/>
  <Listener className="org.apache.catalina.mbeans.GlobalResourcesLifecycleListener"
            debug="0"/>

  <!-- Global JNDI resources -->
  <GlobalNamingResources>

    <!-- Test entry for demonstration purposes -->
    <Environment name="simpleValue" type="java.lang.Integer" value="30"/>

    <!-- Editable user database that can also be used by
         UserDatabaseRealm to authenticate users -->
    <Resource name="UserDatabase" auth="Container"
              type="org.apache.catalina.UserDatabase"
       description="User database that can be updated and saved">
    </Resource>
    <ResourceParams name="UserDatabase">
      <parameter>
        <name>factory</name>
        <value>org.apache.catalina.users.MemoryUserDatabaseFactory</value>
      </parameter>
      <parameter>
        <name>pathname</name>
        <value>conf/tomcat-users.xml</value>
      </parameter>
    </ResourceParams>

  </GlobalNamingResources>

  <!-- A "Service" is a collection of one or more "Connectors" that share
       a single "Container" (and therefore the web applications visible
       within that Container).  Normally, that Container is an "Engine",
       but this is not required.

       Note:  A "Service" is not itself a "Container", so you may not
       define subcomponents such as "Valves" or "Loggers" at this level.
   -->

  <!-- Define the Tomcat Stand-Alone Service -->
  <Service name="Tomcat-Standalone">

    <!-- A "Connector" represents an endpoint by which requests are received
         and responses are returned.  Each Connector passes requests on to the
         associated "Container" (normally an Engine) for processing.

         By default, a non-SSL HTTP/1.1 Connector is established on port 8080.
         You can also enable an SSL HTTP/1.1 Connector on port 8443 by
         following the instructions below and uncommenting the second Connector
         entry.  SSL support requires the following steps (see the SSL Config
         HOWTO in the Tomcat 4.0 documentation bundle for more detailed
         instructions):
         * Download and install JSSE 1.0.2 or later, and put the JAR files
           into "$JAVA_HOME/jre/lib/ext".
         * Execute:
             %JAVA_HOME%\bin\keytool -genkey -alias tomcat -keyalg RSA (Windows)
             $JAVA_HOME/bin/keytool -genkey -alias tomcat -keyalg RSA  (Unix)
           with a password value of "changeit" for both the certificate and
           the keystore itself.

         By default, DNS lookups are enabled when a web application calls
         request.getRemoteHost().  This can have an adverse impact on
         performance, so you can disable it by setting the
         "enableLookups" attribute to "false".  When DNS lookups are disabled,
         request.getRemoteHost() will return the String version of the
         IP address of the remote client.
    -->

    <!-- Define a non-SSL Coyote HTTP/1.1 Connector on port 8080 -->
    <Connector className="org.apache.coyote.tomcat4.CoyoteConnector"
               port="8080" minProcessors="5" maxProcessors="75"
               enableLookups="true" redirectPort="8443"
               acceptCount="100" debug="0" connectionTimeout="20000"
               useURIValidationHack="false" disableUploadTimeout="true" />
    <!-- Note : To disable connection timeouts, set connectionTimeout value
     to -1 -->

    <!-- Define a SSL Coyote HTTP/1.1 Connector on port 8443 -->
    <!--
    <Connector className="org.apache.coyote.tomcat4.CoyoteConnector"
               port="8443" minProcessors="5" maxProcessors="75"
               enableLookups="true"
             acceptCount="100" debug="0" scheme="https" secure="true"
               useURIValidationHack="false" disableUploadTimeout="true">
      <Factory className="org.apache.coyote.tomcat4.CoyoteServerSocketFactory"
               clientAuth="false" protocol="TLS" />
    </Connector>
    -->

    <!-- Define a Coyote/JK2 AJP 1.3 Connector on port 8009 -->
    <Connector className="org.apache.coyote.tomcat4.CoyoteConnector"
               port="8009" minProcessors="5" maxProcessors="75"
               enableLookups="true" redirectPort="8443"
               acceptCount="10" debug="0" connectionTimeout="0"
               useURIValidationHack="false"
               protocolHandlerClassName="org.apache.jk.server.JkCoyoteHandler"/>

    <!-- Define an AJP 1.3 Connector on port 8009 -->
    <!--
    <Connector className="org.apache.ajp.tomcat4.Ajp13Connector"
               port="8009" minProcessors="5" maxProcessors="75"
               acceptCount="10" debug="0"/>
    -->

    <!-- Define a Proxied HTTP/1.1 Connector on port 8082 -->
    <!-- See proxy documentation for more information about using this. -->
    <!--
    <Connector className="org.apache.coyote.tomcat4.CoyoteConnector"
               port="8082" minProcessors="5" maxProcessors="75"
               enableLookups="true"
               acceptCount="100" debug="0" connectionTimeout="20000"
               proxyPort="80" useURIValidationHack="false"
               disableUploadTimeout="true" />
    -->

    <!-- Define a non-SSL legacy HTTP/1.1 Test Connector on port 8083 -->
    <!--
    <Connector className="org.apache.catalina.connector.http.HttpConnector"
               port="8083" minProcessors="5" maxProcessors="75"
               enableLookups="true" redirectPort="8443"
               acceptCount="10" debug="0" />
    -->

    <!-- Define a non-SSL HTTP/1.0 Test Connector on port 8084 -->
    <!--
    <Connector className="org.apache.catalina.connector.http10.HttpConnector"
               port="8084" minProcessors="5" maxProcessors="75"
               enableLookups="true" redirectPort="8443"
               acceptCount="10" debug="0" />
    -->

    <!-- An Engine represents the entry point (within Catalina) that processes
         every request.  The Engine implementation for Tomcat stand alone
         analyzes the HTTP headers included with the request, and passes them
         on to the appropriate Host (virtual host). -->

    <!-- You should set jvmRoute to support load-balancing via JK/JK2 ie :
    <Engine name="Standalone" defaultHost="localhost" debug="0" jmvRoute="jvm1">        
    -->
         
    <!-- Define the top level container in our container hierarchy -->
    <Engine name="Standalone" defaultHost="localhost" debug="0">

      <!-- The request dumper valve dumps useful debugging information about
           the request headers and cookies that were received, and the response
           headers and cookies that were sent, for all requests received by
           this instance of Tomcat.  If you care only about requests to a
           particular virtual host, or a particular application, nest this
           element inside the corresponding <Host> or <Context> entry instead.

           For a similar mechanism that is portable to all Servlet 2.3
           containers, check out the "RequestDumperFilter" Filter in the
           example application (the source for this filter may be found in
           "$CATALINA_HOME/webapps/examples/WEB-INF/classes/filters").

           Request dumping is disabled by default.  Uncomment the following
           element to enable it. -->
      <!--
      <Valve className="org.apache.catalina.valves.RequestDumperValve"/>
      -->

      <!-- Global logger unless overridden at lower levels -->
      <Logger className="org.apache.catalina.logger.FileLogger"
              prefix="catalina_log." suffix=".txt"
              timestamp="true"/>

      <!-- Because this Realm is here, an instance will be shared globally -->

      <!-- This Realm uses the UserDatabase configured in the global JNDI
           resources under the key "UserDatabase".  Any edits
           that are performed against this UserDatabase are immediately
           available for use by the Realm.  -->
      <Realm className="org.apache.catalina.realm.UserDatabaseRealm"
                 debug="0" resourceName="UserDatabase"/>

      <!-- Comment out the old realm but leave here for now in case we
           need to go back quickly -->
      <!--
      <Realm className="org.apache.catalina.realm.MemoryRealm" />
      -->

      <!-- Replace the above Realm with one of the following to get a Realm
           stored in a database and accessed via JDBC -->

      <!--
      <Realm  className="org.apache.catalina.realm.JDBCRealm" debug="99"
             driverName="org.gjt.mm.mysql.Driver"
          connectionURL="jdbc:mysql://localhost/authority"
         connectionName="test" connectionPassword="test"
              userTable="users" userNameCol="user_name" userCredCol="user_pass"
          userRoleTable="user_roles" roleNameCol="role_name" />
      -->

      <!--
      <Realm  className="org.apache.catalina.realm.JDBCRealm" debug="99"
             driverName="oracle.jdbc.driver.OracleDriver"
          connectionURL="jdbc:oracle:thin:@ntserver:1521:ORCL"
         connectionName="scott" connectionPassword="tiger"
              userTable="users" userNameCol="user_name" userCredCol="user_pass"
          userRoleTable="user_roles" roleNameCol="role_name" />
      -->

      <!--
      <Realm  className="org.apache.catalina.realm.JDBCRealm" debug="99"
             driverName="sun.jdbc.odbc.JdbcOdbcDriver"
          connectionURL="jdbc:odbc:CATALINA"
              userTable="users" userNameCol="user_name" userCredCol="user_pass"
          userRoleTable="user_roles" roleNameCol="role_name" />
      -->

      <!-- Define the default virtual host -->
      <Host name="localhost" debug="0" appBase="webapps"
       unpackWARs="true" autoDeploy="true">

        <!-- Normally, users must authenticate themselves to each web app
             individually.  Uncomment the following entry if you would like
             a user to be authenticated the first time they encounter a
             resource protected by a security constraint, and then have that
             user identity maintained across *all* web applications contained
             in this virtual host. -->
        <!--
        <Valve className="org.apache.catalina.authenticator.SingleSignOn"
                   debug="0"/>
        -->

        <!-- Access log processes all requests for this virtual host.  By
             default, log files are created in the "logs" directory relative to
             $CATALINA_HOME.  If you wish, you can specify a different
             directory with the "directory" attribute.  Specify either a relative
             (to $CATALINA_HOME) or absolute path to the desired directory.
        -->
        <!--
        <Valve className="org.apache.catalina.valves.AccessLogValve"
                 directory="logs"  prefix="localhost_access_log." suffix=".txt"
                 pattern="common" resolveHosts="false"/>
        -->

        <!-- Logger shared by all Contexts related to this virtual host.  By
             default (when using FileLogger), log files are created in the "logs"
             directory relative to $CATALINA_HOME.  If you wish, you can specify
             a different directory with the "directory" attribute.  Specify either a
             relative (to $CATALINA_HOME) or absolute path to the desired
             directory.-->
        <Logger className="org.apache.catalina.logger.FileLogger"
                 directory="logs"  prefix="localhost_log." suffix=".txt"
              timestamp="true"/>

        <!-- Define properties for each web application.  This is only needed
             if you want to set non-default properties, or have web application
             document roots in places other than the virtual host's appBase
             directory.  -->

        <!-- Tomcat Root Context -->
        <!--
          <Context path="" docBase="ROOT" debug="0"/>
        -->

        <!-- Tomcat Examples Context -->
        <Context path="/examples" docBase="examples" debug="0"
                 reloadable="true" crossContext="true">
          <Logger className="org.apache.catalina.logger.FileLogger"
                     prefix="localhost_examples_log." suffix=".txt"
                timestamp="true"/>
          <Ejb   name="ejb/EmplRecord" type="Entity"
                 home="com.wombat.empl.EmployeeRecordHome"
               remote="com.wombat.empl.EmployeeRecord"/>

          <!-- If you wanted the examples app to be able to edit the
               user database, you would uncomment the following entry.
               Of course, you would want to enable security on the
               application as well, so this is not done by default!
               The database object could be accessed like this:

               Context initCtx = new InitialContext();
               Context envCtx = (Context) initCtx.lookup("java:comp/env");
               UserDatabase database =
                    (UserDatabase) envCtx.lookup("userDatabase");
          -->
<!--
          <ResourceLink name="userDatabase" global="UserDatabase"
                        type="org.apache.catalina.UserDatabase"/>
-->


          <!-- PersistentManager: Uncomment the section below to test Persistent
                   Sessions.
                         
               saveOnRestart: If true, all active sessions will be saved
                 to the Store when Catalina is shutdown, regardless of
                 other settings. All Sessions found in the Store will be
                 loaded on startup. Sessions past their expiration are
                 ignored in both cases.
               maxActiveSessions: If 0 or greater, having too many active
                 sessions will result in some being swapped out. minIdleSwap
                 limits this. -1 or 0 means unlimited sessions are allowed.
                 If it is not possible to swap sessions new sessions will
                 be rejected.
                 This avoids thrashing when the site is highly active.
               minIdleSwap: Sessions must be idle for at least this long
                 (in seconds) before they will be swapped out due to
                 activity.
                 0 means sessions will almost always be swapped out after
                 use - this will be noticeably slow for your users.
               maxIdleSwap: Sessions will be swapped out if idle for this
                 long (in seconds). If minIdleSwap is higher, then it will
                 override this. This isn't exact: it is checked periodically.
                 -1 means sessions won't be swapped out for this reason,
                 although they may be swapped out for maxActiveSessions.
                 If set to >= 0, guarantees that all sessions found in the
                 Store will be loaded on startup.
               maxIdleBackup: Sessions will be backed up (saved to the Store,
                 but left in active memory) if idle for this long (in seconds),
                 and all sessions found in the Store will be loaded on startup.
                 If set to -1 sessions will not be backed up, 0 means they
                 should be backed up shortly after being used.

               To clear sessions from the Store, set maxActiveSessions, maxIdleSwap,
               and minIdleBackup all to -1, saveOnRestart to false, then restart
               Catalina.
          -->
              <!--
          <Manager className="org.apache.catalina.session.PersistentManager"
              debug="0"
              saveOnRestart="true"
              maxActiveSessions="-1"
              minIdleSwap="-1"
              maxIdleSwap="-1"
              maxIdleBackup="-1">
                <Store className="org.apache.catalina.session.FileStore"/>
          </Manager>
              -->
          <Environment name="maxExemptions" type="java.lang.Integer"
                      value="15"/>
          <Parameter name="context.param.name" value="context.param.value"
                     override="false"/>
          <Resource name="jdbc/EmployeeAppDb" auth="SERVLET"
                    type="javax.sql.DataSource"/>
          <ResourceParams name="jdbc/EmployeeAppDb">
            <parameter><name>username</name><value>sa</value></parameter>
            <parameter><name>password</name><value></value></parameter>
            <parameter><name>driverClassName</name>
              <value>org.hsql.jdbcDriver</value></parameter>
            <parameter><name>url</name>
              <value>jdbc:HypersonicSQL:database</value></parameter>
          </ResourceParams>
          <Resource name="mail/Session" auth="Container"
                    type="javax.mail.Session"/>
          <ResourceParams name="mail/Session">
            <parameter>
              <name>mail.smtp.host</name>
              <value>localhost</value>
            </parameter>
          </ResourceParams>
          <ResourceLink name="linkToGlobalResource"
                    global="simpleValue"
                    type="java.lang.Integer"/>
        </Context>

      </Host>

    </Engine>

  </Service>

  <!-- The MOD_WEBAPP connector is used to connect Apache 1.3 with Tomcat 4.0
       as its servlet container. Please read the README.txt file coming with
       the WebApp Module distribution on how to build it.
       (Or check out the "jakarta-tomcat-connectors/webapp" CVS repository)

       To configure the Apache side, you must ensure that you have the
       "ServerName" and "Port" directives defined in "httpd.conf".  Then,
       lines like these to the bottom of your "httpd.conf" file:

         LoadModule webapp_module libexec/mod_webapp.so
         WebAppConnection warpConnection warp localhost:8008
         WebAppDeploy examples warpConnection /examples/

       The next time you restart Apache (after restarting Tomcat, if needed)
       the connection will be established, and all applications you make
       visible via "WebAppDeploy" directives can be accessed through Apache.
  -->

  <!-- Define an Apache-Connector Service -->
<!--
  <Service name="Tomcat-Apache">

    <Connector className="org.apache.catalina.connector.warp.WarpConnector"
     port="8008" minProcessors="5" maxProcessors="75"
     enableLookups="true" appBase="webapps"
     acceptCount="10" debug="0"/>

    <Engine className="org.apache.catalina.connector.warp.WarpEngine"
     name="Apache" debug="0">

      <Logger className="org.apache.catalina.logger.FileLogger"
              prefix="apache_log." suffix=".txt"
              timestamp="true"/>

      <Realm className="org.apache.catalina.realm.MemoryRealm" />

    </Engine>

  </Service>
-->

</Server>


0
 
LVL 14

Expert Comment

by:kennethxu
ID: 8096022
hmmm, is there any error in your server log?
0
VIDEO: THE CONCERTO CLOUD FOR HEALTHCARE

Modern healthcare requires a modern cloud. View this brief video to understand how the Concerto Cloud for Healthcare can help your organization.

 
LVL 1

Author Comment

by:myuen
ID: 8096095
THis is what's in my examples server log
I don't see anything out of the ordinary:

2003-03-08 17:19:00 WebappLoader[/examples]: Deploying class repositories to work directory C:\jboss-3.0.6_tomcat-4.1.18\tomcat-4.1.x\work\Standalone\localhost\examples
2003-03-08 17:19:00 WebappLoader[/examples]: Deploy class files /WEB-INF/classes to C:\jboss-3.0.6_tomcat-4.1.18\tomcat-4.1.x\bin\..\webapps\examples\WEB-INF\classes
2003-03-08 17:19:00 WebappLoader[/examples]: Reloading checks are enabled for this Context
2003-03-08 17:19:01 ContextConfig[/examples]: Configured an authenticator for method FORM
2003-03-08 17:19:01 StandardManager[/examples]: Seeding random number generator class java.security.SecureRandom
2003-03-08 17:19:01 StandardManager[/examples]: Seeding of random number generator has been completed
2003-03-08 17:19:01 ContextListener: contextInitialized()
2003-03-08 17:19:01 SessionListener: contextInitialized()
2003-03-08 17:19:01 StandardWrapper[/examples:default]: Loading container servlet default
2003-03-08 17:19:01 StandardWrapper[/examples:invoker]: Loading container servlet invoker
2003-03-08 17:19:10 ContextListener: attributeReplaced('org.apache.catalina.WELCOME_FILES', '[Ljava.lang.String;@8d7ace')
2003-03-08 17:19:10 ContextListener: attributeReplaced('org.apache.catalina.WELCOME_FILES', '[Ljava.lang.String;@79953c')
2003-03-08 17:19:10 ContextListener: attributeReplaced('org.apache.catalina.WELCOME_FILES', '[Ljava.lang.String;@34ce4a')
2003-03-08 17:19:10 SessionListener: contextDestroyed()
2003-03-08 17:19:10 ContextListener: contextDestroyed()
0
 
LVL 14

Expert Comment

by:kennethxu
ID: 8096274
did you added something to example context? the logs says the context is destroyed 9 seconds after it is loaded., that's what in my log:
2003-03-08 21:21:06 WebappLoader[/examples]: Deploying class repositories to work directory E:\Develop\jboss-3.0.6_tomcat-4.1.18\tomcat-4.1.x\work\Standalone\localhost\examples
2003-03-08 21:21:06 WebappLoader[/examples]: Deploy class files /WEB-INF/classes to E:\Develop\jboss-3.0.6_tomcat-4.1.18\tomcat-4.1.x\bin\..\webapps\examples\WEB-INF\classes
2003-03-08 21:21:06 WebappLoader[/examples]: Reloading checks are enabled for this Context
2003-03-08 21:21:06 ContextConfig[/examples]: Configured an authenticator for method FORM
2003-03-08 21:21:06 StandardManager[/examples]: Seeding random number generator class java.security.SecureRandom
2003-03-08 21:21:07 StandardManager[/examples]: Seeding of random number generator has been completed
2003-03-08 21:21:07 ContextListener: contextInitialized()
2003-03-08 21:21:07 SessionListener: contextInitialized()
2003-03-08 21:21:07 StandardWrapper[/examples:default]: Loading container servlet default
2003-03-08 21:21:07 StandardWrapper[/examples:invoker]: Loading container servlet invoker
0
 
LVL 1

Author Comment

by:myuen
ID: 8096301
No, I didn't touch the example context in server.xml.  All I did was download the JBoss / Tomcat zip file from jboss.org and unzipped to my c: drive.  Then I messed around with the system/environment variables as stated above and ran JBoss.  I did nothing else.

0
 
LVL 14

Expert Comment

by:kennethxu
ID: 8096324
OK, I found the problem. Copy the "examples" directory to C:\jboss-3.0.6_tomcat-4.1.18\server\default\deploy, and you are set, now access:
http://localhost:8080/examples/
0
 
LVL 1

Author Comment

by:myuen
ID: 8116428
Hey kennethxu.  Thanks for the quick responses but for some reason, it just isn't working.  I did some research and I had to bundle examples up into a war file (called examples.war) and deploy it ot the directory you stated.  However, this didn't work.

So, what I decided to do was write a simpler HelloWorld servlet instead and try to deploy it.
Unfortunately, no luck.

Here's what i've done:
1. I created the following directory structure:
test\WEB-INF\classes
test\WEB-INF\lib

2. I created a web.xml and placed it in test\WEB-INF
Below is the web.xml file I made:
<web-app>
<servlet-mapping>
 <servlet-name>HelloWorldServlet</servlet-name>
 <url-pattern>/HelloWorldServlet</url-pattern>
</servlet-mapping>
</web-app>

3. Wrote a HelloWorldServlet class and it compiled into a class file no problem.  I put the class file in test\WEB-INF\classes

4. I then created a war file by doing jar -cvf test.war .

5. I copied the test.war I made in step 4 into
C:\jboss-3.0.6_tomcat-4.1.18\server\default\deploy

6. Now, when I go to: http://localhost:8080/test, I get the following error:
HTTP Status 404 - /test

--------------------------------------------------------------------------------

type Status report

message /test

description The requested resource (/test) is not available.


--------------------------------------------------------------------------------

Apache Tomcat/4.1.18-LE-jdk14

7.  I'm wondering if I haven't set my environmental or user properties correctly for JBoss? (see the first comment I made for my settings for my environment and user properties.
0
 
LVL 14

Expert Comment

by:kennethxu
ID: 8116776
first of all, how do you start the server do you use "C:\jboss-3.0.6_tomcat-4.1.18\bin\run.bat" or "C:\jboss-3.0.6_tomcat-4.1.18\tomcat-4.1.x\bin\startup.bat"?

if you use run.bat, go to C:\jboss-3.0.6_tomcat-4.1.18\server dir, you should see 3 subdir, they are "all", "default" and "minimal". go to each dir and check which dir has "log" and "tmp" dir? you should deploy your app under the dir that contains "log" and "tmp". in my installation, the "default" contains "log", so I deploy my app under default\deploy.

0
 
LVL 14

Accepted Solution

by:
kennethxu earned 400 total points
ID: 8116784
your web.xml should looks like:

<?xml version="1.0" encoding="ISO-8859-1"?>

<!DOCTYPE web-app
    PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN"
    "http://java.sun.com/dtd/web-app_2_3.dtd">

<web-app>

    <servlet>
        <servlet-name>HelloWorld</servlet-name>
        <servlet-class>HelloWorldServlet</servlet-class>
    </servlet>

    <servlet-mapping>
        <servlet-name>HelloWorld</servlet-name>
        <url-pattern>/HelloWorld</url-pattern>
    </servlet-mapping>

</web-app>

and your should access your servlet at http://localhost:8080/test/HelloWorld
0
 
LVL 14

Expert Comment

by:kennethxu
ID: 8116797
I would suggest you to start from simplest setup just put a "index.html" file under your "test" dir with an empty web.xml under "WEB-INF"
<?xml version="1.0" encoding="ISO-8859-1"?>

<!DOCTYPE web-app
   PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN"
   "http://java.sun.com/dtd/web-app_2_3.dtd">

<web-app>
</web-app>

then access http://localhost:8080/test/index.html

BTW, can you also post the output of: jar -tvf test.war?


0
 
LVL 1

Author Comment

by:myuen
ID: 8117068
Thank you, Thank you, Thank you.

I know this sounds stupid but i've never been more happy to get a Hello World program working in my life.  So much to learn still.  Thanks for your help.  I really appreciate it.

I've also upped the points to 100 for your troubles.
0
 
LVL 1

Author Comment

by:myuen
ID: 8117073
kennethxu, you da'man.  Thanks again for all your help.
0
 
LVL 14

Expert Comment

by:kennethxu
ID: 8120176
my pleasure to help and thanks for you points, happy coding :-)
0

Featured Post

Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

The well known Cerber ransomware continues to spread this summer through spear phishing email campaigns targeting enterprises. Learn how it easily bypasses traditional defenses - and what you can do to protect your data.
This article will show how Aten was able to supply easy management and control for Artear's video walls and wide range display configurations of their newsroom.
In this brief tutorial Pawel from AdRem Software explains how you can quickly find out which services are running on your network, or what are the IP addresses of servers responsible for each service. Software used is freeware NetCrunch Tools (https…
If you’ve ever visited a web page and noticed a cool font that you really liked the look of, but couldn’t figure out which font it was so that you could use it for your own work, then this video is for you! In this Micro Tutorial, you'll learn yo…

800 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question