Hi Mark,
On Wed, May 25, 2016 at 4:56 AM, Mark Thomas wrote:
> On 24/05/2016 23:23, Woonsan Ko wrote:
>> Hi,
>>
>> Since 8.0, I think we should use maxTotal instead of maxActive and
>> maxWaitMillis instead of maxWait. [1,2]
>> However, if I use maxTotal for instance, the jmx console doesn't show
On 24/05/2016 23:23, Woonsan Ko wrote:
> Hi,
>
> Since 8.0, I think we should use maxTotal instead of maxActive and
> maxWaitMillis instead of maxWait. [1,2]
> However, if I use maxTotal for instance, the jmx console doesn't show
> it but show the old maxActive value (100, probably the default
> v
Hello Mark,
Thanks for the quick reply, we will definitely try this !
Aurelien
On 16/09/2015 09:59, Aurelien Pernoud wrote:
> Hello,
>
> In our Tomcat (7 or 8 doesn't matter) servers we always override many
> parameters among datasources, in each application context file (we deploy
> one context file / application under conf/Catalina/localhost).
>
> Every time I have to set
tober 27, 2012 5:24 PM
To: Tomcat Users List
Subject: Re: JNDI datasource error upgrading from Tomcat 7.0.23 to 7.0.27
Hello,
I am mot familiar with Hibernate or Liferay, but I ran into what appear to
be similar. Look onto the thread titled "
JDBCRealm conection timeout failure on getPasswor
tion.
Bob
-Original Message-
From: Konstantin Kolinko [mailto:knst.koli...@gmail.com]
Sent: Saturday, October 27, 2012 3:28 PM
To: Tomcat Users List
Subject: Re: JNDI datasource error upgrading from Tomcat 7.0.23 to 7.0.27
2012/10/28 Bob Dietrich :
> Greetings,
> I've researched this pro
Hello,
I am mot familiar with Hibernate or Liferay, but I ran into what
appear to be similar. Look onto the thread titled "
JDBCRealm conection timeout failure on getPassword" in thus list. It may help.
Aladin
On Oct 27, 2012, at 6:28 PM, Konstantin Kolinko wrote:
> 2012/10/28 Bob Dietrich :
2012/10/28 Bob Dietrich :
> Greetings,
> I've researched this problem for several days, but I must be doing something
> wrong. I'm trying to upgrade from Tomcat 7.0.23 to 7.0.27 (actually running
> Liferay). I'm getting the following exception when trying to access a
> datasource via Hibernate:
>
>
Fred Janon wrote:
I am looking into using the JNDI/Datasource facility in Tomcat 5.5 to
connect to a mySQL 5.0 database on a Windows 2003 server. Both Tomcat and
mySQL run as services.
What happens if the Tomcat service starts before mySQL? Does Tomcat wait for
a while for the DB to be ready? Doe
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Nicholas,
On 8/7/2009 4:39 PM, Nicholas Sushkin wrote:
> On Friday 07 August 2009 10:53, Christopher Schultz wrote:
>
>> Recently, there was a post on the list regarding connection pool leakage
>> from Tomcat (ref:
>> http://www.nabble.com/Right-way-
On Friday 07 August 2009 10:53, Christopher Schultz wrote:
> Recently, there was a post on the list regarding connection pool leakage
> from Tomcat (ref:
> http://www.nabble.com/Right-way-to-close-database-connection-pool-td24832
>197.html).
This is the code I picked up from http://wiki.apache.or
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Kees Jan,
On 8/7/2009 12:44 PM, Kees Jan Koster wrote:
> I have to restart Tomcat regularly because it exhausted my MySQL
> connections. Show processlist confirms the problem.
>
> I use Hibernate. Do you?
No, I just use straight JDBC in all my code.
Dear Chris,
I have to restart Tomcat regularly because it exhausted my MySQL
connections. Show processlist confirms the problem.
I use Hibernate. Do you?
I'll dig deeper later when I have more time.
Kees Jan
On 7 aug 2009, at 16:53, Christopher Schultz > wrote:
-BEGIN PGP SIGNED MES
Hi John,
just an other suggestion which you could try too:
the context.xml file inside yourApp/META-INF/context.xml gets by
default copied to
$CATALINA_HOME/conf/Catalina/localhost/yourApp.xml at the first
deployment normally when undeploying
yourApp.war the container does remove the yourApp.xml
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
John,
John Cartwright wrote:
> I have a problem where a Datasource is configured in
> META-INF/context.xml and referenced in web.xml. If I install this
> webapp unpacked, everything works fine. However, if I try to run this
> webapp as a packed war,
If you try the example exactly without any variations, it should work.
It worked for me.
-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PR
I tried it both ways. Once my resource wasn't defined globally at all, but
it was defined under the Context. Next, my resource was defined only
globally and not under the context. Is that the problem? Should it be global
and under the context? I'm using the test.jsp file and the
standard-taglibs.j
Also what does your JDBC code look like? (Please post small relevant snippets)
-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Is the Context associated with a Host?
I tried and example as shown here:
http://tomcat.apache.org/tomcat-6.0-doc/jndi-datasource-examples-howto.html
and it works fine. I think the same instructions work for Tomcat 5.5.x
as well.
My server.xml
Also, the error message itself is:
javax.servlet.jsp.JspException: Unable to get connection, DataSource
invalid: "java.sql.SQLException: No driver found for jdbc/TestDB"
org.apache.taglibs.standard.tag.common.sql.QueryTagSupport.getConnection(QueryTagSupport.java:276)
and I have mysql-c
Hi,
Have you solved it already ??... well JNDI datasource have been driving me
nuts for a couple of days, with a similar problem, i.e. the output was the
same (but for other JDBC driver...)... It turn out to be the docBase
parameter of the Context entry, which HAS TO BE THE EXACT location of the
I know how you feel. I would have preferred to do that aswell. I'm not
sure how our hosting company has their servers set up, but that was the
only way (after weeks of trying) that we could get things working. It
may be different in our case though, because we are on a shared environment.
Marti
I have tried to put the resource in the server.xml file, and found that
the same problem occurred.
Also the exact same configuration works flawlessly in my test
environment, so I don't know. I'd rather keep the details in my webapp's
context if possible.
Dan
Martin Grogan wrote:
Hi Dan,
I
Hi Dan,
I had the exact problem with my hosting company. The problem was the
resource was not being read from our context.xml file on Tomcat startup.
The guys at the hosting company had to put the entry for the resource
inside our context in the Tomcat common config.
Maybe you are experiencing
The initialSize parameter is specific to DBCP. I believe the
interface in Tomcat only has fields that are common among pooling
implementations (Commons Pool). You'll have to manually edit the pool
configuration.
An idle connection is one that is in the pool that is not currently
being used by th
7;s just a port / repackaging of
Commons DBCP, and that has had initialSize for a long time now.
Tim
-Original Message-
From: John Cherouvim [mailto:[EMAIL PROTECTED]
Sent: Wednesday, March 08, 2006 7:52 AM
To: Tomcat Users List
Subject: Re: JNDI datasource question
Thanks for your detailed e
Thanks for your detailed explanation.
In tomcat 5.0.28 I cannot find initialSize parameter. Is it something
that was added later?
And by idle connection, do we mean the connection that was closed in a
finally block (returned to the pool)?
John
Tim Lucia wrote:
The number of connections is
The number of connections is affected by three parameters:
initialSize="10"
maxIdle="20"
maxActive="50"
also:
maxWait="5000"
initialSize="10" says make 10 connections at startup. SHOW PROCESSLIST will
reveal 10 processes in this case.
maxIdle="20" says close any idle connections
2)
>
> note The full stack trace of the root cause is available in the Apache
> Tomcat/5.5.15 logs.
>
>
> "Caldarale, Charles R" wrote:
> > From: (e==mc²)? [mailto:[EMAIL PROTECTED]
> > Subject: Re: JNDI datasource
> >
> > just a tip why dont y
t; org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264)
> javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
>
> note The full stack trace of the root cause is available in the Apache
> Tomcat/5.5.15 logs.
>
>
> "Caldarale, Charles R" &l
vlet.java:802)
note The full stack trace of the root cause is available in the Apache
Tomcat/5.5.15 logs.
"Caldarale, Charles R" <[EMAIL PROTECTED]> wrote:
> From: (e==mc²)? [mailto:[EMAIL PROTECTED]
> Subject: Re: JNDI datasource
>
> just a tip why don
> From: (e==mc²)? [mailto:[EMAIL PROTECTED]
> Subject: Re: JNDI datasource
>
> just a tip why dont you try creating a datasource manually since neuer
> Tomcat version dont provide the admin application you will be then
> confortable with laater versions and you will dig i
just a tip why dont you try creating a datasource manually since neuer
Tomcat version dont provide the admin application you will be then
confortable with laater versions and you will dig into knowing things
better ?
http://tomcat.apache.org/tomcat-4.1-doc/jndi-datasource-examples-howto.html
good
Shareable
...
3 remove the portion from server.xml (as we don't need it,application
specific context.xml works)
4 remove the resourcelink from ..\conf\Catalina\localhost\...xml
From: "Wang, Hansen" <[EMAIL PROTECTED]>
Reply-To: "Tom
Two problems:
1. In ResourceLink, the value for attribute "golbal" should be
"jdbc/galleryDB" instead of "galleryDB".
2. The factory classname is wrong if you are using tomcat5's
naming-factory-dbcp.jar. You can just remove that line and the default
is used.
-Original Message-
From: lee
s R <[EMAIL PROTECTED]> wrote:
> >
> > > From: umesh balasubramaniam [mailto:[EMAIL PROTECTED]
> > > Subject: Re: JNDI Datasource Problem
> > >
> > > Try using connector/J and the configuration below:
> > >
> > >
> > >
Connector/J is the newer mysql driver.
http://www.mysql.com/products/connector/j/
Umesh
On 2/25/06, Caldarale, Charles R <[EMAIL PROTECTED]> wrote:
>
> > From: umesh balasubramaniam [mailto:[EMAIL PROTECTED]
> > Subject: Re: JNDI Datasource Problem
> >
> &
> From: umesh balasubramaniam [mailto:[EMAIL PROTECTED]
> Subject: Re: JNDI Datasource Problem
>
> Try using connector/J and the configuration below:
>
>
>
No idea what connector/J is, but the question specifically pertained to
Tomcat 5.5, and the
may i know how to use connetor/J?
From: umesh balasubramaniam <[EMAIL PROTECTED]>
Reply-To: "Tomcat Users List"
To: Tomcat Users List
Subject: Re: JNDI Datasource Problem
Date: Fri, 24 Feb 2006 21:55:15 -0800
Try using connector/J and the con
Try using connector/J and the configuration below:
factory
org.apache.commons.dbcp.BasicDataSourceFactory
driverClassName
com.mysql.jdbc.D
> enableLookups="false"
> redirectPort="8443" protocol="AJP/1.3" />
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
className="org.apache.catalina.realm.UserDataba
----- Original Message -
From: "Marc Richards" <[EMAIL PROTECTED]>
To: "Tomcat Users List"
Sent: Monday, February 20, 2006 8:55 PM
Subject: Re: JNDI Datasource Problem
>I didn't see any mention of the Tomcat
I didn't see any mention of the Tomcat version here,
but in 5.5 the part of the config is
no longer used. All paramters go in the tag with name="value" format just like name and
auth from your example below. i.e. maxIdle="30".
-marc
--- Mark Whitby <[EMAIL PROTECTED]> wrote:
> Hey guys,
>
>
Rose, Greg wrote:
> If you look at the resulting link when you click on CONTEXT
> http://tomcat.apache.org/tomcat-5.5-doc/config/context.html
>
> It gives you several options as to setting up your context. They all
> refer to the context.xml file, not the Server.xml file.
>
> I have found that pla
, February 20, 2006 7:43 AM
To: Tomcat Users List
Subject: RE: JNDI Datasource Problem
> From: Rose, Greg [mailto:[EMAIL PROTECTED]
> Subject: RE: JNDI Datasource Problem
>
> If it is 5.5.x, you can not alter the Server.xml file.
That's not correct. It is strongly recommended to p
into my application's
META-INF directory works for me. That is the last option given in the
help.
-Original Message-
From: Mark Whitby [mailto:[EMAIL PROTECTED]
Sent: Monday, February 20, 2006 7:37 AM
To: Tomcat Users List
Subject: Re: JNDI Datasource Problem
Yeah it's 5.5.15.
It
> From: Rose, Greg [mailto:[EMAIL PROTECTED]
> Subject: RE: JNDI Datasource Problem
>
> If it is 5.5.x, you can not alter the Server.xml file.
That's not correct. It is strongly recommended to put tags in
either the META-INF directory of the webapp or in
conf/Catalina/[hostna
ht as it says here:
http://tomcat.apache.org/tomcat-5.5-doc/jndi-datasource-examples-howto.html
Mark
- Original Message -
From: "Rose, Greg" <[EMAIL PROTECTED]>
To: "Tomcat Users List"
Sent: Monday, February 20, 2006 12:33 PM
Subject: RE: JNDI Datasource Prob
is
started.
-Original Message-
From: chuanjiang lo [mailto:[EMAIL PROTECTED]
Sent: Monday, February 20, 2006 7:25 AM
To: Tomcat Users List
Subject: Re: JNDI Datasource Problem
i think you would need to change the context.xml?
On 2/20/06, Mark Whitby <[EMAIL PROTECTED]> wrote:
&
i think you would need to change the context.xml?
On 2/20/06, Mark Whitby <[EMAIL PROTECTED]> wrote:
>
> Hey guys,
>
> Thanks for the help with the previous problem I had, I've managed to solve
> them now thanks to your help. But now I'm having a problem with setting up
> a DataSource connection.
al Message - From: "Mark Whitby" <[EMAIL PROTECTED]>
To: "Tomcat Users List"
Sent: Sunday, February 19, 2006 9:34 PM
Subject: Re: JNDI Datasource Problem
I've checked the documentation and yes I was reading the 5.0 version
not the 5.5 one! Ho
correct.
Mark
- Original Message -
From: "Mark Whitby" <[EMAIL PROTECTED]>
To: "Tomcat Users List"
Sent: Sunday, February 19, 2006 9:34 PM
Subject: Re: JNDI Datasource Problem
I've checked the documentation and yes I was reading the 5.0 version not
the 5.5 on
bc:mysql://localhost:3306/fyptest?autoReconnect=true"/>
Any ideas what's wrong now?
Mark
- Original Message -
From: "Len Popp" <[EMAIL PROTECTED]>
To: "Tomcat Users List"
Sent: Sunday, February 19, 2006 9:22 PM
Subject: Re: JNDI Datasource Pr
d in the Tomcat set up pages. So would it make any difference
> removing one of these or as it's ignored does it not matter?
>
> Mark
>
> - Original Message -
> From: "Bill Barker" <[EMAIL PROTECTED]>
> To:
> Sent: Sunday, February 19, 2006 8:40 PM
&
PROTECTED]>
To:
Sent: Sunday, February 19, 2006 8:40 PM
Subject: Re: JNDI Datasource Problem
Since you have , this suggests you are using some
version of 5.5. In this case, the is ignored (you set
them as attributes on the tag).
"Mark Whitby" <[EMAIL PROTECTED]> wrot
name="jdbc/TestDB"
>global="jdbc/TestDB"
>type="javax.sql.DataSource" auth="Container" />
>
>
>
>
>
> Any further suggestions?
>
> Mark
> - Original Message -
> From: "Parsons Techn
le (rs.next()) {
out.println(rs.getString("foo")+"");
}
rs.close();
conn.close();
%>
- Original Message -
From: "Mark Whitby" <[EMAIL PROTECTED]>
To: "Tomcat Users List"
Sent: Sunday, February 19, 2006 7:26 PM
Subject: Re: JNDI Data
gestions?
Mark
- Original Message -
From: "Parsons Technical Services" <[EMAIL PROTECTED]>
To: "Tomcat Users List"
Sent: Sunday, February 19, 2006 7:02 PM
Subject: Re: JNDI Datasource Problem
Look up resource link. It goes in the context.xml
Also only put th
Look up resource link. It goes in the context.xml
Also only put the jar file in the common/lib and no where else.
- Original Message -
From: "Mark Whitby" <[EMAIL PROTECTED]>
To: "Tomcat Users List"
Sent: Sunday, February 19, 2006 12:53 PM
Subject: JNDI Datasource Problem
Hey guys,
59 matches
Mail list logo
