Hello Rune,

 

There is a problem in Ingres 2.6 with Dynamic Vnodes.  A crash happens when the 
length of a vnode exceeds 64 bytes.  This is true of all vnodes.  When using 
Dynamic Vnodes, it is more likely that the length will be greater than 64 bytes.

 

Here is the description of this problem,

 

Overview: 

        Bug 115280

        Buffer overrun in FRS with vnodeless connection strings 

        because they are generally longer; this occasionally causes 

        crashes in OpenROAD (and Ingres forms applications).  

 

Release Notes: 

        (GENERIC)

        OpenROAD and Ingres forms-based applications crash 

        intermittently when connecting with a vnodeless 

        connection string (aka dynamic vnode). 

 

I have referred to this feature as "Dynamic Vnodes" instead of "Vnodeless".  I 
created a simple OpenROAD application that generates the dynamic vnode strings 
and does simple connection tests.  I found the documentation to be a little 
difficult to understand.  

 

When I started using this application, I found that Dynamic Vnode entries can 
be used to override the contents of an existing vnode.  This means that if your 
use of Dyanmic Vnodes is primarily to supply a userid and password for a 
connection request, then you could create a vnode that has an invalid userid 
and password and then use the dynamic vnode syntax to override the entry.

 

So if you have a vnode defined and use the following to connect to an Ingres 
database

 

            myvnode::mydatabase/ingres

 

Then you can use the following in your program to override the userid and 
password stored in the "myvnode" entry

 

            myvnode[myuserid,mypassword]::mydatabase/ingres

 

If you can use this technique, then you should be able to drop below the 64 
byte length in the dynamic vnode that you specify.

 

I suggest that you try sending a vnode entry that is longer than 64 bytes to 
verify that you have a crash.  Once you verify that this is the problem, you 
can use the circumvention to get around the crash.  Meanwhile, open an issue 
and ask for a fix for bug 115280.

 

I hope that this helps.

 

P.S.  If you want copies of my simple OpenROAD application that generates 
dynamic vnodes, just drop me an email.

 

Durwin Wright | Sr. Architect | [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>  | 
Ingres | 500 Arguello Street | Suite 200 | Redwood City | CA | 94063 | USA 
<http://maps.google.com/maps?q=500+arguello+street,+94063&ll=37.487297,-122.233200&spn=0.004602,0.012771&t=k&hl=en>
   +1 650-587-5523 | fax: +1 650-587-5550 

________________________________

From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED]
Sent: Friday, December 08, 2006 5:56 AM
To: [EMAIL PROTECTED]
Subject: [Openroad-users] vnodeless connection in OpenROAD 4.1 ?

 

Hi,

I'm trying to connect to a server running Ingres gateways (EA 2.1 0106) without 
a defined vnode, but with a connection string like this:

@servername,wintcp,II[*,instpwd]::database/mssql

This string works in an sql-command on my PC, queries run ok.

In OpenRoad it connects ok, but OR crashes/exits on first use.

My development environment is OpenROAD 4.1/0403(int.w32/00) (patch 10464).

Anyone had a similar experience? (and fixed it...)

 

Rune Randøy

Aker Kværner Business Partner (www.akerkvaerner.com)

Kristiansand, Norway


This e-mail and any attachment are confidential and may be privileged or 
otherwise protected from disclosure. It is solely intended for the person(s) 
named above. If you are not the intended recipient, any reading, use, 
disclosure, copying or distribution of all or parts of this e-mail or 
associated attachments is strictly prohibited. If you are not an intended 
recipient, please notify the sender immediately by replying to this message or 
by telephone and delete this e-mail and any attachments permanently from your 
system. 

_______________________________________________
Users mailing list
[email protected]
http://lists.ingres.com/mailman/listinfo/users

Reply via email to