Re: Oracle::DBD under mod_perl on Sun/Solaris

2001-08-23 Thread Alex Povolotsky

On Wed, Aug 22, 2001 at 08:33:53PM +0100, Ged Haywood wrote:
  DBD::Oracle::db prepare failed: ORA-03120: two-task conversion routine:
 [snip]
  DBD::Oracle::db prepare failed: ORA-03113: end-of-file on communication channel 
(DBD: oopen error)
  and EVERY connect to database fails since that.
  I was NOT able to reproduce this bug outside of mod_perl.
 
 Are you running out of memory?
... should not... HOWEVER, Apache::Resource, when it was installed, dropped
children on MEMORY at the time of connect to Oracle. I've set limit to 128
Mb, it didn't help.

Alex.



Re: Problem with DBD::Oracle with mod_perl

2001-08-22 Thread Alex Povolotsky

On Wed, Aug 22, 2001 at 09:42:59AM -0400, Perrin Harkins wrote:
   Are you using Apache::DBI?  Are you opening a connection in the parent
   process (in startup.pl or equivalent)?
  Yes, yes.
 
 Don't open a connection during startup.  If you do, it will be shared when
 Apache forks, and sharing a database handle is bad for the same reasons
 sharig a file handle is.  Open a connection in the child process instead.
 You can use connect_on_init() from Apache::DBI if you like.
I misunderstood you. I was using connect_on_init. With or without
Apache::DBI, it fails

Alex.



Re: Problem with DBD::Oracle with mod_perl

2001-08-22 Thread Alex Povolotsky

On Wed, Aug 22, 2001 at 09:07:59AM -0400, Perrin Harkins wrote:
  (DBD: error possibly near * indicator at char 1 in '*select
 slogan_text
  from
   slogans') at /usr/local/www/lib/SQL.pm line 221.
 Are you using Apache::DBI?  Are you opening a connection in the parent
 process (in startup.pl or equivalent)?
Yes, yes.

... whithout it - runs...  a little longer. 

Alex.



Re: DSO problems summary? (was Re: Children dying)

2001-08-16 Thread Alex Povolotsky

On Thu, Aug 16, 2001 at 09:35:43AM -0700, Doug MacEachern wrote:
 that should be any platform where perl defaults to using its own malloc,
 that is, if:
 % perl -V:usemymalloc
 reports:
 usemymalloc='y'
 
 which is fine if:
 % perl -V:bincompat5005
 reports:
 bincompat5005='undef';
 
 but the default for 5.6.x is:
 bincompat5005='define';
Well... With 
 # perl -v

This is perl, v5.6.1 built for sun4-solaris

# perl -V:usemymalloc
usemymalloc='n';
# perl -V:bincompat5005
bincompat5005='define';

on  # uname -a
SunOS netra 5.8 Generic_108528-09 sun4u sparc SUNW,UltraAX-i2

am I safe? Or what should I rebuild with what flags?

Seems like I'm suffering from dying children problem... My main apache
dies sometimes, bringing neraly everything (well, except
server-status) down.

Alex.