[This got badly mangled in transit the first time, so I'm re-posting,
and adding a bit more detail.]

I've made a couple of attempts to install the Ingres Eclipse DTP Bundle
on a machine that already has a working Ingres Database 9.2
installation (not 9.3 as stated before). I seem to be doing something
wrong. When I set up the data source and test the jdbc properties,
iigcd starts using 50% of the CPU and Eclipse hangs waiting for it.

FWIMBW, here's a stack trace of iigcd:

USER32.dll!GetWindowLongW+0x34
ntdll.dll!RtlInitializeCriticalSection+0x89c
ntdll.dll!RtlTimeToTimeFields+0x19
kernel32.dll!GetSystemTime+0x2f
iilibcompat.dll!TMget_stamp+0x94
iilibcompat.dll!TMnow+0xc
iilibcompat.dll!ERslookup+0x87
iilibcompat.dll!ERlookup+0x3a
iilibgcf.dll!gcu_erfmt+0x13b
iilibgcf.dll!gcu_erlog+0xa9
iigcd.exe+0x835d
iigcd.exe+0x8214
iigcd.exe+0x941e
iilibcompat.dll!GCc_callback_driver+0x6e
iilibcompat.dll!GCexec+0x11d
iigcd.exe+0x1244
iigcd.exe+0x1d69f
kernel32.dll!RegisterWaitForInputIdle+0x49

FYI this is Ingres 2006 Release 3 Microsoft Windows Version II
9.2.0 (int.w32/115).

As you can probably guess from the stack trace, the error log fills up
with error messages, all of which look like: GCD Server internal error:
Invalid state transition in TL FSM. Input = 5, state = 0

It's got to be a bug, but have I provoked it by doing something silly?

--
Roy

UK Ingres User Association Conference 2009 will be on Tuesday June 9,
2009
Go to http://www.iua.org.uk/join to get on the mailing list.

I found this link, which mentions the same error (though on release
9.1, and involving Hibernate - not sure if you're using that in you
app, or straight JDBC connections), but it mentions some amendments to
parameters which I got the impression helped...

http://groups.google.com/group/comp....080999daef7bd3

Sean

One other thing I've found with JDBC in the past is how you create
your Statement...

This was way back in the days of "R3", but I found I needed to create
the statement as follows:

Statement statement = connection.createStatement
(ResultSet.TYPE_SCROLL_INSENSITIVE, ResultSet.CONCUR_READ_ONLY,

ResultSet.HOLD_CURSORS_OVER_COMMIT);

It's the TYPE_SCROLL_INSENSITIVE bit that's important, but I think the
way the method takes parameters means you had to declare all three
just to get that one in!

Hope that helps - apologies if you already know this and have been
doing it for years, but it's often the simplest thing.... )

Cheers,

Sean.

seanjand (AT) googlemail (DOT) com wrote:

Thanks Sean. Yes, that thread reports the same error (amongst others).

Unfortunately none of the config changes mentioned seem relevant in any
way.

All I was doing was using Eclipse Data Source set-up and its built-in
JDBC Test function. I have no idea what that does; probably just
connects to the JDBC server to prove the connection URL is right, then
disconnects. I assume.

Anyway, it looks like a bug. I am hoping that it's just reacting badly
to something I've done wrong, and when I do it right the whole problem
will go away.

--
Roy

UK Ingres User Association Conference 2009 will be on Tuesday June 9, 2009
Go to http://www.iua.org.uk/join to get on the mailing list.

On Feb 5, 9:22 pm, Roy Hann <specia... (AT) processed (DOT) almost.meat> wrote:

This matches a known problem actually caused by a configuration error.
Could you check whether the wintcp and the tcp_ip protocoll are both
enabled and are listening at the same port? In 9.0.4 this miss-
configuration caused exactly the problem you describe. This bug
(118003) is fixed even in 9.2, but 9.2.0 (int.w32/115) is a very
early (alpha?) release, it is not fixed there. Simply disabling the
wintcp protocoll should solve the problem(or if really needed change
the listen address), but you really should use the actual 9.2 release.

Kristoff

Kristoff wrote:

Thanks Kristoff; I wouldn't have thought of that. That did the trick
and the JDBC test in Eclipse now works (after deleting errlog.log, which
had grown to fill an entire disk drive).

I think it might be worth asking whoever looks after the community
download page to add a note about this. It seems this was bound to
happen because win_tcp and tcp_ip both default to ON in the alpha
release of 9.2 and that is the only GPL 9.2 executable; there is no
community update. All you can do is upgrade to 9.3.

This seems like a good moment to ask if there's anyone on this list who
is using/playing with the Eclipse DTP Bundle. Anyone got any
hints/tips?

--
Roy

UK Ingres User Association Conference 2009 will be on Tuesday June 9, 2009
Go to http://www.iua.org.uk/join to get on the mailing list.