[Ray Konopka]

Hi Ricardo,
We’ve received a couple reports of issues with the IDIOHANDLER object file. The odd thing about this is that the IdIOHandler unit is part of the Indy components that come with Delphi and C++Builder. CodeSite uses the Indy components to send CodeSite messages via TCP.
One thing to try is to add the following to your DLL project:
#include
Ray

[Ray Konopka]

Hi Steve,
Do you mean the TRzTabSheet controls used in the TRzPageControl? What are you trying to accomplish with your interface?
There is no Transparent property of the TRzTabSheet because frankly, transparency in the VCL is pretty much a hack or a simulation at best. And the structure of a page control (with embedded) tab sheets makes that even more complicated.
You may be able to get the effect you are wanting by handling the painting events of the TRzPageControl. I did this for a project I worked on years ago. I can try to dig up the code, if it is similar to what you are trying to accomplish.
Ray

[Ray Konopka]

Hi Steve,
I’m sorry, but I missed your follow-up message. You can send your screenshot to support@raize.com and I’ll take a look. Also, what version of Delphi are you using and which version of KSVC? I just noticed that that your subject references KSVC6. Is that correct?
Ray

[Ray Konopka]

Hi Steve,

There are a couple of ways you can override the current VCL Style in a TRzPanel. The first is to change the VisualStyle property from vsWinXP to vsClassic or vsGradient. vsWinXP means that the panel is drawn using the current Style, which was first introduced in Windows XP (hence the enum name). When you change VisualStyle to vsClassic or vsGradient, the various Color properties in the TRzPanel take effect.

Another option is to remove the seClient element from the StyleElements set. This has the same effect as switching the VisualStyle property. StyleElements is a base VCL property that was added many years after the VisualStyle property was added to the TRzPanel, which is why both properties are available in the control.

Ray

[Ray Konopka]

Hi Peter,
I apologize for the delay in responding. Please remove the seClient value from the StyleElements property of the list box. One significant area of focus for KSVC 8 was to provide better support for the StyleElements property. This is one of those cases.

Ray

[Ray Konopka]

Thanks for jumping in Ian!
Ray

[Ray Konopka]

Hi,
Please download the latest version of KSVC (i.e. version 8) and see if you still have issues.

Ray

[Ray Konopka]

160 messages per second is a bit high. For short bursts, that should not cause any issues, but if this rate was over a longer time period, it could certainly put an extra strain on the dispatcher.

You mention that the Out of Memory error is happening on your client’s machine. I’m curious if you have seen this same behavior on your machine? I’m curious as to the memory capacity of the client machine.

Ray

[Ray Konopka]

Hi Hans,
I’m not sure what happened to your message content. I received the message content in the notification message (now that I have them turned back on). I’ve included it below.

Are you able to send me some of the log files? If so, please zip them up and send them to support@raize.com.

Also, are you using the MaxSize and MaxParts properties to control the size of the log files? Or, are you doing that yourself?

The Dispatcher does have an internal queue that new messages are put into when they arrive. The load on the Dispatcher is reflected in the tray icon for the Dispatcher, if you have that visible. The interior of the icon shows varying shades of yellow to indicate load. There is no way to programmatically acquire the Dispatcher load.

What types of data are you capturing in CodeSite? Simple data types, or objects, images, etc. I can also get this from the sample log files, if you are able to send them to me.

Ray

>>>>
Hi Ray,

My client experienced a few ‘Out of Memory’ Pop-ups from the Dispatcher.

Today I received the *.csl files to have a look at and I did notice something.

The logging files are restricted to 10Mbytes, if larger then I start a new file.
Usually, the last entry in the file has the same timestamp as the file itself, which makes sense.
But now I noticed that gradually the timestamp of the last message is earlier than the timestamp of the file.

So I suspect that the Dispatcher is not keeping up with the rate of messages that it receives.
And this increasing backlog of messages probably is eating up the memory?

Is there a way that I can detect that this is happening?
So maybe I can tune the amount of messages that I am sending?

Kind regards,
Hans
<<<<

[Ray Konopka]

Hi Hans,

I’m sorry for the long delay. Somehow my notifications got turned off. CodeSite Studio 5 is sold as a traditional license and not an annual subscription. There is no charge for updates to the same major version.

Ray

[Ray Konopka]

Hi Hans,

Interesting question. There is no built-in way to get that information, but we can leverage the SendFileVersionInfo method in the TCodeSiteLogger. For example, the following code shows how to get the file path to the CSDispatcher.exe from the Registry and then use the SendFileVersionInfo method to send the version info the CodeSite destination. The version number is listed in the details. Perhaps this will help until I can put something a little more elegant into the product.

Ray

uses
  System.Win.Registry,
  CodeSiteLogging,
  CodeSitePlatform;

procedure TForm45.RzButton1Click(Sender: TObject);
var
  R: TRegistry;
  DispatcherFileName: string;
begin
  R := TRegistry.Create;
  try
    R.RootKey := HKEY_LOCAL_MACHINE;
    if R.OpenKeyReadOnly( CodeSiteRegKey ) then
      DispatcherFileName := R.ReadString( 'Dispatcher' )
    else if R.OpenKeyReadOnly( CodeSitePoliciesRegKey ) then
      DispatcherFileName := R.ReadString( 'Dispatcher' );
    R.CloseKey;
  finally
    R.Free;
  end;

  if DispatcherFileName = '' then
    DispatcherFileName := StrDispatcherExeName;

  CodeSite.SendFileVersionInfo( DispatcherFileName );
end;

[Ray Konopka]

Hi,

By default the CodeSite Dispatcher monitors the TCP and UDP ports. In an older version it was possible to toggle the Monitor Ports option in the Dispatcher Settings, but we removed that. However, the CSDispatcher.ini file still holds the setting for those who wish to turn it off.

Anyway, please check the C:\ProgramData\Raize\CodeSite\5.0\CSDispatcher.ini file and see if the MonitorPorts setting is turned off. If so, then simply set it to true and restart the Dispatcher.

Ray

[Ray Konopka]

Hi David,

I sent you an email reply (to the CSDispatcherLog.txt file) on Jan 15. I’ve included the email contents below.

Ray

—-
Hi David,

The CSDispatcherLog.txt file that you sent looks fine. The multiple Register calls are fine. I was really interested in seeing if there were any errors being recorded in the CSDispatcherLog.txt file.

What is also strange is that your most recent forum post on this topic mentions that the log file is now 28 GB in size. Are there other log file “parts” on the computer? Is it the last part that is growing?

What version of CodeSite do you have installed on this computer?

Ray

[Ray Konopka]

Hi David,

I just created a quick test project in Delphi 11 and created the following event handler:

procedure TForm13.RzButton1Click(Sender: TObject);
begin
  CodeSite.TraceMethod( 'RzButton1Click' );
  CodeSite.Send( 'Test Message' );
  CodeSite.Send( 'Test Message #2' );
end;

I ran the program and the output showed the two test messages within an EnterMethod message and an ExitMethod message.

Are you able to duplicate the problem in a test project? If so, please send the source (no executables) to support@raize.com and I’ll take a look.

Ray

[Ray Konopka]

Hi David,

Unfortunately, there is no built in way to search or filter on exit methods that exceed some time threshold, but it would be nice feature. I’m logging it as an enhancement request.

Ray

[Author]

Posts