[omniORB] 'Debug Assertion Failed!' on calling ns bind

[Leslie Chemwolo]

Hi,
I have configured in registry to have omniNames run on port 2809. When I run the server when omniNames is not running?I get TRANSIENT exception (which is expected), but when omniNames is running I get the error below when I attempt to bind the server object to the name server (calling ncRef->bind(objectName,obj)).?I am using WinXP. Please point me to what I did wrong to experience this difficulty with binding an object to the omniNames. I tested the same on JacORB name server and experienced the same thing- TRANSIENT when ns not started and error below when ns is up.
Debug Assertion Failed!
Program:...eMonitorCPP\SpaceInfoSourceImpl\Debug\SpaceInfoSourceImpl.exe
File: dbgdel.cpp
Line: 47
Expression: _BLOCK_TYPE_IS_VALID(PHead->nBlockUse)
For information on how your program can cause an assertion failure, see the Visual C++ documentation on asserts.
(Press Retry to debug the application)
Abort????????????? Retry????????????? Ignore
best rgds,
Leslie

[Leslie Chemwolo]

I get the following messages on running omniNames with ORBtraceLevel 25 -ORBtraceInvocations 1 -ORBtraceThreadId 1 -ORBtraceTime 1
It mentions 'omniRemoteIdentity deleted' at some point. What could be the cause of the problem? I am new to omniORB.
omniORB: (1) 2008-05-15 14:08:08.953000: Server accepted connection from giop:tc
p:127.0.0.1:2941
omniORB: (2) 2008-05-15 14:08:08.953000: AsyncInvoker: thread id = 2 has started
. Total threads = 3
omniORB: (2) 2008-05-15 14:08:08.953000: Scavenger task execute.
omniORB: (3) 2008-05-15 14:08:08.953000: AsyncInvoker: thread id = 3 has started
. Total threads = 3
omniORB: (3) 2008-05-15 14:08:08.953000: giopWorker task execute.
omniORB: (3) 2008-05-15 14:08:08.953000: Accepted connection from giop:tcp:127.0
.0.1:2941 because of this rule: "* unix,ssl,tcp"
omniORB: (3) 2008-05-15 14:08:08.953000: inputMessage: from giop:tcp:127.0.0.1:2
941 100 bytes
omniORB: (3) 2008-05-15 14:08:08.953000: Dispatching remote call '_is_a' to: key
<NameService> (active)
omniORB: (3) 2008-05-15 14:08:08.953000: sendChunk: to giop:tcp:127.0.0.1:2941 2
5 bytes
omniORB: (3) 2008-05-15 14:08:08.953000: inputMessage: from giop:tcp:127.0.0.1:2
941 276 bytes
omniORB: (3) 2008-05-15 14:08:08.953000: Dispatching remote call 'bind' to: key<
NameService> (active)
omniORB: (3) 2008-05-15 14:08:08.953000: Creating ref to remote: root/spaceInfoP
ersistentPOA<SpaceInfoGenerator>
?target id????? : IDL:omg.org/CORBA/Object:1.0
?most derived id: IDL:generator/SpaceInfoSource:1.0
omniORB: (3) 2008-05-15 14:08:08.953000: omniRemoteIdentity deleted.
omniORB: (3) 2008-05-15 14:08:08.953000: ObjRef(IDL:generator/SpaceInfoSource:1.
0) -- deleted.
omniORB: (3) 2008-05-15 14:08:08.953000: sendChunk: to giop:tcp:127.0.0.1:2941 8
1 bytes
omniORB: (3) 2008-05-15 14:08:14.375000: Error in network receive (start of mess
age): giop:tcp:127.0.0.1:2941
omniORB: (3) 2008-05-15 14:08:14.375000: throw giopStream::CommFailure from giop
Stream.cc:874(0,NO,COMM_FAILURE_UnMarshalArguments)
omniORB: (3) 2008-05-15 14:08:14.375000: Server connection refcount = 1
omniORB: (3) 2008-05-15 14:08:14.375000: Server connection refcount = 0
omniORB: (3) 2008-05-15 14:08:14.375000: Server close connection from giop:tcp:1
27.0.0.1:2941
omniORB: (3) 2008-05-15 14:08:24.375000: AsyncInvoker: thread id = 3 has exited.
?Total threads = 3

----- Original Message ----
From: Leslie Chemwolo <***@yahoo.com>
To: omniorb-***@omniorb-support.com
Sent: Thursday, May 15, 2008 12:46:16 PM
Subject: [omniORB] 'Debug Assertion Failed!' on calling ns bind

Hi,
I have configured in registry to have omniNames run on port 2809. When I run the server when omniNames is not running?I get TRANSIENT exception (which is expected), but when omniNames is running I get the error below when I attempt to bind the server object to the name server (calling ncRef->bind(objectName,obj)).?I am using WinXP. Please point me to what I did wrong to experience this difficulty with binding an object to the omniNames. I tested the same on JacORB name server and experienced the same thing- TRANSIENT when ns not started and error below when ns is up.
Debug Assertion Failed!
Program:...eMonitorCPP\SpaceInfoSourceImpl\Debug\SpaceInfoSourceImpl.exe
File: dbgdel.cpp
Line: 47
Expression: _BLOCK_TYPE_IS_VALID(PHead->nBlockUse)
For information on how your program can cause an assertion failure, see the Visual C++ documentation on asserts.
(Press Retry to debug the application)
Abort????????????? Retry????????????? Ignore
best rgds,
Leslie

[Duncan Grisby]

Post by Leslie Chemwolo
I have configured in registry to have omniNames run on port 2809. When
I run the server when omniNames is not running?I get TRANSIENT
exception (which is expected), but when omniNames is running I get the
error below when I attempt to bind the server object to the name
server (calling ncRef->bind(objectName,obj)).?I am using WinXP. Please
point me to what I did wrong to experience this difficulty with
binding an object to the omniNames. I tested the same on JacORB name
server and experienced the same thing- TRANSIENT when ns not started
and error below when ns is up.
Debug Assertion Failed!
Program:...eMonitorCPP\SpaceInfoSourceImpl\Debug\SpaceInfoSourceImpl.exe
File: dbgdel.cpp
Line: 47
Expression: _BLOCK_TYPE_IS_VALID(PHead->nBlockUse)

You are mixing debug application code with non-debug versions of the
omniORB libraries. You must match the debugging settings to cope with
the Windows non-uniform memory model.

Cheers,

Duncan.