Socket Exception with OraSQLMonitor

[WZehntner]

Hi,

I am using Delphi XE2 Update 4 Hotfix 1.
Oracle Data Acces Components 8.6.12 for RAD Studio XE2

I get a Debugger-Exception caused by OraSQLMonitor-Component.
The component is on an empty Form.
The property Active is set to True.
The exception does not happen when dbMonitor.exe (Version 3.0.4) is running.
The exception does not happen when Active is set to false.

I do not always have dbMonitor running,
and I do not want to continually switch the Active-property between compiles.

The full Exception-Message (in German) is:
---------------------------
Benachrichtigung über Debugger-Exception
---------------------------
Im Projekt testserver.exe ist eine Exception der Klasse SocketException mit der Meldung 'Cannot connect to server on host 'localhost':
Es konnte keine Verbindung hergestellt werden, da der Zielcomputer die Verbindung verweigerte.
Socket Error Code: 10061($274D)' aufgetreten.
---------------------------

Is there a workaround ?

[AlexP]

Hello,

We have fixed this behaviour. From now, the moDBMonitor option value is False, and this error won't occur independently on whether DBMonitor is running or not. This fix will be included into the new version, which will be released this week.

[WZehntner]

Thanks a lot !
Looking forward to the new release.

[AlexP]

Hello,

The new version with this fix is already available for download at our website

[WZehntner]

I downloaded the new version.
The moDBMonitor option value is now by default False.
However, in order to monitor sessions, the value needs to be set to true.
When I set it to true (and DBMonitor is not running), I still get the same error
whenever I start my application from within the Delphi IDE.
Can you please explain how to solve this ?

[WZehntner]

Would be nice to know:
can you reproduce this behaviour ?
are you working on it ?
just let me know please

[AlexP]

Hello,

We have deliberately disabled the moDBMonitor option. Now, if you explicitly enable this option, it means you have also run DBMonitor; if you don't use DBMonitor, there is no sense to enable this option.

[WZehntner]

When I compile and step through my application, I usually don't have
dbmonitor running, therefore the moDBMonitor option is set to false.

When I want to deploy my application-exe, I would have to set the option to true
because I might use the dbmonitor with the exe, thus I would have to constantly
switch between those settings before compiling ...
What can you suggest ?

[AlexP]

Hello,

If the moDBMonitor option is set to True and the DBMonitor application is not running, the error will occur only when starting the IDE; if the application is run via the EXE file, the error will not occur independently on whether DBMonitor is running or not