[users@httpd] Issue while generating large documents

2019-08-22 Thread Santosh Kondapuram 
Hi All,

We are running in to issue while generating the large documents from our Java 
application. The Application is deployed in WebLogic server 12.2.1.3.0 version
Apache (2.4.39) is proxying the Backend weblogic servers via WLS Plugin and an 
Load Balancer is sitting in front of Apache servers. It's an clustered 
environment with 3 APP servers and 2 web servers.
When we are generating an larger document (invoice)which contains more than 150 
+ pages then the session is getting invalidate and below are the errors 
recorded in the logs files.
Please note that when we are generating the same document with the direct 
application URL we are not seeing any issue. So I suspect there is something 
timing out between web(WLS Plugin) and app server.
Any suggestions please. Also we recently hit the following 
bug
  for another application for which we have took the work around by disabling 
the mod_reqtimeout module. Tried same for this issue as well but that did not 
help.

Web server log :

[Thu Aug 22 01:50:49.613519 2019] [weblogic:error] [pid 15791:tid 
140550548170496] [client 192.168.72.3:46983] <15791156646356926> Write to the 
client failed: calling URL::close at line 587 of BaseProxy.cpp, referer: 
https://v3.ufcwtrust.com/v3prod/app?service=external/Documents:CreateDocumentPopup&sp=SPAGE&sp=SContributions%3ATransactions&sp=l13443&sp=l7017&sp=S10184813
[Thu Aug 22 01:50:49.613641 2019] [weblogic:error] [pid 15791:tid 
140550548170496] [client 192.168.72.3:46983] <15791156646356926> 
***Exception type [WRITE_ERROR_TO_CLIENT] raised at line 588 of 
BaseProxy.cpp, referer: 
https://xyz/v3prod/app?service=external/Documents:CreateDocumentPopup&sp=SPAGE&sp=SContributions%3ATransactions&sp=l13443&sp=l7017&sp=S10184813
[Thu Aug 22 01:50:49.613892 2019] [weblogic:error] [pid 15791:tid 
140550548170496] [client 192.168.72.3:46983] ap_proxy: trying POST /v3prod/app 
at backend host 10.72.72.5/7003, client 192.168.72.3/46983, total tries 1; got 
exception 'WRITE_ERROR_TO_CLIENT [os error=0,  line 588 of BaseProxy.cpp]: '; 
state: writing response body to client; not failing over, referer: 
https://xyz/v3prod/app?service=external/Documents:CreateDocumentPopup&sp=SPAGE&sp=SContributions%3ATransactions&sp=l13443&sp=l7017&sp=S10184813
[Thu Aug 22 01:50:49.614073 2019] [weblogic:error] [pid 15791:tid 
140550548170496] [client 192.168.72.3:46983] <15791156646356926> request 
[/v3prod/app] did NOT process successfully.., referer: 
https://xyz/v3prod/app?service=external/Documents:CreateDocumentPopup&sp=SPAGE&sp=SContributions%3ATransactions&sp=l13443&sp=l7017&sp=S10184813
[Thu Aug 22 01:52:40.609230 2019] [core:warn] [pid 15788:tid 140550969862112] 
AH00045: child process 15874 still did not exit, sending a SIGTERM
[Thu Aug 22 01:52:42.611458 2019] [core:warn] [pid 15788:tid 140550969862112] 
AH00045: child process 15874 still did not exit, sending a SIGTERM

App Server Log :





**


Exception during post-request cleanup.


  Session id: 
kwu4gBsqTRK188S_h79LFZ-Abn2CeYya1gRJ9NpYRibKXNUa-he9!137202692!1566463499050
  Client address: 192.168.72.3

Exceptions:

java.io.IOException: Broken pipe
sun.nio.ch.FileDispatcherImpl.write0(Native Method)
sun.nio.ch.SocketDispatcher.write(SocketDispatcher.java:47)
sun.nio.ch.IOUtil.writeFromNativeBuffer(IOUtil.java:93)
sun.nio.ch.IOUtil.write(IOUtil.java:65)
sun.nio.ch.SocketChannelImpl.write(SocketChannelImpl.java:471)
java.nio.channels.Channels.writeFullyImpl(Channels.java:78)
java.nio.channels.Channels.writeFully(Channels.java:98)
java.nio.channels.Channels.access$000(Channels.java:61)
java.nio.channels.Channels$1.write(Channels.java:174)
weblogic.socket.JSSEFilterImpl.writeToNetwork(JSSEFilterImpl.java:829)
weblogic.socket.JSSEFilterImpl.wrapAndWrite(JSSEFilterImpl.java:789)
weblogic.socket.JSSEFilterImpl.write(JSSEFilterImpl.java:503)
weblogic.socket.JSSESocket$JSSEOutputStream.write(JSSESocket.java:148)
weblogic.servlet.internal.ChunkOutput.writeChunkTransfer(ChunkOutput.java:625)
weblogic.servlet.internal.ChunkOutput.writeChunks(ChunkOutput.java:587)
weblogic.servlet.internal.ChunkOutput.flush(ChunkOutput.java:471)
weblogic.servlet.internal.CharsetChunkOutput.flush(CharsetChunkOutput.java:318)
weblogic.servlet.internal.ChunkOutputWrapper.flush(ChunkOutputWrapper.java:207)
weblogic.servlet.internal.ServletOutputStreamImpl.flush(ServletOutputStreamImpl.java:153)
org.apache.tapestry.request.ResponseOutputStream.forceFlush(ResponseOutputStream.java:149)
org.apache.tapestry.engine.AbstractEngine.service(AbstractEngine.java:940)
org.apache.tapestry.ApplicationServlet.doService(ApplicationServlet.java:197)
com.vitechinc.core.VitechApplicationServlet.doService(VitechApplicationServlet.java:321)
org.apache.tapestry.ApplicationServlet.doPost(ApplicationServlet.java:326)
javax.servlet

[users@httpd] RE: Issue while generating large documents

2019-08-23 Thread Santosh Kondapuram 
Anybody has any inputs on this please

Thanks,
Santosh.

From: Santosh Kondapuram
Sent: Thursday, August 22, 2019 1:04 PM
To: users@httpd.apache.org
Subject: Issue while generating large documents

Hi All,

We are running in to issue while generating the large documents from our Java 
application. The Application is deployed in WebLogic server 12.2.1.3.0 version
Apache (2.4.39) is proxying the Backend weblogic servers via WLS Plugin and an 
Load Balancer is sitting in front of Apache servers. It's an clustered 
environment with 3 APP servers and 2 web servers.
When we are generating an larger document (invoice)which contains more than 150 
+ pages then the session is getting invalidate and below are the errors 
recorded in the logs files.
Please note that when we are generating the same document with the direct 
application URL we are not seeing any issue. So I suspect there is something 
timing out between web(WLS Plugin) and app server.
Any suggestions please. Also we recently hit the following 
bug<http://mail-archives.apache.org/mod_mbox/httpd-users/201908.mbox/%3c8e6e5316-2c22-9221-83fe-8177022ed...@kippdata.de%3E>
  for another application for which we have took the work around by disabling 
the mod_reqtimeout module. Tried same for this issue as well but that did not 
help.

Web server log :

[Thu Aug 22 01:50:49.613519 2019] [weblogic:error] [pid 15791:tid 
140550548170496] [client 192.168.72.3:46983] <15791156646356926> Write to the 
client failed: calling URL::close at line 587 of BaseProxy.cpp, referer: 
https://v3.ufcwtrust.com/v3prod/app?service=external/Documents:CreateDocumentPopup&sp=SPAGE&sp=SContributions%3ATransactions&sp=l13443&sp=l7017&sp=S10184813
[Thu Aug 22 01:50:49.613641 2019] [weblogic:error] [pid 15791:tid 
140550548170496] [client 192.168.72.3:46983] <15791156646356926> 
***Exception type [WRITE_ERROR_TO_CLIENT] raised at line 588 of 
BaseProxy.cpp, referer: 
https://xyz/v3prod/app?service=external/Documents:CreateDocumentPopup&sp=SPAGE&sp=SContributions%3ATransactions&sp=l13443&sp=l7017&sp=S10184813
[Thu Aug 22 01:50:49.613892 2019] [weblogic:error] [pid 15791:tid 
140550548170496] [client 192.168.72.3:46983] ap_proxy: trying POST /v3prod/app 
at backend host 10.72.72.5/7003, client 192.168.72.3/46983, total tries 1; got 
exception 'WRITE_ERROR_TO_CLIENT [os error=0,  line 588 of BaseProxy.cpp]: '; 
state: writing response body to client; not failing over, referer: 
https://xyz/v3prod/app?service=external/Documents:CreateDocumentPopup&sp=SPAGE&sp=SContributions%3ATransactions&sp=l13443&sp=l7017&sp=S10184813
[Thu Aug 22 01:50:49.614073 2019] [weblogic:error] [pid 15791:tid 
140550548170496] [client 192.168.72.3:46983] <15791156646356926> request 
[/v3prod/app] did NOT process successfully.., referer: 
https://xyz/v3prod/app?service=external/Documents:CreateDocumentPopup&sp=SPAGE&sp=SContributions%3ATransactions&sp=l13443&sp=l7017&sp=S10184813
[Thu Aug 22 01:52:40.609230 2019] [core:warn] [pid 15788:tid 140550969862112] 
AH00045: child process 15874 still did not exit, sending a SIGTERM
[Thu Aug 22 01:52:42.611458 2019] [core:warn] [pid 15788:tid 140550969862112] 
AH00045: child process 15874 still did not exit, sending a SIGTERM

App Server Log :





**


Exception during post-request cleanup.


  Session id: 
kwu4gBsqTRK188S_h79LFZ-Abn2CeYya1gRJ9NpYRibKXNUa-he9!137202692!1566463499050
  Client address: 192.168.72.3

Exceptions:

java.io.IOException: Broken pipe
sun.nio.ch.FileDispatcherImpl.write0(Native Method)
sun.nio.ch.SocketDispatcher.write(SocketDispatcher.java:47)
sun.nio.ch.IOUtil.writeFromNativeBuffer(IOUtil.java:93)
sun.nio.ch.IOUtil.write(IOUtil.java:65)
sun.nio.ch.SocketChannelImpl.write(SocketChannelImpl.java:471)
java.nio.channels.Channels.writeFullyImpl(Channels.java:78)
java.nio.channels.Channels.writeFully(Channels.java:98)
java.nio.channels.Channels.access$000(Channels.java:61)
java.nio.channels.Channels$1.write(Channels.java:174)
weblogic.socket.JSSEFilterImpl.writeToNetwork(JSSEFilterImpl.java:829)
weblogic.socket.JSSEFilterImpl.wrapAndWrite(JSSEFilterImpl.java:789)
weblogic.socket.JSSEFilterImpl.write(JSSEFilterImpl.java:503)
weblogic.socket.JSSESocket$JSSEOutputStream.write(JSSESocket.java:148)
weblogic.servlet.internal.ChunkOutput.writeChunkTransfer(ChunkOutput.java:625)
weblogic.servlet.internal.ChunkOutput.writeChunks(ChunkOutput.java:587)
weblogic.servlet.internal.ChunkOutput.flush(ChunkOutput.java:471)
weblogic.servlet.internal.CharsetChunkOutput.flush(CharsetChunkOutput.java:318)
weblogic.servlet.internal.ChunkOutputWrapper.flush(ChunkOutputWrapper.java:207)
weblogic.servlet.internal.ServletOutputStreamImpl.flush(ServletOutputStreamImpl.java:153)
org.apache.tapestry.request.ResponseOutputStream.forceFlush(ResponseOutputStream.java:149)
org.

[users@httpd] RE: [EXT] [users@httpd] Apache 2.4.25 (Debian Stretch 9.11) reverse proxy load balancing

2019-09-13 Thread Santosh Kondapuram 
Can you try adding the following Apache directive setting it to none:  
SSLProxyVerify none

Thanks,
Santosh.

-Original Message-
From: Antony Stone  
Sent: Friday, September 13, 2019 6:15 PM
To: users@httpd.apache.org
Subject: [EXT] [users@httpd] Apache 2.4.25 (Debian Stretch 9.11) reverse proxy 
load balancing

Hi.

I am trying to set up reverse proxy load balancing using Apache.

I've read https://httpd.apache.org/docs/2.4/howto/reverse_proxy.html and 
https://httpd.apache.org/docs/current/mod/mod_proxy_balancer.html and 
https://httpd.apache.org/docs/2.4/mod/mod_proxy_hcheck.html

What I want to achieve is:

HTTPS connection to my load balancer (which has an appropriate SSL certificate 
for its own URL) forwarding requests on to (currently two) HTTPS back-end 
servers (each of which also has an appropriate SSL certificate for its distinct 
URL).

I can get things working fine if I use HTTP for the "proxy to backend"
connection.

As soon as I use HTTPS, I get "All workers are in error state".

Here is my (sanitised) configuration:


ProxyHCExpr ok200 {%{REQUEST_STATUS} =~ /^200/}


BalancerMember https://first.server.net route=first.server.net hcmethod=GET 
hcuri=/isalive hcexpr=ok200 hcinterval=10
BalancerMember https://second.server.net route=second.server.net 
hcmethod=GET hcuri=/isalive hcexpr=ok200 hcinterval=10
ProxySet lbmethod=bytraffic



ServerName url.mydomain.net
SSLEngine On
SSLProxyEngine On
SSLCertificateFile /etc/url.mydomain.net.crt
SSLCertificateKeyFile /etc/url.mydomain.net.key
ProxyPass / balancer://url.mydomain.net/
ProxyPassReverse / balancer://url.mydomain.net/ 



What happens is that every 10 seconds I get the following entries in
/var/log/apache2/error.log:

[Fri Sep 13 02:50:07.600652 2019] [ssl:error] [pid 8628:tid 140240740148992] 
[remote 203.0.113.223:443] AH01961: SSL Proxy requested for
my.local.host.name:80 but not enabled [Hint: SSLProxyEngine] [Fri Sep 13 
02:50:07.600703 2019] [proxy:error] [pid 8628:tid 140240740148992]
AH00961: HCOH: failed to enable ssl support for 203.0.13.223:443
(first.server.net)

Plus the same thing for second.server.net

Now, I can see the "Hint: SSLProxyEngine", but I already have that in my 
VirtualHost definition, so I don't know what this hint is trying to hint at.

What I also do not understand is the "SSL Proxy requested for 
my.local.host.name:80" part.  I have completely disabled port 80 on this 
machine.  Apache is not listening on port 80, I do not need to use standard 
HTTP, and a packet capture shows that nothing is being sent to, or received on, 
port 80, anywhere.


If I change the BalancerMember URLs to use HTTP instead of HTTPS, the backend 
workers become available and I can proxy requests to them, but this is not how 
the eventual system is required to work.  I have to point at HTTPS-only backend 
servers.


So, what am I doing wrong, and/or what do I need to change in order to get 
BalancerMembers using HTTPS to become available for use?


Happy to supply any further details needed if people ask.


Thanks,


Antony.

--
All generalisations are inaccurate.

   Please reply to the list;
 please *don't* CC me.

-
To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org
For additional commands, e-mail: users-h...@httpd.apache.org


This e-mail message and any files transmitted with it may contain confidential 
and proprietary information and are intended solely for the use of the 
individual or entity to which they are addressed. Any unauthorized review, use, 
disclosure or distribution is strictly prohibited. If you have received this 
e-mail in error please notify the sender by reply email and destroy all copies 
of the original message. Thank you for your cooperation.

-
To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org
For additional commands, e-mail: users-h...@httpd.apache.org

[users@httpd] Does Apache HTTPD support .PFX format

2023-09-13 Thread Santosh Kondapuram 
Hi,

We are running Apache HTTPD 2.4.x web server on top of WebLogic
application server to proxy the requests.
In general we extract SSL certificate and Private key out of a .PFX file
and configure the server parameters accordingly.
So instead of extracting the files is it possible to configure the .pfx
itself in Apache httpd server which is password protected.
P.S. I am running Apache on a Windows machine.


Regards,
Santosh.




This e-mail message and any files transmitted with it may contain confidential 
and proprietary information and are intended solely for the use of the 
individual or entity to which they are addressed. Any unauthorized review, use, 
disclosure or distribution is strictly prohibited. If you have received this 
e-mail in error please notify the sender by reply email and destroy all copies 
of the original message. Thank you for your cooperation.