facebook

tomact 6 and mysql configuration problem in Myeclipse 6

  1. MyEclipse IDE
  2.  > 
  3. Off Topic
Viewing 7 posts - 1 through 7 (of 7 total)
  • Author
    Posts
  • #275004 Reply

    amir55
    Participant

    I followed as in this site:
    http://tomcat.apache.org/tomcat-6.0-doc/jndi-datasource-examples-howto.html

    1 – the error in running the example

    SEVERE: Servlet.service() for servlet jsp threw exception
    org.apache.jasper.JasperException: An exception occurred processing JSP page /index.jsp at line 4

    1: <%@ taglib uri=”http://java.sun.com/jsp/jstl/sql&#8221; prefix=”sql” %>
    2: <%@ taglib uri=”http://java.sun.com/jsp/jstl/core&#8221; prefix=”c” %>
    3:
    4: <sql:query var=”rs” dataSource=”jdbc/TestDB”>
    5: select id, foo, bar from testdata
    6: </sql:query>
    7:

    2 – I added the driver to my web-inf/lib

    3 – I have configured mysql to myeclipse that works with JBoss already

    4 – I have added context to sever.xml just before </host> and my web.xml as in the tutorial as below.

    The question

    MyEclipse 6 comes enabled and should be configured with mysql but anyway what more to do?

    1 – web.xml with only the resource-ref added

    <?xml version=”1.0″ encoding=”UTF-8″?>
    <web-app version=”2.4″
    xmlns=”http://java.sun.com/xml/ns/j2ee&#8221;
    xmlns:xsi=”http://www.w3.org/2001/XMLSchema-instance&#8221;
    xsi:schemaLocation=”http://java.sun.com/xml/ns/j2ee
    http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd”&gt;
    <welcome-file-list>
    <welcome-file>index.jsp</welcome-file>
    </welcome-file-list>
    <!– ************ next added as in the totorial *********** –>

    <description>MySQL Test App</description>
    <resource-ref>
    <description>DB Connection</description>
    <res-ref-name>jdbc/TestDB</res-ref-name>
    <res-type>javax.sql.DataSource</res-type>
    <res-auth>Container</res-auth>
    </resource-ref>
    </web-app>

    2 – server.xml with only context is added

    the same but added the context as follows as in the tutorial

    <!– Note: A “Server” is not itself a “Container”, so you may not
    define subcomponents such as “Valves” at this level.
    Documentation at /docs/config/server.html
    –>
    <Server port=”8005″ shutdown=”SHUTDOWN”>

    <!–APR library loader. Documentation at /docs/apr.html –>
    <Listener className=”org.apache.catalina.core.AprLifecycleListener” SSLEngine=”on” />
    <!–Initialize Jasper prior to webapps are loaded. Documentation at /docs/jasper-howto.html –>
    <Listener className=”org.apache.catalina.core.JasperListener” />
    <!– JMX Support for the Tomcat server. Documentation at /docs/non-existent.html –>
    <Listener className=”org.apache.catalina.mbeans.ServerLifecycleListener” />
    <Listener className=”org.apache.catalina.mbeans.GlobalResourcesLifecycleListener” />

    <!– Global JNDI resources
    Documentation at /docs/jndi-resources-howto.html
    –>
    <GlobalNamingResources>
    <!– 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” />
    </GlobalNamingResources>

    <!– A “Service” is a collection of one or more “Connectors” that share
    a single “Container” Note: A “Service” is not itself a “Container”,
    so you may not define subcomponents such as “Valves” at this level.
    Documentation at /docs/config/service.html
    –>
    <Service name=”Catalina”>

    <!–The connectors can use a shared executor, you can define one or more named thread pools–>
    <!–
    <Executor name=”tomcatThreadPool” namePrefix=”catalina-exec-”
    maxThreads=”150″ minSpareThreads=”4″/>
    –>

    <!– A “Connector” represents an endpoint by which requests are received
    and responses are returned. Documentation at :
    Java HTTP Connector: /docs/config/http.html (blocking & non-blocking)
    Java AJP Connector: /docs/config/ajp.html
    APR (HTTP/AJP) Connector: /docs/apr.html
    Define a non-SSL HTTP/1.1 Connector on port 8080
    –>
    <Connector port=”8080″ protocol=”HTTP/1.1″
    connectionTimeout=”20000″
    redirectPort=”8443″ />
    <!– A “Connector” using the shared thread pool–>
    <!–
    <Connector executor=”tomcatThreadPool”
    port=”8080″ protocol=”HTTP/1.1″
    connectionTimeout=”20000″
    redirectPort=”8443″ />
    –>
    <!– Define a SSL HTTP/1.1 Connector on port 8443
    This connector uses the JSSE configuration, when using APR, the
    connector should be using the OpenSSL style configuration
    described in the APR documentation –>
    <!–
    <Connector port=”8443″ protocol=”HTTP/1.1″ SSLEnabled=”true”
    maxThreads=”150″ scheme=”https” secure=”true”
    clientAuth=”false” sslProtocol=”TLS” />
    –>

    <!– Define an AJP 1.3 Connector on port 8009 –>
    <Connector port=”8009″ protocol=”AJP/1.3″ redirectPort=”8443″ />

    <!– 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).
    Documentation at /docs/config/engine.html –>

    <!– You should set jvmRoute to support load-balancing via AJP ie :
    <Engine name=”Standalone” defaultHost=”localhost” jvmRoute=”jvm1″>
    –>
    <Engine name=”Catalina” defaultHost=”localhost”>

    <!–For clustering, please take a look at documentation at:
    /docs/cluster-howto.html (simple how to)
    /docs/config/cluster.html (reference documentation) –>
    <!–
    <Cluster className=”org.apache.catalina.ha.tcp.SimpleTcpCluster”/>
    –>

    <!– The request dumper valve dumps useful debugging information about
    the request and response data received and sent by Tomcat.
    Documentation at: /docs/config/valve.html –>
    <!–
    <Valve className=”org.apache.catalina.valves.RequestDumperValve”/>
    –>

    <!– 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”/>

    <!– 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”>

    <!– SingleSignOn valve, share authentication between web applications
    Documentation at: /docs/config/valve.html –>
    <!–
    <Valve className=”org.apache.catalina.authenticator.SingleSignOn” />
    –>

    <!– Access log processes all example.
    Documentation at: /docs/config/valve.html –>
    <!–
    <Valve className=”org.apache.catalina.valves.AccessLogValve” directory=”logs”
    prefix=”localhost_access_log.” suffix=”.txt” pattern=”common” resolveHosts=”false”/>
    –>
    <!– ********************* only nest is added before the host ********************* –>
    <Context path=”/DBTest” docBase=”DBTest” debug=”5″ reloadable=”true” crossContext=”true”>
    <!– maxActive: Maximum number of dB connections in pool. Make sure you
    configure your mysqld max_connections large enough to handle
    all of your db connections. Set to 0 for no limit.
    –>

    <!– maxIdle: Maximum number of idle dB connections to retain in pool.
    Set to -1 for no limit. See also the DBCP documentation on this
    and the minEvictableIdleTimeMillis configuration parameter.
    –>

    <!– maxWait: Maximum time to wait for a dB connection to become available
    in ms, in this example 10 seconds. An Exception is thrown if
    this timeout is exceeded. Set to -1 to wait indefinitely.
    –>

    <!– username and password: MySQL dB username and password for dB connections –>

    <!– driverClassName: Class name for the old mm.mysql JDBC driver is
    org.gjt.mm.mysql.Driver – we recommend using Connector/J though.
    Class name for the official MySQL Connector/J driver is com.mysql.jdbc.Driver.
    –>

    <!– url: The JDBC connection url for connecting to your MySQL dB.
    The autoReconnect=true argument to the url makes sure that the
    mm.mysql JDBC Driver will automatically reconnect if mysqld closed the
    connection. mysqld by default closes idle connections after 8 hours.
    –>

    <Resource name=”jdbc/TestDB” auth=”Container” type=”javax.sql.DataSource”
    maxActive=”100″ maxIdle=”30″ maxWait=”10000″
    username=”root” password=”amir” driverClassName=”com.mysql.jdbc.Driver”
    url=”jdbc:mysql://localhost:3306/javatest?autoReconnect=true”/>

    </Context>

    </Host>
    </Engine>
    </Service>
    </Server>

    so many thnaks

    Amir

    #275611 Reply

    vvvngo
    Participant

    What version of Tomcat are you using?

    #275628 Reply

    amir55
    Participant

    This message has not been recovered.

    #276985 Reply

    Hemant
    Member

    This message has not been recovered.

    #276990 Reply

    amir55
    Participant

    This message has not been recovered.

    #277116 Reply

    Hemant
    Member

    This message has not been recovered.

    #283653 Reply

    brajen
    Member

    This message has not been recovered.

Viewing 7 posts - 1 through 7 (of 7 total)
Reply To: tomact 6 and mysql configuration problem in Myeclipse 6

You must be logged in to post in the forum log in