Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

We're trying to setup an SSL server in front of a Weblogic server using Apache as the SSL provider. Here's what's inside of our httpd.conf:

<Location /original>
     SetHandler weblogic-handler
     WebLogicPort 8700
     PathTrim /original
     PathPrepend /destination
     ConnectTimeoutSecs 60

<Location /destination>
     SetHandler weblogic-handler
     WebLogicPort 8700
     ConnectTimeoutSecs 60

This setup works mostly, but in the ssl_error_log file there're these entries:

[Wed Aug 11 14:59:00 2010] [error] [client] ap_proxy: trying GET /original at backend host '; got
     exception 'CONNECTION_REFUSED [os error=0, line 1739 of ../nsapi/URL.cpp]: Error connecting to host'

The weird thing is, the redirection still works, but these annoying entries still shows up. Anyone can point out where did we go wrong? Thanks.

share|improve this question

You might want to tune weblogic with Accept Backlog

To tune the Accept Backlog value from the Administration Console:

  1. Start the Administration Server if it is not already running.

  2. Access the Administration Console for the domain.

  3. Expand the Servers node in the left pane to display the servers configured in your domain.

  4. Click the name of the server instance that you want to configure.

  5. Select the Configuration -> Tuning tab.

  6. Modify the default Accept Backlog value as necessary to tune how many TCP connections can be buffered in a wait queue:During operations, if many connections are dropped or refused at the client, and no other error messages are on the server, the Accept Backlog value might be set too low.

If you are getting "connection refused" messages when you try to access WebLogic Server, raise the Accept Backlog value from the default by 25 percent.

Continue increasing the value by 25 percent until the messages cease to appear.

Click Apply to save your changes.

share|improve this answer

You are seeing original path only because the backend wasnt available, check it in your weblogic access logs.

If your connections to weblogic are being backlogged you should see very high thread usage and this is what you have to solve, identifying the resource causing contention and either using less of this resource or increasing its availability.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.