First of all I meant "no bug in Torque code". It is probably a problem of
the driver, but maybe it also depends on some database server settings, or
network problems....
Thomas
"KERNEUZET FREDERIC" <[EMAIL PROTECTED]> schrieb am 20.04.2006
09:37:37:
> Hi Thomas,
>
> what do you mean by "deeper" ? The driver level ?
> I agree with you, for me it's not Torque directly because if i just
> switch to the MS SQL Driver, everything is ok, whithout any change
> in my application.
>
> I'll try plain jdbc with the JTDS driver to see if the problem is here.
>
> Thanks.
>
> -------- Message d'origine--------
> De: Thomas Fischer [mailto:[EMAIL PROTECTED]
> Date: jeu. 20/04/2006 08:19
> À: Apache Torque Users List
> Cc:
> Objet: Re: RE : RE : RE : Still socket problems
>
> This problem seems to be at a deeper level that torque. To find the
> location of the error, have you tried to create the sql calls by plain
> jdbc ?
>
> Thomas
>
> On Wed, 19 Apr 2006, KERNEUZET FREDERIC wrote:
>
> > Just some additionnal informations to my previous email :
> > =========================================================
> > when i try to select a user that DOESN'T exist, the request is
successful !
> > I just get my "unknown user" error (an empty list is returned by
torque).
> >
> > So, i think that the problem is while Torque is "receiving" data
> from the database server, but why ??
> >
> >
> > Frederic
> >
> >
> > -------- Message d'origine--------
> > De: KERNEUZET FREDERIC
> > Date: mer. 19/04/2006 11:36
> > À: Apache Torque Users List
> > Cc:
> > Objet: RE : RE : Still socket problems
> >
> > Hi,
> >
> > all my tables are owned by the same user.
> > torque.database.schema is set properly.
> >
> > I'm connecting using an SQL user.
> >
> > I think my Torque file configuration is good, because some requestare
OK ...
> >
> > I give you some examples : (this ones are OK)
> > ==========================
> > 2006-04-19 11:33:10,435 DEBUG [main ] BasePeer - SELECT
> MOD_GES_CON.NOM_ENTITE_MODELE, MOD_GES_CON.
> TYPE_MODE_GESTION_CONFIDENTIALITE_CD FROM MOD_GES_CON
> > 2006-04-19 11:33:10,435 DEBUG [main ] BasePeer - Elapsed time=0 ms
> > 2006-04-19 11:33:11,263 DEBUG [main ] BasePeer - SELECT
> ENTITE.GROUP_ID, ENTITE.CD, ENTITE.LA, ENTITE.LIB, ENTITE.
> DATE_DEBUT_VALIDITE, ENTITE.DATE_FIN_VALIDITE, ENTITE.
> SALARIE_CD_RESPONSABLE, ENTITE.ENTITE_CD_MERE FROM ENTITE
> > 2006-04-19 11:33:11,263 DEBUG [main ] BasePeer - Elapsed time=0 ms
> >
> > And this one is KO :
> > ====================
> > 2006-04-19 11:33:23,763 DEBUG [http8080-Processor4] BasePeer -
> SELECT SALARIE.USER_ID, SALARIE.CD, SALARIE.SI, SALARIE.NOM,
> SALARIE.PRENOM, SALARIE.EMAIL, SALARIE.PASSWORD_VALUE, SALARIE.
> CONFIRM_VALUE, SALARIE.MODIFIED, SALARIE.CREATED, SALARIE.
> LAST_LOGIN, SALARIE.OBJECTDATA FROM SALARIE WHERE SALARIE.CD='admin'
> > 2006-04-19 11:33:23,763 DEBUG [http8080-Processor4] BasePeer -
> Elapsed time=0 ms
> >
> >
> > I really don't have any idea ...
> >
> >
> > Frederic
> >
> >
> > -------- Message d'origine--------
> > De: Greg Monroe [mailto:[EMAIL PROTECTED]
> > Date: ven. 14/04/2006 16:38
> > À: Apache Torque Users List
> > Cc:
> > Objet: RE: RE : Still socket problems
> >
> > Below is my Torque.properties info. FYI - I set maxActive higher for
> > production and load testing.
> >
> > About your exceptions problems, are all the tables owned by the user
> > you are connecting to the DB with? Alternatively, does the owner
> > name match the one set by the "torque.database.schema" property
> > in your build.properties file? MS SQL can be picky about this and
> > maybe the MS driver was doing something non-standard like looking
> > for owner.table and then dbo.table.
> >
> > FWIW, I suggest having a common owner/db connection id and not
> > setting the schema unless you need to. It makes the Torque
> > code much more portable.
> >
> > Are you connecting with a SQL User or trying to use MS's net id
> > authentication? I think there may be some extra parameters needed
> > by jTDS in the latter case. FWIW, I don't use this, I use a specific
> > SQL user (which is more portable).
> >
> > Here's my config:
> >
> > torque.database.default.adapter=mssql
> > torque.dsfactory.default.connection.driver =
> > net.sourceforge.jtds.jdbc.Driver
> > # ;TDS=7.0 option needed for MS SQL 7.0 only.
> > torque.dsfactory.default.connection.url =
> > jdbc:jtds:sqlserver://mssql.dukece.com:1433/dbName;TDS=7.0
> > torque.dsfactory.default.connection.user = MSsqlUser
> > torque.dsfactory.default.connection.password = password
> >
> > # # Using commons-dbcp
> >
torque.dsfactory.default.factory=org.apache.torque.dsfactory.SharedPoolD
> > ataSourceFactory
> > torque.dsfactory.default.pool.maxIdle=8
> > torque.dsfactory.default.pool.maxActive=10
> > torque.dsfactory.default.pool.testOnBorrow=true
> > torque.dsfactory.default.pool.validationQuery=SELECT 1
> >
> >> -----Original Message-----
> >> From: KERNEUZET FREDERIC [mailto:[EMAIL PROTECTED]
> >>
> >> thanks for your suggestion, i've tried to install Jtds driver
> >> but unsuccessfully ... Some doSelect() methods start throwing
> >> exceptions (but not all ! Strange ...).
> >>
> >> Which pool do you use with your JTDS driver ? And could you
> >> give me some examples of your torque configuration file ?
> >>
> >
> > Duke CE Privacy Statement
> > Please be advised that this e-mail and any files transmitted with
> it are confidential communication or may otherwise be privileged or
> confidential and are intended solely for the individual or entity to
> whom they are addressed. If you are not the intended recipient you
> may not rely on the contents of this email or any attachments, and
> we ask that you please not read, copy or retransmit this
> communication, but reply to the sender and destroy the email, its
> contents, and all copies thereof immediately. Any unauthorized
> dissemination, distribution or copying of this communication is
> strictly prohibited.
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
