Weblog

OpenACS Community Wiki

Created by gustaf neumann, last modified by Gustaf Neumann 21 Aug 2020, at 04:54 PM

This is the OpenACS Wiki system, built with the xowiki package. This wiki contains user documentation, how-tos, and tips and tricks related to OpenACS. It also serves as a collaboration area for OpenACS contributors.

Quick Links:

• OpenACS Handbook
• OpenACS Packages
• OpenACS Cookbook
• OpenACS Installation

Recent Wiki Page Edits:

Cookbook

Enforcing POST for state-changing requests (require_post) (5 months ago)
Handling JSON Requests with page contracts (5 months ago)
Security: Cross Site Request Forgery (CSRF) (5 months ago)
NaviServer and OpenACS with Docker (1 year ago)
Managing Versions of External JavaScript Libraries (1 year ago)
Running OpenACS behind a proxy (2 years ago)
Fresh install of OpenACS 5.10 on Oracle 19c (2 years ago)
Using OpenACS with External Identity Providers (3 years ago)
E-Mail: Outgoing E-Mail (3 years ago)
Double Click Handling (3 years ago)
Setup with docker-s6 (3 years ago)
Interfacing with MS Teams and related services (Microsoft Graph) (4 years ago)
New Interface for Calling Database functions (4 years ago)
Server-sent events (4 years ago)

Subsystems Documentation

OpenACS Compatibility Matrix (6 months ago)
NaviServer (7 months ago)
Install OpenACS with NaviServer from Scratch (1 year ago)
Installing OpenACS on Windows (1 year ago)
OpenACS Monitoring (2 years ago)
for beginning developers (2 years ago)
Installing OpenACS (2 years ago)
Get the OpenACS Source Code (3 years ago)
Install Oracle (4 years ago)
Upgrade from PostgreSQL 9.6 to 13.1 (4 years ago)
Upgrade to OpenACS 5.10 (4 years ago)

Events

OpenACS Conferences (1 year ago)

HOME

aolserver-market-position-2013-08.png (1 year ago)
for beginning developers (2 years ago)
Privacy Policy (3 years ago)

External Resources

Installing OpenACS on Windows (1 year ago)

OpenACS Projects

OpenACS Release Status (1 year ago)
OpenACS TODO List (1 year ago)
OpenACS 5.10.1 Change Summary (2 years ago)
OpenACS 5.10.0 Change Summary (2 years ago)
E-Mail: Outgoing E-Mail (3 years ago)

Package Documentation

Packages available in the oacs-5-10 channel (1 year ago)

Tutorials for Administrators

OpenACS Monitoring (2 years ago)
rl_json (3 years ago)

Non-Core Packages

Chat (2 years ago)
XoWiki (2 years ago)
XOTcl Core (2 years ago)
xooauth (3 years ago)
xowf (XoWiki Workflow) (4 years ago)

Tutorials

for beginning developers (2 years ago)
Theming in OpenACS (4 years ago)

Documentation

for beginning developers (2 years ago)

Core Documentation

Installing OpenACS (2 years ago)

Coding Standards

Security Guidelines (3 years ago)
Coding Standards - Index (3 years ago)
Tcl Procs (3 years ago)

How to handle "connection already closed" errors

Created by Gustaf Neumann, last modified by Gustaf Neumann 21 Aug 2020, at 12:47 PM

Newer versions of NaviServer produce by default an error, when a script tries to write a connection, which as already closed by the server (e.g. doing two ad_returndirect in a sequence). Such program code does not make sense and indicates an error that should be fixed.

In general, one can silence the behavior or fix it. To silence the behavior, on can alter the NaviServer config file to silently swallow these error conditions named "rejectalreadyclosedconn". See e.g. Sample configuration file

Recent version of OpenACS (oacs-5-10) have such error conditions already fixed in all the actively maintained packages in the oacs-5-10 branch. In order to fix custom packages, one has to watch out for the following situations:

• Request pages: all after every command that finishes a request a call to "ad_script_abort" is required. Such commands are essentially all "ns_return*" commands and the "ad_*" counterparts.
• Filters: in case, an application handles such commands in filters, the filter has to return with "filter_return" to stop the filter chain (i.e. not to call further filters). Notice that the documentation of ns_register states that the request page is as well handled to trigger e.g. the access log entry. So, in rare conditions, one has to check as well for additional closed cases by using "ns_conn isconnected".

Sometimes, it might be still tricky to find such occurrences. On recent versions of OpenACS one can use the xo* machinery to activate/deactivate Tcl command traces for such commands via ds/shell, like e.g. in:

xo::broadcast send {
  set traced_cmds [info commands ::ns_return*]
  foreach cmd $traced_cmds {trace add execution $cmd  enter {::tcltrace::before}}
}

"xo::broadcast" sends the command to every tcl based thread that executes the provided command. Tracing can be deactivated by replacing "trace add" by "trace remove" in this command.

Plain OpenACS (in oacs-5-10) has as well some support for this via acs-tcl/tcl/tcltrace-init.tcl.