Hello again,
still no joy with connecting jdbc to an Ingres server, but I do have more
data now, though not a lot more than what came from the errlog.log. The
new data follows, and I've left the original problem statement below, for
reference.
First, the command:
java -cp /opt/ingres/lib:$CLASSPATH -Djdbc.property_file=jdbc.trace
-Dingres.jdbc.trace.log=jdbctrace.log -Dingres.jdbc.drv.trace=5
-Dingres.jdbc.trace.msg=5 -Dingres.jdbc.trace.drv=5 JdbcInfo
jdbc:ingres://ghia:1523/stdbv30;user=st;password=<pwd>
Note that the driver seemed to be ignoring the property file, so I just
put all the properties directly into the command-line. The log was
created, and it contained:
Ingres Corporation - JDBC Driver [2.5]: Mon Dec 04 13:27:18 PST 2006
Ingres-Driver: registered Ingres-Driver.connect()
Conn: Connecting to server: ghia:1523
MsgIo[0]: opening network connection
MsgIo[0]: ghia:1523 -> ghia/127.0.0.1,1523
MsgOut[0]: open TL Connection
MsgIn[0]: confirm TL connect
MsgIn[0]: error negotiating parameters
MsgIn[0]: closing network connection
Ingres-Driver.connect(): error establishing connection
Exception: 40003, 0xc4003
Message: Connection failed.
So, the question becomes, what TL parameters are negotiated and how do I
set them? More importantly, what flaws might exist in a new installation
that could explain not having the right TL parameters in the first place?
I didn't find any TL intems in config.dat. The error
GC2811_TL_INVALID_TDPU is found in the errlog.log, but searching on TDPU
doesn't yield anything.
Profoundly bizzare that I'd have this problem and nobody else seems to
have it. I do note, though, that I'm running on the Evaluation Version -
any reason to think that'd have anything to do with it? If anything, it
should be _more_ stable!
...Looks like I'll be spending some time in the source code. Anybody got
any heads-up on where to look?
Thanks,
Richard
On Sun, 3 Dec 2006, Richard Troy wrote:
>
> Hello All,
>
> On Thursay past I installed a new Ingres installation - my first in about
> 12 years - and so far everything seems to be working except the
> TERM_INGRES setting and the ability to connect with Java. I have created
> and authorized users, created a database and have no problem putting data
> into tables, etc. I continually get an exception from the jdbc driver,
> merely saying, "Error establishing connection: Connection failed." I've
> been working on this problem since Thursay - Please Help!
>
> Situation: Installation is named D0 (that's capital D, zero -should have
> been II I suppose). I couldn't find any port labled D0, so I took it upon
> myself to set one up in /etc/services, but later just hard-coded the port
> with cbf by going to the net server and configuring the protocols, setting
> TCP_IP to 1523 as the old former port for "ingreslock" was 1524.
> Restarted iigcc and it reports looking for 1523 ast TCP_IP port. So far,
> so good. Ran java JdbcInfo program and it loads the driver fine, so then
> tried with my connection url, like this:
>
> $ java JdbcInfo jdbc:ingres://ghia:1523/stdbv30;user=<user>;password=<pwd>
> Error establishing connection:
> Connection failed.
>
> When that happened, the errlog.log received:
>
> ghia ::[33061 IIGCC, 00000002]: Sun Dec 3 18:26:44 2006
> E_GC2811_TL_INVALID_TPDU TL internal error: Received invalid TPDU
> type 00000040.
> ghia ::[33061 IIGCC, 00000002]: Sun Dec 3 18:26:44 2006
> E_GC2812_TL_INVALID_CONNCTN TL internal error: Received unknown
> connection id 0000544C from partner.
> ghia ::[33061 IIGCC, 00000002]: Sun Dec 3 18:26:44 2006
> E_GC2806_TL_FSM_INP TL internal error: Invalid input event in TL FSM
>
> The port shows up on a port scan from another system. I'm using the jdbc
> driver from iijdbc.jar I shouldn't need the "JDBC Server" and have the
> Data Access Server running instead (default). (Everything excep the JDBC
> Server is running.)
>
> As there wasn't even a Java, much less JDBC, back when I previously worked
> with Ingres, I did my homework and found reference to using the driver's
> trace feature, like this:
>
> java -Djdbc.property_file=java.trace JdbcInfo
> jdbc:ingres://ghia:1523/stdbv30;user=<user>;password=<pwd>
>
> The file java.trace is in the current working directory and contains:
>
> ingres.jdbc.trace.log=jdbc.log
> ingres.jdbc.trace.drv=5
> ingres.jdbc.trace.msg=5
> ingres.trace.msg.nl=3
>
> The flag is accepted but no jdbc.log file is ever created, nor does
> anything new or different come from std-err or std-out.
>
> Please note that while in theory I could set up a vhost, it won't work in
> my deployment scenario; nothing from Ingres (other than the jdbc driver)
> can be required on the client. JDBC should be enough! (Better be or I
> won't be able to use Ingres.) Note that in this environment, Oracle,
> Sybase, DB2, Postgres and Informix are all setup and working correctly and
> only have their jdbc drivers on the client - I just need to add Ingres to
> the mix.
>
> If there's anything I need to do with the name server or anything like
> that, I haven't touched it yet, so please advise about setup issues I
> haven't mentioned already!
>
> THANK YOU for your help,
>
> Richard
>
>
--
Richard Troy, Chief Scientist
Science Tools Corporation
510-924-1363 or 202-747-1263
[EMAIL PROTECTED], http://ScienceTools.com/
_______________________________________________
Users mailing list
Users@lists.ingres.com
http://lists.ingres.com/mailman/listinfo/users
