Hi Bilal,
We had an issue today that brought the production server down. This is
the first error that we’ve seen since updating the connector over a month
ago. The system event log is shown below. Any suggestions on how to
correct this?
Thanks!
Event code: 4010
Event message: An unhandled security exception has occurred.
Best,
BilalOn Monday, November 21, 2016 at 4:43:54 PM UTC-5, Jace Coleman wrote:
Hi Bilal,
We had an issue today that brought the production server down. This is
the first error that we’ve seen since updating the connector over a month
ago. The system event log is shown below. Any suggestions on how to
correct this?
Thanks!
Event code: 4010
Event message: An unhandled security exception has occurred.
We created an event source for the Boncode connector a few weeks back
thanks to Bilal’s recommendation and just had another instance where IIS
worker process locked up at 100% cpu. The log indicates that there was an
error during the spool to the client, but as far as I know this shouldn’t
cause IIS to lock up. Any suggestions on where to look next?
Error during spool to client (browser may have navigated away): The remote
host closed the connection. The error code is 0x800704CD. at
System.Web.Hosting.IIS7WorkerRequest.RaiseCommunicationError(Int32 result,
Boolean throwOnDisconnect)
at System.Web.Hosting.IIS7WorkerRequest.ExplicitFlush()
at System.Web.HttpResponse.Flush(Boolean finalFlush, Boolean async)
at BonCodeIIS.BonCodeCallHandler.PrintFlush(BonCodeAJP13PacketCollection
flushCollection)
Jace,
this error most likely occurs because users have navigated away or closed
their browsers. IIS is still trying to push data to these users. The end
result is this error. In general, disconnects are unavoidable in the
web-communication cycle. This just records the occurrence.
However, if you believe this to be the issue for increased CPU you can
upgrade to version 1.0.32+ which reduces the occurrence of communication
with already disconnected clients.
Also to look at in that case:
using a connection pool: increase maxconnections to >10, e.g.:
500
increase packet size on both tomcat and boncode side
reduce idle timeout on IIS process (Application Pool Advanced
Settings:Process Model), >2 and <5 mins
have a connectionTimeout on Tomcat server.xml AJP protocol definition
Most of this has a mention in the docs if you are not certain how to do it.
I would start with the upgrade though.
Hi Bilal, we updated to the newest connector release last night (AJP13_v1033)
and found that the site was having intermittent connection errors this
morning which was producing the output below:
Generic Connector Communication Error:------------------------------
Please check and adjust your setup:
Ensure that Tomcat is running on given host and port.
If this is a timeout error consider adjusting IIS timeout by changing
executionTimeout attribute in web.config (see manual).
We have since reverted back to AJP13_v1029B which appears to have resolved
the connection error above but leaves us vulnerable to IIS worker processes
locking up again.
On Tuesday, December 13, 2016 at 10:57:43 AM UTC-7, Jace Coleman wrote:
You’re awesome Bilal! I’ll give it a try and post the results.
Jace,
you will need to post your server.xml line that has the AJP protocol
definition and the boncode setting file.
Please remove any sensitive information before posting.
Also post any error messages from Windows log.
Jace,
I am seeing a potential condition where tomcat is closing the connection
after 60 seconds while IIS will maintain them for 20 mins (the default).
This can lead to errors you are seeing when IIS is trying to reuse a
channel that was closed. After displaying the error, upon refresh, this
should go away since the system would refresh connection. Is that what you
see?
Can we try this.
Increase the timeout on tomcat to: connectionTimeout=“1210000”
Then change IIS to a corresponding timeout but a little shorter (see image).
Error during spool to client (browser may have navigated away): The remote
host closed the connection. The error code is 0x80070057. at
System.Web.Hosting.IIS7WorkerRequest.RaiseCommunicationError(Int32 result,
Boolean throwOnDisconnect)
at System.Web.Hosting.IIS7WorkerRequest.ExplicitFlush()
at System.Web.HttpResponse.Flush(Boolean finalFlush, Boolean async)
at
BonCodeIIS.BonCodeCallHandler.PrintFlush(BonCodeAJP13PacketCollection
flushCollection)
<Data>Error during spool to client (browser may have navigated away):
The remote host closed the connection. The error code is 0x80070057. at
System.Web.Hosting.IIS7WorkerRequest.RaiseCommunicationError(Int32 result,
Boolean throwOnDisconnect)
at System.Web.Hosting.IIS7WorkerRequest.ExplicitFlush()
at System.Web.HttpResponse.Flush(Boolean finalFlush, Boolean async)
at
BonCodeIIS.BonCodeCallHandler.PrintFlush(BonCodeAJP13PacketCollection
flushCollection)
Error during spool to client (browser may have navigated away): The remote
host closed the connection. The error code is 0x80070057. at
System.Web.Hosting.IIS7WorkerRequest.RaiseCommunicationError(Int32 result,
Boolean throwOnDisconnect)
at System.Web.Hosting.IIS7WorkerRequest.ExplicitFlush()
at System.Web.HttpResponse.Flush(Boolean finalFlush, Boolean async)
at BonCodeIIS.BonCodeCallHandler.PrintFlush(BonCodeAJP13PacketCollection
flushCollection)
<Data>Error during spool to client (browser may have navigated away):
The remote host closed the connection. The error code is 0x80070057. at
System.Web.Hosting.IIS7WorkerRequest.RaiseCommunicationError(Int32 result,
Boolean throwOnDisconnect)
at System.Web.Hosting.IIS7WorkerRequest.ExplicitFlush()
at System.Web.HttpResponse.Flush(Boolean finalFlush, Boolean async)
at BonCodeIIS.BonCodeCallHandler.PrintFlush(BonCodeAJP13PacketCollection
flushCollection)