Keep-alive problem in apache/weblogic

I have a server with Weblogic 5.1 and Apache
1.3.12 with the weblogic-plugin.
When apache serves pages, the keep-alive works
fine.
When weblogic serves pages, the keep-alive works
fine.
When i added a handler in apache so all requests
to apache should go to weblogic through the
plugin, the keep-alive stopped working.
Anyone seen this before?
Gunnar

send a message to [email protected] with as much info as you can. i d
on't think they're watching the newsgroups for bug reports.
maybe someone who frequents the newsgroups regularly could do a FAQ...
anyone actually got time?
"Gunnar" <[email protected]> wrote in message
news:3a51995e$[email protected]..
In case anyone wondered:
I tried with sp5 and sp7 and everything worked fine. It seems sp6 is
buggy...
Gunnar <[email protected]> skrev i
meldingsnyheter:3a41e618$[email protected]..
I have a server with Weblogic 5.1 and Apache
1.3.12 with the weblogic-plugin.
When apache serves pages, the keep-alive works
fine.
When weblogic serves pages, the keep-alive works
fine.
When i added a handler in apache so all requests
to apache should go to weblogic through the
plugin, the keep-alive stopped working.
Anyone seen this before?
Gunnar

Similar Messages

HTTP persistent connection (keep Alive) problem

Hi,
I'm trying to deploy a RPC web service and I would like to use the HTTP 1.1 keep alive feature (which should be the default).
I generated the server side and client side code using jdev 903. The AS is OC4j 903.
The problem is that the server is sending a âConnection: close:â header in the SOAP response, despite the client sending a âConnection: keep-aliveâ header in the request. This is obviously causing the client to close the connection and open another for the next message.
The documentation implies that the server will always try to use persistent connections, even so, in the file:
<OC4J_HOME>/j2ee/home/config/http-web-site.xml
there is a config option âuse-keep-alivesâ. Setting this to true has no effect.
Iâm guessing there must be another option somewhere to turn on connection persistence.
Can anyone please help ?

Does anyone know whether Oracle Supports persistent connections ?
I tested this on JBOSS and I seems to get better performance.
cheers.

Weblogic proxy plugin closes keep-alive connections to clients randomly

In short we have following arhitecture:
clients ---> wl proxy plugin 1 ----> weblogic 1
clients ---> wl proxy plugin 2 ----> weblogic 2
Beacuse of the application/installation specific requirements, we are not using failover, one wl proxy always forwards requests to one weblogic (simple configuration).
Application is TR-069 protocol based (SOAP over HTTP) so it very much relays on persistence TCP connections (Connection: keep-alive). This TCP persistence has to work correctly in order that TR-069 messages are exchanged in required order, otherwise we have a error on application layer.
Here and there we've noticed applications errors which suggest that we have some problems in TCP connection between the client and the weblogic server. After sniffing, we've noticed that weblogic proxy plugin (Apache) randomly, or because of some other reason we do not know, decides to close TCP connection to client, even app on weblogic did not request so ???
As a result, client opens new connection to the server with new TR-069 session and it gets bounced beacuse it allready has one open on weblogic server.
We've sniffed, traced everything we could, we were searching for patterns in time, etc... but we can not find the reason why proxy plugin decides to close the connection to the client (not to the weblogic server).
Trace (replaced sensitive information):
Thu Apr 29 15:05:50 2010 <958012725463463784> URL::parseHeaders: CompleteStatusLine set to [HTTP/1.1 200 OK]
Thu Apr 29 15:05:50 2010 <958012725463463784> URL::parseHeaders: StatusLine set to [200 OK]
Thu Apr 29 15:05:50 2010 <958012725463463784> parsed all headers OK
Thu Apr 29 15:05:50 2010 <958012725463463784> sendResponse() : r->status = '200'
Thu Apr 29 15:05:50 2010 <958012725463463784> canRecycle: conn=1 status=200 isKA=1 clen=545 isCTE=0
Thu Apr 29 15:05:50 2010 <958012725463463784> closeConn: pooling for '$IP$/$PORT$'
Thu Apr 29 15:05:50 2010 <958012725463463784> request [$URL$] processed successfully..................
!!!! Now it closes the TCP connection and inserts "Connection: close" HTTP header !!!
WL proxy plugin conf params are:
WebLogicCluster $IP$:$PORT$
DynamicServerList OFF
KeepAliveTimeout 90
MaxKeepAliveRequests 0
KeepAliveSecs 55
Apache worker configuration is:
<IfModule mpm_worker_module>
PidFile var/run/httpd-worker.pid
LockFile var/run/accept-worker.lock
StartServers 2
MinSpareThreads 25
MaxSpareThreads 75
ThreadLimit 200
ThreadsPerChild 200
MaxClients 2000
MaxRequestsPerChild 0
AcceptMutex pthread
</IfModule>
Why weblogic proxy plugin ignores Keep-alive directive and decides to close connection to the client by itself?
Any help?

If a WebLogic Server instance listed in either the WebLogicCluster parameter or a dynamic cluster list returned from WebLogic Server fails, the failed server is marked as "bad" and the plug-in attempts to connect to the next server in the list.
MaxSkipTime sets the amount of time after which the plug-in will retry the server marked as "bad." The plug-in attempts to connect to a new server in the list each time a unique request is received (that is, a request without a cookie).
Note: The MaxSkips parameter has been deprecated as the MaxSkipTime parameter.
See also here: http://download-llnw.oracle.com/docs/cd/E13222_01/wls/docs81/plugins/plugin_params.html
You said the problem arises under significant load. Maybe, it is wise to tune the number file descriptor's on your operating system. HTTP connections are nothing more than TCP sockets on the operating system. All modern operating systems treat sockets as a specialized form of file access and use data structures called file descriptors to track open sockets and files for an operating system process. To control resource usage for processes on the machine, the operating system restricts the number of open file descriptors per process. You should be aware that all TCP connections that have been gracefully closed by an application will go into what is known as the TIME_WAIT state before being discarded by the operating system.
On most unix systems you can use netstat -a | grep TIME_WAIT | wc -l to detemine the number of socket in time_wait state. You have to check with your system adminstrator how to tune the tcp_time_wait_interval. On solaris you can use: /usr/sbin/ndd -set /dev/tcp tcp_time_wait_interval 60000

Weblogic shutting down keep-alive socket improperly?

We were sometimes experiencing strange IE behaviour when surfing on webapps on our Weblogic application servers. After investigation we found that IE has a bug in its resend behaviour, so when resending a POST request it sends the headers (including Content-Length) but forgets the form-data. This causes the server to time out waiting for the data. (Note: We are using Win2K and IE6 SP1 on the clients.)
The IE resend is triggered on a default installation when 31-59 seconds have passed since the last request.
This is because IE will try to reuse a socket that has been told to keep-alive until it has been idle for 60 seconds but WLS will by default close kept-alive sockets when they have been idle for 30 seconds. So in the range 31-59 seconds IE will consider the socket alive but WLS has closed it.
The resend bug is really an IE bug and doesn't concern WLS, but then I saw that IE would function correctly with an Apache server with a default keep-alive timeout of 15 seconds.
Using Ethereal I could get the information depicted in the tables below:
Weblogic with keep-alive timeout 30 secs
old socket
Time 00 : User navigates : IE POST request -> WLS, WLS HTML -> IE
Time 30 : Socket times out : (no network traffic)
Time 45 : User navigates : IE POST request -> WLS, WLS TCP_FIN -> IE
new socket
Time 45 : : IE resends POST request without form-data
Apache with keep-alive timeout 15 secs
old socket
Time 00 : User navigates : IE POST request -> Apache, Apache HTML -> IE
Time 15 : Socket times out : Apache TCP_FIN -> WLS
new socket
Time 45 : User navigates : IE POST request -> Apache, Apache HTML -> IE
To summarize, IE handles Apache well as Apache sends a TCP FIN telegram (to close the connection) as soon as the kept-alive socket times out.
Therefore IE never tries to reuse the socket but instead starts on a fresh one on the next navigation and a resend is never necessary.
Weblogic, on the other hand, doesn't send the TCP FIN (connection close) telegram until IE actually tries to use the connection even though it timed out 15 seconds earlier. In this case IE needs to resend the POST request and this is when the form-data is forgotten.
So, my question now is if WLS behaviour could be caused by not shutting down kept-alive sockets properly at keep-alive timeout? Or why are there no TCP FIN telegrams sent at timeout?
Mike Wilson

After doing some more investigation I have found that the "silent" shutdown of keep-alive sockets is only seen on the Linux version. The Windows version of Weblogic 8 behaves correctly, like Apache on Linux, but Weblogic on Linux does not...
Anyone can confirm if this is to be considered a bug?

Apache-weblogic bridge problems with virtual hosting

Hi,
Can we set apache-weblogic bridge where apache webserver is configured
as virtual hosts and each Virtual Host is mapped to a WebLogic server
instance running on separate port ?
Please provide doc or reference or your comments if you have solved this
problem
Thanks
Shriniwas

The above comments notwithstanding, there's one outstanding line in your post that seems crucial:
Also if I type on my browser the name of another secondary (or virtual) domain name in the form http://domain2.com it brings the website hosted under the primary domain which is domain1.com. In case I type http://www.domain2.com than it works as it should and displays the website hosted under this domain name.
As far as Apache is concerned, 'domain2.com' and 'www.domain2.com' are completely separate entities. They have to be otherwise if all domain2.com traffic went to this site you'd never be able to host different sites within the domain (e.g. blogs.domain2.com, wiki.domain2.com, blah.domain2.com, etc.). In other words, there is no automatic relationship between a hostname and sub-records of that hostname.
So what's happening here is Apache is seeing a request for 'domain2.com' which does not match any of its configured virtual hosts, so it handles the request via the default site. If you request www.domain2.com this matches your virtual host configuration so Apache serves the alternate content.
The fix is simple - trivial, even - you just need to tell Apache all the hostnames that match this site - in this case if you've configured the site's primary address as 'www.domain2.com' and you want it to also respond to requests to 'domain2.com' then add 'domain2.com' to the list of Server Aliases in Server Admin.

Speed limit on pipelining keep-alive requests?

Hi all,
          I was wondering if anyone knows of a limit in how fast weblogic can
          handle multiple servlet requests over a keep-alive connection.
          We were trying to throw a bunch for testing purposes, and it seems that
          if we bunch them closer together than ~300ms, it won't handle more than
          two. (I can recreate the problem by hand, too)
          Is this a limit in Weblogic 6?
          Thanks,
          Dave
          ps: here's the exception trace:
          <Mar 5, 2001 4:15:53 PM EST> <Error> <Posix Performance Pack> <Uncaught
          Throwable in processSockets
          java.lang.NullPointerException
          at weblogic.socket.TunnelContext.getServlet(TunnelContext.java:24)
          at weblogic.servlet.internal.MuxableSocketHTTP.dispatch(MuxableSocketHTT
          P.java:459)
          at
          weblogic.socket.PosixSocketMuxer.deliverGoodNews(PosixSocketMuxer.jav
          a:449)
          at
          weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java
          :378)
          at
          weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:
          23)
          at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
          at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
          >


Hi all,
          I was wondering if anyone knows of a limit in how fast weblogic can
          handle multiple servlet requests over a keep-alive connection.
          We were trying to throw a bunch for testing purposes, and it seems that
          if we bunch them closer together than ~300ms, it won't handle more than
          two. (I can recreate the problem by hand, too)
          Is this a limit in Weblogic 6?
          Thanks,
          Dave
          ps: here's the exception trace:
          <Mar 5, 2001 4:15:53 PM EST> <Error> <Posix Performance Pack> <Uncaught
          Throwable in processSockets
          java.lang.NullPointerException
          at weblogic.socket.TunnelContext.getServlet(TunnelContext.java:24)
          at weblogic.servlet.internal.MuxableSocketHTTP.dispatch(MuxableSocketHTT
          P.java:459)
          at
          weblogic.socket.PosixSocketMuxer.deliverGoodNews(PosixSocketMuxer.jav
          a:449)
          at
          weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java
          :378)
          at
          weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:
          23)
          at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
          at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
          >

Disabling Keep Alive

We are using GWT with Glassfish and Sun Web server. We're encountering occassional problems causing the servlet to fail with "Client did not send xxxx bytes" exception.
I read in another post elsewhere that people have solved this problem in Glassfish-Apache configuration with the following settings:
SetEnv force-proxy-request-1.0 1
SetEnv proxy-nokeepalive 1
Can someone tell me what is the equivalent setting in Sun Webserver?
Thanks

Try "set-reverse-proxy-prop"
[http://docs.sun.com/app/docs/doc/820-2204/set-reverse-proxy-prop-1?l=en&a=view|http://docs.sun.com/app/docs/doc/820-2204/set-reverse-proxy-prop-1?l=en&a=view]
* use-keep-alive Indicates whether the HTTP client should attempt to use persistent connections. The default value is true.
* keep-alive-timeout The maximum number of seconds to keep a persistent connection open. The default value is 29.
* always-use-keep-alive Indicates whether the HTTP client can reuse the existing persistent connections for all types of requests. The default value is false, indicating that persistent connections will not be reused for non-GET requests or for requests with a body.
* protocol The HTTP protocol version string. By default, the HTTP client uses either HTTP/1.0 or HTTP/1.1 based on the contents of the HTTP request. In general, you should not use the protocol parameter unless you encounter specific protocol interoperability problems.
...So, probably this will work for you:
set-reverse-proxy-prop use-keep-alive=false protocol="HTTP/1.0"

Problem with Apache Plugin

          Hi,
          Hi I am getting some Errors when i am trying to Run the Apache Server. Actual Problem is
          I want to create an Cluster Environment using 2 weblogic Cluster. i read that documentation, using apache-weblogic plug-in, we can improve the cluster performence.
          I follow the Same rules and i install ed the Apache server and i copy the *.so file that required for apache(if i commented out the LoadModule weblogic_module libexec/mod_wl.so , serverrunning fine)
          But whenever i am trying to run apache Server with that
          Its given a error like
          "BUG IN DYNAMIC LINKER ld.so:dynamic-link.h:57: elf_get_dynamic_info: Assertion '! "bad dynamic tag" failed!
          ./apachectl start: httpd could not be started
          If u will give some help about this its most helpful for me.
          ThankQ
          Krishna Botla


Which version of Apache are you using? Are you on Solaris?
          Have you enabled the bootstap module mod_so for apache? Do httpd -l to ensure that.
          Did you use apxs to deploy mod_wl.so?
          Please go through the steps described in the docs again to see if you missed something.
          --Vinod.
          KrishnaKumar wrote:
          > Hi,
          > Hi I am getting some Errors when i am trying to Run the Apache Server. Actual Problem is
          > I want to create an Cluster Environment using 2 weblogic Cluster. i read that documentation, using apache-weblogic plug-in, we can improve the cluster performence.
          > I follow the Same rules and i install ed the Apache server and i copy the *.so file that required for apache(if i commented out the LoadModule weblogic_module libexec/mod_wl.so , serverrunning fine)
          > But whenever i am trying to run apache Server with that
          > Its given a error like
          > "BUG IN DYNAMIC LINKER ld.so:dynamic-link.h:57: elf_get_dynamic_info: Assertion '! "bad dynamic tag" failed!
          > /apachectl start: httpd could not be started
          >
          > If u will give some help about this its most helpful for me.
          >
          > ThankQ
          > Krishna Botla

Apache-WebLogic Bridhge Failures

Hi all, We are also having a similar setup, except that we are using WebLogic Server 5.1. We had this problem when the traffic in our production site is high. We thought we had solved the problem when we applied Service Pack 5. But after behaving for sometime if the data upload goes beyond say 5 MB the Bridge fails, but surprisingly the actual data gets uploaded. This happens when the traffic is slightly high on the site. We have set the parameter ConnectionTimeoutSecs in weblogic.conf which is called by the httpd.conf to 900. Still we are having this bridge failure problem once in a while. We are not sure what to do, is there anybody who has faced this problem and managed to solve it ? if so please SOS.Cheers,Aejaz

We don't have apache plugin for Win NT.
check our platform support page.
Kumar
ASIF wrote:
where can i get apache-weblogic PLUGIN for
WINNT

Keep alive a session in CRM

Dear CRM folks -
I am calling CRM using BAPIs. The BAPIs are published as Web Services.
I would like that the session between 2 BAPI calls is maintained in an optimized way so I don't make specific calls to the DB to store my session info.
Anyone knows a way of keeping alive a session in the CRM between 2 BAPI calls?
Thanks !

BAPIs are just basically function modules. Two function modules which are in the same function group are able to share information while the session is open.
If your two BAPIs are not in the same function group(you didn't mention the names or I could have checked) then you can create a wrapper function module which has it's own variables to store the information. Unfortunately once the RFC session/ICM Web Session is closed then you'll lose that in-memory information.
I assume that you're making the two BAPI calls at different times which is why you're having this problem. Like one to get user information and then one more to get some other detailed info once the user inputs something.
Without knowing much about what you are really trying to do, my quick idea is to create a Stateful BSP in CRM which accepts all your requests. The BSP can simply call the BAPIs(eliminate the need for the web service - unless you have some reason you need it) and then between the first and second BAPI call, the BSP will keep the state of the BAPI results in-memory.
If you give more info, might be easier to answer your question.

How to Keep Alive a specific HFM application

My PRD landscape has 2-3 applications. Whenever any application loads for the first time in the memory, it takes quite some time before it is loaded. Once the application is loaded, the response times are pretty quick and acceptable.
During specific parts of the day / month, a specific application becomes active. During this time, other applications may or may not be used, but one specific application is definitely used. I want to keep this application's cubes loaded in the RAM, so that response times are quick, whenever the user needs it - whether for the first time or otherwise.
How to keep alive a specific application's cubes alive and loaded in RAM? I am not looking for general solution like setting the "FM Service" to Automatic (currently it is set Manual) - setting this to Automatic, will affect all applications. However, I am looking for a specific application at a specific period of time.
I am ok with a custom solution if required. Let me know, what are my options.

I think you are looking for an inappropriate solution to your problem. Most HFM applications take a few seconds to start up. If your application takes such a long time to start up you really need to examine the root cause. Start by removing the Sub NoInput and Sub Input routines in your rules to see if this is the reason the application takes so long to start.
If the removal of those routines does not significantly change the startup time, look through the event logs for possible causes. It is possible you have a connection problem with the Oracle database for example, or you have an environment configuration problem where the HFM application servers have a very slow connection to the database server, or possibly the database server performs poorly.
I strongly suggest you investigate these root casues first before trying to make HFM behave in a non-standard way. Certainly you can start the HFM Management Service, which will start all of your HFM applications and keep them all up and running. This approach does not allow the applications to shut down on their own though. Only use this if you have exchausted your investigations (as I suggsted above).
--Chris

Http keep-alive with SOAP webservices

Just had an interesting experience with a web service setup behind UAG...under low load conditions all SOAP responses were coming across with no issue...once a high load was introduced by the client app the behavior changed where an initial request was
processed and subsequent requests were rejected by UAG with a Bad Parameter : Length message...but high load (relatively) on a web browser ran without issue...the client app had to wait ~100 seconds before the next request would process correctly...browser
works - app has problems...turns out it was the keep-alive "default" settings on both the client app server, as well as my web service in IIS...so -apparently UAG thought the 2nd (and subsequent < 100 seconds) were a parameter of the first request...and
was way too long and got rejected...I unchecked the keep-alive enabled box on the http response header (set common headers) and all is fine now! Apparently the browsers were closing the connection with each page load and the service responded appropriately
- so it looked like all was well. Using SOAP UI revealed the error...but it also had it's connection set to keep-alive...once that was disabled in SOAP UI all requests ran correctly...that's when I poked around and found that response header setting.

ejp wrote:
and also an incorrect implementation of the timeout period. This code will still wait forever if no data arrives.You're right... actually I didn't mean to put that while loop there! What I meant was simply
if (!reader.ready())
wait(keepAliveTimeout);
if (!reader.ready())
break mainLoop;
// If we get here there is a new request to read...and I agree that it's ugly, that's why I'm asking you guys for help!
setSoTimeout() is of course a way to go... didn't think of that although I have kind of already added it to my code but with a different timeout. Thanks!
Last question then is:
does reader.readLine() block like reader.read(), or do I have to use the latter?
I would test for myself I could, but at the moment I can't...

Question about Keep Alive feature in Forte 3.

Does anyone use Keep Alive feature under Forte 3.0F.2 environment.
I got trouble and encounters the following problem in the service objects
daily:
INFORMATION: An abnormal disconnect from partition
(CFFE2500-85B0-11D1-B37F-E2F7F3F1AA77:0xec254) was received. Since there
are
no method invocations outstanding to this partition, no notification could
be
given of this disconnect (by indicating a method invocation failed).
Therefore, the information associated with this disconnect is being
reported
to the log.
Class: qqsp_DistAccessException
Error #: [601, 119]
INFORMATION: The connection to the partner was terminated by the
Communication Manager for the reasons below.
Class: qqsp_DistAccessException
Detected at: qqdo_PartitionMgr::StopLocation at 1
Error Time: Fri Nov 26 17:45:39
SYSTEM ERROR: Failed to establish connection: OS Error 61: Connection
refused
Class: qqsp_DistAccessException
Detected at: qqcm_HoseFSM::SetError at 5
Error Time: Fri Nov 26 17:45:39
SYSTEM ERROR: hose 15 STATE_CONNECTING (EXT_RECEIVED) from
qqcm_HoseFSM::IssueConnect (after EstablishConnection)
Class: qqsp_ErrorDescriptor
Detected at: qqcm_HoseFSM::SetError at 1
Error Time: Fri Nov 26 17:45:39
It seems that Keep Alive sometimes disconnects the connection between the
service objects and the environmental manager.
So that any further connection request from the client encounters the
abnormal exception.
Forte seems not to recommend to use this feature in the Forte Relase note
3.0J1.
She states that "Sites that chooses to test KeepAlives should report all
problems to Technical Support ( and let
Technical Support know that you have enabled this capability)"
Should I disable Keep Alive feature under Forte 3.0F2 environment?
Rgds
Tom

Hey Marco,
I can`t find a view that is named like "APEX_APPLICATION_PAGE_IR%". Is it not available on the evaluation instance.
I don`t want to use the build-in CSV download, becaus I want to export thousands of data sets. I got this already to work with APEX 3.0 and I get the sql from the application views. The procedure which creates the file runs a few hours and after that it is inserted into a table from which the user can download the file. In the procedure there happens a few other things, which are very import, so I have to create my custom solution.
And for that I thought it would be very very very cool if I can get the sql behind the interactive report with the filters ant those things.
Don`t you think that would be possible? I guess the APEX create a SQL although, or am I wrong?
Thank you,
Tim

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

Installing Apache-Weblogic Plug-in on RedHat 7.0

I am trying to install the apache-weblogic plug-in on redhat 7.0
I modifed my httpd.conf with the following lines:
LoadModule weblogic_module /usr/lib/apache/mod_wl.so
AddModule mod_weblogic.c
<Location /weblogic>
SetHandler weblogic-handler
PathTrim /weblogic
ErrorPage http://www.yahoo.com
</Location>
<Files *.jsp>
SetHandler weblogic-handler
</Files>
<Ifmodule mod_weblogic.c>
WebLogicHost 10.0.0.3
WebLogicPort 7001
</IfModule>
When I try 10.0.0.3/weblogic/ I get nothing!
Looking in my httpd logs it prints a 302 error!
Help
Kevin

<BLOCKQUOTE><font size="1" face="Verdana, Arial">quote:</font><HR>Originally posted by david walker ([email protected]):
Has anyone encountered problems installing Oracle 8.0.5 on Redhat 7.0. RedHat 6.2 installation works.<HR></BLOCKQUOTE>
Should be OK. I was running that combination for a while and can't recall any serious issues during install.
I am currently running 8.0.5.1 on a Mandrake 7.2 PC. The install was pretty straightforward :
- Install compatability RPMs (I used slightly higher versioned RPMs than listed in the Oracle documentation);
- Install 8.0.5.1 s/w;
- Apply Oracle patch;
- Create dbs;
- Configure listener;
- Create the startup/shutdown rc script and links.
That's about it for the installation.
I haven't put the database to much use yet, so there may be other issues ahead :)
Oh, one thing to note on that last point is that you should have a look at how the /etc/rc.d/rc file operates.
Under Mandrake 7.2 it will look for a file in /var/lock/subsystem that has the same name as the /etc/init.d script before running the stop script correctly.
This differs slightly from what I see in the *8.1.7* documentation, so might be due to a difference between mandrake and the other distributions.
FWIW here is my /etc/init.d/oracle file.
#!/bin/sh
# chkconfig: 345 99 10
# description: Oracle databases
# Source function library.
. /etc/init.d/functions
CWD=`pwd`
# See how we were called.
case "$1" in
start)
su - oracle -c '. $HOME/.oraclerc && dbstart && lsnrctl start'
touch /var/lock/subsys/oracle
stop)
su - oracle -c '. $HOME/.oraclerc && dbshut && lsnrctl stop'
rm -f /var/lock/subsys/oracle
restart)
cd $CWD
$0 stop
$0 start
echo "Usage: oracle {start|stop|restart}"
exit 1
esac
exit 0
null

Keep-alive problem in apache/weblogic

Similar Messages

Maybe you are looking for