RE: Help Needed for Root cause - ApacheTomcat services stopped

[Verma, Sahil]

Hi Mark,
Good day!

Thank you very much for the reply!

Yes, we are using both Apache & Tomcat environment.

Apache - 2.4.25 version
Tomcat - 8.5.5 version
OS - Linux 


You are correct, we got this error in Apache webserver logs. We are attaching 
both Apache httpd (error.log) and Tomcat (Catalina.out) logs

Please let us know if any other information required.

Thanks,
Sahil



-Original Message-
From: Mark Thomas  
Sent: Wednesday, May 11, 2022 11:39 PM
To: users@tomcat.apache.org
Subject: Re: Help Needed for Root cause - ApacheTomcat services stopped

That is an Apache Web Server (httpd) log message, not an Apache Tomcat log 
message. Are you sure you are using Apache Tomcat?

Mark


On 11/05/2022 19:01, Verma, Sahil wrote:
> Hi Team,
> 
> 
> 
> In our production environment, ApacheTomcat services went down. We 
> have checked the logs and found below error -
> 
> 
> 
> [Thu May 05 10:34:51.441668 2022] [mpm_event:error] [pid 27440:tid 
> 140464737793792] AH00484: server reached MaxRequestWorkers setting, 
> consider raising the MaxRequestWorkers setting
> 
> 
> 
> Please help to find the root cause of the issue why services got stopped. 
> Kindly let us know if any other information required.
> 
> Apache version - 2.2
> OS - Linux
> 
> 
> Thanks,
> Sahil
> 
> DXC Technology India Private Limited - 9th Floor, Block-D Littlewood Tower, 
> TRIL Info Park Ramanujan IT City, Rajiv Gandhi Salai, Taramani, Chennai - 
> 600113. CIN: U72900TN2015FTC102489.
> DXC Technology Company -- This message is transmitted to you by or on behalf 
> of DXC Technology Company or one of its affiliates. It is intended 
> exclusively for the addressee. The substance of this message, along with any 
> attachments, may contain proprietary, confidential or privileged information 
> or information that is otherwise legally exempt from disclosure. Any 
> unauthorized review, use, disclosure or distribution is prohibited. If you 
> are not the intended recipient of this message, you are not authorized to 
> read, print, retain, copy or disseminate any part of this message. If you 
> have received this message in error, please destroy and delete all copies and 
> notify the sender by return e-mail. Regardless of content, this e-mail shall 
> not operate to bind DXC Technology Company or any of its affiliates to any 
> order or other contract unless pursuant to explicit written agreement or 
> government initiative expressly permitting the use of e-mail for such purpose.
> 

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

-bash-4.1$ cat error_log.20220505
rm: cannot remove `/share/images/pdf/Statementkimpickett20220505.zip': No such 
file or directory
rm: cannot remove `/share/images/pdf/Statementcweishuhn20220505.zip': No such 
file or directory
[Thu May 05 10:34:51.441668 2022] [mpm_event:error] [pid 27440:tid 
140464737793792] AH00484: server reached MaxRequestWorkers setting, consider 
raising the MaxRequestWorkers setting
[Thu May 05 11:28:16.826878 2022] [core:warn] [pid 27440:tid 140464737793792] 
AH00045: child process 27465 still did not exit, sending a SIGTERM
[Thu May 05 11:28:16.826994 2022] [core:warn] [pid 27440:tid 140464737793792] 
AH00045: child process 27466 still did not exit, sending a SIGTERM
[Thu May 05 11:28:16.827047 2022] [core:warn] [pid 27440:tid 140464737793792] 
AH00045: child process 27467 still did not exit, sending a SIGTERM
[Thu May 05 11:28:16.827098 2022] [core:warn] [pid 27440:tid 140464737793792] 
AH00045: child process 27698 still did not exit, sending a SIGTERM
[Thu May 05 11:28:16.827151 2022] [core:warn] [pid 27440:tid 140464737793792] 
AH00045: child process 27896 still did not exit, sending a SIGTERM
[Thu May 05 11:28:16.827205 2022] [core:warn] [pid 27440:tid 140464737793792] 
AH00045: child process 27971 still did not exit, sending a SIGTERM
[Thu May 05 11:28:16.827254 2022] [core:warn] [pid 27440:tid 140464737793792] 
AH00045: child process 28071 still did not exit, sending a SIGTERM
[Thu May 05 11:28:16.827307 2022] [core:warn] [pid 27440:tid 140464737793792] 
AH00045: child process 28135 still did not exit, sending a SIGTERM
[Thu May 05 11:28:18.829711 2022] [core:warn] [pid 27440:tid 140464737793792] 
AH00045: child process 27465 still did not exit, sending a SIGTERM
[Thu May 05 11:28:18.829835 2022] [core:warn] [pid 27440:tid 140464737793792] 
AH00045: child process 27466 still did not exit, sending a SIGTERM
[Thu May 05 11:28:18.829901 2022] [core:warn] [pid 27440:tid 140464737793792] 
AH00045: child process 27467 still did not exit, sending a SIGTERM
[Thu May 05 11:28:18.829970 2022] [core:warn] [pid 27440:tid 140464737793792] 
AH00045: child process 27698 still did not exit, sending a SIGTERM
[Thu May 05 11:28:18.830032 2022] [core:warn] [pid 27440:tid 140464737793792] 
AH00045: child process 27896 still did not exit, sending a 

Re: Help Needed for Root cause - ApacheTomcat services stopped

[Mark Thomas]

That is an Apache Web Server (httpd) log message, not an Apache Tomcat 
log message. Are you sure you are using Apache Tomcat?


Mark


On 11/05/2022 19:01, Verma, Sahil wrote:

Hi Team,



In our production environment, ApacheTomcat services went down. We have checked 
the logs and found below error -



[Thu May 05 10:34:51.441668 2022] [mpm_event:error] [pid 27440:tid 
140464737793792] AH00484: server reached MaxRequestWorkers setting, consider 
raising the MaxRequestWorkers setting



Please help to find the root cause of the issue why services got stopped. 
Kindly let us know if any other information required.

Apache version - 2.2
OS - Linux


Thanks,
Sahil

DXC Technology India Private Limited - 9th Floor, Block-D Littlewood Tower, 
TRIL Info Park Ramanujan IT City, Rajiv Gandhi Salai, Taramani, Chennai - 
600113. CIN: U72900TN2015FTC102489.
DXC Technology Company -- This message is transmitted to you by or on behalf of 
DXC Technology Company or one of its affiliates. It is intended exclusively for 
the addressee. The substance of this message, along with any attachments, may 
contain proprietary, confidential or privileged information or information that 
is otherwise legally exempt from disclosure. Any unauthorized review, use, 
disclosure or distribution is prohibited. If you are not the intended recipient 
of this message, you are not authorized to read, print, retain, copy or 
disseminate any part of this message. If you have received this message in 
error, please destroy and delete all copies and notify the sender by return 
e-mail. Regardless of content, this e-mail shall not operate to bind DXC 
Technology Company or any of its affiliates to any order or other contract 
unless pursuant to explicit written agreement or government initiative 
expressly permitting the use of e-mail for such purpose.



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

Re: Catalina.policy for SAP BO

[Zdeněk Henek]

Hi,

Java Security Manager is deprecated in jdk 17 release
https://docs.oracle.com/en/java/javase/17/docs/api/java.base/java/lang/SecurityManager.html
and may be even removed soon.

Regards,
Zdenek Henek

On Wed, May 11, 2022 at 10:14 AM Chavez Ortiz, Oscar (Externo) <
oscar.chavez.exte...@vwfs.com> wrote:

> Hello group.
>
> Our system is a SAP Business Object 4.2 server wich uses Tomcat 9.0.58 as
> web container.
>
> We’re implementing Security Hardening for Tomcat in our BO Server server,
> thus, i’ve configured starting configuration in java options with “–
> Security Manager” option.
>
> Now, the problem is when opening SAP BO Launch Pad tool in web browser i’m
> gettint the HTTP 500 error.
>
> I think that the catalina.policy file isn’t accordingly configurated and
> there are some permissions left that aren’t implemented.
>
> My request is: If you have any template of catalina.policy that implements
> Security Manager for SAP BO and you can share it i’d compare it against the
> ours one.
>
> SAP Support said that Tomcat is not part of their duties because it’s a
> third software.
>
> Thank you in advance.
> Best regards.
> Oscar.
> AVISO LEGAL
>
> Este mensaje y su contenido está dirigido únicamente a su destinatario y
> es confidencial. Por ello, se informa a quien lo reciba por error o tenga
> conocimiento del mismo sin ser su destinatario, que la información
> contenida en él es reservada y su uso no autorizado, por lo que en tal caso
> le rogamos nos lo comunique por la misma vía o por teléfono 91.427.99.03,
> así como que se abstenga de reproducir el mensaje mediante cualquier medio
> o remitirlo o entregarlo a otra persona, procediendo a su destrucción de
> manera inmediata.
>
> VOLKSWAGEN RENTING SA se reserva las acciones legales que le correspondan
> contra todo tercero que acceda de forma ilegítima al contenido de cualquier
> mensaje externo procedente del mismo.
>
> VOLKSWAGEN FINANCIAL SERVICES es una marca comercializada por Volkswagen
> Renting SA
>
> Se le informa que sus datos personales son tratados por Volkswagen Renting
> S.A., con domicilio social en Avda. de Bruselas, nº 34, 28108, Alcobendas
> (Madrid).
>
> Ud. podrá ejercitar los derechos de acceso, rectificación o supresión,
> oposición y portabilidad de los datos, bien por correo postal a VOLKSWAGEN
> RENTING S.A. a la dirección indicada arriba o por correo electrónico a
> clientes.rent...@vwfs.com. Asimismo, y
> en las mismas direcciones, Ud. podrá solicitar la limitación del
> tratamiento de sus datos en los casos legalmente previstos. Igualmente,
> puede contactar con nuestro Delegado de Protección de Datos en la siguiente
> dirección dpo...@vwfs.com. Asimismo, podrá
> dirigirse a la Agencia Española de Protección de Datos.
>
> -
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: users-h...@tomcat.apache.org
>

Help Needed for Root cause - ApacheTomcat services stopped

[Verma, Sahil]

Hi Team,



In our production environment, ApacheTomcat services went down. We have checked 
the logs and found below error -



[Thu May 05 10:34:51.441668 2022] [mpm_event:error] [pid 27440:tid 
140464737793792] AH00484: server reached MaxRequestWorkers setting, consider 
raising the MaxRequestWorkers setting



Please help to find the root cause of the issue why services got stopped. 
Kindly let us know if any other information required.

Apache version - 2.2
OS - Linux


Thanks,
Sahil

DXC Technology India Private Limited - 9th Floor, Block-D Littlewood Tower, 
TRIL Info Park Ramanujan IT City, Rajiv Gandhi Salai, Taramani, Chennai - 
600113. CIN: U72900TN2015FTC102489.
DXC Technology Company -- This message is transmitted to you by or on behalf of 
DXC Technology Company or one of its affiliates. It is intended exclusively for 
the addressee. The substance of this message, along with any attachments, may 
contain proprietary, confidential or privileged information or information that 
is otherwise legally exempt from disclosure. Any unauthorized review, use, 
disclosure or distribution is prohibited. If you are not the intended recipient 
of this message, you are not authorized to read, print, retain, copy or 
disseminate any part of this message. If you have received this message in 
error, please destroy and delete all copies and notify the sender by return 
e-mail. Regardless of content, this e-mail shall not operate to bind DXC 
Technology Company or any of its affiliates to any order or other contract 
unless pursuant to explicit written agreement or government initiative 
expressly permitting the use of e-mail for such purpose.

RE: WELCOME to users@tomcat.apache.org

[Verma, Sahil]

Hi Team,

In our production environment, ApacheTomcat services went down. We have checked 
the logs and found below error -

[Thu May 05 10:34:51.441668 2022] [mpm_event:error] [pid 27440:tid 
140464737793792] AH00484: server reached MaxRequestWorkers setting, consider 
raising
the MaxRequestWorkers setting

Please help to find the root cause of the issue why services got stopped. 
Kindly let us know if any other information required.


Thanks and Regards,
Sahil Verma

-Original Message-
From: users-h...@tomcat.apache.org 
Sent: Wednesday, May 11, 2022 11:25 PM
To: Verma, Sahil 
Subject: WELCOME to users@tomcat.apache.org

Hi! This is the ezmlm program. I'm managing the users@tomcat.apache.org mailing 
list.

I'm working for my owner, who can be reached at users-ow...@tomcat.apache.org.

Acknowledgment: I have added the address

   sverm...@dxc.com

to the users mailing list.

Welcome to users@tomcat.apache.org!

Please save this message so that you know the address you are subscribed under, 
in case you later want to unsubscribe or change your subscription address.


--- Administrative commands for the users list ---

I can handle administrative requests automatically. Please do not send them to 
the list address! Instead, send your message to the correct command address:

To subscribe to the list, send a message to:
   

To remove your address from the list, send a message to:
   

Send mail to the following for info and FAQ for this list:
   
   

Similar addresses exist for the digest list:
   
   

To get messages 123 through 145 (a maximum of 100 per request), mail:
   

To get an index with subject and author for messages 123-456 , mail:
   

They are always returned as sets of 100, max 2000 per request, so you'll 
actually get 100-499.

To receive all messages with the same subject as message 12345, send a short 
message to:
   

The messages should contain one line or word of text to avoid being treated as 
sp@m, but I will ignore their content.
Only the ADDRESS you send to is important.

You can start a subscription for an alternate address, for example 
"john@host.domain", just add a hyphen and your address (with '=' instead of 
'@') after the command word:


To stop subscription for this address, mail:


In both cases, I'll send a confirmation message to that address. When you 
receive it, simply reply to it to complete your subscription.

If despite following these instructions, you do not get the desired results, 
please contact my owner at users-ow...@tomcat.apache.org. Please be patient, my 
owner is a lot slower than I am ;-)

--- Enclosed is a copy of the request I received.

Return-Path: 
Received: (qmail 52135 invoked by uid 99); 11 May 2022 17:54:43 -
Received: from spamproc1-he-de.apache.org (HELO spamproc1-he-de.apache.org) 
(116.203.196.100)
by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 11 May 2022 17:54:43 +
Received: from localhost (localhost [127.0.0.1])
by spamproc1-he-de.apache.org (ASF Mail Server at 
spamproc1-he-de.apache.org) with ESMTP id BCD701FF0FC
for 
; 
Wed, 11 May 2022 17:54:42 + (UTC)
X-Virus-Scanned: Debian amavisd-new at spamproc1-he-de.apache.org
X-Spam-Flag: NO
X-Spam-Score: 0.099
X-Spam-Level:
X-Spam-Status: No, score=0.099 tagged_above=-999 required=6.31
tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1,
DKIM_VALID_EF=-0.1, POISEN_SPAM_PILL=0.1, POISEN_SPAM_PILL_1=0.1,
POISEN_SPAM_PILL_3=0.1, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001,
URIBL_BLOCKED=0.001] autolearn=disabled
Authentication-Results: spamproc1-he-de.apache.org (amavisd-new);
dkim=pass (2048-bit key) header.d=dxc.com
Received: from mx1-he-de.apache.org ([116.203.227.195])
by localhost (spamproc1-he-de.apache.org [116.203.196.100]) 
(amavisd-new, port 10024)
with ESMTP id TcSHZayvXWFL
for 
;
Wed, 11 May 2022 17:54:41 + (UTC)
Received-SPF: Pass (mailfrom) identity=mailfrom; client-ip=67.219.250.2; 
helo=mail1.bemta35.messagelabs.com; envelope-from=sverm...@dxc.com; 
receiver=
Received: from mail1.bemta35.messagelabs.com (mail1.bemta35.messagelabs.com 
[67.219.250.2])
by mx1-he-de.apache.org (ASF Mail Server at mx1-he-de.apache.org) with 
ESMTPS id 68A197ED15
for 
; 
Wed, 11 May 2022 17:54:41 + (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=dxc.com;
s=DXCSelector1; t=1652291673; i=@dxc.com;
bh=AYlNUORjdD96V1Y7SYiGLP3+0Wb+gqh5r3FxfEiUC1c=;
h=From:To:Subject:Date:Message-ID:References:In-Reply-To:
 Content-Type:Content-Transfer-Encoding:MIME-Version;
b=UK0SFURP0WREua4cv3m1B3TmSXKRewRpNRYo6yHjtvcdJ+vq08mzOB0BjoCHOtE+y
 0szQAsWsxszpz+393b3hAcB14bqusqHMOILJkjJ97LJv7tv8YF4fU61cXKuQ9sIbau
 2u3ntI8OG28UBHW/hBPrWHbZPeW9NEKHiJvJu9V7qL9b9ZWF9QU5CvFItMCh90wStP
 lG5jPOQD+e8YheAmwZG2Pediiuc62orpW0D6uh8SQqJQ6fgYVS17LTE8uwZ/ufI+/z
 

Re: SAML SSO Login issue

[Olaf Kock]

On 11.05.22 17:36, harish lal wrote:
> Facing SSO Login issue after upgrade from Tomcat 6.0.33 to Tomcat 7.0.62
>
> We upgraded our application from Tomcat 6.0.33 to Tomcat 7.0.62 due to web
> socket dependency in Tomcat.
> After upgrade , while try to do SAML SSO login from application we are
> facing below issue ,

Do you know that you "upgraded" to a version released in 2015 (see
https://archive.apache.org/dist/tomcat/tomcat-7/), which has seen its
end of life last year (see https://tomcat.apache.org/tomcat-70-eol.html)?

As a quick minimum - if you now have a hard dependency on Tomcat 7, you
should use the end-of-line 7.0.109 - maybe your issue is fixed in that
release already. In general (and if it isn't fixed) I'd recommend to go
to the latest in the 8.5 or 9.0 line and try to reproduce. I doubt
someone will start debugging 7 years old code that explicitly went out
of service more than a year ago. If you're lucky, someone will remember
something.

In case you still can reproduce: I'm quite uncertain what your phrase
"/If we remove only the "JSESSIONID" from the cookie/" means. Also, you
might want to look at all of the redirected requests and identify if
they're identical to each other, or where they're different.

Best,

Olaf

SAML SSO Login issue

[harish lal]

Facing SSO Login issue after upgrade from Tomcat 6.0.33 to Tomcat 7.0.62

We upgraded our application from Tomcat 6.0.33 to Tomcat 7.0.62 due to web
socket dependency in Tomcat.
After upgrade , while try to do SAML SSO login from application we are
facing below issue ,

"This page isn’t working  redirected you too many times.
Try clearing your cookies.
ERR_TOO_MANY_REDIRECTS"

Once we clear the whole cookie from the browser , it navigate to login page
and again it is failing while do Saml Sso login
If we remove only the "JSESSIONID" from the cookie , the application able
to login with the Saml sso credentials .

This issue is not happening in the older version of Tomcat 6.0.33 , even in
the Tomcat 7.0.12 version .
Issue is reproducing from the Tomcat 7.0.14 version onwards.

We tried in many ways to resolve the issue . Kindly help me on this to
resolve the issue.

Thanks in advance

Re: Catalina.policy for SAP BO

[logo]

Oscar,

> Am 11.05.2022 um 10:14 schrieb Chavez Ortiz, Oscar (Externo) 
> :
> 
> Hello group.
> 
> Our system is a SAP Business Object 4.2 server wich uses Tomcat 9.0.58 as web 
> container.
> 
> We’re implementing Security Hardening for Tomcat in our BO Server server, 
> thus, i’ve configured starting configuration in java options with “– Security 
> Manager” option.
> 

as an InfoSec and OpSec Manager in my company and a hardening fetishist I would 
recommend to review the recent comments of Marc...

In you situation I'd try to dispute the need for the implementation of Tomcat 
with Security Manager and focus on the hardening of the underlying OS/machine 
and used services. That would lead to a more substantial and durable result.

Java Security Manager has been a pain for a long time and if you don't want to 
put effort in now and then after every update of BO (or any other software), 
don't do it.

In my opinion the requirements of your hardening guidelines may be not 
appropriate for the risk level of your application (SAP BO vs. health data in 
hospitals eg). In our company I would go with a risk acceptance or even change 
the requirements - if I read about the future removal of the security manager 
functionality.


Just my 2ct.

Peter

> Now, the problem is when opening SAP BO Launch Pad tool in web browser i’m 
> gettint the HTTP 500 error.
> 
> I think that the catalina.policy file isn’t accordingly configurated and 
> there are some permissions left that aren’t implemented.
> 
> My request is: If you have any template of catalina.policy that implements 
> Security Manager for SAP BO and you can share it i’d compare it against the 
> ours one.
> 
> SAP Support said that Tomcat is not part of their duties because it’s a third 
> software.
> 
> Thank you in advance.
> Best regards.
> Oscar.
> AVISO LEGAL
> 
> Este mensaje y su contenido está dirigido únicamente a su destinatario y es 
> confidencial. Por ello, se informa a quien lo reciba por error o tenga 
> conocimiento del mismo sin ser su destinatario, que la información contenida 
> en él es reservada y su uso no autorizado, por lo que en tal caso le rogamos 
> nos lo comunique por la misma vía o por teléfono 91.427.99.03, así como que 
> se abstenga de reproducir el mensaje mediante cualquier medio o remitirlo o 
> entregarlo a otra persona, procediendo a su destrucción de manera inmediata.
> 
> VOLKSWAGEN RENTING SA se reserva las acciones legales que le correspondan 
> contra todo tercero que acceda de forma ilegítima al contenido de cualquier 
> mensaje externo procedente del mismo.
> 
> VOLKSWAGEN FINANCIAL SERVICES es una marca comercializada por Volkswagen 
> Renting SA
> 
> Se le informa que sus datos personales son tratados por Volkswagen Renting 
> S.A., con domicilio social en Avda. de Bruselas, nº 34, 28108, Alcobendas 
> (Madrid).
> 
> Ud. podrá ejercitar los derechos de acceso, rectificación o supresión, 
> oposición y portabilidad de los datos, bien por correo postal a VOLKSWAGEN 
> RENTING S.A. a la dirección indicada arriba o por correo electrónico a 
> clientes.rent...@vwfs.com. Asimismo, y en 
> las mismas direcciones, Ud. podrá solicitar la limitación del tratamiento de 
> sus datos en los casos legalmente previstos. Igualmente, puede contactar con 
> nuestro Delegado de Protección de Datos en la siguiente dirección 
> dpo...@vwfs.com. Asimismo, podrá dirigirse a la 
> Agencia Española de Protección de Datos.
> 
> -
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: users-h...@tomcat.apache.org
> 


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

Catalina.policy for SAP BO

[Chavez Ortiz, Oscar (Externo)]

Hello group.

Our system is a SAP Business Object 4.2 server wich uses Tomcat 9.0.58 as web 
container.

We’re implementing Security Hardening for Tomcat in our BO Server server, thus, 
i’ve configured starting configuration in java options with “– Security 
Manager” option.

Now, the problem is when opening SAP BO Launch Pad tool in web browser i’m 
gettint the HTTP 500 error.

I think that the catalina.policy file isn’t accordingly configurated and there 
are some permissions left that aren’t implemented.

My request is: If you have any template of catalina.policy that implements 
Security Manager for SAP BO and you can share it i’d compare it against the 
ours one.

SAP Support said that Tomcat is not part of their duties because it’s a third 
software.

Thank you in advance.
Best regards.
Oscar.
AVISO LEGAL

Este mensaje y su contenido está dirigido únicamente a su destinatario y es 
confidencial. Por ello, se informa a quien lo reciba por error o tenga 
conocimiento del mismo sin ser su destinatario, que la información contenida en 
él es reservada y su uso no autorizado, por lo que en tal caso le rogamos nos 
lo comunique por la misma vía o por teléfono 91.427.99.03, así como que se 
abstenga de reproducir el mensaje mediante cualquier medio o remitirlo o 
entregarlo a otra persona, procediendo a su destrucción de manera inmediata.

VOLKSWAGEN RENTING SA se reserva las acciones legales que le correspondan 
contra todo tercero que acceda de forma ilegítima al contenido de cualquier 
mensaje externo procedente del mismo.

VOLKSWAGEN FINANCIAL SERVICES es una marca comercializada por Volkswagen 
Renting SA

Se le informa que sus datos personales son tratados por Volkswagen Renting 
S.A., con domicilio social en Avda. de Bruselas, nº 34, 28108, Alcobendas 
(Madrid).

Ud. podrá ejercitar los derechos de acceso, rectificación o supresión, 
oposición y portabilidad de los datos, bien por correo postal a VOLKSWAGEN 
RENTING S.A. a la dirección indicada arriba o por correo electrónico a 
clientes.rent...@vwfs.com. Asimismo, y en las 
mismas direcciones, Ud. podrá solicitar la limitación del tratamiento de sus 
datos en los casos legalmente previstos. Igualmente, puede contactar con 
nuestro Delegado de Protección de Datos en la siguiente dirección 
dpo...@vwfs.com. Asimismo, podrá dirigirse a la Agencia 
Española de Protección de Datos.

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