Hi,
Yes, I am running the latest x86 version of ActiveState Perl (5.8.8. "with
50 registered patches").
There are no interesting messages in the Event Logs, but after the problem
appears, I start getting other strange errors as well. For example,
PostgreSQL starts rejecting new connections, and other network-related apps
fail. Also, the following is logged in the System log: "The DNS proxy agent
was unable to allocate 0 bytes of memory". Memory seems fine in Task Manager
(my computer has 3 GB installed). DameWare Mini Remote Control reports
"error 10013: An attempt was made to access a socket in a way forbidden by
its access permissions". Generally all socket-related operations seem to
fail (not just http).
I don't think this is a Perl problem because of the following reasons:
1. It only happens on Vista. XP runs the test script fine for hours.
2. The problem persists after Perl.exe has exited. Windows should release
all resources held by user-mode applications, shouldn't it? And especially
Vista should not let non-administrative programs affect other users.
3. The problem doesn't appear if I add a "sleep 1" in the test script and
run the script for hours. It only appears when many http requests are made
in rapid succession. This sounds like some kind of attack detection logic
that doesn't get properly reset.
Did you (or anyone else) reproduce the problem?
--
Mikko Noromaa (mikkon@excelsql.com)
- SQL in Excel, check out ExcelSQL! - see
http://www.excelsql.com -
"Scissor" <Scissor.2qarh8@no-mx.forums.net> wrote in message
news:Scissor.2qarh8@no-mx.forums.net...
>
> Are you running the latest version of ActiveState Perl (5.8.8.820)? Did
> you download the correct version (x86 vs x64)? The latest version is
> here: 'ActiveState - ActivePerl free Perl open source binary language
> distribution - Dynamic Tools for Dynamic Languages'
> (http://www.activestate.com/Products/ActivePerl/)
>
> Anything interesting reported in your computer's Event Logs?
>
> If you have found a bug in Perl, I suggest reporting it to ActiveState
> so that they can fix it in the next release. ActiveState's bug tracker
> is here: 'ActiveState Bug Database - Simple Query Page'
> (http://bugs.activestate.com/query.cg...uct=ActivePerl)
>
>
> --
> Scissor