Apache plugin won't do sticky sessions

Hi,
I'm trying to use the apache plugin, with apache 1.3.26, front-ending 2 WL6.0SP2;
and I can't get session affinity to work.
the plugin get loaded properly, and "works" since it is load balancing requests.
unfortunately, sticky sessions don't
here the relevant config
<IfModule mod_weblogic.c>
WebLogicCluster 10.2.255.35:7070,10.2.255.50:7070
DebugConfigInfo ON
CookieName SID
Debug ALL
</IfModule>
and a dump of the URLs for a single session. you can see it's going to the 2 servers.
================New Request:
Wed Sep 25 08:23:29 2002 Connected to 10.2.255.35:7070
Wed Sep 25 08:23:29 2002 Hdrs to WLS:[X-WebLogic-Force-Cookie]=[true]
Wed Sep 25 08:23:29 2002 Hdrs from WLS:[Set-Cookie]=[SID=PZHUuWPR; path=/]
Wed Sep 25 08:23:29 2002 Hdrs to client:[Set-Cookie]=[SID=PZHUuWPR; path=/]
================New Request:
Wed Sep 25 08:23:29 2002 Init: availcookie=[SID=PZHUuWPR; path=/]
Wed Sep 25 08:23:29 2002 Connected to 10.2.255.35:7070
Wed Sep 25 08:23:29 2002 Hdrs from clnt:[Cookie]=[SID=PZHUuWPR; path=/]
Wed Sep 25 08:23:29 2002 Hdrs to WLS:[Cookie]=[SID=PZHUuWPR; path=/]
Wed Sep 25 08:23:29 2002 Hdrs to WLS:[X-WebLogic-Force-Cookie]=[true]
================New Request:
Wed Sep 25 08:23:29 2002 Init: availcookie=[SID=PZHUuWPR; path=/]
Wed Sep 25 08:23:29 2002 Connected to 10.2.255.50:7070
Wed Sep 25 08:23:29 2002 Hdrs from clnt:[Cookie]=[SID=PZHUuWPR; path=/]
Wed Sep 25 08:23:29 2002 Hdrs to WLS:[Cookie]=[SID=PZHUuWPR; path=/]
Wed Sep 25 08:23:29 2002 Hdrs to WLS:[X-WebLogic-Force-Cookie]=[true]
================New Request:
Wed Sep 25 08:23:29 2002 Init: availcookie=[SID=PZHUuWPR; path=/]
Wed Sep 25 08:23:29 2002 Connected to 10.2.255.50:7070
Wed Sep 25 08:23:29 2002 Hdrs from clnt:[Cookie]=[SID=PZHUuWPR; path=/]
Wed Sep 25 08:23:29 2002 Hdrs to WLS:[Cookie]=[SID=PZHUuWPR; path=/]
Wed Sep 25 08:23:29 2002 Hdrs to WLS:[X-WebLogic-Force-Cookie]=[true]
The weird part is that I'm seeeing this behavior with the iplanet plugin as well.
anyone got any luck in setting that up ?
thanks,
jm.

You can use the console to edit the deployment descriptor for the webapp.
Or you can modify the weblogic.xml and add the following:
<session-descriptor>
<session-param>
<param-name>
PersistentStoreType
</param-name>
<param-value>
Replicated
</param-value>
</session-param>
</session-descriptor>
Some useful links:
http://e-docs.bea.com/wls/docs61/webapp/weblogic_xml.html#1014231
http://e-docs.bea.com/wls/docs61/webapp/sessions.html#100659
http://e-docs.bea.com/wls/docs61/cluster/servlet.html
Regards,
Eric
"Pancday Pac" <[email protected]> wrote in message
news:[email protected]...
Eric,
I also met this problem.
How to "have replicated sessions set for the webapp". What I found is just
the CookieName which I didn't change and just use the default value.
"Eric Gross" <[email protected]> wrote in message
news:[email protected]...
It looks like you have properly setup clustering on WebLogic itself.
You need to make sure you have replicated sessions set for the webapp in
question.
Regards,
Eric
"Jean-Michel Leon" <[email protected]> wrote in message
news:[email protected]...
Hi,
I'm trying to use the apache plugin, with apache 1.3.26, front-ending
2
WL6.0SP2;
and I can't get session affinity to work.
the plugin get loaded properly, and "works" since it is load balancingrequests.
unfortunately, sticky sessions don't
here the relevant config
<IfModule mod_weblogic.c>
WebLogicCluster 10.2.255.35:7070,10.2.255.50:7070
DebugConfigInfo ON
CookieName SID
Debug ALL
</IfModule>
and a dump of the URLs for a single session. you can see it's going to
the
2 servers.
================New Request:
Wed Sep 25 08:23:29 2002 Connected to 10.2.255.35:7070
Wed Sep 25 08:23:29 2002 Hdrs to WLS:[X-WebLogic-Force-Cookie]=[true]
Wed Sep 25 08:23:29 2002 Hdrs from WLS:[Set-Cookie]=[SID=PZHUuWPR;
path=/]
Wed Sep 25 08:23:29 2002 Hdrs to client:[Set-Cookie]=[SID=PZHUuWPR;path=/]
================New Request:
Wed Sep 25 08:23:29 2002 Init: availcookie=[SID=PZHUuWPR; path=/]
Wed Sep 25 08:23:29 2002 Connected to 10.2.255.35:7070
Wed Sep 25 08:23:29 2002 Hdrs from clnt:[Cookie]=[SID=PZHUuWPR;
path=/]
>>>
Wed Sep 25 08:23:29 2002 Hdrs to WLS:[Cookie]=[SID=PZHUuWPR; path=/]
Wed Sep 25 08:23:29 2002 Hdrs to WLS:[X-WebLogic-Force-Cookie]=[true]
================New Request:
Wed Sep 25 08:23:29 2002 Init: availcookie=[SID=PZHUuWPR; path=/]
Wed Sep 25 08:23:29 2002 Connected to 10.2.255.50:7070
Wed Sep 25 08:23:29 2002 Hdrs from clnt:[Cookie]=[SID=PZHUuWPR;path=/]
>>>
Wed Sep 25 08:23:29 2002 Hdrs to WLS:[Cookie]=[SID=PZHUuWPR; path=/]
Wed Sep 25 08:23:29 2002 Hdrs to WLS:[X-WebLogic-Force-Cookie]=[true]
================New Request:
Wed Sep 25 08:23:29 2002 Init: availcookie=[SID=PZHUuWPR; path=/]
Wed Sep 25 08:23:29 2002 Connected to 10.2.255.50:7070
Wed Sep 25 08:23:29 2002 Hdrs from clnt:[Cookie]=[SID=PZHUuWPR;path=/]
>>>
Wed Sep 25 08:23:29 2002 Hdrs to WLS:[Cookie]=[SID=PZHUuWPR; path=/]
Wed Sep 25 08:23:29 2002 Hdrs to WLS:[X-WebLogic-Force-Cookie]=[true]
The weird part is that I'm seeeing this behavior with the iplanetplugin
as well.
anyone got any luck in setting that up ?
thanks,
jm.

Similar Messages

  • Finding the handler host in cluster when using sticky sessions

              Our design is like this: we have Apache front-ending the WL cluster. The session
              is not replicated across WL hosts in cluster. However, the Apache-weblogic bridge
              takes care of handling sticky - sessions ( i.e. forwarding requests in same session
              to one host in cluster )
              Now, we have some code running on Apache itself , in Perl.
              The requirement is as follows : In the Perl code, we trap certain requests which
              are NOT forwarded to Weblogic. However, in the Perl code, we do trap the JSESSIONID
              cookie. Now, using this cookie value, is it possible to know which WL host in
              cluster is handling its corresponding session ??
              This is required, since the Perl module is supposed to make an explicit HTTP request
              to that WL host - passing the JSESSIONID as a parameter - for authentication.
              Thanks,
              Subodh
              

    can the perl module send this request to the apache webserver itself and set
              the cookie the same? That would allow apache plugin to send it to the right
              node.
              "Subodh" <[email protected]> wrote in message
              news:[email protected]..
              >
              > Our design is like this: we have Apache front-ending the WL cluster. The
              session
              > is not replicated across WL hosts in cluster. However, the Apache-weblogic
              bridge
              > takes care of handling sticky - sessions ( i.e. forwarding requests in
              same session
              > to one host in cluster )
              >
              > Now, we have some code running on Apache itself , in Perl.
              >
              > The requirement is as follows : In the Perl code, we trap certain requests
              which
              > are NOT forwarded to Weblogic. However, in the Perl code, we do trap the
              JSESSIONID
              > cookie. Now, using this cookie value, is it possible to know which WL host
              in
              > cluster is handling its corresponding session ??
              >
              > This is required, since the Perl module is supposed to make an explicit
              HTTP request
              > to that WL host - passing the JSESSIONID as a parameter - for
              authentication.
              >
              >
              > Thanks,
              > Subodh
              >
              

  • Apache Plugin is not working with Cluster Entry in httpd.conf

    Hi Guys,
    We have a very particular issue that is happening here in our production environments. Before explaining the issue to you, I will just give a brief of our architecture.
    We are using Weblogic Portal Platform SP4.
    Our current Production Domain Consists of 1 Admin Server and 2 Managed Servers. The managed servers are in a cluster.
    We have two Linux boxes on which the weblogic servers are running. These two machines have IPs: x.x.x.58 and x.x.x.59. Now, the Admin Server and managed Server 1 are started on the machine x.x.x.58 and managed server 2 is started on the machine x.x.x.59. Both the managedServers listen on port 8007.
    This entire setup mentioned in the above paragraph is at a location A (lets say).
    Now, the requests are proxied to the managed server cluster using BEA's Apache plugin residing on Apache. Apache is running on two Linux boxes that are present at a location B.
    Location B is connected to Location A by a dedicated WAN Link.
    Now, before the two Apache servers there is a physical Load Balancer that balances the requests between the two Apache boxes.
    This means that whenever there is a request from the Internet to the weblogic cluster, the load balancer first sends it to either of the Apache servers and then the BEA Apache plugin on that Apache forwards the request via the 2 mbps WAN link to the weblogic cluster.
    Now following is the description of the issue we are facing. We donot know whether the issue is with the plugin or with weblogic server.
    In order that the plugin load balances the requests between the servers in the cluster and for failover, the following entry was put in httpd.conf on both the Apache Servers.
    WebLogicCluster y.y.y.11:8007,y.y.y.13:8007
    Note: Because of the WAN link there is natting used. This implies y.y.y.11 is natted to x.x.x.58 and y.y.y.13 is natted to x.x.x.59.
    Here in lies the issue. When we use this plugin entry the following issue occurs.
    1.     First we go to the home page and login.
    2.     The user is then redirected to a Portal Desktop fitting those credentials.
    3.     Now on this Portal Desktop, invariably whenever we click any of the desktop's links, an HTTP 403 is thrown. This error is thrown because on the desktop there are entitlements so that it cannot be accessed without a user logging in with credentials. But this error indicates that the server is losing the session and entitlement details.
    Why does this happen?
    As a result, we cannot use that plugin entry. The current entry we have is
    WebLogicHost y.y.y.11
    WebLogicPort 8007
    As you can see, here we are only redirecting to one managed server. This entry is not what we want, obviously because if that server fails, the plugin wont know which other server to pass the request on to. Also in this case there is no load balancing.
    Our issues our,
    1. How to resolve this plugin entry issue. How can we use the cluster entry without encountering this HTTP 403 Error?
    3. Consider the following sequence of steps.
    - Request for the home page is served by Apache Server 1
    - User logins in, the login request is sent by the Load Balancer to Apache Server 1 and plugin on Apache Server 1 sends it to the cluster via WAN l ink. Then the internal mechanism works with creating the session id and primary server and secondary server and logs the user in and sends the response via Apache Server 1.
    - Now, the user clicks a link on the desktop. The request now goes to the load balancer and it sends it to Apache Server 2.
    The question is now does the plugin on Apache server 2 correctly understand and send the request to the primary server of that session.
    Pls help me as to giving me some direction in resolving this issue

    From your Xorg.0.log:
    (II) fglrx(0): DRIScreenInit done
    (II) fglrx(0): Kernel Module Version Information:
    (II) fglrx(0): Name: fglrx
    (II) fglrx(0): Version: 8.49.7
    (II) fglrx(0): Date: May 12 2008
    (II) fglrx(0): Desc: ATI FireGL DRM kernel module
    (WW) fglrx(0): Kernel Module version does *not* match driver.
    (EE) fglrx(0): incompatible kernel module detected - HW accelerated OpenGL will not work
    You have to quit X, then rmmod and modprobe the kernel module - you're still using the old one.  (a reboot would technically fix it too)
    # rmmod fglrx
    # modprobe fglrx
    # dmesg | tail
    The dmesg output should say you've successfully loaded the 8.501 driver.

  • How to configure Apache Plug-in CookieName for multiple session cookies?

    I'm deploying an ear file with 2 web applications (.war files) in it and each .war
    has its own CookieName defined in the weblogic.xml file. I need to set up the
    Apache plugin for Weblogic to look at both of them and not just one. Can I simply
    add both CookieName lines into my httpd.conf or will this not work?
    Thanks,
    -wr

    We are facing exactly the same need.
    If you tested it and got answers, we will be happy to hear from you.
    Concerning alternatives, we thought of defining the CookiePath to the contextroot of each WebApp. In our case, the name (and so then the contextroot) of our WebApps is always changing (it includes the version number), so we would have to change the weblogic.xml at each build which we would like to avoid ...
    Apparently the CookiePath can also be set to a "basis" for "begings with" test. See http://groups.google.fr/groups?q=weblogic.xml session-param CookiePath&hl=fr&lr=&ie=UTF-8&oe=UTF-8&selm=3e84a75a%[email protected]&rnum=1 so it could be less harmfull but anyway we do not put too much confidence into this kind of behaviour for future WLS sp/versions :(
    Any help appreciated,
    Philippe.

  • Sticky sessions and Load Balancing in WL Clusters

    We are using iPlanet Web Server 4.1 with WebLogic App Server; and would like
    to implement load balancing with sticky sessions and in-memory state
    replication.
    The documentation in Weblogic says that -
    When using in-memory state replication, your WebLogic Server Cluster must
    live behind one or more proxy servers. The proxy servers are smart enough to
    send servlet requests, belonging to the same HTTP session, back to the same
    server in the cluster that holds the session data.
    (Ref: http://www.weblogic.com/docs51/cluster/setup.html)
    Does this mean that the sticky session configuration has to be done on the
    iPlanet Web Server itself ?
    Also, if WebLogic is used as the Web server, does WebLogic provide any
    support for sticky sessions?
    Any help, suggestions or links to useful info are welcome.
    Regards,
    Milind.

    Mike,
    im curious as to why you would recomend using weblogic as a web server in 6.1?
    I would not for the following reasons:
    - it costs 10x more per cpu list
    - it doesnt support hardware accell cards (afaik, please let me know if this has
    changed)
    iplanet is really good a serving up static html and gif's, especially in ssl if you
    have a hardware accell card. So if you have a site with lots of graphics and you use
    ssl a lot, I think its still a better solution.
    -Joel
    Mike Reiche wrote:
    You get sticky round-robin by default.
    You need to have session tracking turned on (i think it is on by default). You
    need to have the WL plugin configured in iPlanet.
    When WL creates an httpSession, it writes a cookie (or rewrites the URL) back
    to the browser. On subsequent requests, the browser sends the cookie and iPlanet
    plug-in directs the request to the correct WL instance based on the ip address
    of the WL server embedded in the cookie.
    If you are using WLS 6.1, I would recommend using it as a web server (and not
    using iPlanet). I imagine that it supports stickly load balancing as well.
    Mike
    Joel Nylund <[email protected]> wrote:
    you get round robin by default, if you want a different scheme you can
    use one
    of the other 3 options (weight, random or parameter).
    -Joel
    I think weight can be set in weblogic properties. I havent used any other
    than
    round robin.
    Milind Prabhu wrote:
    We are using iPlanet Web Server 4.1 with WebLogic App Server; and wouldlike
    to implement load balancing with sticky sessions and in-memory state
    replication.
    The documentation in Weblogic says that -
    When using in-memory state replication, your WebLogic Server Clustermust
    live behind one or more proxy servers. The proxy servers are smartenough to
    send servlet requests, belonging to the same HTTP session, back tothe same
    server in the cluster that holds the session data.
    (Ref: http://www.weblogic.com/docs51/cluster/setup.html)
    Does this mean that the sticky session configuration has to be doneon the
    iPlanet Web Server itself ?
    Also, if WebLogic is used as the Web server, does WebLogic provideany
    support for sticky sessions?
    Any help, suggestions or links to useful info are welcome.
    Regards,
    Milind.

  • Apache plugin - Cookies

              Hi. We are trying to set up Apache plugin with WebLogic servers in a cluster. Before
              even getting to clustering, I was just trying to proxy requests to one WebLogic Server
              from the Apache server . I am able to get to the WebLogic server thru the proxy plugin
              but when I create a session on the WebLogic server in a jsp page, no cookie with
              the session id is being created . However if I access the WebLogic server directly
              , then there is no problem with session. Is there something on the Apache plugin
              that needs to be enabled to pass cookies thru to the browser.
              Any help will be greatly appreciated.
              Thanks.
              Srivats
              

    Never mind. It turns out that wasn't problem.
    Kirk
    Kirk Everett wrote:
    When the user submits a form, we process it, add a cookie to the
    response and then do a response.sendRedirect() to redirect the user to
    the next page. On the next page we access the cookie. With the apache
    plugin, it seems as if the cookie is not making it through. If we hit
    the weblogic server directly, everything works fine. I saw a post way
    back where someone complained of a similar problem and the solution was
    to do the redirect from the html page using javascript. I'd rather not
    change my application to work correctly with the plugin...
    Has anyone seen similar behavior? I'm running WLS 6.0 SP2.
    Kirk

  • Apache Plugin - Unable to set cookies

    Hi. I am having a really crazy problem. I am running Apache on Solaris with the WebLogic
    proxy plugin and I am also having one WebLogic server running on a different machine(Solaris
    again). When I connect to the WebLogic Server using the Apache -WebLogic bridge and
    login to the system , on the appserver I have a jsp page which basically creates
    a session, stores the login info and does a response.sendRedirect() to the main page
    of the application.
    However there is no cookie with the session id being created . If I directly accessed
    the appserver without the Apache plugin, then everything works fine with a cookie
    containing the session id being created. Is there some thing that needs to be done
    on the Apache side to enable cookies.
    If instead of doing a redirect, I do a encodeRedirectURL and then redirect to the
    main page , then the session id is in the URL and everything is OK. Is there a problem
    creating cookies thru the apache plugin.
    Any advice or response will be greatly appreciated.
    Thanks.
    Srivats

    Hi. I am having a really crazy problem. I am running Apache on Solaris with the WebLogic
    proxy plugin and I am also having one WebLogic server running on a different machine(Solaris
    again). When I connect to the WebLogic Server using the Apache -WebLogic bridge and
    login to the system , on the appserver I have a jsp page which basically creates
    a session, stores the login info and does a response.sendRedirect() to the main page
    of the application.
    However there is no cookie with the session id being created . If I directly accessed
    the appserver without the Apache plugin, then everything works fine with a cookie
    containing the session id being created. Is there some thing that needs to be done
    on the Apache side to enable cookies.
    If instead of doing a redirect, I do a encodeRedirectURL and then redirect to the
    main page , then the session id is in the URL and everything is OK. Is there a problem
    creating cookies thru the apache plugin.
    Any advice or response will be greatly appreciated.
    Thanks.
    Srivats

  • Weblogic Http Apache Plugin not working

    Hi,
    I have installed weblogic server 10.3 on WindowsXP Professional and Http Apache 2.2 is running on port 80. I followed the following document to configure the Apache plugin:
    http://e-docs.bea.com/wls/docs103/plugins/apache.html
    but when I go and test the plugin it always comes back with 404 page not found. As per the documentation I am testing it as
    http://localhost:80/weblogic/
    Here is my httpd.conf
    Include "C:/bea/alui/plumtreeconf/"
    # This is the main Apache HTTP server configuration file.  It contains the
    # configuration directives that give the server its instructions.
    # See <URL:http://httpd.apache.org/docs/2.2> for detailed information.
    # In particular, see
    # <URL:http://httpd.apache.org/docs/2.2/mod/directives.html>
    # for a discussion of each configuration directive.
    # Do NOT simply read the instructions in here without understanding
    # what they do.  They're here only as hints or reminders.  If you are unsure
    # consult the online docs. You have been warned. 
    # Configuration and logfile names: If the filenames you specify for many
    # of the server's control files begin with "/" (or "drive:/" for Win32), the
    # server will use that explicit path.  If the filenames do *not* begin
    # with "/", the value of ServerRoot is prepended -- so "logs/foo.log"
    # with ServerRoot set to "C:/Program Files/Apache Software Foundation/Apache2.2" will be interpreted by the
    # server as "C:/Program Files/Apache Software Foundation/Apache2.2/logs/foo.log".
    # NOTE: Where filenames are specified, you must use forward slashes
    # instead of backslashes (e.g., "c:/apache" instead of "c:\apache").
    # If a drive letter is omitted, the drive on which httpd.exe is located
    # will be used by default.  It is recommended that you always supply
    # an explicit drive letter in absolute paths to avoid confusion.
    # ServerRoot: The top of the directory tree under which the server's
    # configuration, error, and log files are kept.
    # Do not add a slash at the end of the directory path.  If you point
    # ServerRoot at a non-local disk, be sure to point the LockFile directive
    # at a local disk.  If you wish to share the same ServerRoot for multiple
    # httpd daemons, you will need to change at least LockFile and PidFile.
    ServerRoot "C:/Program Files/Apache Software Foundation/Apache2.2"
    # Listen: Allows you to bind Apache to specific IP addresses and/or
    # ports, instead of the default. See also the <VirtualHost>
    # directive.
    # Change this to Listen on specific IP addresses as shown below to
    # prevent Apache from glomming onto all bound IP addresses.
    #Listen 12.34.56.78:80
    Listen 80
    # Dynamic Shared Object (DSO) Support
    # To be able to use the functionality of a module which was built as a DSO you
    # have to place corresponding `LoadModule' lines at this location so the
    # directives contained in it are actually available _before_ they are used.
    # Statically compiled modules (those listed by `httpd -l') do not need
    # to be loaded here.
    # Example:
    # LoadModule foo_module modules/mod_foo.so
    LoadModule actions_module modules/mod_actions.so
    LoadModule alias_module modules/mod_alias.so
    LoadModule asis_module modules/mod_asis.so
    LoadModule auth_basic_module modules/mod_auth_basic.so
    #LoadModule auth_digest_module modules/mod_auth_digest.so
    #LoadModule authn_alias_module modules/mod_authn_alias.so
    #LoadModule authn_anon_module modules/mod_authn_anon.so
    #LoadModule authn_dbd_module modules/mod_authn_dbd.so
    #LoadModule authn_dbm_module modules/mod_authn_dbm.so
    LoadModule authn_default_module modules/mod_authn_default.so
    LoadModule authn_file_module modules/mod_authn_file.so
    #LoadModule authnz_ldap_module modules/mod_authnz_ldap.so
    #LoadModule authz_dbm_module modules/mod_authz_dbm.so
    LoadModule authz_default_module modules/mod_authz_default.so
    LoadModule authz_groupfile_module modules/mod_authz_groupfile.so
    LoadModule authz_host_module modules/mod_authz_host.so
    #LoadModule authz_owner_module modules/mod_authz_owner.so
    LoadModule authz_user_module modules/mod_authz_user.so
    LoadModule autoindex_module modules/mod_autoindex.so
    #LoadModule cache_module modules/mod_cache.so
    #LoadModule cern_meta_module modules/mod_cern_meta.so
    LoadModule cgi_module modules/mod_cgi.so
    #LoadModule charset_lite_module modules/mod_charset_lite.so
    #LoadModule dav_module modules/mod_dav.so
    #LoadModule dav_fs_module modules/mod_dav_fs.so
    #LoadModule dav_lock_module modules/mod_dav_lock.so
    #LoadModule dbd_module modules/mod_dbd.so
    #LoadModule deflate_module modules/mod_deflate.so
    LoadModule dir_module modules/mod_dir.so
    #LoadModule disk_cache_module modules/mod_disk_cache.so
    #LoadModule dumpio_module modules/mod_dumpio.so
    LoadModule env_module modules/mod_env.so
    #LoadModule expires_module modules/mod_expires.so
    #LoadModule ext_filter_module modules/mod_ext_filter.so
    #LoadModule file_cache_module modules/mod_file_cache.so
    #LoadModule filter_module modules/mod_filter.so
    #LoadModule headers_module modules/mod_headers.so
    #LoadModule ident_module modules/mod_ident.so
    #LoadModule imagemap_module modules/mod_imagemap.so
    LoadModule include_module modules/mod_include.so
    #LoadModule info_module modules/mod_info.so
    LoadModule isapi_module modules/mod_isapi.so
    #LoadModule ldap_module modules/mod_ldap.so
    #LoadModule logio_module modules/mod_logio.so
    LoadModule log_config_module modules/mod_log_config.so
    #LoadModule log_forensic_module modules/mod_log_forensic.so
    #LoadModule mem_cache_module modules/mod_mem_cache.so
    LoadModule mime_module modules/mod_mime.so
    #LoadModule mime_magic_module modules/mod_mime_magic.so
    LoadModule negotiation_module modules/mod_negotiation.so
    LoadModule proxy_module modules/mod_proxy.so
    #LoadModule proxy_ajp_module modules/mod_proxy_ajp.so
    #LoadModule proxy_balancer_module modules/mod_proxy_balancer.so
    #LoadModule proxy_connect_module modules/mod_proxy_connect.so
    LoadModule proxy_ftp_module modules/mod_proxy_ftp.so
    LoadModule proxy_http_module modules/mod_proxy_http.so
    #LoadModule rewrite_module modules/mod_rewrite.so
    LoadModule setenvif_module modules/mod_setenvif.so
    #LoadModule speling_module modules/mod_speling.so
    #LoadModule ssl_module modules/mod_ssl.so
    #LoadModule status_module modules/mod_status.so
    #LoadModule substitute_module modules/mod_substitute.so
    #LoadModule unique_id_module modules/mod_unique_id.so
    #LoadModule userdir_module modules/mod_userdir.so
    #LoadModule usertrack_module modules/mod_usertrack.so
    #LoadModule version_module modules/mod_version.so
    #LoadModule vhost_alias_module modules/mod_vhost_alias.so
    LoadModule weblogic_module modules/mod_wl_22.so
    <IfModule mod_weblogic.c>
      WebLogicHost localhost
      WebLogicPort 7001
    </IfModule>
    <Location /weblogic>
      SetHandler weblogic-handler
      PathTrim /weblogic
    </Location>
    <IfModule !mpm_netware_module>
    <IfModule !mpm_winnt_module>
    # If you wish httpd to run as a different user or group, you must run
    # httpd as root initially and it will switch. 
    # User/Group: The name (or #number) of the user/group to run httpd as.
    # It is usually good practice to create a dedicated user and group for
    # running httpd, as with most system services.
    User daemon
    Group daemon
    </IfModule>
    </IfModule>
    # 'Main' server configuration
    # The directives in this section set up the values used by the 'main'
    # server, which responds to any requests that aren't handled by a
    # <VirtualHost> definition.  These values also provide defaults for
    # any <VirtualHost> containers you may define later in the file.
    # All of these directives may appear inside <VirtualHost> containers,
    # in which case these default settings will be overridden for the
    # virtual host being defined.
    # ServerAdmin: Your address, where problems with the server should be
    # e-mailed.  This address appears on some server-generated pages, such
    # as error documents.  e.g. [email protected]
    ServerAdmin [email protected]
    # ServerName gives the name and port that the server uses to identify itself.
    # This can often be determined automatically, but we recommend you specify
    # it explicitly to prevent problems during startup.
    # If your host doesn't have a registered DNS name, enter its IP address here.
    #ServerName localhost:80
    # DocumentRoot: The directory out of which you will serve your
    # documents. By default, all requests are taken from this directory, but
    # symbolic links and aliases may be used to point to other locations.
    DocumentRoot "C:/Program Files/Apache Software Foundation/Apache2.2/htdocs"
    # Each directory to which Apache has access can be configured with respect
    # to which services and features are allowed and/or disabled in that
    # directory (and its subdirectories).
    # First, we configure the "default" to be a very restrictive set of
    # features. 
    ProxyRequests On
    <Directory />
        Options FollowSymLinks
        AllowOverride None
        Order deny,allow
        Deny from all
    </Directory>
    # Note that from this point forward you must specifically allow
    # particular features to be enabled - so if something's not working as
    # you might expect, make sure that you have specifically enabled it
    # below.
    # This should be changed to whatever you set DocumentRoot to.
    <Directory "C:/Program Files/Apache Software Foundation/Apache2.2/htdocs">
        # Possible values for the Options directive are "None", "All",
        # or any combination of:
        #   Indexes Includes FollowSymLinks SymLinksifOwnerMatch ExecCGI MultiViews
        # Note that "MultiViews" must be named *explicitly* --- "Options All"
        # doesn't give it to you.
        # The Options directive is both complicated and important.  Please see
        # http://httpd.apache.org/docs/2.2/mod/core.html#options
        # for more information.
        Options Indexes FollowSymLinks
        # AllowOverride controls what directives may be placed in .htaccess files.
        # It can be "All", "None", or any combination of the keywords:
        #   Options FileInfo AuthConfig Limit
        AllowOverride None
        # Controls who can get stuff from this server.
        Order allow,deny
        Allow from all
    </Directory>
    # DirectoryIndex: sets the file that Apache will serve if a directory
    # is requested.
    <IfModule dir_module>
        DirectoryIndex index.html
    </IfModule>
    # The following lines prevent .htaccess and .htpasswd files from being
    # viewed by Web clients.
    <FilesMatch "^\.ht">
        Order allow,deny
        Deny from all
        Satisfy All
    </FilesMatch>
    # ErrorLog: The location of the error log file.
    # If you do not specify an ErrorLog directive within a <VirtualHost>
    # container, error messages relating to that virtual host will be
    # logged here.  If you *do* define an error logfile for a <VirtualHost>
    # container, that host's errors will be logged there and not here.
    ErrorLog "logs/error.log"
    # LogLevel: Control the number of messages logged to the error_log.
    # Possible values include: debug, info, notice, warn, error, crit,
    # alert, emerg.
    LogLevel warn
    <IfModule log_config_module>
        # The following directives define some format nicknames for use with
        # a CustomLog directive (see below).
        LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\"" combined
        LogFormat "%h %l %u %t \"%r\" %>s %b" common
        <IfModule logio_module>
          # You need to enable mod_logio.c to use %I and %O
          LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\" %I %O" combinedio
        </IfModule>
        # The location and format of the access logfile (Common Logfile Format).
        # If you do not define any access logfiles within a <VirtualHost>
        # container, they will be logged here.  Contrariwise, if you *do*
        # define per-<VirtualHost> access logfiles, transactions will be
        # logged therein and *not* in this file.
        CustomLog "logs/access.log" common
        # If you prefer a logfile with access, agent, and referer information
        # (Combined Logfile Format) you can use the following directive.
        #CustomLog "logs/access.log" combined
    </IfModule>
    <IfModule alias_module>
        # Redirect: Allows you to tell clients about documents that used to
        # exist in your server's namespace, but do not anymore. The client
        # will make a new request for the document at its new location.
        # Example:
        # Redirect permanent /foo http://localhost/bar
        # Alias: Maps web paths into filesystem paths and is used to
        # access content that does not live under the DocumentRoot.
        # Example:
        # Alias /webpath /full/filesystem/path
        # If you include a trailing / on /webpath then the server will
        # require it to be present in the URL.  You will also likely
        # need to provide a <Directory> section to allow access to
        # the filesystem path.
        # ScriptAlias: This controls which directories contain server scripts.
        # ScriptAliases are essentially the same as Aliases, except that
        # documents in the target directory are treated as applications and
        # run by the server when requested rather than as documents sent to the
        # client.  The same rules about trailing "/" apply to ScriptAlias
        # directives as to Alias.
        ScriptAlias /cgi-bin/ "C:/Program Files/Apache Software Foundation/Apache2.2/cgi-bin/"
    </IfModule>
    <IfModule cgid_module>
        # ScriptSock: On threaded servers, designate the path to the UNIX
        # socket used to communicate with the CGI daemon of mod_cgid.
        #Scriptsock logs/cgisock
    </IfModule>
    # "C:/Program Files/Apache Software Foundation/Apache2.2/cgi-bin" should be changed to whatever your ScriptAliased
    # CGI directory exists, if you have that configured.
    <Directory "C:/Program Files/Apache Software Foundation/Apache2.2/cgi-bin">
        AllowOverride None
        Options None
        Order allow,deny
        Allow from all
    </Directory>
    # DefaultType: the default MIME type the server will use for a document
    # if it cannot otherwise determine one, such as from filename extensions.
    # If your server contains mostly text or HTML documents, "text/plain" is
    # a good value.  If most of your content is binary, such as applications
    # or images, you may want to use "application/octet-stream" instead to
    # keep browsers from trying to display binary files as though they are
    # text.
    DefaultType text/plain
    <IfModule mime_module>
        # TypesConfig points to the file containing the list of mappings from
        # filename extension to MIME-type.
        TypesConfig conf/mime.types
        # AddType allows you to add to or override the MIME configuration
        # file specified in TypesConfig for specific file types.
        #AddType application/x-gzip .tgz
        # AddEncoding allows you to have certain browsers uncompress
        # information on the fly. Note: Not all browsers support this.
        #AddEncoding x-compress .Z
        #AddEncoding x-gzip .gz .tgz
        # If the AddEncoding directives above are commented-out, then you
        # probably should define those extensions to indicate media types:
        AddType application/x-compress .Z
        AddType application/x-gzip .gz .tgz
        # AddHandler allows you to map certain file extensions to "handlers":
        # actions unrelated to filetype. These can be either built into the server
        # or added with the Action directive (see below)
        # To use CGI scripts outside of ScriptAliased directories:
        # (You will also need to add "ExecCGI" to the "Options" directive.)
        #AddHandler cgi-script .cgi
        # For type maps (negotiated resources):
        #AddHandler type-map var
        # Filters allow you to process content before it is sent to the client.
        # To parse .shtml files for server-side includes (SSI):
        # (You will also need to add "Includes" to the "Options" directive.)
        #AddType text/html .shtml
        #AddOutputFilter INCLUDES .shtml
    </IfModule>
    # The mod_mime_magic module allows the server to use various hints from the
    # contents of the file itself to determine its type.  The MIMEMagicFile
    # directive tells the module where the hint definitions are located.
    #MIMEMagicFile conf/magic
    # Customizable error responses come in three flavors:
    # 1) plain text 2) local redirects 3) external redirects
    # Some examples:
    #ErrorDocument 500 "The server made a boo boo."
    #ErrorDocument 404 /missing.html
    #ErrorDocument 404 "/cgi-bin/missing_handler.pl"
    #ErrorDocument 402 http://localhost/subscription_info.html
    # EnableMMAP and EnableSendfile: On systems that support it,
    # memory-mapping or the sendfile syscall is used to deliver
    # files.  This usually improves server performance, but must
    # be turned off when serving from networked-mounted
    # filesystems or if support for these functions is otherwise
    # broken on your system.
    #EnableMMAP off
    #EnableSendfile off
    # Supplemental configuration
    # The configuration files in the conf/extra/ directory can be
    # included to add extra features or to modify the default configuration of
    # the server, or you may simply copy their contents here and change as
    # necessary.
    # Server-pool management (MPM specific)
    #Include conf/extra/httpd-mpm.conf
    # Multi-language error messages
    #Include conf/extra/httpd-multilang-errordoc.conf
    # Fancy directory listings
    #Include conf/extra/httpd-autoindex.conf
    # Language settings
    #Include conf/extra/httpd-languages.conf
    # User home directories
    #Include conf/extra/httpd-userdir.conf
    # Real-time info on requests and configuration
    #Include conf/extra/httpd-info.conf
    # Virtual hosts
    #Include conf/extra/httpd-vhosts.conf
    # Local access to the Apache HTTP Server Manual
    #Include conf/extra/httpd-manual.conf
    # Distributed authoring and versioning (WebDAV)
    #Include conf/extra/httpd-dav.conf
    # Various default settings
    #Include conf/extra/httpd-default.conf
    # Secure (SSL/TLS) connections
    #Include conf/extra/httpd-ssl.conf
    # Note: The following must must be present to support
    #       starting without SSL on platforms with no /dev/random equivalent
    #       but a statically compiled-in mod_ssl.
    <IfModule ssl_module>
    SSLRandomSeed startup builtin
    SSLRandomSeed connect builtin
    </IfModule>Is there anything else I need to add to this file. As I am trying to install ALUI and for this I need to add the plugin as when I go to my portal page none of the
    images shows. Any help is appreciated.
    Thanks

    Hi,
    There is patch for the webserver(Apache Plugin),thats needs to be downloaded from Metalink,dont use the default plugin that comes with the weblogic 10.3 installtion.
    Regards,
    Dinesh

  • Java Plugin won't work in Netscape 7.1

    I'm using Windows XP Home with Netscape 7.1, and the Java plugin won't work.
    Java Plug-in 1.4.2_05 for Netscape Navigator (DLL Helper) is listed 7 times in Help>About:Plugins;
    The Java Plugin works in Internet Explorer (I use the Test Java Virtual Machine to determine this). With Netscape, I just get the "Click here to get the plugin" window, and believe me, I've clicked here many times, and gone through the installation process, and it still doesn't work. I've uninstalled Java, rebooted, and installed it with the browsers closed, and it still doesn't work. Everything else in Netscape seems to be working properly.
    Under Edit>Preferences>Advanced in Netscape I have "Enable Java" checked.
    I posted this problem in the Windows-BBS Netscape and Mozilla forum, http://www.windowsbbs.com/showthread.php?t=33994, and tried everything suggested there, but it still didn't work.
    Anybody have any suggestions?

    I was facing a similar problem. I think the problem is with different versions of JRE. For example, I was trying to associate with Netscape the JRE version of 1.4.2_01 without any success. But on associating jdk version 1.4.2_05, it started working fine.
    Regards,
    Harish

  • Setup issues: Apache plugin for Weblogic

    Hi,
    I've spent couple of days without success trying to configure apache plugin for weblogic. I've configured in accordance with bea documentation and it works fine in windows environment but fails in Solaris 9.
    Plugin log file says it's processed the request successfully but I see error message in browser saying it can't find the jsp file. It works fine if I access the weblogic box directly without going through apache.
    I'm using Weblogic 8.1 SP2, single server.
    Please find below the messages appear in browser, plugin logs, and apache version.
    Thanks in advance for your help.
    ======================Browser Error Message================
    JSP Processing Error
    HTTP Error Code: 404
    Error Message:JSPG0036E: Failed to find resource /AppConsole/common/login.jsp
    Root Cause:java.io.FileNotFoundException: JSPG0036E: Failed to find resource /AppConsole/common/login.jsp     at com.ibm.ws.jsp.webcontainerext.JSPExtensionProcessor.findWrapper(JSPExtensionProcessor.java:246)     at com.ibm.ws.jsp.webcontainerext.JSPExtensionProcessor.handleRequest(JSPExtensionProcessor.java:228)     at com.ibm.ws.webcontainer.webapp.WebApp.handleRequest(WebApp.java:2841)     at com.ibm.ws.webcontainer.webapp.WebGroup.handleRequest(WebGroup.java:220)     at com.ibm.ws.webcontainer.VirtualHost.handleRequest(VirtualHost.java:204)     at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:1681)     at com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:77)     at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:421)     at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewInformation(HttpInboundLink.java:367)     at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.ready(HttpInboundLink.java:276)     at com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.sendToDiscriminaters(NewConnectionInitialReadCallback.java:201)     at com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.complete(NewConnectionInitialReadCallback.java:103)     at com.ibm.ws.tcp.channel.impl.WorkQueueManager.requestComplete(WorkQueueManager.java:548)     at com.ibm.ws.tcp.channel.impl.WorkQueueManager.attemptIO(WorkQueueManager.java:601)     at com.ibm.ws.tcp.channel.impl.WorkQueueManager.workerRun(WorkQueueManager.java:934)     at com.ibm.ws.tcp.channel.impl.WorkQueueManager$Worker.run(WorkQueueManager.java:1021)     at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1332)
    ======================Browser Error Message End================
    ==========Apache version============
    Please find apache version and plugin logs below:
    # ./apachectl -v
    Server version: IBM_HTTP_Server/6.0 Apache/2.0.47
    Server built: Nov 4 2004 09:58:18
    ==========Apache version End============
    =================Plugin Logs================
    ================New Request: [GET /AppConsole/ HTTP/1.1] =================
    Mon Jun 12 08:20:14 2006 INFO: SSL is not configured
    Mon Jun 12 08:20:14 2006 After trimming path: '/AppConsole/'
    Mon Jun 12 08:20:14 2006 The final request string is '/AppConsole/'
    Mon Jun 12 08:20:14 2006 SEARCHING id=[83.231.147.129:27110] from current ID=[83.231.147.129:27110]
    Mon Jun 12 08:20:14 2006 @@@FOUND...id=[83.231.147.129:27110], server_name=[83.231.147.65], server_port=[80]
    Mon Jun 12 08:20:14 2006 attempt #0 out of a max of 5
    Mon Jun 12 08:20:14 2006 general list: trying connect to '83.231.147.129'/27110/27110 at line 1981 for '/AppConsole/'
    Mon Jun 12 08:20:14 2006 INFO: New NON-SSL URL
    Mon Jun 12 08:20:14 2006 general list: trying connect to '83.231.147.129'/27110
    Mon Jun 12 08:20:14 2006 Hdrs from clnt:[Via]=[1.0 NMUKPER]
    Mon Jun 12 08:20:14 2006 Hdrs from clnt:[User-Agent]=[Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; NissanEurope; .NET CLR 1.0.3705)]
    Mon Jun 12 08:20:14 2006 Hdrs from clnt:[Accept]=[image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, application/x-shockwave-flash, application/vnd.ms-excel, application/vnd.ms-powerpoint, application/msword, */*]
    Mon Jun 12 08:20:14 2006 Hdrs from clnt:[Accept-Language]=[en-gb,fr;q=0.8,es;q=0.6,nl;q=0.4,ja;q=0.2]
    Mon Jun 12 08:20:14 2006 Hdrs from clnt:[Host]=[83.231.147.65]
    Mon Jun 12 08:20:14 2006 URL::sendHeaders(): meth='GET' file='/AppConsole/' protocol='HTTP/1.1'
    Mon Jun 12 08:20:14 2006 Hdrs to WLS:[Via]=[1.0 NMUKPER]
    Mon Jun 12 08:20:14 2006 Hdrs to WLS:[User-Agent]=[Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; NissanEurope; .NET CLR 1.0.3705)]
    Mon Jun 12 08:20:14 2006 Hdrs to WLS:[Accept]=[image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, application/x-shockwave-flash, application/vnd.ms-excel, application/vnd.ms-powerpoint, application/msword, */*]
    Mon Jun 12 08:20:14 2006 Hdrs to WLS:[Accept-Language]=[en-gb,fr;q=0.8,es;q=0.6,nl;q=0.4,ja;q=0.2]
    Mon Jun 12 08:20:14 2006 Hdrs to WLS:[Host]=[83.231.147.65]
    Mon Jun 12 08:20:14 2006 Hdrs to WLS:[Connection]=[Keep-Alive]
    Mon Jun 12 08:20:14 2006 Hdrs to WLS:[WL-Proxy-SSL]=[false]
    Mon Jun 12 08:20:14 2006 Hdrs to WLS:[X-WebLogic-Force-JVMID]=[unset]
    Mon Jun 12 08:20:14 2006 Hdrs to WLS:[WL-Proxy-Client-IP]=[62.172.128.4]
    Mon Jun 12 08:20:14 2006 Hdrs to WLS:[Proxy-Client-IP]=[62.172.128.4]
    Mon Jun 12 08:20:14 2006 Hdrs to WLS:[X-Forwarded-For]=[62.172.128.4]
    Mon Jun 12 08:20:14 2006 Hdrs to WLS:[X-WebLogic-Request-ClusterInfo]=[true]
    Mon Jun 12 08:20:14 2006 Hdrs to WLS:[X-WebLogic-KeepAliveSecs]=[30]
    Mon Jun 12 08:20:14 2006 INFO: sysSend 639
    Mon Jun 12 08:20:14 2006 Hdrs from WLS:[Date]=[Mon, 12 Jun 2006 07:20:14 GMT]
    Mon Jun 12 08:20:14 2006 Hdrs from WLS:[Location]=[http://83.231.147.65/AppConsole/common/login.jsp;jsessionid=ENVulmFw71QICHDuP5nSB8kRPe2teTcbjdBtwkjwSY96UxrHEYXr!-656182639!NONE]
    Mon Jun 12 08:20:14 2006 Hdrs from WLS:[Server]=[WebLogic Server 8.1 SP2 Fri Dec 5 15:01:51 PST 2003 316284 with CR174792 CR173632 CR135189 CR134122 CR133071 CR132575 CR129505 CR129371 CR129122 CR128888 CR124746 CR124239 CR107373]
    Mon Jun 12 08:20:14 2006 Hdrs from WLS:[Content-Type]=[text/html]
    Mon Jun 12 08:20:14 2006 Hdrs from WLS:[Set-Cookie]=[JSESSIONID=ENVulmFw71QICHDuP5nSB8kRPe2teTcbjdBtwkjwSY96UxrHEYXr!-656182639!NONE; path=/]
    Mon Jun 12 08:20:14 2006 Hdrs from WLS:[X-WebLogic-Cluster-Hash]=[mx4NFnJY0ypWiiF1G2lM080SToc]
    Mon Jun 12 08:20:14 2006 Hdrs from WLS:[X-WebLogic-Cluster-List]=[-656182639!eus0000160.eu.verio.net!27110!-1]
    Mon Jun 12 08:20:14 2006 Hdrs from WLS:[Transfer-Encoding]=[chunked]
    Mon Jun 12 08:20:14 2006 parsed all headers OK
    Mon Jun 12 08:20:14 2006 Hdrs to client:[Date]=[Mon, 12 Jun 2006 07:20:14 GMT]
    Mon Jun 12 08:20:14 2006 Hdrs to client:[Location]=[http://83.231.147.65/AppConsole/common/login.jsp;jsessionid=ENVulmFw71QICHDuP5nSB8kRPe2teTcbjdBtwkjwSY96UxrHEYXr!-656182639!NONE]
    Mon Jun 12 08:20:14 2006 Hdrs to client:[Server]=[WebLogic Server 8.1 SP2 Fri Dec 5 15:01:51 PST 2003 316284 with CR174792 CR173632 CR135189 CR134122 CR133071 CR132575 CR129505 CR129371 CR129122 CR128888 CR124746 CR124239 CR107373]
    Mon Jun 12 08:20:14 2006 Hdrs to client:[Set-Cookie]=[JSESSIONID=ENVulmFw71QICHDuP5nSB8kRPe2teTcbjdBtwkjwSY96UxrHEYXr!-656182639!NONE; path=/]
    Mon Jun 12 08:20:14 2006 Hdrs to client:[X-WebLogic-Cluster-List]=[-656182639!eus0000160.eu.verio.net!27110!-1]
    Mon Jun 12 08:20:14 2006 canRecycle: conn=1 status=302 isKA=1 clen=-1 isCTE=1
    Mon Jun 12 08:20:14 2006 closeConnection in load_utils: deleting URL*
    Mon Jun 12 08:20:14 2006 request [AppConsole/] processed sucessfully..................
    =================Plugin Logs End================

    Yes it is IBM Http Server, but it works fine from Windows accessing the same weblogic server I'm trying to connect from Solaris.
    I see 500 error in the apache access log file.
    I've also tried with by setting "MaxRequestsPerChild" to 0 in the apache config file but no good.
    Please find below httpd.conf file content.
    ==============httpd.conf===============
    ServerName eus0000168.eu.verio.net
    # Based upon the NCSA server configuration files originally by Rob McCool.
    # This is the main Apache server configuration file. It contains the
    # configuration directives that give the server its instructions.
    # See <URL:http://httpd.apache.org/docs-2.0/> for detailed information about
    # the directives.
    # Do NOT simply read the instructions in here without understanding
    # what they do. They're here only as hints or reminders. If you are unsure
    # consult the online docs. You have been warned.
    # The configuration directives are grouped into three basic sections:
    # 1. Directives that control the operation of the Apache server process as a
    # whole (the 'global environment').
    # 2. Directives that define the parameters of the 'main' or 'default' server,
    # which responds to requests that aren't handled by a virtual host.
    # These directives also provide default values for the settings
    # of all virtual hosts.
    # 3. Settings for virtual hosts, which allow Web requests to be sent to
    # different IP addresses or hostnames and have them handled by the
    # same Apache server process.
    # Configuration and logfile names: If the filenames you specify for many
    # of the server's control files begin with "/" (or "drive:/" for Win32), the
    # server will use that explicit path. If the filenames do not begin
    # with "/", the value of ServerRoot is prepended -- so "logs/foo.log"
    # with ServerRoot set to "/opt/IBMIHS" will be interpreted by the
    # server as "/opt/IBMIHS/logs/foo.log".
    ### Section 1: Global Environment
    # The directives in this section affect the overall operation of Apache,
    # such as the number of concurrent requests it can handle or where it
    # can find its configuration files.
    # ServerRoot: The top of the directory tree under which the server's
    # configuration, error, and log files are kept.
    # NOTE! If you intend to place this on an NFS (or otherwise network)
    # mounted filesystem then please read the LockFile documentation (available
    # at <URL:http://httpd.apache.org/docs-2.0/mod/mpm_common.html#lockfile>);
    # you will save yourself a lot of trouble.
    # Do NOT add a slash at the end of the directory path.
    ServerRoot "/opt/IBMIHS"
    # The accept serialization lock file MUST BE STORED ON A LOCAL DISK.
    #LockFile logs/accept.lock
    # PidFile: The file in which the server should record its process
    # identification number when it starts.
    PidFile logs/httpd.pid
    # Timeout: The number of seconds before receives and sends time out.
    Timeout 300
    # KeepAlive: Whether or not to allow persistent connections (more than
    # one request per connection). Set to "Off" to deactivate.
    KeepAlive On
    # MaxKeepAliveRequests: The maximum number of requests to allow
    # during a persistent connection. Set to 0 to allow an unlimited amount.
    # We recommend you leave this number high, for maximum performance.
    MaxKeepAliveRequests 100
    # KeepAliveTimeout: Number of seconds to wait for the next request from the
    # same client on the same connection.
    KeepAliveTimeout 10
    ## Server-Pool Size Regulation (MPM specific)
    # worker MPM
    # ThreadLimit: maximum setting of ThreadsPerChild
    # ServerLimit: maximum setting of StartServers
    # StartServers: initial number of server processes to start
    # MaxClients: maximum number of simultaneous client connections
    # MinSpareThreads: minimum number of worker threads which are kept spare
    # MaxSpareThreads: maximum number of worker threads which are kept spare
    # ThreadsPerChild: constant number of worker threads in each server process
    # MaxRequestsPerChild: maximum number of requests a server process serves
    <IfModule worker.c>
    #StartServers 5
    StartServers 1
    MaxClients 150
    MinSpareThreads 25
    MaxSpareThreads 75
    ThreadsPerChild 25
    MaxRequestsPerChild 1000
    </IfModule>
    # Listen: Allows you to bind Apache to specific IP addresses and/or
    # ports, in addition to the default. See also the <VirtualHost>
    # directive.
    # Change this to Listen on specific IP addresses as shown below to
    # prevent Apache from glomming onto all bound IP addresses (0.0.0.0)
    # Change this to "Listen 0.0.0.0:port" to restrict the server to
    # IPv4.
    #Listen 12.34.56.78:80
    Listen 80
    # Dynamic Shared Object (DSO) Support
    # To be able to use the functionality of a module which was built as a DSO you
    # have to place corresponding `LoadModule' lines at this location so the
    # directives contained in it are actually available before they are used.
    # Statically compiled modules (those listed by `httpd -l') do not need
    # to be loaded here.
    # Example:
    # LoadModule foo_module modules/mod_foo.so
    LoadModule access_module modules/mod_access.so
    LoadModule auth_module modules/mod_auth.so
    #LoadModule auth_anon_module modules/mod_auth_anon.so
    LoadModule auth_dbm_module modules/mod_auth_dbm.so
    LoadModule include_module modules/mod_include.so
    LoadModule log_config_module modules/mod_log_config.so
    LoadModule env_module modules/mod_env.so
    #LoadModule mime_magic_module modules/mod_mime_magic.so
    #LoadModule cern_meta_module modules/mod_cern_meta.so
    LoadModule expires_module modules/mod_expires.so
    LoadModule headers_module modules/mod_headers.so
    LoadModule usertrack_module modules/mod_usertrack.so
    LoadModule unique_id_module modules/mod_unique_id.so
    LoadModule setenvif_module modules/mod_setenvif.so
    #LoadModule proxy_module modules/mod_proxy.so
    #LoadModule proxy_connect_module modules/mod_proxy_connect.so
    #LoadModule proxy_ftp_module modules/mod_proxy_ftp.so
    #LoadModule proxy_http_module modules/mod_proxy_http.so
    LoadModule mime_module modules/mod_mime.so
    #LoadModule dav_module modules/mod_dav.so
    LoadModule autoindex_module modules/mod_autoindex.so
    LoadModule asis_module modules/mod_asis.so
    #LoadModule info_module modules/mod_info.so
    LoadModule cgid_module modules/mod_cgid.so
    #LoadModule dav_fs_module modules/mod_dav_fs.so
    LoadModule vhost_alias_module modules/mod_vhost_alias.so
    LoadModule dir_module modules/mod_dir.so
    LoadModule imap_module modules/mod_imap.so
    LoadModule actions_module modules/mod_actions.so
    #LoadModule speling_module modules/mod_speling.so
    LoadModule userdir_module modules/mod_userdir.so
    LoadModule alias_module modules/mod_alias.so
    LoadModule rewrite_module modules/mod_rewrite.so
    #LoadModule deflate_module modules/mod_deflate.so
    # ExtendedStatus controls whether Apache will generate "full" status
    # information (ExtendedStatus On) or just basic information (ExtendedStatus
    # Off) when the "server-status" handler is called. The default is Off.
    #LoadModule status_module modules/mod_status.so
    <IfModule mod_status.c>
    ExtendedStatus On
    </IfModule>
    ### Section 2: 'Main' server configuration
    # The directives in this section set up the values used by the 'main'
    # server, which responds to any requests that aren't handled by a
    # <VirtualHost> definition. These values also provide defaults for
    # any <VirtualHost> containers you may define later in the file.
    # All of these directives may appear inside <VirtualHost> containers,
    # in which case these default settings will be overridden for the
    # virtual host being defined.
    # If you wish httpd to run as a different user or group, you must run
    # httpd as root initially and it will switch.
    # User/Group: The name (or #number) of the user/group to run httpd as.
    # . On SCO (ODT 3) use "User nouser" and "Group nogroup".
    # . On HPUX you may not be able to use shared memory as nobody, and the
    # suggested workaround is to create a user www and use that user.
    # NOTE that some kernels refuse to setgid(Group) or semctl(IPC_SET)
    # when the value of (unsigned)Group is above 60000;
    # don't use Group #-1 on these systems!
    User nobody
    Group nobody
    # ServerAdmin: Your address, where problems with the server should be
    # e-mailed. This address appears on some server-generated pages, such
    # as error documents. e.g. [email protected]
    ServerAdmin [email protected]
    # ServerName gives the name and port that the server uses to identify itself.
    # This can often be determined automatically, but we recommend you specify
    # it explicitly to prevent problems during startup.
    # If this is not set to valid DNS name for your host, server-generated
    # redirections will not work. See also the UseCanonicalName directive.
    # If your host doesn't have a registered DNS name, enter its IP address here.
    # You will have to access it by its address anyway, and this will make
    # redirections work in a sensible way.
    #ServerName new.host.name:80
    # UseCanonicalName: Determines how Apache constructs self-referencing
    # URLs and the SERVER_NAME and SERVER_PORT variables.
    # When set "Off", Apache will use the Hostname and Port supplied
    # by the client. When set "On", Apache will use the value of the
    # ServerName directive.
    UseCanonicalName Off
    # DocumentRoot: The directory out of which you will serve your
    # documents. By default, all requests are taken from this directory, but
    # symbolic links and aliases may be used to point to other locations.
    #DocumentRoot "/opt/IBMIHS/htdocs/en_US"
    #DocumentRoot "/www/a"
    # Each directory to which Apache has access can be configured with respect
    # to which services and features are allowed and/or disabled in that
    # directory (and its subdirectories).
    # First, we configure the "default" to be a very restrictive set of
    # features.
    <Directory />
    Options FollowSymLinks
    AllowOverride None
    </Directory>
    # Note that from this point forward you must specifically allow
    # particular features to be enabled - so if something's not working as
    # you might expect, make sure that you have specifically enabled it
    # below.
    # This should be changed to whatever you set DocumentRoot to.
    <Directory "/opt/IBMIHS/htdocs/en_US">
    # Possible values for the Options directive are "None", "All",
    # or any combination of:
    # Indexes Includes FollowSymLinks SymLinksifOwnerMatch ExecCGI Multiviews
    # Note that "MultiViews" must be named explicitly --- "Options All"
    # doesn't give it to you.
    # The Options directive is both complicated and important. Please see
    # http://httpd.apache.org/docs-2.0/mod/core.html#options
    # for more information.
    Options Indexes FollowSymLinks
    # AllowOverride controls what directives may be placed in .htaccess files.
    # It can be "All", "None", or any combination of the keywords:
    # Options FileInfo AuthConfig Limit
    AllowOverride None
    # Controls who can get stuff from this server.
    Order allow,deny
    Allow from all
    </Directory>
    # UserDir: The name of the directory that is appended onto a user's home
    # directory if a ~user request is received.
    UserDir public_html
    # Control access to UserDir directories. The following is an example
    # for a site where these directories are restricted to read-only.
    #<Directory /home/*/public_html>
    # AllowOverride FileInfo AuthConfig Limit Indexes
    # Options MultiViews Indexes SymLinksIfOwnerMatch IncludesNoExec
    # <Limit GET POST OPTIONS PROPFIND>
    # Order allow,deny
    # Allow from all
    # </Limit>
    # <LimitExcept GET POST OPTIONS PROPFIND>
    # Order deny,allow
    # Deny from all
    # </LimitExcept>
    #</Directory>
    # DirectoryIndex: sets the file that Apache will serve if a directory
    # is requested.
    # The index.html.var file (a type-map) is used to deliver content-
    # negotiated documents. The MultiViews Option can be used for the
    # same purpose, but it is much slower.
    DirectoryIndex index.html index.html.var
    # AccessFileName: The name of the file to look for in each directory
    # for additional configuration directives. See also the AllowOverride
    # directive.
    AccessFileName .htaccess
    # The following lines prevent .htaccess and .htpasswd files from being
    # viewed by Web clients.
    <Files ~ "^\.ht">
    Order allow,deny
    Deny from all
    </Files>
    # TypesConfig describes where the mime.types file (or equivalent) is
    # to be found.
    TypesConfig conf/mime.types
    # DefaultType is the default MIME type the server will use for a document
    # if it cannot otherwise determine one, such as from filename extensions.
    # If your server contains mostly text or HTML documents, "text/plain" is
    # a good value. If most of your content is binary, such as applications
    # or images, you may want to use "application/octet-stream" instead to
    # keep browsers from trying to display binary files as though they are
    # text.
    DefaultType text/plain
    # The mod_mime_magic module allows the server to use various hints from the
    # contents of the file itself to determine its type. The MIMEMagicFile
    # directive tells the module where the hint definitions are located.
    <IfModule mod_mime_magic.c>
    MIMEMagicFile conf/magic
    </IfModule>
    # HostnameLookups: Log the names of clients or just their IP addresses
    # e.g., www.apache.org (on) or 204.62.129.132 (off).
    # The default is off because it'd be overall better for the net if people
    # had to knowingly turn this feature on, since enabling it means that
    # each client request will result in AT LEAST one lookup request to the
    # nameserver.
    HostnameLookups Off
    # EnableMMAP: Control whether memory-mapping is used to deliver
    # files (assuming that the underlying OS supports it).
    # The default is on; turn this off if you serve from NFS-mounted
    # filesystems. On some systems, turning it off (regardless of
    # filesystem) can improve performance; for details, please see
    # http://httpd.apache.org/docs-2.0/mod/core.html#enablemmap
    # EnableMMAP off
    # EnableSendfile: Control whether the sendfile kernel support is
    # used to deliver files (assuming that the OS supports it).
    # The default is on; turn this off if you serve from NFS-mounted
    # filesystems. Please see
    # http://httpd.apache.org/docs-2.0/mod/core.html#enablesendfile
    EnableSendfile off
    # ErrorLog: The location of the error log file.
    # If you do not specify an ErrorLog directive within a <VirtualHost>
    # container, error messages relating to that virtual host will be
    # logged here. If you do define an error logfile for a <VirtualHost>
    # container, that host's errors will be logged there and not here.
    ErrorLog logs/error_log
    # LogLevel: Control the number of messages logged to the error_log.
    # Possible values include: debug, info, notice, warn, error, crit,
    # alert, emerg.
    LogLevel debug
    # The following directives define some format nicknames for use with
    # a CustomLog directive (see below).
    LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\"" combined
    LogFormat "%h %l %u %t \"%r\" %>s %b" common
    LogFormat "%{Referer}i -> %U" referer
    LogFormat "%{User-agent}i" agent
    # The location and format of the access logfile (Common Logfile Format).
    # If you do not define any access logfiles within a <VirtualHost>
    # container, they will be logged here. Contrariwise, if you do
    # define per-<VirtualHost> access logfiles, transactions will be
    # logged therein and not in this file.
    CustomLog logs/access_log common
    # If you would like to have agent and referer logfiles, uncomment the
    # following directives.
    #CustomLog logs/referer_log referer
    #CustomLog logs/agent_log agent
    # If you prefer a single logfile with access, agent, and referer information
    # (Combined Logfile Format) you can use the following directive.
    #CustomLog logs/access_log combined
    # ServerTokens
    # This directive configures what you return as the Server HTTP response
    # Header. The default is 'Full' which sends information about the OS-Type
    # and compiled in modules.
    # Set to one of: Full | OS | Minor | Minimal | Major | Prod
    # where Full conveys the most information, and Prod the least.
    ServerTokens Prod
    # Optionally add a line containing the server version and virtual host
    # name to server-generated pages (internal error documents, FTP directory
    # listings, mod_status and mod_info output etc., but not CGI generated
    # documents or custom error documents).
    # Set to "EMail" to also include a mailto: link to the ServerAdmin.
    # Set to one of: On | Off | EMail
    ServerSignature Off
    # Aliases: Add here as many aliases as you need (with no limit). The format is
    # Alias fakename realname
    # Note that if you include a trailing / on fakename then the server will
    # require it to be present in the URL. So "/icons" isn't aliased in this
    # example, only "/icons/". If the fakename is slash-terminated, then the
    # realname must also be slash terminated, and if the fakename omits the
    # trailing slash, the realname must also omit it.
    # We include the /icons/ alias for FancyIndexed directory listings. If you
    # do not use FancyIndexing, you may comment this out.
    Alias /icons/ "/opt/IBMIHS/icons/"
    <Directory "/opt/IBMIHS/icons">
    Options Indexes MultiViews
    AllowOverride None
    Order allow,deny
    Allow from all
    </Directory>
    # ScriptAlias: This controls which directories contain server scripts.
    # ScriptAliases are essentially the same as Aliases, except that
    # documents in the realname directory are treated as applications and
    # run by the server when requested rather than as documents sent to the client.
    # The same rules about trailing "/" apply to ScriptAlias directives as to
    # Alias.
    ScriptAlias /cgi-bin/ "/opt/IBMIHS/cgi-bin/"
    <IfModule mod_cgid.c>
    # Additional to mod_cgid.c settings, mod_cgid has Scriptsock <path>
    # for setting UNIX socket for communicating with cgid.
    #Scriptsock logs/cgisock
    </IfModule>
    # "/opt/IBMIHS/cgi-bin" should be changed to whatever your ScriptAliased
    # CGI directory exists, if you have that configured.
    <Directory "/opt/IBMIHS/cgi-bin">
    AllowOverride None
    Options None
    Order allow,deny
    Allow from all
    </Directory>
    # Redirect allows you to tell clients about documents which used to exist in
    # your server's namespace, but do not anymore. This allows you to tell the
    # clients where to look for the relocated document.
    # Example:
    # Redirect permanent /foo http://www.example.com/bar
    # Directives controlling the display of server-generated directory listings.
    # IndexOptions: Controls the appearance of server-generated directory
    # listings.
    IndexOptions FancyIndexing VersionSort
    # AddIcon* directives tell the server which icon to show for different
    # files or filename extensions. These are only displayed for
    # FancyIndexed directories.
    AddIconByEncoding (CMP,/icons/compressed.gif) x-compress x-gzip
    AddIconByType (TXT,/icons/text.gif) text/*
    AddIconByType (IMG,/icons/image2.gif) image/*
    AddIconByType (SND,/icons/sound2.gif) audio/*
    AddIconByType (VID,/icons/movie.gif) video/*
    AddIcon /icons/binary.gif .bin .exe
    AddIcon /icons/binhex.gif .hqx
    AddIcon /icons/tar.gif .tar
    AddIcon /icons/world2.gif .wrl .wrl.gz .vrml .vrm .iv
    AddIcon /icons/compressed.gif .Z .z .tgz .gz .zip
    AddIcon /icons/a.gif .ps .ai .eps
    AddIcon /icons/layout.gif .html .shtml .htm .pdf
    AddIcon /icons/text.gif .txt
    AddIcon /icons/c.gif .c
    AddIcon /icons/p.gif .pl .py
    AddIcon /icons/f.gif .for
    AddIcon /icons/dvi.gif .dvi
    AddIcon /icons/uuencoded.gif .uu
    AddIcon /icons/script.gif .conf .sh .shar .csh .ksh .tcl
    AddIcon /icons/tex.gif .tex
    AddIcon /icons/bomb.gif core
    AddIcon /icons/back.gif ..
    AddIcon /icons/hand.right.gif README
    AddIcon /icons/folder.gif ^^DIRECTORY^^
    AddIcon /icons/blank.gif ^^BLANKICON^^
    # DefaultIcon is which icon to show for files which do not have an icon
    # explicitly set.
    DefaultIcon /icons/unknown.gif
    # AddDescription allows you to place a short description after a file in
    # server-generated indexes. These are only displayed for FancyIndexed
    # directories.
    # Format: AddDescription "description" filename
    #AddDescription "GZIP compressed document" .gz
    #AddDescription "tar archive" .tar
    #AddDescription "GZIP compressed tar archive" .tgz
    # ReadmeName is the name of the README file the server will look for by
    # default, and append to directory listings.
    # HeaderName is the name of a file which should be prepended to
    # directory indexes.
    ReadmeName README.html
    HeaderName HEADER.html
    # IndexIgnore is a set of filenames which directory indexing should ignore
    # and not include in the listing. Shell-style wildcarding is permitted.
    IndexIgnore .??* *~ *# HEADER* README* RCS CVS *,v *,t
    # AddEncoding allows you to have certain browsers (Mosaic/X 2.1+) uncompress
    # information on the fly. Note: Not all browsers support this.
    # Despite the name similarity, the following Add* directives have nothing
    # to do with the FancyIndexing customization directives above.
    AddEncoding x-compress Z
    AddEncoding x-gzip gz tgz
    # AddType allows you to add to or override the MIME configuration
    # file mime.types for specific file types.
    AddType application/x-tar .tgz
    AddType image/x-icon .ico
    # AddHandler allows you to map certain file extensions to "handlers":
    # actions unrelated to filetype. These can be either built into the server
    # or added with the Action directive (see below)
    # To use CGI scripts outside of ScriptAliased directories:
    # (You will also need to add "ExecCGI" to the "Options" directive.)
    #AddHandler cgi-script .cgi
    # For files that include their own HTTP headers:
    #AddHandler send-as-is asis
    # For server-parsed imagemap files:
    #AddHandler imap-file map
    # For type maps (negotiated resources):
    # (This is enabled by default to allow the Apache "It Worked" page
    # to be distributed in multiple languages.)
    AddHandler type-map var
    # Filters allow you to process content before it is sent to the client.
    # To parse .shtml files for server-side includes (SSI):
    # (You will also need to add "Includes" to the "Options" directive.)
    #AddType text/html .shtml
    #AddOutputFilter INCLUDES .shtml
    # Action lets you define media types that will execute a script whenever
    # a matching file is called. This eliminates the need for repeated URL
    # pathnames for oft-used CGI file processors.
    # Format: Action media/type /cgi-script/location
    # Format: Action handler-name /cgi-script/location
    # Customizable error responses come in three flavors:
    # 1) plain text 2) local redirects 3) external redirects
    # Some examples:
    #ErrorDocument 500 "The server made a boo boo."
    #ErrorDocument 404 /missing.html
    #ErrorDocument 404 "/cgi-bin/missing_handler.pl"
    #ErrorDocument 402 http://www.example.com/subscription_info.html
    # Putting this all together, we can internationalize error responses.
    # We use Alias to redirect any /error/HTTP_<error>.html.var response to
    # our collection of by-error message multi-language collections. We use
    # includes to substitute the appropriate text.
    # You can modify the messages' appearance without changing any of the
    # default HTTP_<error>.html.var files by adding the line:
    # Alias /error/include/ "/your/include/path/"
    # which allows you to create your own set of files by starting with the
    # /opt/IBMIHS/error/include/ files and copying them to /your/include/path/,
    # even on a per-VirtualHost basis. The default include files will display
    # your Apache version number and your ServerAdmin email address regardless
    # of the setting of ServerSignature.
    # The internationalized error documents require mod_alias, mod_include
    # and mod_negotiation. To activate them, uncomment the following 30 lines.
    # Alias /error/ "/opt/IBMIHS/error/"
    # <Directory "/opt/IBMIHS/error">
    # AllowOverride None
    # Options IncludesNoExec
    # AddOutputFilter Includes html
    # AddHandler type-map var
    # Order allow,deny
    # Allow from all
    # LanguagePriority en de es fr it nl sv
    # ForceLanguagePriority Prefer Fallback
    # </Directory>
    # ErrorDocument 400 /error/HTTP_BAD_REQUEST.html.var
    # ErrorDocument 401 /error/HTTP_UNAUTHORIZED.html.var
    # ErrorDocument 403 /error/HTTP_FORBIDDEN.html.var
    # ErrorDocument 404 /error/HTTP_NOT_FOUND.html.var
    # ErrorDocument 405 /error/HTTP_METHOD_NOT_ALLOWED.html.var
    # ErrorDocument 408 /error/HTTP_REQUEST_TIME_OUT.html.var
    # ErrorDocument 410 /error/HTTP_GONE.html.var
    # ErrorDocument 411 /error/HTTP_LENGTH_REQUIRED.html.var
    # ErrorDocument 412 /error/HTTP_PRECONDITION_FAILED.html.var
    # ErrorDocument 413 /error/HTTP_REQUEST_ENTITY_TOO_LARGE.html.var
    # ErrorDocument 414 /error/HTTP_REQUEST_URI_TOO_LARGE.html.var
    # ErrorDocument 415 /error/HTTP_SERVICE_UNAVAILABLE.html.var
    # ErrorDocument 500 /error/HTTP_INTERNAL_SERVER_ERROR.html.var
    # ErrorDocument 501 /error/HTTP_NOT_IMPLEMENTED.html.var
    # ErrorDocument 502 /error/HTTP_BAD_GATEWAY.html.var
    # ErrorDocument 503 /error/HTTP_SERVICE_UNAVAILABLE.html.var
    # ErrorDocument 506 /error/HTTP_VARIANT_ALSO_VARIES.html.var
    # The following directives modify normal HTTP response behavior to
    # handle known problems with browser implementations.
    BrowserMatch "Mozilla/2" nokeepalive
    BrowserMatch "MSIE 4\.0b2;" nokeepalive downgrade-1.0 force-response-1.0
    BrowserMatch "RealPlayer 4\.0" force-response-1.0
    BrowserMatch "Java/1\.0" force-response-1.0
    BrowserMatch "JDK/1\.0" force-response-1.0
    # The following directive disables redirects on non-GET requests for
    # a directory that does not include the trailing slash. This fixes a
    # problem with Microsoft WebFolders which does not appropriately handle
    # redirects for folders with DAV methods.
    # Same deal with Apple's DAV filesystem and Gnome VFS support for DAV.
    BrowserMatch "Microsoft Data Access Internet Publishing Provider" redirect-carefully
    BrowserMatch "^WebDrive" redirect-carefully
    BrowserMatch "^WebDAVFS/1.[012]" redirect-carefully
    BrowserMatch "^gnome-vfs" redirect-carefully
    # Allow server status reports generated by mod_status,
    # with the URL of http://servername/server-status
    # Change the ".example.com" to match your domain to enable.
    #<Location /server-status>
    # SetHandler server-status
    # Order deny,allow
    # Deny from all
    # Allow from .example.com
    #</Location>
    # Allow remote server configuration reports, with the URL of
    # http://servername/server-info (requires that mod_info.c be loaded).
    # Change the ".example.com" to match your domain to enable.
    #<Location /server-info>
    # SetHandler server-info
    # Order deny,allow
    # Deny from all
    # Allow from .example.com
    #</Location>
    # Proxy Server directives. Uncomment the following lines to
    # enable the proxy server:
    #<IfModule mod_proxy.c>
    #Enable the forward proxy server. Note: Do not use the ProxyRequests directive if
    #all you require is reverse proxy.
    #ProxyRequests On
    #<Proxy *>
    # Order deny,allow
    # Deny from all
    # Allow from .example.com
    #</Proxy>
    # Enable/disable the handling of HTTP/1.1 "Via:" headers.
    # ("Full" adds the server version; "Block" removes all outgoing Via: headers)
    # Set to one of: Off | On | Full | Block
    #ProxyVia On
    #</IfModule>
    # End of proxy directives.
    ### Section 3: Virtual Hosts
    # VirtualHost: If you want to maintain multiple domains/hostnames on your
    # machine you can setup VirtualHost containers for them. Most configurations
    # use only name-based virtual hosts so the server doesn't need to worry about
    # IP addresses. This is indicated by the asterisks in the directives below.
    # Please see the documentation at
    # <URL:http://httpd.apache.org/docs-2.0/vhosts/>
    # for further details before you try to setup virtual hosts.
    # You may use the command line option '-S' to verify your virtual host
    # configuration.
    # Use name-based virtual hosting.
    #NameVirtualHost *
    NameVirtualHost 83.231.147.65:80
    <VirtualHost 83.231.147.65:80>
    ServerName eus0000168
    DocumentRoot "/www/a/global/nissan-europe"
    RewriteEngine on
    RewriteLogLevel 0
    RewriteOptions inherit
    #--RAM----
    LoadModule weblogic_module modules/mod_wl_20.so
    Debug ALL
    WLLogFile "/logs/apache2/wllog.log"
    StatPath true
    DebugConfigInfo On
    KeepAliveEnabled ON
    <IfModule mod_weblogic.c>
    WebLogicHost 83.231.147.129
    #WebLogicHost eus0000160
    #WebLogicCluster eus0000160.eu.verio.net:27110,eus0000160.eu.verio.net:27001
    WebLogicPort 27110
    </IfModule>
    DynamicServerList OFF
         <Location /AppConsole>
         SetHandler weblogic-handler
         </Location>
    <Location /console>
    SetHandler weblogic-handler
    </Location>
    <Location /HTTPClnt>
    SetHandler weblogic-handler
    </Location>
    <Location /iiop>
    SetHandler weblogic-handler
    </Location>
    #------RAM------
    Alias /data "/www/a/data"
    Alias /at "/www/a/at"
    Alias /ch "/www/a/ch"
    Alias /ch_fr "/www/a/ch/ch_FR"
    Alias /ch_de "/www/a/ch/ch_DE"
    Alias /de "/www/a/de"
    Alias /es "/www/a/es"
    Alias /fr "/www/a/fr"
    Alias /it "/www/a/it"
    Alias /nl "/www/a/nl"
    Alias /se "/www/a/se"
    Alias /tr "/www/a/tr"
    Alias /uk "/www/a/uk"
    Alias /cz "/www/a/cz"
    Alias /hu "/www/a/hu"
    Alias /sk "/www/a/sk"
    Alias /global "/www/a/global"
    Alias /dk "/www/a/dk"
    Alias /fi "/www/a/fi"
    Alias /no "/www/a/no"
    Alias /pl "/www/a/pl"
    Alias /pt "/www/a/pt"
    ErrorDocument 404 /error404.html
    ErrorDocument 500 /error.html
    </VirtualHost>
    Include conf/virtual-hosts/
    CoreDumpDirectory /logs/apache2
    LoadModule was_ap20_module /opt/IBM/WebSphere/Plugins/bin/mod_was_ap20_http.so
    WebSpherePluginConfig /opt/IBM/WebSphere/Plugins/config/webserver1/plugin-cfg.xml
    LoadModule weblogic_module modules/mod_wl_20.so
    Debug ALL
    WLLogFile "/logs/apache2/wllog.log"
    StatPath true
    DebugConfigInfo ON
    KeepAliveEnabled ON
    <IfModule mod_weblogic.c>
    WebLogicHost 83.231.147.129
    WebLogicPort 27110
    </IfModule>
    CoreDumpDirectory /logs/apache2
    D

  • WL 7 apache plugin

    I'm running Weblogic 7 sp2 server on a RedHat Linux 7.3 as the backend server and
    a Redhat 7.3 server with Apache 1.327 as the frontend.
    At first I had only one site to configure with the Bea Apache plugin. But there
    will be at least 3 sites more. I let the Bea server serv all the content for the
    sites because behind the Bea Server there is a Tridion Publication server that
    is not capable of splitting content. So all the content, including .jsp's, gifs,
    html's, will be published at one target. So I choose the Bea server to do that
    job.
    I've looked at the documentation of Bea but I can't find any solution to configure
    more WeblogicPorts for one WeblogicHost in the Apache Plugin.
    All the sites will be configured on different WeblogicPorts.
    Does anyone has any experience with this?
    Thanks in advanced.

              If the redirection is sent to another server, the client doesn't sent the cookies to the server. It could be dangerous.
              You should use encodeRedirectURL to pass sessionId and cookies to the destination server :
              res.sendRedirect(res.encodeRedirectURL("java.sun.com");
              Jean-Paul Guigui
              "Alex Rojkov" <[email protected]> wrote:
              >When using apache plugin with weblogic51 on solaris we run into problem when
              >trying to send redirect with the request which has Cookie added. Cookie
              >never makes it to the browser. Here is the sample code we used.
              >
              > public void doGet(HttpServletRequest req, HttpServletResponse res)
              > {
              > try{
              > req.getSession(true);
              > Cookie z = new Cookie("name", "value");
              > z.setMaxAge(0xFFFF);
              > res.addCookie(z);
              > res.sendRedirect("http://java.sun.com");
              > }
              > catch(Exception e) {e.printStackTrace(System.out);}
              > }
              >
              >
              >Thanks,
              >
              >Alex
              >
              >
              

  • Issue with sticky sessions

    My application has the following architecture:
    1.) a load balanced Flex frontend with sticky sessions which queries
    2.) a load balanced REST service also with sticky sessions
    The flex frontend queries the service using a Flex HTTPService object.  However, although sticky sessions are enabled on both the flex frontend and
    rest service, we are seeing queries go to different instances. For example
    user will request Flex App1 which will then call RestService1
    then user will request Flex App1 again which will call RestService2(instead of RestService1).
    Has anyone seen this issue before in a load balanced environment?  I need this to work because the REST service does not have a distributed cache, so subsequent requests must hit the same box to use the cache.
    thanks

    NW6 SP5 needs nw6nss5c in order for NSS to work properly; once applied
    then do
    nss /poolrebuild /purge
    on all pools. Make sure you have tested backups first, just in case.
    Also Load Monitor - Server Parameters - NCP. Set Level 2 OpLocks Enabled
    = Off, and Client File Caching Enabled = Off.
    What lan driver, date and version, on the server?
    Andrew C Taubman
    Novell Support Forums Volunteer SysOp
    http://support.novell.com/forums
    (Sorry, support is not provided via e-mail)
    Opinions expressed above are not
    necessarily those of Novell Inc.

  • Authentication in clustered web application without sticky session

    I have built JSP/Servlet/Struts application in the past on a cluster of app servers. Each app server has its own JVM running the Servlel Container. All of the HTTP requests come into a hardware load balancer, which directs the requests to one of the app servers in the cluster.
    I have wanted to use the Java HttpSession management without any kind of distributed session provided by the app server. We have used "sticky" sessions. The application writes a cookie to the client on the first request. The load balancer looks for that cookie on subsequent requests and directs the request to the server that originally wrote the cookie. This ensures that all requests within the same session are handled by the same application server. This also means that if I do request.getSession().setAttribute("authenticated",true) on one request, when I do request.getSession().getAttribute(authenticated) on subsequent requests in the same session, I can be sure the value will not be null. This allows me to create a filter that checks for that session attribute on each request, and if it is false or null, redirect the request to some sort of login page. Otherwise I can be sure the user has logged in.
    I want to build a stateless/non-session based application that can still handle authentication. What I mean by that is that I don't want the load balancer to have to send requests for the same session all to the same server. I would like the load balancer to send each request where ever it wants. That means the simple authentication example I explained in the last paragraph would not work. The user could login on server A, but then on a subsequent request during the same "session", the user's request could be handled by server B. In that case, the session attribute would be null, and the app would think that the user has not logged in.
    My application can require that users have cookies enabled, so therefore I can assume the user is accepting cookies (I would have something to check that and redirect the user to an error page saying "turn cookies on" if cookies weren't on). I think one thing that I could do is use encrpytion with a key that is shared between all the servers in the cluster. For example, user logins in on server A, server A writes a cookie with the contents "username,1109272102009". The first part being the username that the user successfully authenticated as and the second part being a timestamp for when the cookie was created. The contents of the actual cookie would be encrypted and I would send the ciphertext as the value of the cookie. When server B gets the cookie, it can decrypt the ciphertext (using the same key as was used to encrypt the data on server A), and check that the username is valid and that the timestamp does not exceed some timeout. The timestamp in the cookie would then have to be updated for the next request.
    So my question is (thanks for sticking with me and reading this really long post), has anyone done anything like this before? Is what I have described totally ridiculous or insecure? Are there any books or articles that describe a pattern similar to this that has been know to work well?

    I have worked on a web site that did exactly that.
    The cookie contained a little bit more information - there was a small amount of user data that were needed on heavily accessed pages.
    You'll have a problem if your web application uses attributes. We solved this by keeping most stuff in hidden inputs (backed up by hidden input cryptographic checksums in places where forgery was a concern.) HttpSession attributes have some problems and gotchas.
    A few possible fine tunings:
    Add a random number to the cookie. Should make known plaintext attacks harder.
    Add some extra stuff to the cookie, so that any random hex string that happens to decode to "xZoiyqw,15" isn't accepted. It's easy to try a million cookies until you get "<something>,<integer>" but getting "<something>,<integer>,HelloHowAreYou" is a lot harder.
    Be paranoid in checking the format of the cookie. If you add a random number, check that it is all digits etc. Belt and suspenders: also check that the time stamp isn't in the future (allow e.g. 15 seconds future time, in case different servers' clocks are a bit off.)
    Don't update the cookie at every hit, only if the time stamp is older than a couple of minutes. Saves encryption CPU power.
    After encrypting, prepend a short version number to the cookie. E.g. if the hex cookie is ABCDEF, make it 1ABCDEF. If you later e.g. change the encryption algorithm, change version to 2 and you can easily skip any obviously non-decipherable cookies. A second version number within the cookie might or might not be useful.
    Even though you can make random load balancing, consider not doing that. E.g. a server might pull the user's name from the database into memory cache. You get less database traffic and smaller caches if the user still goes to the same server. If a server goes down, only then switch him elsewhere. Downside though: if one server is "half alive" (doesn't respond to requests but alive enough so the load balancer doesn't notice the malfunction), all users bound to that server see a 100% failure.
    Benchmark cookie decryption time when selecting the crypto algorithm. How many hits per second you can get and how many you need.
    Guard your crypto keys like the crown jewels. Change them periodically and whenever someone in your company (especially IT department) gets the pink slip.

  • JMX with apache plugin and weblogic

    Hy every body
    I use weblogic 9.1, throw apache plugin
    I try to get mbean with JMX,
    i have this error on the log of the server when I try to acces to a server by passing apache url into jmxConnector:
    java.lang.AssertionError: Assertion violated
         at weblogic.utils.Debug.assertion(Debug.java:57)
         at weblogic.iiop.MuxableSocketIIOP.getMessageLength(MuxableSocketIIOP.java:315)
         at weblogic.socket.AbstractMuxableSocket.isMessageComplete(AbstractMuxableSocket.java:336)
         at weblogic.socket.MuxableSocketDiscriminator.dispatch(MuxableSocketDiscriminator.java:166)
         at weblogic.socket.NTSocketMuxer.processSockets(NTSocketMuxer.java:105)
         at weblogic.socket.SocketReaderRequest.run(SocketReaderRequest.java:29)
         at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:42)
         at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:145)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:117)
    the log:
    ================New Request: [GIOP] =================
    Tue May 31 14:25:36 2011 <35921306844736112> INFO: SSL is not configured
    Tue May 31 14:25:36 2011 <35921306844736112> Using Uri /
    Tue May 31 14:25:36 2011 <35921306844736112> After trimming path: '/'
    Tue May 31 14:25:36 2011 <35921306844736112> The final request string is '/'
    Tue May 31 14:25:36 2011 <35921306844736112> SEARCHING id=[192.168.2.83:7001] from current ID=[192.168.2.83:7001]
    Tue May 31 14:25:36 2011 <35921306844736112> The two ids matched
    Tue May 31 14:25:36 2011 <35921306844736112> @@@FOUND...id=[192.168.2.83:7001], server_name=[AdminServer], server_port=[80]
    Tue May 31 14:25:36 2011 <35921306844736112> attempt #0 out of a max of 5
    Tue May 31 14:25:36 2011 <35921306844736112> Trying a pooled connection for '192.168.2.83/7001/7001'
    Tue May 31 14:25:36 2011 <35921306844736112> getPooledConn: No more connections in the pool for Host[192.168.2.83] Port[7001] SecurePort[7001]
    Tue May 31 14:25:36 2011 <35921306844736112> general list: trying connect to '192.168.2.83'/7001/7001 at line 2724 for '/'
    Tue May 31 14:25:36 2011 <35921306844736112> INFO: New NON-SSL URL
    Tue May 31 14:25:36 2011 <35921306844736112> Connect returns -1, and error no set to 10035, msg 'Unknown error'
    Tue May 31 14:25:36 2011 <35921306844736112> EINPROGRESS in connect() - selecting
    Tue May 31 14:25:36 2011 <35921306844736112> Local Port of the socket is 2039
    Tue May 31 14:25:36 2011 <35921306844736112> Remote Host 192.168.2.83 Remote Port 7001
    Tue May 31 14:25:36 2011 <35921306844736112> general list: created a new connection to '192.168.2.83'/7001 for '/', Local port:2039
    Tue May 31 14:25:36 2011 <35921306844736112> URL::sendHeaders(): meth='GIOP' file='/' protocol='HTTP/0.9'
    Tue May 31 14:25:36 2011 <35921306844736112> Hdrs to WLS:[Connection]=[Keep-Alive]
    Tue May 31 14:25:36 2011 <35921306844736112> Hdrs to WLS:[WL-Proxy-SSL]=[false]
    Tue May 31 14:25:36 2011 <35921306844736112> Hdrs to WLS:[WL-Proxy-Client-IP]=[192.168.0.143]
    Tue May 31 14:25:36 2011 <35921306844736112> Hdrs to WLS:[Proxy-Client-IP]=[192.168.0.143]
    Tue May 31 14:25:36 2011 <35921306844736112> Hdrs to WLS:[X-Forwarded-For]=[192.168.0.143]
    Tue May 31 14:25:36 2011 <35921306844736112> Hdrs to WLS:[X-WebLogic-KeepAliveSecs]=[24]
    Tue May 31 14:25:36 2011 <35921306844736112> Hdrs to WLS:[X-WebLogic-Force-JVMID]=[unset]
    Tue May 31 14:25:36 2011 <35921306844736112> readStatus: Local port of the socket 2039, connected to Remote Host/Port 192.168.2.83/7001
    Tue May 31 14:25:36 2011 <35921306844736112> readStatus: Response contains no data - isRecycled: 0
    Tue May 31 14:25:36 2011 <35921306844736112> *******Exception type [READ_ERROR_FROM_SERVER] (Unexpected EOF reading HTTP status - failover request based on Idempotent flag) raised at line 841 of ../nsapi/URL.cpp
    Tue May 31 14:25:36 2011 <35921306844736112> Marking 192.168.2.83:7001 as bad
    Tue May 31 14:25:36 2011 <35921306844736112> got exception in sendRequest phase: READ_ERROR_FROM_SERVER [os error=0, line 841 of ../nsapi/URL.cpp]: Unexpected EOF reading HTTP status - failover request based on Idempotent flag at line 3160
    Tue May 31 14:25:36 2011 <35921306844736112> Failing over after sendRequest() exception: READ_ERROR_FROM_SERVER as Idempotent is set to ON
    Tue May 31 14:25:36 2011 <35921306844736112> attempt #1 out of a max of 5
    Tue May 31 14:25:36 2011 <35921306844736112> general list: trying connect to '192.168.2.83'/7001/7001 at line 2724 for '/'
    Tue May 31 14:25:36 2011 <35921306844736112> INFO: New NON-SSL URL
    Tue May 31 14:25:36 2011 <35921306844736112> Connect returns -1, and error no set to 10035, msg 'Unknown error'
    Tue May 31 14:25:36 2011 <35921306844736112> EINPROGRESS in connect() - selecting
    Tue May 31 14:25:36 2011 <35921306844736112> Local Port of the socket is 2040
    Tue May 31 14:25:36 2011 <35921306844736112> Remote Host 192.168.2.83 Remote Port 7001
    Tue May 31 14:25:36 2011 <35921306844736112> general list: created a new connection to '192.168.2.83'/7001 for '/', Local port:2040
    Tue May 31 14:25:36 2011 <35921306844736112> URL::sendHeaders(): meth='GIOP' file='/' protocol='HTTP/0.9'
    Tue May 31 14:25:36 2011 <35921306844736112> Hdrs to WLS:[Connection]=[Keep-Alive]
    Tue May 31 14:25:36 2011 <35921306844736112> Hdrs to WLS:[WL-Proxy-SSL]=[false]
    Tue May 31 14:25:36 2011 <35921306844736112> Hdrs to WLS:[WL-Proxy-Client-IP]=[192.168.0.143]
    Tue May 31 14:25:36 2011 <35921306844736112> Hdrs to WLS:[Proxy-Client-IP]=[192.168.0.143]
    Tue May 31 14:25:36 2011 <35921306844736112> Hdrs to WLS:[X-Forwarded-For]=[192.168.0.143]
    Tue May 31 14:25:36 2011 <35921306844736112> Hdrs to WLS:[X-WebLogic-KeepAliveSecs]=[24]
    Tue May 31 14:25:36 2011 <35921306844736112> Hdrs to WLS:[X-WebLogic-Force-JVMID]=[unset]
    Tue May 31 14:25:36 2011 <35921306844736112> readStatus: Local port of the socket 2040, connected to Remote Host/Port 192.168.2.83/7001
    Tue May 31 14:25:36 2011 <35921306844736112> readStatus: Response contains no data - isRecycled: 0
    Tue May 31 14:25:36 2011 <35921306844736112> *******Exception type [READ_ERROR_FROM_SERVER] (Unexpected EOF reading HTTP status - failover request based on Idempotent flag) raised at line 841 of ../nsapi/URL.cpp
    Tue May 31 14:25:36 2011 <35921306844736112> Marking 192.168.2.83:7001 as bad
    Tue May 31 14:25:36 2011 <35921306844736112> got exception in sendRequest phase: READ_ERROR_FROM_SERVER [os error=0, line 841 of ../nsapi/URL.cpp]: Unexpected EOF reading HTTP status - failover request based on Idempotent flag at line 3160
    Tue May 31 14:25:36 2011 <35921306844736112> Failing over after sendRequest() exception: READ_ERROR_FROM_SERVER as Idempotent is set to ON
    Tue May 31 14:25:36 2011 <35921306844736112> attempt #2 out of a max of 5
    Tue May 31 14:25:36 2011 <35921306844736112> general list: trying connect to '192.168.2.83'/7001/7001 at line 2724 for '/'
    Tue May 31 14:25:36 2011 <35921306844736112> INFO: New NON-SSL URL
    Tue May 31 14:25:36 2011 <35921306844736112> Connect returns -1, and error no set to 10035, msg 'Unknown error'
    Tue May 31 14:25:36 2011 <35921306844736112> EINPROGRESS in connect() - selecting
    Tue May 31 14:25:36 2011 <35921306844736112> Local Port of the socket is 2041
    Tue May 31 14:25:36 2011 <35921306844736112> Remote Host 192.168.2.83 Remote Port 7001
    Tue May 31 14:25:36 2011 <35921306844736112> general list: created a new connection to '192.168.2.83'/7001 for '/', Local port:2041
    Tue May 31 14:25:36 2011 <35921306844736112> URL::sendHeaders(): meth='GIOP' file='/' protocol='HTTP/0.9'
    Tue May 31 14:25:36 2011 <35921306844736112> Hdrs to WLS:[Connection]=[Keep-Alive]
    Tue May 31 14:25:36 2011 <35921306844736112> Hdrs to WLS:[WL-Proxy-SSL]=[false]
    Tue May 31 14:25:36 2011 <35921306844736112> Hdrs to WLS:[WL-Proxy-Client-IP]=[192.168.0.143]
    Tue May 31 14:25:36 2011 <35921306844736112> Hdrs to WLS:[Proxy-Client-IP]=[192.168.0.143]
    Tue May 31 14:25:36 2011 <35921306844736112> Hdrs to WLS:[X-Forwarded-For]=[192.168.0.143]
    Tue May 31 14:25:36 2011 <35921306844736112> Hdrs to WLS:[X-WebLogic-KeepAliveSecs]=[24]
    Tue May 31 14:25:36 2011 <35921306844736112> Hdrs to WLS:[X-WebLogic-Force-JVMID]=[unset]
    Tue May 31 14:25:36 2011 <35921306844736112> readStatus: Local port of the socket 2041, connected to Remote Host/Port 192.168.2.83/7001
    Tue May 31 14:25:36 2011 <35921306844736112> readStatus: Response contains no data - isRecycled: 0
    Tue May 31 14:25:36 2011 <35921306844736112> *******Exception type [READ_ERROR_FROM_SERVER] (Unexpected EOF reading HTTP status - failover request based on Idempotent flag) raised at line 841 of ../nsapi/URL.cpp
    Tue May 31 14:25:36 2011 <35921306844736112> Marking 192.168.2.83:7001 as bad
    Tue May 31 14:25:36 2011 <35921306844736112> got exception in sendRequest phase: READ_ERROR_FROM_SERVER [os error=0, line 841 of ../nsapi/URL.cpp]: Unexpected EOF reading HTTP status - failover request based on Idempotent flag at line 3160
    Tue May 31 14:25:36 2011 <35921306844736112> Failing over after sendRequest() exception: READ_ERROR_FROM_SERVER as Idempotent is set to ON
    Tue May 31 14:25:36 2011 <35921306844736112> attempt #3 out of a max of 5
    Tue May 31 14:25:36 2011 <35921306844736112> general list: trying connect to '192.168.2.83'/7001/7001 at line 2724 for '/'
    Tue May 31 14:25:36 2011 <35921306844736112> INFO: New NON-SSL URL
    Tue May 31 14:25:36 2011 <35921306844736112> Connect returns -1, and error no set to 10035, msg 'Unknown error'
    Tue May 31 14:25:36 2011 <35921306844736112> EINPROGRESS in connect() - selecting
    Tue May 31 14:25:36 2011 <35921306844736112> Local Port of the socket is 2042
    Tue May 31 14:25:36 2011 <35921306844736112> Remote Host 192.168.2.83 Remote Port 7001
    Tue May 31 14:25:36 2011 <35921306844736112> general list: created a new connection to '192.168.2.83'/7001 for '/', Local port:2042
    Tue May 31 14:25:36 2011 <35921306844736112> URL::sendHeaders(): meth='GIOP' file='/' protocol='HTTP/0.9'
    Tue May 31 14:25:36 2011 <35921306844736112> Hdrs to WLS:[Connection]=[Keep-Alive]
    Tue May 31 14:25:36 2011 <35921306844736112> Hdrs to WLS:[WL-Proxy-SSL]=[false]
    Tue May 31 14:25:36 2011 <35921306844736112> Hdrs to WLS:[WL-Proxy-Client-IP]=[192.168.0.143]
    Tue May 31 14:25:36 2011 <35921306844736112> Hdrs to WLS:[Proxy-Client-IP]=[192.168.0.143]
    Tue May 31 14:25:36 2011 <35921306844736112> Hdrs to WLS:[X-Forwarded-For]=[192.168.0.143]
    Tue May 31 14:25:36 2011 <35921306844736112> Hdrs to WLS:[X-WebLogic-KeepAliveSecs]=[24]
    Tue May 31 14:25:36 2011 <35921306844736112> Hdrs to WLS:[X-WebLogic-Force-JVMID]=[unset]
    Tue May 31 14:25:36 2011 <35921306844736112> readStatus: Local port of the socket 2042, connected to Remote Host/Port 192.168.2.83/7001
    Tue May 31 14:25:36 2011 <35921306844736112> readStatus: Response contains no data - isRecycled: 0
    Tue May 31 14:25:36 2011 <35921306844736112> *******Exception type [READ_ERROR_FROM_SERVER] (Unexpected EOF reading HTTP status - failover request based on Idempotent flag) raised at line 841 of ../nsapi/URL.cpp
    Tue May 31 14:25:36 2011 <35921306844736112> Marking 192.168.2.83:7001 as bad
    Tue May 31 14:25:36 2011 <35921306844736112> got exception in sendRequest phase: READ_ERROR_FROM_SERVER [os error=0, line 841 of ../nsapi/URL.cpp]: Unexpected EOF reading HTTP status - failover request based on Idempotent flag at line 3160
    Tue May 31 14:25:36 2011 <35921306844736112> Failing over after sendRequest() exception: READ_ERROR_FROM_SERVER as Idempotent is set to ON
    Tue May 31 14:25:36 2011 <35921306844736112> attempt #4 out of a max of 5
    Tue May 31 14:25:36 2011 <35921306844736112> general list: trying connect to '192.168.2.83'/7001/7001 at line 2724 for '/'
    Tue May 31 14:25:36 2011 <35921306844736112> INFO: New NON-SSL URL
    Tue May 31 14:25:36 2011 <35921306844736112> Connect returns -1, and error no set to 10035, msg 'Unknown error'
    Tue May 31 14:25:36 2011 <35921306844736112> EINPROGRESS in connect() - selecting
    Tue May 31 14:25:36 2011 <35921306844736112> Local Port of the socket is 2043
    Tue May 31 14:25:36 2011 <35921306844736112> Remote Host 192.168.2.83 Remote Port 7001
    Tue May 31 14:25:36 2011 <35921306844736112> general list: created a new connection to '192.168.2.83'/7001 for '/', Local port:2043
    Tue May 31 14:25:36 2011 <35921306844736112> URL::sendHeaders(): meth='GIOP' file='/' protocol='HTTP/0.9'
    Tue May 31 14:25:36 2011 <35921306844736112> Hdrs to WLS:[Connection]=[Keep-Alive]
    Tue May 31 14:25:36 2011 <35921306844736112> Hdrs to WLS:[WL-Proxy-SSL]=[false]
    Tue May 31 14:25:36 2011 <35921306844736112> Hdrs to WLS:[WL-Proxy-Client-IP]=[192.168.0.143]
    Tue May 31 14:25:36 2011 <35921306844736112> Hdrs to WLS:[Proxy-Client-IP]=[192.168.0.143]
    Tue May 31 14:25:36 2011 <35921306844736112> Hdrs to WLS:[X-Forwarded-For]=[192.168.0.143]
    Tue May 31 14:25:36 2011 <35921306844736112> Hdrs to WLS:[X-WebLogic-KeepAliveSecs]=[24]
    Tue May 31 14:25:36 2011 <35921306844736112> Hdrs to WLS:[X-WebLogic-Force-JVMID]=[unset]
    Tue May 31 14:25:36 2011 <35921306844736112> readStatus: Local port of the socket 2043, connected to Remote Host/Port 192.168.2.83/7001
    Tue May 31 14:25:36 2011 <35921306844736112> readStatus: Response contains no data - isRecycled: 0
    Tue May 31 14:25:36 2011 <35921306844736112> *******Exception type [READ_ERROR_FROM_SERVER] (Unexpected EOF reading HTTP status - failover request based on Idempotent flag) raised at line 841 of ../nsapi/URL.cpp
    Tue May 31 14:25:36 2011 <35921306844736112> Marking 192.168.2.83:7001 as bad
    Tue May 31 14:25:36 2011 <35921306844736112> got exception in sendRequest phase: READ_ERROR_FROM_SERVER [os error=0, line 841 of ../nsapi/URL.cpp]: Unexpected EOF reading HTTP status - failover request based on Idempotent flag at line 3160
    Tue May 31 14:25:36 2011 <35921306844736112> Failing over after sendRequest() exception: READ_ERROR_FROM_SERVER as Idempotent is set to ON
    Tue May 31 14:25:36 2011 <35921306844736112> attempt #5 out of a max of 5
    Tue May 31 14:25:36 2011 <35921306844736112> general list: trying connect to '192.168.2.83'/7001/7001 at line 2724 for '/'
    Tue May 31 14:25:36 2011 <35921306844736112> INFO: New NON-SSL URL
    Tue May 31 14:25:36 2011 <35921306844736112> Connect returns -1, and error no set to 10035, msg 'Unknown error'
    Tue May 31 14:25:36 2011 <35921306844736112> EINPROGRESS in connect() - selecting
    Tue May 31 14:25:36 2011 <35921306844736112> Local Port of the socket is 2044
    Tue May 31 14:25:36 2011 <35921306844736112> Remote Host 192.168.2.83 Remote Port 7001
    Tue May 31 14:25:36 2011 <35921306844736112> general list: created a new connection to '192.168.2.83'/7001 for '/', Local port:2044
    Tue May 31 14:25:36 2011 <35921306844736112> URL::sendHeaders(): meth='GIOP' file='/' protocol='HTTP/0.9'
    Tue May 31 14:25:36 2011 <35921306844736112> Hdrs to WLS:[Connection]=[Keep-Alive]
    Tue May 31 14:25:36 2011 <35921306844736112> Hdrs to WLS:[WL-Proxy-SSL]=[false]
    Tue May 31 14:25:36 2011 <35921306844736112> Hdrs to WLS:[WL-Proxy-Client-IP]=[192.168.0.143]
    Tue May 31 14:25:36 2011 <35921306844736112> Hdrs to WLS:[Proxy-Client-IP]=[192.168.0.143]
    Tue May 31 14:25:36 2011 <35921306844736112> Hdrs to WLS:[X-Forwarded-For]=[192.168.0.143]
    Tue May 31 14:25:36 2011 <35921306844736112> Hdrs to WLS:[X-WebLogic-KeepAliveSecs]=[24]
    Tue May 31 14:25:36 2011 <35921306844736112> Hdrs to WLS:[X-WebLogic-Force-JVMID]=[unset]
    Tue May 31 14:25:36 2011 <35921306844736112> readStatus: Local port of the socket 2044, connected to Remote Host/Port 192.168.2.83/7001
    Tue May 31 14:25:36 2011 <35921306844736112> readStatus: Response contains no data - isRecycled: 0
    Tue May 31 14:25:36 2011 <35921306844736112> *******Exception type [READ_ERROR_FROM_SERVER] (Unexpected EOF reading HTTP status - failover request based on Idempotent flag) raised at line 841 of ../nsapi/URL.cpp
    Tue May 31 14:25:36 2011 <35921306844736112> Marking 192.168.2.83:7001 as bad
    Tue May 31 14:25:36 2011 <35921306844736112> got exception in sendRequest phase: READ_ERROR_FROM_SERVER [os error=0, line 841 of ../nsapi/URL.cpp]: Unexpected EOF reading HTTP status - failover request based on Idempotent flag at line 3160
    Tue May 31 14:25:36 2011 <35921306844736112> Failing over after sendRequest() exception: READ_ERROR_FROM_SERVER as Idempotent is set to ON
    Tue May 31 14:25:36 2011 <35921306844736112> request [] did NOT process successfully..................
    the httpd.conf:
    <IfModule mod_weblogic.c>
    WebLogicHost 192.168.2.83
    WebLogicPort 7001
    #WebLogicCluster t3://192.168.2.83:7003, t3://192.168.2.83: 7005, t3://192.168.2.83:7013
    Idempotent on
    Debug HFC,HTW,HFW
    WLLogFile c:/wlproxy.log
    WLTempDir c:/TEMP
    DebugConfigInfo On
    KeepAliveEnabled ON
    KeepAliveSecs 14
    MatchExpression *
    </IfModule>
    <Location /HTTPClnt>
    SetHandler weblogic-handler
    </Location>
    I don't use ssl.
    I can access to the jsp of the server with the url of apach , but i cannot use jmx throught apache. I can use jmx with the server if I don't use apache, but i need apache for the next step of the project.
    please, help me !

    I think the plug-in is intended for serves static pages, and another part of the document like MIME types.
    I assume you are using the http protocol in your client to establish a jmx connection. Try enabling HTTP tunneling in weblogic server.
    Can you post the code used to establish connetion?

  • Weblogic Apache Plugin - Load Balancing

    Hi,
    I have two Apache servers each with the WLS Apache Plugin installed. These sit in front of two WL servers each having two managed servers.
    Each plugin is setup with the list of servers as follows:
    <IfModule mod_weblogic.c>
              WebLogicCluster Server_1:7030,Server_1:7040,Server_2:7010Server_2:7020
              Debug           OFF
              WLLogFile logs/cws_proxy.log
              WLTempDir "logs"
              DebugConfigInfo OFF
              WLProxySSL On
              KeepAliveEnabled ON
              KeepAliveSecs 15
              MatchExpression *.xhtml
              MatchExpression *.jsp
         </IfModule>
    Look OK so far?
    Anyway, looking at the WL access.log I can see that server 1 is only receiving requests from one Apache, and the same goes for the other access.log. So... it's not really load balancing is it?
    Can anyone offer any advice or comments on my plugin configuration or why it is not load balancing properly?
    Much Appreciated,

    I came across this link which says ‘WebLogic Server does not always load balance an object’s method calls.” And has few more details about the load balancing strategy of weblogic.
    http://download.oracle.com/docs/cd/E11035_01/wls100/cluster/load_balancing.html#wp1026599
    http://download.oracle.com/docs/cd/E11035_01/wls100/cluster/load_balancing.html
    This might help.

Maybe you are looking for