> On Dec 14, 11:02 am, ap...@student.open.ac.uk wrote:
>
[quoted text clipped - 12 lines]
> number of issues you've encountered are roughly the same number I
> experienced nearly a decade ago. It's time to move on.
Indeed. I never argued that the choices were sane. Allowing the sw to
become so out of date wih the maintenance issues it has IMO is, ahem,
sub-optimal. But I have to make it work until they can migrate away
from CORBA completely.
> How is wasting your time saving your organization any money,
> especially when there are plenty of free orbs out there?
It's not my organisation - I'm a contractor. And I did use jacorb to
do most of the development, which was painless by comparison. I did
argue for using jacorb but lost that argument. I also lost the
argument to change to a much more recent version of Orbix even though
we got a VERY reasonable quote from IONA.
> As a general
> rule of thumb, many organizations take the 'if it isn't broke, don't
> fix it' route.
But it was broken (bugs and lack of robustness in the C++ app code).
And using such as ancient unsupported buggy mix of technologies they
brought me in the migrate them away from all that. Now the servers
have been rewritten in java and I am in the process of moving them off
CORBA.
> They're not going to throw out working software just
> for the sake of running the latest and greatest. However, it's quite
> clear here that it *is* broken, and it can't be fixed.
Yes it was broken but now the servers are rewritten in java things are
alot better. Now theres just the task of moving away from the CORBA. I
am in the intermediate stage where we have brand new java code and
people need to get that warm comfortable feeling that all the new code
is ok. Part of that is not having the change the clients at the same
time due to a change in the mechanisms for inter-process
communication.
> I know it's not your choice. I hope you're learning something valuable
> as you struggle through this.
I'm having a great time. My java has really improved and I am learning
it in the context of java enterprise technologies including JMS. I
have also had a play with swing. And I'm working with people I like.
And I've had the chance to renew some personal ties with the people at
IONA. Yes there have been struggles but its my job to make things
work. I have taken the approach of iterative incremental development
rather than big-bang. That's why there is CORBA for now.
Also, I think that CORBA is a good technology for the problem at hand,
it's the ancient version that is the problem. I did recommend that
they stay with CORBA but was overruled. The fact is that CORBA skills
are rare and expensive something cheaper and more maintainable is
needed in terms of finding the people to look after it. It took them
ages to find me :-)
> I wouldn't be that patient. If my
> organization saddled me with a crappy piece of code like OW, I'd have
> resigned ages ago.
I'm a contractor and will be saying goodbye in February :-)
> Mark
arun.darra@gmail.com - 12 Jan 2008 07:44 GMT
> > On Dec 14, 11:02 am, ap...@student.open.ac.uk wrote:
>
[quoted text clipped - 78 lines]
>
> - Show quoted text -
Hi,
I agree with Mark that using such a old version is not going to make
thing easy for you.
Based on what you said looks like ur using CORBA for an underlying c++
app, 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
migrating to TAO or Omni should be very simple, you will find tones of
info for this... u can always ping me if needed ;)
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
Glance from HP for HPUX
regards,
Arun
apm35@student.open.ac.uk - 22 Jan 2008 15:07 GMT
On 12 Jan, 07:44, "arun.da...@gmail.com" <arun.da...@gmail.com> wrote:
> > > On Dec 14, 11:02 am, ap...@student.open.ac.uk 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
marlow.andrew@googlemail.com - 07 Feb 2008 21:01 GMT
> > I guess I'm beating a dead horse here, but I have to question the
> > sanity of an organization that continues to suffer with an ancient,
[quoted text clipped - 6 lines]
> sub-optimal. But I have to make it work until they can migrate away
> from CORBA completely.
Not any more I don't. The system is reverting to the old C++ servers,
java is being removed from the equation.
> > How is wasting your time
Well, I have been paid, at least.
> > saving your organization any money,
> > especially when there are plenty of free orbs out there?
[quoted text clipped - 4 lines]
> argument to change to a much more recent version of Orbix even though
> we got a VERY reasonable quote from IONA.
And now I've lost the case for CORBA servers in java.
> > As a general
> > rule of thumb, many organizations take the 'if it isn't broke, don't
[quoted text clipped - 5 lines]
> have been rewritten in java and I am in the process of moving them off
> CORBA.
It's all off now. If java is ever reintroduced it will be with JMS
instead of CORBA.
> > They're not going to throw out working software just
> > for the sake of running the latest and greatest. However, it's quite
> > clear here that it *is* broken, and it can't be fixed.
>
> Yes it was broken but now the servers are rewritten in java things are
> alot better.
There were a few incidents of Orbix connectivity problems after this
move. The two events were connected. The conclusion was to remove the
java work.
> Now theres just the task of moving away from the CORBA. I
> am in the intermediate stage where we have brand new java code and
> people need to get that warm comfortable feeling that all the new code
> is ok.
They never got that warm comfortable feeling.It was running for 22
days.
> > I know it's not your choice. I hope you're learning something valuable
> > as you struggle through this.
>
> I'm having a great time.
Not any more.
> My java has really improved and I am learning
> it in the context of java enterprise technologies including JMS.
Well, that's something I gained.
> Also, I think that CORBA is a good technology for the problem at hand,
> it's the ancient version that is the problem. I did recommend that
> they stay with CORBA but was overruled.
This was a great pity, IMO.
> The fact is that CORBA skills
> are rare and expensive something cheaper and more maintainable is
[quoted text clipped - 6 lines]
>
> I'm a contractor and will be saying goodbye in February :-)
Only 7 working days left to go.
Mark Woyna - 11 Feb 2008 16:06 GMT
On Feb 7, 3:01 pm, marlow.and...@googlemail.com wrote:
> > > I guess I'm beating a dead horse here, but I have to question the
> > > sanity of an organization that continues to suffer with an ancient,
[quoted text clipped - 87 lines]
>
> Only 7 working days left to go.
Thanks for the update. I share your pain. You certainly can't be
faulted for not trying.
Since this is a CORBA newsgroup, I'll add this. I've been using Java/
CORBA successfully for over 10 years. We run the worlds largest
options exchange on a CORBA platform, written in Java. We process over
2 billion quotes a day.
I have to imagine that many within your company will point to this
fiasco as a failure of CORBA. I would say it's simply a failure of
management, not technology. The decision to stick with a old,
unsupported, buggy product when there are viable alternatives is a
100% management decision. It'll be interesting to see what they do in
the future when they have to integrate with a non-Java application.
Mark
apm35@student.open.ac.uk - 12 Feb 2008 13:42 GMT
> > > Indeed. I never argued that the choices were sane. Allowing the sw to
> > > become so out of date wih the maintenance issues it has IMO is, ahem,
> > > sub-optimal. But I have to make it work until they can migrate away
> > It's all off now. If java is ever reintroduced it will be with JMS
> > instead of CORBA.
> > There were a few incidents of Orbix connectivity problems after this
> > move. The two events were connected. The conclusion was to remove the
> > java work.
> > > Also, I think that CORBA is a good technology for the problem at hand,
> > > it's the ancient version that is the problem. I did recommend that
> > > they stay with CORBA but was overruled.
> Thanks for the update. I share your pain. You certainly can't be
> faulted for not trying.
[quoted text clipped - 3 lines]
> options exchange on a CORBA platform, written in Java. We process over
> 2 billion quotes a day.
Well, I believe in CORBA and IMO there is nothing wrong in using CORBA
wirh java.
> I have to imagine that many within your company will point to this
> fiasco as a failure of CORBA.
Looks that way.
> I would say it's simply a failure of
> management, not technology.
Yes.
> The decision to stick with a old,
> unsupported, buggy product when there are viable alternatives is a
> 100% management decision.
I did what I could, and so did IONA.
> It'll be interesting to see what they do in
> the future when they have to integrate with a non-Java application.
This place is 100% java so I don't think that will ever happen. If it
does then I may get another contract!
> Mark
FWIW, the Orbix connectivity problems we were only seeing in
production now seem to happen in our pre-UAT environment. So it looks
like the sickness is spreading.
Mark Woyna - 12 Feb 2008 15:47 GMT
On Feb 12, 7:42 am, ap...@student.open.ac.uk wrote:
> > > > Indeed. I never argued that the choices were sane. Allowing the sw to
> > > > become so out of date wih the maintenance issues it has IMO is, ahem,
[quoted text clipped - 39 lines]
> This place is 100% java so I don't think that will ever happen. If it
> does then I may get another contract!
Famous last words. No organization of any significant size stays
single language for long, if they ever manage to achieve it at all. If
they're successful, they're often buyout targets, and get gobbled up
by larger companies with their own systems and platforms. In your case
the company is moving away from C++ to Java. How long will it be until
a new management team comes along and decides on a new language? Java
is a fine language, but it won't be the last language we ever learn.
Lastly, what happens when they discover some new third-party
application that they just have to have, and it happens to be written
in C#?
Mark
> > Mark
>
> FWIW, the Orbix connectivity problems we were only seeing in
> production now seem to happen in our pre-UAT environment. So it looks
> like the sickness is spreading.
Rob Ratcliff - 13 Feb 2008 00:44 GMT
> Lastly, what happens when they discover some new third-party
> application that they just have to have, and it happens to be written
> in C#?
There is always web services! :->
Mark Woyna - 13 Feb 2008 14:41 GMT
> > Lastly, what happens when they discover some new third-party
> > application that they just have to have, and it happens to be written
> > in C#?
>
> There is always web services! :->
And the cycle of life completes, and starts all over again....
Mark
Rob Ratcliff - 14 Feb 2008 04:34 GMT
>>> Lastly, what happens when they discover some new third-party
>>> application that they just have to have, and it happens to be written
[quoted text clipped - 4 lines]
>
> Mark
....and ten times slower, less capable and more complex.... :-)