COM+ /Oracle To Bug report or not to bug report

Hi guys,

I've having a bunch of problems using COM+ with Oracle 9.2 and ODPNET9202102.exe under .NET Framework 1.0 sp1/windows 2000 server.

Some problems are interesting, some are not. For some I have a c# code file that easily reproduces the problem, some problems aren't that easy to reproduce

What I'm wondering is if there is a process for bug report for such (nearly ancient) technologies and what would be the chance of success to resolving those bugs?

All problems revolve around COM+ transactions with ADO.NET Connection pooling (just doesn't work right), plus COM+ automatic component registraion (bunch of m_punk errors in Event Log for which google yields 5 answers only).

I can always go through the official channels of filing that bug though my current employer, but that would mean that the paperwork will span over the existing release schedule. On top of that, even if there would be a patch resolving those issues from either of vendors, our production team will never agree to retest them on production environment.

Any help will be greatly appreciated.

[1093 byte] By [B0rG] at [2008-1-28]
# 1
B0rG wrote:
Hi guys,

I've having a bunch of problems using COM+ with Oracle 9.2 and ODPNET9202102.exe under .NET Framework 1.0 sp1/windows 2000 server.

Some problems are interesting, some are not. For some I have a c# code file that easily reproduces the problem, some problems aren't that easy to reproduce

What I'm wondering is if there is a process for bug report for such (nearly ancient) technologies and what would be the chance of success to resolving those bugs?

All problems revolve around COM+ transactions with ADO.NET Connection pooling (just doesn't work right), plus COM+ automatic component registraion (bunch of m_punk errors in Event Log for which google yields 5 answers only).

I can always go through the official channels of filing that bug though my current employer, but that would mean that the paperwork will span over the existing release schedule. On top of that, even if there would be a patch resolving those issues from either of vendors, our production team will never agree to retest them on production environment.

Any help will be greatly appreciated.

B0rG,

Have you tried the product feedback center at:

http://lab.msdn.microsoft.com/productfeedback/

If you are experiencing the problems with the beta of .NET 2.0, then this is a good way of getting that information into MS's hands sooner.

As far as your problem with COM+ distributed transactions and connection pooling, you arent keeping a connection open across transactions, are you (as well as having the object holding the connection being pooled)? Can you show a code sample of an object and how it is obtaining the connection (as well as with any attributes for object pooling, transactions, etc, etc).

Hope this helps.

- Nicholas Paldino [.NET/C# MVP]
- mvp@spam.guard.caspershouse.com

casperOne at 2007-8-21 > top of Msdn Tech,.NET Development,.NET Base Class Library...

.NET Development

Site Classified