How to install the APR for Tomcat9 version in Linux OS with out internet access

2021-01-17 Thread Naga Ramesh
Team,

 

I am trying to install the APR for tomcat 9 version in my local linux
(RHEL-6 OS version) server but don't have the internet access and keep on
asking many dependencies and tried multiple ways.

Can you please let me know, where can I download the all dependencies rpm
files or if any url/doc is there for this.

 

 

Regards,

Naga R



RE: Error parsing HTTP request header

2020-02-26 Thread Naga Ramesh
May I know the tomcat version please.

-Original Message-
From: dku...@ccilindia.co.in [mailto:dku...@ccilindia.co.in] 
Sent: 26 February 2020 19:01
To: 'Tomcat Users List'
Subject: Error parsing HTTP request header

Dear Team,

We are getting below error in catelina log while starting the tomcat.

26-Feb-2020 18:57:36.795 INFO [main]
org.apache.catalina.startup.Catalina.start Server startup in 21520 ms
26-Feb-2020 18:57:38.277 INFO [http-nio-443-exec-11]
org.apache.coyote.http11.AbstractHttp11Processor.process Error parsing HTTP
request header
 Note: further occurrences of HTTP header parsing errors will be logged at
DEBUG level.
 java.lang.IllegalArgumentException: Invalid character found in the request
target. The valid characters are defined in RFC 7230 and RFC 3986
at
org.apache.coyote.http11.AbstractNioInputBuffer.parseRequestLine(AbstractNio
InputBuffer.java:283)
at
org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Proce
ssor.java:1017)
at
org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(Abstrac
tProtocol.java:684)
at
org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.jav
a:1524)
at
org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:
1480)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:11
49)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:6
24)
at
org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.ja
va:61)
at java.lang.Thread.run(Thread.java:748)

Will this impact any performance of our tomcat.

Thanks & Regards
Deepak Kumar
CCIL - IT
022-61546230
CIN of CCIL- U65990MH2001PLC131804
"Disclaimer and confidentiality clause -  This message and any attachments
relating to official business of CCIL OR ANY OF IT'S SUBSIDIARIES is
proprietary to CCIL and intended for the original addressee only.
The message may contain information that is confidential and subject to
legal privilege. 
Any views expressed in this message are those of the individual sender. 
If you have received this message in error, please notify the original
sender immediately and destroy the message and copies thereof and any
attachments contained in it .
 If you are not the intended recipient of this message, you are hereby
notified that you must not disseminate, copy, use, distribute, or take any
action in connection therewith. 
 CCIL cannot ensure that the integrity of this communication has been
maintained nor that it is free of errors, viruses, interception and/or
interference. 
CCIL is not liable whatsoever for loss or damage resulting from the opening
of this message and/or attachments and/or the use of the information
contained in this message and/or attachments."


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



RE: How to restrict the AWS ELB IP url acceess from tomcat

2019-07-23 Thread Naga Ramesh
Thanks Chris.. we have redirected the ELB IP based url to domain url on AWS
ELB end.

Thanks for your support.

Regards,
Naga Ramesh R

-Original Message-
From: Christopher Schultz [mailto:ch...@christopherschultz.net] 
Sent: 23 July 2019 00:15
To: users@tomcat.apache.org
Subject: Re: How to restrict the AWS ELB IP url acceess from tomcat

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Naga,

On 7/21/19 13:00, Naga Ramesh wrote:
> We have configured the tomcat8 version with AWS ELB and mapped to 
> specific domain name. but url accessing with ELB ip's also.
> 
> So we need to restrict the url access with IP, please let us know what 
> are all the configurations changes needed on tomcat end.

Can you ask this in a different way? I can't understand what you are asking.

Are you trying to limit the IP addresses which can reach Tomcat? Are you
trying to change the URL that users use to access Tomcat?

Maybe show us what you want to do and how it fails to work as expected when
you try it.

- -chris
-BEGIN PGP SIGNATURE-
Comment: Using GnuPG with Thunderbird - https://www.enigmail.net/

iQIzBAEBCAAdFiEEMmKgYcQvxMe7tcJcHPApP6U8pFgFAl02BDgACgkQHPApP6U8
pFi47hAAm+c8UpjJvG6q6KZ043yuVdNGXjWDzUiwD62JCVaJYgvEqZBy9VM/NWOK
0Gu8/fn6dN5D1eV5kqwBMybf9N7K+dFNheOreodH3FY6FUxKCKmXZK+gcgUQthDR
OvDr1SmI9Gfk7dWJfKLi1reCIMFjZO/jPOHXli+Fc6sZncyOEAH6JJvUEk9mtHHo
owMEjmOWjUdjywvcF/Dga3jz+Mrb7skxuFDi+Dz9MiguaKLndKBK0vlNwMgIYske
oMci8oGVumzPeNBIVxotbtzL7+9nvd14x87ELfTYkFdx8RP9iRJnyaSj6xfAWJFk
bzwPRCNZRtmrmo+MigYLafILrcOqSfK3rrX8EZYt0CDxu5F7AYLXFuAgdw+SBrUy
js5h6eahQUjp5GgJBgqyRG+9y2eRQ5q8vpyKFYzMQiVLBplHRvJ/tr0pXnJohVIQ
6XBuD3uBnxpt9QaK+9tFA6ZCPJsR3l3qQNYCmBjVhypjTtgrhdG8ynOF2RqLbPiO
mIXY60OHDQbVNkOQ3df6PwjdDtbZUQMyPFovwf8lf8X6Bc4hNoip/BpAiN83RzuM
rXLDsBQsvHs34H4V47i92GvZ/IH6lVDkCUYGoI2u4kpXD4Pdk89NL8/nST7zlFlQ
R1/CmiCaJaEXvrricyeS7BEcV0limoUuNU2QgS6SQwlJxJQMZt0=
=+f1G
-END PGP SIGNATURE-

-
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



How to restrict the AWS ELB IP url acceess from tomcat

2019-07-21 Thread Naga Ramesh
Team,

 

We have configured the tomcat8 version with AWS ELB and mapped to specific
domain name. but url accessing with ELB ip's also.

 

So we need to restrict the url access with IP, please let us know what are
all the configurations changes needed on tomcat end.

 

Little bit urgent,  please help me ASAP.

 

Regards,

Naga Ramesh

 



RE: Tomcat8 hardening issues

2018-06-29 Thread Naga Ramesh
Please update AEAP.

 

From: Naga Ramesh [mailto:naga.ram...@manthan.com] 
Sent: Thursday, June 28, 2018 11:01 PM
To: users@tomcat.apache.org
Subject: Tomcat8 hardening issues

 

Guys,

 

I have done the hardening on Tomcat 8 version (PF below mentioned
configuration changes), but in application level some of the functionalities
are not working properly and observed some errors in the backend (PF below
mentioned errors), please re-check and  provide me the proper solution ASAP.

 

Enabled the below changes on web.xml file (tomcat8/conf).

 

Web.xml:

 



httpHeaderSecurity

 
org.apache.catalina.filters.HttpHeaderSecurityFilter



  hstsMaxAgeSeconds

  31536000





  hstsMaxAgeSeconds

  31536000



 

true



 

 



httpHeaderSecurity

/*

REQUEST



 

Server.xml: (added the secure tag on connector)

 


Tomcat8 hardening issues

2018-06-28 Thread Naga Ramesh
Guys,

 

I have done the hardening on Tomcat 8 version (PF below mentioned
configuration changes), but in application level some of the functionalities
are not working properly and observed some errors in the backend (PF below
mentioned errors), please re-check and  provide me the proper solution ASAP.

 

Enabled the below changes on web.xml file (tomcat8/conf).

 

Web.xml:

 



httpHeaderSecurity

 
org.apache.catalina.filters.HttpHeaderSecurityFilter



  hstsMaxAgeSeconds

  31536000





  hstsMaxAgeSeconds

  31536000



 

true



 

 



httpHeaderSecurity

/*

REQUEST



 

Server.xml: (added the secure tag on connector)

 


tomcat 7 and 8 version memory setting

2018-04-26 Thread Naga Ramesh
Team,

 

I have configured the tomcat7 & 8 versions on our AWS environment, but how
much memory need to give min and max for each tomcat.  ( max to max how much
need to give the max vlaue)

 

Server:  AWS linux

RAM: 128GB

 

I have given min:4096M  and max:32768M

 

 

Regards,

Ramesh R



RE: unable to set the "secure="true" flag on server.xml

2017-11-30 Thread Naga Ramesh
Thanks Chris..

See the below output and here not showing the secure.

< HTTP/1.1 200 OK
< Set-Cookie: JSESSIONID=D14ACAB7CADB83FAD5C11296C75A09DB; Path=/; HttpOnly
< X-Frame-Options: DENY
< X-Content-Type-Options: nosniff
< X-XSS-Protection: 1; mode=block
< Content-Type: text/html;charset=ISO-8859-1
< Content-Length: 5472
< Date: Thu, 30 Nov 2017 17:26:37 GMT
< Server:


Regards,
Naga Ramesh

-Original Message-
From: Christopher Schultz [mailto:ch...@christopherschultz.net] 
Sent: Thursday, November 30, 2017 10:52 PM
To: users@tomcat.apache.org
Subject: Re: unable to set the "secure="true" flag on server.xml

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Naga,

On 11/30/17 12:11 PM, Naga Ramesh wrote:
> I have configured the tomcat8 version & used the AWS ELB, but I have 
> set the “secure="true" flag on tomcat8/conf/server.xml file end, after 
> that service started and login page came but I am unable to login the 
> application and getting the oops session expired error message coming.

Please post your  configuration.

What did you expect secure="true" to actually do?

> Note: we have applied the SSL on AWS ELB end.

So you are terminating TLS at the ELB, right?

> ELB(https) -à tomcat-conenctor-8080

Traffic from ELB -> Tomcat is using HTTPS?

Why encrypt within your own VLAN?

- -chris
-BEGIN PGP SIGNATURE-
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQJRBAEBCAA7FiEEMmKgYcQvxMe7tcJcHPApP6U8pFgFAlogPjgdHGNocmlzQGNo
cmlzdG9waGVyc2NodWx0ei5uZXQACgkQHPApP6U8pFjNsw/6AgqvEO54pTNb2Uid
V9sAx5XLpH3YCQpRifJRQwM/VIyL8WCCASeEKHOf9ZFGQwgmdGbsWhiVbGIXZiKP
JsT5NMWOvL22ipLwj4EiTq0w7+8va4+fQGmFWqR29pLb6lRP0xpvkZZGndYWAH88
67/giHBiSSD3HtmZtuwmR9UItBLepIrd4bxK37aZtMIMztVMfFZlFpQcBzmRhoVX
kR8rEyJnbAn7Gqc0MY+nYpD5t/1xlUwypjN/GekfpgJX1Kg9Ac3OO2UlwaXECgM1
Yt9IGHHn2xILryfRfBdgxY+M+f013kGDRGerE2K/dDSsF7/T1W6uYiuPCsj3UX2t
tzMvdr1gDtZIVbBm2YyUoh3QMISuteYNTufFCyAWrvOjSSWgTeySTowNWmMvOHG9
PG6a+/gZawGjDDerIcPdUMMPJfsqJ85a0TbYJpHf5FJPeOkFkzMrrMPIeLVUlNpV
eAAwV3z3hTlpgyV8xaRNCKeMmli0/XDcruVrEKJXHOhmH0e1rqWa2A6OMkcBGxbu
xoUqVf69BOQz460iGMtO6TqDGF5InELKShEsfELHoSTr0SJ20qBsDM73cOCAKIFF
wu8wPoWla2f2psoQTLIQ521UQq/bVGm3V68ILr7rvRBtuSLl8GzF2VQoJeo6Dmto
pPMCCQwV75qLTjnO2Nk6LZ39Ai8=
=1f6y
-END PGP SIGNATURE-

-
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



unable to set the "secure="true" flag on server.xml

2017-11-30 Thread Naga Ramesh
All,

 

I have configured the tomcat8 version & used the AWS ELB, but I have set the
“secure="true" flag on tomcat8/conf/server.xml file end, after that service
started and login page came but I am unable to login the application and
getting the oops session expired error message coming.

 

Please let us know how do I set this flag on tomcat8 version end.

 

Note: we have applied the SSL on AWS ELB end.

 

ELB(https) -à tomcat-conenctor-8080

 

 

 

Regards,

Naga Ramesh



RE: getting some cookie & security related issues.

2017-11-30 Thread Naga Ramesh
Thanks Olaf..

There's one piece of information that looks suspicious to me: HTTPS from AWS
to Tomcat, port 8080. While it's possible that you're doing this,
8080 is typically used to handle http requests, while 8443 would be a
default choice in the 8000+ range of ports for handling https. Please
confirm or deny that you have reconfigured a secure connector to listen to
port 8080, otherwise it's not clear that you're indeed configuring the
communication from AWS to Tomcat as an encrypted one.


User-https request  --->AWS-ELB-443 & here we have applied the SSL
&443 redirect to 8080 of tomcat(non SSL)



To preempt the next mail and give more information upfront: If you indeed
have tomcat listen on 8080 for http, it won't have a clue that this
connection is secure, because it doesn't know anything about the original
connection. You can fake the knowledge about the connection to be secure
with the connector attribute secure="true", but you'll have to make sure
that nobody can reach your tomcat through any other way than through your
load balancer when you do. Another option is to use AJP for the
communication between AWS and Tomcat (I don't know if this is supported on
the AWS-ELB side). While this protocol is unencrypted, it does forward the
http/https information from the original connection

I have tried this way (secure="true") also, but application is working fine
but we are unable to login the application & getting the oops session
expired error message, so I have reverted this parameter.



Regards,
Naga Ramesh R
1974
-Original Message-
From: Olaf Kock [mailto:tom...@olafkock.de] 
Sent: Thursday, November 30, 2017 1:33 PM
To: users@tomcat.apache.org
Subject: Re: getting some cookie & security related issues.


On 30.11.2017 08:52, Naga Ramesh wrote:
> User > AWS > Tomcat
>(HTTPS)(HTTPS)
>
> User-HTTPS request> AWS-ELB(https-443)  re-direct to tomcat 
> connector
> port-8080
>
> What is the (expected) path when the user makes an HTTPS request? Is it:
>
> User > AWS > Tomcat
>(HTTPS)(HTTPS)
There's one piece of information that looks suspicious to me: HTTPS from AWS
to Tomcat, port 8080. While it's possible that you're doing this,
8080 is typically used to handle http requests, while 8443 would be a
default choice in the 8000+ range of ports for handling https. Please
confirm or deny that you have reconfigured a secure connector to listen to
port 8080, otherwise it's not clear that you're indeed configuring the
communication from AWS to Tomcat as an encrypted one.

To preempt the next mail and give more information upfront: If you indeed
have tomcat listen on 8080 for http, it won't have a clue that this
connection is secure, because it doesn't know anything about the original
connection. You can fake the knowledge about the connection to be secure
with the connector attribute secure="true", but you'll have to make sure
that nobody can reach your tomcat through any other way than through your
load balancer when you do. Another option is to use AJP for the
communication between AWS and Tomcat (I don't know if this is supported on
the AWS-ELB side). While this protocol is unencrypted, it does forward the
http/https information from the original connection 
User->AWS

Please clarify your situation. Thanks,
Olaf

-
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



RE: getting some cookie & security related issues.

2017-11-29 Thread Naga Ramesh
Hi Mark,

Please find my comments here & PFA diagram.

User > AWS > Tomcat
  (HTTPS)(HTTPS)

User-HTTPS request> AWS-ELB(https-443)  re-direct to tomcat connector
port-8080

What is the (expected) path when the user makes an HTTPS request? Is it:

User > AWS > Tomcat 
  (HTTPS)(HTTPS)


Regards,
Naga Ramesh

-Original Message-
From: Mark Thomas [mailto:ma...@apache.org] 
Sent: Thursday, November 30, 2017 1:06 PM
To: Tomcat Users List
Subject: Re: getting some cookie & security related issues.

On 30/11/2017 06:53, Naga Ramesh wrote:
> Team,
> 
> We are facing some issues on security level testing time, so please 
> check the below mentioned issues and suggest me the changes on tomcat 
> level ASAP.
> 
> 1.  *Session Cookie do not contain secure attribute:* for this
> what are all the changes I need to take are on tomcat level
> 
> 2.  *Site susceptible to Man-In-The-Middle HTTPS Downgrade
> attack*: Here we have used the AWS ELB with SSL and mapped to the
> tomcat instance, but in testing time instance went to http instead
> of Https, so what are all the changes need to take care for this
> issues on tomcat level.
> 
> Versions:
> Tomcat version:
tomcat-8.0.33
> Java Version: 1.8.0_60-b27
> 
> And also attached the server.xml, web.xml & context file of tomcat/conf.

Thank you for providing the version and configuration details. To answer
your questions we need to know a little more information.

What is the (expected) path when the user makes an HTTP request? Is it:

User > AWS > Tomcat
  (HTTP)(HTTP)


What is the (expected) path when the user makes an HTTPS request? Is it:

User > AWS > Tomcat
  (HTTPS)(HTTP)

Mark


-
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

RE: applicatio shared path is not working on tomcat8 version

2017-08-29 Thread Naga Ramesh
Chris,

At present application configured on one of app server and jars located on 
different server.

So we have shared the jars folder and given the shared path of classpath on 
tomcat end.

But in tomcat 7 version is working fine but same shared path of jars classpath 
it's not working on tomcat 8 version and observed the below errors.

So we have enabled changes on context file end and it's working.

Can you please validate and let me know if any proper solution for this.


25-Aug-2017 23:58:40.282 WARNING [localhost-startStop-1] 
org.apache.tomcat.util.scan.StandardJarScanner.scan Failed to scan 
[file://msbpo120/config/workflow/] from classloader hierarchy
java.io.IOException
at 
org.apache.tomcat.util.scan.StandardJarScanner.process(StandardJarScanner.java:339)
at 
org.apache.tomcat.util.scan.StandardJarScanner.scan(StandardJarScanner.java:245)
at 
org.apache.catalina.startup.ContextConfig.processJarsForWebFragments(ContextConfig.java:1887)
at 
org.apache.catalina.startup.ContextConfig.webConfig(ContextConfig.java:1127)
at 
org.apache.catalina.startup.ContextConfig.configureStart(ContextConfig.java:779)
at 
org.apache.catalina.startup.ContextConfig.lifecycleEvent(ContextConfig.java:306)
at 
org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:95)
at 
org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:90)
at 
org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5150)
at 
org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:147)
at 
org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:725)
at 
org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:701)
at 
org.apache.catalina.core.StandardHost.addChild(StandardHost.java:717)
at 
org.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.java:587)
at 
org.apache.catalina.startup.HostConfig$DeployDescriptor.run(HostConfig.java:1798)
at 
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Caused by: java.lang.IllegalArgumentException: URI has an authority component
at java.io.File.(File.java:423)
at 
org.apache.tomcat.util.scan.StandardJarScanner.process(StandardJarScanner.java:318)
... 19 more


Regards,
Naga
 
-Original Message-
From: Christopher Schultz [mailto:ch...@christopherschultz.net] 
Sent: Tuesday, August 29, 2017 5:30 PM
To: users@tomcat.apache.org
Subject: Re: applicatio shared path is not working on tomcat8 version

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Naga,

On 8/28/17 12:38 PM, Naga Ramesh wrote:
> Chris, We don’t have the context file on app/WEB-INF path

You need to create a new one.

> , that’s why we have done on /tomcat/conf/context.xml file.

You have modified the defaults for the whole server. If you deploy another web 
application, it will also have the JarScanner disabled, even if you need JAR 
scanning enabled. Please fix your global defaults file and configure your 
application correctly.

> After that issue is resolved, but how do I resolve the issue, please 
> guide me
Which issue? You said that disabling JAR scanning has fixed your original 
report (which doesn't actually make any sense to me). so what problem are you 
now facing?

- -chris

> -Original Message- From: Christopher Schultz 
> [mailto:ch...@christopherschultz.net] Sent: Monday, August 28,
> 2017 9:09 PM To: users@tomcat.apache.org Subject: Re: applicatio 
> shared path is not working on tomcat8 version
> 
> Naga,
> 
> On 8/28/17 11:23 AM, Naga Ramesh wrote:
>> Thanks Chris.. issues is resolved..
> 
>> We have enabled the below thing on context file and it's working 
>> fine.
> 
> 
>> tomcat8/conf/context.xml:  added the below line and restarted the 
>> service.
> 
>> > scanAllDirectories="false"/>
> 
> STOP. Undo what you have just done.
> 
> You only want to disable the JAR scanner for your application.
> What you have done is disable the JAR scanner for the entire server.
> 
> The file you want is $yourapplication/WEB-INF/context.xml not 
> $CATALINA_BASE/conf/context.xml
> 
> -chris
> 
>> -Original Message- From: Christopher Schultz 
>> [mailto:ch...@christopherschultz.net] Sent: Monday, August 28,
>>

RE: applicatio shared path is not working on tomcat8 version

2017-08-28 Thread Naga Ramesh
Chris, We don’t have the context file on app/WEB-INF path, that’s why we have 
done on /tomcat/conf/context.xml file.

After that issue is resolved, but how do I resolve the issue, please guide me

-Original Message-
From: Christopher Schultz [mailto:ch...@christopherschultz.net] 
Sent: Monday, August 28, 2017 9:09 PM
To: users@tomcat.apache.org
Subject: Re: applicatio shared path is not working on tomcat8 version

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Naga,

On 8/28/17 11:23 AM, Naga Ramesh wrote:
> Thanks Chris.. issues is resolved..
> 
> We have enabled the below thing on context file and it's working fine.
> 
> 
> tomcat8/conf/context.xml:  added the below line and restarted the 
> service.
> 
>  scanAllDirectories="false"/>

STOP. Undo what you have just done.

You only want to disable the JAR scanner for your application. What you have 
done is disable the JAR scanner for the entire server.

The file you want is $yourapplication/WEB-INF/context.xml not 
$CATALINA_BASE/conf/context.xml

- -chris

> -Original Message- From: Christopher Schultz 
> [mailto:ch...@christopherschultz.net] Sent: Monday, August 28, 2017
> 8:11 PM To: users@tomcat.apache.org Subject: Re: applicatio shared 
> path is not working on tomcat8 version
> 
> Naga,
> 
> On 8/27/17 12:24 PM, Naga Ramesh wrote:
>> Christopher,
> 
>> We have done the load balancer configuration and one of the 
>> properties file need to give the shared path and that shared path 
>> need to give the tomcat end for some functionality purpose.
> 
>> So we have set the class path on tomcat7 and it's working fine but 
>> same thing we have tried on tomcat8 version, here throwing the below 
>> mentioned errors.
> 
>> Please suggest any alternative solution for this.
> 
> Please post your configuration showing how you are setting the 
> CLASSPATH .
> 
> -chris
> 
> -
>
> 
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
> 
-BEGIN PGP SIGNATURE-
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQIcBAEBCAAGBQJZpDj3AAoJEBzwKT+lPKRYXlwQALePo58g/Bz2A5pXylBvD68+
lwF1toFVBRAuNPXW2OiZUi6yn+L9LxtKwewwR35gShV18/H99hlyXZ8HEpY3b2jg
W34MsWxDz8QqUjd0nVYiGpY/WIatqhzRytQc1Hy+yPg8cyZ7JXbNKtC3fWZzGcyb
A2s7DxtmjpKGI4AvqJfUkIAZ3hjsbyj6Iabik8AvFDLzocxIQrB0u+l25Y/QDbyj
JuqblLi64N5Ovy8lAh9fo1iFFJ8eRvOoI981WskvRlb0SXmi/vrBeGUKDQI/jAiB
qHudUjT2x/e5O3EUQFljhKwWuINp24myqpdLp+GiWrZmD2a6ilFjkqnRYRag4clo
XmoYhFj8tY0cVZgFi8z4IjDGjdCrEawHPe5SmJ4k/elWydzOJYuXTgIdTzyMTgR9
LEwBmzjnmQ5xMFjJZdbsTN7oPzM3XO7Dk0kNhC+e8d5VWWXZvG5uOsTraL2TQjRr
LmfkhmlDBO4K/KpGXYrtM1edCRBfO/HE4QlHF0hRPlqST+E6KVZ8wUpSbXIi0A47
T9rFDIS0IHRa9NyeutJX9gOL6Vy6qX8H1DStVVfOVV5ENijUIqGUFHjLfJ8pEBrj
Fy2TFcstDWu/wS8MsBGT8egyVh5KvFbn7XOAyUVyDX9iVEWqygPAThil21pOe9dX
mRG/UFIE6r4qIcJBnU68
=cKUz
-END PGP SIGNATURE-

-
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



RE: applicatio shared path is not working on tomcat8 version

2017-08-28 Thread Naga Ramesh
Thanks Chris.. issues is resolved..

We have enabled the below thing on context file and it's working fine.


tomcat8/conf/context.xml:  added the below line and restarted the service.




Regards,
Naga Ramesh
-Original Message-
From: Christopher Schultz [mailto:ch...@christopherschultz.net] 
Sent: Monday, August 28, 2017 8:11 PM
To: users@tomcat.apache.org
Subject: Re: applicatio shared path is not working on tomcat8 version

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Naga,

On 8/27/17 12:24 PM, Naga Ramesh wrote:
> Christopher,
> 
> We have done the load balancer configuration and one of the properties 
> file need to give the shared path and that shared path need to give 
> the tomcat end for some functionality purpose.
> 
> So we have set the class path on tomcat7 and it's working fine but 
> same thing we have tried on tomcat8 version, here throwing the below 
> mentioned errors.
> 
> Please suggest any alternative solution for this.

Please post your configuration showing how you are setting the CLASSPATH .

- -chris
-BEGIN PGP SIGNATURE-
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQIcBAEBCAAGBQJZpCt4AAoJEBzwKT+lPKRYtsoP/RZLTsJSPgP6tZIzZWM2/ryF
HBd6JfYWRBCUWkxdZdsPcLz++E7I/couPDlK2NIbwy0c1jwp3p84I1LnxbL1okp2
5njlLDt9MfPX4fmYRC1vHe9KR+sGKHJUbZX7dBANb5SucfuLBJwe4HHdiDAn4erk
36X/WArNJ6FZO5QLmGH5WBQI27u/dpyMqbyFGuETey/ivCQjO0eVOmbwVkPbTGms
WDzFOfFmEW29srenYilpZRnh/wL4wpNtPj5rYCSVP/RXZk4/N/u2RFw76xIHJdGj
/7kH9G8QbFGd+vK2J9IfveK3lMSr2xodS/BrLRT2gEW1/sz1tsWUIXK6c865ch1N
5LTtj3KZwyqIkVNXaxhFYvA7eDe4fsTM8lR0XTw+23ixMHvKNv0UlYaYLwcdVB0d
co5ZzICesoCBANYZx7Icnx7K3ouWsrM3oyEpb/PwZVFL8P5cQNnBZjC3ij96FWD3
aD3SbGeQe3jw0LGf9QUI4/rN/OxUUO8U4qLxlfloEi+cAkK9uIkYH5/J3FGVnd4C
NlfIreTLa7B6MScO7DpE4oEWZTUdU7d5WXkJo8OI2iI3EeS7fcFIfdj+sZA9Lul6
weBqi+hKx3ACgNQewsOYMAkpxS+Yl2N9guaD8i8M6xjG7wxqlfYV2UI4ZCxT1eh7
GUimvv4ks21Wc9ew/g+C
=Fp1k
-END PGP SIGNATURE-

-
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



RE: applicatio shared path is not working on tomcat8 version

2017-08-27 Thread Naga Ramesh
Christopher,

We have done the load balancer configuration and one of the properties file 
need to give the shared path and that shared path need to give the tomcat end 
for some functionality purpose.

So we have set the class path on tomcat7 and it's working fine but same thing 
we have tried on tomcat8 version, here throwing the below mentioned errors.

Please suggest any alternative solution for this.

Regards,
Naga 

-Original Message-
From: Christopher Schultz [mailto:ch...@christopherschultz.net] 
Sent: Sunday, August 27, 2017 7:56 PM
To: users@tomcat.apache.org
Subject: Re: applicatio shared path is not working on tomcat8 version

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Naga,

On 8/25/17 2:37 PM, Naga Ramesh wrote:
> We have set the application shared class path on tomcat7 and it’s 
> working fine.
> 
> But same thing we have set the tomcat8 version, it’s not working and 
> geting the below errors please check and let me know the solution 
> please.

Did you read the migration guide?

> OS: windows:
> 
> 25-Aug-2017 23:58:40.282 WARNING [localhost-startStop-1] 
> org.apache.tomcat.util.scan.StandardJarScanner.scan Failed to scan 
> [file://msbpo120/config/workflow/] from classloader hierarchy
> 
> java.io.IOException
> 
> at
> org.apache.tomcat.util.scan.StandardJarScanner.process(StandardJarScan
ner.java:339)
>
> 
[...]
> Caused by: java.lang.IllegalArgumentException: URI has an authority 
> component
> 
> at java.io.File.(File.java:423)

Seems pretty straightforward: "file" URIs don't have a hostname; you have too 
many slashes.

What does your configuration look like? Your screenshot did not make it to the 
list.

- -chris
-BEGIN PGP SIGNATURE-
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQIcBAEBCAAGBQJZotZ2AAoJEBzwKT+lPKRYA/UP+wR7LfZwnKeGRfLtFCF9c/YS
CRBaI5VB+a8hTr4/P2F4TSpwb6oyVGrIbEEVE9dQMps1u0HaCXgzL0QAQZD2mEiC
09Nwa/y4k+i8SKx9tN1ScHXtSNjq4kzQuvDpzo/jpbVrv38Gg/cLTIN0tLXuzKBB
2YXZgrbYN1S22sufkEVIFVNRGG9PlZixTNjkTP93IlbWaE44kRidrEztgn6GxjKK
DN69CxZSk/KUe/3XRWBO6omWw/KI9TV+V2DXp2D9pa/W+vwiVkzneOa4JsvcDg1H
zpEJ5/bxsrUpJ8Uso0qhiIf0SKyNeWcdZUSrtTNUDIFBII+Avfetk1HBnM73SNf2
Oe9JTksQ52komeEkSpInkYv/Jh1hOXtDrVAXdnALumXYfbspAQxsXazRikc8D/ez
ZiBUXiiuPBQK1eWS6dX1tw700N6FXV7Kqw64ImpSOX6pOnwlcSn/N0Dl+arfdl/m
9dV39l9WFBHNlLA0o8I8bKJIhZrSkH2lN5Mxa2C2GAB0/yeTxwLMR1bK9GxFQKmB
Zxt/Z2HPPfTT6fZfJLu7MQdkSxkClnPivC3/dleiaQwzQTzAx3BF0pKX0dcVKbdy
vymye95/Iq9KLlzsXuJdluNL2tlJkPO3Zh+JxuRlYrIQhniWmj8kfmSc8x1LCA6K
KU3myOwUaxAQPKnC4yK2
=v9Sp
-END PGP SIGNATURE-

-
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



applicatio shared path is not working on tomcat8 version

2017-08-25 Thread Naga Ramesh
Hi Team,

 

We have set the application shared class path on tomcat7 and it's working
fine.

 

But same thing we have set the tomcat8 version, it's not working and geting
the below errors please check and let me know the solution please.

 

OS: windows:

 

 

25-Aug-2017 23:58:40.282 WARNING [localhost-startStop-1]
org.apache.tomcat.util.scan.StandardJarScanner.scan Failed to scan
[file://msbpo120/config/workflow/] from classloader hierarchy

java.io.IOException

at
org.apache.tomcat.util.scan.StandardJarScanner.process(StandardJarScanner.ja
va:339)

at
org.apache.tomcat.util.scan.StandardJarScanner.scan(StandardJarScanner.java:
245)

at
org.apache.catalina.startup.ContextConfig.processJarsForWebFragments(Context
Config.java:1887)

at
org.apache.catalina.startup.ContextConfig.webConfig(ContextConfig.java:1127)

at
org.apache.catalina.startup.ContextConfig.configureStart(ContextConfig.java:
779)

at
org.apache.catalina.startup.ContextConfig.lifecycleEvent(ContextConfig.java:
306)

at
org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSuppor
t.java:95)

at
org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java
:90)

at
org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:
5150)

at
org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:147)

at
org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:7
25)

at
org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:701)

at
org.apache.catalina.core.StandardHost.addChild(StandardHost.java:717)

at
org.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.java:587)

at
org.apache.catalina.startup.HostConfig$DeployDescriptor.run(HostConfig.java:
1798)

at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)

at java.util.concurrent.FutureTask.run(FutureTask.java:266)

at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:11
42)

at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:6
17)

at java.lang.Thread.run(Thread.java:745)

Caused by: java.lang.IllegalArgumentException: URI has an authority
component

at java.io.File.(File.java:423)

at
org.apache.tomcat.util.scan.StandardJarScanner.process(StandardJarScanner.ja
va:318)

... 19 more

 

 



 

Regards,

Naga



RE: tomcat 7, null tag attributes

2017-06-13 Thread Naga Ramesh
All,

As of now we are using the below parameters for tomcat8 version on production 
environment, please recheck and confirm, these are fine or anything need to add 
or change.

Please confirm me.

export CATALINA_OPTS="$CATALINA_OPTS -Xms1024m"
export CATALINA_OPTS="$CATALINA_OPTS -Xmx8192m"
export CATALINA_OPTS="$CATALINA_OPTS -server"
export JAVA_OPTS="$JAVA_OPTS  -Xverify:none"
export CATALINA_OPTS="$CATALINA_OPTS -XX:+TieredCompilation -XX:+AggressiveOpts 
-XX:+UseG1GC -XX:SurvivorRatio=1 -XX:NewRatio=2 -XX:MaxTenuringThreshold=15 
-XX:+UseTLAB
 -XX:G1HeapRegionSize=32m -XX:-UseAdaptiveSizePolicy -XX:MaxMetaspaceSize=512m 
-XX:-UseSplitVerifier "



-Original Message-
From: Chris Cheshire [mailto:yahoono...@gmail.com] 
Sent: Tuesday, June 13, 2017 7:58 PM
To: Tomcat Users List
Subject: Re: tomcat 7, null tag attributes

On Tue, Jun 6, 2017 at 2:29 PM, Mark Thomas  wrote:

> On 31/05/17 23:31, Chris Cheshire wrote:
> > I am using tomcat 7 on CentOS 7 and I need to pass a null value to 
> > tag attributes of type Long/Integer/Float, however it is *always* 
> > coerced to zero.
> >
> > <%@attribute name="parentId" required="true" rtexprvalue="true"
> > type="java.lang.Long" %>
> >
> > Changing required to false does nothing. I tried setting the system 
> > property org.apache.el.parser.COERCE_TO_ZERO to false in tomcat.conf 
> > (-Dorg.apache.el.parser.COERCE_TO_ZERO=false with my other 
> > JAVA_OPTS)
> but
> > this does nothing.
>
> As expected. That system property only affects evaluation of EL 
> expressions.
>
>
But isn't  evaluation of an EL expression? Why is it 
treated differently than the evaluation of ${val} when it is used in the same 
scope as it is declared/assigned?

For instance, this tests in a JSP :


l is null

will succeed.

The moment I pass l into a tag and try the exact same evaluation inside, it 
fails because it has been coerced to 0.


>
> > How do I pass a null Long/Float/Integer as a tag attribute and have 
> > it
> kept
> > as null and not turned into an incorrect value?
>
> Use parentId="<%=null%>" rather than parentId=""
>
> Ugly, but it does the job. Scriplets aren't coerced.
>
> Mark
>


I can't use that because I'm not trying to pass the value null, rather a 
variable that possibly equates to null.

Also, if I have a custom bean

public class Foo {
  private Long val;

  public Foo() { }
  public Long getVal() { return val; }
  public void setVal(Long val) { this.val = val; } }

and I pass an instance of Foo into a tag, then val stays as null.

It seems the only solutions are to use a sentinel value that "shouldn't"
get used (cringeworthy in its own right), or to wrap everything in a custom 
bean (also extremely ugly).

I'm bewildered at why tomcat operates this way when it comes to Numbers and 
Strings. Why is it insistent on coercion when null and zero are absolutely not 
the same value.  If this is because of autoboxing, then isn't that a bug? A 
long is not a Long, and when tag attributes must be objects and not atomic 
types, shouldn't they be treated accordingly?


Chris


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



Re: Tomcat Auto Shutdown issues

2017-04-29 Thread Naga Ramesh
Naveen,

Can u provide the setenv changes and total system RAM and free RAM output
for need to investigation

Regards,
Ramesh
On Apr 29, 2017 8:53 PM, "Naveen Nandyala - Vendor" <
naveen.nandy...@walmart.com> wrote:

> Hi Team,
>
> We are using Tomcat "7.0.61.0", and running on SUSE Linux
> Enterprise Server 11 (x86_64), Version 11, and PatchLevel 3.  Our tomcat
> instance is going down due to below message, and its not a normal shutdown
> we are not sure why and who is causing to throw this messages and causing
> tomcat instance go down.  Can anyone provide some inputs for cause of this
> and how can we debug what is causing.
>
> Below is op from catalina logs.
>
>
> Apr 26, 2017 12:38:41 PM org.apache.coyote.AbstractProtocol pause
> INFO: Pausing ProtocolHandler ["http-nio-61034"]
> Apr 26, 2017 12:38:41 PM org.apache.catalina.core.StandardService
> stopInternal
> INFO: Stopping service Catalina
> Apr 26, 2017 12:38:52 PM org.apache.catalina.loader.WebappClassLoader
> clearReferencesJdbc
> SEVERE: The web application [/MainframeJobRequest] registered the JDBC
> driver [com.ibm.db2.jcc.DB2Driver] but failed to unregister it when the web
> application was stopped. To prevent a memory leak
> , the JDBC Driver has been forcibly unregistered.
> Apr 26, 2017 12:38:52 PM org.apache.coyote.AbstractProtocol stop
> INFO: Stopping ProtocolHandler ["http-nio-61034"]
> Apr 26, 2017 12:38:52 PM org.apache.coyote.AbstractProtocol destroy
>
>
>
> Warm Regards,
> Naveen Kumar Reddy N
>
>
>


RE: + character is always encoded in url path after request dispatch since #59317

2017-04-24 Thread Naga Ramesh
Thanks for providing the information & confirm me what are all the details 
required from my end.

Many times we are facing the same issues with the same revision tomcat setup 
only, PFA e-mail for your ref:

Regards,
Naga Ramesh R
9972229728

-Original Message-
From: Mark Thomas [mailto:ma...@apache.org] 
Sent: Monday, April 24, 2017 5:54 PM
To: Tomcat Users List
Subject: Re: + character is always encoded in url path after request dispatch 
since #59317

On 21/04/17 20:54, Mark Thomas wrote:
> On 21/04/17 17:27, Tobias Brennecke wrote:
> 
> 
> 
>> My question is whether this behavior is intended or if this is a bug.
> 
> That looks like a bug to me.
> 
> We need to go through and check all the places URLs are being encoding 
> and check it is being done correctly.

This is now complete for 9.0.x, 8.5.x, 8.0.x and 7.0.x.

> I am concerned that fixing this may break apps that rely on the broken 
> behaviour. We might need to provide some configuration to work around this.

I haven't provided any configuration options yet. Any issues will be considered 
on a case by case basis.

Mark


> 
>> As I'm a native German speaker, I apologize for any grammar mistakes 
>> or misspellings. Thank you for your efforts and patience while 
>> reading this mail.
> 
> No need to apologise. I had no idea you weren't a native English 
> speaker (I am) until I read that last sentence.
> 
> Kind regards,
> 
> Mark
> 
> 
> -
> 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
--- Begin Message ---
Tomcat Team,

 

Always we are getting the below mentioned errors, please check ASAP and
guide me if anything missing from our end, this is very urgent, please
respond asap.

 

Tomcat Version: apache-tomcat-8.0.33

Java Version: "1.8.0_77"

 

Setenv.sh file setting:

 

export JAVA_OPTS="$JAVA_OPTS -DR_E_T_A_P_P"

export CATALINA_OPTS="$CATALINA_OPTS -Xms1024m"

export CATALINA_OPTS="$CATALINA_OPTS -Xmx4196m"

#export CATALINA_OPTS="$CATALINA_OPTS -Xss64m"

export CATALINA_OPTS="$CATALINA_OPTS -server"

export CATALINA_OPTS="$CATALINA_OPTS -XX:+TieredCompilation
-XX:+AggressiveOpts -XX:+UseG1GC -XX:SurvivorRatio=1 -XX:NewRatio=2
-XX:MaxTenuringThreshold=15 -XX:-UseAda

ptiveSizePolicy -XX:+HeapDumpOnOutOfMemoryError -XX:MaxMetaspaceSize=512m
-XX:-UseSplitVerifier -noverify"

export LD_LIBRARY_PATH=/usr/lib64/

 

 

Errors:

 

24-Apr-2017 12:16:18.701 INFO [main]
org.apache.catalina.core.StandardService.startInternal Starting service
Catalina

24-Apr-2017 12:16:18.701 INFO [main]
org.apache.catalina.core.StandardEngine.startInternal Starting Servlet
Engine: rafg

24-Apr-2017 12:16:18.707 INFO [localhost-startStop-1]
org.apache.catalina.startup.HostConfig.deployDirectory Deploying web
application directory /opt/install/ra6.6/apache-tomcat-8.0.33/webapps/ROOT

24-Apr-2017 12:16:31.198 SEVERE [localhost-startStop-1]
org.apache.catalina.core.ContainerBase.addChildInternal
ContainerBase.addChild: start:

org.apache.catalina.LifecycleException: Failed to start component
[StandardEngine[Catalina].StandardHost[localhost].StandardContext[]]

at
org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:153)

at
org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:7
25)

at
org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:701)

at
org.apache.catalina.core.StandardHost.addChild(StandardHost.java:717)

at
org.apache.catalina.startup.HostConfig.deployDirectory(HostConfig.java:1092)

at
org.apache.catalina.startup.HostConfig$DeployDirectory.run(HostConfig.java:1
834)

at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)

at java.util.concurrent.FutureTask.run(FutureTask.java:266)

at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:11
42)

at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:6
17)

at java.lang.Thread.run(Thread.java:745)

Caused by: java.lang.IllegalStateException: Unable to complete the scan for
annotations for web application [] due to a StackOverflowError. Possible
root causes include a too low setting for -Xss and illegal cyclic
inheritance dependencies. The class hierarchy being processed was
[org.bouncycastle.asn1.ASN1EncodableVector->org.bouncycastle.asn1.DEREncodab
leVector->org.bouncycastle.asn1.ASN1EncodableVector]

at
org.apache

RE: needed your help very urgent

2017-04-24 Thread Naga Ramesh
We need solution for this issue, please guide to us.

-Original Message-
From: Mark Thomas [mailto:ma...@apache.org] 
Sent: Monday, April 24, 2017 3:11 PM
To: Tomcat Users List
Subject: Re: needed your help very urgent

On 24/04/2017 10:22, Naga Ramesh wrote:



> Caused by: java.lang.IllegalStateException: Unable to complete the 
> scan for annotations for web application [] due to a 
> StackOverflowError. Possible root causes include a too low setting for 
> -Xss and illegal cyclic inheritance dependencies. The class hierarchy 
> being processed was 
> [org.bouncycastle.asn1.ASN1EncodableVector->org.bouncycastle.asn1.DERE
> ncodab
> leVector->org.bouncycastle.asn1.ASN1EncodableVector]

What isn't clear?

Where that cyclic dependency came from is a whole different questions. I
don't see any hint of it in the bouncy castle source.

Mark

-
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



needed your help very urgent

2017-04-24 Thread Naga Ramesh
   at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)

at java.util.concurrent.FutureTask.run(FutureTask.java:266)

at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:11
42)

at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:6
17)

at java.lang.Thread.run(Thread.java:745)

 

24-Apr-2017 12:16:31.200 INFO [localhost-startStop-1]
org.apache.catalina.startup.HostConfig.deployDirectory Deployment of web
application directory /opt/install/ra6.6/apache-tomcat-8.0.33/webapps/ROOT
has finished in 12,493 ms

24-Apr-2017 12:16:31.204 INFO [main]
org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler
["http-apr-0.0.0.0-8080"]

24-Apr-2017 12:16:31.206 INFO [main]
org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler
["ajp-apr-7002"]

24-Apr-2017 12:16:31.207 INFO [main]
org.apache.catalina.startup.Catalina.start Server startup in 12648 ms

 

Regards,

Naga Ramesh