Migrating from V2

Jannie,

Also what are the specs on the PC you're using? Processor/Memory etc..

 

PC is a 1GHz Celeron, 256MB

database file is not read only

No GUI's open

Using single click.

I've tried various combinations of starting C-Gate/Toolkit all with similar result.

Just did a scan now again (after yet another crash) and the scan went through....

 

Thanks for the further information Jannie.

We've re-run our basic tests on a Windows 2000 Machine (VM). Using a 3.06 PCI we've had no issues. Did you have the firmware version of the particular PCI that you are using and the bridge?

We dont have a 1GHZ/256 Celeron machine, I doubt its related.. but if you did have access to another machine it would be worth trying it. Is the machine particularly loaded down with other processes running?

 

From a previous post in this thread:

PCI Firmware is 3.11.
Bridge Firmware is 4.1.00

Java Version 1.4.2_05

As stated before, the system is a clean install with only C-Bus products installed, i.e. C-Gate, Toolkit and Tica

I don't see any error messages in the Console.

There is another C-Gate 1.5 on the network and as the network is a production network a fair amount of traffic can be seen on the network.

I canot build another, smaller network as this is a production network.

I've now managed to scan each network once but still get the crashes.

 

OK.. thanks for that information. We're going to build up a Network with the same versions.

I think this is going to be the crux of problem.. with a lower spec PC such as you have CGate and Toolkit have a LOT of communications to exchange.. CGate is busily passing everything through to toolkit for processing and Toolkit is trying to get things done in the opposite direction (onto the bus).. Shutting down the other CGate, and/or using a faster PC may well solve the issues. We obviously need to make Toolkit a little more graceful in how it deals with this overload, so we'll set up some tests to replicate what you've experienced.

Thanks for your persistence.. looking forward to hearing how you go once the other CGate is shut down or during a lower traffic period.. or a faster PC (unlikely to fix it).. As it stands Toolkit just appears to be failing to get responses to commands that should happen quickly but dont. Albeit somewhat ungracefully.

 

Not sure I buy this.

I monitor the system resources and less than 5% CPU is being used while more than 60% of memory is free. So the system is basically idling. C-Gate 1.5 and V2 on an even smaller box (220MHz Pentium, 256M RAM and Win98!) have no problem working on this network. Been stable for a few years now.

If there's a communication problem it must be internal to this version of software.

I've shut down C-gate 1.5 (it's now 1AM) to ensure it's not generating any traffic.

Even when I just open the network, it crashes. Log below:

--------------------------------------------------------------------------------
TITLE
--------------------------------------------------------------------------------
Application Error
--------------------------------------------------------------------------------
USER COMMENTS
--------------------------------------------------------------------------------

--------------------------------------------------------------------------------
CUSTOM INFO
--------------------------------------------------------------------------------
Version = 1.1.4
Build = 124

--------------------------------------------------------------------------------
ERROR MESSAGE
--------------------------------------------------------------------------------
Exception 'ECGateCommandTimeOut' in module CBusToolkit1_1.exe at 0012DC1C
TcgcProjectSave

Module: CIS_TCGateCommand, Source: CIS_TCGateCommand.pas, Line 539
Procedure: TThreadCommandSynchroniser.ProcessResponses
--------------------------------------------------------------------------------
CALL STACK
--------------------------------------------------------------------------------
Call stack:
:0052EC1C [CBusToolkit1_1.exe] TThreadCommandSynchroniser.ProcessResponses (CIS_TCGateCommand.pas, line 539)
:7C59BBF3 [kernel32.dll]
Recursive call (3 times):
:0052EC1C [CBusToolkit1_1.exe] TThreadCommandSynchroniser.ProcessResponses (CIS_TCGateCommand.pas, line 539)
:77A72C2B [ole32.dll]
:77A82955 [ole32.dll]
:00402C95 [CBusToolkit1_1.exe] SysFreeMem (GETMEM.INC, line 1123)
:00402CBD [CBusToolkit1_1.exe] SysFreeMem (GETMEM.INC, line 1127)
:0040288F [CBusToolkit1_1.exe] TryHarder (GETMEM.INC, line 946)
:0040776D [CBusToolkit1_1.exe] DynArrayHigh (system.pas, line 10344)
:00411EE6 [CBusToolkit1_1.exe] TMultiReadExclusiveWriteSynchronizer.WriterIsOnlyReader (sysutils.pas, line 7071)
:00411FD9 [CBusToolkit1_1.exe] TMultiReadExclusiveWriteSynchronizer.EndWrite (sysutils.pas, line 7103)
:0064A121 [CBusToolkit1_1.exe] TBaseThreadWriteSocket.SetTimeout (CIS_TThreadWrappedIndySocket.pas, line 587)
:00411FD9 [CBusToolkit1_1.exe] TMultiReadExclusiveWriteSynchronizer.EndWrite (sysutils.pas, line 7103)
:00649DB7 [CBusToolkit1_1.exe] TBaseThreadWriteSocket.WriteBuffer_EndWrite (CIS_TThreadWrappedIndySocket.pas, line 463)
:00649F7B [CBusToolkit1_1.exe] TBaseThreadWriteSocket.WriteLine (CIS_TThreadWrappedIndySocket.pas, line 525)
:0064A6C4 [CBusToolkit1_1.exe] TThreadCommandSocket.ProcessCommand (CIS_TThreadWrappedIndySocket.pas, line 825)
:00648BB3 [CBusToolkit1_1.exe] TcgConnectionAdministrator.SendCommand (CIS_TcgConnectionAdministrator.pas, line 42)
:0052E2DB [CBusToolkit1_1.exe] InternalSendCommand (CIS_TCGateCommand.pas, line 201)
:0052E3ED [CBusToolkit1_1.exe] TCGateCommand.CommandExecute (CIS_TCGateCommand.pas, line 240)
:0040288F [CBusToolkit1_1.exe] TryHarder (GETMEM.INC, line 946)
:00402A99 [CBusToolkit1_1.exe] SysGetMem (GETMEM.INC, line 1023)
:00402ABC [CBusToolkit1_1.exe] SysGetMem (GETMEM.INC, line 1026)
:00403075 [CBusToolkit1_1.exe] ReallocMem (system.pas, line 1281)
:0040792F [CBusToolkit1_1.exe] DynArraySetLength (system.pas, line 10450)
:00403EC2 [CBusToolkit1_1.exe] AfterConstruction (system.pas, line 4207)
:00411E5A [CBusToolkit1_1.exe] TMultiReadExclusiveWriteSynchronizer.Create (sysutils.pas, line 7051)
:00403E8D [CBusToolkit1_1.exe] ClassCreate (system.pas, line 4171)
:00403EC2 [CBusToolkit1_1.exe] AfterConstruction (system.pas, line 4207)
:0052E7DC [CBusToolkit1_1.exe] TThreadCommandSynchroniser.Create (CIS_TCGateCommand.pas, line 422)
:00403E8D [CBusToolkit1_1.exe] ClassCreate (system.pas, line 4171)
:004EF0E9 [CBusToolkit1_1.exe] TFlashEntityManager.ResolveChange (CIS_TCustomFlashObject.pas, line 3656)
:004EE175 [CBusToolkit1_1.exe] TCISAttribute.ResolveChange (CIS_TCustomFlashObject.pas, line 3121)
:00534BEE [CBusToolkit1_1.exe] TStringAttribute.GetAsString (CIS_TStringAttribute.pas, line 95)
:00543E36 [CBusToolkit1_1.exe] TProjectCGateAgent.ProjectIdentifier (CIS_TProjectCGateAgent.pas, line 100)
:00544B67 [CBusToolkit1_1.exe] TProjectCGateAgent.CommandProjectSave (CIS_TProjectCGateAgent.pas, line 372)
:0054474C [CBusToolkit1_1.exe] TProjectCGateAgent.SaveProject (CIS_TProjectCGateAgent.pas, line 280)
:00544036 [CBusToolkit1_1.exe] TProjectCGateAgent.AgentSave (CIS_TProjectCGateAgent.pas, line 156)
:005327B4 [CBusToolkit1_1.exe] TPersistableObject.StorageSave (CIS_TIdentifiableObject.pas, line 96)
:006363D7 [CBusToolkit1_1.exe] TCBusNetwork.CheckStandardConfiguration (CIS_TCommonCBus.pas, line 2503)
:006FD55B [CBusToolkit1_1.exe] TnmNetwork.OnNodeExpand (CIS_TnmNetwork.pas, line 223)
:005B6A9F [CBusToolkit1_1.exe] TExplorerManager.TreeNodeExpand (CIS_TExplorerManagerUnit.pas, line 1684)
:005B6B43 [CBusToolkit1_1.exe] TExplorerManager.TreeViewExpanding (CIS_TExplorerManagerUnit.pas, line 1705)
:0048FAFB [CBusToolkit1_1.exe] TCustomTreeView.CanExpand (comctrls.pas, line 8328)
:0048FAC4 [CBusToolkit1_1.exe] TCustomTreeView.Expand (comctrls.pas, line 8323)
:0048C017 [CBusToolkit1_1.exe] TTreeNode.DoCanExpand (comctrls.pas, line 6283)
:0048C10F [CBusToolkit1_1.exe] TTreeNode.ExpandItem (comctrls.pas, line 6316)
:0048C1A5 [CBusToolkit1_1.exe] TTreeNode.Expand (comctrls.pas, line 6338)
:006FC3B2 [CBusToolkit1_1.exe] TnmProject.OnStartProject (CIS_TnmProject.pas, line 499)
:00508151 [CBusToolkit1_1.exe] TTBCustomItem.Click (TB2Item.pas, line 1350)
:00508096 [CBusToolkit1_1.exe] TTBCustomItem.ClickWndProc (TB2Item.pas, line 1318)
:00463D1E [CBusToolkit1_1.exe] StdWndProc (Forms.pas, line 1459)
:77E11EF0 [user32.dll]
:77E1204C [user32.dll]
:77E117A0 [user32.dll]
:77E15E6E [user32.dll]
:77E15F69 [user32.dll]
:0046EA59 [CBusToolkit1_1.exe] TApplication.ProcessMessage (Forms.pas, line 6630)
:0046EAA0 [CBusToolkit1_1.exe] TApplication.HandleMessage (Forms.pas, line 6649)
:0046B08D [CBusToolkit1_1.exe] TCustomForm.ShowModal (Forms.pas, line 4692)
:0046B11B [CBusToolkit1_1.exe] TCustomForm.ShowModal (Forms.pas, line 4700)
:0046B1C7 [CBusToolkit1_1.exe] TCustomForm.ShowModal (Forms.pas, line 4714)
:0046B1E7 [CBusToolkit1_1.exe] TCustomForm.ShowModal (Forms.pas, line 4714)
:0051346F [CBusToolkit1_1.exe] TDialogDirector.Direct (CIS_TDialogDirector.pas, line 127)
:005134BB [CBusToolkit1_1.exe] TDialogDirector.Direct (CIS_TDialogDirector.pas, line 135)
:77E13869 [user32.dll]
:77E177F4 [user32.dll]
:77E17803 [user32.dll]
:0040288F [CBusToolkit1_1.exe] TryHarder (GETMEM.INC, line 946)
:00402E9F [CBusToolkit1_1.exe] ResizeInPlace (GETMEM.INC, line 1198)
:0040C2DD [CBusToolkit1_1.exe] FileExists (sysutils.pas, line 2882)
:0064AD54 [CBusToolkit1_1.exe] TddMainFormDialogDirector.Direct (CIS_TddMainFormDialogDirector.pas, line 26)
:00504C70 [CBusToolkit1_1.exe] TApplicationManager.Run (CIS_TApplicationManager.pas, line 162)
:00504CB7 [CBusToolkit1_1.exe] TApplicationManager.Run (CIS_TApplicationManager.pas, line 167)
:00738EF1 [CBusToolkit1_1.exe] TamgKipper.Run (CIS_TamgKipper.pas, line 413)
:007C078E [CBusToolkit1_1.exe] initialization (prjKipper.dpr, line 56)
:007C07A4 [CBusToolkit1_1.exe] initialization (prjKipper.dpr, line 56)
:7C59893D [kernel32.dll]

--------------------------------------------------------------------------------
REGISTERS
--------------------------------------------------------------------------------
Main Thread ID = 00000610, Current Thread ID = 00000610
Registers:
EAX = 0012F7F0 CS = 001B EIP = 7C59BBF3 Flags = 00000202
EBX = 01766CB8 SS = 0023 ESP = 0012F7E8 EBP = 0012F840
ECX = 00000000 DS = 0023 ESI = 0012F874 FS = 003B
EDX = 0052EC1C ES = 0023 EDI = 0012F820 GS = 0000
Code at CS:EIP
5F 5E C9 C2 10 00 8B 4C 24 04 A1 F0 A1 5C 7C 89
Stack:
01766CB8 017806C4 0EEDFADE 00000001 00000000
00000000 00000000 7C59893D 00403A05 034AEF54
0042690B 017796D0 0000000B 00000000 034AE640
7C59893D FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF

 

Jannie.. thanks for the additional tests.. obviously its hard from a distance trying to diagnose the issue, I'm not trying to 'sell' you an excuse however.

What am I going to do (if you're willing) is send you a special build of the Toolkit Software that will generate a Log file of communications between Toolkit/CGate/CBus that should get us to the bottom of the problem a little faster..

Would that be OK? Your site obviously gives us a chance to fix a significant problem.

I will email you a link to download this new executable in the next 24hrs and instructions on what log to send back to us.

 

Duncan, will gladly run the software and send logs back.

Asleigh, when we originally built this network (2-3 years ago), we had lots of comms problems. Had to break the network into 3 seperate networks and use hardware burdens to stabilise the comms.

Ever since it's been very stable with no problem for C-Gate 1.5 and V2 to read the network.

Duncan, I'll install V2 on the same box and see what it does.

 

Just installed 2.7.7 on the same box and with everything else running the way it always run, i.e. C-Gate 1.5 active, it scanned all 3 networks without a problem.

Thus the only variable is the new software.

 

Thanks Jannie,

Download link for special build and instructions emailed to you.

 

Installed the software and mailed you a few logs.

The build you sent me (125) seems to be much more stable that 124 I had installed before. Murphy's law or are there substantial improvements?

It still crashes but I can now scan all three networks, and in general work with the application.

 

Got the logs Jannie, many thanks, we will be examining them today. Build 125 is essentially the 'tip' of the development build. Because we've been working away since the 1.1.4 release some defects have been repaired.. but nothing that would explain the puzzling problems you've had..

Will get back to you about the logs!

 

It definitely is MUCH more stable. Unless the installation of 2.7.7 (last thing I did before loading 125) did something.

I've been able to work most of today on the system as long as I'm carefull not to invoke certain functions, like deleting a unit from the db.

 

Something strange going on here:

1) Started with clean system
2) Load 1.1.4 - 124 - Terrible stability issues
3) Load 2.7.7 - runs fine
4) load 1.1.4 - 125 - much more stable with occasional crash
5) revert to 124 - even more stable (after hour or so testing). Managed to do all the deletes I needed to do with no crashes.

I get the impression, the more I use the system, the more stable it becomes....maybe a db issue?

I'll put my head on a block that nothing else in the environment changed.

 

Hmm interesting.. I honestly cant point to anything in Build 125 that would explain your increase in stability.. Puzzled.

One of the key differences between V2 and Toolkit is that we are driving the PCI much harder and invoking modes in it that 2.7.7 doesnt even know about. Running 2.7.7 might have resulted in the PCI falling back to a more 'vanilla' mode. But the first scan that Build 125 SHOULD have resulted in the all neat features in the PCI being turned on again.

I'll dig into it more on Monday. Thanks for the update.