[Info-ingres] Ingres 2.5 Net Client: Faulting Application iijdbc.exe

Programming and Web Development Forums - DATABASE - Issues relating to INGRES products.

Skip to content

[Info-ingres] Ingres 2.5 Net Client: Faulting Application iijdbc.exe

DATABASE
Post a reply

    Sponsored Links

    Next

  • 1. [Info-Ingres] problems with cursorselect
    Hi all, I have a strange behavior in our installation and I dont find any explanation for that: Application works with a cursor select, declares the cursor, opens it for readonly (prefetch is default, not expicitly set), fetches the rows (mostly 0 rows) and closes the cursor finaly. This statement is executed many times a day. It takes milliseconds to execute. But after some days the execution growes up to several minutes to execute the first fetch and the execution does not get better for all the next executions. Stopping the application, starting it again shows no effect. But when I reboot Ingres it works fine for next days, until the same procedure begins. The manual states, that the open will collect the data in a temporary table and places the cursor at the first row. The fetch gets then the data. So I wonder, why the fetch takes so much time. Any explanation for that? Does anyone has the same behavior in the past? Any solutions? Installation is: HP UX 11.11 Ingres version II 2.5/0011 patch 9007 Thanks in advance Hans Weisenberger _______________________________________________ Info-ingres mailing list XXXX@XXXXX.COM
  • 2. problems with cursorselect
    Hi all, I have a strange behavior in our installation and I dont find any explanation for that: Application works with a cursor select, declares the cursor, opens it for readonly (prefetch is default, not expicitly set), fetches the rows (mostly 0 rows) and closes the cursor finaly. This statement is executed many times a day. It takes milliseconds to execute. But after some days the execution growes up to several minutes to execute the first fetch and the execution does not get better for all the next executions. Stopping the application, starting it again shows no effect. But when I reboot Ingres it works fine for next days, until the same procedure begins. The manual states, that the open will collect the data in a temporary table and places the cursor at the first row. The fetch gets then the data. So I wonder, why the fetch takes so much time. Any explanation for that? Does anyone has the same behavior in the past? Any solutions? Installation is: HP UX 11.11 Ingres version II 2.5/0011 patch 9007 Thanks in advance Hans Weisenberger
  • 3. ingres dates and the Oracle gateway
    We're currently migrating an OR application to Oracle using the Enterprise Access Gateway. Sadly, our database does contain date entries of blank strings and these don't seem to be favoured by Oracle when we copy across the table using the gateway. It looks as though we may have to update our database to change problem date prior to unloading it to be reloaded into Oracle. Any war stories/tips and tricks for transferring some rather dubious dates over to Oracle? Unfortunately we have code inside our application that looks for 'blank' date values and while we are addressing this issue in the Oracle variation of the code, we are trying to minimise the potential disruption to our ingres based live system Thanks, Paul

Re: [Info-ingres] Ingres 2.5 Net Client: Faulting Application iijdbc.exe

Postby m-angel » Thu, 16 Mar 2006 01:58:59 GMT

lient_max -1 --> number max clients (-1 nothing) must put a
number > 0 by example40

client_timeout 5
connect_pool_expire 5
connect_pool_size -1 > 0
connect_pool_status optional
port II7 el number of port ejem 2006
protocol wintcp or tcp_ip best

see you the help ,
a good idea is install r3 version on xp , there are a toll for config server

if you push F1 had a good help for the config parameters of the config.dat

salu2


13 Mar 2006 16:34:58 -0800, XXXX@XXXXX.COM < XXXX@XXXXX.COM

<div> </div>
<div>client_max          -1    --> number max clients (-1 nothing) must put a number > 0  by         example40<br> </div>
<div>client_timeout       5<br>connect_pool_expire 5<br>connect_pool_size -1     > 0<br>connect_pool_status    optional<br>port   II7     el number of port ejem 2006<br>protocol    wintcp  or tcp_ip best<br><br>see you the help ,
</div>
<div>a good idea is install r3 version on xp , there are a toll for config server </div>
<div>if you push F1 had a good help for the config parameters of the config..dat</div>
<div> </div>
<div>salu2<br><br> </div>
<div><span class="gmail_quote">13 Mar 2006 16:34:58 -0800, <a href="mailto: XXXX@XXXXX.COM "> XXXX@XXXXX.COM </a> <<a href="mailto: XXXX@XXXXX.COM "> XXXX@XXXXX.COM </a>>:</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">I have just upgraded 2.5 of the net client to version 2.6.  This<br>software is used for the jdbc component, which allows our software to
<br>communicate with a client's Ingres database server by jdbc.  Although<br>the net client has had problems in the past, since the upgrade we have<br>new and severe problems in that the jdbc component of the net client<br>
shuts down frequently (a few times per hour). In the Windows Event<br>Viewer, we get the following error:<br><br>Faulting application iijdbc.exe, version 2.60.305.0, faulting module<br>OICLFNT.DLL, version 2.60.305.0, fault address 0x000338aa.
<br><br>Ingres net client server machine is running on a Windows 2003 Server<br>Standard Edition, version 5.2.3790 Service Pack 1.<br><br>Also, the Ingres database server is:<br>Ingres (Hospro db etc) version  2.0/0001 (usl.us5
/00)<br><br>Ingres net client jdbc settings are:<br>client_max          -1<br>client_timeout       5<br>connect_pool_expire 5<br>connect_pool_size -1<br>connect_pool_status    optional<br>port   II7<br>protocol    wintcp<br>
<br>Can anyone throw any light on the matter?  Thanks!<br><br>The error log in Ingres reports the following at the time of this<br>shutdown:<br>(Note, event viewer er
Top

Similar Threads:

1.Ingres 2.5 Net Client: Faulting Application iijdbc.exe 

I have just upgraded 2.5 of the net client to version 2.6.  This
software is used for the jdbc component, which allows our software to
communicate with a client's Ingres database server by jdbc.  Although
the net client has had problems in the past, since the upgrade we have
new and severe problems in that the jdbc component of the net client
shuts down frequently (a few times per hour). In the Windows Event
Viewer, we get the following error:

Faulting application iijdbc.exe, version 2.60.305.0, faulting module
OICLFNT.DLL, version 2.60.305.0, fault address 0x000338aa.

Ingres net client server machine is running on a Windows 2003 Server
Standard Edition, version 5.2.3790 Service Pack 1.

Also, the Ingres database server is:
Ingres (Hospro db etc) version  2.0/0001 (usl.us5/00)

Ingres net client jdbc settings are:
client_max          -1
client_timeout       5
connect_pool_expire 5
connect_pool_size -1
connect_pool_status    optional
port   II7
protocol    wintcp

Can anyone throw any light on the matter?  Thanks!

The error log in Ingres reports the following at the time of this
shutdown:
(Note, event viewer error is reported at 10:58:28)

Tue Mar 14 10:51:55 2006 E_JD0100_STARTUP	JDBC Server normal startup.
PHOSQL  ::[II\JDBC\9ec       , 00000000]: Tue Mar 14 10:51:55 2006
E_JD0101_SHUTDOWN	JDBC Server normal shutdown.
PHOSQL  ::[II\JDBC\e08       , 00000000]: Tue Mar 14 10:57:48 2006
E_JD0107_CONN_ABORT	Aborting client connection, reason follows.
PHOSQL  ::[II\JDBC\e08       , 00000000]: Tue Mar 14 10:57:48 2006
E_JD010D_IDLE_LIMIT	Client has been idle longer than the configured
limit: connection aborted.
PHOSQL  ::[II\JDBC\e08       , 00000000]: Tue Mar 14 10:57:48 2006
E_JD0107_CONN_ABORT	Aborting client connection, reason follows.
PHOSQL  ::[II\JDBC\e08       , 00000000]: Tue Mar 14 10:57:48 2006
E_JD010D_IDLE_LIMIT	Client has been idle longer than the configured
limit: connection aborted.
PHOSQL  ::[II\JDBC\e08       , 00000000]: Tue Mar 14 10:57:48 2006
E_JD0107_CONN_ABORT	Aborting client connection, reason follows.
PHOSQL  ::[II\JDBC\e08       , 00000000]: Tue Mar 14 10:57:48 2006
E_JD010D_IDLE_LIMIT	Client has been idle longer than the configured
limit: connection aborted.
PHOSQL  ::[II\JDBC\e08       , 00000000]: Tue Mar 14 10:57:48 2006
E_JD0107_CONN_ABORT	Aborting client connection, reason follows.
PHOSQL  ::[II\JDBC\e08       , 00000000]: Tue Mar 14 10:57:48 2006
E_JD010D_IDLE_LIMIT	Client has been idle longer than the configured
limit: connection aborted.
PHOSQL  ::[II\COMSVR\c7c     , 00000000]: Tue Mar 14 10:57:48 2006
E_GC220A_NRM_RCV_FAIL	GCA normal receive failure: reason follows.
PHOSQL  ::[II\COMSVR\c7c     , 00000000]: Tue Mar 14 10:57:48 2006
E_GC0001_ASSOC_FAIL	Association failure: partner abruptly released
association
PHOSQL  ::[II\COMSVR\c7c     , 00000005]: Tue Mar 14 10:57:48 2006
E_GC220A_NRM_RCV_FAIL	GCA normal receive failure: reason follows.
PHOSQL  ::[II\COMSVR\c7c     , 00000005]: Tue Mar 14 10:57:48 2006
E_GC0001_ASSOC_FAIL	Association failure: partner abruptly released
association
PHOSQL  ::[II\COMSVR\c7c     , 00000006]: Tue Mar 14 10:57:48 2006
E_GC220A_NRM_RCV_FAIL	GCA normal receive failure: reason follows.
PHOSQL  ::[II\COMSVR\c7c     , 00000006]: Tue Mar 14 10:57:48 2006
E_GC0001_ASSOC_FAIL	Association failure: partner abruptly released
association
PHOSQL  ::[II\COMSVR\c7c     , 00000004]: Tue Mar 14 10:57:48 2006
E_GC220A_NRM_RCV_FAIL	GCA normal receive failure: reason follows.
PHOSQL  ::[II\COMSVR\c7c     , 00000004]: Tue Mar 14 10:57:48 2006
E_CLFE07_BS_READ_ERR	Read from peer process failed; it may have exited.
PHOSQL  ::[II\JDBC\e08       , 00000000]: Tue Mar 14 10:58:11 2006
E_JD0107_CONN_ABORT	Aborting client connection, reason follows.
PHOSQL  ::[II\JDBC\e08       , 00000000]: Tue Mar 14 10:58:11 2006
E_JD010D_IDLE_LIMIT	Client has been idle longer than the configured
limit: connection aborted.
PHOSQL  ::[II\COMSVR\c7c     , 00000001]: Tue Mar 14 10:58:11 2006
E_GC220A_NRM_RCV_FAIL	GCA normal receive failure: reason follows.
PHOSQL  ::[II\COMSVR\c7c     , 00000001]: Tue Mar 14 10:58:11 2006
E_CLFE07_BS_READ_ERR	Read from peer process failed; it may have exited.
PHOSQL  ::[II\COMSVR\c7c     , 0000000b]: Tue Mar 14 10:58:38 2006
E_GC220B_EXP_RCV_FAIL	GCA expedited receive failure: reason follows.
PHOSQL  ::[II\COMSVR\c7c     , 0000000b]: Tue Mar 14 10:58:38 2006
E_GC0001_ASSOC_FAIL	Association failure: partner abruptly released
association
PHOSQL  ::[II\COMSVR\c7c     , 00000009]: Tue Mar 14 10:58:38 2006
E_GC220B_EXP_RCV_FAIL	GCA expedited receive failure: reason follows.
PHOSQL  ::[II\COMSVR\c7c     , 00000009]: Tue Mar 14 10:58:38 2006
E_GC0001_ASSOC_FAIL	Association failure: partner abruptly released
association
PHOSQL  ::[II\COMSVR\c7c     , 00000008]: Tue Mar 14 10:58:38 2006
E_GC220B_EXP_RCV_FAIL	GCA expedited receive failure: reason follows.
PHOSQL  ::[II\COMSVR\c7c     , 00000008]: Tue Mar 14 10:58:38 2006
E_GC0001_ASSOC_FAIL	Association failure: partner abruptly released
association
PHOSQL  ::[II\COMSVR\c7c     , 00000007]: Tue Mar 14 10:58:38 2006
E_GC220B_EXP_RCV_FAIL	GCA expedited receive failure: reason follows.
PHOSQL  ::[II\COMSVR\c7c     , 00000007]: Tue Mar 14 10:58:38 2006
E_GC0001_ASSOC_FAIL	Association failure: partner abruptly released
association
PHOSQL  ::[II\COMSVR\c7c     , 00000003]: Tue Mar 14 10:58:38 2006
E_GC220B_EXP_RCV_FAIL	GCA expedited receive failure: reason follows.
PHOSQL  ::[II\COMSVR\c7c     , 00000003]: Tue Mar 14 10:58:38 2006
E_GC0001_ASSOC_FAIL	Association failure: partner abruptly released
association
PHOSQL  ::[II\COMSVR\c7c     , 00000000]: Tue Mar 14 10:58:38 2006
E_GC220A_NRM_RCV_FAIL	GCA normal receive failure: reason follows.
PHOSQL  ::[II\COMSVR\c7c     , 00000000]: Tue Mar 14 10:58:38 2006
E_GC0001_ASSOC_FAIL	Association failure: partner abruptly released
association
PHOSQL  ::[JDBC              , 00000000]: Tue Mar 14 10:59:23 2006
E_JD0106_NTWK_OPEN	Network open complete for protocol WINTCP, port II7
(21071).
PHOSQL  ::[II\JDBC\494       , 00000000]: Tue Mar 14 10:59:23 2006
E_JD0113_LOAD_CONFIG	Finished loading configuration parameters for
configuration '(DEFAULT)' of server type 'JDBC'.
PHOSQL  ::[II\JDBC\494       , 00000000]: Tue Mar 14 10:59:23 2006
E_JD0100_STARTUP	JDBC Server normal startup.

2.[Info-Ingres] Upgrading Ingres Client from 2.5 to 2.6

3.[Info-ingres] Trying to use Openroad3.5/03 application on a IngresII2.6sp2 net client

4.[Info-ingres] Ingres/Net & ODBC on Client PC's

5.[Info-Ingres] Ingres NET on the client node 

Gang,

The general rule of thumb I've always used for
server net is 80-120 connections per Ingres/NET
server (GCC).

So if I have 450 expected simultaneous sessions,
I use 5 GCCs.

My question is ... what about the client?  If one client
node runs 450 ABF applications that all connect with
Ingres NET, do I need 5 GCCs on the client?

Once a client establishes a connection with a server,
does the GCC on the client still play a role?  Or
does the ABF app talk directly to the GCC on the server?

I used to know this, but now I've confused myself.

Please help!

Mike Leo

6. [Info-Ingres] Slow Ingres Net / Client

7. [Info-Ingres] JDBC driver for Ingres 2.5

8. [Info-Ingres] Ingres 2.5 and cache memory

Post a reply

Return to DATABASE

 

Who is online

Users browsing this forum: No registered users and 59 guest

Powered by phpBB © 2000, 2002, 2005, 2007 phpBB Group