[ic] Verisign, double, tripe charges, orders not going through IC

[Ron Phipps]

> From: interchange-users-admin@interchange.redhat.com
[mailto:interchange-
> users-admin@interchange.redhat.com] On Behalf Of mheins@redhat.com
> 
> Quoting Ron Phipps (rphipps@reliant-solutions.com):
> > > [snip]
> > > Remember all bugs are not Interchange. 8-\ If you didn't know,
> > > thousands of bugs have been fixed in Perl and Linux in the last
two
> > > years.
> >
> > I know this :)  And once again I apologize if you took my message as
an
> > attack on IC.  You know that I'm very thankful for the software that
you
> > have provided and do not take it for granted.  I got tied up in the
> > moment of finding a quick fix instead of looking at the situation
from
> > further away.  Those things happen when a launch goes bad and sales
are
> > being lost ;)
> >
> 
> I didn't see it as an attack -- but it is easy to lose site of how
much
> a system depends on all its parts. I was trying to bring that out, and
> trying to emphasize how much Interchange depends on its underlying
> platform. Did you mention a multi-CPU system? I am not sure. If you
have
> a multi-CPU system, then that applies 10 times over.

And I did lose site of the underlying system which IC relies on.  We
actually are running on two cpus which definitely complicates matters
more.

> All that being said, I am certainly not asserting that there could
> not possibly be a problem with Interchange 4.8. I know better than
> that. I just think it is more likely to be the kernel or Perl.

I agree with your assessment and I appreciate the time you put into this
problem.  I went looking for a 'whatsnew' for the newest Perl and while
searching I found this about the version we are using

"For the faint of heart, the previous version of Perl is the 5.005_03
release. Timid souls who are afraid to upgrade to the current release
might want this."

I guess it's time to upgrade :)

> After racking my brain, the only thing I can think of, is that
> Interchange 4.8.x does that 4.6 didn't that might conceivably affect
> this is to use the reset() function in Perl. There may have been some
> bugs with that function fixed in Perl 5.6.

By the way I did not see any messages in /var/log/messages so it seems
that these processes are dying quietly.  After the upgrade to 5.6 we
will again try IC 4.8.x and verify if it was a perl issue or not, I can
then alert other people to the problem if they run into this situation.

> >
> > > The fact that the problem only appears at busy times means it can
> > > be anything, and that it is less likely to be Interchange than it
> > > is overall system.
> >
> > Point noted, we will be testing and deploying the new perl and will
then
> > readdress IC 4.8.x and see if the problem is tied to the old perl.
I
> > have watched the load averages and memory usage when the problem
occurs
> > and it is independent of how busy the site is.
> >
> 
> [snip]
> 
> > I hope you see my true intentions (to resolve the situation quickly)
and
> > look over my frustration which was expressed in my message.
> >
> 
> Good luck. I understand the frustration, believe me. I still remember
> flaky problems from my days of bringing high-volume sites online.

Thanks, I get to relax a little bit today...  I'm sure next week I'll
want to go at it again to get to the bottom of the problem.

Take it easy,
-Ron