Sir
Very very thanks Greg Monroe to reply
I did all changes according to the given doc on below link:
http://db.apache.org/torque/releases/torque-3.3/runtime/reference/initialisation-configuration.html
Still i am facing that torque is not initialized.
torque.properties are as below
torque.databas
By migrated I assume you mean from an older version of Torque.
Most likely it was a version prior to the properties file revamp
that took place in Version 3.1 (I think).
If this is true, you will need to modify your Torque runtime
configuration properties file to the new format. See:
http://db
I got resolution of this issue - there was a bug elsewhere in the
classes we're using to initialize Torque; they were calling the wrong
torque.properties file. It was impossible to determine from my unit
test, but when I went higher up the chain we figured it out.
Owen B. Mehegan wrote:
Hi, I'
Do you call Torque.init() in your code before any attempt to use the
connection?
On Wed, 2008-02-06 at 17:50 -0800, Owen B. Mehegan wrote:
> Hi, I've seen this question asked many times in the mailing list
> archives, but so far I can't figure out a solution to the problem in my
> case. I have a
Oh, I see what you were getting at, sorry! I obfuscated the actual value
of 'url' in this email, since I considered it to be sensitive data :)
Alvaro Coronel wrote:
torque.dsfactory.recoverable.connection.url looks yucky.
"Owen B. Mehegan" <[EMAIL PROTECTED]> wrote: Hi, I've seen this questio
Yeah, I'm experimenting with your suggestions now. My torque.properties
includes three other entries. These three are identical except in name:
torque.dsfactory.friend.factory=com.friend.db.MockDataSourceFactory
torque.dsfactory.friend.pool.maxActive=22
torque.dsfactory.friend.pool.maxIdle=22
to
Well, RecoverableDataSourceFactory is apparently just one of the
standard Torque drivers, which we just happen to store in a logical
location in our source tree. The comment at the top of that source file
says:
/**
* A factory that looks up the DataSource using the JDBC2 pool methods.
*
* @
torque.dsfactory.recoverable.connection.url looks yucky.
"Owen B. Mehegan" <[EMAIL PROTECTED]> wrote: Hi, I've seen this question asked
many times in the mailing list
archives, but so far I can't figure out a solution to the problem in my
case. I have a unit test that is using Easymock to cre
Were you able to connect to any other database than "recoverable" database?
what driver did you use ? were you able to connect to recoverable database
itself using JDBC test with the same username and password? Lastly, try using
different different dsfactory to see if it works for you. Here is m
Hello,
Today I started again the process from the begining and all is allright.
Error could come from a Torque conflict version as you said but right now
all is allright.
Thanks a lot for your help!
Pierre
> I'd assume you have a new Torque version at compile time but the new
> 3.3-RC1 torque v
I'd assume you have a new Torque version at compile time but the new
3.3-RC1 torque version at compile time. Make sure you use the same Torque
version at compile time and run time.
I'm glad the connection issue is solved. I have created an issue about
displaying a more interpretable error message i
Hi again,
Reading one more time Thomas mail I realize that I had not initialize
Torque with Torque.init("torque.properties"); command.
So I added this line and it seems that the connection is enabled but right
now I have a new error that I could not solve. Here is the trace:
Exception in thread
Hi Thomas,
Thank you for your tip, I could access my database without error message
as following:
Class.forName("org.gjt.mm.mysql.Driver");
java.sql.Connection connection =
java.sql.DriverManager.getConnection("jdbc:mysql://localhost:3306/BddPortalCCG",
"", "");
However, the Torque code still ge
Ok, I presume you are using the Torque sample code, so you call
Torque.init() with the correct properties file first thing in the
application, as Guy remarked.
Maybe it's time to step back and try whether you can access the database
using plain jdbc. You would use the code
Class.forName("org.gjt.m
Hi Thomas,
I am using a correct db user name and password in my torque.properties and
build.properties files but I don't show it in the mail.
Any other idea?
Pierre
> a) I do not believe that the torque.properties needs to be in the
> classpath. The tutorial example code loads it from the file
Do you initiate Torque in your code?
In the old version we use we call
Torque.init();
Before we try using Torque in any way.
I put it in the init method of the first servlet of the web application.
On Mon, 2007-01-22 at 11:46 -0600, Pierre-Alain Branger wrote:
> Hi everybody,
>
> I follow your s
a) I do not believe that the torque.properties needs to be in the
classpath. The tutorial example code loads it from the file system, as far
as I know.
b) in your torque.properties, you have set
torque.dsfactory.BddPortalCCG.connection.user =
which means that there is no user set for your connne
Hi everybody,
I follow your suggestions but I still can not execute my program properly.
Following, the different things I did:
- I added torque.properties, actually it was not in it:
export CLASSPATH=/home/pbranger/BddPortalCCG/src/conf
By the way the tutorial don't mention this step.
- I also
This usually means that connecting to the database failed. Possible reasons
are
- the database is not started
- the connection url, password or username are wrong in the configuration
file
Loking at your configuration, I am sure whethet mysql accepts connections
without specifying a database user (
Hi Pierre,
Everything seems to be ok! Is the torque.properties in your classpath?
Regards,
Robert
-Original Message-
From: Pierre-Alain Branger [mailto:[EMAIL PROTECTED]
Sent: Saturday, January 20, 2007 2:04 AM
To: torque-user@db.apache.org
Subject: no DataSourceFactory configured
Hi e
20 matches
Mail list logo
