WLS 7.0SP2 Apache Plug-in application fault

I'm running WLS 7.0SP2 on XP and have the WLS Apache plug-in in Apache 2.0.49.
I get this application fault alot...
Faulting application apache.exe, version 2.0.49.0, faulting module unknown, version
0.0.0.0, fault address 0x008be6ae.
The only other non-default module I'm using mod_headers.
I have the same problem in Apache 2.0.45, 2.0.46, 2.0.47, 2.0.48, and 2.0.49
Has anyone else run across this problem? I'd REALLY like to know the root cause..
Thanks,

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 Virtual Hosting and WLS 6.0 Apache plug-in

We have a client that uses Apache and virtual hosting. We also have a
single webapp that serves these virtual hosts/domains.
Therefore, all of the served virtual hosts/domain has the same webapp
directory structure ( e.g.: index.jsp, advert.jsp, css/ )
For the above to work, we are thinking of getting the requested virtual
hostname ( supposedly part of the HTTP header sent by the browser as the
"Host:" parameter ) to figure out how the page will be displayed ... Does
the Apache plug-in send this information to WLS?

Apache plugin will forward the "Host" header to wls.
BTW, HTTP1.0 client will not send the HOST header if I recalled properly since
HOST header is not part of HTTP1.0 spec.
Jesus M. Salvo Jr. <[email protected]> wrote:
>
We have a client that uses Apache and virtual hosting. We also have a
single webapp that serves these virtual hosts/domains.
Therefore, all of the served virtual hosts/domain has the same webapp
directory structure ( e.g.: index.jsp, advert.jsp, css/ )
For the above to work, we are thinking of getting the requested virtual
hostname ( supposedly part of the HTTP header sent by the browser as
the
"Host:" parameter ) to figure out how the page will be displayed ...
Does
the Apache plug-in send this information to WLS?

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

Apache - Weblogic plug-in - Segmentation fault. Please Help me!

Hi all,
Im trying to set up Apache weblogic plug-in, and im having problems with
that.
Im running Solaris 9 with Apache/1.3.26 (Unix) and Weblogic 7 with sp2.
Here is what i did:
I copied mod_wl_ssl.so from
/bea/weblogic700/server/lib/solaris/mod_wl_ssl.so to /usr/apache/libexec
Added entries in httpd.conf as
LoadModule weblogic_module /usr/apache/libexec/mod_wl_ssl.so
AddModule mod_weblogic.c
<LocationMatch "\.jsp$">
SetHandler weblogic-handler
StatPath false
</LocationMatch>
<LocationMatch "/(service1|service2|service3)/">
SetHandler weblogic-handler
StatPath false
</LocationMatch>
<IfModule mod_weblogic.c>
WebLogicHost 127.0.0.1
WebLogicPort 7001
HungServerRecoverSecs 300
ConnectTimeoutSecs 5
</IfModule>
When i access the url with out specifying port 7001 it's not working.
I checked the /var/apache/logs/error_log file. Im getting the error as
child pid 805 exit signal Segmentation Fault (11)
Am i missing anything here?
Thank you
Raja

You may want to check the certifications for Solaris 9 and the Apache plug-in at
http://e-docs.bea.com/wls/certifications/certifications/sun_solaris9.html#40366.
It looks like you will have to upgrade to at least Apache 2.0.39. We had to do
this on Solaris 8 as well.
"Raja Balasubramanian" <[email protected]> wrote:
Thank you Eric,
I will do that
Raja
"Eric Gross" <[email protected]> wrote in message
news:[email protected]...
I believe this is going to require more debugging such as attachinga
debugger(gdb) to Apache and getting a backtrace.
I suggest opening up a support case.
Regards,
Eric
"Raja Balasubramanian" <[email protected]> wrote in message
news:[email protected]...
Hi Eric,
Thank you for the replies.
I tried with the same test as you specified. Still im getting the
same
problem.
[Mon Mar 10 13:57:21 2003] [notice] child pid 1184 exit signal
Segmentation Fault (11)
Im running Solaris 9 in SPARC platform. It's a Sun E450 server.
Im using the default apache package which comes with Solaris 9. Ididn't
do
anything with apache.
Bea website says that Weblogic 7 sp2 is certified for Soalris 9.
That's
y
i
installed Solaris 9.
I tested the same on a Linux Machine (Redhat Linux 7.1 on IA). It
works
fine
without any problem.
How can i make things work?
Thank you for your kind replies
Raja
"Eric Gross" <[email protected]> wrote in message
news:[email protected]...
Looks like it should work.
Let's simplify your test:
<Location /test>
WebLogicHost 127.0.0.1
WebLogicPort 7001
Debug ALL
DebugConfigInfo ON
SetHandler weblogic-handler
</Location>
Try with just that.
Another thing is that I am unsure as to whether we have tested
with
Solaris
9. This is SPARC right? Also, can you outline the steps you took
when
building apache? Did you use GCC?
Thanks,
Eric
"Raja Balasubramanian" <[email protected]> wrote
in
message
news:[email protected]...
Hi,
Now i changed to mod_wl_ssl.so.
And i changed the httpd.conf as
LoadModule weblogic_module libexec/mod_wl_ssl.so
<IfModule mod_weblogic.c>
WebLogicHost 127.0.0.1
WebLogicPort 7001
Debug ALL
DebugConfigInfo ON
StatPath true
HungServerRecoverSecs 300
ConnectTimeoutSecs 5
</IfModule>
But im getting the same error. NO wlproxy.log file is created
in my
server.
I tried Debug ON also. Still the same.
Am i doing anything wrong?
Please help me...
Thank you
Raja
"Eric Gross" <[email protected]> wrote in message
news:[email protected]...
That means that your apache instance is compiled with -DEAPI
and
should
use
the mod_wl_ssl.so.
Can you please try to set Debug ALL and get the log in
/tmp/wlproxy.log
and
share that?
Thanks,
Eric
"Raja Balasubramanian" <[email protected]> wrote
in
message
news:[email protected]...
Hi Eric,
When im using mod_wl.so im getting warning from Apache as
[Mon Mar 10 12:41:15 2003] [warn] Loaded DSO
libexec/mod_wl.so
uses
plain Apache 1.3 API, this module might crash under
EAPI!
(please
recompile it with -DEAPI)
Thank you
Raja
"Eric Gross" <[email protected]> wrote in message
news:[email protected]...
Are you using modssl or any apache with EAPI compiled in?
Otherwise, you should be using the mod_wl.so.
As well, please set Debug ALL to see if we can get more
debug.
Thanks,
Eric
"Raja Balasubramanian" <[email protected]>
wrote
in
message
news:[email protected]...
Hi all,
Im trying to set up Apache weblogic plug-in, and im having
problems
with
that.
Im running Solaris 9 with Apache/1.3.26 (Unix) and Weblogic
7
with
sp2.
Here is what i did:
I copied mod_wl_ssl.so from
/bea/weblogic700/server/lib/solaris/mod_wl_ssl.so to/usr/apache/libexec
Added entries in httpd.conf as
LoadModule weblogic_module/usr/apache/libexec/mod_wl_ssl.so
AddModule mod_weblogic.c
<LocationMatch "\.jsp$">
SetHandler weblogic-handler
StatPath false
</LocationMatch>
<LocationMatch "/(service1|service2|service3)/">
SetHandler weblogic-handler
StatPath false
</LocationMatch>
<IfModule mod_weblogic.c>
WebLogicHost 127.0.0.1
WebLogicPort 7001
HungServerRecoverSecs 300
ConnectTimeoutSecs 5
</IfModule>
When i access the url with out specifying port 7001 it's
not
working.
I checked the /var/apache/logs/error_log file. Im getting
the
error
as
child pid 805 exit signal Segmentation Fault
(11)
Am i missing anything here?
Thank you
Raja

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

Help about W2K Apache plug-in for WLS

Hi,everybody.
I want to use the W2K apache http server for redirect the dynamic request to
WLS. But i don't have the corresponding plug-in. Who can help me? or Who can
give me some hint about this?
Thanks in advance.
BR
Steven Zhao

Hi Steven,
as far as I know there is no Apache Plugin for Windows Platform. Your
choice is either Unix->Apache or Windows->IIS. I think there is a
Netscape Plugin as well, but I don't know for which platforms.
Daniel
-----Original Message-----
From: Steven Zhao [mailto:[email protected]]
Posted At: Friday, October 20, 2000 6:02 AM
Posted To: management
Conversation: Help about W2K Apache plug-in for WLS
Subject: Help about W2K Apache plug-in for WLS
Hi,everybody.
I want to use the W2K apache http server for redirect the dynamic
request to
WLS. But i don't have the corresponding plug-in. Who can help me? or Who
can
give me some hint about this?
Thanks in advance.
BR
Steven Zhao

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

Question with using ssl of apache plug-in

hi all,
I use redhat 6.0,apache 1.3.19, wls6.0sp1.
how can I proxy a ssl request from apache to wls?
can someone give example conf files(httpd.conf,weblogic.conf)?
Thanks.
Kent

Yes the weserver could help in taking some load off weblogic. In case of
upload
the connection from WebLogic is not initiated until all the POST data is
read from the
client. So if the client connection is slow WebLogic will not be affected.
Similarly
after reading the response data from weblogic, plugins close the connetion
with
WebLogic. So worth a try.
-Vinod.
"Matt Geis" <[email protected]> wrote in message
news:3a7af7b6$[email protected]..
Hi,
We have an application (JSP, EJB) running on WLS 5.1sp6, and we're
experiencing load issues. In the past, I've been able to get much higher
performance out of weblogic (at one point we were maxing the server, anE450
with 3cpu, 3GB memory) with 100 users. In the meantime, we've identified
problem areas (db, solaris tuning, etc.). I'm wondering what kind of
performance gain we might see using the apache plug-in.
Obviously, having apache serve up static content will free up weblogic to
handle the requests for dynamic content.
What I'd really like to know is how does the apache plug-in actuallyhandle
requests/responses. We have a number of users who connect directly to our
network by modem, and I'm thinking that they may be hogging resources. AmI
correct in assuming that if the modem user needs 20 seconds to download40k
of data from our server, that his connection to weblogic will be activefor
the 20 seconds? If so, would adding the apache bridge help? If apache
maintains a connection to weblogic during the entire download, servingonly
as a passthrough, I imagine it wouldn't help a lot. However, if Apache
makes the request, and buffers the response, such an approach would freeup
weblogic threads to handle other requests while busies itself with the
delivery of data to the slow client.
Please help me out on this one (and thanks in advance).
Matt

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

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

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

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

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.

WLS 7.0SP2 Apache Plug-in application fault

Similar Messages

Maybe you are looking for