SERVICES I am also experiencing the same service hangs, but I am not sure if it's due
to memory usage. The problem appears on both Perl v5.6.1.638+PerlEx 2.3.1 on
Win2003 Server, and Perl 5.8.7.815 on IIS 6.0 on Win2003 Server, Interfacing
to either MS SQL Server 2000 or MS SQL Server 2005.

Killing w3wp.exe would get the application moving again.

Have you tried running it off a Win2k server?

The only common denominator is Windows 2003 Server, so I think it's
something between IIS 6.0 and ActivePerl; but there is also a possibility
that it's something between DBI/DBD and ODBC.

I am configuring to use RemoteService (from http://www.intelliadmin.com) to
remotely stop w32wp.exe service. But it isn't really a solution for me,
since the data integrity is at stake.

best regards,
Philip Kuok 
infoarch sdn bhd 
http:www.infoarch.net 


-----Original Message-----
From: perlex-bounces@[...].com
[mailto:perlex-bounces@[...].com] On Behalf Of
perlex-request@[...].com
Sent: Tuesday, 17 April 2007 3:00 AM
To: perlex@[...].com
Subject: PerlEx Digest, Vol 27, Issue 1

Send PerlEx mailing list submissions to
	perlex@[...].com

To subscribe or unsubscribe via the World Wide Web, visit
	http://listserv.ActiveState.com/mailman/listinfo/perlex
or, via email, send a message with subject or body 'help' to
	perlex-request@[...].com

You can reach the person managing the list at
	perlex-owner@[...].com

When replying, please edit your Subject line so it is more specific than
"Re: Contents of PerlEx digest..."


Today's Topics:

   1. Automatic recovery from "Script failed to send data"
      (Bryan M. Kramer)


----------------------------------------------------------------------

Message: 1
Date: Mon, 16 Apr 2007 14:25:45 -0400
From: "Bryan M. Kramer" <bryan.kramer@[...].com> 
Subject: Automatic recovery from "Script failed to send data"
To: perlex@[...].com
Message-ID: <4623BFA9.4090706@[...].com> 
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

I am finding that some operations fail after using too much memory - the
user sees "Script failed to send data". It seems that the only way to start
the web application again is to restart IIS. This will be unacceptable once
the application is deployed. I'm pretty sure it is a memory problem since
the operation fails intermittently and one can see the memory usage climbing
sky high in task manager.

Is there any way to make sure that PerlEx kills the bad interpreter and
starts up again automatically?

Thanks
Bryan M. Kramer


Perl Version:

This is perl, v5.8.8 built for MSWin32-x86-multi-thread (with 33 registered
patches, see perl -V for more detail)

Copyright 1987-2006, Larry Wall

Binary build 819 [267479] provided by ActiveState http://www.ActiveState.com
Built Aug 29 2006 12:42:41



------------------------------

_______________________________________________
PerlEx mailing list
PerlEx@[...].com
To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs

End of PerlEx Digest, Vol 27, Issue 1
*************************************

_______________________________________________
PerlEx mailing list
PerlEx@[...].com
To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs