Re: Can't return outside a subroutine, <SOCKET> line 138.

[prev] [thread] [next] [Date index for 2005/03/17]

Actually, we solved the issue soon after this post (which took quite a while 
to make it to the list) ... anyhow, we developed a compiled language 
interface to our databases that does simple queries and in some cases data 
comparison, and returns the results to the aforementioned perl object 
creating base module for higher level per-database modules that give each an 
object identity.

Well, that regex on line 905 was inappropriatelly culling out an AND given 
to the SQL maker in question, and handing it off to the database service... 
the service (which is relatively young so far and not particularly emotive 
when it fails) was somehow interrupting or bullying the error_log buffer 
such that the few lines of warns that came between the regex and the return 
$sql line never saw the light of day, making the whole ordeal appear as if 
the subroutine simply stopped on the same line as the regex.  And we 
couldn't for the life of us figure out why the subroutine would abort 
several lines premature of the return statement... and it wasn't.

So let our embarrassment serve the greater good; don't always believe what 
the error_log tells you!!! We did and ended up chasing a wild goose.

----- Original Message ----- 
From: "Stas Bekman" <stas@xxxxxx.xxx>
To: "Tom Schindl" <tomAtLinux@xxx.xx>
Cc: "jet" <jet@xxxxxxx.xxx>; <modperl@xxxx.xxxxxx.xxx>
Sent: Wednesday, March 16, 2005 9:01 PM
Subject: Re: Can't return outside a subroutine, <SOCKET> line 138.


> Tom Schindl wrote:
>> jet wrote:
>>
>>> i'm losing my mind here;
>>>
>>> to protect the client, i am 're-naming' the module names for 
>>> confidentiality, but I have a seriously weird problem that is not adding 
>>> up to anything intuitive for me at all.
>>>
>>> We have a foundation module that deals with interacting with our 
>>> databases... higher level modules then base themselves off this 
>>> foundation,. which provides functionalities such 
>>> as ->select, ->new, ->save, ->update, ->find ...
>>>
>>> well, we've recently upgraded servers and moved towards apache2/modperl2
>>>
>>> more precisely:
>>>
>>> httpd-2.0.52-9.ent
>>> mod_perl-1.99_16-4
>>
>>
>>
>> I'd say that you should upgrade mod_perl to the latest and greatest and 
>> look if the problem goes away.
>
> If the problem persists after the upgrade, please try to minimise the 
> module to a very minimum so we can see the whole picture. Is it an anon 
> sub by chance?
>
> -- 
> __________________________________________________________________
> Stas Bekman            JAm_pH ------> Just Another mod_perl Hacker
> http://stason.org/     mod_perl Guide ---> http://perl.apache.org
> mailto:stas@xxxxxx.xxx http://use.perl.org http://apacheweek.com
> http://modperlbook.org http://apache.org   http://ticketmaster.com
>
>
> -- 
> No virus found in this incoming message.
> Checked by AVG Anti-Virus.
> Version: 7.0.308 / Virus Database: 266.7.3 - Release Date: 3/15/2005
>
>