DBMonitor 3.0 produces a lot of handled Exceptions
DBMonitor 3.0 produces a lot of handled Exceptions
Hi devart team,
i am using the new dbMonitor for tracing.
The Monitor produces a lot of catched exceptions.
Is this possible to avoid??
(It can only be first chance catched, if Debugging with not only my code switch on)
A lot of first chance exceptions running to the output window
Eine Ausnahme (erste Chance) des Typs "System.Net.Sockets.SocketException" ist in System.dll aufgetreten.
Eine Ausnahme (erste Chance) des Typs "System.Net.Sockets.SocketException" ist in System.dll aufgetreten.
Eine Ausnahme (erste Chance) des Typs "System.InvalidOperationException" ist in Devart.Data.dll aufgetreten.
Eine Ausnahme (erste Chance) des Typs "System.Net.Sockets.SocketException" ist in System.dll aufgetreten.
Eine Ausnahme (erste Chance) des Typs "System.Net.Sockets.SocketException" ist in System.dll aufgetreten.
Eine Ausnahme (erste Chance) des Typs "System.InvalidOperationException" ist in Devart.Data.dll aufgetreten.
Exception:
System.Net.Sockets.SocketException
Es konnte keine Verbindung hergestellt werden, da der Zielcomputer die Verbindung verweigerte 127.0.0.1:1000
10061
System.Net.Sockets.SocketError.ConnectionRefused
Stack:
> System.dll!System.Net.Sockets.TcpClient.Connect(string hostname, int port) + 0x2de Bytes
Devart.Data.dll!Devart.DbMonitor.o.h() + 0x185 Bytes
Devart.Data.dll!Devart.DbMonitor.l.f() + 0x102 Bytes
Devart.Data.dll!Devart.DbMonitor.l.e() + 0x2c Bytes
Devart.Data.dll!Devart.Common.y.a() + 0x151 Bytes
mscorlib.dll!System.Threading.ThreadHelper.ThreadStart_Context(object state) + 0x66 Bytes
mscorlib.dll!System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, object state) + 0x6f Bytes
mscorlib.dll!System.Threading.ThreadHelper.ThreadStart() + 0x44 Bytes
Tnx
Roman
i am using the new dbMonitor for tracing.
The Monitor produces a lot of catched exceptions.
Is this possible to avoid??
(It can only be first chance catched, if Debugging with not only my code switch on)
A lot of first chance exceptions running to the output window
Eine Ausnahme (erste Chance) des Typs "System.Net.Sockets.SocketException" ist in System.dll aufgetreten.
Eine Ausnahme (erste Chance) des Typs "System.Net.Sockets.SocketException" ist in System.dll aufgetreten.
Eine Ausnahme (erste Chance) des Typs "System.InvalidOperationException" ist in Devart.Data.dll aufgetreten.
Eine Ausnahme (erste Chance) des Typs "System.Net.Sockets.SocketException" ist in System.dll aufgetreten.
Eine Ausnahme (erste Chance) des Typs "System.Net.Sockets.SocketException" ist in System.dll aufgetreten.
Eine Ausnahme (erste Chance) des Typs "System.InvalidOperationException" ist in Devart.Data.dll aufgetreten.
Exception:
System.Net.Sockets.SocketException
Es konnte keine Verbindung hergestellt werden, da der Zielcomputer die Verbindung verweigerte 127.0.0.1:1000
10061
System.Net.Sockets.SocketError.ConnectionRefused
Stack:
> System.dll!System.Net.Sockets.TcpClient.Connect(string hostname, int port) + 0x2de Bytes
Devart.Data.dll!Devart.DbMonitor.o.h() + 0x185 Bytes
Devart.Data.dll!Devart.DbMonitor.l.f() + 0x102 Bytes
Devart.Data.dll!Devart.DbMonitor.l.e() + 0x2c Bytes
Devart.Data.dll!Devart.Common.y.a() + 0x151 Bytes
mscorlib.dll!System.Threading.ThreadHelper.ThreadStart_Context(object state) + 0x66 Bytes
mscorlib.dll!System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, object state) + 0x6f Bytes
mscorlib.dll!System.Threading.ThreadHelper.ThreadStart() + 0x44 Bytes
Tnx
Roman
-
- Devart Team
- Posts: 1710
- Joined: Thu 03 Dec 2009 10:48
DBMonitor 3.0 produces a lot of handled Exceptions
Hi Stanislav,
I can not say, why the DB-Monitor try a socket connection to the local loopback adapter? 127.0.0.0:1000 on Port 1000??
On my machine is also a local oracle installed, but the current traced session does not connect local, only to a remote oracle.
Is it so difficult to look to the not dotfuscated code documented in the previous stack??
I think, this error comes with the new 3.0 Version, so there must be some change in that dll?
The exception is catched by devart code, but if you can, you should avoid exceptions!
So your team should investigate some time to find a solution or an explanation.
Tnx,
Roman
I can not say, why the DB-Monitor try a socket connection to the local loopback adapter? 127.0.0.0:1000 on Port 1000??
On my machine is also a local oracle installed, but the current traced session does not connect local, only to a remote oracle.
Is it so difficult to look to the not dotfuscated code documented in the previous stack??
I think, this error comes with the new 3.0 Version, so there must be some change in that dll?
The exception is catched by devart code, but if you can, you should avoid exceptions!
So your team should investigate some time to find a solution or an explanation.
Tnx,
Roman
-
- Devart Team
- Posts: 1710
- Joined: Thu 03 Dec 2009 10:48
It seems that you are using an active OracleMonitor object in your application while dbMonitor.exe is not started. In this case, your application tries to connect dbMonitor.exe and throws exceptions.
If you are encountering the problem in some other scenario, please specify the steps needed to reproduce the issue.
If you are encountering the problem in some other scenario, please specify the steps needed to reproduce the issue.
DBMonitor 3.0 produces a lot of handled Exceptions
Hi Stanislav,
yes, I have not started the DBMonitor and this is ok for my tests!.
I am only using the event OracleMonitor.TraceEvent for my own tracing.
(Writing my own logfile and measure performances etc.)
I do not need and do not active try to connect to DBMonitor, this is tryed internal by devart as you can see on the stack.
Is this avoidable? (Can I set any Flag in the monitor???)
(Or should you spent the monitor one?)
Tnx,
Roman
yes, I have not started the DBMonitor and this is ok for my tests!.
I am only using the event OracleMonitor.TraceEvent for my own tracing.
(Writing my own logfile and measure performances etc.)
I do not need and do not active try to connect to DBMonitor, this is tryed internal by devart as you can see on the stack.
Is this avoidable? (Can I set any Flag in the monitor???)
(Or should you spent the monitor one?)
Tnx,
Roman
-
- Devart Team
- Posts: 1710
- Joined: Thu 03 Dec 2009 10:48
-
- Devart Team
- Posts: 1710
- Joined: Thu 03 Dec 2009 10:48
-
- Devart Team
- Posts: 1710
- Joined: Thu 03 Dec 2009 10:48
The new 5.55.97 Beta build of dotConnect for Oracle is available now. It can be downloaded from
http://www.devart.com/dotconnect/oracle/download.html
(trial version) or from Registered Users' Area (for users with active subscription only). For more information, please refer to
http://www.devart.com/forums/viewtopic.php?t=17143
http://www.devart.com/dotconnect/oracle/download.html
(trial version) or from Registered Users' Area (for users with active subscription only). For more information, please refer to
http://www.devart.com/forums/viewtopic.php?t=17143