Welcome to HostingForumz.com!
FAQFAQ   SearchSearch      ProfileProfile    Private MessagesPrivate Messages   Log inLog in

ISAPI and perlIS.dll

 
   Web Hosting Problem Solving Community! (Home) -> IIS RSS
Related Topics:
IIS 4.0 performance with PerlIS.dll - Loads I am running a script that used the package. To created the filename. the script can be called many time in one second. the last example it got called 8 times, but only 6 files appeared. is there a issue I need to..

IIS, PerlIS.dll, and perl scripts. - Hi all, I've installed Perl 5.8.8 to work along side IIS and we are using as the parser. What is happening is that when ever we view a perl script we only see the html code printed out. I'm told that it is a result of result..

IIS 6 + ISAPI + Win 2003 - What specific do I need to create a file in Win 2003 server, by a ISAPI extension running on IIS 6.0. In our we would create a temporary file to hold some important and place it inside one of the

ISAPI - I wrote an ISAPI filter and installed it on my Web server. it adds headers to the response headers. Here's my problem: I removed it from IIS and the custom headers are still included. I even rebooted the machine, still there. I even..

ISAPI and ASP.net - Hi I would like to get some support from some developer that has some with this. This is my first time to do this... (why was I given this task by my manager) ....... In 6 weeks the Windows NT domain will be taken down. I have a tiny small..
Next:  Help! iisstate log analysis  
Author Message
bj_newsgroups

External


Since: Aug 28, 2003
Posts: 12



(Msg. 1) Posted: Tue Oct 07, 2003 2:43 pm
Post subject: ISAPI and perlIS.dll
Archived from groups: microsoft>public>inetserver>iis (more info?)

NT 4.0 IIS 4.0 SP 6a.
I am doing only one script in Perl
it retirieves a post and writes it to file time on the iss logs show 80.
However I may have 10-30 of these per second.

This webserver does one other opteration. it uses a ASP page to field a post
and return informtion from an SQL server. IIS logs show 140 for time.
There are 5-10 currently persecond.

every once in a while Inetinfo goes into a 75-95% continuos usage from a
normal 30% spikes

Every thing in the IISSTATE. log is in wait state but the PerlIIS

I have include some logs from different instances where this has happend.

I know you don't debug PerlIIS, however i am hoping you will take the slant
on the ISAPI.
Also look at Process 21. ---RPCRT4!WMSG_ADDRESS::ReceiveLotsaCalls+0x17f
I can find in the event recordes or log files anything that would tell me
what cause the RPCRT4!WMSG_ADDRESS::ReceiveLotsaCalls+0x17f



Thread ID: 19
System Thread ID: e1
Kernel Time: 0:32:49.71
User Time: 0:19:41.418
*** WARNING: Unable to verify checksum for perlis.dll
*** ERROR: Symbol file could not be found. Defaulted to export symbols for
perlis.dll -
*** WARNING: Unable to verify checksum for Perl58.dll
*** ERROR: Symbol file could not be found. Defaulted to export symbols for
Perl58.dll -
Thread Type: ISAPI Extension
# ChildEBP RetAddr
WARNING: Stack unwind information not available. Following frames may be
wrong.
00 0266eaa8 281a2bed perlis+0x17a4
01 0266eac8 281a22ea perlis+0x2bed
02 0266eafc 280878f4 perlis+0x22ea
03 0266eb3c 28089d48 Perl58!Perl_PerlIO_write+0x21
04 0266eb58 2808961a Perl58!PerlIOBuf_set_ptrcnt+0x4d4
05 0266eb74 28089c68 Perl58!PerlIOBuf_write+0x9b
06 0266eb98 280878f4 Perl58!PerlIOBuf_set_ptrcnt+0x3f4
07 0266ebd0 2803b74e Perl58!Perl_PerlIO_write+0x21
08 0266ebfc 2805d784 Perl58!Perl_sv_compile_2op+0x37df
09 0266ec84 281a2863 Perl58!Perl_runops_standard+0xc
0a 0266ecb4 281a38d6 perlis+0x2863
0b 0266f0dc 281a2fb2 perlis!GetExtensionVersion+0x880
0c 0266fc40 68891807 perlis!HttpExtensionProc+0x173
0d 0266fc50 688917a8 wam!HSE_APPDLL::ExecuteRequest+0x3b
0e 0266fc88 6889128d wam!WAM::InvokeExtension+0x36
0f 0266fcbc 68c053de wam!WAM::ProcessRequest+0x11d
10 0266fce4 68c052c1 w3svc!CWamInfo::ProcessWamRequest+0x68
11 0266fd24 68c0523d w3svc!WAM_DICTATOR::ProcessWamRequest+0xc9
12 0266fd4c 68c051a7 w3svc!HTTP_REQUEST::DoWamRequest+0x49
13 0266fd70 68c01d3c w3svc!HTTP_REQUEST::ProcessBGI+0x136
14 0266fed4 68c01769 w3svc!HTTP_REQUEST::DoWork+0x386
15 0266fef0 68c046ea w3svc!CLIENT_CONN::DoWork+0xdc
16 0266ff14 68c04689 w3svc!CreateClient+0x3f
17 0266ff54 6862132b w3svc!W3OnConnectEx+0x83
18 0266ff88 68622676 ISATQ!AtqpProcessContext+0x190
19 0266ffb8 77f04ede ISATQ!AtqPoolThread+0x14
1a 0266ffec 00000000 KERNEL32!BaseThreadStart+0x51




Thread ID: 20
System Thread ID: 192
Kernel Time: 0:0:0.0
User Time: 0:0:0.0
Thread Type: Possible ASP page. Possible DCOM activity
Executing Page: Unable to locate ASP page

No remote call being made

# ChildEBP RetAddr
00 03c8fdec 77e15b9f ntdll!NtReplyWaitReceivePort+0xb
01 03c8ff90 77e15a1d RPCRT4!WMSG_ADDRESS::ReceiveLotsaCalls+0x17f
02 03c8ff94 77e160f7 RPCRT4!RecvLotsaCallsWrapper+0x9
03 03c8ffac 77e160bb RPCRT4!BaseCachedThreadRoutine+0x22
04 03c8ffb8 77f04ede RPCRT4!ThreadStartRoutine+0x17
05 03c8ffec 00000000 KERNEL32!BaseThreadStart+0x51




Thread ID: 21
System Thread ID: 199
Kernel Time: 0:0:0.0
User Time: 0:0:0.0
Thread Type: Possible ASP page. Possible DCOM activity
Executing Page: Unable to locate ASP page

No remote call being made

# ChildEBP RetAddr
00 03ccfdec 77e15b9f ntdll!NtReplyWaitReceivePort+0xb
01 03ccff90 77e15a1d RPCRT4!WMSG_ADDRESS::ReceiveLotsaCalls+0x17f
02 03ccff94 77e160f7 RPCRT4!RecvLotsaCallsWrapper+0x9
03 03ccffac 77e160bb RPCRT4!BaseCachedThreadRoutine+0x22
04 03ccffb8 77f04ede RPCRT4!ThreadStartRoutine+0x17
05 03ccffec 00000000 KERNEL32!BaseThreadStart+0x51

 >> Stay informed about: ISAPI and perlIS.dll 
Back to top
Login to vote
someone9

External


Since: Aug 25, 2003
Posts: 2419



(Msg. 2) Posted: Wed Oct 08, 2003 3:29 am
Post subject: Re: ISAPI and perlIS.dll [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)

Nothing unusual with processes 20 and 21.

Perl is likely using synchronous WriteClient, which is one potential cause
of high CPU usage when under moderate stress. A known CPU-usage problem can
be caused by merely dribbling a couple of 1Meg files with synchronous
WriteClient.

If this is the cause, then there is nothing anyone can do other than fix the
Perl ISAPI.

--
//David
IIS
This posting is provided "AS IS" with no warranties, and confers no rights.
//
"BJ Freeman" <bj_newsgroups.RemoveThis@free-man.net> wrote in message
news:uaqTZLQjDHA.2636@TK2MSFTNGP11.phx.gbl...
NT 4.0 IIS 4.0 SP 6a.
I am doing only one script in Perl
it retirieves a post and writes it to file time on the iss logs show 80.
However I may have 10-30 of these per second.

This webserver does one other opteration. it uses a ASP page to field a post
and return informtion from an SQL server. IIS logs show 140 for time.
There are 5-10 currently persecond.

every once in a while Inetinfo goes into a 75-95% continuos usage from a
normal 30% spikes

Every thing in the IISSTATE. log is in wait state but the PerlIIS

I have include some logs from different instances where this has happend.

I know you don't debug PerlIIS, however i am hoping you will take the slant
on the ISAPI.
Also look at Process 21. ---RPCRT4!WMSG_ADDRESS::ReceiveLotsaCalls+0x17f
I can find in the event recordes or log files anything that would tell me
what cause the RPCRT4!WMSG_ADDRESS::ReceiveLotsaCalls+0x17f



Thread ID: 19
System Thread ID: e1
Kernel Time: 0:32:49.71
User Time: 0:19:41.418
*** WARNING: Unable to verify checksum for perlis.dll
*** ERROR: Symbol file could not be found. Defaulted to export symbols for
perlis.dll -
*** WARNING: Unable to verify checksum for Perl58.dll
*** ERROR: Symbol file could not be found. Defaulted to export symbols for
Perl58.dll -
Thread Type: ISAPI Extension
# ChildEBP RetAddr
WARNING: Stack unwind information not available. Following frames may be
wrong.
00 0266eaa8 281a2bed perlis+0x17a4
01 0266eac8 281a22ea perlis+0x2bed
02 0266eafc 280878f4 perlis+0x22ea
03 0266eb3c 28089d48 Perl58!Perl_PerlIO_write+0x21
04 0266eb58 2808961a Perl58!PerlIOBuf_set_ptrcnt+0x4d4
05 0266eb74 28089c68 Perl58!PerlIOBuf_write+0x9b
06 0266eb98 280878f4 Perl58!PerlIOBuf_set_ptrcnt+0x3f4
07 0266ebd0 2803b74e Perl58!Perl_PerlIO_write+0x21
08 0266ebfc 2805d784 Perl58!Perl_sv_compile_2op+0x37df
09 0266ec84 281a2863 Perl58!Perl_runops_standard+0xc
0a 0266ecb4 281a38d6 perlis+0x2863
0b 0266f0dc 281a2fb2 perlis!GetExtensionVersion+0x880
0c 0266fc40 68891807 perlis!HttpExtensionProc+0x173
0d 0266fc50 688917a8 wam!HSE_APPDLL::ExecuteRequest+0x3b
0e 0266fc88 6889128d wam!WAM::InvokeExtension+0x36
0f 0266fcbc 68c053de wam!WAM::ProcessRequest+0x11d
10 0266fce4 68c052c1 w3svc!CWamInfo::ProcessWamRequest+0x68
11 0266fd24 68c0523d w3svc!WAM_DICTATOR::ProcessWamRequest+0xc9
12 0266fd4c 68c051a7 w3svc!HTTP_REQUEST::DoWamRequest+0x49
13 0266fd70 68c01d3c w3svc!HTTP_REQUEST::ProcessBGI+0x136
14 0266fed4 68c01769 w3svc!HTTP_REQUEST::DoWork+0x386
15 0266fef0 68c046ea w3svc!CLIENT_CONN::DoWork+0xdc
16 0266ff14 68c04689 w3svc!CreateClient+0x3f
17 0266ff54 6862132b w3svc!W3OnConnectEx+0x83
18 0266ff88 68622676 ISATQ!AtqpProcessContext+0x190
19 0266ffb8 77f04ede ISATQ!AtqPoolThread+0x14
1a 0266ffec 00000000 KERNEL32!BaseThreadStart+0x51




Thread ID: 20
System Thread ID: 192
Kernel Time: 0:0:0.0
User Time: 0:0:0.0
Thread Type: Possible ASP page. Possible DCOM activity
Executing Page: Unable to locate ASP page

No remote call being made

# ChildEBP RetAddr
00 03c8fdec 77e15b9f ntdll!NtReplyWaitReceivePort+0xb
01 03c8ff90 77e15a1d RPCRT4!WMSG_ADDRESS::ReceiveLotsaCalls+0x17f
02 03c8ff94 77e160f7 RPCRT4!RecvLotsaCallsWrapper+0x9
03 03c8ffac 77e160bb RPCRT4!BaseCachedThreadRoutine+0x22
04 03c8ffb8 77f04ede RPCRT4!ThreadStartRoutine+0x17
05 03c8ffec 00000000 KERNEL32!BaseThreadStart+0x51




Thread ID: 21
System Thread ID: 199
Kernel Time: 0:0:0.0
User Time: 0:0:0.0
Thread Type: Possible ASP page. Possible DCOM activity
Executing Page: Unable to locate ASP page

No remote call being made

# ChildEBP RetAddr
00 03ccfdec 77e15b9f ntdll!NtReplyWaitReceivePort+0xb
01 03ccff90 77e15a1d RPCRT4!WMSG_ADDRESS::ReceiveLotsaCalls+0x17f
02 03ccff94 77e160f7 RPCRT4!RecvLotsaCallsWrapper+0x9
03 03ccffac 77e160bb RPCRT4!BaseCachedThreadRoutine+0x22
04 03ccffb8 77f04ede RPCRT4!ThreadStartRoutine+0x17
05 03ccffec 00000000 KERNEL32!BaseThreadStart+0x51

 >> Stay informed about: ISAPI and perlIS.dll 
Back to top
Login to vote
bj_newsgroups

External


Since: Aug 28, 2003
Posts: 12



(Msg. 3) Posted: Wed Oct 08, 2003 9:51 am
Post subject: Re: ISAPI and perlIS.dll [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)

I appreciate your input. I needed confirmation.
Thanks for your time.


"David Wang [Msft]" <someone.TakeThisOut@online.microsoft.com> wrote in message
news:#c9ITBXjDHA.1656@tk2msftngp13.phx.gbl...
 > Nothing unusual with processes 20 and 21.
 >
 > Perl is likely using synchronous WriteClient, which is one potential cause
 > of high CPU usage when under moderate stress. A known CPU-usage problem
can
 > be caused by merely dribbling a couple of 1Meg files with synchronous
 > WriteClient.
 >
 > If this is the cause, then there is nothing anyone can do other than fix
the
 > Perl ISAPI.
 >
 > --
 > //David
 > IIS
 > This posting is provided "AS IS" with no warranties, and confers no
rights.
 > //
 > "BJ Freeman" <bj_newsgroups.TakeThisOut@free-man.net> wrote in message
 > news:uaqTZLQjDHA.2636@TK2MSFTNGP11.phx.gbl...
 > NT 4.0 IIS 4.0 SP 6a.
 > I am doing only one script in Perl
 > it retirieves a post and writes it to file time on the iss logs show 80.
 > However I may have 10-30 of these per second.
 >
 > This webserver does one other opteration. it uses a ASP page to field a
post
 > and return informtion from an SQL server. IIS logs show 140 for time.
 > There are 5-10 currently persecond.
 >
 > every once in a while Inetinfo goes into a 75-95% continuos usage from a
 > normal 30% spikes
 >
 > Every thing in the IISSTATE. log is in wait state but the PerlIIS
 >
 > I have include some logs from different instances where this has happend.
 >
 > I know you don't debug PerlIIS, however i am hoping you will take the
slant
 > on the ISAPI.
 > Also look at Process 21. ---RPCRT4!WMSG_ADDRESS::ReceiveLotsaCalls+0x17f
 > I can find in the event recordes or log files anything that would tell me
 > what cause the RPCRT4!WMSG_ADDRESS::ReceiveLotsaCalls+0x17f
 >
 >
 >
 > Thread ID: 19
 > System Thread ID: e1
 > Kernel Time: 0:32:49.71
 > User Time: 0:19:41.418
 > *** WARNING: Unable to verify checksum for perlis.dll
 > *** ERROR: Symbol file could not be found. Defaulted to export symbols
for
 > perlis.dll -
 > *** WARNING: Unable to verify checksum for Perl58.dll
 > *** ERROR: Symbol file could not be found. Defaulted to export symbols
for
 > Perl58.dll -
 > Thread Type: ISAPI Extension
 > # ChildEBP RetAddr
 > WARNING: Stack unwind information not available. Following frames may be
 > wrong.
 > 00 0266eaa8 281a2bed perlis+0x17a4
 > 01 0266eac8 281a22ea perlis+0x2bed
 > 02 0266eafc 280878f4 perlis+0x22ea
 > 03 0266eb3c 28089d48 Perl58!Perl_PerlIO_write+0x21
 > 04 0266eb58 2808961a Perl58!PerlIOBuf_set_ptrcnt+0x4d4
 > 05 0266eb74 28089c68 Perl58!PerlIOBuf_write+0x9b
 > 06 0266eb98 280878f4 Perl58!PerlIOBuf_set_ptrcnt+0x3f4
 > 07 0266ebd0 2803b74e Perl58!Perl_PerlIO_write+0x21
 > 08 0266ebfc 2805d784 Perl58!Perl_sv_compile_2op+0x37df
 > 09 0266ec84 281a2863 Perl58!Perl_runops_standard+0xc
 > 0a 0266ecb4 281a38d6 perlis+0x2863
 > 0b 0266f0dc 281a2fb2 perlis!GetExtensionVersion+0x880
 > 0c 0266fc40 68891807 perlis!HttpExtensionProc+0x173
 > 0d 0266fc50 688917a8 wam!HSE_APPDLL::ExecuteRequest+0x3b
 > 0e 0266fc88 6889128d wam!WAM::InvokeExtension+0x36
 > 0f 0266fcbc 68c053de wam!WAM::ProcessRequest+0x11d
 > 10 0266fce4 68c052c1 w3svc!CWamInfo::ProcessWamRequest+0x68
 > 11 0266fd24 68c0523d w3svc!WAM_DICTATOR::ProcessWamRequest+0xc9
 > 12 0266fd4c 68c051a7 w3svc!HTTP_REQUEST::DoWamRequest+0x49
 > 13 0266fd70 68c01d3c w3svc!HTTP_REQUEST::ProcessBGI+0x136
 > 14 0266fed4 68c01769 w3svc!HTTP_REQUEST::DoWork+0x386
 > 15 0266fef0 68c046ea w3svc!CLIENT_CONN::DoWork+0xdc
 > 16 0266ff14 68c04689 w3svc!CreateClient+0x3f
 > 17 0266ff54 6862132b w3svc!W3OnConnectEx+0x83
 > 18 0266ff88 68622676 ISATQ!AtqpProcessContext+0x190
 > 19 0266ffb8 77f04ede ISATQ!AtqPoolThread+0x14
 > 1a 0266ffec 00000000 KERNEL32!BaseThreadStart+0x51
 >
 >
 >
 >
 > Thread ID: 20
 > System Thread ID: 192
 > Kernel Time: 0:0:0.0
 > User Time: 0:0:0.0
 > Thread Type: Possible ASP page. Possible DCOM activity
 > Executing Page: Unable to locate ASP page
 >
 > No remote call being made
 >
 > # ChildEBP RetAddr
 > 00 03c8fdec 77e15b9f ntdll!NtReplyWaitReceivePort+0xb
 > 01 03c8ff90 77e15a1d RPCRT4!WMSG_ADDRESS::ReceiveLotsaCalls+0x17f
 > 02 03c8ff94 77e160f7 RPCRT4!RecvLotsaCallsWrapper+0x9
 > 03 03c8ffac 77e160bb RPCRT4!BaseCachedThreadRoutine+0x22
 > 04 03c8ffb8 77f04ede RPCRT4!ThreadStartRoutine+0x17
 > 05 03c8ffec 00000000 KERNEL32!BaseThreadStart+0x51
 >
 >
 >
 >
 > Thread ID: 21
 > System Thread ID: 199
 > Kernel Time: 0:0:0.0
 > User Time: 0:0:0.0
 > Thread Type: Possible ASP page. Possible DCOM activity
 > Executing Page: Unable to locate ASP page
 >
 > No remote call being made
 >
 > # ChildEBP RetAddr
 > 00 03ccfdec 77e15b9f ntdll!NtReplyWaitReceivePort+0xb
 > 01 03ccff90 77e15a1d RPCRT4!WMSG_ADDRESS::ReceiveLotsaCalls+0x17f
 > 02 03ccff94 77e160f7 RPCRT4!RecvLotsaCallsWrapper+0x9
 > 03 03ccffac 77e160bb RPCRT4!BaseCachedThreadRoutine+0x22
 > 04 03ccffb8 77f04ede RPCRT4!ThreadStartRoutine+0x17
 > 05 03ccffec 00000000 KERNEL32!BaseThreadStart+0x51
 >
 >
 >
 >
 ><!-- ~MESSAGE_AFTER~ -->
 >> Stay informed about: ISAPI and perlIS.dll 
Back to top
Login to vote
Display posts from previous:   
   Web Hosting Problem Solving Community! (Home) -> IIS All times are: Pacific Time (US & Canada) (change)
Page 1 of 1

 
You can post new topics in this forum
You can reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum



[ Contact us | Terms of Service/Privacy Policy ]