---

Web Server Adaptors

Radar #2454840

When using the CGI WebObjects HTTP Adaptor in multicast mode, performance is suboptimal.

Description:

Configuring the CGI adaptor to use multicast to discover wotaskd daemons on the deployment subnet results in very slow performance. Configuring to use non-multicast mode and to already know which wotaskd daemons it should talk to results in a seven-fold performance increase. CGI in multicast mode is the configuration that will generate the most noise on your deployment subnet, so it is not recommended except for development or functionality testing.

Workaround:

If CGI performance is unacceptable in multicast mode, then one of the non-multicast modes should be used. Note that multicast is not the default mode, so you should already know how to switch the CGI back to a non-multicast mode. More information is available in the WebObjects Deployment guide.

Radar #2455171

WOHTTPConnections cannot be shared between worker threads.

Description:

Due to the fact that WOHTTPConnection currently has one input buffer per instance, and no locking thereof, WOHTTPConnection objects cannot easily be shared between threads, as unpredictable results will occur.

Workaround:

Either avoid sharing WOHTTPConnection objects between threads, or add additional locking logic in your own code.

Radar #2766065

When using a WebObjects application running in WebLogic, you cannot connect to WebObjects application deployed through the WebObjects HTTP adaptor.

Description:

WebLogic can be configured in 2 ways. The first way is by MIME type, and the second is by Path. However, there seem to be some issues with configuration by Path.

Workaround:

If WebLogic can be configured to service URLs by path, a standard WebObjects deployment should be able to work concurrently with a WebLogic deployment.

Radar #3046661

Solaris HTTP adaptor must use same compiler as web server.

Description:

The WebObjects 5.2 HTTP adaptor binaries for Solaris were compiled using gcc 3.1. If a customer compiles their own version of a the web server using a different compiler (the Sun compiler, for example), the prebuilt plugin adaptor binary may be incompatible.

Workaround:

Build the HTTP adaptor using the same compiler that was used to build the web server.

---