Thanks Hans - that fits with what I'm seeing (including no connection with
Oracle).
I had previously discovered that including DateTime in a handler made it
crash at start-up (actually using DateTime wasn't actually necessary) , but
didn't make the connection between that and Params::Classify part
The Classify.dll issue gave me much trouble to figure out. In my instance,
the issue has nothing to do with the database or Oracle.
Here's what I found:
Updating DateTime to version 0.72 includes Params::Classify as a dependency.
http://search.cpan.org/~drolsky/DateTime-0.72/
Also, DateTime-Tim
Sorry, just a clumsy cell phone touch.
- Perrin
On Jan 27, 2012 5:42 PM, "Perrin Harkins" wrote:
> - Perrin
> On Jan 13, 2012 6:47 PM, "Andrew Merton (subscriptions)" <
> amerton.sig...@gmail.com> wrote:
>
>> On 17/12/2011 7:20 a.m., Randolf Richardson wrote:
>>
>> Thanks for the responses :)
- Perrin
On Jan 13, 2012 6:47 PM, "Andrew Merton (subscriptions)" <
amerton.sig...@gmail.com> wrote:
> On 17/12/2011 7:20 a.m., Randolf Richardson wrote:
>
> Thanks for the responses :)
>
> However - I just read another thread somewhere that made me think of
> looking in the Event log.
>
> It ap
> I was getting exception code 0xC0FD (Stack overflow) in Classify.dll
(Params::Classify?)
Well. This goes to show that desperation is the mother of invention :)
I went so far as to look at the code for Params::Classify, and noticed that
there is a pure Perl version if the XS load fails, so I
On Fri, Dec 16, 2011 at 1:20 PM, Randolf Richardson wrote:
> I've been using DBI in threaded Perl environments for many years,
> and it works just fine for me. I used Oracle 8i in the past on
> NetWare (with ModPerl 1 in a threaded environment because the NetWare
> OS is a thread-based arc
On 17/12/2011 7:20 a.m., Randolf Richardson wrote:
Thanks for the responses :)
However - I just read another thread somewhere that made me think of
looking in the Event log.
It appears that the culprit is Oracle - there are errors
naming OraOCIEI11.dll as the "Faulting Module name".
Th
> Thanks for the responses :)
>
> However - I just read another thread somewhere that made me think of
> looking in the Event log.
>
> It appears that the culprit is Oracle - there are errors
> naming OraOCIEI11.dll as the "Faulting Module name".
That's very interesting. Windows Event V
That stinks of a segfault. The admission to using Windows at the end
makes me suspect it even more, as Windows has an unfortunate habit, due
to the MPM implementation, of a thread segfault taking the whole server
down with it, causing a several second delay while it cleans up the old
process and r
> Hi --
>
> I am getting the following message recurring in my log:
>
> Parent: child process exited with status 255 -- Restarting.
>
> followed by the process restart sequence.
>
> I have tracked it down to a call to $r->content which doesn't seem to
> return properly.
>
> It would appear tha
10 matches
Mail list logo
