On 12 Jan, 07:44, "arun.da...@[EMAIL PROTECTED]
" <arun.da...@[EMAIL PROTECTED]
> wrote:
> On Dec 18 2007, 5:41 am, ap...@[EMAIL PROTECTED]
wrote:
> > On 17 Dec, 15:44, Mark Woyna <wo...@[EMAIL PROTECTED]
> wrote:
> > > On Dec 14, 11:02 am, ap...@[EMAIL PROTECTED]
wrote:
> > > > Occasionally (3 or 4 times times now in the last 3 months) orbixd
> > > > appears to go into CPU meltdown on our UAT machine. No-one can
fathom
> > > > why.
> I agree with Mark that using such a old version is not going to make
> thing easy for you.
You're right there.
> Based on what you said looks like ur using CORBA for an underlying c++
> app,
No. The rewritten app is in Java. OrbixWeb is for java apps, Orbix
(without the Web) is for C++ apps.
> i can recommed the following ORBs they are free and dont suffer
> from the crash issue ur faced with:
> TAO - ORB part of the ACE framework
> OmniORB - light weight and easy to use
> Orbit
These are C++ orbs so are no good for me. Besides, I said originally
that I used JacORB, an open source java ORB that works just fine
thankyou. But this HAS to be made to work with OrbixWeb.
> migrating to TAO or Omni should be very simple, you will find tones of
> info for this... u can always ping me if needed ;)
No need, thanks.
>
> But in case all you want to do is solve the meltdown... then try some
> of the thread monitoring or kernal monitoring utils... like
> VTune from Intel for Linux, Windows
These dont work or are not available on Solaris.
> Glance from HP for HPUX
HPUX, not Solaris.
>
> regards,
> Arun
|
