[omniORB] Quite Strange problem.

[janarbek]

Quite strage thing happened to my program.

I did worked everything successfully with several interfaces. My Client and Server are sharing *Sk and *.h files into two separate projects in Visual C++.


So, Today, I made *.Sk and all necessary *.cpp *.h files into a library frameworkd.lib. Anda I included my my lib to Server and Client projects.

Server Worked fine but Client fails when it starts.

I am starting my client and Server with following argument

-ORBInitRef NameService=corbaloc::janarbek.:2809/NameService 8054


The code files in following function
void*
_objref_GlobalRef::_ptrToObjRef(const char* id)
{
if( id == ::GlobalRef::_PD_repoId )
return (::GlobalRef_ptr) this;

if( id == ::CORBA::Object::_PD_repoId )
return (::CORBA::Object_ptr) this;

if( omni::strMatch(id, ::GlobalRef::_PD_repoId) )
return (::GlobalRef_ptr) this;

if( omni::strMatch(id, ::CORBA::Object::_PD_repoId) )
return (::CORBA::Object_ptr) this;
return 0;
}

I really didn't understand why it fails,.............Anyone has this experience before? Strange thing is if I just include *Sk and *.h files it works fine and it fails with *.lib????

Regards
janar


---------------------------------
Check out the hottest 2008 models today at Yahoo! Autos.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.omniorb-support.com/pipermail/omniorb-list/attachments/20071001/b2fb2a7b/attachment.htm

[Thomas Lockhart]

Post by janarbek
I really didn't understand why it fails,.............Anyone has this
experience before? Strange thing is if I just include *Sk and *.h files
it works fine and it fails with *.lib????

What do you mean by "fails"? You have to be more specific. My guess is
that your library is missing components or your application is having
trouble finding the library. Or it is some M$ baloney with the build
environment.

hth

- Tom

[Sean Parker]

Hello -

I'm writing to ask if this bug:
"http://osdir.com/ml/corba.omniorb.user/2003-09/msg00034.html"
has officially been fixed in omniORB 4.1 or latest? I seem
to be experiencing this now and wonder if I must upgrade
(it's non-trivial to upgrade to latest version on our
system)

Thanks.
Sean





God Bless
Sean Parker






____________________________________________________________________________________
Building a website is a piece of cake. Yahoo! Small Business gives you all the tools to get online.
http://smallbusiness.yahoo.com/webhosting

[Duncan Grisby]

Post by Sean Parker
"http://osdir.com/ml/corba.omniorb.user/2003-09/msg00034.html"
has officially been fixed in omniORB 4.1 or latest? I seem
to be experiencing this now and wonder if I must upgrade
(it's non-trivial to upgrade to latest version on our
system)

That bug was fixed between 4.0.2 and 4.0.3:

http://omniorb.sourceforge.net/bugs/bugfixes-402.html

The fix is in 4.1.x as well, of course.

What version are you currently using?

Cheers,

Duncan.

[Peter Klotz]

Post by Sean Parker
"http://osdir.com/ml/corba.omniorb.user/2003-09/msg00034.html"
has officially been fixed in omniORB 4.1 or latest? I seem
to be experiencing this now and wonder if I must upgrade
(it's non-trivial to upgrade to latest version on our
system)

We have encountered a very similar bug in omniORB 4.0.7 (using Linux).
Tests showed that it is not present in 4.0.6.

When several clients connect in parallel to a server there is a chance
for sockets to remain in state CLOSE_WAIT forever.

I have narrowed the problem down to method
giopServer::removeConnectionAndWorker(giopWorker* w) in giopServer.cc.

Variable cs_removed never gets set to 1 since
Link::is_empty(cs->workers) always returns 0.

I am not 100% sure but I think the problem only occurred when all
clients were constantly calling the same method.

The problem did definitely not occur when only a single client
continuously called the same method. Therefore I would assume that some
kind of interaction between server side worker threads is responsible
for this problem.

So far I have not investigated if this issue still persists in omniORB
4.1.0.

Best regards, Peter.

[Duncan Grisby]

Post by Peter Klotz

Post by Sean Parker
"http://osdir.com/ml/corba.omniorb.user/2003-09/msg00034.html"
has officially been fixed in omniORB 4.1 or latest? I seem
to be experiencing this now and wonder if I must upgrade
(it's non-trivial to upgrade to latest version on our
system)

We have encountered a very similar bug in omniORB 4.0.7 (using
Linux). Tests showed that it is not present in 4.0.6.

If you can, please try with either omniORB 4.1.1, or failing that with
the latest CVS contents on the omni4_0_develop branch.

If you still see the issue, it would be great if you could try to come
up with a minimal example that exhibits the problem.

Cheers,

Duncan.