Re: [openorb-users] CPU Load Average Threshold Alarm due to corba

[L. K. <lk...@us...>]

Hi,


Scenario 1:
>

I don't think it's that helpful to repeat the same questions again and
again. Just write the new stuff you figured out. I don't want to waste my
time reading the same stuff over and over.


> [...]
>
>
>
> Ø      For Naming service, client(GUI) needs to ask ORB to get the server
> object reference and send request and get response, Server doesn't have
> knowledge about how ORB handle the details of communication, that is one of
> reasons why we use CORBA but not pure socket call.    *Is this statement
> is correct?*
>

Yes.


> **
>
>
>
> Ø      For Notification service, is there any configuration inside ORB
> which can let us to set the number of max threads*?  Is there Any Solution
> for this*.
>
>
Set maxThreadPoolSize in the openorb configuration file. And make sure that
you are using an appropriate threading strategy in the ORB / POA
configuration, not "thread per client".


>
>
> Ø      Is there any tool that can be used to identify the Corba threads
> and how it communicates on Solaris 9/10. how to check the name sevices and
> notification services are correct.
>
>
>

This is probably not a "Solaris only" problem. If you are having
difficulties getting a profiler to run (see below) you might be able to
reproduce this on Windows. If you can't do that, profiling tools typically
support remote profiling. Read your profilers documentation how to do that.


> I am getting the error .
>
>  [...]
> *No X11 DISPLAY variable was set, but this program performed an operation
> which requires it.*
>

Have you tried to paste this error message into the google search box?
Whenever I run across some error message, this strategy works quite well for
me...

A profiler is a GUI driven program, just like your IDE, so it needs to open
a window on your desktop. X11 is the GUI environment of Unix Systems.
Dedicated unix servers often don't have a GUI running and allow interaction
only via the command shell.  The stack trace says that YourKit is trying to
open a window and it failed because X11 is not there or not configured
correctly. If X11 is running, ask your sysadmin for help. If X11 is not
running, use one of the options I described above.

Regards,
Lars