After some more testing, I have determined that I can remove the user
name and password from context.xml in Tomcat 5.5.4, and it still
works. Removing the entire Resource tag, however, causes it to crash
out, as it should. This means that Tomcat 5.5.4 needs the connection
information in
After some more testing, I have determined that I can remove the user
name and password from context.xml in Tomcat 5.5.4, and it still
works. Removing the entire Resource tag, however, causes it to crash
out, as it should. This means that Tomcat 5.5.4 needs the connection
information in
Its seems you have correctly defined the datasource,
but it is not linked to your application. In the
server.xml your application should be defined as a
context and in the context you have to specify that
the global resource defined earlier is available to
this application.
Look at resource-ref
Hi,
I am not exactly sure what you meant by you don't
have to do that ? For example, how would a class
differentiate between
org.apache.commons.dbcp.BasicDataSourceFactory and
org.apache.tomcat.dbcp.dbcp.BasicDataSourceFactory
without doing anything? Off course the import
declarations have to
On Mon, Mar 14, 2005 at 08:55:35AM -0800, sven morales wrote:
:I am not exactly sure what you meant by you don't
: have to do that ? For example, how would a class
: differentiate between
: org.apache.commons.dbcp.BasicDataSourceFactory and
: org.apache.tomcat.dbcp.dbcp.BasicDataSourceFactory
On Mon, 8 Nov 2004 16:07:26 -0800, Mark Fleischman
[EMAIL PROTECTED] wrote:
Hello,
After upgrading from Tomcat 5.0.27 to Tomcat 5.5.4 my JNDI datasources are
not resolving in 5.5.4
The configuration of the datasources was too verbose, and has been
changed in this release. Look in the JNDI
Hi,
The ResourceParams nested elements are history, it's all in the Resource
element now. See the new configuration page at
http://jakarta.apache.org/tomcat/tomcat-5.5-doc/jndi-datasource-examples
-howto.html.
Yoav Shapira http://www.yoavshapira.com
-Original Message-
From: Mark
Thanks Rémy Yoav!
Mark
Quoting Shapira, Yoav [EMAIL PROTECTED]:
Hi,
The ResourceParams nested elements are history, it's all in the Resource
element now. See the new configuration page at
http://jakarta.apache.org/tomcat/tomcat-5.5-doc/jndi-datasource-examples
-howto.html.
Yoav
java:comp/env is the default namespace defined by JNDI. The call to
lookup() with this as an argument is returning an instance of a context
corresponding to that namespace, which you need to do a further lookup
for your specific resource.
On a related note, I'm pretty sure you could condense
I'll give it a shot...
All JNDI resource lookups occur relative to some context. The code you
posted first gets the default initial context, then looks for a resource
named java:comp/env relative to that default context. It then gets a
reference to a DataSource that exists within the context
On Sat, Nov 06, 2004 at 07:05:12PM -0800, Eric Wulff wrote:
I just returned from working on a tutorial at sun which I was inspired
to go over based on my lack of understanding of the code snippet
below. I'm trying to fully understand what's going on. Docs state
that the code...
helpful somewhat... at least in helping me narrow my question. So
what is this java:comp/env? What exactly is being returned based on
this string passed to lookup()?
Eric
On Sat, 06 Nov 2004 23:35:34 -0500, Frank W. Zammetti
[EMAIL PROTECTED] wrote:
I'll give it a shot...
All JNDI
there can be two things to change: if ur using tc5 you can change your
dbcp resource via yourcustomapp.xml (conf/catalina/localhost/)
Resource name=jdbc/yourcustomname auth=Container
type=javax.sql.DataSource/
ResourceParams name=jdbc/yourcustomname
parameter
and then in your web.xml
Hi,
Read the section on Automatic Application Deployment in the Tomcat docs,
and you will see that these are simply multiple options to do the same
thing. Which one is best depends on your needs and preferences, but
they're not that different from each other.
Yoav Shapira
Millennium Research
Yoav Shapira,
thanks.
After reading Tomcat docs and some books I realized the context issue.
Valter
- Original Message -
From: Shapira, Yoav [EMAIL PROTECTED]
To: Tomcat Users List [EMAIL PROTECTED]
Sent: Wednesday, August 04, 2004 2:57 PM
Subject: RE: Datasource Definition
Hi
Hello!
just restart tomcat and your done... =)
aris
-Original Message-
From: Bussie, Andre D [mailto:[EMAIL PROTECTED]
Sent: Wed 7/28/2004 9:35 PM
To: [EMAIL PROTECTED]
Cc:
Subject:DataSource
By adding the resource-ref tag to the web.xml and including the
Hi,
I think the exception already told you what going wrong
according to:
http://jakarta.apache.org/tomcat/tomcat-5.0-doc/jndi-resources-howto.html
the url should be:
parameter
nameurl/name
valuejdbc:HypersonicSQL:database/value
/parameter
so if your database call testDB
the url
Devlin,
From my understanding, this is not a function of Tomcat. The appending is
MySQL looking up who is sending. If you use the MySQL prompt to access MySQL
it will only prompt you for a user name and password, but MySQL check for
the location. Try logging in to MySQL directly on the machine
Snotman,
For an example.
Search the archives for the thread Servlets with JDBC connectivity.
Look for the messages from me.
Doug Parsons
- Original Message -
From: Snotman [EMAIL PROTECTED]
To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Sent: Friday, March 05, 2004 1:08 AM
Subject: RE
i goofed
i forgot to put 2 lines in my server.xml file.
inside the global naming resources
Resource auth=Container description=User database that can be updated
and saved name=UserDatabase type=org.apache.catalina.UserDatabase/
Resource auth=Container name=jdbc/TSRDATA type=javax.sql.DataSource/
Daniel,
I have not been able to get Global Resources to work. I played around
with them for a while, but I decided to cheat by defining my resources
under the Host element in the DefaultContext. Below is a stripped
down example. I also define a context.xml and place it under webapp
This sounds as anything but a DataSource problem.
What are you using NetBeans web monitor module for?
Antonio Fiol
Nathan Maves wrote:
Hey guys just joined the alias today!
I am getting the following error from my web app.
NotifyUtil::java.net.ConnectException: Connection refused
Means
I was not aware that I was :)
I have turned this off in net beans. I just use this for my
development and create a war file with it. I just drop this war in the
webapps dir of tomcat. Now I can't seem to get rid of it!
Nathan
On Feb 20, 2004, at 1:55 PM, Antonio Fiol Bonnín wrote:
This
This is probably not the only way to accomplish what you want, but a simple one to
code for.
1)Define your DataSource resource in GlobalNamingResources of conf/server.xml.
2)Add a ResourceLink to the DataSource in the application context file in
conf/Catalina/yourserver/yourapp.xml
This way
Hi
From: Antonio Fiol Bonnin [mailto:[EMAIL PROTECTED]
Sent: 11 2004 . 11:39
Subject: Re: Datasource - OK in app context - Fails in Global context
So, could someone summarize for me the different ways of
creating a JDBC
DataSource in Tomcat?
I will start the summary, so that it's
, if not, the workaround works just fine.
Bruno.
-Original Message-
From: ext Keshav Sarin [mailto:[EMAIL PROTECTED]
Sent: Friday, January 09, 2004 4:23 PM
To: [EMAIL PROTECTED]
Subject: RE: Datasource - OK in app context - Fails in Global context
There's a catch though
In TC 4.x, if you put a app
]
Subject: RE: Datasource - OK in app context - Fails in Global context
There's a catch though
In TC 4.x, if you put a app context entry in the server.xml, the app
doesn't get reloaded even if the war is overwritten or the app
directory
is deleted or the server is restarted. The fully
-
From: ext Keshav Sarin [mailto:[EMAIL PROTECTED]
Sent: Monday, January 12, 2004 9:25 AM
To: [EMAIL PROTECTED]
Subject: RE: Datasource - OK in app context - Fails in Global context
When I tested 5.0 for auto deployment, the datasource JNDI context was
no longer available to the application
: Friday, January 09, 2004 4:23 PM
To: [EMAIL PROTECTED]
Subject: RE: Datasource - OK in app context - Fails in Global context
There's a catch though
In TC 4.x, if you put a app context entry in the server.xml, the app
doesn't get reloaded even if the war is overwritten or the app
directory
-effects.
-Original Message-
From: ext Keshav Sarin [mailto:[EMAIL PROTECTED]
Sent: Monday, January 12, 2004 11:26 AM
To: [EMAIL PROTECTED]
Subject: RE: Datasource - OK in app context - Fails in Global context
On a different topic, do you have the database driver under WEB-INF/lib
or common
So, could someone summarize for me the different ways of creating a JDBC
DataSource in Tomcat?
I will start the summary, so that it's easier to correct/complete.
Please fill in the gaps ;-)
1. Have the DataSource defined in your application's context.
That way, if you have two apps, you
Have you defined a reference to the global resource in the
ResourceLink element of the application context ?
[EMAIL PROTECTED] 01/09/04 10:38AM
I have an Oracle JDBC datasource that I defined in the Tomcat5 context
for an application (conf/Catalina/localhost/nwg.xml). Works fine,
context file
[mailto:[EMAIL PROTECTED]
Sent: Friday, January 09, 2004 3:22 PM
To: [EMAIL PROTECTED]; Melloni Bruno (Nokia-BI/Dallas)
Subject: Re: Datasource - OK in app context - Fails in Global context
Have you defined a reference to the global resource in the
ResourceLink element of the application context
hair on this issue for almost a month.
Bruno
-Original Message-
From: ext Keshav Sarin [mailto:[EMAIL PROTECTED]
Sent: Friday, January 09, 2004 3:22 PM
To: [EMAIL PROTECTED]; Melloni Bruno (Nokia-BI/Dallas)
Subject: Re: Datasource - OK in app context - Fails in Global context
Have you
-
From: ext Keshav Sarin [mailto:[EMAIL PROTECTED]
Sent: Friday, January 09, 2004 3:22 PM
To: [EMAIL PROTECTED]; Melloni Bruno (Nokia-BI/Dallas)
Subject: Re: Datasource - OK in app context - Fails in Global context
Have you defined a reference to the global resource in the
ResourceLink element
Howdy,
You need a ResourceParam for the DB URL. It looks like your driver name
me be the URL?
Yoav Shapira
Millennium ChemInformatics
-Original Message-
From: Jim Kennedy [mailto:[EMAIL PROTECTED]
Sent: Wednesday, November 26, 2003 12:30 PM
To: Tomcat Users List
Subject: Datasource
[EMAIL PROTECTED]
Sent: Wednesday, November 26, 2003 12:41 PM
Subject: RE: Datasource problem upgrading from 4.06
Howdy,
You need a ResourceParam for the DB URL. It looks like your driver name
me be the URL?
Yoav Shapira
Millennium ChemInformatics
-Original Message-
From: Jim Kennedy
Howdy,
http://jakarta.apache.org/tomcat/tomcat-4.1-doc/jndi-datasource-examples
-howto.html
Yoav Shapira
Millennium ChemInformatics
-Original Message-
From: Jim Kennedy [mailto:[EMAIL PROTECTED]
Sent: Wednesday, November 26, 2003 12:47 PM
To: Tomcat Users List
Subject: Re: Datasource
: Shapira, Yoav [EMAIL PROTECTED]
To: Tomcat Users List [EMAIL PROTECTED]
Sent: Wednesday, November 26, 2003 12:57 PM
Subject: RE: Datasource problem upgrading from 4.06
Howdy,
http://jakarta.apache.org/tomcat/tomcat-4.1-doc/jndi-datasource-examples
-howto.html
Yoav Shapira
Millennium ChemInformatics
I have a datasource configured with the name 'jdbc/TestDB' as in
http://jakarta.apache.org/tomcat/tomcat-4.1-doc/jndi-datasource-examples-howto.html.
I wanna use this datasource in a JSP test using 'jakarta/dbtags'
taglib. What is the name I should use for the 'dataSource' attribute
of the
Would you mind run netstat to see what kind of connection they are, e.g.
port, host, status?
-Original Message-
From: Matt Raible [mailto:[EMAIL PROTECTED]
Sent: October 3, 2003 11:52 AM
To: 'Tomcat Users List'
Subject: RE: Datasource connections not released when reloading context
I
]
Sent: Friday, October 03, 2003 9:52 AM
To: 'Tomcat Users List'
Subject: RE: Datasource connections not released when reloading context
I tried changing the removeAbandonedTimeout to value1/value and then
to test it was working - here's what I did.
1. My app opens 2 connections to MySQL
On Thu, 2003-10-02 at 01:12, Peter Harrison wrote:
On Thu, 02 Oct 2003 01:01, Tuna Vardar wrote:
What can be the cause for the exception I mentioned above? Any comments?
Sounds very similar to the issue I had when trying to move to 4.1.27. When I
moved from 4.0.4 to 4.1.27 the exact
Sorry, but I didn't see which datasource you were using. With DBCP, you
have these optional parameters:
!-- abandoned dB connections are removed and recycled --
parameter
nameremoveAbandoned/name
valuetrue/value
/parameter
!-- set the number of seconds a dB connection has been idle
not work on Tomcat 4.1.27/WinXP/JDK 1.4.2.
Thanks,
Matt
-Original Message-
From: Adam Hardy [mailto:[EMAIL PROTECTED]
Sent: Friday, October 03, 2003 1:22 AM
To: Tomcat Users List
Subject: Re: Datasource connections not released when reloading context
Sorry, but I didn't see which datasource
-Original Message-
From: Matt Raible [mailto:[EMAIL PROTECTED]
Sent: Friday, October 03, 2003 9:52 AM
To: 'Tomcat Users List'
Subject: RE: Datasource connections not released when reloading context
I tried changing the removeAbandonedTimeout to value1/value and then
to test it was working - here's
On Wed, Oct 01, 2003 at 11:37:39AM -0500, Matt Raible wrote:
I already do this, but when I reload my context, I get two database
connections, rather than one. So each time I reload, I get an additional
connection - eventually resulting in an OutOfMemory Error (which I'm
attributing to this)
to RTFM.
Matt
-Original Message-
From: Phillip Qin [mailto:[EMAIL PROTECTED]
Sent: Monday, September 29, 2003 8:04 AM
To: 'Tomcat Users List'
Subject: RE: Datasource connections not released when reloading context
- to release your DB connections when your app is shutdown or reloaded
, 2003 8:04 AM
To: 'Tomcat Users List'
Subject: RE: Datasource connections not released when reloading context
- to release your DB connections when your app is shutdown or reloaded:
implement destroy method in your servlet class to close them.
- to prevent connections getting exhausted, use evictor
and nullify the data source.
-Original Message-
From: Adam Hardy [mailto:[EMAIL PROTECTED]
Sent: October 1, 2003 5:20 AM
To: Tomcat Users List
Subject: Re: Datasource connections not released when reloading context
actually that doesn't really close them, since it's a connection pool
: Adam Hardy [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 01, 2003 3:20 AM
To: Tomcat Users List
Subject: Re: Datasource connections not released when reloading context
actually that doesn't really close them, since it's a connection pool,
but it tells the connection pool that they're free
]
Sent: October 1, 2003 12:38 PM
To: 'Tomcat Users List'
Subject: RE: Datasource connections not released when reloading context
I already do this, but when I reload my context, I get two database
connections, rather than one. So each time I reload, I get an additional
connection - eventually
On Thu, 02 Oct 2003 01:01, Tuna Vardar wrote:
What can be the cause for the exception I mentioned above? Any comments?
Sounds very similar to the issue I had when trying to move to 4.1.27. When I
moved from 4.0.4 to 4.1.27 the exact same issue arose. If you put everything
under a context it
- to release your DB connections when your app is shutdown or reloaded:
implement destroy method in your servlet class to close them.
- to prevent connections getting exhausted, use evictor if your use commons
pooling and dbcp.
-Original Message-
From: Jose Alfonso Martinez [mailto:[EMAIL
To: 'Tomcat Users List'
Subject: RE: Datasource connections not released when reloading context
- to release your DB connections when your app is shutdown or reloaded:
implement destroy method in your servlet class to close them.
- to prevent connections getting exhausted, use evictor if your use commons
You can have a context for your application defined in a seperate xml
file but not in the web.xml. If you read the dtd for the web.xml you'll
see that this is not allowed.
Simply copy your context that works and paste into a new xml file, which
has the same name as your webapp.
So if you had
Tomcat binds the DataSource object in JNDI to jdbc/PubsDb, but relative to
java:comp/env and not the root of the context.
See the code examples at
http://jakarta.apache.org/tomcat/tomcat-4.1-doc/jndi-datasource-examples-howto.html
-chris
-Original Message-
From: Alexey Tyurin
Are you using a finally bock to close your connections? You might be
reaching the maximum connections allowed in the pool for DBCP. Please
provide an example of a query statement where you do try/catch/finally. If
you are not checking if your connections are not null and then making a
last
]
Sent: Tuesday, April 01, 2003 7:39 AM
To: Tomcat Users List
Subject: Re: DataSource misconfigured?
Are you using a finally bock to close your connections? You might be
reaching the maximum connections allowed in the pool for DBCP. Please
provide an example of a query statement where you do try
Hi,
Marco Rossi wrote:
Hi,
it's possible to configure Tomcat 4.1.24 to use another DataSource implementation, and
not DBCP?
yes. Tomcat can be configured to use another DataSource than DBCP by modifying its
server.xml file
(see JNDI DataSource HOWTO[1]).
AS an example, I've done it to use a
It is just a scope thing.
-Original Message-
From: Jon Archer [mailto:[EMAIL PROTECTED]
Sent: March 4, 2003 6:49 PM
To: [EMAIL PROTECTED]
Subject: DataSource resource in GlobalNamingResources
I see a lot of to and fro over setting up database connection pooling as
a JNDI resource. I
On Tue, 2003-03-04 at 19:50, Jacob Kjome wrote:
Look in server.xml in recent tomcat-4.1.x versions ( I have 4.1.19
here). There is an entry in GlobalNamingResources called
UserDatabase
There's your example.
Jake
Fabulous, thanks Jake. That worked a treat :-)
Look in server.xml in recent tomcat-4.1.x versions ( I have 4.1.19
here). There is an entry in GlobalNamingResources called UserDatabase
GlobalNamingResources
!-- Editable user database that can also be used by
UserDatabaseRealm to authenticate users --
Resource
Georges,
For the documentation of JNDI Datasource HOW-TO, their files jar should be
located in $CATALINA_HOME/common/lib. This road should be put in CLASSPATH of the
system also.
*** REPLY SEPARATOR ***
On 26/2/2003 at 13:31 Georges Roux wrote:
Hi,
I run under Linux,
Sebastião Carlos Santos wrote:
Georges,
For the documentation of JNDI Datasource HOW-TO, their files jar should be located in $CATALINA_HOME/common/lib. This road should be put in CLASSPATH of the system also.
*** REPLY SEPARATOR ***
On 26/2/2003 at 13:31 Georges Roux wrote:
I'm curious as to why you're asking this question. You should be using the
connection pool according to the documentation provided, because that is how
it is intended to be used. That is...
void doPost(...)
{
InitialContext ic = new InitialContext();
Context jdbcCtx = (Context)
So so Sean.
Then this is a way of tomcat implements the concept of connection pools.
Right, i only wanted have certain.
Thanks for all.
- Original Message -
From: Sean Dockery [EMAIL PROTECTED]
To: Tomcat Users List [EMAIL PROTECTED]
Sent: Monday, February 03, 2003 16:25
Subject: RE
:
net.mn Subject: RE: DataSource error (DBCP)
12/23
Dorjgotov To: Tomcat Users List [EMAIL PROTECTED]
galbayar@mobi cc:
net.mn Subject: RE: DataSource error (DBCP
pengtuck@makm To: Tomcat Users List
[EMAIL PROTECTED]
al.net cc:
Subject: Re: DataSource error
:
Subject: Re: DataSource error (DBCP)
12/23/2002
08:23 AM
while executing ... http://195.54.247.110:8080/DBTest/test.jsp
getting the error message
org.apache.jasper.JasperException: Unable to compile class for JSP
An error occurred at line: 6 in the jsp file: /test.jsp
Generated servlet error:
[javac] Compiling 1 source file
tomcat 4.x doesn't like classes in the root directory - place that class
into a package and then try again.
- Original Message -
From: [EMAIL PROTECTED]
To: Tomcat Users List [EMAIL PROTECTED]
Sent: Monday, December 23, 2002 12:42 AM
Subject: Re: DataSource error (DBCP)
while
Users List [EMAIL PROTECTED]
To: Tomcat Users List [EMAIL PROTECTED]
Subject: Re: DataSource error (DBCP)
Date: Mon, 23 Dec 2002 08:42:05 +
while executing ... http://195.54.247.110:8080/DBTest/test.jsp
getting the error message
org.apache.jasper.JasperException: Unable to compile class
that's cool!!! worked.
bringing attention to my old problem like i'm unable to compile DBTest.java
(i compiled the same in another machine where oracle 9i is running, and
copied to the machine where tomcat is running :))
I tried to compile DBTest.java and ended up an error
Type
:
12/23/2002 02:53 Subject: Re: DataSource error (DBCP)
PM
Please respond
Did you import javax.sql.*; ?? DataSource is part of the J2EE package. Just
an extension to the normal java.sql package
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, 24 December 2002 2:20 AM
To: Tomcat Users List
Subject: Re: DataSource error (DBCP
copy mysql jdbc driver to tomcat/common/lib directory
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Monday, December 23, 2002 3:09 AM
To: [EMAIL PROTECTED]
Subject: DataSource error (DBCP)
hi all,
i'm new to tomcat... if my queries are foolish...pl
.
-Original Message-
From: Manavendra Gupta [mailto:[EMAIL PROTECTED]]
Sent: Friday, December 06, 2002 9:19 PM
To: Tomcat Users List
Subject: RE: DataSource problem.
I haven't been able to solve this yet... but was wondering if tomcat logs
somewhere that the Resource Manager added a new resource
Tried the same with a simplistic jsp page:
%@ page import=java.sql.*, javax.sql.*, javax.naming.* %
HTML
BODY
%
out.println(hello);
Context initCtx = new InitialContext();
Context envCtx = (Context) initCtx.lookup(java:comp/env);
DataSource ds = (DataSource) envCtx.lookup(jdbc/rtidb);
Connection
List
Subject: RE: DataSource problem.
Tried the same with a simplistic jsp page:
%@ page import=java.sql.*, javax.sql.*, javax.naming.* %
HTML
BODY
%
out.println(hello);
Context initCtx = new InitialContext();
Context envCtx = (Context) initCtx.lookup(java:comp/env);
DataSource ds = (DataSource
*deep breath.
I'm lost about this... would anyone take a shot at helping me?
Thanks
Manav.
-Original Message-
From: Manavendra Gupta [mailto:[EMAIL PROTECTED]]
Sent: Friday, December 06, 2002 9:19 PM
To: Tomcat Users List
Subject: RE: DataSource problem.
I haven't been able to solve
parameternameUser/namevaluesa/value/parameter
should be
parameternameusername/namevaluesa/value/parameter
Also, I'm not sure if the names are case sensitive. I suggest using All
lower case just to be sure.
Jake
At 05:23 AM 12/3/2002 -0800, you wrote:
Hi
i spent 7 hours trying to figure
I could be wrong but isnt
parameternameusername/namevaluesa/value/parameter
specific to dbcp .BasicDataSourceFactory ? I am using
SQLServerDataSource and according the docs
they specify a param called User whose value should be a user name.
Jacob Kjome wrote:
DBCP ultimately wraps your DataSource object. So, the config is specific
to DBCP, not to your implementation of your DataSource. Someone please
correct me if I am wrong.
Jake
At 06:32 AM 12/3/2002 -0800, you wrote:
I could be wrong but isnt
parameternameusername/namevaluesa/value/parameter
Jacob Kjome wrote:
DBCP ultimately wraps your DataSource object.
no it doesnt, if you specify a different factory class DBCP plays no role.
So, the config is specific to DBCP, not to your implementation of your
DataSource. Someone please correct me if I am wrong.
yes, the examples
i will pass onto you what i learnt from Craig, and its check common-dbcp
implementation . you will be able to set up your cloudscape pretty soon.
i just finished making some changes to my datasource class and factory
class and it works fine with tomcat. Took me few hours, YMMV , but i
learnt
On Tue, 3 Dec 2002, Peng Tuck Kwok wrote:
Date: Tue, 03 Dec 2002 12:09:42 +0800
From: Peng Tuck Kwok [EMAIL PROTECTED]
Reply-To: Tomcat Users List [EMAIL PROTECTED]
To: Tomcat Users List [EMAIL PROTECTED]
Subject: Datasource and Web.xml
If a web application uses a jndi datasource, should
Thanks craig. I'll look up the ResourceLink element.
Craig R. McClanahan wrote:
On Tue, 3 Dec 2002, Peng Tuck Kwok wrote:
Date: Tue, 03 Dec 2002 12:09:42 +0800
From: Peng Tuck Kwok [EMAIL PROTECTED]
Reply-To: Tomcat Users List [EMAIL PROTECTED]
To: Tomcat Users List [EMAIL PROTECTED]
On Mon, 2 Dec 2002, maninder s batth wrote:
Date: Mon, 02 Dec 2002 20:41:10 -0800
From: maninder s batth [EMAIL PROTECTED]
Reply-To: Tomcat Users List [EMAIL PROTECTED]
To: Tomcat Users List [EMAIL PROTECTED]
Subject: Datasource and Initial Context
hi i am using my own DataSource class
Remove the sql validation parameter in your datasource definition or
give it a table to select from.
Daniel Tamborelli Alvarenga wrote:
I've installed Tomcat 4.1 on Windows 2000 and MySQL
I've configured the Data Source in the server.xml and that's ok... but when
I try to
get the connection
Ok... now it's working fine...
Thank you very much...
:)
Daniel Tamborelli Alvarenga
- Original Message -
From: Kwok Peng Tuck [EMAIL PROTECTED]
To: Tomcat Users List [EMAIL PROTECTED]
Sent: Sunday, November 24, 2002 9:08 PM
Subject: Re: DataSource problem
Remove the sql validation
You must define the DataSource in your web.xml too. For example:
resource-ref
descriptionMy datasource/description
res-ref-namemyjndi/res-ref-name
res-typejavax.sql.DataSource/res-type
res-authContainer/res-auth
/resource-ref
Regards.
-Mensaje original-
De: Lindomar
: Miguel Angel Mulero Martinez [EMAIL PROTECTED]
To: Tomcat Users List [EMAIL PROTECTED]
Sent: Monday, September 30, 2002 11:27 AM
Subject: RE: Datasource
You must define the DataSource in your web.xml too. For example:
resource-ref
descriptionMy datasource/description
res-ref
Try this:
DataSource ds = (DataSource) ic.lookup(java:comp/env/myjndi);
but you should use this (note the /jdbc before /myjndi):
DataSource ds = (DataSource) ic.lookup(java:comp/env/jdbc/myjndi);
and bind your datasource to the name jdbc/myjndi.
All environment resources are bind to the
I've had the exact same problem with for the past couple of weeks, only with
the Microsoft Type4 SQL Server driver. Everything seems to work great, and
the Context is definitely found, but the DataSource is always null.
I haven't been able to find a solution, the closest I came was going to
-Original Message-
From: Turner, John [mailto:[EMAIL PROTECTED]]
Sent: Friday, July 19, 2002 5:05 AM
To: 'Tomcat Users List'
Subject: RE: Datasource JNDI lookup failing
I've had the exact same problem with for the past couple of weeks, only with
the Microsoft Type4 SQL Server driver
: Friday, July 19, 2002 8:16 AM
To: 'Tomcat Users List'
Subject: RE: Datasource JNDI lookup failing
I had a similar problem, but i was using classes12.zip that is from Oracle.
I tried every option, but it didnt seem to work. Then at the end upgraded to
tc 4.1.7. TC 4.1.7 had all the included files
: RE: Datasource JNDI lookup failing
I had a similar problem, but i was using classes12.zip that is from Oracle.
I tried every option, but it didnt seem to work. Then at the end upgraded to
tc 4.1.7. TC 4.1.7 had all the included files, and got the DataSource and
the connection.
My advice, upgrade
Maier Holger wrote:
Wouldn't it be better to read the
data source once in a singleton class
and then just get it back, i.e.
I did the same thing with my application where I did a key/value storage
object that was a singleton in my ServletContext. I did notice a slight
speed improvement and I've
1 - 100 of 113 matches
Mail list logo
