Since you are running it in servlet , you need to have the jar accessible by the servlet container. You either include the connector as part of your application war or put it as part of the servlet container's extended library and datasource management stuff, if it has one. The second part is totally depend on the container that you have.
The others are right about making the driver JAR available to your servlet container. My comment was meant to suggest that you verify from the command line whether the driver itself is intact. Rather than an empty main , try something like this, adapted from the included documentation:. On your platform, you need to use ; as the path separator, as discussed here and here. Place mysql-connector-java Your problem will be solved.
Then place all files that are present in the folder containing bin to C:Program Filesmysqlmysql server5. Ok, after had the same issue and after reading some answers here and other places. Each time you start this Tomcat server in Eclipse, those files will overwrite the corresponding files in the Tomcat installation. Any changes made locally to those files in the installation would be lost. This implies there will be problems trying to make permanent changes to the Tomcat server using the Manager or Admin Web applications available for Tomcat.
An additional disadvantage is that any custom options added to the Tomcat server's launch configuration within Eclipse will need to be duplicated in the Tomcat batch scripts if the Tomcat server is to be run outside of Eclipse.
The Tomcat server's configuration can be changed using the server editor. This editor is opened by displaying the context menu for the server in the Servers view and selecting Open. Double-clicking on the server in the Servers view also opens this editor. The editor contains two pages, Overview and Modules , which display different portions of the Tomcat configuration. You switch between these pages by clicking on their respective tabs at the bottom of the editor.
The configuration for a Tomcat server includes a number of WTP specific options and settings, which appear on the Overview page. In WTP 1. More importantly, the configuration also includes the set of Tomcat configuration files found in the folder specified by the Configuration Path field shown in the General section of this page.
This server editor has the ability to make a limited set of modifications to the server. Modifications to the other files and other modifications to server. The Modules page displays the contexts that the Tomcat server is configured to serve.
These contexts include Dynamic Web Projects that have been added to the server as well as contexts manually added using this page or modifying server.
Note: As a convenience, the launch configuration Properties dialog for the Tomcat server may be opened from the Overview page of the server editor by clicking on the Open launch configuration link found in the General section.
The Java start-up environment for a Tomcat server is displayed in the launch configuration Properties dialog for the server. The most straightforward way to open this dialog is to first open the server editor for the Tomcat server. Once the server editor is open, click the Open launch configuration link found in the General section of the Overview page.
This approach has the advantage of creating the launch configuration if it is a new server that has not yet been started for the first time. It is found in the General section of the Overview page. If checked, a separate instance is used. If not checked, the instance from the Tomcat installation is used.
The default is checked. It is best to change this option immediately after creating the server, or at least while no projects have been added to the server. Choosing the Use workspace metadata does not modify Tomcat installation will use a separate instance and is equivalent to enabling WTP 1. In addition, the Server Path field displays the location of this separate instance relative to your workspace. A separate instance is also created if you choose Use custom location does not modify Tomcat installation and specify your desired location in the Server Path field.
Choosing Use Tomcat installation takes control of Tomcat installation uses the instance from your Tomcat installation and is equivalent to disabling WTP 1.
Note that changes to the settings in the Server Locations section can only occur when there are no projects present on the server. All the settings in the section are disabled if this is not the case. Remove all of the projects and publish the server to enable the settings in this section. The instance location is displayed in the Server path field.
Relative paths are relative to your workspace. Examine the contents of the VM Arguments field. The value for the catalina. To find this location, see the previous question. The Servers project is created, along with a subfolder associated with the Tomcat server, to hold copies of the server.
This makes is easier to make modifications to those files. It also allows these files to be 'working copies', separate from the copies that are found in the conf directory of the instance location.
This avoids the possibility of interfering with a running Tomcat server if modifications are made to the files in the Servers project while the server is running. This Servers project must remain open for Tomcat servers to function properly. Be aware that use of the Close Unrelated Projects command may unintentionally close the Servers project. Reopen the Servers project if this occurs. From the Servers view, open the server editor for the desired Tomcat server.
In the General section of the Overview page, the Configuration path field displays the path to the associated folder in the workspace that contains the Tomcat configuration files. The default name for this folder is the name of the server with '-config' appended. Publish updates the server instance with any server configuration changes, changes related to projects added or removed from the server, and content changes in projects already added to the server.
This includes copying the server configuration files found under the associated subfolder of the Servers project to the server's instance location. In the case of server. For an example of an 'adjustment', see this question. Note the configuration files under the subfolders in the Servers project are not used directly by running servers. The running server uses copies of these files.
This implies that any manual changes made to the copy will be overwritten the next time the server is published. Also note that all files found in the subfolder of the Servers project will be copied. If you have imported additional files there, such as logging. A couple of files you may wish to import are catalina. WTP 2. The support for individual context XML files is not supported for Tomcat 3. For Tomcat 5.
This behavior is enabled by checking the Publish module contexts to separate XML files option in the Server Options section of the Tomcat server editor. Note that only contexts for added projects will be written to separate XML files.
Manually added contexts in server. Note that if the project is removed from the server, this configuration will be lost. You can save a copy of the configuration in some file in your project if you want to persist this information. The purpose of connection timeout is to keep invalid requests from tying up the server. Unfortunately, sometimes the server can tie up the server, and blame it on the request.
This results in valid requests timing out. The most common reason that this occurs is JVM garbage collection. The JVM temporarily freezes all its running processes when it collects garbage, which can result in request timeout.
There are two ways to mitigate this issue. The first and best method is to properly tune your JVM's garbage collection so that it does not interfere with Tomcat. There is really no reason your garbage collection should take more than a second if you have configured your JVM correctly for your server load and applications. The second thing that can cause this problem is an improperly configured timeout threshold, which is configured in the Resource element with the "maxWait" attribute.
Typically, this should be set to around seconds to avoid any problems, although this varies by situation. How JDBC works JDBC provides an abstraction layer between Java applications and database servers, so that an application's code does not need to be altered in order for it to communicate with multiple database formats. Preventing bottlenecks using DBCP The problem with using JDBC in a high-load environment is that it can become overwhelmed with requests, and begin dropping them or delaying them, causing a bottleneck in the architecture that slows down the entire application.
The Java Servlet specification that Tomcat implements requires resources to be declared in two places: As a resource in your application's context element. This will direct Tomcat to create the resource when the application launches. Alternatively, if you want the database to be available to multiple applications, you can provide this information in Tomcat's server. We'll cover both situations.
This provides a references to your database that does not contain information specific to your servers, so that the application can easily be ported to another server environment. Step 2a: JDBC resource configuration The Resource Element defines server-specific information about your database, including URL, database type , driver, and authentication information. And the IDE is not complaining about anything missing.
It's just when I try to start the server. I added the mysql-connector-java And I made sure the Server is referencing that folder. I also made sure it is not in the webapp's lib folder. This is how I always did it before. I assume it's a driver thing. But maybe not?
Can someone please suggest a good way to debug this? Because, I'm stumped Password is correct and can connect from the IDE no problem. It is with great embarrassment that I admit I forgot to copy the web.
Sitting so close Sometimes you can't see the forest for the trees. If you double-click your Tomcat instance under Eclipse it will take you to the setting for the server, and from there you can select the "Open Launch Configuration" option where you can add your driver jar to the bootstrap classpath. That said, I don't think the problem is a missing driver as that generally results in a "Class not found" exception.
Check your logs carefully and maker sure you're not getting any errors.
0コメント