WebLogic Apache Plug-in

I've just read about the WebLogic Apache plug-in that's new in 5.1 :-)
          Am I right to assume that this plug-in only works for Apache running on
          Solaris? :-(
          I'm running Apache (Stronghold actually) on Linux and I need to use this to
          proxy JSP request to my Weblogic Servers running on Solaris - any thoughts?
          Ken
          

          We will be making a port of the plug-in in the future. You should contact
          your account manager who can supply the full details.
          Thanks,
          Michael Girdley
          WLS Product Manager
          Ken <kenw{noSpam]@lostwax.com> wrote in message
          news:8cej50$dsu$[email protected]..
          > I've just read about the WebLogic Apache plug-in that's new in 5.1 :-)
          >
          > Am I right to assume that this plug-in only works for Apache running on
          > Solaris? :-(
          >
          > I'm running Apache (Stronghold actually) on Linux and I need to use this
          to
          > proxy JSP request to my Weblogic Servers running on Solaris - any
          thoughts?
          >
          > Ken
          >
          >
          

Similar Messages

  • Error loading weblogic apache plug-in

    HPUX11i
    Apache 2.0.55
    WebLogic 8.13
    I am following the instructions on how to configure the Weblogic Apache plug-in:
    http://e-docs.bea.com/wls/docs81/plugins/apache.html#119517
    When I attempt to verify the syntax of the http.conf or attempt to start apache, I get the following error:
    /usr/lib/dld.sl: Can't shl_load() a library containing Thread Local Storage:
    /usr/lib/libcl.2
    /usr/lib/dld.sl: Exec format error
    Syntax error on line 247 of /usr/local/apache2/conf/httpd.conf:
    Cannot load /usr/local/apache2/modules/mod_wl_20.so into server: Exec format error
    Any ideas on how to fix this?
    Thanks.

              We will be making a port of the plug-in in the future. You should contact
              your account manager who can supply the full details.
              Thanks,
              Michael Girdley
              WLS Product Manager
              Ken <kenw{noSpam]@lostwax.com> wrote in message
              news:8cej50$dsu$[email protected]..
              > I've just read about the WebLogic Apache plug-in that's new in 5.1 :-)
              >
              > Am I right to assume that this plug-in only works for Apache running on
              > Solaris? :-(
              >
              > I'm running Apache (Stronghold actually) on Linux and I need to use this
              to
              > proxy JSP request to my Weblogic Servers running on Solaris - any
              thoughts?
              >
              > Ken
              >
              >
              

  • Configuring WebLogic Apache plug-in

    I think the answer to this question is no but I'm going to ask anyway...
    Is it possible to configure Apache to proxy requests to managed weblogic servers
    on one physical machine only? we have a cluster containing 4 managed weblogics
    spanning 2 physical machines and would prefer to have one machine be like our
    primary server and the other machine as our secondary server.
    Replication groups do not do the trick as it is a feature of WLS that tells it
    how to handle the backup of session state information to another server in the
    cluster (aside from the default algorithm WLS uses)

    The solution is for BEA to provide the plug-in. Probably a few minutes of a work for BEA developer. Weblogic 9.0 has it.
    Edited by muralive at 09/17/2007 10:08 PM

  • Apache plug-in prob : when trying to access '/weblogic/' URL , "404 : file not found" error is shown

    On : Apache 2.0 , Weblogic 7.0, Win 2000
    I installed the Apache plug-in for as described in WL docs, but when I try to
    access a URL /weblogic/ ( supposed to be configured automatically ) on apache,
    I get '404 : file not found' error.
    As per the docs, I did following config in Apache:
    1. Copied the 'mod_wl_20.so' file found in WLHOME\server\bin directory to the
    APACHE_HOME\modules directory
    2. Added to httpd.conf :
    LoadModule weblogic_module modules/mod_wl_20.so
    3. Apache httpd.conf syntax correct : checked by running ' APACHE_HOME\bin\Apache
    -t '
    4. Restarted WL & Apache.
    Now, the weblogic documentation says,
    "Test the Apache plug-in by opening a browser and setting the URL to the Apache
    Server + "/weblogic/", which should bring up the default WebLogic Server HTML
    page, welcome file, or default servlet, as defined for the default Web Application
    on WebLogic Server. For example:
    http://myApacheserver.com/weblogic/".
    For my server, 'http://localhost/weblogic/' - I get a "404 : file not found" error.
    What other configuration is needed ? Do I have to specify '/weblogic/' name anywhere
    else in Apache configuration file ?
    Any pointers will be appreciated.
    Thanks,
    S

    Forgot to mention , I've also added following configuration in httpd.conf :
    LoadModule weblogic_module modules\mod_wl_20.so
    <IfModule mod_weblogic.c>
    WebLogicHost localhost
    WebLogicPort 7501
    </IfModule>
    <Location /weblogic>
    SetHandler weblogic-handler
    PathTrim /weblogic
    </Location>
    "S" <[email protected]> wrote:
    >
    On : Apache 2.0 , Weblogic 7.0, Win 2000
    I installed the Apache plug-in for as described in WL docs, but when
    I try to
    access a URL /weblogic/ ( supposed to be configured automatically ) on
    apache,
    I get '404 : file not found' error.
    As per the docs, I did following config in Apache:
    1. Copied the 'mod_wl_20.so' file found in WLHOME\server\bin directory
    to the
    APACHE_HOME\modules directory
    2. Added to httpd.conf :
    LoadModule weblogic_module modules/mod_wl_20.so
    3. Apache httpd.conf syntax correct : checked by running ' APACHE_HOME\bin\Apache
    -t '
    4. Restarted WL & Apache.
    Now, the weblogic documentation says,
    "Test the Apache plug-in by opening a browser and setting the URL to
    the Apache
    Server + "/weblogic/", which should bring up the default WebLogic Server
    HTML
    page, welcome file, or default servlet, as defined for the default Web
    Application
    on WebLogic Server. For example:
    http://myApacheserver.com/weblogic/".
    For my server, 'http://localhost/weblogic/' - I get a "404 : file not
    found" error.
    What other configuration is needed ? Do I have to specify '/weblogic/'
    name anywhere
    else in Apache configuration file ?
    Any pointers will be appreciated.
    Thanks,
    S

  • Error NO_RESOURCES when using Apache Plug-in for Weblogic

    Hi all,
    LoadModule weblogic_module modules/mod_wl.so
       OS.....: OEL 6.3 64 bits
       Weblogic Server: 12.1.0.2 (192.168.0.123)
       Apache: Apache/2.2.15 (Unix) (192.168.0.149)
       I am trying to configure the Apache Plug-in to forward the requests to the Weblogic Server. I already did all the configuration, but when i try to access a page, i get the following error in Apache's error.log:
    [Wed Dec 03 18:25:42 2014] [error] [client 192.168.0.149] <649114176419322> weblogic: *******Exception type [NO_RESOURCES] (apr_socket_connect call failed with error=13, host=192.168.0.123, port=7006 ) raised at line 1682 of URL.cpp
    [Wed Dec 03 18:25:42 2014] [error] [client 192.168.0.149] weblogic: Trying GET /benefits/ at backend host '192.168.0.123/7006; got exception 'NO_RESOURCES: [os error=13,  line 1682 of URL.cpp]: apr_socket_connect call failed with error=13, host=192.168.0.123, port=7006 '
    [Wed Dec 03 18:25:44 2014] [error] [client 192.168.0.149] <649114176419322> weblogic: request [/benefits/] did NOT process successfully..................
       My httpd.conf if configured as follows:
    Listen 8080
    LoadModule weblogic_module modules/mod_wl.so
    <IfModule mod_weblogic.c>
       WeblogicHost 192.168.0.123
       WeblogicPort 7006
    </IfModule>
    <Location /benefits>
       SetHandler weblogic-handler
    </Location>
    When i try to access the app deployed in Weblogic with the following address: "http://192.168.0.149:8080/benefits/" , i get the error mentioned above and the following error is displayed in my browser:
       Failure of Web Server bridge:
       No backend server available for connection: timed out after 10 seconds or idempotent set to OFF or method not idempotent.
    What am i doing wrong?
    Thanks in advance.

    Hi all,
    I had some progress... i disabled the firewall (SELinux) on the Apache server. Before, i had just disabled the firewall from the Weblogic Server. Now, when i access the apache server, it redirects (sometimes, actually) the request to my Weblogic Cluster. Let's say that 50% of the time it works and the other 50% i get the error informed previously.
       I am using the apache user and the ulimit of this user is:
          [apache@vm-apache conf]$ ulimit -a
    core file size          (blocks, -c) 0
    data seg size           (kbytes, -d) unlimited
    scheduling priority             (-e) 0
    file size               (blocks, -f) unlimited
    pending signals                 (-i) 15915
    max locked memory       (kbytes, -l) 64
    max memory size         (kbytes, -m) unlimited
    open files                      (-n) 1024
    pipe size            (512 bytes, -p) 8
    POSIX message queues     (bytes, -q) 819200
    real-time priority              (-r) 0
    stack size              (kbytes, -s) 8192
    cpu time               (seconds, -t) unlimited
    max user processes              (-u) 1024
    virtual memory          (kbytes, -v) unlimited
    file locks                      (-x) unlimited
       From the Apache server (192.168.0.149), when i execute the "culr" command, i get the following message:
          [apache@vm-apache conf]$ curl http://192.168.0.123:7006/benefits
          <html><head><title>302 Moved Temporarily</title></head>
          <body bgcolor="#FFFFFF">
          <p>This document you requested has moved temporarily.</p>
          <p>It's now at <a href="http://192.168.0.123:7006/benefits/">http://192.168.0.123:7006/benefits/</a>.</p>
          </body></html>
       The message above represents a OK situation or a problematic one?
       Below you can see the last few lines of my Error Log and Access Log:
       ### error log ###
    [Thu Dec 18 20:54:16 2014] [error] [client 192.168.0.123] <340514189468553> weblogic: parseJVMID: could not resolve hostname '-1062731653'. Returning NULL from parseJVMID 
    [Thu Dec 18 20:54:16 2014] [error] [client 192.168.0.123] <340314189468563> weblogic: parseJVMID: could not resolve hostname '-1062731653'. Returning NULL from parseJVMID
    [Thu Dec 18 20:54:17 2014] [error] [client 192.168.0.123] File does not exist: /var/www/html/favicon.ico
    [Thu Dec 18 20:54:17 2014] [error] [client 192.168.0.123] File does not exist: /var/www/html/favicon.ico
    [Thu Dec 18 20:54:21 2014] [error] [client 192.168.0.123] <340114189468603> weblogic: parseJVMID: could not resolve hostname '-1062731653'. Returning NULL from parseJVMID, referer: http://192.168.0.149:8080/benefits/
    [Thu Dec 18 20:54:44 2014] [error] [client 192.168.0.149] <339814189468792> weblogic: parseJVMID: could not resolve hostname '-1062731653'. Returning NULL from parseJVMID
    [Thu Dec 18 20:54:44 2014] [error] [client 192.168.0.149] <339814189468792> weblogic: initJVMID: parseClusterServerList failure
    [Thu Dec 18 20:54:45 2014] [error] [client 192.168.0.123] <339914189468844> weblogic: parseJVMID: could not resolve hostname '-1062731653'. Returning NULL from parseJVMID, referer: http://192.168.0.149:8080/benefits/servlet
    [Thu Dec 18 20:54:45 2014] [error] [client 192.168.0.123] <339914189468844> weblogic: initJVMID: parseClusterServerList failure, referer: http://192.168.0.149:8080/benefits/servlet
    [Thu Dec 18 20:54:56 2014] [error] [client 192.168.0.149] <339814189468792> weblogic: request [/benefits/welcome.html] did NOT process successfully..................
    [Thu Dec 18 20:54:57 2014] [error] [client 192.168.0.123] <339914189468844> weblogic: request [/benefits/welcome.html] did NOT process successfully.................., referer:http://192.168.0.149:8080/benefits/servlet
       ### access log ###
    192.168.0.123 - - [18/Dec/2014:20:54:15 -0300] "GET /benefits HTTP/1.1" 302 267 "-" "Mozilla/5.0 (X11; Linux x86_64; rv:10.0.5) Gecko/20120605 Firefox/10.0.5" 
    192.168.0.123 - - [18/Dec/2014:20:54:16 -0300] "GET /benefits/ HTTP/1.1" 200 5832 "-" "Mozilla/5.0 (X11; Linux x86_64; rv:10.0.5) Gecko/20120605 Firefox/10.0.5"
    192.168.0.123 - - [18/Dec/2014:20:54:17 -0300] "GET /favicon.ico HTTP/1.1" 404 290 "-" "Mozilla/5.0 (X11; Linux x86_64; rv:10.0.5) Gecko/20120605 Firefox/10.0.5"
    192.168.0.123 - - [18/Dec/2014:20:54:17 -0300] "GET /favicon.ico HTTP/1.1" 404 290 "-" "Mozilla/5.0 (X11; Linux x86_64; rv:10.0.5) Gecko/20120605 Firefox/10.0.5"
    192.168.0.123 - - [18/Dec/2014:20:54:20 -0300] "POST /benefits/servlet HTTP/1.1" 200 492 "http://192.168.0.149:8080/benefits/" "Mozilla/5.0 (X11; Linux x86_64; rv:10.0.5) Gecko/20120605 Firefox/10.0.5"
    192.168.0.149 - - [18/Dec/2014:20:54:39 -0300] "GET /benefits/welcome.html HTTP/1.1" 503 250 "-" "Mozilla/5.0 (X11; Linux x86_64; rv:10.0.5) Gecko/20120605 Firefox/10.0.5"
    192.168.0.123 - - [18/Dec/2014:20:54:44 -0300] "GET /benefits/welcome.html HTTP/1.1" 503 250 "http://192.168.0.149:8080/benefits/servlet" "Mozilla/5.0 (X11; Linux x86_64; rv:10.0.5) Gecko/20120605 Firefox/10.0.5"
    Is there any additional or recommended configuration for this solution to work properly?
    Thanks again for the attention and pacience.

  • Weblogic 8.1 Apache Plug-In

    Where can I find the plug-in for WLS 8.1/Apache 2.0/Windows 2003?

    Hi Vishwas,
    Thank you for the reply. I forgot to mention that Apache and WebLogic are on Solaris 9 platform.
    Accesing a webapp hosted on WebLogic through Apache->plug-in->WebLogic return 500 internal server error, but other webapps hosted on the same WebLogic domain works properly. Looking at the Response Hdrs from WebLogic shows that WLS returns transfer-encoding=chunked. The other webapps which work properly has content-length set and transfer-encoding is not chunked.
    So, the question is does Apache Plug-in for weblogic 8.1 SP5 read the chunked data properly?
    Thanks,
    Janani

  • Apache Plug-in wont re-direct.

    I'm trying to use the apache plug-in to redirect traffic to my non-clusterd weblogic server but I can not get it to work. I'm trying to route everything to Weblogic. It loads the weblogic plugin but I never get re-routed. Any help is appreciated.
    Thanks,
    Tom.
    The pertinent information below:
    OS: Solaris 10
    Apache: 2.0.63
    Weblogic 9.2 MP3
    weblogic module copied to:
    /usr/apache2/libexec/mod_wl_20.so
    httpd.conf entries:
    # load the weblogic module
    LoadModule weblogic_module libexec/mod_wl_20.so
    #weblogic settings
    <IfModule mod_weblogic.c>
    WebLogicHost myserver.lc.ca.gov
    WebLogicPort 9001
    MatchExpression /*
    Debug ON
    WLLogFile /tmp/global_proxy.log
    WLTempDir /tmp
    DebugConfigInfo ON
    </IfModule>
    Error.log output:
    [Tue Nov 18 11:05:19 2008] [info] mod_unique_id: using ip addr 165.107.72.112
    [Tue Nov 18 11:05:20 2008] [info] mod_unique_id: using ip addr 165.107.72.112
    [Tue Nov 18 11:05:21 2008] [notice] BEA plugin build date/time: Dec 5 2007 15:1
    2:41. Change Number: 1014998
    [Tue Nov 18 11:05:21 2008] [info] mod_weblogic: init_mod: mpm doesn't support th
    reads.
    [Tue Nov 18 11:05:21 2008] [notice] Digest: generating secret for digest authent
    ication ...
    [Tue Nov 18 11:05:21 2008] [notice] Digest: done
    [Tue Nov 18 11:05:21 2008] [info] mod_weblogic: init_child: isThreaded = -1
    [Tue Nov 18 11:05:21 2008] [info] mod_weblogic: Testing Debug=ON LogFile=/var/ap
    ache2/logs/global_proxy.log TempDir=/tmp
    [Tue Nov 18 11:05:21 2008] [info] mod_weblogic: created global log context in ch
    ild
    [Tue Nov 18 11:05:21 2008] [info] mod_weblogic: init_child: isThreaded = -1
    [Tue Nov 18 11:05:21 2008] [info] mod_weblogic: Testing Debug=ON LogFile=/var/ap
    ache2/logs/global_proxy.log TempDir=/tmp
    [Tue Nov 18 11:05:21 2008] [info] mod_weblogic: created global log context in ch
    ild
    [Tue Nov 18 11:05:21 2008] [info] mod_weblogic: init_child: isThreaded = -1
    [Tue Nov 18 11:05:21 2008] [info] mod_weblogic: Testing Debug=ON LogFile=/var/ap
    ache2/logs/global_proxy.log TempDir=/tmp
    [Tue Nov 18 11:05:21 2008] [info] mod_weblogic: created global log context in ch
    ild
    [Tue Nov 18 11:05:21 2008] [notice] Apache/2.0.63 (Unix) DAV/2 configured -- res
    uming normal operations
    [Tue Nov 18 11:05:21 2008] [info] Server built: Feb 10 2008 04:45:11
    [Tue Nov 18 11:05:21 2008] [info] mod_weblogic: init_child: isThreaded = -1
    [Tue Nov 18 11:05:21 2008] [info] mod_weblogic: Testing Debug=ON LogFile=/var/ap
    ache2/logs/global_proxy.log TempDir=/tmp
    [Tue Nov 18 11:05:21 2008] [info] mod_weblogic: created global log context in ch
    ild
    [Tue Nov 18 11:05:21 2008] [info] mod_weblogic: init_child: isThreaded = -1

    OK, I chmod 777 to the mod_wl_20.so.
    I also changed the httpd.config to:
    &lt;IfModule mod_weblogic.c&gt;
    WebLogicHost lwpvcma1.lc.ca.gov
    WebLogicPort 9001
    WLLocalIP "my local ip - removed for security"
    Debug ON
    WLLogFile /var/apache2/logs/global_proxy.log
    WLTempDir /tmp
    DebugConfigInfo ON
    &lt;/IfModule&gt;
    &lt;Location /ShoppingCart&gt;
    SetHandler weblogic-handler
    PathTrim /ShoppingCart
    &lt;/Location&gt;
    But I still get the same result. The apache server and weblogic server are running on the same machine - not sure if that makes a difference.
    Here is what apache Server-info displays:
    Module Name: mod_weblogic.c
    Content handlers: yes
    Configuration Phase Participation: Create Directory Config, Merge Directory Configs, Create Server Config, Merge Server Configs
    Request Phase Participation: Fixups
    Module Directives:
    CookieName - Defines CookieName
    WLCookieName - Defines WLCookieName
    WebLogicCluster - Defines a list of WebLogic Clusters
    WebLogicHost - Defines a WebLogic Host
    WebLogicPort - Defines a WebLogic Port
    PathTrim - Defines PathTrim
    PathPrepend - Defines PathPrepend
    HungServerRecoverSecs - This parameter is used for recovery from hung servers min:default=10:300
    WLIOTimeoutSecs - Defines WLIOTimeoutSecs
    WLSocketTimeoutSecs - Defines WLSocketTimeoutSecs
    ConnectTimeoutSecs - Defines ConnectTimeoutSecs
    ConnectRetrySecs - Defines ConnectRetrySecs
    MaxPostSize - Defines MaxPostSize
    StatPath - Defines StatPath
    ErrorPage - Defines ErrorPage
    DebugConfigInfo - Whether to log the config info or not
    Idempotent - Whether to failover or not
    DynamicServerList - Whether to use dynamic server list or not
    MaxSkips - Defines MaxSkips
    MaxSkipTime - Defines MaxSkipTime
    SecureProxy - Whether SSL is required
    EnforceBasicConstraints - Whether basic constraints checking is enforced
    RequireSSLHostMatch - Whether SSL host match is required
    SSLHostMatchOID - Which OID to use for SSL host match
    TrustedCAFile - Where SSL trusted CA file is located
    FileCaching - Whether to failover or not
    MatchExpression - Regular expression for matching weblogic requests (e.g., "*.jsp")
    Debug - Log the debugging info or not
    DefaultFileName - Set the default filename
    DisableCookie2Server - Igore session info in the cookie
    KeepAliveEnabled - Turn on/off keep alive enable feature
    KeepAliveSecs - how long we keep the socket open
    WLDNSRefreshInterval - how frequent we do DNS lookup
    QueryFromRequest - should use r-&gt;args as query string
    WLForwardUriUnparsed - should use r-&gt;unparsed_uri instead of r-&gt;uri
    WLLocalIP - specify the local IP to bind
    WLTempDir - specify the location for wlproxy directory
    WLLogFile - specify the log file to be used
    WLProxySSL - whether to send WL-Proxy-SSL header or not
    WLCrossOverProxyEnabled - whether to allow cross over proxy
    WLExcludePathOrMimeType - requests to be excluded for proxying (e.g., "*.php")
    Current Configuration:
    WebLogicHost myhost.lc.ca.gov
    WebLogicPort 9001
    WLLocalIP "My Local IP Address"
    Debug ON
    WLLogFile /var/apache2/logs/global_proxy.log
    WLTempDir /tmp
    DebugConfigInfo ON
    *&lt;Location /ShoppingCart&gt;*
    PathTrim /ShoppingCart
    *&lt;/Location&gt;*

  • Apache Plug-In: PathPrepend doesn't work?

    Hello All,
    I've run into a problem at a customer site with the WLS 5.1 Apache Plug-In
    with Apache 1.3.12 on Solaris 6: the PathTrim parameter does not work.
    Could somebody look at my httpd.conf file and tell me what I'm doing wrong:
    <Location /weblogic>
    SetHandler weblogic-handler
    </Location>
    WebLogicHost ism-app
    WebLogicPort 7010
    PathTrim weblogic
    DebugConfigInfo ON
    That's as basic as it gets, but it doesn't work! The url
    /weblogic/index.html should get sent to wls as /index.html; instead, it's
    sent verbatim.
    I've tried the plug-in from service pack versions 3, 4, 6, and 8, and tried
    the PathPrepend parameter inside the Location tag as well as outside. I
    can't imagine that this does not work for any plug-in in any service pack;
    if this is a bug in all these service packs, we really need to take a
    serious look at QA.
    Vijay Garla
    Consultant, BEA Systems
    [httpd.conf]

    Hi,
    the "apex.widget.initPageItem" will not help you in your case, it's used to register callbacks for $s, $v, show, hide, ... if you have a more advanced item type. You can have a look at the "Star Rating" plug-in which implements several of these callbacks.
    For adding cascading LOV support, please have a look at our own select list implementation in /i/javascript/uncompressed/apex_widget_4_0.js
    Search for
    apex.widget.selectList = function(pSelector, pOptions) {to get a blue print implementation for all the steps you have to add to your widget to add cascading LOV support.
    If you need further help, please let me know.
    Regards
    Patrick
    My Blog: http://www.inside-oracle-apex.com
    APEX 4.0 Plug-Ins: http://apex.oracle.com/plugins
    Twitter: http://www.twitter.com/patrickwolf

  • WLS 8.1 Apache Plug-in is changing HTTP status code 999 to 500

    I'm seeing the weblogic server 8.1 sp4 apache plug-in change the HTTP status code of 999 (set by the application) to 500 Internal Server Error. I'm seeing this with Apache 2.0.48 on aix and with Apache 2.0.58 on windows. I've tried the plug-in from 8.1 SP2, SP4 and SP6 with all yielding the same result. I've tried the SSL plug-in too - same result. I'm told by the maker of this application that they are not seeing this issue with the plug-in for SunOne/NES. What does BEA say about the Apache plug-in changing the http status code? Why is it doing this? Why doesn't the SunOne/NES plug-in do it? Can you provide a plug-in that does not do this?

    Try setting
    Debug ALL
    inside your IfModule. All proxy activity will be written to /tmp/wlproxy.log (on
    unixes). If no info appears in the log, Apache is not invoking the plug-in properly.
    HTH
    "Lukas" <[email protected]> wrote:
    >
    I am trying to set up Apache 2.0.49 proxy plug-in for my WLS 8.1 cluster
    (2 managed
    servers). I followed instructions at http://edocs.bea.com/wls/docs81/plugins/apache.html.
    My test web application runs on
    192.168.10.142:5001/public/testwebapp
    and
    192.168.10.142:6001/public/testwebapp
    I have tested my cluster using another instance on WLS and HttpClusterServlet
    and it works fine.
    I have added following section to my httpd.conf
    LoadModule weblogic_module modules/mod_wl_20.so
    <IfModule mod_weblogic.c>
    WebLogicCluster 192.168.10.142:6001,192.168.10.142:5001
    </IfModule>
    <Location /public/testwebapp>
    SetHandler weblogic-handler
    PathTrim /public/testwebapp
    ErrorPage http://myerrorpage1.mydomain.com
    </Location>
    I restarted my wls cluster and apache as well and when I specify http://192.168.10.142/public/testwebapp
    (apache web server) I receive Error 404--Not Found (even thou I have
    tested my
    http://192.168.10.142:5001/public/testwebapp and http://192.168.10.142:6001/public/testwebapp
    - they work correctly).
    There is nothing in apache’s error_log file.
    There is a record in access_log file reading:
    192.168.10.126 - - [08/Jun/2004:16:23:32 -0700] "GET /public/testwebapp
    HTTP/1.1"
    404 1214
    which gives me an impression that “proxy” – forwarding does not work.
    Where should I look for some errors?
    Thanks,
    Lukas

  • Hardware Load Balancers and Cluster WebLogic Proxy Plug-in setting

    Documentation states that we need to enable the Cluster WebLogic Proxy Plug-in setting when there is a proxy plugin or HttpClusterServlet configured.
    We used to have Weblogic Proxy plugin and the setting is still there, also the proxy was replaced by the hardware loadbalancer. Everything works normally and no one complained, but I would assume that WebLogic Proxy Plug-in setting should not be applicable any longer.
    Is it possibly harmful to have that setting there? Does it mean that the loadbalancer emulates WebLogic Proxy Plug-in and also need this set?
    Thank you

    The Weblogic Proxy Plug-in Enabled flag only affects the behavior of a WL proxy module (such as if you were using Apache to proxy to WL via the mod_wl.so module). The value controls what IP address is returned when you call request.getRemoteAddr() from your application. If not enabled, you will get the IP address of the web server that proxied the request. If enabled, you will get the remote client IP address (instead of the proxy IP address) facilitated by the WL-Proxy-Client-IP header. If you are no longer using a plug-in module, the setting will have no affect. Hope this helps...

  • Apache plug-in won't load balance requests evenly on cluster

    I can't seem to get the Apache plug-in to actually do round-robin load balancing
    of HTTP
    requests. It does random-robin, as I like to call it, since the plug-in will usually
    hit all the
    servers in the cluster but in a random fashion.
    I've got three managed servers:
    192.168.1.5:8001 (WL6 on Linux) 192.168.1.2:8001 (WL6 on Linux) 192.168.1.7:8001
    (WL6 on Linux)
    Admin server on 192.168.1.7:7000 (WL6 on W2k)
    My Apache server is 1.3.9 (RedHat SSL) on 192.168.1.52.
    The log file for each servers has something like this:
    ####<Apr 19, 2001 1:18:54 AM MDT> <Info> <Cluster> <neptune> <cluster1server1>
    <main> <system> <> <000102> <Joined cluster cluster1 at address 225.0.0.5 on port
    8001>
    ####<Apr 19, 2001 1:19:31 AM MDT> <Info> <Cluster> <neptune> <cluster1server1>
    <ExecuteThread: '9' for queue: 'default'> <> <> <000127> <Adding
    3773576126129840579S:192.168.1.2:[8001,8001,7002,7002,8001,7002,-1]:192.168.1.52
    to the cluster> ####<Apr 19, 2001 1:19:31 AM MDT> <Info> <Cluster> <neptune>
    <cluster1server1> <ExecuteThread: '11' for queue: 'default'> <> <> <000127> <Adding
    -6393447100509727955S:192.168.1.5:[8001,8001,7002,7002,8001,7002,-1]:192.168.1.52
    to the cluster>
    So I believe I have correctly created a cluster, although I did not bother to
    assign
    replication groups for HTTP session replication (yet).
    The Apache debug output indicates it knows about all three servers and I can see
    it
    doing the "random-robin" load balancing. Here is the output:
    Thu Apr 19 00:20:53 2001 Initializing lastIndex=2 for a list of length=3 Thu Apr
    19
    00:20:53 2001 Init Srvr# [1] = [192.168.1.2:8001] load=1077584792 isGood=1077590272
    numSk ip=134940256 Thu Apr 19 00:20:53 2001 Init Srvr# [2] = [192.168.1.5:8001]
    load=1077584792 isGood=1077590272 numSk ip=134940256 Thu Apr 19 00:20:53 2001
    Init Srvr# [3] = [192.168.1.7:8001] load=1077584792 isGood=1077590272 numSk
    ip=134940256 Thu Apr 19 00:20:53 2001 INFO: SSL is not configured Thu Apr 19
    00:20:53 2001 Now trying whatever is on the list; ci->canUseSrvrList = 1 Thu Apr
    19
    00:20:53 2001 INFO: New NON-SSL URL Thu Apr 19 00:20:53 2001 general list: trying
    connect to '192.168.1.7'/8001 Thu Apr 19 00:20:53 2001 Connected to 192.168.1.7:8001
    Thu Apr 19 00:20:53 2001 INFO: sysSend 320 Thu Apr 19 00:20:53 2001 INFO:
    Reader::fill(): first=0 last=0 toRead=4096 Thu Apr 19 00:21:06 2001 parsed all
    headers
    OK Thu Apr 19 00:21:06 2001 Initializing lastIndex=1 for a list of length=3 Thu
    Apr 19
    00:21:06 2001 ###Response### : Srvr# [1] = [192.168.1.5:8001] load=1077584792
    isGood=1077 546628 numSkip=1077546628 Thu Apr 19 00:21:06 2001 ###Response###
    : Srvr# [2] = [192.168.1.2:8001] load=1077584792 isGood=1077 546628
    numSkip=1077546628 Thu Apr 19 00:21:06 2001 ###Response### : Srvr# [3] =
    [192.168.1.7:8001] load=1077584792 isGood=1077 546628 numSkip=1077546628 Thu Apr
    19 00:21:06 2001 INFO: Reader::fill(): first=0 last=0 toRead=4096
    Basically, the lastIndex=XXX appears to be random. It may do round-robin for 4
    or 5
    connections but then always it resorts to randomly directing new connections.
    This is what the configuration looks like using the plug-in's
    /weblogic?__WebLogicBridgeConfig URL:
    Weblogic Apache Bridge Configuration parameters:
    WebLogic Cluster List:
    1.Host: '192.168.1.2' Port: 8001 Primary
    General Server List:
    1.Host: '192.168.1.2' Port: 8001
    2.Host: '192.168.1.5' Port: 8001
    3.Host: '192.168.1.7' Port: 8001
    DefaultFileName: ''
    PathTrim: '/weblogic'
    PathPrepend: '' ConnectTimeoutSecs:
    '10' ConnectRetrySecs: '2'
    HungServerRecoverSecs: '300'
    MaxPostSize: '0'
    StatPath: false
    CookieName: JSESSIONID
    Idempotent:
    ON FileCaching:
    ON ErrorPage: ''
    DisableCookie2Server: OFF
    Can someone please help to shed some light on this? I would be really grateful,
    thanks!
    Jeff

    Right - it means that the only configuration which can do perfect round-robin is a
    single plugin (non-Apache, or single-process Apache) - all others essentially do random
    (sort of, but it can skew test results during first N requests).
    Robert Patrick <[email protected]> wrote:
    Dimitri,
    The way Apache works is that is spawns a bunch of child processes and the parent process
    that listens on the port delegates the processing of each request to one of the child
    processes. This means that the load-balancing dome by the plugin before the session ID is
    assigned does not do perfect round-robining because there are multiple copies of the plugin
    loaded in the multiple child processes. This situation is similar to the one you would get
    by running multiple proxy servers on different machines with the NES/iPlanet and IIS
    plugins.
    As I pointed out in my response to Jeff, attempting to address this problem with IPC
    machanisms would only solve the single machine problem and most people deploy multiple
    proxy servers to avoid a single point of failure...
    Hope this helps,
    Robert
    Dimitri Rakitine wrote:
    Hrm. This is strange - I thought that all the information nesessary for a
    'sticky' load-balancing (primary/secondary) is contained in the cookie/session info,
    so, the particular plug-in implementation should not make any difference. For
    load-balancing - statistically, given large enough sampling base, Apache plug-in
    should perform just a well as NS one (unless apache is somehow misconfigured and
    calls fork() for each new request).
    Jeff Calog <[email protected]> wrote:
    Robert,
    Thanks for the sanity reply, you are definitely right. I used Netscape 3.0 on
    Win2k and it did perfect round-robin load balancing to my servers.
    <raving>
    BEA - ARE YOU LISTENING? STOP TELLING PEOPLE YOUR APACHE PLUG-IN IS A VIABLE
    LOAD BALANCING SOLUTION! It's worthless for load balancing!
    </raving>
    In some tests, as many as 90% of my connections/requests would be sent to a single
    server. There should be something in the release notes like "By the way, the
    Apache plug-in is only advertised as doing round-robin load balancing, in reality
    it doesn't work worth a darn".
    I'm surprised they don't used shared memory or some other technique (pipes, sockets,
    signals, writing to /tmp, anything) for interprocess communication to fix that.
    Jeff
    Robert Patrick <[email protected]> wrote:
    Yes, the problem lies in the fact that Apache uses multiple processes
    instead of
    multiple threads to process requests. Therefore, you end up with multiple
    processes all
    with the WebLogic plugin loaded into them (and they cannot see one another)...
    Hopefully, Apache 2.0 when it comes out will allow the plugin to do a
    better job...
    Jeff Calog wrote:
    I can't seem to get the Apache plug-in to actually do round-robin loadbalancing
    of HTTP
    requests. It does random-robin, as I like to call it, since the plug-inwill usually
    hit all the
    servers in the cluster but in a random fashion.
    I've got three managed servers:
    192.168.1.5:8001 (WL6 on Linux) 192.168.1.2:8001 (WL6 on Linux) 192.168.1.7:8001
    (WL6 on Linux)
    Admin server on 192.168.1.7:7000 (WL6 on W2k)
    My Apache server is 1.3.9 (RedHat SSL) on 192.168.1.52.
    The log file for each servers has something like this:
    ####<Apr 19, 2001 1:18:54 AM MDT> <Info> <Cluster> <neptune> <cluster1server1>
    <main> <system> <> <000102> <Joined cluster cluster1 at address 225.0.0.5on port
    8001>
    ####<Apr 19, 2001 1:19:31 AM MDT> <Info> <Cluster> <neptune> <cluster1server1>
    <ExecuteThread: '9' for queue: 'default'> <> <> <000127> <Adding
    3773576126129840579S:192.168.1.2:[8001,8001,7002,7002,8001,7002,-1]:192.168.1.52
    to the cluster> ####<Apr 19, 2001 1:19:31 AM MDT> <Info> <Cluster><neptune>
    <cluster1server1> <ExecuteThread: '11' for queue: 'default'> <> <><000127> <Adding
    -6393447100509727955S:192.168.1.5:[8001,8001,7002,7002,8001,7002,-1]:192.168.1.52
    to the cluster>
    So I believe I have correctly created a cluster, although I did notbother to
    assign
    replication groups for HTTP session replication (yet).
    The Apache debug output indicates it knows about all three serversand I can see
    it
    doing the "random-robin" load balancing. Here is the output:
    Thu Apr 19 00:20:53 2001 Initializing lastIndex=2 for a list of length=3Thu Apr
    19
    00:20:53 2001 Init Srvr# [1] = [192.168.1.2:8001] load=1077584792 isGood=1077590272
    numSk ip=134940256 Thu Apr 19 00:20:53 2001 Init Srvr# [2] = [192.168.1.5:8001]
    load=1077584792 isGood=1077590272 numSk ip=134940256 Thu Apr 19 00:20:532001
    Init Srvr# [3] = [192.168.1.7:8001] load=1077584792 isGood=1077590272numSk
    ip=134940256 Thu Apr 19 00:20:53 2001 INFO: SSL is not configured ThuApr 19
    00:20:53 2001 Now trying whatever is on the list; ci->canUseSrvrList= 1 Thu Apr
    19
    00:20:53 2001 INFO: New NON-SSL URL Thu Apr 19 00:20:53 2001 generallist: trying
    connect to '192.168.1.7'/8001 Thu Apr 19 00:20:53 2001 Connected to192.168.1.7:8001
    Thu Apr 19 00:20:53 2001 INFO: sysSend 320 Thu Apr 19 00:20:53 2001INFO:
    Reader::fill(): first=0 last=0 toRead=4096 Thu Apr 19 00:21:06 2001parsed all
    headers
    OK Thu Apr 19 00:21:06 2001 Initializing lastIndex=1 for a list oflength=3 Thu
    Apr 19
    00:21:06 2001 ###Response### : Srvr# [1] = [192.168.1.5:8001] load=1077584792
    isGood=1077 546628 numSkip=1077546628 Thu Apr 19 00:21:06 2001 ###Response###
    : Srvr# [2] = [192.168.1.2:8001] load=1077584792 isGood=1077 546628
    numSkip=1077546628 Thu Apr 19 00:21:06 2001 ###Response### : Srvr#[3] =
    [192.168.1.7:8001] load=1077584792 isGood=1077 546628 numSkip=1077546628Thu Apr
    19 00:21:06 2001 INFO: Reader::fill(): first=0 last=0 toRead=4096
    Basically, the lastIndex=XXX appears to be random. It may do round-robinfor 4
    or 5
    connections but then always it resorts to randomly directing new connections.
    This is what the configuration looks like using the plug-in's
    /weblogic?__WebLogicBridgeConfig URL:
    Weblogic Apache Bridge Configuration parameters:
    WebLogic Cluster List:
    1.Host: '192.168.1.2' Port: 8001 Primary
    General Server List:
    1.Host: '192.168.1.2' Port: 8001
    2.Host: '192.168.1.5' Port: 8001
    3.Host: '192.168.1.7' Port: 8001
    DefaultFileName: ''
    PathTrim: '/weblogic'
    PathPrepend: '' ConnectTimeoutSecs:
    '10' ConnectRetrySecs: '2'
    HungServerRecoverSecs: '300'
    MaxPostSize: '0'
    StatPath: false
    CookieName: JSESSIONID
    Idempotent:
    ON FileCaching:
    ON ErrorPage: ''
    DisableCookie2Server: OFF
    Can someone please help to shed some light on this? I would be reallygrateful,
    thanks!
    Jeff
    Dimitri--
    Dimitri

  • Question about the Apache plug-in and WL server

    We have a bunch of Weblogic app-servers, and I want to set up Apache servers to
    front-end them. Here is what I'd like to do:
    (1) Load balancer forwards requests to one of Apache servers
    (2) Apache serves the static content (html,gif,css etc.)
    (3) Apache servers forward the request to one of the alive Weblogic servers, with
    requests for the same Weblogic session should preferably stay with the same Weblogic
    server.
    The catch is that we are not using Weblogic clustering - we have our own application-specific
    light-weight clustering (virtually no replication of dynamic state). All I want
    is that the Apache plug-ins keep forwarding the packets to the same Weblogic server
    for a session (unless the server dies), and that thsi property hold even if multiple
    client requests (for the same session) are rotated across multiple Apache servers.
    The first is really important, the second just nice-to-have (I can setup load-balancer
    with sticky sessions if needed).
    The Apache plug-in documentation seems to suggest that we must use Weblogic clustering
    for us to be able to specify multiple Weblogic servers in the plug-in config file,
    but is that really required?
    Second, does the session cookie uniquely identify the Weblogic server or does
    the Apache plug-in keep the mapping between the cookie and the server? Also, does
    this answer depend on whether we use Weblogic clustering or not?
    The answer depends on the protocol between the Apache plug-in and the Weblogic
    server. Is it documented? Available under NDA?
    Your help will be really appreciated!!
    thanks
    -amit

    is that the Apache plug-ins keep forwarding the packets to the same Weblogic
    server
    for a session (unless the server dies), If the session id is found in the cookie, request or postdata (in that order),
    the plugin will preserve the sticky session.
    and that thsi property hold even
    if multiple
    client requests (for the same session) are rotated across multiple Apache
    servers.The rules apply to all apache instances as the single instance.
    BTW, the preferred server from the session has to be in the serverList(you defined
    in the httpd.conf). You are not using clusters in the backend hence the server
    list will not be updated
    dynamically. The plugin will not know the changes in the backend without modifying
    the httpd.conf and restarted.
    The first is really important, the second just nice-to-have (I can setup
    load-balancer
    with sticky sessions if needed).
    The Apache plug-in documentation seems to suggest that we must use Weblogic
    clustering
    for us to be able to specify multiple Weblogic servers in the plug-in
    config file,
    but is that really required?
    It's a recommended configuration, but not mandatory.
    Second, does the session cookie uniquely identify the Weblogic server
    or does
    the Apache plug-in keep the mapping between the cookie and the server?The server info is in the cookie for the same client although
    the plugin also maintains a list of servers.
    Also, does
    this answer depend on whether we use Weblogic clustering or not?
    No.
    The answer depends on the protocol between the Apache plug-in and the
    Weblogic
    server. Is it documented? Available under NDA?
    Your help will be really appreciated!!
    We only support http and https(60sp1 or later).

  • Httpproxyservlet or NSAPI or apache plug-in

              Hi all,
              I am new in bea. I want to know if NSAPI's interface is an open document or not,
              because we want to develop our self's web proxy server and cooperate with weblogic
              application server.
              or I am not sure if I can develope or modify a java web server and get httpproxyservlet
              code and integrate it with the web server?
              Thanks for any advice.
              Laura
              

    Hello,
    Chances are you are using the plugin from the base install of WebLogic.
    Please get the latest one from the Service Pack. The MatchExpression
    directive does not exist in the plugin from the base installation of
    WebLogic.
    Regards,
    Eric
    "SenthilKumaran Sivabalan" <[email protected]> wrote in message
    news:[email protected]..
    Hello,
    i have installed the apache-plug-in as the per the documentation. wheniam
    starting the apache webserver i have received the error
    " Invalid Command 'MatchExpression',Perhaps mis-spelled or defined by a
    module not included in the server configuration "
    The Apache webserver is not even starting.
    Environment Apache 1.3.12, SunOS 7, Weblogic 5.1
    Can anyone help me. Thanks in advance
    Senthilkumaran Sivabalan

  • HTTP-Tunneling through Apache Plug-in

    Hello,
    has anybody experience with HTTP-Tunneling of requests to a WLS
    4.5.1SP13 through an Apache-Webserver?
    I'm not able to configure the apache plug-in from weblogic to act as a
    reverse proxy for requests coming from a
    Java Client Application.
    Any Hints available?
    Remo

    "Jong Lee" <[email protected]> wrote in message
    news:3a4a9efa$[email protected]..
    >
    Remo Schnidrig <[email protected]> wrote:
    Hello Jong,
    HTTP tunneling will append ".tun" to your request.
    For apache, you can use "MatchExpression" to proxy the mime type.
    i.e: add the following line to your httpd.conf
    MatchExpression *.tunThat is functioning. Thank you very much.
    Another question:
    What about HTTPS-Tunneling through an Apache-Server?
    How can I get everything through?
    Thank you
    Remo
    We don't support https from the bridge to the server yet.
    JongWhat about using HTTPS-Tunneling between our Java client and the WLS
    Stronghold plug-in and HTTP-Tunneling between the plug-in and the WLS?
    If this is possible, how do I have to setup the stronghold?
    Remo

  • Compile Apache plug-in for WL7.1 SP4

    Hi all,
    Several advisories of Apache have been published. We would like to acquire the latest Apache version. According to the information of BEA. Apache plug-in of WL71SP4 is only provided for Apache 2.0.42-2.0.49. As a result, a new plug-in is needed: we would like to compile one.
    We only have compiled Apache plug-in (with WL71SP4). We cannot find the source in WL71SP4.
    Does anyone know how can I compile a Apache plug-in for the latest Apache version? Preferably, we would like to use APXS for the compilation.
    Does anyone know if we can use the existing plug-in in latest Apache version? We have encountered problems before -- the plug-in refuses to start and complains about incorrect magic string of the Apache version.
    Thank you very much.
    Regards.

    I'm using the mod_wl_ssl.so for Apache on Linux from service pack 5. I
              understand that the communication from Apache to WLS will be via http...
              that's not the issue.
              I think what would solve the issue would be if someone from BEA could post
              an httpd.conf file that was configured correctly to use the ssl proxy for
              Apach on Linux. Also, I can't seem to get clarification if openssl is or is
              not supported.
              Can you post a correctly configured httpd.conf file that was used in testing
              the ssl proxy as well as confirm whether or not openssl is supported???
              Steve...
              Vinod Mehra wrote:
              > Also note that currently we do not support https between the plugins and
              >
              > WebLogic. https requests will be degraded to http. So the WebLogicPort
              > parameter in the plugins should point to the http port of WebLogic.
              >
              > https between plug-ins and WebLogic will be available in near future.
              >
              > --Vinod.
              >
              > Vinod Mehra wrote:
              >
              > > > Are there any known issues with the Apache SSL proxy???
              > >
              > > No
              > >
              > > > I've setup the ssl
              > > > proxy but can't access any WL content via https... http works ok
              > > > though. Also,
              > > > does BEA support openssl or just Stronghold and Raven???
              > >
              > > Yes. Try using mod_wl_ssl.so from 510 SP4 or later.
              > >
              > > --Vinod.
              

Maybe you are looking for