We use IPMonitor ( http://www.ipmonitor.com ) which supports a SMTP test which just checks the port connection, so we also attach the CF Connector that iMS uses to a private IIS site and then use a HTTP test to make sure the connector is alive. In almost all cases IIS also fails to talk to ColdFusion at the same time iMS does. You should be able to do the same thing with HealthMonitor *free* (http://sourceforge.net/projects/healthmonitor)
Below is what I just got out of our connector log, looks like a different core problem then yours, but the end result is the same. I'm going to spend some time on this for the next few hours. We have a slew of other problems with iMS I need to try to fix too. I just wish CoolFusion had better support/documentation to give us some direction on this... .brett 2007-02-13 08:48:42 jrISAPI[ 904:816] 127.0.0.1:51004 connect failed[652]: 10060 Connection timed out 2007-02-13 08:48:42 jrISAPI[ 904:816] returning error page for Connection timed out 2007-02-13 08:54:55 jrISAPI[init:816] JRun ISAPI Extension DLL Detaching (process termination) 2007-02-13 08:54:55 jrISAPI[init:816] socket shutdown failed[652]: 10093, 10093 Unknown error 2007-02-13 08:54:55 jrISAPI[init:816] socket close fail[652]: 10093, 10093 Unknown error 2007-02-13 08:54:55 jrISAPI[init:812] JRun 4.0 (Build 106363) JRun ISAPI Extension - Aug 17 2005 12:50:05 2007-02-13 08:54:55 jrISAPI[init:812] JRun ISAPI Extension DLL Attaching 2007-02-13 08:54:56 jrISAPI[init:792] JRun ISAPI Extension DLL Detaching (process termination) 2007-02-13 08:54:56 jrISAPI[init:792] socket shutdown failed[388]: 10093, 10093 Unknown error 2007-02-13 08:54:56 jrISAPI[init:792] socket close fail[388]: 10093, 10093 Unknown error 2007-02-13 08:54:57 jrISAPI[init:788] JRun 4.0 (Build 106363) JRun ISAPI Extension - Aug 17 2005 12:50:05 2007-02-13 08:54:57 jrISAPI[init:788] JRun ISAPI Extension DLL Attaching > -----Original Message----- > From: Dharmendar Kumar [mailto:[EMAIL PROTECTED] > Sent: Monday, February 12, 2007 2:56 PM > To: inFusion Support List > Subject: [SPAM] RE: [iMS] " JRun ISAPI Extension failed " error > > Hi Brett, > > How do you "watch" the connector? What kind of network monitor are you > using? > > We see this problem on 2 of the 8 IMS servers that we have. And it is > pretty > random. > > We have entries in the connector log which correspond to the error in > the > POST log. Not sure what this could mean? > > > The entries in the connector log is as follows: > > 2007-02-12 00:01:05 jrISAPI[3356:4956] 127.0.0.1:51011 connect failed: > 10055 No buffer space available, no sock added to pool > 2007-02-12 00:01:05 jrISAPI[3356:4956] returning error page for No > buffer > space available > 2007-02-12 00:01:05 jrISAPI[4360:4956] 127.0.0.1:51011 connect failed: > 10055 No buffer space available, no sock added to pool > 2007-02-12 00:01:05 jrISAPI[4360:4956] returning error page for No > buffer > space available > > 2007-02-12 09:34:28 jrISAPI[init:4956] JRun ISAPI Extension DLL > Detaching > (process termination) > 2007-02-12 09:34:28 jrISAPI[init:4956] socket shutdown failed[30056]: > 10093, 10093 Unknown error > 2007-02-12 09:34:28 jrISAPI[init:4956] socket close fail[30056]: > 10093, > 10093 Unknown error > 2007-02-12 09:34:28 jrISAPI[init:4956] socket shutdown failed[31296]: > 10093, 10093 Unknown error > 2007-02-12 09:34:28 jrISAPI[init:4956] socket close fail[31296]: > 10093, > 10093 Unknown error > 2007-02-12 09:34:28 jrISAPI[init:4956] socket shutdown failed[9780]: > 10093, > 10093 Unknown error > 2007-02-12 09:34:28 jrISAPI[init:4956] socket close fail[9780]: 10093, > 10093 Unknown error > 2007-02-12 09:34:56 jrISAPI[ 880:9248] jrRecv failed[592]: 10053 > Connection > aborted > 2007-02-12 09:41:14 jrISAPI[init:6952] JRun 4.0 (Build 91015) JRun > ISAPI > Extension - Jan 6 2005 15:24:23 > 2007-02-12 09:41:14 jrISAPI[init:6952] JRun ISAPI Extension DLL > Attaching > > Did you also see similar entries in your connector logs? > > DK > > -----Original Message----- > From: WebFlint [mailto:[EMAIL PROTECTED] > Sent: Monday, February 12, 2007 12:26 PM > To: inFusion Support List > Subject: RE: [iMS] " JRun ISAPI Extension failed " error > > > We also get this exact same error multiple times a day, running iMS > attached > to an instance of CFMX 6.1 running on JRUN. > > It seems fairly random where the connector just fails, I've spent a > number > of days playing with the iMS/CF settings and could never get it solved. > > Unfortunately what we do now is have a network monitor that watches the > connector and when it fails we restart the CF instance which brings it > back > up. > > I'm really not sure if it is iMS or CF, but none of our other CF > instances > experience this problem, only the one that iMS interacts with. > > I would love to get this fixed too so if you find out anything or want > to > compare any notes please let me know. > > .brett > > inFusion SMTP Server version 2.8 > inFusion POST Server version 2.8.5 > inFusion Scheduler version 2.8.2 > > > -----Original Message----- > > From: Dharmendar Kumar [mailto:[EMAIL PROTECTED] > > Sent: Monday, February 12, 2007 11:09 AM > > To: inFusion Support List > > Subject: [iMS] " JRun ISAPI Extension failed " error > > > > We are seeing the following error in our POST server log. > > > > > > 02/11/2007 11:12:33 AM [036] WARNING: inFusionEngine error: JRun > ISAPI > > Extension failed (HSE_STATUS_ERROR) 02/11/2007 11:12:33 AM [036] > > DEBUG: HTTP/1.1 503 Server Error > > content-type: text/html > > > > 02/11/2007 11:12:33 AM [036] DEBUG: <H2>Server Error</H2>The server > > encountered an internal error and was unable to complete your > > request.<P><B>JRun Connector Protocol Error.</B> > > > > > > At first look it seems that was some problem with the ColdFusion > > Server. But when we checked out ColdFusion logs there does not seem > to > > be any entries in any of the ColdFusion logs around that time. > > Sometimes, this problem seems to go on its own. At other times, we > > have to restart POST Server for this error to go. > > > > We are using CFMX 7 and POST Server is ver 2.8.1 r2 > > > > The setting for Simultaneous App Server Connections is at "8" (which > > is less that the "Max number of Simultaneous Connections" setting in > > CF Admin). > > > > Has anyone seen this error? Any idea what could be causing it? > > > > Thanks > > DK > ==^======================================================= This list server is Powered by iMS "The Swiss Army Knife of Mail Servers" -------------------------------------------------------------------------------------- This list is provided as a free service. Although we will try to address issues in a timely manner, support via this list is not guaranteed. If you require expedited support then a support contract is required. Support may be purchased from http://www.coolfusion.com/commerce. Details regarding support options may be reviewed at: http://www.coolfusion.com/SupportOptions.cfm -------------------------------------------------------------------------------------- To leave this list please complete the form at http://www.coolfusion.com/Support/ Need an iMS Developer license? Sign up for a free license here: http://www.coolfusion.com/Developers/ List archives: http://www.coolfusion.com/cfbb/ Note: You are subscribed as archive_jab_org / [email protected] ==^=======================================================
