Tomcat 5.5 & jsp

hi i am using tomcat 5.5 form my jsp, but when i use tomcat 4, it did not show me any error but when i use tomcat 5.0, it show mr this error:
javax.servlet.ServletException: [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified
but i have already put the data source name in the ODBC. i am using the microsoft access database.

Class.forName("sun.jdbc.odbc.JdbcOdbcDriver");
Connection connection = DriverManager.getConnection("jdbc:odbc:trying","","");
Statement statement = connection.createStatement();

Similar Messages

  • Calling a servlet (in Tomcat) from a JSP Page (in Apache)

    I have a web form in my JSP Page, which upon submits, will send the params to a servlet. The servlet will then process the request and send the results back to the calling JSP Page.
    with that above senario, is there any way for me to reference a servlet (resides in Tomcat) from a JSP Page (resides in Apache HTTP Server)?
    Thanks!

    Apache HTTP server isn't a servlet/JSP engine.
    Your JSP runs on Tomcat, right where the servlet does. Apache just forwards the request.
    %

  • Is Tomcat 4's jsp:plugin tag hardwired to 1.2?

    Is Tomcat 4's <jsp:plugin > tag hardwired to version 1.2 of the JPI?
    I was absolutely horrified today at a job interview when, proudly navigating to the page containing the 1.4-demanding applet I embedded in the page using <jsp:plugin ...> the plugin installation dialogue came up -- asking whether they wanted to install the 1.2 plugin (up until recently, I had the applet's object tag embedded manually... switching to jsp:plugin was fairly recent).
    As it turns out, the <object> tag generated by Tomcat was specifying the download path for the 1.2 plugin, even though I specified jreversion="1.4" in the <jsp:plugin> tag:
    <OBJECT
       classid="clsid:8AD9C840-044E-11D1-B3E9-00805F499D93"
       name="theApplet"
       width="550" 
       height="400" 
       align="middle" 
       codebase="http://java.sun.com/products/plugin/1.2.2/jinstall-1_2_2-win.cab#Version=1,2,2,0">The "clsid" value can be changed in web.xml by changing the jsp servlet's "ieClassId" initParam, but as far as I can tell there's NO mechanism for changing the "codebase" value anywhere.
    Is the <jsp:plugin> tag (under Tomcat 4, at least) just useless for Applets that must have 1.4, or is there a configuration parameter somewhere to set the "codebase" value generated by the tag?
    I know I could always put the manually-specified code back in, but I'd prefer to stay with the <jsp:plugin> tag if possible just because it makes the jsp source cleaner. What's strange is that nobody seems to have complained about that problem on the usual places (Usenet/dejanews/Google, jguru.com, etc). Whether that's just because nobody writes applets that actually demand 1.4, or whether everybody who does just embeds the <object> tag manually, I'm not sure.
    In any case, I'm trying to figure out how to make <jsp:plugin> generate the right HTML for 1.4-using applets... or whether it's even possible.

    Sigh. I found it. It's actually specified as the "iepluginurl" property of the <jsp:plugin> tag.
    <emotion:frustration variation="anger">
    Now I just need to figure out what *$%!# value to use for it.
    The JPI's developer guide has to be the worst document I've ever seen from Sun. Normally, Sun's documents are good. Often, exceptionally so. But the JPI guide... well, after reading http://java.sun.com/j2se/1.4.1/docs/guide/plugin/developer_guide/using_tags.html multiple times, I'm still not sure what #$%^&* URL corresponds to "The newest released JPI equal to or newer than 1.4.0". The only URL on the whole page that they even imply works is hardwired to 1.4.0, and in the same breath they imply that every other codebase URL on the page is wrong, hypothetical, and shouldn't be used... oh, and for that matter, the 1.4_0 one shouldn't really be used ether, because it might change in the future. Grrrrr.
    If there's a pattern to the following URLs (all used on the same page) that's supposed to illustrate something besides abyssmally bad editing and apparent indecision, I haven't seen it yet:
    http://java.sun.com/products/plugin/autodl/jinstall-1_4-windows-i586.cab#Version=1,4,0,0
    http://java.sun.com/products/plugin/1.4/jinstall-14-win32.cab#Version=1,4,0,mn
    http://java.sun.com/products/plugin/autodl/jinstall-1_4-windows-i586.cab#Version=1,4,1,mn
    http://java.sun.com/products/plugin/autodl/jinstall-1_4_0-win.cabHmmm. Let's see here. They're all the same up to http://java.sun.com/products/plugin, but from that point one diverges into /1.4/, while the others continue into /autodl/. But even past that point, two imply that the filename follows the pattern jinstall-1_4-windows-i586.cab#Version=1,4,x,* ... but whether developers who really, truly, don't care about the specific maintenance release should use "0" or "mn" is left up in the air.
    Furthermore, the ONE URL on the entire page that they come halfway close to implying will work is the last one I listed above, which itself goes totally against whatever hypthetical pattern they were trying to imply with the other three. For now I'll probably stick the last one listed as the parameter because it's the only one they actually come out and say will work, but I suspect the first one is probably the "right" one.
    Of course, there's always the matter of Macintosh users running IE. Or Windows users running Mozilla (which is technically Netscape, but uses MSIE ActiveX plugins). Does Mozilla get fed the value of "iepluginurl", or the value of "nspluginurl"? Sigh.
    </emotion:frustration>

  • Problem with Configuring Tomcat for running jsp web applications..Plz HELP

    I am using Tomcat 5.5 and Jdk 1.5.0_12 and Oracle 10g. I am using jdbc-odbc bridge connection
    to connect to the database. I have placed my project folder called
    tdm under the webapps folder in Tomcat. This 'tdm' folder consists of
    a collection of html pages,jsp pages and images of my project. Also I created a
    WEB-INF folderand in that I have lib folder which contains catalina-root.jar
    , classes12.jar and nls_charset.jar files. And also in the WEB-INF folder I have the web.xml
    file which looks like this
    <?xml version="1.0" encoding="ISO-8859-1"?>
    <!--
    Copyright 2004 The Apache Software Foundation
    Licensed under the Apache License, Version 2.0 (the "License");
    you may not use this file except in compliance with the License.
    You may obtain a copy of the License at
    http://www.apache.org/licenses/LICENSE-2.0
    Unless required by applicable law or agreed to in writing, software
    distributed under the License is distributed on an "AS IS" BASIS,
    WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
    See the License for the specific language governing permissions and
    limitations under the License.
    -->
    <web-app>
    <resource-ref>
    <description>Oracle Datasource example</description>
    <res-ref-name>jdbc/gdn</res-ref-name>
    <res-type>javax.sql.DataSource</res-type>
    <res-auth>Container</res-auth>
    </resource-ref>
    </web-app>
    My Server.xml file in Tomcat\conf folder is as follows
    <!-- 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">
    <!-- Comment these entries out to disable JMX MBeans support used for the
    administration web application -->
    <Listener className="org.apache.catalina.mbeans.ServerLifecycleListener" />
    <Listener className="org.apache.catalina.mbeans.GlobalResourcesLifecycleListener" />
    <!-- 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"
    factory="org.apache.catalina.users.MemoryUserDatabaseFactory"
    pathname="conf/tomcat-users.xml" />
    <Resource name="jdbc/gdn" auth="Container"
    type="javax.sql.DataSource" driverClassName="sun.jdbc.odbc.JdbcOdbcDriver"
    url="jdbc:odbc:gdn"
    username="system" password="tiger" maxActive="20" maxIdle="10"
    maxWait="-1"/>
    </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="Catalina">
    <!-- 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 5 documentation bundle for more detailed
    instructions):
    * If your JDK version 1.3 or prior, 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 HTTP/1.1 Connector on port 8080 -->
    <Connector
    port="5050" maxThreads="150" minSpareThreads="25" maxSpareThreads="75"
    enableLookups="false" redirectPort="8443" acceptCount="100"
    connectionTimeout="20000" disableUploadTimeout="true" />
    <!-- Note : To disable connection timeouts, set connectionTimeout value
    to 0 -->
         <!-- Note : To use gzip compression you could set the following properties :
                   compression="on"
                   compressionMinSize="2048"
                   noCompressionUserAgents="gozilla, traviata"
                   compressableMimeType="text/html,text/xml"
         -->
    <!-- Define a SSL HTTP/1.1 Connector on port 8443 -->
    <!--
    <Connector port="8443"
    maxThreads="150" minSpareThreads="25" maxSpareThreads="75"
    enableLookups="false" disableUploadTimeout="true"
    acceptCount="100" scheme="https" secure="true"
    clientAuth="false" sslProtocol="TLS" />
    -->
    <!-- Define an AJP 1.3 Connector on port 8009 -->
    <Connector port="8009"
    enableLookups="false" redirectPort="8443" protocol="AJP/1.3" />
    <!-- Define a Proxied HTTP/1.1 Connector on port 8082 -->
    <!-- See proxy documentation for more information about using this. -->
    <!--
    <Connector port="8082"
    maxThreads="150" minSpareThreads="25" maxSpareThreads="75"
    enableLookups="false" acceptCount="100" connectionTimeout="20000"
    proxyPort="80" disableUploadTimeout="true" />
    -->
    <!-- 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 AJP ie :
    <Engine name="Standalone" defaultHost="localhost" jvmRoute="jvm1">
    -->
    <!-- Define the top level container in our container hierarchy -->
    <Engine name="Catalina" defaultHost="localhost">
    <!-- 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.4
    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"/>
    -->
    <!-- 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"
    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"
    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"
    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"
    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
    Note: XML Schema validation will not work with Xerces 2.2.
    -->
    <Host name="localhost" appBase="webapps"
    unpackWARs="true" autoDeploy="true"
    xmlValidation="false" xmlNamespaceAware="false">
    <!-- Defines a cluster for this node,
    By defining this element, means that every manager will be changed.
    So when running a cluster, only make sure that you have webapps in there
    that need to be clustered and remove the other ones.
    A cluster has the following parameters:
    className = the fully qualified name of the cluster class
    name = a descriptive name for your cluster, can be anything
    mcastAddr = the multicast address, has to be the same for all the nodes
    mcastPort = the multicast port, has to be the same for all the nodes
    mcastBindAddr = bind the multicast socket to a specific address
    mcastTTL = the multicast TTL if you want to limit your broadcast
    mcastSoTimeout = the multicast readtimeout
    mcastFrequency = the number of milliseconds in between sending a "I'm alive" heartbeat
    mcastDropTime = the number a milliseconds before a node is considered "dead" if no heartbeat is received
    tcpThreadCount = the number of threads to handle incoming replication requests, optimal would be the same amount of threads as nodes
    tcpListenAddress = the listen address (bind address) for TCP cluster request on this host,
    in case of multiple ethernet cards.
    auto means that address becomes
    InetAddress.getLocalHost().getHostAddress()
    tcpListenPort = the tcp listen port
    tcpSelectorTimeout = the timeout (ms) for the Selector.select() method in case the OS
    has a wakup bug in java.nio. Set to 0 for no timeout
    printToScreen = true means that managers will also print to std.out
    expireSessionsOnShutdown = true means that
    useDirtyFlag = true means that we only replicate a session after setAttribute,removeAttribute has been called.
    false means to replicate the session after each request.
    false means that replication would work for the following piece of code: (only for SimpleTcpReplicationManager)
    <%
    HashMap map = (HashMap)session.getAttribute("map");
    map.put("key","value");
    %>
    replicationMode = can be either 'pooled', 'synchronous' or 'asynchronous'.
    * Pooled means that the replication happens using several sockets in a synchronous way. Ie, the data gets replicated, then the request return. This is the same as the 'synchronous' setting except it uses a pool of sockets, hence it is multithreaded. This is the fastest and safest configuration. To use this, also increase the nr of tcp threads that you have dealing with replication.
    * Synchronous means that the thread that executes the request, is also the
    thread the replicates the data to the other nodes, and will not return until all
    nodes have received the information.
    * Asynchronous means that there is a specific 'sender' thread for each cluster node,
    so the request thread will queue the replication request into a "smart" queue,
    and then return to the client.
    The "smart" queue is a queue where when a session is added to the queue, and the same session
    already exists in the queue from a previous request, that session will be replaced
    in the queue instead of replicating two requests. This almost never happens, unless there is a
    large network delay.
    -->
    <!--
    When configuring for clustering, you also add in a valve to catch all the requests
    coming in, at the end of the request, the session may or may not be replicated.
    A session is replicated if and only if all the conditions are met:
    1. useDirtyFlag is true or setAttribute or removeAttribute has been called AND
    2. a session exists (has been created)
    3. the request is not trapped by the "filter" attribute
    The filter attribute is to filter out requests that could not modify the session,
    hence we don't replicate the session after the end of this request.
    The filter is negative, ie, anything you put in the filter, you mean to filter out,
    ie, no replication will be done on requests that match one of the filters.
    The filter attribute is delimited by ;, so you can't escape out ; even if you wanted to.
    filter=".*\.gif;.*\.js;" means that we will not replicate the session after requests with the URI
    ending with .gif and .js are intercepted.
    The deployer element can be used to deploy apps cluster wide.
    Currently the deployment only deploys/undeploys to working members in the cluster
    so no WARs are copied upons startup of a broken node.
    The deployer watches a directory (watchDir) for WAR files when watchEnabled="true"
    When a new war file is added the war gets deployed to the local instance,
    and then deployed to the other instances in the cluster.
    When a war file is deleted from the watchDir the war is undeployed locally
    and cluster wide
    -->
    <!--
    <Cluster className="org.apache.catalina.cluster.tcp.SimpleTcpCluster"
    managerClassName="org.apache.catalina.cluster.session.DeltaManager"
    expireSessionsOnShutdown="false"
    useDirtyFlag="true"
    notifyListenersOnReplication="true">
    <Membership
    className="org.apache.catalina.cluster.mcast.McastService"
    mcastAddr="228.0.0.4"
    mcastPort="45564"
    mcastFrequency="500"
    mcastDropTime="3000"/>
    <Receiver
    className="org.apache.catalina.cluster.tcp.ReplicationListener"
    tcpListenAddress="auto"
    tcpListenPort="4001"
    tcpSelectorTimeout="100"
    tcpThreadCount="6"/>
    <Sender
    className="org.apache.catalina.cluster.tcp.ReplicationTransmitter"
    replicationMode="pooled"
    ackTimeout="15000"/>
    <Valve className="org.apache.catalina.cluster.tcp.ReplicationValve"
    filter=".*\.gif;.*\.js;.*\.jpg;.*\.htm;.*\.html;.*\.txt;"/>
    <Deployer className="org.apache.catalina.cluster.deploy.FarmWarDeployer"
    tempDir="/tmp/war-temp/"
    deployDir="/tmp/war-deploy/"
    watchDir="/tmp/war-listen/"
    watchEnabled="false"/>
    </Cluster>
    -->
    <!-- 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" />
    -->
    <!-- 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"/>
    -->
    <!-- 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.
    This access log implementation is optimized for maximum performance,
    but is hardcoded to support only the "common" and "combined" patterns.
    -->
    <!--
    <Valve className="org.apache.catalina.valves.FastCommonAccessLogValve"
    directory="logs" prefix="localhost_access_log." suffix=".txt"
    pattern="common" resolveHosts="false"/>
    -->
    <Context path="/tdm" docBase="tdm" debug="0" reloadable="true" />
    </Host>
    </Engine>
    </Service>
    </Server>
    I have set the context path to /tdm in the server.xml file. Should this be placed in context.xml?
    My first page in the project is called Homepage.html. To start my project I give http://localhost:5050/tdm/homepage.html
    in a browser. Here I accept a username and password from the user and then do the validation in
    a valid.jsp file, where I connect to the database and check and use jsp:forward to go to next pages
    accordingly. However when I enter the username and password and click Go in the homepage, nothing is
    displayed on the next page. The URL in the browser says valid.jsp but a blank screen appears.
    WHY DOES IT HAPPEN SO? DOES IT MEAN THAT TOMCAT IS NOT RECOGNIZING JAVA IN MY SYSTEM OR IS IT A PROBLEM
    WITH THE DATABASE CONNECTION OR SOMETHING ELSE? I FEEL THAT TOMCAT IS NOT EXECUTING JSP COMMANDS?
    IS IT POSSIBLE?WHY WILL THIS HAPPEN?
    I set the JAVA_HOME and CATALINA_HOME environment to the jdk and tomcat folders resp.
    Is there any other thing that I need to set in classpath? Should I have my project as a
    WAR file in the webapps of TOMCAT or just a folder i.e. directory structure will fine?

    I am using Tomcat 5.5 and Jdk 1.5.0_12 and Oracle 10g. I am using jdbc-odbc bridge connection
    to connect to the database. I have placed my project folder called
    tdm under the webapps folder in Tomcat. This 'tdm' folder consists of
    a collection of html pages,jsp pages and images of my project. Also I created a
    WEB-INF folderand in that I have lib folder which contains catalina-root.jar
    , classes12.jar and nls_charset.jar files. And also in the WEB-INF folder I have the web.xml
    file which looks like this
    <?xml version="1.0" encoding="ISO-8859-1"?>
    <!--
    Copyright 2004 The Apache Software Foundation
    Licensed under the Apache License, Version 2.0 (the "License");
    you may not use this file except in compliance with the License.
    You may obtain a copy of the License at
    http://www.apache.org/licenses/LICENSE-2.0
    Unless required by applicable law or agreed to in writing, software
    distributed under the License is distributed on an "AS IS" BASIS,
    WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
    See the License for the specific language governing permissions and
    limitations under the License.
    -->
    <web-app>
    <resource-ref>
    <description>Oracle Datasource example</description>
    <res-ref-name>jdbc/gdn</res-ref-name>
    <res-type>javax.sql.DataSource</res-type>
    <res-auth>Container</res-auth>
    </resource-ref>
    </web-app>
    My Server.xml file in Tomcat\conf folder is as follows
    <!-- 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">
    <!-- Comment these entries out to disable JMX MBeans support used for the
    administration web application -->
    <Listener className="org.apache.catalina.mbeans.ServerLifecycleListener" />
    <Listener className="org.apache.catalina.mbeans.GlobalResourcesLifecycleListener" />
    <!-- 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"
    factory="org.apache.catalina.users.MemoryUserDatabaseFactory"
    pathname="conf/tomcat-users.xml" />
    <Resource name="jdbc/gdn" auth="Container"
    type="javax.sql.DataSource" driverClassName="sun.jdbc.odbc.JdbcOdbcDriver"
    url="jdbc:odbc:gdn"
    username="system" password="tiger" maxActive="20" maxIdle="10"
    maxWait="-1"/>
    </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="Catalina">
    <!-- 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 5 documentation bundle for more detailed
    instructions):
    * If your JDK version 1.3 or prior, 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 HTTP/1.1 Connector on port 8080 -->
    <Connector
    port="5050" maxThreads="150" minSpareThreads="25" maxSpareThreads="75"
    enableLookups="false" redirectPort="8443" acceptCount="100"
    connectionTimeout="20000" disableUploadTimeout="true" />
    <!-- Note : To disable connection timeouts, set connectionTimeout value
    to 0 -->
         <!-- Note : To use gzip compression you could set the following properties :
                   compression="on"
                   compressionMinSize="2048"
                   noCompressionUserAgents="gozilla, traviata"
                   compressableMimeType="text/html,text/xml"
         -->
    <!-- Define a SSL HTTP/1.1 Connector on port 8443 -->
    <!--
    <Connector port="8443"
    maxThreads="150" minSpareThreads="25" maxSpareThreads="75"
    enableLookups="false" disableUploadTimeout="true"
    acceptCount="100" scheme="https" secure="true"
    clientAuth="false" sslProtocol="TLS" />
    -->
    <!-- Define an AJP 1.3 Connector on port 8009 -->
    <Connector port="8009"
    enableLookups="false" redirectPort="8443" protocol="AJP/1.3" />
    <!-- Define a Proxied HTTP/1.1 Connector on port 8082 -->
    <!-- See proxy documentation for more information about using this. -->
    <!--
    <Connector port="8082"
    maxThreads="150" minSpareThreads="25" maxSpareThreads="75"
    enableLookups="false" acceptCount="100" connectionTimeout="20000"
    proxyPort="80" disableUploadTimeout="true" />
    -->
    <!-- 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 AJP ie :
    <Engine name="Standalone" defaultHost="localhost" jvmRoute="jvm1">
    -->
    <!-- Define the top level container in our container hierarchy -->
    <Engine name="Catalina" defaultHost="localhost">
    <!-- 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.4
    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"/>
    -->
    <!-- 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"
    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"
    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"
    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"
    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
    Note: XML Schema validation will not work with Xerces 2.2.
    -->
    <Host name="localhost" appBase="webapps"
    unpackWARs="true" autoDeploy="true"
    xmlValidation="false" xmlNamespaceAware="false">
    <!-- Defines a cluster for this node,
    By defining this element, means that every manager will be changed.
    So when running a cluster, only make sure that you have webapps in there
    that need to be clustered and remove the other ones.
    A cluster has the following parameters:
    className = the fully qualified name of the cluster class
    name = a descriptive name for your cluster, can be anything
    mcastAddr = the multicast address, has to be the same for all the nodes
    mcastPort = the multicast port, has to be the same for all the nodes
    mcastBindAddr = bind the multicast socket to a specific address
    mcastTTL = the multicast TTL if you want to limit your broadcast
    mcastSoTimeout = the multicast readtimeout
    mcastFrequency = the number of milliseconds in between sending a "I'm alive" heartbeat
    mcastDropTime = the number a milliseconds before a node is considered "dead" if no heartbeat is received
    tcpThreadCount = the number of threads to handle incoming replication requests, optimal would be the same amount of threads as nodes
    tcpListenAddress = the listen address (bind address) for TCP cluster request on this host,
    in case of multiple ethernet cards.
    auto means that address becomes
    InetAddress.getLocalHost().getHostAddress()
    tcpListenPort = the tcp listen port
    tcpSelectorTimeout = the timeout (ms) for the Selector.select() method in case the OS
    has a wakup bug in java.nio. Set to 0 for no timeout
    printToScreen = true means that managers will also print to std.out
    expireSessionsOnShutdown = true means that
    useDirtyFlag = true means that we only replicate a session after setAttribute,removeAttribute has been called.
    false means to replicate the session after each request.
    false means that replication would work for the following piece of code: (only for SimpleTcpReplicationManager)
    <%
    HashMap map = (HashMap)session.getAttribute("map");
    map.put("key","value");
    %>
    replicationMode = can be either 'pooled', 'synchronous' or 'asynchronous'.
    * Pooled means that the replication happens using several sockets in a synchronous way. Ie, the data gets replicated, then the request return. This is the same as the 'synchronous' setting except it uses a pool of sockets, hence it is multithreaded. This is the fastest and safest configuration. To use this, also increase the nr of tcp threads that you have dealing with replication.
    * Synchronous means that the thread that executes the request, is also the
    thread the replicates the data to the other nodes, and will not return until all
    nodes have received the information.
    * Asynchronous means that there is a specific 'sender' thread for each cluster node,
    so the request thread will queue the replication request into a "smart" queue,
    and then return to the client.
    The "smart" queue is a queue where when a session is added to the queue, and the same session
    already exists in the queue from a previous request, that session will be replaced
    in the queue instead of replicating two requests. This almost never happens, unless there is a
    large network delay.
    -->
    <!--
    When configuring for clustering, you also add in a valve to catch all the requests
    coming in, at the end of the request, the session may or may not be replicated.
    A session is replicated if and only if all the conditions are met:
    1. useDirtyFlag is true or setAttribute or removeAttribute has been called AND
    2. a session exists (has been created)
    3. the request is not trapped by the "filter" attribute
    The filter attribute is to filter out requests that could not modify the session,
    hence we don't replicate the session after the end of this request.
    The filter is negative, ie, anything you put in the filter, you mean to filter out,
    ie, no replication will be done on requests that match one of the filters.
    The filter attribute is delimited by ;, so you can't escape out ; even if you wanted to.
    filter=".*\.gif;.*\.js;" means that we will not replicate the session after requests with the URI
    ending with .gif and .js are intercepted.
    The deployer element can be used to deploy apps cluster wide.
    Currently the deployment only deploys/undeploys to working members in the cluster
    so no WARs are copied upons startup of a broken node.
    The deployer watches a directory (watchDir) for WAR files when watchEnabled="true"
    When a new war file is added the war gets deployed to the local instance,
    and then deployed to the other instances in the cluster.
    When a war file is deleted from the watchDir the war is undeployed locally
    and cluster wide
    -->
    <!--
    <Cluster className="org.apache.catalina.cluster.tcp.SimpleTcpCluster"
    managerClassName="org.apache.catalina.cluster.session.DeltaManager"
    expireSessionsOnShutdown="false"
    useDirtyFlag="true"
    notifyListenersOnReplication="true">
    <Membership
    className="org.apache.catalina.cluster.mcast.McastService"
    mcastAddr="228.0.0.4"
    mcastPort="45564"
    mcastFrequency="500"
    mcastDropTime="3000"/>
    <Receiver
    className="org.apache.catalina.cluster.tcp.ReplicationListener"
    tcpListenAddress="auto"
    tcpListenPort="4001"
    tcpSelectorTimeout="100"
    tcpThreadCount="6"/>
    <Sender
    className="org.apache.catalina.cluster.tcp.ReplicationTransmitter"
    replicationMode="pooled"
    ackTimeout="15000"/>
    <Valve className="org.apache.catalina.cluster.tcp.ReplicationValve"
    filter=".*\.gif;.*\.js;.*\.jpg;.*\.htm;.*\.html;.*\.txt;"/>
    <Deployer className="org.apache.catalina.cluster.deploy.FarmWarDeployer"
    tempDir="/tmp/war-temp/"
    deployDir="/tmp/war-deploy/"
    watchDir="/tmp/war-listen/"
    watchEnabled="false"/>
    </Cluster>
    -->
    <!-- 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" />
    -->
    <!-- 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"/>
    -->
    <!-- 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.
    This access log implementation is optimized for maximum performance,
    but is hardcoded to support only the "common" and "combined" patterns.
    -->
    <!--
    <Valve className="org.apache.catalina.valves.FastCommonAccessLogValve"
    directory="logs" prefix="localhost_access_log." suffix=".txt"
    pattern="common" resolveHosts="false"/>
    -->
    <Context path="/tdm" docBase="tdm" debug="0" reloadable="true" />
    </Host>
    </Engine>
    </Service>
    </Server>
    I have set the context path to /tdm in the server.xml file. Should this be placed in context.xml?
    My first page in the project is called Homepage.html. To start my project I give http://localhost:5050/tdm/homepage.html
    in a browser. Here I accept a username and password from the user and then do the validation in
    a valid.jsp file, where I connect to the database and check and use jsp:forward to go to next pages
    accordingly. However when I enter the username and password and click Go in the homepage, nothing is
    displayed on the next page. The URL in the browser says valid.jsp but a blank screen appears.
    WHY DOES IT HAPPEN SO? DOES IT MEAN THAT TOMCAT IS NOT RECOGNIZING JAVA IN MY SYSTEM OR IS IT A PROBLEM
    WITH THE DATABASE CONNECTION OR SOMETHING ELSE? I FEEL THAT TOMCAT IS NOT EXECUTING JSP COMMANDS?
    IS IT POSSIBLE?WHY WILL THIS HAPPEN?
    I set the JAVA_HOME and CATALINA_HOME environment to the jdk and tomcat folders resp.
    Is there any other thing that I need to set in classpath? Should I have my project as a
    WAR file in the webapps of TOMCAT or just a folder i.e. directory structure will fine?

  • Question concerning Eclipse and Tomcat Plugin and JSP

    I have a Tomcat-Project that I am working on in Eclipse and quite a few external JARs. Everything works fine, when I run my Test class within my project (in Eclipse). But as soon, as I am trying to call the jsp in my browser I get Exceptions: "java.lang.NoClassDefFoundError: org/apache/log4j/Logger" for example, which tells me that in the browser it can't find the JARs... I'm guessing something's wrong with the classpath but I was thinking that Eclipse would handle those things for me...
    I've added the JARs to my project via Eclipse (Properties -> Java Build Path -> Libraries -> Add external JARs). And I've created a subdirectory for my jsp files and allowed my project to update the .xml file for the settings and all... Do I need to do anything else? What have I done wrong so far, have I forgotten to do?

    I solved the problem...

  • Tomcat not loading jsp pages

    I've running 10.6.2 with default install of Tomcat and Apache. Tomcat is enabled in Server Admin, and I've created a site in Server Admin that points 8080 port requests to /Library/Tomcat/webapps. And index.jsp is set as a default index file.
    When I try and go to myserver:8080/mysite the browser loads the jsp as text. Just like I'd opened it in a text file.
    I've removed the site folder, and uploaded a new war file (which works on my local 10.6.2 client machine with Tomcat 6.0.24 installed), and a new site folder is created as expected. But the jsp page just doesn't load correctly.
    What am I missing (besides years of Tomcat and Apache experience..)

    hey.. noticed one more thing.. stuff works when i put
    it in my file:///var/lib/tomcat-5.5/webapps/ROOT/
    folder .. so i think i havent set my user properly..
    any pointers??I don't think you should be putting stuff in ROOT.
    Create your own web context and put it under /webapps.
    %

  • Tomcat 5.0 JSP ServiceFactory Error

    Hi,
    I am running Apache 2, Tomcat 5.0, Axis on a server for deploying webservics. When I execute a command line java program it works just fine, but When I attempt to use this same code from a JSP it throws a ServiceException for ServiceFactory.newInstance at runtime. The code Find2p is common to both the Command Line and the JSP. For detail Find2p.java is listed way below.
    Any insight into this error would be greatly appreciated, if more info is need I would happily add it to this discussion.
    Thanks in Advance,
    Wayne
    JSP Code
    package test.jsp;
    import java.io.*;
    import javax.servlet.*;
    import javax.servlet.http.*;
    import javax.xml.namespace.QName;
    /** Simple servlet for testing the use of packages
    * and utilities from the same package.
    * <P>
    * Taken from Core Servlets and JavaServer Pages 2nd Edition
    * from Prentice Hall and Sun Microsystems Press,
    * http://www.coreservlets.com/.
    * &copy; 2003 Marty Hall; may be freely used or adapted.
    public class HelloServlet3 extends HttpServlet {
    public void doGet(HttpServletRequest request,
    HttpServletResponse response)
    throws ServletException, IOException {
    response.setContentType("text/html");
    PrintWriter out = response.getWriter();
    Find2p f = new Find2p("smith");
    String title = "Hello (z)";
    String x = "RESULTS " + f.getRes() + " INPUT " + f.getParam1();
    out.println(ServletUtilities.headWithTitle(title) +
    "<BODY BGCOLOR=\"#FDF5E6\">\n" +
    "<H1>" + title + x + "</H1>\n" +
    "</BODY></HTML>");
    HERE IS THE COMMAND LINE CODE:
    package test.jsp;
    import javax.xml.namespace.QName;
    import javax.xml.rpc.*;
    import javax.xml.rpc.ServiceFactory;
    import javax.xml.rpc.Service;
    import javax.xml.rpc.Call;
    public class ClientFind2p
    public static void main(String [] args) throws Exception
    String param2 = args[0];
    System.out.println("sending: " + param2);
    Find2p f = new Find2p(param2);
    System.out.println("RESULTS " + f.getRes() + " INPUT " + f.getParam1());
    AND Find2p.java
    package test.jsp;
    import javax.xml.namespace.QName;
    import javax.xml.rpc.*;
    import java.net.*;
    import java.rmi.*;
    import javax.xml.rpc.ServiceFactory;
    import javax.xml.rpc.Service;
    import javax.xml.rpc.Call;
    class Find2p
    public Find2p(String ln)
    try
    String epAddr = "http://172.16.1.232/axis/services/JDBCServiceDMPort1";
    String wsdlAddr = epAddr + "?wsdl";
    param1 = ln;
    String nameSpaceUri = "http://www.ussa.org/test/";
    String svcName = "JDBCServiceDM";
    String portName = "JDBCServiceDMPort1";
    java.net.URL wsdlUrl = new java.net.URL(wsdlAddr);
    ServiceFactory svcFactory = ServiceFactory.newInstance(); THIS LINE THROW A ServiceException in JSP
    QName svcQName = new QName(nameSpaceUri, svcName);
    what = "Nothing Thrown";
    Service svc = svcFactory.createService(wsdlUrl, svcQName);
    Call call = (Call) svc.createCall();
    call.setTargetEndpointAddress(epAddr);
    call.setOperationName( new QName(nameSpaceUri, "findussa") );
    call.setPortTypeName( new QName(nameSpaceUri, portName) );
    Object argx = param1;
    res = (String) call.invoke(new Object[] {argx});
    catch (ServiceException e2)
    servicemsg = e2.getMessage();
    catch (JAXRPCException e3)
    rpcmsg = e3.getMessage();
    catch (MalformedURLException e4)
    malmsg = e4.getMessage();
    catch (RemoteException e5)
    remotemsg = e5.getMessage();
    public String getRes()
    return res;
    public String getParam1()
    return param1;
    public String getWhat()
    return what;
    public String getExceptionmsg()
    return exceptionmsg;
    public String getServicemsg()
    return servicemsg;
    public String getRPCmsg()
    return rpcmsg;
    public String getMALmsg()
    return malmsg;
    public String getRemotemsg()
    return remotemsg;
    private String res;
    private String param1;
    private String what;
    private String exceptionmsg;
    private String servicemsg;
    private String rpcmsg;
    private String malmsg;
    private String remotemsg;
    }

    Can you give us more details of Exception or try to debug your Servlet by using remote debug.

  • Tomcat directory structure + jsp

    Hi all,
    I have been trying for a long time now to setup my tomcat-directory as described, but I don't get my application running... My directory structure is currently as follows:
    d:\
        webapp\
             web\
                  WEB-INF\
                        classes\
                             servlet
                        libThe path for tomcat is set to d:\webapp\web, where my JSPs are. From the JSPs, I start some applets - the problem is, where do I have to put them? They are in the directory project; if I put this directory in WEB-INF/classes, they are not found. If I put them directly in the web-directory, they are found, but not the classes they depend on... I can then put all the classes I need in the web-directory, and my application runs, but as far as I understood, this is not the supposed setting :-( And besides, the only reason for the WEB-INF directory would then be the servlets inside (which run without problems!)
    Might I do something wrong in calling the applets? In the moment, I start them with <applet code="project/Start.class"> Or do I need to change something in the web.xml file?
    Thanks for any hints,
    Thea

    but as far as I understood, this is not the supposed setting That IS the appropriate setting.
    An applet runs on the client machine.
    Therefore the client has to download all the class files to run the applet.
    The client cannot download any classes that are under WEB-INF. WEB-INF directory is for the server only.
    Therefore any classes needed to run your applet must be outside of the WEB-INF folder, so they can be downloaded.
    JSP/Servlet code runs on the server side. The code for this you can put under WEB-INF, and it will only be available to the server. That way you have your application, but don't have the code freely downloadable.
    Cheers,
    evnafets

  • Using TomCat to view JSP files

    I've installed tomcat for the purpose of viewing jsp files.
    In which folder am i supposed to place the jsp files to view them?
    Also, what address am i supposed to type in my browser ( http://localhost:8080/myJspFile.jsp ?????? )
    My tomcat folder is e:\tomcat
    and JAVA_HOME is d:\jdk1.3
    Thank you

    Here is a good link for you to start from
    http://www.moreservlets.com/Using-Tomcat-4.html#Try-Pages
    http://localhost:8080/myJspFile.jsp
    This looks right unless you have changed your port setting which the link above shows you how to change the port setting to port 80 so you dont have to type http://localhost:8080/blah it would http://localhost/blah.
    You_tomcat_install/webapps/ROOT
    or
    You_tomcat_install/webapps/ROOT/some_dir
    Anyways good luck and go to that link I gave you and it should help you out alot.

  • Tomcat is compiling JSP's on each request

    Hi , I have deployed an application on Tomcat 5.0.28 on Linux, and the strange thing is that Tomcat is compiling the JSP's on each request , Any idea why such a thing is happening.
    TIA
    rc

    As i checked the Date and time stamp of the .java and .class files produced , after each request to JSP
    I am yet to try the soln u provided yesterday .This new bug is more urgent.
    rc

  • Tomcat not opening jsp pages

    I installed apache 2 and tomcat and configured them both.... i installed mod_jk as the connector
    But when i open a jsp page, i get
    HTTP Status 404 - /~scriptdevil/hello.jsp
    type Status report
    message /~scriptdevil/hello.jsp
    description The requested resource (/~scriptdevil/hello.jsp) is not available.
    Apache Tomcat/5.5PHP files open just fine.
    How should i use it??

    hey.. noticed one more thing.. stuff works when i put
    it in my file:///var/lib/tomcat-5.5/webapps/ROOT/
    folder .. so i think i havent set my user properly..
    any pointers??I don't think you should be putting stuff in ROOT.
    Create your own web context and put it under /webapps.
    %

  • TOMCAT 5 AND JSP

    I have a application web (jsp and servlets)and when I work from LOCALHOST the jsp works correctly, but IF I access from INTERNET (NOT LOCALHOST)THE JSP DON T SHOW CORRECTLY, THE DATA THAT LOAD FROM A JAVA VECTOR (ONLY IT IS SEEN IN THE TOMCAT CONSOLE)BUT NOT IN THE JSP, I USED
    <%@ page isThreadSafe="false" %>
    FOR CONCURRENCY SETTINGS, but i dont know that it happens. Thanks-

    I don't think the concurrency settings would make any difference.
    What does the JSP actually show when you attempt to access it via the Internet? If you are not getting a page at all, then the most likely situation is that a firewall somewhere is blocking it. Another possibility is that you did not correctly configure your servlet engine to respond to that network address.
    Err, for example, it is possible to configure Tomcat such that it gives one set of pages to localhost, another set of pages to www.carlos_borjas.com, and yet third set of pages to admin.carlos_borjas.com. But more commonly, people do forget that to access Tomcat directly, they need to specify port 8080. Or alternatively, you've installed Apache as well as Tomcat, but forgot to install the software module that told Apache to forward all JSP requests to Tomcat.
    Or it could be that only part of your JSP page is loading, and usually we can tell you why it stopped loading if we saw the code where it stopped loading.
    I can go on, there are lots of possibilities. The key question is, what is actually happening, and what are you expecting to happen?

  • Tomcat config problem: jsp can't find a bean class

    I've been working within a JSP/Javabeans/JDBC/MySQL architecture with Windows XP and Websphere. So far everything works perfectly. Now I need to get the same project and make it run with a Tomcat server.
    I've already set the Tomcat server but its not working properly. I have a problem when a jsp tries to access any class inside my project's package.
    For example, when I make the next call:
    <jsp:useBean id="ctrl" class="myPack.myBean" scope="page"/>
    I get an error saying:
    Error: 500
    Location: /myproj/login.jsp
    Internal Servlet Error:
    org.apache.jasper.JasperException: Unable to compile C:\Program Files\jakarta-tomcat-3.3.1\work\DEFAULT\myproj\login_1.java:64: Class myPack.myBean not found.
    myPack.myBean ctrl = null;
    ^
    I believe that my problem cames when setting the Tomcat environment. So far what I have done is:
    * install j2sdk-1.3.1.03
    * install jakarta-tomcat-3.3.1
    * install mysql-max-3.23.51-win
    * set the environment variable JAVA_HOME
    * set the environment variable TOMCAT_HOME
    * set the environment variable MYSQL_HOME
    * add the %JAVA_HOME%\bin to the PATH
    * create 'myproj' directory inside TOMCAT_HOME\webapps
    * create into 'myproj' the subdirectory WEB-INF\classes and copy into it the jar file with my java classes (myPack.jar).
    * copy into TOMCAT_HOME\lib\apps the JDBC driver for MySQL.
    * copy my project files (jsp, html, images, etc.) and its structure into 'myproj' directory.
    I haven't include anything into the CLASSPATH because so far I've read that Tomcat will automatically include all the classes that are inside the directories TOMCAT_HOME\myproj\WEB-INF\classes and TOMCAT_HOME\lib\apps.
    I really don't have a clue about what I'm doing wrong. I'd apreciate if anyone can help me out with this one ;) ... I thank you in advance!

    Hi, it's me again!.
    Since nobody replied to me I'm replying myself :D
    Ok, seriously is just to let you know that I have solved my problem and I would like to tell you how I solved it ... somebody might be doing the same mistake than I was doing and could found this helpful. I just forgot to mention that I was using Tomcat 3.3.
    Well, first of all let me tell you that there was nothing wrong with the previous configuration that I post in my first message. Everything is ok except that in the TOMCAT_HOME\webapps\myproj\WEB-INF\classes directory I was putting my classes as a jar file, so I deleted it and instead I put the directory myPack with its unpacked class files. THIS SOLVED MY PROBLEM!!!
    First I was trying to do some complicated things editing bat and xml files, but as a matter of fact I found it's quite simple. Furthermore, I was really surprised by the performance of Tomcat. I'm relly happy for that !! ;)
    Hope it works for you,
    Ernesto

  • Restart Tomcat with every JSP change??

    I hope I'm missing something obvious here...
    Using JWSDP-1.2 (EA4).
    Every time I make a change to the component tree by adding an <h:whatever> tag in my page, JSF breaks when I refresh.
    For example, if I have the code below:
          <h:input_text id="password" valueRef="testBean.password">
               <f:validate_required/>
          </h:input_text>             
          <h:command_button id="submit" label="Submit"
            commandName="submit" />And I insert this line before the <h:command_button>:
    <h:output_errors  for="password"/>  The command button does not render.
    I find that the only way to get the page to render correctly is to go to the Tomcat manager, reload the webapp, and then use another JSP to invalidate my session. Then the page functions correctly. Pretty cumbersome for someone who develops JSPs with the "modify and refresh" method.
    Is this standard behavior that all of you are encountering? Will it continue to be so?

    From what I learned with tryout and error, you need to force JSF to recreate the components tree for it to register modifications.
    The easiest way I found was to load another page with JSF, so I made a link to another page from within the page I was testing.
    Hope this help.
    Patrick

  • Changing tomcat to read jsp from database

    Is there any way to change tomcat 5.5 to read the JSPs from a database instead of local disk. I have been reading the tomcat javadoc for some time but was unable to find the right classes to customize for this task.
    Can you please give us a help on which are the sections that we should look into to create this feature?
    THANKS!

    It doesn't make sense to read a database directly from an applet. If an applet needs data from a database is should request if from the server which the applet is located on and the server should do the actual database actions.
    The whole point of applets is that they require no installation on the client machine. If you have to change policy files or the like, you might as well install a Swing application. Furthermore accessing a database tends to depend on how the client is set up on the network. Any sensible network has firewall settings that block access to the database ports to any external access (and, again, if you are limiting the facility to a few internal machines then why not just install a program on them).

Maybe you are looking for

  • I don't seem to have View anymore. I can't fix my screen. Why is Mozilla deciding that I should ignore threads. I don't want to ignore threads. I can't fix this

    I am really distressed that Mozilla apparently unilaterally decided I should not see all my threads. I DO want to see all my threads. In fact, one reason I don't get my mail from a website is that I don't like my messages grouped according to threads

  • Can't get photo gallery slide show to work

    Hello, If anyone could help, I'd appreciate it. This is for a non-profit I work for. After getting the gallery to work, I can't get the slide show to work. from my gallery.html: <title>Photo Gallery</title> <link href="../css/screen.css" rel="stylesh

  • 11gR1 backup for 11gR2 database clone.

    Hi all, Our OS is 64 bit RHEL 5.7. On this we have EBS R12.1.3. with db version 11.1. Recently I installed EBS 12.1.3 (actually installed 12.1.1 and upgraded to 12.1.3) on a VM and upgraded its 11.1.0.7 db to 11.2.0.3. Now as I want to test the CPU p

  • Internal Stock transfer in Hospital Senatio

    Dear Experts, we are doing in IS-Hospital Implementation in MM Scenario  we have one Plant and 1 Main storage location is there In Hospital 10 Different departments is there like Radiology, cardiology etc. Departments if need a material how we follow

  • Split single column to multiple

    Hello dears. please i have the following along column as below and i want to make it multiple column. 07700000295 07700000519 07700000937 07700000987 07700001113 07700001846 07700002397 07700002427 Output>> 07700000295 07700000937 07700001113 0770000