WLS 8.1, Apache 2.0.49 proxy plug-in problem

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

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

Similar Messages

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

Apache 2.0.53 with proxy plug-in adds characters to static files

When delivering a javascript (.js) file that is packaged within the WAR deployed on the WebLogic 8.1, it will deliver correctly when going directly to the AppServer port. However, when requesting this same file trhough the Apache web server and proxy plug-in, additional characters are appearing.
The beginnig of the javascript file is a comment header.
* some coment info
When transmitted through the proxy-plugin and apache, this file is delivered as:
ï»¿/*
* some comment info
Thanks in advance for the help.
-Travis

Mr. Melhiser -
shoot me an e-mail if you get a chance - gots a rh quicky.

Windows Oracle Proxy Plug-in with Apache

I've loaded and configured the Oracle Proxy Plug-in for use on an IIS system, but would now like to configure this for Apache (as in an IAS) on a Windows platform.
I've mimicked the LoadModule and AddModule commands as a best guess, but I haven't been able to deduce the path information for the serverdef.conf file. As a result the HTTPD service fails to start.
Is anybody able to help?
Best regards,
Malcolm

Hello Malcolm
I was intrigued to see that you have successfully configured Oracle App Server proxy plugin for IIS. I have been trying to do this for a while but have not been successful. I would be really grateful for any assistance please.
I'm using Ora App server 10.1.2.0.2 and IIS 6. I've also put the proxy dll from the 10.1.2..0.2 Companion CD. I've even tried to use port 80 in the proxy.txt file.
All registry keys are setup for the dll and the log entries.
If I forward all requests - ie have the URLRule for all requests, then just typing the IIS server name (http://iisserver) dies forward to the APp server's welcome page on the Application Server.
The following are in the oas_proxy.txt file
oproxy.serverlist=ias1
# Hostname to use when communicating with a specific server.
oproxy.ias1.hostname=farswserver1.ads.autodesk.com
# Port to use when communicating with a specific server.
oproxy.ias1.port=80
# Description of URL(s) that will be redirected to this server.
oproxy.ias1.urlrule=/*
Much appreciate all help please.
Many thanks
Shashi

Apache Proxy Plug-in with multiple clusters?

We are using the Apache Proxy Plug-in , the
          basic question is if we can place multiple cluster
          IP's in the same Location definition or do we have
          to have a different definition for each cluster?
          Currently we have only 1 cluster, but if we decide
          to segment the large cluster into smaller clusters
          this is a critical network,url question.
          For example we have 4 clusters containing 2 IP:PORT pairs each.
          IP1:P1,IP2:P2 <== Cluster 1
          IP3:P3,IP4:P4 <== Cluster 2
          IP5:P5,IP6:P6 <== Cluster 3
          IP7:P7,IP8:P8 <== Cluster 4
          Can we have a single location "application" that services all of these clusters?
          <Location /webapp>
          SetHandler weblogic-handler
          WebLogicCluster IP1:P1,IP2:P2,IP3:P3,IP4:P4,IP5:P5,IP6:P6,IP7:P7,IP8:P8
          </Location>
          Or do we have to have distinct entries?
          <Location /webapp1>
          SetHandler weblogic-handler
          WebLogicCluster IP1:P1,IP2:P2
          </Location>
          <Location /webapp2>
          SetHandler weblogic-handler
          WebLogicCluster IP3:P3,IP4:P4
          </Location>
          <Location /webapp3>
          SetHandler weblogic-handler
          WebLogicCluster IP5:P5,IP6:P6
          </Location>
          <Location /webapp4>
          SetHandler weblogic-handler
          WebLogicCluster IP7:P7,IP8:P8
          </Location>
          Regards.

you should define location for each cluster.This would be a proper setup.
          The setup with same location definition would work partially, all the requests would be roundrobined across all the servers (all the clusters) and most likely you wouldn't get a proper failover.(cluster1 does not know about cluster2 from weblogic perspective)
          Vijay

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...

Load balancer vs. proxy plug-in

          Using WebLogic 6.1 SP2, the proxy plug-in handles the logic of connecting to
          the secondary server (stored in a cookie) if the primary is down. How does
          this work if you use a hardware load balancer in place of the proxy
          plug-ins?


More info at http://edocs.bea.com/wls/docs61/cluster/alteon.html#591902 and
          http://edocs.bea.com/wls/docs61/cluster/bigip.html#591902.
          Kumar Allamraju wrote:
          > Hi:
          >
          > yeah this was a problem in 5.1
          > We relaxed this restriction in 6.x release. This is the main reason WLS
          > clustering will now
          > work with hardware load balancers.
          >
          > Starting from 6.x, any server can become a primary server when failover
          > happens.
          > For e.g. if S1 and S2 are primary & secondary servers for client1 and when
          > the HW LD detects
          > that the primary is down, it will route the request to any of the servers
          > (can be S3, S4, S5) in the cluster
          > and that server(e.g. S3) will become the primary server for this
          > request(i.e. client1) and get this client's session data
          > from S2. At this point S3 become primary and S3 will nominate another server
          > (e.g. S4) as a secondary server
          > (based on the replication groups, if any)
          > We will only do this for active clients. For e.g if client2 doesn't make a
          > request when S1 is down, we don't try to
          > get it's data and chose a new secondary for him. This is called lazy
          > initialization/replication.
          >
          > Hope it helps.
          >
          > --
          > Kumar
          > "Joe" <[email protected]> wrote in message news:[email protected]...
          > >
          > > Using WebLogic 6.1 SP2, the proxy plug-in handles the logic of connecting
          > to
          > > the secondary server (stored in a cookie) if the primary is down. How
          > does
          > > this work if you use a hardware load balancer in place of the proxy
          > > plug-ins?
          > >
          > >
          > >
          > >
          Rajesh Mirchandani
          Developer Relations Engineer
          BEA Support

AS Proxy Plug-In for IIS 6.0 Windows 2003

Any ideas when and what version of the Application Server Proxy Plug-in will work with IIS 6.0 / Windows 2003.

Hi I am attempting to install IIS on one server with another server using Oc4j standalone can and the server dosnt seem to respond. Can you give me any insight on how to get this to work or if it can ?

IIS (proxy) plug-in and gif images

I was wondering if anyone has run into the problem of not having the linked images load/show up that within a jsp going thru the iis proxy plug-in setup?


Hello,
          If the GIF images are located on the WebLogic Server, then you need to setup
          IIS to proxy .gif to WebLogic as well.
          It is recommended to place the GIf images on IIS as static content should be
          served by IIS for performance reasons.
          Regards,
          Eric
          "Steve Kruse" <[email protected]> wrote in message
          news:3acd5b9c$[email protected]..
          > I was wondering if anyone has run into the problem of not having the
          linked images load/show up that within a jsp going thru the iis proxy
          plug-in setup?

Iplanet Proxy Plug-in issue

We use sunone web server(6.1 sp7) to communicate weblogic cluster app servers
In the web server error logs we continue to see following error messages all the time even though there is no issues in accessing application and everthing else working fine. These error messages are misleading and how we can avoid it.
do we need upgrade plugin or use some parameter with plugin?
cpp]: Error connecting to host xx.xx.xx.xx:23120'
[16/Sep/2009:06:26:02] failure (19970): for host yy.yy.yy.yy trying to GET /default-home.htm, wl-proxy reports
: exception occurred for backend host 'xx.xx.xx.xx/23120/0': 'CONNECTION_REFUSED [os error=0, line 1732 of URL.
magnus.conf has following setting
Init fn="load-modules" funcs="wl_proxy,wl_init" shlib="/rim/webapp/wls92mp2/weblogic92/server/plugin/solaris/sparc/libproxy_61.so"

http or https
          daniel lolieux wrote:
          > hi
          >
          > what is the protocol between the proxy plug-in and the weblogic server?
          >
          > thx

Load Balance Plug-in VS Reserve Proxy Plug-in

Hi,
We are trying to setup the connectivity between sun java system web server 7.0 to glass fish 2.1.
Which technology of Load Balance Plug-in VS Reserve Proxy Plug-in is better? What is the advantage one over another? Thanks!

It may be helpful to note the lineage of the SAFs:
The GF LoadBalancer SAF is the eldest
The Web Server Reverse Proxy SAF is the next version and is derived from the GF LoadBalancer
The Reverse Proxy feature of WS7 is the third version and is derived from the Web Server Reverse Proxy SAF
The source for the Reverse Proxy SAF in WS7 is visible in the moribund Open Web Server source drop.

9iAS Proxy Plug-in

I have successfully configured iPlanet to serve as the front-end web server for 9iAS R2.
In my case, the iPlanet and the 9iAS reside in the same machine. So, that's mean I have to run two HTTP listeners (iPlanet and Oracle HTTP server) at the same time. Am I right?
Does anyone have similar configuration? What I concern about is the performance. Will the response time be doubled if all HTTP requests have to pass thru iPlanet first?
Thanks,
Kae

Hi Kae,
Glad to hear you've got the 9iAS Proxy Plug-In configured properly and working.
You are correct, you will be running both the iPlanet and Oracle HTTP Servers (OHS) -- the Proxy Plug-In will forward on the appropriate requests from iPlanet to OHS. Regarding performance, you shouldn't notice much of a hit since both web servers are on the same box. Also, depending on what activity you're performing in the app server itself (DB calls?, servlet execution, etc.) the percentage of time making the hop between iPlanet and OHS should be minimal when measured in the context of the total request/response time.
By making the hop to OHS, you continue to have the benefit of using mod_ocj4 to load balance across your OC4J's as well as still making use of 9iAS high availablity (OPMN) and clustering features (DCM).
Hope this helps...
John

Reverse Proxy plug in and Load Balancer Plug in

Hi,
Can anyone please provide me with an example obj.conf file showing how to combine the reverse proxy plug-in and Load Balancer plug-in.
I would like to use the reverse proxy plug in to detect when static content is requested and provide this from the web server. Requests for dynamic content would then be forwarded to an Application server via the Load balancer plug-in. I have found plenty of documentation on how to configure these plug-in separately but nothing on how to combine the two.

smiking
reverse proxy plugin - its job is to forward the requests to another server for a specific task. you can use the webserver 7 . it does forward and limited load balancing (using round robin ) based on the number of servers you provide in the configuration. i would say this is a poor man's setup.
load balancer plugin - some app servers like sun java system app server or web logic provide this plugin so that you can effectively use the back end app server
with both these setup, you can <if> constructs to determine which requests need to be forwarded to the back end server.
I wonder, why do you need both - if both of them is designed to do the same thing.

Released :: Reverse Proxy Plug-in 1.0.2

We are delighted to announce that Reverse Proxy Plug-in 1.0.2 is released for Sun Java System WebServer 6.1 SP11. It can be publicly downloaded at:
[https://cds.sun.com/is-bin/INTERSHOP.enfinity/WFS/CDS-CDS_SMI-Site/en_US/-/USD/ViewProductDetail-Start?ProductRef=SJWS-6.1SP11-RPAddOn1.0.2-G-F@CDS-CDS_SMI]
The Release Notes are here: [http://docs.sun.com/app/docs/doc/820-7660]
This new RPP release addresses couple of bugs, that includes one RPP related bug fixed in the base WS6.1SP11.
All RPP Plug-in users (RPP1.0 & RPP1.0.1) are encourage to upgrade to RPP1.0.2 & WS6.1SP11.
Thank you to the entire product team for another great release!
On Behalf of WS Team!
============== WS6.1 SP11 Release =====================
We are delighted to announce that Web Server 6.1 SP11 has been released. It can be publicly downloaded at:
[https://cds.sun.com/is-bin/INTERSHOP.enfinity/WFS/CDS-CDS_SMI-Site/en_US/-/USD/ViewProductDetail-Start?ProductRef=SJWS-6.1-SP11-OTH-G-F@CDS-CDS_SMI]
The Release Notes are here: [http://docs.sun.com/app/docs/doc/820-7659]
This service pack addresses around 15-bugs, which are mostly customer escalated issues. All users of Web Server 6.1 through Web Server 6.1 SP10 are encourage to upgrade.
Thank you to the entire product team for another great release!
On Behalf of WS Team!

We are delighted to announce that Reverse Proxy Plug-in 1.0.2 is released for Sun Java System WebServer 6.1 SP11. It can be publicly downloaded at:
[https://cds.sun.com/is-bin/INTERSHOP.enfinity/WFS/CDS-CDS_SMI-Site/en_US/-/USD/ViewProductDetail-Start?ProductRef=SJWS-6.1SP11-RPAddOn1.0.2-G-F@CDS-CDS_SMI]
The Release Notes are here: [http://docs.sun.com/app/docs/doc/820-7660]
This new RPP release addresses couple of bugs, that includes one RPP related bug fixed in the base WS6.1SP11.
All RPP Plug-in users (RPP1.0 & RPP1.0.1) are encourage to upgrade to RPP1.0.2 & WS6.1SP11.
Thank you to the entire product team for another great release!
On Behalf of WS Team!
============== WS6.1 SP11 Release =====================
We are delighted to announce that Web Server 6.1 SP11 has been released. It can be publicly downloaded at:
[https://cds.sun.com/is-bin/INTERSHOP.enfinity/WFS/CDS-CDS_SMI-Site/en_US/-/USD/ViewProductDetail-Start?ProductRef=SJWS-6.1-SP11-OTH-G-F@CDS-CDS_SMI]
The Release Notes are here: [http://docs.sun.com/app/docs/doc/820-7659]
This service pack addresses around 15-bugs, which are mostly customer escalated issues. All users of Web Server 6.1 through Web Server 6.1 SP10 are encourage to upgrade.
Thank you to the entire product team for another great release!
On Behalf of WS Team!

WLS with the HttpClusterServlet or Apache with proxy plug-in?

I'm newbie with WebLogic Server cluster.
Please tell me which is better for load balancing for WLS cluster? WLS with the HttpClusterServlet or Apache HTTP Server Plug-In? And which is recommended for production environment?
Many thanks.

Apache with plug-in, as this is easier configurable.
For the HttpClusterServlet all the configuration goes into web.xml which has to be packaged as a war file and deployed to WebLogic.
When any change is needed you have to edit the web.xml file, package it again and redeploy it.
An example of the Apache plug-in set-up can be found here: http://middlewaremagic.com/weblogic/?p=7795 (the load balancing section)
Or if you want to use the Oracle Web-Tier (which includes a precompiled Apache HTTP server): http://middlewaremagic.com/weblogic/?p=7819 (the load balancer section)

WLS 8.1, Apache 2.0.49 proxy plug-in problem

Similar Messages

Maybe you are looking for