The thing here is the code is not failing always. I am using a cron
It can happen. Clearly, it will fail upon a condition. Without seeing
the code, or (preferably) a minimal version of it, it's hard to say.
wrapper script which creates an object of a module, then runs a
reports and emails it. The problem is it is failing only rarely like
This is hardly relevant except possibly for permission issues: which
have nothing to do with the fact that the code is an object creation
one.
for eg once in a month. The script runs daily.
I just wanted to know when we experience object creation failure.
In just so many situations that one can't really give you a proper
answer. The code that takes care of object creation can do quite about
anything, so the only proper answer to your actual question thus far
can only be: quite about anything.
1. One thing is the system runs out of RAM, but it is very very
remote scenario.
Yes, it can be. Hard to say without seeing the actual code. How 'bout
logging memory usage anyway, if you have this suspect?
2. May be when the cron is running there is something which causing
the failure in middle ?
In the middle of... what?
3. Or something wrong in the code ?.
May be. Once again: hard to say without seeing the actual code.
It is really a simple object creation code, which is failing only some
cases. There is nothing wrong in the code also since the same code
This claim of yours is in contradiction with possibility 3 above.
runs fine most of the cases.
"running fine most of the cases" generally is not regarded as a good
proof of "there not being anything wrong in the code." Perhaps you
mean that it is syntactically correct, and that may well be. A whole
another story...
Michele
--
{$_=pack'B8'x25,unpack'A8'x32,$a^=sub{pop^pop}->(map substr
(($a||=join'',map--$|x$_,(unpack'w',unpack'u','G^<R<Y]*YB='
.'KYU;*EVH[.FHF2W+#"\Z*5TI/ER<Z`S(G.DZZ9OX0Z')=~/./g)x2,$_,
256),7,249);s/[^\w,]/ /g;$ \=/^J/?$/:"\r";print,redo}#JAPH,