RE: [users@httpd] Issues migrating Weblogic proxies from Sun One 6.1 to Apache 2.4
I have not yet tried disabling KeepAlive. For our IPlanet servers we have always had KeepAlive turned ON. Also support recommended I make sure it is ON. I guess I can try turning it off just to see what happens, but I imagine there is a performance hit leaving it like that. I have tried increasing the KeepAlive timeout, and increasing the WLSocketTimeoutSecs and WLIOTimeoutSecs, but that did not help. I also have not fiddled with ConnectRetrySecs or ConnectTimeoutsecs yet. I didn't think would those were applicable here, since I increasing the sleep timeout would not be applicable. Also our application has not been returning any 503 Service Unavailable responses. -Joe -Original Message- From: Mike Rumph [mailto:mike.ru...@oracle.com] Sent: Friday, July 01, 2016 10:03 AM To: users@httpd.apache.org Subject: Re: [users@httpd] Issues migrating Weblogic proxies from Sun One 6.1 to Apache 2.4 Hello Joe, You can see the parameters that are available from the WLS plug-ins here: - https://docs.oracle.com/middleware/1213/webtier/PLGWL/plugin_params.htm#PLGWL475 The equivalent to what Yann was referring could be KeepAliveEnabled and KeepAliveSecs. But ConnectTimeoutSecs, ConnectRetrySecs, WLSocketTimeoutSecs and WLIOTimeoutSecs might also be useful. Thanks, Mike On 7/1/2016 3:06 AM, Joe Muller wrote: > As far as we can see from fiddler and the Apache logs the request is fully > sent. I assume those parameters you mentioned are for mod_proxy ? We are > not using mod_proxy for this, we are using the Weblogic plug-in for Apache > 2.4. > > -Original Message- > From: Yann Ylavic [mailto:ylavic@gmail.com] > Sent: Friday, July 01, 2016 3:42 AM > To: users@httpd.apache.org > Subject: Re: [users@httpd] Issues migrating Weblogic proxies from Sun > One 6.1 to Apache 2.4 > > On Fri, Jul 1, 2016 at 12:49 AM, Joe Muller wrote: >>One interesting thing we did find on a packet capture on the back end >> between the proxy server and the application server is that 3 seconds after >> the proxy server apparently closed the port, the Weblogic application server >> tried to send data. It almost like Weblogic did not realize the port was >> closed. Very odd. > Is the HTTP request fully sent (proxy) and responded (backend) when this > happens? (I try to understand why a backend/application would send data on > its own). > > Otherwise, on a general rule, did you take care that the TTL of proxy > connection (to the backend) is lower than the KeepAliveTimeout configured on > the backend? > This can be done by using the ProxyPass/BalancerMember parameter ttl=... > But before that, does disabling keepalive on the proxy help already? > (ProxyPass' disablereuse=on or SetEnv proxy-nokeepalive) > > Regards, > Yann. > > - > To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org > For additional commands, e-mail: users-h...@httpd.apache.org > > - > To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org > For additional commands, e-mail: users-h...@httpd.apache.org - To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org For additional commands, e-mail: users-h...@httpd.apache.org - To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org For additional commands, e-mail: users-h...@httpd.apache.org
Re: [users@httpd] Issues migrating Weblogic proxies from Sun One 6.1 to Apache 2.4
Hello Joe, You can see the parameters that are available from the WLS plug-ins here: - https://docs.oracle.com/middleware/1213/webtier/PLGWL/plugin_params.htm#PLGWL475 The equivalent to what Yann was referring could be KeepAliveEnabled and KeepAliveSecs. But ConnectTimeoutSecs, ConnectRetrySecs, WLSocketTimeoutSecs and WLIOTimeoutSecs might also be useful. Thanks, Mike On 7/1/2016 3:06 AM, Joe Muller wrote: As far as we can see from fiddler and the Apache logs the request is fully sent. I assume those parameters you mentioned are for mod_proxy ? We are not using mod_proxy for this, we are using the Weblogic plug-in for Apache 2.4. -Original Message- From: Yann Ylavic [mailto:ylavic@gmail.com] Sent: Friday, July 01, 2016 3:42 AM To: users@httpd.apache.org Subject: Re: [users@httpd] Issues migrating Weblogic proxies from Sun One 6.1 to Apache 2.4 On Fri, Jul 1, 2016 at 12:49 AM, Joe Muller wrote: One interesting thing we did find on a packet capture on the back end between the proxy server and the application server is that 3 seconds after the proxy server apparently closed the port, the Weblogic application server tried to send data. It almost like Weblogic did not realize the port was closed. Very odd. Is the HTTP request fully sent (proxy) and responded (backend) when this happens? (I try to understand why a backend/application would send data on its own). Otherwise, on a general rule, did you take care that the TTL of proxy connection (to the backend) is lower than the KeepAliveTimeout configured on the backend? This can be done by using the ProxyPass/BalancerMember parameter ttl=... But before that, does disabling keepalive on the proxy help already? (ProxyPass' disablereuse=on or SetEnv proxy-nokeepalive) Regards, Yann. - To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org For additional commands, e-mail: users-h...@httpd.apache.org - To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org For additional commands, e-mail: users-h...@httpd.apache.org - To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org For additional commands, e-mail: users-h...@httpd.apache.org
Re: [users@httpd] Issues migrating Weblogic proxies from Sun One 6.1 to Apache 2.4
that would certainly be a good test. To see if you get the same behaviour disabling weblogic plugin and switching to mod_proxy. If with both the issue happens the same you have a very good reason to believe the issue is not in the reverse proxy, but rather the backend or the balancer. 2016-07-01 12:06 GMT+02:00 Joe Muller : > > As far as we can see from fiddler and the Apache logs the request is fully > sent. I assume those parameters you mentioned are for mod_proxy ? We are > not using mod_proxy for this, we are using the Weblogic plug-in for Apache > 2.4. > > -Original Message- > From: Yann Ylavic [mailto:ylavic@gmail.com] > Sent: Friday, July 01, 2016 3:42 AM > To: users@httpd.apache.org > Subject: Re: [users@httpd] Issues migrating Weblogic proxies from Sun One > 6.1 to Apache 2.4 > > On Fri, Jul 1, 2016 at 12:49 AM, Joe Muller wrote: > > > > One interesting thing we did find on a packet capture on the back end > between the proxy server and the application server is that 3 seconds after > the proxy server apparently closed the port, the Weblogic application > server tried to send data. It almost like Weblogic did not realize the > port was closed. Very odd. > > Is the HTTP request fully sent (proxy) and responded (backend) when this > happens? (I try to understand why a backend/application would send data on > its own). > > Otherwise, on a general rule, did you take care that the TTL of proxy > connection (to the backend) is lower than the KeepAliveTimeout configured > on the backend? > This can be done by using the ProxyPass/BalancerMember parameter ttl=... > But before that, does disabling keepalive on the proxy help already? > (ProxyPass' disablereuse=on or SetEnv proxy-nokeepalive) > > Regards, > Yann. > > - > To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org > For additional commands, e-mail: users-h...@httpd.apache.org > -- *Daniel Ferradal* IT Specialist email dferradal at gmail.com linkedin es.linkedin.com/in/danielferradal
RE: [users@httpd] Issues migrating Weblogic proxies from Sun One 6.1 to Apache 2.4
As far as we can see from fiddler and the Apache logs the request is fully sent. I assume those parameters you mentioned are for mod_proxy ? We are not using mod_proxy for this, we are using the Weblogic plug-in for Apache 2.4. -Original Message- From: Yann Ylavic [mailto:ylavic@gmail.com] Sent: Friday, July 01, 2016 3:42 AM To: users@httpd.apache.org Subject: Re: [users@httpd] Issues migrating Weblogic proxies from Sun One 6.1 to Apache 2.4 On Fri, Jul 1, 2016 at 12:49 AM, Joe Muller wrote: > > One interesting thing we did find on a packet capture on the back end > between the proxy server and the application server is that 3 seconds after > the proxy server apparently closed the port, the Weblogic application server > tried to send data. It almost like Weblogic did not realize the port was > closed. Very odd. Is the HTTP request fully sent (proxy) and responded (backend) when this happens? (I try to understand why a backend/application would send data on its own). Otherwise, on a general rule, did you take care that the TTL of proxy connection (to the backend) is lower than the KeepAliveTimeout configured on the backend? This can be done by using the ProxyPass/BalancerMember parameter ttl=... But before that, does disabling keepalive on the proxy help already? (ProxyPass' disablereuse=on or SetEnv proxy-nokeepalive) Regards, Yann. - To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org For additional commands, e-mail: users-h...@httpd.apache.org
Re: [users@httpd] Issues migrating Weblogic proxies from Sun One 6.1 to Apache 2.4
On Fri, Jul 1, 2016 at 12:49 AM, Joe Muller wrote: > > One interesting thing we did find on a packet capture on the back end > between the proxy server and the application server is that 3 seconds after > the proxy server apparently closed the port, the Weblogic application server > tried to send data. It almost like Weblogic did not realize the port was > closed. Very odd. Is the HTTP request fully sent (proxy) and responded (backend) when this happens? (I try to understand why a backend/application would send data on its own). Otherwise, on a general rule, did you take care that the TTL of proxy connection (to the backend) is lower than the KeepAliveTimeout configured on the backend? This can be done by using the ProxyPass/BalancerMember parameter ttl=... But before that, does disabling keepalive on the proxy help already? (ProxyPass' disablereuse=on or SetEnv proxy-nokeepalive) Regards, Yann. - To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org For additional commands, e-mail: users-h...@httpd.apache.org
Re: [users@httpd] Issues migrating Weblogic proxies from Sun One 6.1 to Apache 2.4
Hello Joe,
First of all, beginning with version 12.2.1, OHS is based on Apache
httpd 2.4.x.
But the Apache httpd form of the WLS plug-in should also be working for you.
I can try to help you in working with the Oracle support people.
Could you send directly to my email (to keep your information private)
the name of the person in Oracle support that you are working with and
the SR number they have assigned to you?
I will see if I can check on the status for you.
In the meantime, perhaps Rainer or someone else on this mailing list
will have further ideas from the Apache httpd point of view.
Thanks,
Mike
On 6/30/2016 3:49 PM, Joe Muller wrote:
One interesting thing we did find on a packet capture on the back end
between the proxy server and the application server is that 3 seconds after the
proxy server apparently closed the port, the Weblogic application server tried
to send data. It almost like Weblogic did not realize the port was closed.
Very odd.
At this point I may try implementing OHS and see if we have the same results. However it
is based on Apache 2.2, and I was hoping to take advantage of the improved performance
offered by Apache 2.4. Also reading through the documentation it looks like a PITA to
install (we have to install X to the run "Oracle Universal Installer" ?
Seriously ?) Maybe Oracle support will take us more seriously and give us better support
if we are using all their products.
-Joe
-Original Message-
From: Rainer Jung [mailto:rainer.j...@kippdata.de]
Sent: Saturday, June 25, 2016 4:45 AM
To: users@httpd.apache.org
Subject: Re: [users@httpd] Issues migrating Weblogic proxies from Sun One 6.1
to Apache 2.4
Am 24.06.2016 um 21:58 schrieb Joe Muller:
Just an update on this issue, if anybody is following. We have eliminated the
Load Balancer and the Firewall as a possible cause. Our last test was directly
between the IE client browser and the Apache 2.4 proxy server, resulting in the
same errors in the Apache logs similar to this:
*Exception type] [WRITE_ERROR_TO_CLIENT raised at line 560 of
BaseProxy.cpp, refer:
https://intgalf.xyz.com/ALFA/selectFileType.do?fileType=O1MM
We also tested using different browsers (IE, Fire Fox, Chrome, and had mixed
results, but eventually we saw the same errors from the Weblogic 12c plug-in
the Apache logs at some point.
So at this point it is down to the Apache proxy and/or the Oracle
Weblogic 12c Plug-in for Apache. Anybody have any ideas ? I am out
of them right now :-(
Perhaps it has something to do with the Apache 2.4 compilation options ? If I
had known before that going with Apache 2.4 instead of IPlanet would have been
this difficult we would have just purchased Oracle HTTP Server. At least we
would have full Oracle support through and through, although that may not be
saying much, since it is based on Apache 2.2. Also I am worried about
Oracle compatibility with 3rd party plug-ins like RSA Access Manager (SSO) and
Tea Leaf.
To be honest I am surprised Oracle doesn't give more guidance on this. I
would think we wouldn't be the first people to encounter this, but based on the
lack of information in their knowledge base and the response from their
technical support it seems otherwise.
I'd sniff the network in front of Apache and when the problem happens filter the raw
sniff packet dump file using the connection information from the error log line
("[client 10.165.254.1:28171]"). Then use the time stamp of the error message
and look at the sniff of the single connection what happens before the error is logged.
In case you are using https and you can switch on a reproduction system to http
this might help understanding the packet dump, but in general this approach
could also be used for https.
Regards,
Rainer
-
To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org
For additional commands, e-mail: users-h...@httpd.apache.org
RE: [users@httpd] Issues migrating Weblogic proxies from Sun One 6.1 to Apache 2.4
One interesting thing we did find on a packet capture on the back end between
the proxy server and the application server is that 3 seconds after the proxy
server apparently closed the port, the Weblogic application server tried to
send data. It almost like Weblogic did not realize the port was closed. Very
odd.
At this point I may try implementing OHS and see if we have the same results.
However it is based on Apache 2.2, and I was hoping to take advantage of the
improved performance offered by Apache 2.4. Also reading through the
documentation it looks like a PITA to install (we have to install X to the run
"Oracle Universal Installer" ? Seriously ?) Maybe Oracle support will take us
more seriously and give us better support if we are using all their products.
-Joe
-Original Message-
From: Rainer Jung [mailto:rainer.j...@kippdata.de]
Sent: Saturday, June 25, 2016 4:45 AM
To: users@httpd.apache.org
Subject: Re: [users@httpd] Issues migrating Weblogic proxies from Sun One 6.1
to Apache 2.4
Am 24.06.2016 um 21:58 schrieb Joe Muller:
>
> Just an update on this issue, if anybody is following. We have eliminated
> the Load Balancer and the Firewall as a possible cause. Our last test was
> directly between the IE client browser and the Apache 2.4 proxy server,
> resulting in the same errors in the Apache logs similar to this:
>
>>>*Exception type] [WRITE_ERROR_TO_CLIENT raised at line 560 of
>>> BaseProxy.cpp, refer:
>>> https://intgalf.xyz.com/ALFA/selectFileType.do?fileType=O1MM
>
> We also tested using different browsers (IE, Fire Fox, Chrome, and had
> mixed results, but eventually we saw the same errors from the Weblogic 12c
> plug-in the Apache logs at some point.
>
> So at this point it is down to the Apache proxy and/or the Oracle
> Weblogic 12c Plug-in for Apache. Anybody have any ideas ? I am out
> of them right now :-(
>
> Perhaps it has something to do with the Apache 2.4 compilation options ? If
> I had known before that going with Apache 2.4 instead of IPlanet would have
> been this difficult we would have just purchased Oracle HTTP Server. At
> least we would have full Oracle support through and through, although that
> may not be saying much, since it is based on Apache 2.2. Also I am
> worried about Oracle compatibility with 3rd party plug-ins like RSA Access
> Manager (SSO) and Tea Leaf.
>
> To be honest I am surprised Oracle doesn't give more guidance on this. I
> would think we wouldn't be the first people to encounter this, but based on
> the lack of information in their knowledge base and the response from their
> technical support it seems otherwise.
I'd sniff the network in front of Apache and when the problem happens filter
the raw sniff packet dump file using the connection information from the error
log line ("[client 10.165.254.1:28171]"). Then use the time stamp of the error
message and look at the sniff of the single connection what happens before the
error is logged.
In case you are using https and you can switch on a reproduction system to http
this might help understanding the packet dump, but in general this approach
could also be used for https.
Regards,
Rainer
> -Original Message-
> From: Mike Rumph [mailto:mike.ru...@oracle.com]
> Sent: Monday, June 20, 2016 4:08 PM
> To: users@httpd.apache.org
> Subject: Re: [users@httpd] Issues migrating Weblogic proxies from Sun
> One 6.1 to Apache 2.4
>
> Hello Joe,
>
> It seems to me that mod_reqtimeout applies to the amount of time a allowed
> for the server to receive the request from the client (Read from client).
>
> But your errors are indicating a problem on the Write to client.
> As I am understanding our WLS plugin developer, the problem seems to be that
> when the server has readied a response to send back to the client, the client
> has already dropped the connection.
> So in your topology this could be client browser, firewall or load balancer.
>
> Have you considered the email responses from Todd Simons and Daniel?
> The response from Daniel concerning the load balancer may be the most
> pertinent.
>
> Thanks,
>
> Mike
>
> On 6/20/2016 11:11 AM, Joe Muller wrote:
>> I checked our httpd.conf and we do have reqtimeout_module already loaded,
>> however there is nothing set. According to the Apache 2.4 documentation the
>> default values are:
>>
>> Default: header=20-40,MinRate=500 body=20,MinRate=500
>>
>> Wouldn't you think that should be high enough ? I know for a fact
>> that the data is not taking 20-40 seconds to post in these
>> applications, as the users are not waiting that long. They are only
>> seeing slowdowns of a
Re: [users@httpd] Issues migrating Weblogic proxies from Sun One 6.1 to Apache 2.4
Am 24.06.2016 um 21:58 schrieb Joe Muller:
Just an update on this issue, if anybody is following. We have eliminated the
Load Balancer and the Firewall as a possible cause. Our last test was directly
between the IE client browser and the Apache 2.4 proxy server, resulting in the
same errors in the Apache logs similar to this:
*Exception type] [WRITE_ERROR_TO_CLIENT raised at line 560 of
BaseProxy.cpp, refer:
https://intgalf.xyz.com/ALFA/selectFileType.do?fileType=O1MM
We also tested using different browsers (IE, Fire Fox, Chrome, and had mixed
results, but eventually we saw the same errors from the Weblogic 12c plug-in
the Apache logs at some point.
So at this point it is down to the Apache proxy and/or the Oracle Weblogic 12c
Plug-in for Apache. Anybody have any ideas ? I am out of them right now :-(
Perhaps it has something to do with the Apache 2.4 compilation options ? If I
had known before that going with Apache 2.4 instead of IPlanet would have been
this difficult we would have just purchased Oracle HTTP Server. At least we
would have full Oracle support through and through, although that may not be
saying much, since it is based on Apache 2.2. Also I am worried about
Oracle compatibility with 3rd party plug-ins like RSA Access Manager (SSO) and
Tea Leaf.
To be honest I am surprised Oracle doesn't give more guidance on this. I
would think we wouldn't be the first people to encounter this, but based on the
lack of information in their knowledge base and the response from their
technical support it seems otherwise.
I'd sniff the network in front of Apache and when the problem happens
filter the raw sniff packet dump file using the connection information
from the error log line ("[client 10.165.254.1:28171]"). Then use the
time stamp of the error message and look at the sniff of the single
connection what happens before the error is logged.
In case you are using https and you can switch on a reproduction system
to http this might help understanding the packet dump, but in general
this approach could also be used for https.
Regards,
Rainer
-Original Message-
From: Mike Rumph [mailto:mike.ru...@oracle.com]
Sent: Monday, June 20, 2016 4:08 PM
To: users@httpd.apache.org
Subject: Re: [users@httpd] Issues migrating Weblogic proxies from Sun One 6.1
to Apache 2.4
Hello Joe,
It seems to me that mod_reqtimeout applies to the amount of time a allowed for
the server to receive the request from the client (Read from client).
But your errors are indicating a problem on the Write to client.
As I am understanding our WLS plugin developer, the problem seems to be that
when the server has readied a response to send back to the client, the client
has already dropped the connection.
So in your topology this could be client browser, firewall or load balancer.
Have you considered the email responses from Todd Simons and Daniel?
The response from Daniel concerning the load balancer may be the most pertinent.
Thanks,
Mike
On 6/20/2016 11:11 AM, Joe Muller wrote:
I checked our httpd.conf and we do have reqtimeout_module already loaded,
however there is nothing set. According to the Apache 2.4 documentation the
default values are:
Default: header=20-40,MinRate=500 body=20,MinRate=500
Wouldn't you think that should be high enough ? I know for a fact
that the data is not taking 20-40 seconds to post in these
applications, as the users are not waiting that long. They are only
seeing slowdowns of a few seconds between pages (which in network time
is pretty long, ecspecially accessing the applications locally and not
coming in from over the internet.)
-Original Message-
From: Mike Rumph [mailto:mike.ru...@oracle.com]
Sent: Monday, June 20, 2016 10:45 AM
To: users@httpd.apache.org
Subject: Re: [users@httpd] Issues migrating Weblogic proxies from Sun
One 6.1 to Apache 2.4
Hello Joe,
I am not in a position to offer an official Oracle statement for your situation.
But I do work closely with the owners of the WLS plug-ins.
Here is an initial evaluation from one of the developers:
"WRITE_ERROR_TO_CLIENT is typically seen when there is an error
writing the response to the client (WLS plug-in client). This usually
occurs when the user sends a request, but closes the browser (or hits
a stop
button) before the response is received by the client. In such a scenario, from the
plug-in perspective, whenever response is received from WLS, it cannot relay it to
the client as the connection is broken, and it logs WRITE_ERROR_TO_CLIENT error.
This is usually a harmless error. If the above is not true (closing the browser
etc), then it may be possible that the client timeout is too low (or lower than the
WLS response time for the request). In such cases, the timeout needs to be
increased. I am not aware of what parameters to look out for here, but
mod_reqtimeout may be a good beginning."
I ho
RE: [users@httpd] Issues migrating Weblogic proxies from Sun One 6.1 to Apache 2.4
Just an update on this issue, if anybody is following. We have eliminated the Load Balancer and the Firewall as a possible cause. Our last test was directly between the IE client browser and the Apache 2.4 proxy server, resulting in the same errors in the Apache logs similar to this: >>*Exception type] [WRITE_ERROR_TO_CLIENT raised at line 560 of >> BaseProxy.cpp, refer: >> https://intgalf.xyz.com/ALFA/selectFileType.do?fileType=O1MM We also tested using different browsers (IE, Fire Fox, Chrome, and had mixed results, but eventually we saw the same errors from the Weblogic 12c plug-in the Apache logs at some point. So at this point it is down to the Apache proxy and/or the Oracle Weblogic 12c Plug-in for Apache. Anybody have any ideas ? I am out of them right now :-( Perhaps it has something to do with the Apache 2.4 compilation options ? If I had known before that going with Apache 2.4 instead of IPlanet would have been this difficult we would have just purchased Oracle HTTP Server. At least we would have full Oracle support through and through, although that may not be saying much, since it is based on Apache 2.2. Also I am worried about Oracle compatibility with 3rd party plug-ins like RSA Access Manager (SSO) and Tea Leaf. To be honest I am surprised Oracle doesn't give more guidance on this. I would think we wouldn't be the first people to encounter this, but based on the lack of information in their knowledge base and the response from their technical support it seems otherwise. Thanks, -Joe -Original Message- From: Mike Rumph [mailto:mike.ru...@oracle.com] Sent: Monday, June 20, 2016 4:08 PM To: users@httpd.apache.org Subject: Re: [users@httpd] Issues migrating Weblogic proxies from Sun One 6.1 to Apache 2.4 Hello Joe, It seems to me that mod_reqtimeout applies to the amount of time a allowed for the server to receive the request from the client (Read from client). But your errors are indicating a problem on the Write to client. As I am understanding our WLS plugin developer, the problem seems to be that when the server has readied a response to send back to the client, the client has already dropped the connection. So in your topology this could be client browser, firewall or load balancer. Have you considered the email responses from Todd Simons and Daniel? The response from Daniel concerning the load balancer may be the most pertinent. Thanks, Mike On 6/20/2016 11:11 AM, Joe Muller wrote: > I checked our httpd.conf and we do have reqtimeout_module already loaded, > however there is nothing set. According to the Apache 2.4 documentation the > default values are: > > Default: header=20-40,MinRate=500 body=20,MinRate=500 > > Wouldn't you think that should be high enough ? I know for a fact > that the data is not taking 20-40 seconds to post in these > applications, as the users are not waiting that long. They are only > seeing slowdowns of a few seconds between pages (which in network time > is pretty long, ecspecially accessing the applications locally and not > coming in from over the internet.) > > > -Original Message- > From: Mike Rumph [mailto:mike.ru...@oracle.com] > Sent: Monday, June 20, 2016 10:45 AM > To: users@httpd.apache.org > Subject: Re: [users@httpd] Issues migrating Weblogic proxies from Sun > One 6.1 to Apache 2.4 > > Hello Joe, > > I am not in a position to offer an official Oracle statement for your > situation. > But I do work closely with the owners of the WLS plug-ins. > > Here is an initial evaluation from one of the developers: > > "WRITE_ERROR_TO_CLIENT is typically seen when there is an error > writing the response to the client (WLS plug-in client). This usually > occurs when the user sends a request, but closes the browser (or hits > a stop > button) before the response is received by the client. In such a scenario, > from the plug-in perspective, whenever response is received from WLS, it > cannot relay it to the client as the connection is broken, and it logs > WRITE_ERROR_TO_CLIENT error. This is usually a harmless error. If the above > is not true (closing the browser etc), then it may be possible that the > client timeout is too low (or lower than the WLS response time for the > request). In such cases, the timeout needs to be increased. I am not aware of > what parameters to look out for here, but mod_reqtimeout may be a good > beginning." > > I hope that this is helpful to you. > For more specific details, you would still need to contact official Oracle > support channels. > > Thanks, > > Mike > > On 6/17/2016 7:30 AM, Joe Muller wrote: >> I am working on a project to migrate all our IPlanet 6.1 SP19 webserver >> proxies (formerly Sun One) to
RE: [users@httpd] Issues migrating Weblogic proxies from Sun One 6.1 to Apache 2.4
We did some testing hitting the Apache proxy server directly, bypassing the Load Balancer URL and Firewall and we are still seeing errors. There is still a firewall between the client browser and proxy server though. Not sure how we can eliminate that as a possible cause unless we actually get our user on the DMZ network to test. -Joe -Original Message- From: Mike Rumph [mailto:mike.ru...@oracle.com] Sent: Monday, June 20, 2016 4:08 PM To: users@httpd.apache.org Subject: Re: [users@httpd] Issues migrating Weblogic proxies from Sun One 6.1 to Apache 2.4 Hello Joe, It seems to me that mod_reqtimeout applies to the amount of time a allowed for the server to receive the request from the client (Read from client). But your errors are indicating a problem on the Write to client. As I am understanding our WLS plugin developer, the problem seems to be that when the server has readied a response to send back to the client, the client has already dropped the connection. So in your topology this could be client browser, firewall or load balancer. Have you considered the email responses from Todd Simons and Daniel? The response from Daniel concerning the load balancer may be the most pertinent. Thanks, Mike On 6/20/2016 11:11 AM, Joe Muller wrote: > I checked our httpd.conf and we do have reqtimeout_module already loaded, > however there is nothing set. According to the Apache 2.4 documentation the > default values are: > > Default: header=20-40,MinRate=500 body=20,MinRate=500 > > Wouldn't you think that should be high enough ? I know for a fact > that the data is not taking 20-40 seconds to post in these > applications, as the users are not waiting that long. They are only > seeing slowdowns of a few seconds between pages (which in network time > is pretty long, ecspecially accessing the applications locally and not > coming in from over the internet.) > > > -Original Message- > From: Mike Rumph [mailto:mike.ru...@oracle.com] > Sent: Monday, June 20, 2016 10:45 AM > To: users@httpd.apache.org > Subject: Re: [users@httpd] Issues migrating Weblogic proxies from Sun > One 6.1 to Apache 2.4 > > Hello Joe, > > I am not in a position to offer an official Oracle statement for your > situation. > But I do work closely with the owners of the WLS plug-ins. > > Here is an initial evaluation from one of the developers: > > "WRITE_ERROR_TO_CLIENT is typically seen when there is an error > writing the response to the client (WLS plug-in client). This usually > occurs when the user sends a request, but closes the browser (or hits > a stop > button) before the response is received by the client. In such a scenario, > from the plug-in perspective, whenever response is received from WLS, it > cannot relay it to the client as the connection is broken, and it logs > WRITE_ERROR_TO_CLIENT error. This is usually a harmless error. If the above > is not true (closing the browser etc), then it may be possible that the > client timeout is too low (or lower than the WLS response time for the > request). In such cases, the timeout needs to be increased. I am not aware of > what parameters to look out for here, but mod_reqtimeout may be a good > beginning." > > I hope that this is helpful to you. > For more specific details, you would still need to contact official Oracle > support channels. > > Thanks, > > Mike > > On 6/17/2016 7:30 AM, Joe Muller wrote: >> I am working on a project to migrate all our IPlanet 6.1 SP19 webserver >> proxies (formerly Sun One) to Apache 2.4, since IPlanet 6.1 does not support >> TLS 1.2 and IPlanet 7.0 is being EOL. Our backend application servers are >> Weblogic 9.2 / Weblogic 12c. The IPlanet proxies have performed FLAWLESSLY >> for over 10 years, despite the product being no longer supported and their >> WL Plug-in not officially supported with Weblogic 12c. >> >>However now that we are trying to use a more supported configuration >> (self-compiled Apache 2.4.18 running Weblogic Server Plugin 12.1.3) we are >> constantly seeing these errors, which results in performance degradation for >> our applications, and in some cases I think maybe even lost data. >> >> >>[Tue Jun 14 09:27:36.239682 2016] [weblogic:error] [pid 12513:tid >> 140185150932736] [client 10.165.254.1:28171] <1251314659108487> Write >> to the client failed: calling URL::close at line 559 of >> BaseProxy.cpp, >> referer: https://intgalf.xyz.com/ALFA/selectFileType.do?fileType=O1MM >> >>[Tue Jun 14 09:27:36.239747 2016] [weblogic:error] [pid 12513:tid >> 140185150932736] [client 10.165.254.1:28171] <1251314659108487> ** >>*Exception t
Re: [users@httpd] Issues migrating Weblogic proxies from Sun One 6.1 to Apache 2.4
Hello Joe, It seems to me that mod_reqtimeout applies to the amount of time a allowed for the server to receive the request from the client (Read from client). But your errors are indicating a problem on the Write to client. As I am understanding our WLS plugin developer, the problem seems to be that when the server has readied a response to send back to the client, the client has already dropped the connection. So in your topology this could be client browser, firewall or load balancer. Have you considered the email responses from Todd Simons and Daniel? The response from Daniel concerning the load balancer may be the most pertinent. Thanks, Mike On 6/20/2016 11:11 AM, Joe Muller wrote: I checked our httpd.conf and we do have reqtimeout_module already loaded, however there is nothing set. According to the Apache 2.4 documentation the default values are: Default: header=20-40,MinRate=500 body=20,MinRate=500 Wouldn't you think that should be high enough ? I know for a fact that the data is not taking 20-40 seconds to post in these applications, as the users are not waiting that long. They are only seeing slowdowns of a few seconds between pages (which in network time is pretty long, ecspecially accessing the applications locally and not coming in from over the internet.) -Original Message- From: Mike Rumph [mailto:mike.ru...@oracle.com] Sent: Monday, June 20, 2016 10:45 AM To: users@httpd.apache.org Subject: Re: [users@httpd] Issues migrating Weblogic proxies from Sun One 6.1 to Apache 2.4 Hello Joe, I am not in a position to offer an official Oracle statement for your situation. But I do work closely with the owners of the WLS plug-ins. Here is an initial evaluation from one of the developers: "WRITE_ERROR_TO_CLIENT is typically seen when there is an error writing the response to the client (WLS plug-in client). This usually occurs when the user sends a request, but closes the browser (or hits a stop button) before the response is received by the client. In such a scenario, from the plug-in perspective, whenever response is received from WLS, it cannot relay it to the client as the connection is broken, and it logs WRITE_ERROR_TO_CLIENT error. This is usually a harmless error. If the above is not true (closing the browser etc), then it may be possible that the client timeout is too low (or lower than the WLS response time for the request). In such cases, the timeout needs to be increased. I am not aware of what parameters to look out for here, but mod_reqtimeout may be a good beginning." I hope that this is helpful to you. For more specific details, you would still need to contact official Oracle support channels. Thanks, Mike On 6/17/2016 7:30 AM, Joe Muller wrote: I am working on a project to migrate all our IPlanet 6.1 SP19 webserver proxies (formerly Sun One) to Apache 2.4, since IPlanet 6.1 does not support TLS 1.2 and IPlanet 7.0 is being EOL. Our backend application servers are Weblogic 9.2 / Weblogic 12c. The IPlanet proxies have performed FLAWLESSLY for over 10 years, despite the product being no longer supported and their WL Plug-in not officially supported with Weblogic 12c. However now that we are trying to use a more supported configuration (self-compiled Apache 2.4.18 running Weblogic Server Plugin 12.1.3) we are constantly seeing these errors, which results in performance degradation for our applications, and in some cases I think maybe even lost data. [Tue Jun 14 09:27:36.239682 2016] [weblogic:error] [pid 12513:tid 140185150932736] [client 10.165.254.1:28171] <1251314659108487> Write to the client failed: calling URL::close at line 559 of BaseProxy.cpp, referer: https://intgalf.xyz.com/ALFA/selectFileType.do?fileType=O1MM [Tue Jun 14 09:27:36.239747 2016] [weblogic:error] [pid 12513:tid 140185150932736] [client 10.165.254.1:28171] <1251314659108487> ** *Exception type [WRITE_ERROR_TO_CLIENT] raised at line 560 of BaseProxy.cpp, referer: https://intgalf.xyz.com/ALFA/selectFileType.do?fileType=O1MM [Tue Jun 14 09:27:36.239952 2016] [weblogic:error] [pid 12513:tid 140185150932736] [client 10.165.254.1:28171] <1251314659108487> request [/ALFA/servlet/DecryptDownload?linkName=al_o1mm_carr20150630.csv] did NOT process successfully.., referer:https://intgalf.xyz.com/ALFA/selectFileType.do?fileType=O1MM Our topology is like this: Client Browser <--> Firewall <--> Load Balancer <--> Web Proxies <--> Firewall <--> Weblogic Application Servers Oracle support suggested as work around that we increase WLSocketsTimeOut in the plug-in, but I think that only masks the issue, as we still the errors. We did a network trace and it looks like the Apache plug-in is pre-maturely closing the connection to the WL server, but I can't be certain. We know that our firewall is not responsible. Any ideas ? I thought Ap
RE: [users@httpd] Issues migrating Weblogic proxies from Sun One 6.1 to Apache 2.4
I checked our httpd.conf and we do have reqtimeout_module already loaded, however there is nothing set. According to the Apache 2.4 documentation the default values are: Default: header=20-40,MinRate=500 body=20,MinRate=500 Wouldn't you think that should be high enough ? I know for a fact that the data is not taking 20-40 seconds to post in these applications, as the users are not waiting that long. They are only seeing slowdowns of a few seconds between pages (which in network time is pretty long, ecspecially accessing the applications locally and not coming in from over the internet.) -Original Message- From: Mike Rumph [mailto:mike.ru...@oracle.com] Sent: Monday, June 20, 2016 10:45 AM To: users@httpd.apache.org Subject: Re: [users@httpd] Issues migrating Weblogic proxies from Sun One 6.1 to Apache 2.4 Hello Joe, I am not in a position to offer an official Oracle statement for your situation. But I do work closely with the owners of the WLS plug-ins. Here is an initial evaluation from one of the developers: "WRITE_ERROR_TO_CLIENT is typically seen when there is an error writing the response to the client (WLS plug-in client). This usually occurs when the user sends a request, but closes the browser (or hits a stop button) before the response is received by the client. In such a scenario, from the plug-in perspective, whenever response is received from WLS, it cannot relay it to the client as the connection is broken, and it logs WRITE_ERROR_TO_CLIENT error. This is usually a harmless error. If the above is not true (closing the browser etc), then it may be possible that the client timeout is too low (or lower than the WLS response time for the request). In such cases, the timeout needs to be increased. I am not aware of what parameters to look out for here, but mod_reqtimeout may be a good beginning." I hope that this is helpful to you. For more specific details, you would still need to contact official Oracle support channels. Thanks, Mike On 6/17/2016 7:30 AM, Joe Muller wrote: > I am working on a project to migrate all our IPlanet 6.1 SP19 webserver > proxies (formerly Sun One) to Apache 2.4, since IPlanet 6.1 does not support > TLS 1.2 and IPlanet 7.0 is being EOL. Our backend application servers are > Weblogic 9.2 / Weblogic 12c. The IPlanet proxies have performed FLAWLESSLY > for over 10 years, despite the product being no longer supported and their WL > Plug-in not officially supported with Weblogic 12c. > > However now that we are trying to use a more supported configuration > (self-compiled Apache 2.4.18 running Weblogic Server Plugin 12.1.3) we are > constantly seeing these errors, which results in performance degradation for > our applications, and in some cases I think maybe even lost data. > > > [Tue Jun 14 09:27:36.239682 2016] [weblogic:error] [pid 12513:tid > 140185150932736] [client 10.165.254.1:28171] <1251314659108487> Write > to the client failed: calling URL::close at line 559 of BaseProxy.cpp, > referer: https://intgalf.xyz.com/ALFA/selectFileType.do?fileType=O1MM > > [Tue Jun 14 09:27:36.239747 2016] [weblogic:error] [pid 12513:tid > 140185150932736] [client 10.165.254.1:28171] <1251314659108487> ** > *Exception type [WRITE_ERROR_TO_CLIENT] raised at line 560 of > BaseProxy.cpp, referer: > https://intgalf.xyz.com/ALFA/selectFileType.do?fileType=O1MM > > [Tue Jun 14 09:27:36.239952 2016] [weblogic:error] [pid 12513:tid > 140185150932736] [client 10.165.254.1:28171] <1251314659108487> > request > [/ALFA/servlet/DecryptDownload?linkName=al_o1mm_carr20150630.csv] did > NOT process successfully.., > referer:https://intgalf.xyz.com/ALFA/selectFileType.do?fileType=O1MM > > > > Our topology is like this: > > Client Browser <--> Firewall <--> Load Balancer <--> Web Proxies > <--> Firewall <--> Weblogic Application Servers > > Oracle support suggested as work around that we increase WLSocketsTimeOut > in the plug-in, but I think that only masks the issue, as we still the errors. > > We did a network trace and it looks like the Apache plug-in is pre-maturely > closing the connection to the WL server, but I can't be certain. We know that > our firewall is not responsible. > > Any ideas ? I thought Apache would work better then Sun One, but this has > been the opposite. Is there some fundamental webserver tunable parameter that > is so different between out of the box Sun One and out of the box Apache that > could be causing this ? > > > > - > To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org > For additional commands
RE: [users@httpd] Issues migrating Weblogic proxies from Sun One 6.1 to Apache 2.4
Thanks for the response ! This is very informative. I am going to investigate this further. I do have a ticket open with Oracle Support, unfortunately he has not been that helpful yet. That is one of the reasons I decided to join this list. I am very impressed with the breadth of Apache knowledge out there, so I am hopeful the Apache collective can help me resolve this. -Joe -Original Message- From: Mike Rumph [mailto:mike.ru...@oracle.com] Sent: Monday, June 20, 2016 10:45 AM To: users@httpd.apache.org Subject: Re: [users@httpd] Issues migrating Weblogic proxies from Sun One 6.1 to Apache 2.4 Hello Joe, I am not in a position to offer an official Oracle statement for your situation. But I do work closely with the owners of the WLS plug-ins. Here is an initial evaluation from one of the developers: "WRITE_ERROR_TO_CLIENT is typically seen when there is an error writing the response to the client (WLS plug-in client). This usually occurs when the user sends a request, but closes the browser (or hits a stop button) before the response is received by the client. In such a scenario, from the plug-in perspective, whenever response is received from WLS, it cannot relay it to the client as the connection is broken, and it logs WRITE_ERROR_TO_CLIENT error. This is usually a harmless error. If the above is not true (closing the browser etc), then it may be possible that the client timeout is too low (or lower than the WLS response time for the request). In such cases, the timeout needs to be increased. I am not aware of what parameters to look out for here, but mod_reqtimeout may be a good beginning." I hope that this is helpful to you. For more specific details, you would still need to contact official Oracle support channels. Thanks, Mike On 6/17/2016 7:30 AM, Joe Muller wrote: > I am working on a project to migrate all our IPlanet 6.1 SP19 webserver > proxies (formerly Sun One) to Apache 2.4, since IPlanet 6.1 does not support > TLS 1.2 and IPlanet 7.0 is being EOL. Our backend application servers are > Weblogic 9.2 / Weblogic 12c. The IPlanet proxies have performed FLAWLESSLY > for over 10 years, despite the product being no longer supported and their WL > Plug-in not officially supported with Weblogic 12c. > > However now that we are trying to use a more supported configuration > (self-compiled Apache 2.4.18 running Weblogic Server Plugin 12.1.3) we are > constantly seeing these errors, which results in performance degradation for > our applications, and in some cases I think maybe even lost data. > > > [Tue Jun 14 09:27:36.239682 2016] [weblogic:error] [pid 12513:tid > 140185150932736] [client 10.165.254.1:28171] <1251314659108487> Write > to the client failed: calling URL::close at line 559 of BaseProxy.cpp, > referer: https://intgalf.xyz.com/ALFA/selectFileType.do?fileType=O1MM > > [Tue Jun 14 09:27:36.239747 2016] [weblogic:error] [pid 12513:tid > 140185150932736] [client 10.165.254.1:28171] <1251314659108487> ** > *Exception type [WRITE_ERROR_TO_CLIENT] raised at line 560 of > BaseProxy.cpp, referer: > https://intgalf.xyz.com/ALFA/selectFileType.do?fileType=O1MM > > [Tue Jun 14 09:27:36.239952 2016] [weblogic:error] [pid 12513:tid > 140185150932736] [client 10.165.254.1:28171] <1251314659108487> > request > [/ALFA/servlet/DecryptDownload?linkName=al_o1mm_carr20150630.csv] did > NOT process successfully.., > referer:https://intgalf.xyz.com/ALFA/selectFileType.do?fileType=O1MM > > > > Our topology is like this: > > Client Browser <--> Firewall <--> Load Balancer <--> Web Proxies > <--> Firewall <--> Weblogic Application Servers > > Oracle support suggested as work around that we increase WLSocketsTimeOut > in the plug-in, but I think that only masks the issue, as we still the errors. > > We did a network trace and it looks like the Apache plug-in is pre-maturely > closing the connection to the WL server, but I can't be certain. We know that > our firewall is not responsible. > > Any ideas ? I thought Apache would work better then Sun One, but this has > been the opposite. Is there some fundamental webserver tunable parameter that > is so different between out of the box Sun One and out of the box Apache that > could be causing this ? > > > > - > To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org > For additional commands, e-mail: users-h...@httpd.apache.org > > - To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org For additional commands, e-mail: users-h...@httpd.apache.org - To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org For additional commands, e-mail: users-h...@httpd.apache.org
Re: [users@httpd] Issues migrating Weblogic proxies from Sun One 6.1 to Apache 2.4
I have experienced the same issue two times, both scenarios had a loadbalancer in front of apache while the same scenario in pre-producttion without load-balancing didn't yield the same problem. All cases involved a POST response instead of the tipical GET. I would check if the problem occurs in these situations to discard the possible cause: * With one apache down so Balancer always sends to the same server. (Also check which kind of persistance is set in the balancer). * Same request without balancer on top. * Set WLProxyPassThrough to ON and see if there is any difference with previous two points. * We also had a case in which the module version was old and needed FileCaching set to OFF. Good luck 2016-06-20 16:44 GMT+02:00 Mike Rumph : > Hello Joe, > > I am not in a position to offer an official Oracle statement for your > situation. > But I do work closely with the owners of the WLS plug-ins. > > Here is an initial evaluation from one of the developers: > > "WRITE_ERROR_TO_CLIENT is typically seen when there is an error writing > the response to the client (WLS plug-in client). This usually occurs when > the user sends a request, but closes the browser (or hits a stop button) > before the response is received by the client. In such a scenario, from the > plug-in perspective, whenever response is received from WLS, it cannot > relay it to the client as the connection is broken, and it logs > WRITE_ERROR_TO_CLIENT error. This is usually a harmless error. If the above > is not true (closing the browser etc), then it may be possible that the > client timeout is too low (or lower than the WLS response time for the > request). In such cases, the timeout needs to be increased. I am not aware > of what parameters to look out for here, but mod_reqtimeout may be a good > beginning." > > I hope that this is helpful to you. > For more specific details, you would still need to contact official Oracle > support channels. > > Thanks, > > Mike > > > On 6/17/2016 7:30 AM, Joe Muller wrote: > >> I am working on a project to migrate all our IPlanet 6.1 SP19 webserver >> proxies (formerly Sun One) to Apache 2.4, since IPlanet 6.1 does not >> support TLS 1.2 and IPlanet 7.0 is being EOL. Our backend application >> servers are Weblogic 9.2 / Weblogic 12c. The IPlanet proxies have performed >> FLAWLESSLY for over 10 years, despite the product being no longer supported >> and their WL Plug-in not officially supported with Weblogic 12c. >> >> However now that we are trying to use a more supported configuration >> (self-compiled Apache 2.4.18 running Weblogic Server Plugin 12.1.3) we are >> constantly seeing these errors, which results in performance degradation >> for our applications, and in some cases I think maybe even lost data. >> >> >> [Tue Jun 14 09:27:36.239682 2016] [weblogic:error] [pid 12513:tid >> 140185150932736] [client 10.165.254.1:28171] <1251314659108487> Write to >> the client failed: calling URL::close at line 559 of BaseProxy.cpp, >> referer: https://intgalf.xyz.com/ALFA/selectFileType.do?fileType=O1MM >> >> [Tue Jun 14 09:27:36.239747 2016] [weblogic:error] [pid 12513:tid >> 140185150932736] [client 10.165.254.1:28171] <1251314659108487> ** >> *Exception type [WRITE_ERROR_TO_CLIENT] raised at line 560 of >> BaseProxy.cpp, referer: >> https://intgalf.xyz.com/ALFA/selectFileType.do?fileType=O1MM >> >> [Tue Jun 14 09:27:36.239952 2016] [weblogic:error] [pid 12513:tid >> 140185150932736] [client 10.165.254.1:28171] <1251314659108487> request >> [/ALFA/servlet/DecryptDownload?linkName=al_o1mm_carr20150630.csv] did NOT >> process successfully.., referer: >> https://intgalf.xyz.com/ALFA/selectFileType.do?fileType=O1MM >> >> >> >> Our topology is like this: >> >> Client Browser <--> Firewall <--> Load Balancer <--> Web Proxies <--> >> Firewall <--> Weblogic Application Servers >> >> Oracle support suggested as work around that we increase >> WLSocketsTimeOut in the plug-in, but I think that only masks the issue, as >> we still the errors. >> >> We did a network trace and it looks like the Apache plug-in is >> pre-maturely closing the connection to the WL server, but I can't be >> certain. We know that our firewall is not responsible. >> >> Any ideas ? I thought Apache would work better then Sun One, but this >> has been the opposite. Is there some fundamental webserver tunable >> parameter that is so different between out of the box Sun One and out of >> the box Apache that could be causing this ? >> >> >> >> - >> To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org >> For additional commands, e-mail: users-h...@httpd.apache.org >> >> >> > > - > To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org > For additional commands, e-mail: users-h...@httpd.apache.org > > -- *Daniel Ferradal* IT Specialist email dferrada
RE: [users@httpd] Issues migrating Weblogic proxies from Sun One 6.1 to Apache 2.4
You may need to tune the socket timeout on the Linux kernel, and work with your firewall admin as well to make sure those timeouts match with each other. ___ Todd Simons Director of Information Technology tsim...@delphi-tech.com Delphi Technology, Inc. T: +1-732-353-3570 -Original Message- From: Mike Rumph [mailto:mike.ru...@oracle.com] Sent: Monday, June 20, 2016 10:45 To: users@httpd.apache.org Subject: Re: [users@httpd] Issues migrating Weblogic proxies from Sun One 6.1 to Apache 2.4 Hello Joe, I am not in a position to offer an official Oracle statement for your situation. But I do work closely with the owners of the WLS plug-ins. Here is an initial evaluation from one of the developers: "WRITE_ERROR_TO_CLIENT is typically seen when there is an error writing the response to the client (WLS plug-in client). This usually occurs when the user sends a request, but closes the browser (or hits a stop button) before the response is received by the client. In such a scenario, from the plug-in perspective, whenever response is received from WLS, it cannot relay it to the client as the connection is broken, and it logs WRITE_ERROR_TO_CLIENT error. This is usually a harmless error. If the above is not true (closing the browser etc), then it may be possible that the client timeout is too low (or lower than the WLS response time for the request). In such cases, the timeout needs to be increased. I am not aware of what parameters to look out for here, but mod_reqtimeout may be a good beginning." I hope that this is helpful to you. For more specific details, you would still need to contact official Oracle support channels. Thanks, Mike On 6/17/2016 7:30 AM, Joe Muller wrote: > I am working on a project to migrate all our IPlanet 6.1 SP19 webserver > proxies (formerly Sun One) to Apache 2.4, since IPlanet 6.1 does not support > TLS 1.2 and IPlanet 7.0 is being EOL. Our backend application servers are > Weblogic 9.2 / Weblogic 12c. The IPlanet proxies have performed FLAWLESSLY > for over 10 years, despite the product being no longer supported and their WL > Plug-in not officially supported with Weblogic 12c. > > However now that we are trying to use a more supported configuration > (self-compiled Apache 2.4.18 running Weblogic Server Plugin 12.1.3) we are > constantly seeing these errors, which results in performance degradation for > our applications, and in some cases I think maybe even lost data. > > > [Tue Jun 14 09:27:36.239682 2016] [weblogic:error] [pid 12513:tid > 140185150932736] [client 10.165.254.1:28171] <1251314659108487> Write to the > client failed: calling URL::close at line 559 of BaseProxy.cpp, referer: > https://intgalf.xyz.com/ALFA/selectFileType.do?fileType=O1MM > > [Tue Jun 14 09:27:36.239747 2016] [weblogic:error] [pid 12513:tid > 140185150932736] [client 10.165.254.1:28171] <1251314659108487> ** > *Exception type [WRITE_ERROR_TO_CLIENT] raised at line 560 of > BaseProxy.cpp, referer: > https://intgalf.xyz.com/ALFA/selectFileType.do?fileType=O1MM > > [Tue Jun 14 09:27:36.239952 2016] [weblogic:error] [pid 12513:tid > 140185150932736] [client 10.165.254.1:28171] <1251314659108487> request > [/ALFA/servlet/DecryptDownload?linkName=al_o1mm_carr20150630.csv] did NOT > process successfully.., > referer:https://intgalf.xyz.com/ALFA/selectFileType.do?fileType=O1MM > > > > Our topology is like this: > > Client Browser <--> Firewall <--> Load Balancer <--> Web Proxies <--> > Firewall <--> Weblogic Application Servers > > Oracle support suggested as work around that we increase WLSocketsTimeOut > in the plug-in, but I think that only masks the issue, as we still the errors. > > We did a network trace and it looks like the Apache plug-in is pre-maturely > closing the connection to the WL server, but I can't be certain. We know that > our firewall is not responsible. > > Any ideas ? I thought Apache would work better then Sun One, but this has > been the opposite. Is there some fundamental webserver tunable parameter that > is so different between out of the box Sun One and out of the box Apache that > could be causing this ? > > > > - > To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org > For additional commands, e-mail: users-h...@httpd.apache.org > > - To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org For additional commands, e-mail: users-h...@httpd.apache.org CONFIDENTIALITY NOTICE This e-mail message from Delphi Technology, Inc. is intended only for the individual or entity to which it is add
Re: [users@httpd] Issues migrating Weblogic proxies from Sun One 6.1 to Apache 2.4
Hello Joe, I am not in a position to offer an official Oracle statement for your situation. But I do work closely with the owners of the WLS plug-ins. Here is an initial evaluation from one of the developers: "WRITE_ERROR_TO_CLIENT is typically seen when there is an error writing the response to the client (WLS plug-in client). This usually occurs when the user sends a request, but closes the browser (or hits a stop button) before the response is received by the client. In such a scenario, from the plug-in perspective, whenever response is received from WLS, it cannot relay it to the client as the connection is broken, and it logs WRITE_ERROR_TO_CLIENT error. This is usually a harmless error. If the above is not true (closing the browser etc), then it may be possible that the client timeout is too low (or lower than the WLS response time for the request). In such cases, the timeout needs to be increased. I am not aware of what parameters to look out for here, but mod_reqtimeout may be a good beginning." I hope that this is helpful to you. For more specific details, you would still need to contact official Oracle support channels. Thanks, Mike On 6/17/2016 7:30 AM, Joe Muller wrote: I am working on a project to migrate all our IPlanet 6.1 SP19 webserver proxies (formerly Sun One) to Apache 2.4, since IPlanet 6.1 does not support TLS 1.2 and IPlanet 7.0 is being EOL. Our backend application servers are Weblogic 9.2 / Weblogic 12c. The IPlanet proxies have performed FLAWLESSLY for over 10 years, despite the product being no longer supported and their WL Plug-in not officially supported with Weblogic 12c. However now that we are trying to use a more supported configuration (self-compiled Apache 2.4.18 running Weblogic Server Plugin 12.1.3) we are constantly seeing these errors, which results in performance degradation for our applications, and in some cases I think maybe even lost data. [Tue Jun 14 09:27:36.239682 2016] [weblogic:error] [pid 12513:tid 140185150932736] [client 10.165.254.1:28171] <1251314659108487> Write to the client failed: calling URL::close at line 559 of BaseProxy.cpp, referer: https://intgalf.xyz.com/ALFA/selectFileType.do?fileType=O1MM [Tue Jun 14 09:27:36.239747 2016] [weblogic:error] [pid 12513:tid 140185150932736] [client 10.165.254.1:28171] <1251314659108487> ** *Exception type [WRITE_ERROR_TO_CLIENT] raised at line 560 of BaseProxy.cpp, referer: https://intgalf.xyz.com/ALFA/selectFileType.do?fileType=O1MM [Tue Jun 14 09:27:36.239952 2016] [weblogic:error] [pid 12513:tid 140185150932736] [client 10.165.254.1:28171] <1251314659108487> request [/ALFA/servlet/DecryptDownload?linkName=al_o1mm_carr20150630.csv] did NOT process successfully.., referer:https://intgalf.xyz.com/ALFA/selectFileType.do?fileType=O1MM Our topology is like this: Client Browser <--> Firewall <--> Load Balancer <--> Web Proxies <--> Firewall <--> Weblogic Application Servers Oracle support suggested as work around that we increase WLSocketsTimeOut in the plug-in, but I think that only masks the issue, as we still the errors. We did a network trace and it looks like the Apache plug-in is pre-maturely closing the connection to the WL server, but I can't be certain. We know that our firewall is not responsible. Any ideas ? I thought Apache would work better then Sun One, but this has been the opposite. Is there some fundamental webserver tunable parameter that is so different between out of the box Sun One and out of the box Apache that could be causing this ? - To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org For additional commands, e-mail: users-h...@httpd.apache.org - To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org For additional commands, e-mail: users-h...@httpd.apache.org
Re: [users@httpd] Issues migrating Weblogic proxies from Sun One 6.1 to Apache 2.4
How are you connecting between the web-proxies and web-logic application servers? Having a firewall in place can be an issue - the firewall may drop idle connections silently (we see this with oracle, mod_jk/ajp/memcache and in some instances cached mysql connections; unfortunately neither end know the connection has been dropped and they still send packets down the broken connection.. - so any attempt to connect just hangs even doing a database ping! We have dropped mod_jk in favour of using mod_proxy/mod_proxy_http as this doesn't have the same problem (but is slightly less efficietnt) You can have some success with playing the the tcp keep alive settings: echo 600 > /proc/sys/net/ipv4/tcp_keepalive_time echo 60 > /proc/sys/net/ipv4/tcp_keepalive_intvl echo 10 > /proc/sys/net/ipv4/tcp_keepalive_probes But even these don't always seem to work - our more robust applications keep a track of when the connection was last used and will not re-connect to a connection which hasn't been used for 15 minutes (using mod_perl this can happen!) On 17/06/2016 15:30, Joe Muller wrote: I am working on a project to migrate all our IPlanet 6.1 SP19 webserver proxies (formerly Sun One) to Apache 2.4, since IPlanet 6.1 does not support TLS 1.2 and IPlanet 7.0 is being EOL. Our backend application servers are Weblogic 9.2 / Weblogic 12c. The IPlanet proxies have performed FLAWLESSLY for over 10 years, despite the product being no longer supported and their WL Plug-in not officially supported with Weblogic 12c. However now that we are trying to use a more supported configuration (self-compiled Apache 2.4.18 running Weblogic Server Plugin 12.1.3) we are constantly seeing these errors, which results in performance degradation for our applications, and in some cases I think maybe even lost data. [Tue Jun 14 09:27:36.239682 2016] [weblogic:error] [pid 12513:tid 140185150932736] [client 10.165.254.1:28171] <1251314659108487> Write to the client failed: calling URL::close at line 559 of BaseProxy.cpp, referer: https://intgalf.xyz.com/ALFA/selectFileType.do?fileType=O1MM [Tue Jun 14 09:27:36.239747 2016] [weblogic:error] [pid 12513:tid 140185150932736] [client 10.165.254.1:28171] <1251314659108487> ** *Exception type [WRITE_ERROR_TO_CLIENT] raised at line 560 of BaseProxy.cpp, referer: https://intgalf.xyz.com/ALFA/selectFileType.do?fileType=O1MM [Tue Jun 14 09:27:36.239952 2016] [weblogic:error] [pid 12513:tid 140185150932736] [client 10.165.254.1:28171] <1251314659108487> request [/ALFA/servlet/DecryptDownload?linkName=al_o1mm_carr20150630.csv] did NOT process successfully.., referer:https://intgalf.xyz.com/ALFA/selectFileType.do?fileType=O1MM Our topology is like this: Client Browser <--> Firewall <--> Load Balancer <--> Web Proxies <--> Firewall <--> Weblogic Application Servers Oracle support suggested as work around that we increase WLSocketsTimeOut in the plug-in, but I think that only masks the issue, as we still the errors. We did a network trace and it looks like the Apache plug-in is pre-maturely closing the connection to the WL server, but I can't be certain. We know that our firewall is not responsible. Any ideas ? I thought Apache would work better then Sun One, but this has been the opposite. Is there some fundamental webserver tunable parameter that is so different between out of the box Sun One and out of the box Apache that could be causing this ? - To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org For additional commands, e-mail: users-h...@httpd.apache.org -- The Wellcome Trust Sanger Institute is operated by Genome Research Limited, a charity registered in England with number 1021457 and a company registered in England with number 2742969, whose registered office is 215 Euston Road, London, NW1 2BE. - To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org For additional commands, e-mail: users-h...@httpd.apache.org
