Re: Information about incident ID 2205106170494020972

[Theo Sweeny]

Hello Ivan,

From: John D. Ament 
Sent: 05 April 2016 03:11
To: Tomcat Users List
Subject: Re: Information about incident ID 2205106170494020972

Is it at all possible that you have some network level security that's
blocking your access to this port?

On Mon, Apr 4, 2016 at 10:03 PM Yin, Ivan  wrote:

> Hi,
>
> I am sure this error message doesn't come from that webapp since there is
> no "incident ID" in the webapp.
> In addition, I searched this error in google and I found a lot of similar
> error messages coming from different webapps deployed on tomcat so I
> thought it might come from Tomcat.
>
> The original error is:
>
> This page can't be displayed. Contact support for additional information.
> The incident ID is: N/A.
>
> I found the following message in http trace:
>
> This page can't be displayed. Contact support for additional information.
> The incident ID is: 2205106170494020972.
>
> May I know if there is a concept called "incident ID" in tomcat?
>
> Regards,
> Ivan
>
> -邮件原件-
> 发件人: Caldarale, Charles R [mailto:chuck.caldar...@unisys.com]
> 发送时间: 2016年4月5日 9:38
> 收件人: Tomcat Users List 
> 主题: RE: Information about incident ID 2205106170494020972
>
> > From: Yin, Ivan [mailto:ivan@sap.com]
> > Subject: Information about incident ID 2205106170494020972
>
> > When I tried to click one button in the web application deployed in
> Tomcat 7, it throws
> > an error message as below:
>
> > This page can't be displayed. Contact support for additional information.
> > The incident ID is: 2205106170494020972.
>
> > May I know what is the meaning of this incident ID and how I can solve
> this issue?
>
> The message does not come from Tomcat itself, but most likely a webapp
> deployed under Tomcat.  As the message says, you'll need to contact the
> support personnel for the webapp.
>
>  - Chuck

That response looks like an F5 firewall response message.

Usually this happens due to the web service inadvertently submitting an attack 
/ illegal signature due to -

Header size, number of headers, restricted header type, restricted verb or and 
body size.

Speak with the guys that manage the F5, give them the message ID and they will 
pin point the exact issue in the F5 logs.

Theo
Avios Group (AGL) Ltd is a limited company registered in England (registered 
number 2260073 and VAT number 512566754) whose registered address is Astral 
Towers, Betts Way, London Road, Crawley, West Sussex RH10 9XY . Avios Group 
(AGL) Limited is part of the IAG group of companies This email and any files 
transmitted with it are confidential and intended solely for the use of the 
individual or entity to whom they are addressed. If you have received this 
email in error please notify the system manager.

Re: Tomcat 8 Connection Reset Issue

[Theo Sweeny]

Hi Chris,

From: Christopher Schultz <ch...@christopherschultz.net>
Sent: 29 March 2016 16:48
To: Tomcat Users List
Subject: Re: Tomcat 8 Connection Reset Issue

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Theo,

On 3/29/16 2:55 AM, Theo Sweeny wrote:
> Yes - that does look like a spring connect timeout - which then
> passes back to java.net.SocketException: Connection reset. So
> either the client or the server is resetting before the connection
> can complete.
>
> The only system change to coincide with these connection resets is
> the new connection pool config as listed above. This implies that
> there is some conflict within the datasource config.

I don't believe that's the case, unless you are using the same port
numbers for both your JDBC connections and whatever other component is
failing. Have you tried reverting the JNDI configuration only?

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

iEYEARECAAYFAlb6o84ACgkQ9CaO5/Lv0PC75QCgiNExQYWamSs9kmnZIoEZEnMP
3FcAoLIBEzB9NpLbvbjwqHH5wdQ/CIe7
=X5ZC
-END PGP SIGNATURE-

Yes I rolled back the datasource configs but the problem persisted.

The issue resides with the F5 firewall hanging every other request. When the F5 
is removed from the network routing, the connection reset issue resolves itself.

Thanks for the help!

Theo

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

Avios Group (AGL) Ltd is a limited company registered in England (registered 
number 2260073 and VAT number 512566754) whose registered address is Astral 
Towers, Betts Way, London Road, Crawley, West Sussex RH10 9XY . Avios Group 
(AGL) Limited is part of the IAG group of companies This email and any files 
transmitted with it are confidential and intended solely for the use of the 
individual or entity to whom they are addressed. If you have received this 
email in error please notify the system manager.

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

Re: Tomcat 8 Connection Reset Issue

[Theo Sweeny]

Hi Chris,


From: Christopher Schultz <ch...@christopherschultz.net>
Sent: 24 March 2016 19:42
To: Tomcat Users List
Subject: Re: Tomcat 8 Connection Reset Issue

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Theo,

On 3/24/16 1:19 PM, Theo Sweeny wrote:
> Hello - we are running Tomcat v8.0.21 on RH7 with Java7.
>
> Recently we changed the datasource's to use connection pooling but
> as a result we are seeing connection timeouts in the logs as seen
> here -
>
> 2016-03-24 16:27:36,638 14321113 [http-nio-20180-exec-3] INFO
> org.springframework.security.oauth2.provider.endpoint.TokenEndpoint
>
>
Correlation-Identifier=77063426-8942-4259-aafd-cd9bc1d03305,
> Timestamp=2016-03-24T14:54:46.084Z - Handling error:
> ResourceAccessException, I/O error on POST request for
> "https://localhost:8080/membership/programmes/ATRP/member-identificati
on":Connection
>
>
reset; nested exception is java.net.SocketException: Connection
> reset

That looks like an error with a Spring-related component, not Tomcat.
(Right?). There are plenty of folks here who might be able to answer
this question, but I think this is actually off-topic for this list.
(No problem; carry on. Just pointing it out).

> The timeouts occur about every 1 in 3 attempts.
>
>
> Here is the new datasource config -
>
>
>  factory="org.apache.tomcat.jdbc.pool.DataSourceFactory"
> type="javax.sql.DataSource"
> driverClassName="oracle.jdbc.OracleDriver"
> url="jdbc:oracle:thin:@myhost:1521:MYSID" username="MYUSER"
> password="x" removeAbandoned="True"
> removeAbandonedTimeout="30" logAbandoned="True"
> abandonWhenPercentageFull="0" testOnBorrow="True"
> testOnReturn="False" testWhileIdle="True" maxActive="32"
> initialSize="8" maxIdle="8" minIdle="8"
> minEvictableIdleTimeMillis="15000" validationQuery="select 1 from
> dual" validationInterval="15000" validationQueryTimeout="15"
> timeBetweenEvictionRunsMillis="15000" logValidationErrors="True"
> jdbcInterceptors="ConnectionState;StatementFinalizer;SlowQueryReport(t
hreshold=1500);QueryTimeoutInterceptor(queryTimeout=10),ResetAbandonedTi
mer"
>
>
maxWait="-1"/>
>
> Are there any conflicts within this config that could be resulting
> in this issue?

I don't believe your JNDI DataSource has anything to do with making
outgoing connections to OAuth providers...

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

iEYEARECAAYFAlb0Qx0ACgkQ9CaO5/Lv0PA7KACfYVLubbNfIxKrInh9SNwY/JHf
h+kAnRRevkPjZBdCl0RD53QdtsndtXGe
=h3bQ
-END PGP SIGNATURE-

Thanks for the replay.

Yes - that does look like a spring connect timeout - which then passes back to 
java.net.SocketException: Connection reset. So either the client or the server 
is resetting before the connection can complete.

The only system change to coincide with these connection resets is the new 
connection pool config as listed above. This implies that there is some 
conflict within the datasource config.

Theo
Avios Group (AGL) Ltd is a limited company registered in England (registered 
number 2260073 and VAT number 512566754) whose registered address is Astral 
Towers, Betts Way, London Road, Crawley, West Sussex RH10 9XY . Avios Group 
(AGL) Limited is part of the IAG group of companies This email and any files 
transmitted with it are confidential and intended solely for the use of the 
individual or entity to whom they are addressed. If you have received this 
email in error please notify the system manager.

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

Tomcat 8 Connection Reset Issue

[Theo Sweeny]

Hello - we are running Tomcat v8.0.21 on RH7 with Java7.


Recently we changed the datasource's to use connection pooling but as a result 
we are seeing connection timeouts in the logs as seen here -


2016-03-24 16:27:36,638 14321113 [http-nio-20180-exec-3] INFO  
org.springframework.security.oauth2.provider.endpoint.TokenEndpoint 
Correlation-Identifier=77063426-8942-4259-aafd-cd9bc1d03305, 
Timestamp=2016-03-24T14:54:46.084Z - Handling error: ResourceAccessException, 
I/O error on POST request for 
"https://localhost:8080/membership/programmes/ATRP/member-identification":Connection
 reset; nested exception is java.net.SocketException: Connection reset


The timeouts occur about every 1 in 3 attempts.


Here is the new datasource config -




Are there any conflicts within this config that could be resulting in this 
issue?


Thank you,


Theo

Avios Group (AGL) Ltd is a limited company registered in England (registered 
number 2260073 and VAT number 512566754) whose registered address is Astral 
Towers, Betts Way, London Road, Crawley, West Sussex RH10 9XY . Avios Group 
(AGL) Limited is part of the IAG group of companies This email and any files 
transmitted with it are confidential and intended solely for the use of the 
individual or entity to whom they are addressed. If you have received this 
email in error please notify the system manager.

Re: Tomcat 8 Hung State

[Theo Sweeny]

Hi Mark,


From: Mark Thomas <ma...@apache.org>
Sent: 17 March 2016 17:36
To: Tomcat Users List
Subject: Re: Tomcat 8 Hung State

On 17 March 2016 16:13:28 GMT+00:00, Theo Sweeny <theo.swe...@avios.com> wrote:
>Hello - yesterday Tomcat 8 went into a hung state, because an external
>API went offline.
>
>
>Eventually the external service was restored but Tomcat was unable to
>recovery from it.
>
>
>When a new connection is sent to Tomcat the connection hangs as no
>additional thread can be allocated to the new request.
>
>
>Here is an example of the log -
>
>
>17-Mar-2016 15:53:36.671 WARNING
>[ContainerBackgroundProcessor[StandardEngine[Catalina].StandardHost[localhost]]]
>org.apache.catalina.valves.StuckThreadDetectionValve.notifyStuckThreadDetected
>Thread "http-nio-10180-exec-40" (id=422) has been active for 33,717
>milliseconds (since 3/17/16 3:53 PM) to serve the same request for
>http://localhost:10180/retrieve-1.2/retrieve-prices and may be stuck
>(configured threshold for this StuckThreadDetectionValve is 30
>seconds). There is/are 1 thread(s) in total that are monitored by this
>Valve and may be stuck.
> java.lang.Throwable
>at sun.misc.Unsafe.park(Native Method)
>   at java.util.concurrent.locks.LockSupport.park(LockSupport.java:186)
>at java.util.concurrent.FutureTask.awaitDone(FutureTask.java:425)
>at java.util.concurrent.FutureTask.get(FutureTask.java:187)
>at
>com.spring.application.repository.product.price.IlogPriceRepository.getPrices_aroundBody0(IlogPriceRepository.java:104)
>at
>com.spring.application.repository.product.price.IlogPriceRepository$AjcClosure1.run(IlogPriceRepository.java:1)
>at
>org.aspectj.runtime.reflect.JoinPointImpl.proceed(JoinPointImpl.java:149)
>at
>com.spring.framework.aspects.LoggingAspect.logMethodEntryAndExit(LoggingAspect.java:61)
>at
>com.spring.application.repository.product.price.IlogPriceRepository.getPrices(IlogPriceRepository.java:86)
>at
>com.spring.application.repository.product.price.IlogPriceRepository$$FastClassBySpringCGLIB$$142c62f1.invoke()
>at
>org.springframework.cglib.proxy.MethodProxy.invoke(MethodProxy.java:204)
>at
>org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.invokeJoinpoint(CglibAopProxy.java:717)
>at
>org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:157)
>at
>org.springframework.dao.support.PersistenceExceptionTranslationInterceptor.invoke(PersistenceExceptionTranslationInterceptor.java:136)
>at
>org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179)
>at
>org.springframework.aop.framework.CglibAopProxy$DynamicAdvisedInterceptor.intercept(CglibAopProxy.java:653)
>at
>com.spring.application.repository.product.price.IlogPriceRepository$$EnhancerBySpringCGLIB$$4fdb7af0.getPrices()
>at
>com.spring.application.service.product.price.RealTimePriceApplicationService.getPrices_aroundBody0(RealTimePriceApplicationService.java:48)
>at
>com.spring.application.service.product.price.RealTimePriceApplicationService$AjcClosure1.run(RealTimePriceApplicationService.java:1)
>at
>org.aspectj.runtime.reflect.JoinPointImpl.proceed(JoinPointImpl.java:149)
>at
>com.spring.framework.aspects.LoggingAspect.logMethodEntryAndExit(LoggingAspect.java:61)
>at
>com.spring.application.service.product.price.RealTimePriceApplicationService.getPrices(RealTimePriceApplicationService.java:47)
>at
>com.spring.application.service.product.price.GetPriceApplicationController.getPrices_aroundBody0(GetPriceApplicationController.java:74)
>at
>com.spring.application.service.product.price.GetPriceApplicationController$AjcClosure1.run(GetPriceApplicationController.java:1)
>at
>org.aspectj.runtime.reflect.JoinPointImpl.proceed(JoinPointImpl.java:149)
>at
>com.spring.framework.aspects.LoggingAspect.logMethodEntryAndExit(LoggingAspect.java:61)
>at
>com.spring.application.service.product.price.GetPriceApplicationController.getPrices(GetPriceApplicationController.java:70)
>at sun.reflect.GeneratedMethodAccessor1306.invoke(Unknown Source)
>at
>sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>at java.lang.reflect.Method.invoke(Method.java:606)
>at
>org.springframework.web.method.support.InvocableHandlerMethod.doInvoke(InvocableHandlerMethod.java:221)
>at
>org.springframework.web.method.support.InvocableHandlerMethod.invokeForRequest(InvocableHandlerMethod.java:137)
>at
>org.springframework.web.servlet.mvc.method.annotation.ServletInvocableHandlerMethod.invokeAndHandle(ServletInvocableHandlerMethod.java:110)
>at
>org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.

Tomcat 8 Hung State

[Theo Sweeny]

Hello - yesterday Tomcat 8 went into a hung state, because an external API went 
offline.


Eventually the external service was restored but Tomcat was unable to recovery 
from it.


When a new connection is sent to Tomcat the connection hangs as no additional 
thread can be allocated to the new request.


Here is an example of the log -


17-Mar-2016 15:53:36.671 WARNING 
[ContainerBackgroundProcessor[StandardEngine[Catalina].StandardHost[localhost]]]
 org.apache.catalina.valves.StuckThreadDetectionValve.notifyStuckThreadDetected 
Thread "http-nio-10180-exec-40" (id=422) has been active for 33,717 
milliseconds (since 3/17/16 3:53 PM) to serve the same request for 
http://localhost:10180/retrieve-1.2/retrieve-prices and may be stuck 
(configured threshold for this StuckThreadDetectionValve is 30 seconds). There 
is/are 1 thread(s) in total that are monitored by this Valve and may be stuck.
 java.lang.Throwable
at sun.misc.Unsafe.park(Native Method)
at java.util.concurrent.locks.LockSupport.park(LockSupport.java:186)
at java.util.concurrent.FutureTask.awaitDone(FutureTask.java:425)
at java.util.concurrent.FutureTask.get(FutureTask.java:187)
at 
com.spring.application.repository.product.price.IlogPriceRepository.getPrices_aroundBody0(IlogPriceRepository.java:104)
at 
com.spring.application.repository.product.price.IlogPriceRepository$AjcClosure1.run(IlogPriceRepository.java:1)
at org.aspectj.runtime.reflect.JoinPointImpl.proceed(JoinPointImpl.java:149)
at 
com.spring.framework.aspects.LoggingAspect.logMethodEntryAndExit(LoggingAspect.java:61)
at 
com.spring.application.repository.product.price.IlogPriceRepository.getPrices(IlogPriceRepository.java:86)
at 
com.spring.application.repository.product.price.IlogPriceRepository$$FastClassBySpringCGLIB$$142c62f1.invoke()
at org.springframework.cglib.proxy.MethodProxy.invoke(MethodProxy.java:204)
at 
org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.invokeJoinpoint(CglibAopProxy.java:717)
at 
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:157)
at 
org.springframework.dao.support.PersistenceExceptionTranslationInterceptor.invoke(PersistenceExceptionTranslationInterceptor.java:136)
at 
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179)
at 
org.springframework.aop.framework.CglibAopProxy$DynamicAdvisedInterceptor.intercept(CglibAopProxy.java:653)
at 
com.spring.application.repository.product.price.IlogPriceRepository$$EnhancerBySpringCGLIB$$4fdb7af0.getPrices()
at 
com.spring.application.service.product.price.RealTimePriceApplicationService.getPrices_aroundBody0(RealTimePriceApplicationService.java:48)
at 
com.spring.application.service.product.price.RealTimePriceApplicationService$AjcClosure1.run(RealTimePriceApplicationService.java:1)
at org.aspectj.runtime.reflect.JoinPointImpl.proceed(JoinPointImpl.java:149)
at 
com.spring.framework.aspects.LoggingAspect.logMethodEntryAndExit(LoggingAspect.java:61)
at 
com.spring.application.service.product.price.RealTimePriceApplicationService.getPrices(RealTimePriceApplicationService.java:47)
at 
com.spring.application.service.product.price.GetPriceApplicationController.getPrices_aroundBody0(GetPriceApplicationController.java:74)
at 
com.spring.application.service.product.price.GetPriceApplicationController$AjcClosure1.run(GetPriceApplicationController.java:1)
at org.aspectj.runtime.reflect.JoinPointImpl.proceed(JoinPointImpl.java:149)
at 
com.spring.framework.aspects.LoggingAspect.logMethodEntryAndExit(LoggingAspect.java:61)
at 
com.spring.application.service.product.price.GetPriceApplicationController.getPrices(GetPriceApplicationController.java:70)
at sun.reflect.GeneratedMethodAccessor1306.invoke(Unknown Source)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at 
org.springframework.web.method.support.InvocableHandlerMethod.doInvoke(InvocableHandlerMethod.java:221)
at 
org.springframework.web.method.support.InvocableHandlerMethod.invokeForRequest(InvocableHandlerMethod.java:137)
at 
org.springframework.web.servlet.mvc.method.annotation.ServletInvocableHandlerMethod.invokeAndHandle(ServletInvocableHandlerMethod.java:110)
at 
org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.invokeHandleMethod(RequestMappingHandlerAdapter.java:777)
at 
org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.handleInternal(RequestMappingHandlerAdapter.java:706)
at 
org.springframework.web.servlet.mvc.method.AbstractHandlerMethodAdapter.handle(AbstractHandlerMethodAdapter.java:85)
at 
org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:943)
at 

Re: Starting and stopping contexts programmatically

[Theo Sweeny]

Hi James,


From: Mark Thomas 
Sent: 15 March 2016 09:21
To: Tomcat Users List
Subject: Re: Starting and stopping contexts programmatically

On 15/03/2016 00:25, James H. H. Lampert wrote:
> The only ways I know of to start and stop individual webapp contexts is
> to (1) start and stop them from the manager, or (2) start and stop
> Tomcat itself.
>
> Is there a way, from the back end, to start and stop individual contexts?

You could do that via JMX.

Mark


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


You can also call Tomcat Manager via Curl -

curl -X GET 
http://:@:/manager/text/start?path=/%23%23v1.0.9

The %23 implies #

E.G - my-web-service##v1.0.9

Theo
Avios Group (AGL) Ltd is a limited company registered in England (registered 
number 2260073 and VAT number 512566754) whose registered address is Astral 
Towers, Betts Way, London Road, Crawley, West Sussex RH10 9XY . Avios Group 
(AGL) Limited is part of the IAG group of companies This email and any files 
transmitted with it are confidential and intended solely for the use of the 
individual or entity to whom they are addressed. If you have received this 
email in error please notify the system manager.

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

Re: Tomcat 8 Shared Classloader

[Theo Sweeny]

Hi Mark,

From: Mark Thomas <ma...@apache.org>
Sent: 10 March 2016 10:22
To: Tomcat Users List
Subject: Re: Tomcat 8 Shared cCassloader

On 10/03/2016 10:19, Theo Sweeny wrote:
> Hello - I've recently noticed that there is no reference to shared.loader in 
> this Tomcat How To guide seen here -
>
> https://tomcat.apache.org/tomcat-8.0-doc/class-loader-howto.html
>
> Has the shared.loader property from within catalina.properties been 
> deprecated?

No. It was removed because it was rarely used / needed.

> If so - should shared.loader resources now be loaded via the common.loader 
> instead?

You can re-introduce the shared loader (and the catalina loader) if you
want to.

Mark

Thanks for the heads up.

The motivation for asking this question is that we do have issues with web apps 
classes not being removed cleanly from memory after they are undeployed, which 
eventually results Perm Gen errors.

Is it safe to say that using shared.loader would not contribute to this issue?

Theo


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

Avios Group (AGL) Ltd is a limited company registered in England (registered 
number 2260073 and VAT number 512566754) whose registered address is Astral 
Towers, Betts Way, London Road, Crawley, West Sussex RH10 9XY . Avios Group 
(AGL) Limited is part of the IAG group of companies This email and any files 
transmitted with it are confidential and intended solely for the use of the 
individual or entity to whom they are addressed. If you have received this 
email in error please notify the system manager.

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

Tomcat 8 Shared cCassloader

[Theo Sweeny]

Hello - I've recently noticed that there is no reference to shared.loader in 
this Tomcat How To guide seen here -

https://tomcat.apache.org/tomcat-8.0-doc/class-loader-howto.html

Has the shared.loader property from within catalina.properties been deprecated?

If so - should shared.loader resources now be loaded via the common.loader 
instead?


Thank you,


Theo

Avios Group (AGL) Ltd is a limited company registered in England (registered 
number 2260073 and VAT number 512566754) whose registered address is Astral 
Towers, Betts Way, London Road, Crawley, West Sussex RH10 9XY . Avios Group 
(AGL) Limited is part of the IAG group of companies This email and any files 
transmitted with it are confidential and intended solely for the use of the 
individual or entity to whom they are addressed. If you have received this 
email in error please notify the system manager.

RE: Debugging Apache Tomcat

[Theo Sweeny]

Hi Chiranga,

-Original Message-
From: Chiranga Alwis [mailto:chirangaal...@gmail.com]
Sent: 25 February 2016 07:03
To: Tomcat Users List 
Subject: Debugging Apache Tomcat

Hi,

please refer this post regarding Tomcat debugging issue:


http://stackoverflow.com/questions/35620472/debug-apache-tomcat

In the setenv.sh the properties can be set and then do one export via 
CATALINA_OPTS as seen here -

JPDA_OPTS="-agentlib:jdwp=transport=dt_socket,address=10094,server=y,suspend=n"

export CATALINA_OPTS ="$TAG $MEM_ARGS $APP_ARGS $JPDA_OPTS"

Then start Tomcat without the jdpa option on the start command -

bin/catalina.sh start

Theo
Avios Group (AGL) Ltd is a limited company registered in England (registered 
number 2260073 and VAT number 512566754) whose registered address is Astral 
Towers, Betts Way, London Road, Crawley, West Sussex RH10 9XY . Avios Group 
(AGL) Limited is part of the IAG group of companies This email and any files 
transmitted with it are confidential and intended solely for the use of the 
individual or entity to whom they are addressed. If you have received this 
email in error please notify the system manager.

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

Tomcat 8 Chunked Encoding

[Theo Sweeny]

Hello All - I'm running Tomcat 8.0.21 on Linux 64x and there is a recent issue 
where clients making requests and declaring the header - 
Transfer-Encoding:chunked, have their connections hang, with no obvious leads 
in the logs.

I'm aware that up to version 8.0.9 there was a Tomcat vulnerability with 
regards to this header type.

Could it be that there are legacy Tomcat security features that are causing the 
request to hang?

Theo

Avios Group (AGL) Ltd is a limited company registered in England (registered 
number 2260073 and VAT number 512566754) whose registered address is Astral 
Towers, Betts Way, London Road, Crawley, West Sussex RH10 9XY . Avios Group 
(AGL) Limited is part of the IAG group of companies This email and any files 
transmitted with it are confidential and intended solely for the use of the 
individual or entity to whom they are addressed. If you have received this 
email in error please notify the system manager.

RE: Tomcat 8 Application dispatcherServlet Stats

[Theo Sweeny]

Chris,

-Original Message-
From: Christopher Schultz [mailto:ch...@christopherschultz.net]
Sent: 25 January 2016 23:29
To: Tomcat Users List <users@tomcat.apache.org>
Subject: Re: Tomcat 8 Application dispatcherServlet Stats

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Theo,

On 1/25/16 4:12 AM, Theo Sweeny wrote:
> Hi Chris -
>
> On 1/14/16 5:53 AM, Theo Sweeny wrote:
>> Hello Kyohei,
>>
>> -Original Message- From: Kyohei Nakamura
>> [mailto:nakamura.kyohei@gmail.com] Sent: 14 January 2016
>> 09:59 To: Tomcat Users List <users@tomcat.apache.org> Subject:
>> Re: Tomcat 8 Application dispatcherServlet Stats
>>
>> What does "response time" mean?
>>
>> The "Processing time" include a time that is from the end of service
>> method of servlet instance until the end of
>> StandardWrapperValve#invoke().
>>
>>
>> 2016-01-14 17:27 GMT+09:00 Theo Sweeny <theo.swe...@avios.com>:
>>
>>> Hello Kyohei,
>>>
>>> -Original Message- From: Kyohei Nakamura
>>> [mailto:nakamura.kyohei@gmail.com] Sent: 14 January 2016
>>> 06:45 To: Tomcat Users List <users@tomcat.apache.org> Subject:
>>> Re: Tomcat 8 Application dispatcherServlet Stats
>>>
>>> Hello
>>>
>>> The "Processing time" metric represents the execution time of
>>> StandardWrapperValve#invoke(). This is the execution time of the
>>> servlet and filters. This value of "Processing time" is the total
>>> time of each request execution time.
>>>
>>> What is the dispatcherServlet? If dispatcherServlet accept all
>>> request as a front controller(like Spring's DispatcherServlet), then
>>> this value is the total execution time of all request that the
>>> context receive.
>>>
>>>
>>> 2016-01-13 20:19 GMT+09:00 Theo Sweeny
>>> <theo.swe...@avios.com>:
>>>
>>>> Hello - at the moment stats can be found for Tomcat 8 web services
>>>> using the manager UI /manager/status/all
>>>>
>>>> Is the "Processing time" metric found under dispatcherServlet [ / ]
>>>> subsection, the total time take to serve all requests, including
>>>> the response time for each request?
>>>>
>>>> Regards,
>>>>
>>>> Theo
>>>
>>> Does the total execution time for each request include the response
>>> time?
>>>
>>> Thank you,
>>>
>>> Theo
>>>
>>
>> I think indirectly you have answered my question. From a network
>> perspective you have the initial connection time to send the request
>> (request time), then you have the time to process the request, and
>> finally response time back to the client. Both the processing time
>> and response time for the purpose of this task are merged under the
>> umbrella of response time. So going full circle - the
>> dispatcherServlet Processing time fits the bill of response time.
>
> There is a case where this might not actually give you what you are
> looking for -- which sounds essentially like the amount of time the
> server spent processing that request.
>
> If StandardWrapperValve only times how long invoke() takes and (and I
> haven't read the code, so I'm not sure) some component in Tomcat
> executes *after* invoke() completes for the purposes of flushing any
> buffered data back to the client, then "Processing Time" may be off by
> the amount of time it takes Tomcat to flush those buffers back to the
> client. If you have big buffers or slow clients, this could add up
> quickly.
>
> -chris
>
> Thanks for the reply. I've done some further digging into the
> Application List Startup Time. Here is one example from the Tomcat
> Manager -
>
> localhost/account-information-bs-1.1##v1.1.1 Start time: Fri Jan 22
> 13:26:17 GMT 2016 Startup time: 33 ms TLD scan time: 0 ms
>
> When the startup time is compared back to the catalina.out log for the
> same webapp, the time is dramatically more (307,324 ms) as seen here -
>
> 22-Jan-2016 13:26:17.204 INFO [localhost-startStop-15]
> org.apache.catalina.startup.HostConfig.deployWAR Deployment of web
> application archive
> /opt/tomcat/webapps/account-information-bs-1.1##v1.1.1.war has
> finished in 307,324 ms
>
> Any ideas why such a difference exists?

The above is the time it takes to deploy the application, not the time it takes 
to service a request (or a whole bunch of requests over a period of time).

Maybe I don't understand your question?

- -chris

Sorry - I went off

RE: Tomcat 8 Application dispatcherServlet Stats

[Theo Sweeny]

Hi Chris -

On 1/14/16 5:53 AM, Theo Sweeny wrote:
> Hello Kyohei,
>
> -Original Message-
> From: Kyohei Nakamura [mailto:nakamura.kyohei@gmail.com]
> Sent: 14 January 2016 09:59
> To: Tomcat Users List <users@tomcat.apache.org>
> Subject: Re: Tomcat 8 Application dispatcherServlet Stats
>
> What does "response time" mean?
>
> The "Processing time" include a time that is from the end of service method 
> of servlet instance until the end of StandardWrapperValve#invoke().
>
>
> 2016-01-14 17:27 GMT+09:00 Theo Sweeny <theo.swe...@avios.com>:
>
>> Hello Kyohei,
>>
>> -Original Message-
>> From: Kyohei Nakamura [mailto:nakamura.kyohei@gmail.com]
>> Sent: 14 January 2016 06:45
>> To: Tomcat Users List <users@tomcat.apache.org>
>> Subject: Re: Tomcat 8 Application dispatcherServlet Stats
>>
>> Hello
>>
>> The "Processing time" metric represents the execution time of
>> StandardWrapperValve#invoke().
>> This is the execution time of the servlet and filters.
>> This value of "Processing time" is the total time of each request
>> execution time.
>>
>> What is the dispatcherServlet?
>> If dispatcherServlet accept all request as a front controller(like
>> Spring's DispatcherServlet), then this value is the total execution
>> time of all request that the context receive.
>>
>>
>> 2016-01-13 20:19 GMT+09:00 Theo Sweeny <theo.swe...@avios.com>:
>>
>>> Hello - at the moment stats can be found for Tomcat 8 web services
>>> using the manager UI /manager/status/all
>>>
>>> Is the "Processing time" metric found under dispatcherServlet [ / ]
>>> subsection, the total time take to serve all requests, including the
>>> response time for each request?
>>>
>>> Regards,
>>>
>>> Theo
>>
>> Does the total execution time for each request include the response time?
>>
>> Thank you,
>>
>> Theo
>>
>
> I think indirectly you have answered my question. From a network
> perspective you have the initial connection time to send the request
> (request time), then you have the time to process the request, and
> finally response time back to the client. Both the processing time and
> response time for the purpose of this task are merged under the
> umbrella of response time. So going full circle - the
> dispatcherServlet Processing time fits the bill of response time.

There is a case where this might not actually give you what you are looking for 
-- which sounds essentially like the amount of time the server spent processing 
that request.

If StandardWrapperValve only times how long invoke() takes and (and I haven't 
read the code, so I'm not sure) some component in Tomcat executes *after* 
invoke() completes for the purposes of flushing any buffered data back to the 
client, then "Processing Time" may be off by the amount of time it takes Tomcat 
to flush those buffers back to the client. If you have big buffers or slow 
clients, this could add up quickly.

-chris

Thanks for the reply. I've done some further digging into the Application List 
Startup Time. Here is one example from the Tomcat Manager -

localhost/account-information-bs-1.1##v1.1.1
Start time: Fri Jan 22 13:26:17 GMT 2016 Startup time: 33 ms TLD scan time: 0 ms

When the startup time is compared back to the catalina.out log for the same 
webapp, the time is dramatically more (307,324 ms) as seen here -

22-Jan-2016 13:26:17.204 INFO [localhost-startStop-15] 
org.apache.catalina.startup.HostConfig.deployWAR Deployment of web application 
archive /opt/tomcat/webapps/account-information-bs-1.1##v1.1.1.war has finished 
in 307,324 ms

Any ideas why such a difference exists?

Regards,

Theo

Avios Group (AGL) Ltd is a limited company registered in England (registered 
number 2260073 and VAT number 512566754) whose registered address is Astral 
Towers, Betts Way, London Road, Crawley, West Sussex RH10 9XY . Avios Group 
(AGL) Limited is part of the IAG group of companies This email and any files 
transmitted with it are confidential and intended solely for the use of the 
individual or entity to whom they are addressed. If you have received this 
email in error please notify the system manager.

RE: Tomcat 8 Application dispatcherServlet Stats

[Theo Sweeny]

Hello Kyohei,

-Original Message-
From: Kyohei Nakamura [mailto:nakamura.kyohei@gmail.com]
Sent: 14 January 2016 06:45
To: Tomcat Users List <users@tomcat.apache.org>
Subject: Re: Tomcat 8 Application dispatcherServlet Stats

Hello

The "Processing time" metric represents the execution time of 
StandardWrapperValve#invoke().
This is the execution time of the servlet and filters.
This value of "Processing time" is the total time of each request execution 
time.

What is the dispatcherServlet?
If dispatcherServlet accept all request as a front controller(like Spring's 
DispatcherServlet), then this value is the total execution time of all request 
that the context receive.


2016-01-13 20:19 GMT+09:00 Theo Sweeny <theo.swe...@avios.com>:

> Hello - at the moment stats can be found for Tomcat 8 web services
> using the manager UI /manager/status/all
>
> Is the "Processing time" metric found under dispatcherServlet [ / ]
> subsection, the total time take to serve all requests, including the
> response time for each request?
>
> Regards,
>
> Theo
> Avios Group (AGL) Ltd is a limited company registered in England
> (registered number 2260073 and VAT number 512566754) whose registered
> address is Astral Towers, Betts Way, London Road, Crawley, West Sussex
> RH10 9XY . Avios Group (AGL) Limited is part of the IAG group of
> companies This email and any files transmitted with it are
> confidential and intended solely for the use of the individual or entity to 
> whom they are addressed.
> If you have received this email in error please notify the system manager.
>

Does the total execution time for each request include the response time?

Thank you,

Theo

Avios Group (AGL) Ltd is a limited company registered in England (registered 
number 2260073 and VAT number 512566754) whose registered address is Astral 
Towers, Betts Way, London Road, Crawley, West Sussex RH10 9XY . Avios Group 
(AGL) Limited is part of the IAG group of companies This email and any files 
transmitted with it are confidential and intended solely for the use of the 
individual or entity to whom they are addressed. If you have received this 
email in error please notify the system manager.

RE: Tomcat 8 Application dispatcherServlet Stats

[Theo Sweeny]

Hello Kyohei,

-Original Message-
From: Kyohei Nakamura [mailto:nakamura.kyohei@gmail.com]
Sent: 14 January 2016 09:59
To: Tomcat Users List <users@tomcat.apache.org>
Subject: Re: Tomcat 8 Application dispatcherServlet Stats

What does "response time" mean?

The "Processing time" include a time that is from the end of service method of 
servlet instance until the end of StandardWrapperValve#invoke().


2016-01-14 17:27 GMT+09:00 Theo Sweeny <theo.swe...@avios.com>:

> Hello Kyohei,
>
> -Original Message-
> From: Kyohei Nakamura [mailto:nakamura.kyohei@gmail.com]
> Sent: 14 January 2016 06:45
> To: Tomcat Users List <users@tomcat.apache.org>
> Subject: Re: Tomcat 8 Application dispatcherServlet Stats
>
> Hello
>
> The "Processing time" metric represents the execution time of
> StandardWrapperValve#invoke().
> This is the execution time of the servlet and filters.
> This value of "Processing time" is the total time of each request
> execution time.
>
> What is the dispatcherServlet?
> If dispatcherServlet accept all request as a front controller(like
> Spring's DispatcherServlet), then this value is the total execution
> time of all request that the context receive.
>
>
> 2016-01-13 20:19 GMT+09:00 Theo Sweeny <theo.swe...@avios.com>:
>
> > Hello - at the moment stats can be found for Tomcat 8 web services
> > using the manager UI /manager/status/all
> >
> > Is the "Processing time" metric found under dispatcherServlet [ / ]
> > subsection, the total time take to serve all requests, including the
> > response time for each request?
> >
> > Regards,
> >
> > Theo
>
> Does the total execution time for each request include the response time?
>
> Thank you,
>
> Theo
>

I think indirectly you have answered my question. From a network perspective 
you have the initial connection time to send the request (request time), then 
you have the time to process the request, and finally response time back to the 
client. Both the processing time and response time for the purpose of this task 
are merged under the umbrella of response time. So going full circle - the 
dispatcherServlet Processing time fits the bill of response time.

Thanks for the help!

Theo
Avios Group (AGL) Ltd is a limited company registered in England (registered 
number 2260073 and VAT number 512566754) whose registered address is Astral 
Towers, Betts Way, London Road, Crawley, West Sussex RH10 9XY . Avios Group 
(AGL) Limited is part of the IAG group of companies This email and any files 
transmitted with it are confidential and intended solely for the use of the 
individual or entity to whom they are addressed. If you have received this 
email in error please notify the system manager.

Tomcat 8 Application dispatcherServlet Stats

[Theo Sweeny]

Hello - at the moment stats can be found for Tomcat 8 web services using the 
manager UI /manager/status/all

Is the "Processing time" metric found under dispatcherServlet [ / ] subsection, 
the total time take to serve all requests, including the response time for each 
request?

Regards,

Theo
Avios Group (AGL) Ltd is a limited company registered in England (registered 
number 2260073 and VAT number 512566754) whose registered address is Astral 
Towers, Betts Way, London Road, Crawley, West Sussex RH10 9XY . Avios Group 
(AGL) Limited is part of the IAG group of companies This email and any files 
transmitted with it are confidential and intended solely for the use of the 
individual or entity to whom they are addressed. If you have received this 
email in error please notify the system manager.

RE: Can tomcat serve MPI (parallel) applications?

[Theo Sweeny]

Hi Konstantin,

-Original Message-
From: Konstantin Kolinko [mailto:knst.koli...@gmail.com]
Sent: 27 November 2015 09:15
To: Tomcat Users List 
Subject: Re: Can tomcat serve MPI (parallel) applications?

2015-11-26 23:18 GMT+03:00 Martijn Slouter :
> Hello,
> I am looking for a solution for a tomcat container, which is supposed
> to serve a web application, which is using MPI (openmpi) internally.
> (The servlet is making JNI calls to C library functions. I have
> validated that this Java-MPI connection runs without problems when NOT
> using tomcat.)
>
> In catalina.sh, I have changed the lines which actually starts tomcat
>   eval "\"$_RUNJAVA\"" "\"$LOGGING_CONFIG\"" $LOGGING_MANAGER ...
> into the same command preceded by mpirun:
>   eval mpirun -n 2 "\"$_RUNJAVA\"" "\"$LOGGING_CONFIG\""
> $LOGGING_MANAGER ...
>
> However, in catalina.out I get errors like
>   "... java.net.BindException: Address already in use ..."
> This makes sense, because both MPI processes will try to bind to the
> same address.
>
> Is there any chance to have tomcat serve a web application which is
> using native MPI functions inside one of its servlets?
>
> I am using apache-tomcat-7.0.65 on Ubuntu 15.04.

What is your goal, your expectation of Tomcat? What these n instances should do 
that 1 instance cannot?

Is is possible to start several Tomcats with the same CATALINA_BASE in 
parallel, but you have to 1. Disable shutdown port (set port="-1" on  
element if I remember correctly)

It means that these Tomcats have to shut themselves down eventually (like 
explicitly calling System.exit()), or you have to kill them by sending a signal 
(knowing pid of the process).

2. Remove connectors, or disable them (port="-1" if I remember correctly), or 
configure them to autoselect a random port number (port="0" if I remember 
correctly)

A connector can be configured, reconfigured, started/stopped programmatically 
via JMX.

3. Do not perform any writing activity in CATALINA_BASE

- Do not deploy war files (so that Tomcat does not need to unpack them)
- Do not deploy any new applications while Tomcat is running. Turn off 
autoDeploy feature on Host. Do not use Tomcat Manager web application.

- Do not compile JSP pages. Turn them into servlets by precompiling them with 
Jasper JspC.

- Do not write serialized session data (configure  with pathname="").

- Turn off logging (or turn a deaf ear to it trying to concurrently write into 
the same log files).

Best regards,
Konstantin Kolinko

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


In reply to - " Is it possible to start several Tomcats with the same 
CATALINA_BASE in parallel, but you have to 1. Disable shutdown port (set 
port="-1" on  element if I remember correctly)"

The approach I've taken is to create a port standard for each JVM instance, 
where each protocol in use within the JVM has its own unique port number, this 
prevents conflict between multiple Tomcat instances.

E.G. Where there are four Tomcat instances calling shutdown -

tomcat0/conf/server.xml:
tomcat1/conf/server.xml:
tomcat2/conf/server.xml:
tomcat3/conf/server.xml:

The same approach applied for HTTP connector -

tomcat0/conf/server.xml:

RE: /manager/text/list

[Theo Sweeny]

Hi Chris,

-Original Message-
From: Chris Gamache [mailto:cgama...@gmail.com]
Sent: 22 October 2015 19:58
To: Tomcat Users List 
Subject: /manager/text/list

Hi all,

Using Tomcat 8 ...

Has anyone noticed that /manager/text/list doesn't show version numbers when 
there are multiple versions of a webapp running (via parallel deployment)?

Is there a different listing facility I should be using to find out the version 
tags of the currently running applications?

CG

When running a similar search on Tomcat v8.0.21, Red Hat x64 with JDK 1.7.0.8, 
the parallel versions are displayed as -

tomcat@localhost:/opt/tomcat
$ curl -s -X GET http://username:password@localhost:8080/manager/text/list |sort
/account-information-bs-1.0:running:0:account-information-bs-1.0##v1.0.3
/account-information-bs-1.1:running:0:account-information-bs-1.1##v1.1.0

How are you implementing the version numbers?

Regards,

Theo
Avios Group (AGL) Ltd is a limited company registered in England (registered 
number 2260073 and VAT number 512566754) whose registered address is Astral 
Towers, Betts Way, London Road, Crawley, West Sussex RH10 9XY . Avios Group 
(AGL) Limited is part of the IAG group of companies This email and any files 
transmitted with it are confidential and intended solely for the use of the 
individual or entity to whom they are addressed. If you have received this 
email in error please notify the system manager.

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

Re: Tomcat 8 Rewrite Valve

[Theo . Sweeny]

After further investigation it was discovered that Tomcat with a Logback 
implementation is blocking the Rewrite 
Valve module, yet to decipher why?

However - on a different Tomcat prototype running with the standard JULI 
logging, the rewrites worked as expected.




From:   theo.swe...@avios.com
To: Tomcat , 
Date:   13/10/2015 15:10
Subject:Tomcat 8 Rewrite Valve



Hello - I'm having issues implementing a HTTP 301 redirect via the Rewrite 

Valve module.

Ref - https://tomcat.apache.org/tomcat-8.0-doc/rewrite.html

Tomcat v8.021 is running on Ubuntu 14.04 x64.

The requirement is to run the rewrite config globally for all webapps, for 

this reason the valve is set inside the host.

conf/server.xml









Redirect set inside - conf/Catalina/localhost/rewrite.config

RewriteCond %{REQUEST_URI}  ^/abc/key$
RewriteRule ^/abc/key(.*)   /audit-management-ds-1.0/info 
[R=301,L]

Test - curl -vv -X GET http://ubt-srv-14-01:10080/abc/key

* Hostname was NOT found in DNS cache
*   Trying 127.0.1.1...
* Connected to ubt-srv-14-01 (127.0.1.1) port 10080 (#0)
> GET /abc/key HTTP/1.1
> User-Agent: curl/7.35.0
> Host: ubt-srv-14-01:10080
> Accept: */*
> 
< HTTP/1.1 404 Not Found
* Server Apache-Coyote/1.1 is not blacklisted
< Server: Apache-Coyote/1.1
< Content-Length: 0
< Date: Tue, 13 Oct 2015 13:52:20 GMT

Debug has been enabled on logging yet nothing is showing in the redirect 
in the access log.

However - logs do appear for curl -X GET 
http://ubt-srv-14-01:10080/audit-management-ds-1.0/info 

Any ideas?

Regards,

Theo

-
The Mileage Company Limited is a limited company registered in England 
under company number 2260073 whose registered office address is at
Astral Towers, Betts Way, London Road, Crawley, West Sussex, RH10 9XY.

This email and any files transmitted with it are confidential and intended 
solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify the 
system manager.

This footnote also confirms that this email message has been swept by 
Mimecast for the presence of computer viruses. 
-

-
The Mileage Company Limited is a limited company registered in England under 
company number 2260073 whose registered office address is at
Astral Towers, Betts Way, London Road, Crawley, West Sussex, RH10 9XY.

This email and any files transmitted with it are confidential and intended 
solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify the 
system manager.

This footnote also confirms that this email message has been swept by Mimecast 
for the presence of computer viruses. 
-

Tomcat 8 Rewrite Valve

[Theo . Sweeny]

Hello - I'm having issues implementing a HTTP 301 redirect via the Rewrite 
Valve module.

Ref - https://tomcat.apache.org/tomcat-8.0-doc/rewrite.html

Tomcat v8.021 is running on Ubuntu 14.04 x64.

The requirement is to run the rewrite config globally for all webapps, for 
this reason the valve is set inside the host.

conf/server.xml









Redirect set inside - conf/Catalina/localhost/rewrite.config

RewriteCond %{REQUEST_URI}  ^/abc/key$
RewriteRule ^/abc/key(.*)   /audit-management-ds-1.0/info 
[R=301,L]

Test - curl -vv -X GET http://ubt-srv-14-01:10080/abc/key

* Hostname was NOT found in DNS cache
*   Trying 127.0.1.1...
* Connected to ubt-srv-14-01 (127.0.1.1) port 10080 (#0)
> GET /abc/key HTTP/1.1
> User-Agent: curl/7.35.0
> Host: ubt-srv-14-01:10080
> Accept: */*
> 
< HTTP/1.1 404 Not Found
* Server Apache-Coyote/1.1 is not blacklisted
< Server: Apache-Coyote/1.1
< Content-Length: 0
< Date: Tue, 13 Oct 2015 13:52:20 GMT

Debug has been enabled on logging yet nothing is showing in the redirect 
in the access log.

However - logs do appear for curl -X GET 
http://ubt-srv-14-01:10080/audit-management-ds-1.0/info 

Any ideas?

Regards,

Theo

-
The Mileage Company Limited is a limited company registered in England under 
company number 2260073 whose registered office address is at
Astral Towers, Betts Way, London Road, Crawley, West Sussex, RH10 9XY.

This email and any files transmitted with it are confidential and intended 
solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify the 
system manager.

This footnote also confirms that this email message has been swept by Mimecast 
for the presence of computer viruses. 
-

Re: Tomcat 8 Session Timeout

[Theo . Sweeny]

Hi Chris - I added this value to the Engine container - 

backgroundProcessorDelay="20"

This has made a big improvement  - there is much more frequent clear down 
of the sessions.

Is there a config setting for maximum session age?

The reason for asking is that in a REST stateless environment the concept 
is to tear down after each request is served. However - this may have 
performance implications for Tomcat. Are there any best practices papers / 
pointers for stateless setup?

Theo




From:   Christopher Schultz 
To: Tomcat Users List , 
Date:   04/09/2015 18:39
Subject:Re: Tomcat 8 Session Timeout



-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Theo,

On 9/4/15 6:14 AM, theo.swe...@avios.com wrote:
> Hi Chris - the servlet spec states "If the time out is 0 or less,
> the container ensures the default behavior of sessions is never to
> time out."
> 
> Currently the timeout value is set to 2 minutes.
> 
> However the problem is persisting - the environment is using
> Jersery Servlet 1.3 for REST.
> 
> If we look inside web service stats -
> 
> Longest session alive time: 183 s / Processing time: 625 ms Longest
> session alive time: 207 s / Processing time: 232 ms
> 
> The current session timeout is set to 120 seconds, so neither of
> these above session times make any sense, unless a dependency is
> hanging?

Remember that the session timeout is not session age. If you have a
process which is touching the session more often than every 2 minutes
or so, then the session will live indefinitely.

Is the background processing thread still running? If it dies, your
sessions will never time out. Also, the background processing thread
is the thread that reaps old sessions... if you have the background
processor thread set to run infrequently, you'll see the behavior you
describe.

- -chris
-BEGIN PGP SIGNATURE-
Comment: GPGTools - http://gpgtools.org

iQIcBAEBCAAGBQJV6dciAAoJEBzwKT+lPKRYyogP+wfP5lNV8SxFTNDmiwLYxG/9
GnUxSQN8rQmWI6r1pl4UpWU+WFoUtL2BCTfnUuH2qP6Pg0KWn46P4Lon5XnThEqk
4mnHNCe4NYdGlw4rvVYgdy4zTP62hFvSm3ECb/QkZ1gcO1f8w4+0wqZh5k1g+0PQ
HkOg9SYSHRAUUKtG2YBPZWbEMnjKnkQKeKO3WjNBDLTbEU9mMyyJgZCsJCC4fmZa
sJN8yFW7JcG0jhhsEoBzYznT1dLxNliNs9kMiINoS1wWmIjHLHnHvaTDqDCE4Npd
VQh/ZrI7paRdVI4wOJ299CuZ4cpB9lxWEKi4vQAP5Jg/EgZrACrmZFnPMJG5np/v
lR2g+KCNxIvIpIlaGLbUOn4Ah0QMrfPEDFsLXHlYjfixdIrDjugbqdNnVYRvSOSt
LsR+xZcPOJ/ZiJCnD+2MK8dy8QYgq62oW8xpvald58x/gUk/uR8IuwdvswTIUVTV
+5k2YUcL+xcH1uEKHyMK3KCjty8aC+Rq+oEpkJjyFKJA1K0x161PIAdFq8P50VLn
rcJUjxTIcMP7hgg3BCQzdXH5qucVnFTlHNwKrX4MoT9LsGiraTOqhRt5EJLWBy+/
oYg3k/Vgkm2HzmRBuMGydv8RMNCq2hZaEXWDKoMtWRRvmYTOKcNC4nUiE/V8Dbr0
KaYwkgTvycLJzzohkMIn
=9riB
-END PGP SIGNATURE-

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

-
The Mileage Company Limited is a limited company registered in England under 
company number 2260073 whose registered office address is at
Astral Towers, Betts Way, London Road, Crawley, West Sussex, RH10 9XY.

This email and any files transmitted with it are confidential and intended 
solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify the 
system manager.

This footnote also confirms that this email message has been swept by Mimecast 
for the presence of computer viruses. 
-

Re: Tomcat 8 Session Timeout

[Theo . Sweeny]

Hi Chris - the servlet spec states "If the time out is 0 or less, the 
container ensures the default behavior of sessions is never to time out."

Currently the timeout value is set to 2 minutes.

However the problem is persisting - the environment is using Jersery 
Servlet 1.3 for REST.

If we look inside web service stats -

Longest session alive time: 183 s / Processing time: 625 ms
Longest session alive time: 207 s / Processing time: 232 ms

The current session timeout is set to 120 seconds, so neither of these 
above session times make any sense, unless a dependency is hanging?

Theo



From:   Christopher Schultz 
To: Tomcat Users List , 
Date:   03/09/2015 16:43
Subject:Re: Tomcat 8 Session Timeout



-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Theo,

On 9/3/15 8:28 AM, theo.swe...@avios.com wrote:
> Thanks Chris - that pointer is very helpful.
> 
> Can you clarify by setting session-timeout to 0, implies after 60
> seconds the session will expire or does it imply the same as -1,
> that sessions will not timeout?
> 
>  0 
> 

What does the servlet specification say about the values used there?
Hint: your assumptions are already wrong.

- -chris
-BEGIN PGP SIGNATURE-
Comment: GPGTools - http://gpgtools.org

iQIcBAEBCAAGBQJV6GptAAoJEBzwKT+lPKRYNC4P/0cuUR+RAyAHmWXcaQXIExai
VgACUHVxqajMxaBPwVjfap/DRH25COmqzvMo2Bj8KtviL3wIRR5CDxySUObVx14A
4skSKdO8L0MvYaSmx2GDFRNTQkRKRe2EoNivbuCwuT06W0dKr1V2gPXyqp2f9Hm8
GIOOiToU43MONBR2n0IM+F/UvbFxaHVLJoWEIXZ3PoGIcVk6scmGVrS8fp6BvXmw
xIWa0VWZuVTnJ0E32vVEuWNBnNSdwpnvQyR4dz5r+Ty/OATNeeYi9JiloBGlKPg0
j02bR8to+vZokGgRz+A1qxQZdmGFHxbsxgrWFNGRJz4MVuBT1kimBs4mq6yDWCg4
kC/lBEO/8QWGag2zuNW1s1oCI0jskEqTWd+PipNYAQSv/GGu7Tvpa5N6CUriePmH
3se/rJdiNlcI0S4AVJpnJ3d8kaxzOltlImP8VgBG5ep2FJH5kZ2biTtQRiHxXjUI
FCw+hR5mNKauTGiUKfwc4BVswD0QMa3ncDONtKmOcyirpEZDEapTk5Un1bKZ7pso
ZrmhcdhLO8BuK0EKyK4IoTiysyA43CJ+4Uu7MK8X8weJR74FyTKGBmg/5OqAypk+
QSc1BcEDv9JMH7tPI1Fcb412jGc0B9y/zMdQDcpSXp9Aw4CKl9bhJXY60GnjcxOH
LgyxvMq/UZnoYRAFGRxX
=//Bk
-END PGP SIGNATURE-

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

-
The Mileage Company Limited is a limited company registered in England under 
company number 2260073 whose registered office address is at
Astral Towers, Betts Way, London Road, Crawley, West Sussex, RH10 9XY.

This email and any files transmitted with it are confidential and intended 
solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify the 
system manager.

This footnote also confirms that this email message has been swept by Mimecast 
for the presence of computer viruses. 
-

Re: Tomcat 8 Session Timeout

[Theo . Sweeny]

Thanks Chris - that pointer is very helpful.

Can you clarify by setting session-timeout to 0, implies after 60 seconds 
the session will expire or does it imply the same as -1, that sessions 
will not timeout?


0


Theo



From:   Christopher Schultz 
To: Tomcat Users List , 
Date:   01/09/2015 17:23
Subject:Re: Tomcat 8 Session Timeout



-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Theo,

On 9/1/15 4:29 AM, theo.swe...@avios.com wrote:
> Mark - I took a look at the Manager How To Guide  as seen here -
> 
> https://tomcat.apache.org/tomcat-8.0-doc/manager-howto.html#Expire_Ses
sions
>
>  It mentions that it's possible to expire sessions for each
> individual app using a command similar to -
> 
> curl -X GET 
> http://username:password@localhost:8080/manager/text/expire?path=/exam
ples=0
>
>  Do you know if a wildcard can be used for the app name?

You can't.

If you want to script it, you can write some code to pull the list of
sessions and then interrogate them for various things. I'm not sure
what the manager application's interface is willing to cough-up, but
if you use JMX (either directly or via the manager's JMXProxyServlet),
you can list the sessions, look at their attributes, and expire them
using whatever criteria you want.

Check out slide 40 in this presentation from ApacheCon NA 2015:
http://events.linuxfoundation.org/sites/events/files/slides/Monitoring%2
0Apache%20Tomcat%20with%20JMX_0.pdf

This trick requires that you have an attribute in the session called
"user" that has the user's username in the toString() output. It's
just an example, but you can see how you can grab sessions and do
things with them.

- -chris
-BEGIN PGP SIGNATURE-
Comment: GPGTools - http://gpgtools.org

iQIcBAEBCAAGBQJV5dDTAAoJEBzwKT+lPKRYRIUQAIuCucb4uj6o9uyr6CD/N+Yh
9NDAedOdxygaR14+uy8vHPB/V60O65bURSArFt65oNIB0U0YIA5A7/dpp+8NNWLE
O31mJu9GPLb5X1RdArRV8esiI23QRkZWNtEuNPn1pVcVwMMmfym+NzX1N1Ng9Sdu
Tkkom3GKf4MXujl4UqqiGEgy1nnSvmRUUoRAdGRsEWamz5GgfjFT6TIhmy+RBDxy
Doh4iRxDNO9g0yMHL/SWxOssEh+unJCcFKEJEo2nsRkh4MjsOkmVlyzWHiXkC/IZ
P+815UQjxgwPX+xQq2U3ptghj+SS3MJGKm2HuihF/ia+0xT7+0V0l1Oo8+H7y4Br
4Jf9FO9hfan9W0pnqi9U0tg3Ojthl8m1Q9nucU+v6CbGYUU5RExqaJBATU46wuda
PvDCP8MkVmYGGPNnUDDi9RIw9dggKC/FPm//iLLSBeHKZMfN1PXBViQOZVbj3X84
Dc1RU7c7F1OfuXCcAb2koQJjDGmgxr7KF8mPtNdzq+dSUeVDn1L2JZziXJ6MICVp
xrlslFSZ7iCUgpuc1+/FX99jG+CvxBj4v+LDgMlw1VEkqxeqg7V5HO5T4KhdHXZ2
IjjlUMsEUtsmIrF00EXyW/gXGyl15Nzn6ULEPFwnm4nUf0vEUVoWyjdBsXWaAo5O
N8okIJvNcDxwaQWBWm7w
=epgx
-END PGP SIGNATURE-

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

-
The Mileage Company Limited is a limited company registered in England under 
company number 2260073 whose registered office address is at
Astral Towers, Betts Way, London Road, Crawley, West Sussex, RH10 9XY.

This email and any files transmitted with it are confidential and intended 
solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify the 
system manager.

This footnote also confirms that this email message has been swept by Mimecast 
for the presence of computer viruses. 
-

Re: Tomcat 8 Session Timeout

[Theo . Sweeny]

Hi Chris,

That's pretty much it (except the path for the app's web.xml looks a
little odd).

We are running multi-instance environment and this is why the path is 
$CATALINA_BASE/conf/web.xml

Are the web services specifying their own session-timeout in the
application-specific web.xml?

No the web-apps are not specifying their own session-timeout. We want to 
run with a stateless environment. Eventually the session-timeout will be 
brought down to 0, but the current setting for 2 minutes doesn't work. The 
sessions do not timeout.

Theo




From:   Christopher Schultz 
To: Tomcat Users List , 
Date:   28/08/2015 19:09
Subject:Re: Tomcat 8 Session Timeout



-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Theo,

On 8/28/15 12:08 PM, theo.swe...@avios.com wrote:
> Hello - currently HTTP sessions are configured to timeout after 120
>  seconds, in $CATALINA_BASE/conf/web.xml
> 
>  2 
> 

I'd highly recommend that you move that configuration from
conf/web.xml to your own web application's web.xml.

> However this is not being honoured by the web services, where many
> session are lasting longer.
> 
>> From what I understand - the order for session timeouts is -
> 
> HttpSession.setMaxInactiveInterval(int) 
> $WebApplication/webapp/WEB-INF/web.xml $TOMCAT_BASE/conf/web.xml
> 
> Is there something that I'm missing?

That's pretty much it (except the path for the app's web.xml looks a
little odd).

Are the web services specifying their own session-timeout in the
application-specific web.xml?

- -chris
-BEGIN PGP SIGNATURE-
Comment: GPGTools - http://gpgtools.org

iQIcBAEBCAAGBQJV4KO3AAoJEBzwKT+lPKRYh8cQALjjzZ4glyywX4HrTpfAOtEJ
Ck1LC/S82MgNfCfS1dOx8fUpuER6ZSJ+fkALjAMjAr5MmQX+/Z2nODvj/XWDLkRj
6Hyp/F+rEnExt4bS6idWz32hPtzDqxA4Ffxy9oCROihXXdvA0qGn6xGfKwtUaBH2
rviw3au4uD2W3iPffszUj3VnGQnWhK3QFQpFCLkpVu1lF/EiqBCL3XHIY+6cDzBO
fpGWiFrk+9RSuP/uN3LEGzdZNvuHNiNu5OrlvBq9P8Q1zwya6fcuPGu0NvFD7ESl
o0pCmcie9NUFXN1R0/RtT8uw7ZVELWrPx5C6zLR1tbwodMnarlQMazAdQFDDtiVK
DLPjpKF0bPqAP3ORUzRAu3IfSaXhtgE77byAB8DLnPJjpKeyWEp4tCDP1CmI6NI1
5dVQmt5CJAo5pP5YAMM38GsJyY5NoQ2NI61tPJ/NFTJkV0pyCGlufiRMp6ySMvBP
zY8CjhNEjhfEV35RB1hYzawhZ3hgV3oq78HLGLZ15eaYiBTBHyHyKgdbitRfawIP
ICdvpuElYDPNKFI2SfSb3qQc64sm+kqN6B1DNWMALAWISNENB0ahu6D4a9UJTr0R
FgFRCdpkkV8/3FfpoSpu2kzzBubYMA7XpMyuk9HWlABJvT99AJCwPeA2C5falShv
j5HCHDLxsn1LzK8hl9mK
=3HRA
-END PGP SIGNATURE-

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

-
The Mileage Company Limited is a limited company registered in England under 
company number 2260073 whose registered office address is at
Astral Towers, Betts Way, London Road, Crawley, West Sussex, RH10 9XY.

This email and any files transmitted with it are confidential and intended 
solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify the 
system manager.

This footnote also confirms that this email message has been swept by Mimecast 
for the presence of computer viruses. 
-

Re: Tomcat 8 Session Timeout

[Theo . Sweeny]

Hi Mark 

Tomcat version?

v8.0.21

The usual causes are:
 - something unexpected accessing the session
 - the background processing thread is crashed / busy doing something
   else

Is there a command line mechanism to gracefully terminate sessions?

Theo




From:   Mark Thomas 
To: Tomcat Users List , 
Date:   28/08/2015 19:13
Subject:Re: Tomcat 8 Session Timeout



On 28/08/2015 12:08, theo.swe...@avios.com wrote:
> Hello - currently HTTP sessions are configured to timeout after 120 
> seconds, in $CATALINA_BASE/conf/web.xml
> 
>
> 2
> 
> 
> However this is not being honoured by the web services, where many 
session 
> are lasting longer.
> 
> From what I understand - the order for session timeouts is - 
> 
> HttpSession.setMaxInactiveInterval(int) 
> $WebApplication/webapp/WEB-INF/web.xml 
> $TOMCAT_BASE/conf/web.xml
> 
> Is there something that I'm missing?

Tomcat version?

The usual causes are:
 - something unexpected accessing the session
 - the background processing thread is crashed / busy doing something
   else

Mark

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

-
The Mileage Company Limited is a limited company registered in England under 
company number 2260073 whose registered office address is at
Astral Towers, Betts Way, London Road, Crawley, West Sussex, RH10 9XY.

This email and any files transmitted with it are confidential and intended 
solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify the 
system manager.

This footnote also confirms that this email message has been swept by Mimecast 
for the presence of computer viruses. 
-

Re: Tomcat 8 Session Timeout

[Theo . Sweeny]

Mark - I took a look at the Manager How To Guide  as seen here - 

https://tomcat.apache.org/tomcat-8.0-doc/manager-howto.html#Expire_Sessions

It mentions that it's possible to expire sessions for each individual app 
using a command similar to - 

curl -X GET 
http://username:password@localhost:8080/manager/text/expire?path=/examples=0

Do you know if a wildcard can be used for the app name? 

Theo




From:   Mark Thomas 
To: Tomcat Users List , 
Date:   01/09/2015 09:02
Subject:Re: Tomcat 8 Session Timeout



On 01/09/2015 08:53, theo.swe...@avios.com wrote:
> Hi Mark 
> 
> Tomcat version?
> 
> v8.0.21

OK. Fairly recent and no known issues. I'll add session expiration is
testing as part of the 'unit' tests we run after every commit and I
don't ever remember it failing. The same tests are also run before every
release and must pass on multiple platforms before the release is started.

> The usual causes are:
>  - something unexpected accessing the session
>  - the background processing thread is crashed / busy doing something
>else
> 
> Is there a command line mechanism to gracefully terminate sessions?

No, but you can use the Manager app to view session contents and expire
the sessions.

Mark

> 
> Theo
> 
> 
> 
> 
> From:   Mark Thomas 
> To: Tomcat Users List , 
> Date:   28/08/2015 19:13
> Subject:Re: Tomcat 8 Session Timeout
> 
> 
> 
> On 28/08/2015 12:08, theo.swe...@avios.com wrote:
>> Hello - currently HTTP sessions are configured to timeout after 120 
>> seconds, in $CATALINA_BASE/conf/web.xml
>>
>>
>> 2
>> 
>>
>> However this is not being honoured by the web services, where many 
> session 
>> are lasting longer.
>>
>> From what I understand - the order for session timeouts is - 
>>
>> HttpSession.setMaxInactiveInterval(int) 
>> $WebApplication/webapp/WEB-INF/web.xml 
>> $TOMCAT_BASE/conf/web.xml
>>
>> Is there something that I'm missing?
> 
> Tomcat version?
> 
> The usual causes are:
>  - something unexpected accessing the session
>  - the background processing thread is crashed / busy doing something
>else
> 
> Mark
> 
> -
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: users-h...@tomcat.apache.org
> 
> 
-
> The Mileage Company Limited is a limited company registered in England 
under company number 2260073 whose registered office address is at
> Astral Towers, Betts Way, London Road, Crawley, West Sussex, RH10 9XY.
> 
> This email and any files transmitted with it are confidential and 
intended solely for the use of the individual or entity to whom they
> are addressed. If you have received this email in error please notify 
the system manager.
> 
> This footnote also confirms that this email message has been swept by 
Mimecast for the presence of computer viruses. 
> 
-
> 


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

-
The Mileage Company Limited is a limited company registered in England under 
company number 2260073 whose registered office address is at
Astral Towers, Betts Way, London Road, Crawley, West Sussex, RH10 9XY.

This email and any files transmitted with it are confidential and intended 
solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify the 
system manager.

This footnote also confirms that this email message has been swept by Mimecast 
for the presence of computer viruses. 
-

Tomcat 8 Session Timeout

[Theo . Sweeny]

Hello - currently HTTP sessions are configured to timeout after 120 
seconds, in $CATALINA_BASE/conf/web.xml

   session-config
session-timeout2/session-timeout
/session-config

However this is not being honoured by the web services, where many session 
are lasting longer.

From what I understand - the order for session timeouts is - 

HttpSession.setMaxInactiveInterval(int) 
$WebApplication/webapp/WEB-INF/web.xml 
$TOMCAT_BASE/conf/web.xml

Is there something that I'm missing?

Theo

-
The Mileage Company Limited is a limited company registered in England under 
company number 2260073 whose registered office address is at
Astral Towers, Betts Way, London Road, Crawley, West Sussex, RH10 9XY.

This email and any files transmitted with it are confidential and intended 
solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify the 
system manager.

This footnote also confirms that this email message has been swept by Mimecast 
for the presence of computer viruses. 
-

Re: Command line requests for starting/reloading/stoping applications are not working in Tomcat 7.0.57 Manager

[Theo . Sweeny]

Hello Yudin - try using the -X GET option with curl

E.G.  curl --user OurName:OurSecurePasswd -X GET 
http://our.server.fqdn:8080/manager/text/stop?path=/docs


Theo Sweeny
Web Support Contractor

T: 01293 722211
W: www.avios.com







From:   Yudin, Ilya yudi...@nytimes.com
To: users@tomcat.apache.org, 
Date:   14/07/2015 15:58
Subject:Command line requests for starting/reloading/stoping 
applications are not working in Tomcat 7.0.57 Manager



Hello,

I'm running Apache Tomcat 7.0.57 on RHEL 6.6 servers for CCI NewsGate
editorial system which uses around 20 applications per Tomcat server. 
There
is a requirement here (for the reasons of automating administrative tasks)
to enable starting, stoping and reloading individual applications from
Linux command line

I am using your documentation on Apache Tomcat Manager at the following
URL:
http://tomcat.apache.org/tomcat-7.0-doc/manager-howto.html#Reload_An_Existing_Application

to achieve that, but the commands do not work as described, even though 
Web
GUI Manager works just fine.

I do have appropriate roles for the user added to my
tomcat/conf/tomcat-users.xml file:

tomcat-users
  role rolename=manager-gui/
  role rolename=manager-script/
  user username=OurName password=OurSecurePasswd
roles=manager-gui,manager-script/
/tomcat-users

... and I have re-started Tomcat after adding the manager-script role.

The list command works exactly as described in documentation:

[ngtom@ng-web01 ~]$ curl --user OurName:OurSecurePasswd
http://our.server.fqdn:8080/manager/text/list
OK - Listed applications for virtual host localhost
...
/manager:running:0:manager
/workschedule:running:0:workschedule
/docs:running:0:docs
/sample:running:348:sample
...

However when I try to start/stop/reload any of the listed applications I 
am
getting the following result:

[ngtom@ng-web01 ~]$ curl --user OurName:OurSecurePasswd
http://our.server.fqdn:8080/manager/text/stop?path=/docs
curl: No match.

I think that I've done everything exactly as shown in the examples given 
in
your documentation, but apparently something there or in what I'm doing is
wrong.

Could you please help?

Thanks,
*--*
*Ilya Yudin*

*SystemsTechnology**yudi...@nytimes.com*

-
The Mileage Company Limited is a limited company registered in England under 
company number 2260073 whose registered office address is at
Astral Towers, Betts Way, London Road, Crawley, West Sussex, RH10 9XY.

This email and any files transmitted with it are confidential and intended 
solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify the 
system manager.

This footnote also confirms that this email message has been swept by Mimecast 
for the presence of computer viruses. 
-

Re: Tomcat 8 - Manager Deploy

[Theo . Sweeny]

Hi Chris - I did search for the version tag but was unable to identify 
it in the Tomcat 8 documentation.

Would you mind pointing me toward it please?




From:   Christopher Schultz ch...@christopherschultz.net
To: Tomcat Users List users@tomcat.apache.org, 
Date:   13/07/2015 20:04
Subject:Re: Tomcat 8 - Manager Deploy



-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Theo,

On 7/13/15 8:47 AM, theo.swe...@avios.com wrote:
 Hello Violeta - I finally cracked it.
 
 The problem was using the hash mark in the curl command. The ASCII
  equivalent value of %23 needs to be used instead of # value as
 seen here -

Or you could follow the documentation and use the version parameter.
It's much less messy and more clear to whoever is reading the script.

- -chris
-BEGIN PGP SIGNATURE-
Comment: GPGTools - http://gpgtools.org

iQIbBAEBCAAGBQJVpAuYAAoJEBzwKT+lPKRYGeEP+M7yNhlrGdhJOiylGKHZurF3
kdVMB7SuZhMaHJ0uJfC3wUzxpi6zrDqSE9G83yuomdKELxUJxLzr5oB9oHSr92J5
75C63q6Mt8LyEmuYTCqbNdM07S5YLgljsNRAXtKjcK8haqojIsuoXuCCzY4GwtB7
rhPMiqLuMlz5VCZK6vsh2qVqoMOEGadpqIx1Mko6gJ1kDoT3k+ndrf/kz6TiEbzD
m6t0sM/WmjM/bfWuUlMK82o4J/9KihhoNAo17/u7Ht3JEUNFkJuBio04Pt3KH3ZN
IYist8pv+VPzH+E1j7sBB0oipSPRjk1CdMbDxIcdabIn6zUwIwDoyBLj08gvmcO2
efg5XE0MgI8EhEWHUYwg+yvBN+Dhm9SJyYg0FF+0g0pd38aJSwiugFrUvPfhss9k
SLVt+wxijUfjPtD3EEIx5+IXWi5nLAg5SsP89I70igimLNjO93aSX7KKQ/UVc/sB
AqJ9g1dewMnh+uejOVKWrT4p9KdS/nDwNEvTN/SvnQIl726TMdHzCdQJYUgZ3QX7
ozFqubYfZqh8/1v5k6aMzkp7OJ8mULrvxJ2jFVnuYG5yiSp2vQreeTGQyxJUcKAn
2ol2YtJ2O4/gAwmMvz3NNrHo5j9nNyaew0iAS3y4YvSROqPR9jMuwbhFWoY0LII5
dbmHu34r9RH5GJ1UTCk=
=yiOO
-END PGP SIGNATURE-

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

-
The Mileage Company Limited is a limited company registered in England under 
company number 2260073 whose registered office address is at
Astral Towers, Betts Way, London Road, Crawley, West Sussex, RH10 9XY.

This email and any files transmitted with it are confidential and intended 
solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify the 
system manager.

This footnote also confirms that this email message has been swept by Mimecast 
for the presence of computer viruses. 
-

Re: Tomcat 8 - Manager Deploy

[Theo . Sweeny]

Hello Again - I've ran a new test with a sample war file downloaded from -

https://tomcat.apache.org/tomcat-6.0-doc/appdev/sample/sample.war

The war is renamed as sample-1.0##v1.0.0.war

This time the war deploys and starts but it doesn't honour the version 
number given in the path - 

curl -v --upload-file /usr/share/tomcat/installs/sample-1.0##v1.0.0.war -X 
PUT 
http://username:password@localhost:10080/manager/text/deploy?path=/sample-1.0##v1.0.0update=true


View running webapps - 

$ curl -X GET http://tcsct:cbiw2PXB@localhost:10080/manager/text/list
OK - Listed applications for virtual host localhost
/manager:running:4:manager
/sample-1.0:running:0:sample-1.0

Instead I would expect to see - 

$ curl -X GET http://tcsct:cbiw2PXB@localhost:10080/manager/text/listOK - 
Listed applications for virtual host localhost
/manager:running:4:manager
/sample-1.0:running:0:sample-1.0##v1.0.0

Is there a reason why the version number is being omitted?




From:   Theo Sweeny/LGW/MILEAGE
To: Tomcat Users List users@tomcat.apache.org, 
Date:   13/07/2015 08:33
Subject:Re: Tomcat 8 - Manager Deploy


Hello Konstantin - thank you for the reply.

So your deployment (upload) was successful,  but the application itself is 
broken and failed to start.

If I take the same application and deploy it using deployOnStartup, it 
deploys and starts without issue. This removes the possibility of there 
being an issue with the war file.

Here are the Catalina and Localhost logs - 

logs/catalina.2015-07-10.log:10-Jul-2015 11:20:54.560 INFO 
[localhost-startStop-1] org.apache.catalina.startup.HostConfig.deployWAR 
Deploying web application archive 
/opt/tomcat/webapps/address-information-ds-1.0.war

logs/catalina.2015-07-10.log:10-Jul-2015 11:20:54.568 SEVERE 
[localhost-startStop-1] 
org.apache.catalina.startup.ContextConfig.beforeStart Exception fixing 
docBase for context [/address-information-ds-1.0]

logs/catalina.2015-07-10.log:10-Jul-2015 11:20:54.571 SEVERE 
[localhost-startStop-1] 
org.apache.catalina.core.ContainerBase.addChildInternal 
ContainerBase.addChild: start: 

logs/catalina.2015-07-10.log:10-Jul-2015 11:20:54.572 SEVERE 
[localhost-startStop-1] org.apache.catalina.startup.HostConfig.deployWAR 
Error deploying web application archive 
/opt/tomcat/webapps/address-information-ds-1.0.war

logs/catalina.2015-07-10.log:10-Jul-2015 11:20:54.573 INFO 
[localhost-startStop-1] org.apache.catalina.startup.HostConfig.deployWAR 
Deployment of web application archive 
/opt/tomcat/webapps/address-information-ds-1.0.war has finished in 13 ms

logs/catalina.2015-07-10.log:10-Jul-2015 11:20:54.574 INFO 
[localhost-startStop-1] 
org.apache.catalina.startup.HostConfig.deployDirectory Deploying web 
application directory /opt/tomcat/webapps/ROOT

logs/catalina.2015-07-10.log:10-Jul-2015 11:20:55.031 INFO 
[localhost-startStop-1] 
org.apache.catalina.startup.HostConfig.deployDirectory Deployment of web 
application directory /opt/tomcat/webapps/ROOT has finished in 456 ms

logs/catalina.2015-07-10.log:10-Jul-2015 11:20:55.031 INFO 
[localhost-startStop-1] 
org.apache.catalina.startup.HostConfig.deployDirectory Deploying web 
application directory /opt/tomcat/webapps/host-manager

logs/catalina.2015-07-10.log:10-Jul-2015 11:20:55.544 INFO 
[localhost-startStop-1] 
org.apache.catalina.startup.HostConfig.deployDirectory Deployment of web 
application directory /opt/tomcat/webapps/host-manager has finished in 513 
ms

logs/catalina.2015-07-10.log:10-Jul-2015 11:20:55.545 INFO 
[localhost-startStop-1] 
org.apache.catalina.startup.HostConfig.deployDirectory Deploying web 
application directory /opt/tomcat/webapps/manager

logs/catalina.2015-07-10.log:10-Jul-2015 11:20:55.973 INFO 
[localhost-startStop-1] 
org.apache.catalina.startup.HostConfig.deployDirectory Deployment of web 
application directory /opt/tomcat/webapps/manager has finished in 427 ms

logs/catalina.2015-07-10.log:10-Jul-2015 11:20:55.980 INFO [main] 
org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler 
[http-nio-10080]

logs/catalina.2015-07-10.log:10-Jul-2015 11:20:55.990 INFO [main] 
org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler 
[ajp-nio-10009]

logs/catalina.2015-07-10.log:10-Jul-2015 11:20:55.990 INFO [main] 
org.apache.catalina.startup.Catalina.start Server startup in 58884 ms

logs/localhost.2015-07-10.log:10-Jul-2015 11:20:42.779 INFO 
[localhost-startStop-1] org.apache.catalina.core.ApplicationContext.log 
Initializing Spring embedded WebApplicationContext

logs/localhost.2015-07-10.log:10-Jul-2015 11:20:54.547 FINE 
[localhost-startStop-1] 
org.apache.catalina.core.StandardContext.listenerStart Sending application 
start events

logs/localhost.2015-07-10.log:10-Jul-2015 11:20:54.551 FINE 
[localhost-startStop-1] 
org.apache.catalina.core.StandardContext.filterStart Starting filters

logs/localhost.2015-07-10.log:10-Jul-2015 11:20:54.552 FINE 
[localhost-startStop-1

Re: Tomcat 8 - Manager Deploy

[Theo . Sweeny]

Hello Violeta - I finally cracked it.

The problem was using the hash mark in the curl command. The ASCII 
equivalent value of %23 needs to be used instead of # value as seen here - 


curl -v --upload-file /usr/share/tomcat/installs/sample.war -X PUT 
http://username:password@localhost:10080/manager/text/deploy?path=/sample-1.0%23%231.0.7update=true
OK - Deployed application at context path /sample-1.0##1.0.7

This then deploys as - 

$ curl -X GET http://username:password@localhost:10080/manager/text/list
/manager:running:0:manager
/sample-1.0:running:0:sample-1.0##1.0.7

And the content also works for undeploy, providing the hash symbol 
substitution is put in place - 

curl -v -X GET 
http://username:password@localhost:10080/manager/text/undeploy?path=/sample-1.0%23%231.0.7
OK - Undeployed application at context path /sample-1.0##1.0.7

Thanks to everyone for the help!



From:   Violeta Georgieva miles...@gmail.com
To: Tomcat Users List users@tomcat.apache.org, 
Date:   13/07/2015 12:55
Subject:Re: Tomcat 8 - Manager Deploy



Hi,

2015-07-13 14:48 GMT+03:00 theo.swe...@avios.com:

 Hello Again - I've ran a new test with a sample war file downloaded from 
-

 https://tomcat.apache.org/tomcat-6.0-doc/appdev/sample/sample.war

 The war is renamed as sample-1.0##v1.0.0.war

 This time the war deploys and starts but it doesn't honour the version
 number given in the path -

 curl -v --upload-file /usr/share/tomcat/installs/sample-1.0##v1.0.0.war 
-X
 PUT 
 http://username:password@localhost
:10080/manager/text/deploy?path=/sample-1.0##v1.0.0update=true
 


If you need to specify a version that use the correct syntax:

http://tomcat.apache.org/tomcat-8.0-doc/manager-howto.html#Supported_Manager_Commands


path - The context path (including the leading slash) of the web
application you are dealing with. To select the ROOT web application,
specify /. NOTE: It is not possible to perform administrative commands 
on
the Manager application itself.
version - The version of this web application as used by the parallel
deployment feature,

Regards,
Violeta

 View running webapps -

 $ curl -X GET http://tcsct:cbiw2PXB@localhost:10080/manager/text/list
 OK - Listed applications for virtual host localhost
 /manager:running:4:manager
 /sample-1.0:running:0:sample-1.0

 Instead I would expect to see -

 $ curl -X GET http://tcsct:cbiw2PXB@localhost:10080/manager/text/listOK 
-
 Listed applications for virtual host localhost
 /manager:running:4:manager
 /sample-1.0:running:0:sample-1.0##v1.0.0

 Is there a reason why the version number is being omitted?




 From:   Theo Sweeny/LGW/MILEAGE
 To: Tomcat Users List users@tomcat.apache.org,
 Date:   13/07/2015 08:33
 Subject:Re: Tomcat 8 - Manager Deploy


 Hello Konstantin - thank you for the reply.

 So your deployment (upload) was successful,  but the application itself 
is
 broken and failed to start.

 If I take the same application and deploy it using deployOnStartup, it
 deploys and starts without issue. This removes the possibility of there
 being an issue with the war file.

 Here are the Catalina and Localhost logs -

 logs/catalina.2015-07-10.log:10-Jul-2015 11:20:54.560 INFO
 [localhost-startStop-1] org.apache.catalina.startup.HostConfig.deployWAR
 Deploying web application archive
 /opt/tomcat/webapps/address-information-ds-1.0.war

 logs/catalina.2015-07-10.log:10-Jul-2015 11:20:54.568 SEVERE
 [localhost-startStop-1]
 org.apache.catalina.startup.ContextConfig.beforeStart Exception fixing
 docBase for context [/address-information-ds-1.0]

 logs/catalina.2015-07-10.log:10-Jul-2015 11:20:54.571 SEVERE
 [localhost-startStop-1]
 org.apache.catalina.core.ContainerBase.addChildInternal
 ContainerBase.addChild: start:

 logs/catalina.2015-07-10.log:10-Jul-2015 11:20:54.572 SEVERE
 [localhost-startStop-1] org.apache.catalina.startup.HostConfig.deployWAR
 Error deploying web application archive
 /opt/tomcat/webapps/address-information-ds-1.0.war

 logs/catalina.2015-07-10.log:10-Jul-2015 11:20:54.573 INFO
 [localhost-startStop-1] org.apache.catalina.startup.HostConfig.deployWAR
 Deployment of web application archive
 /opt/tomcat/webapps/address-information-ds-1.0.war has finished in 13 ms

 logs/catalina.2015-07-10.log:10-Jul-2015 11:20:54.574 INFO
 [localhost-startStop-1]
 org.apache.catalina.startup.HostConfig.deployDirectory Deploying web
 application directory /opt/tomcat/webapps/ROOT

 logs/catalina.2015-07-10.log:10-Jul-2015 11:20:55.031 INFO
 [localhost-startStop-1]
 org.apache.catalina.startup.HostConfig.deployDirectory Deployment of web
 application directory /opt/tomcat/webapps/ROOT has finished in 456 ms

 logs/catalina.2015-07-10.log:10-Jul-2015 11:20:55.031 INFO
 [localhost-startStop-1]
 org.apache.catalina.startup.HostConfig.deployDirectory Deploying web
 application directory /opt/tomcat/webapps/host-manager

 logs/catalina.2015-07-10.log:10-Jul-2015 11:20:55.544 INFO
 [localhost-startStop-1

Re: Tomcat 8 - Manager Deploy

[Theo . Sweeny]

Hello Konstantin - thank you for the reply.

So your deployment (upload) was successful,  but the application itself is 
broken and failed to start.

If I take the same application and deploy it using deployOnStartup, it 
deploys and starts without issue. This removes the possibility of there 
being an issue with the war file.

Here are the Catalina and Localhost logs - 

logs/catalina.2015-07-10.log:10-Jul-2015 11:20:54.560 INFO 
[localhost-startStop-1] org.apache.catalina.startup.HostConfig.deployWAR 
Deploying web application archive 
/opt/tomcat/webapps/address-information-ds-1.0.war

logs/catalina.2015-07-10.log:10-Jul-2015 11:20:54.568 SEVERE 
[localhost-startStop-1] 
org.apache.catalina.startup.ContextConfig.beforeStart Exception fixing 
docBase for context [/address-information-ds-1.0]

logs/catalina.2015-07-10.log:10-Jul-2015 11:20:54.571 SEVERE 
[localhost-startStop-1] 
org.apache.catalina.core.ContainerBase.addChildInternal 
ContainerBase.addChild: start: 

logs/catalina.2015-07-10.log:10-Jul-2015 11:20:54.572 SEVERE 
[localhost-startStop-1] org.apache.catalina.startup.HostConfig.deployWAR 
Error deploying web application archive 
/opt/tomcat/webapps/address-information-ds-1.0.war

logs/catalina.2015-07-10.log:10-Jul-2015 11:20:54.573 INFO 
[localhost-startStop-1] org.apache.catalina.startup.HostConfig.deployWAR 
Deployment of web application archive 
/opt/tomcat/webapps/address-information-ds-1.0.war has finished in 13 ms

logs/catalina.2015-07-10.log:10-Jul-2015 11:20:54.574 INFO 
[localhost-startStop-1] 
org.apache.catalina.startup.HostConfig.deployDirectory Deploying web 
application directory /opt/tomcat/webapps/ROOT

logs/catalina.2015-07-10.log:10-Jul-2015 11:20:55.031 INFO 
[localhost-startStop-1] 
org.apache.catalina.startup.HostConfig.deployDirectory Deployment of web 
application directory /opt/tomcat/webapps/ROOT has finished in 456 ms

logs/catalina.2015-07-10.log:10-Jul-2015 11:20:55.031 INFO 
[localhost-startStop-1] 
org.apache.catalina.startup.HostConfig.deployDirectory Deploying web 
application directory /opt/tomcat/webapps/host-manager

logs/catalina.2015-07-10.log:10-Jul-2015 11:20:55.544 INFO 
[localhost-startStop-1] 
org.apache.catalina.startup.HostConfig.deployDirectory Deployment of web 
application directory /opt/tomcat/webapps/host-manager has finished in 513 
ms

logs/catalina.2015-07-10.log:10-Jul-2015 11:20:55.545 INFO 
[localhost-startStop-1] 
org.apache.catalina.startup.HostConfig.deployDirectory Deploying web 
application directory /opt/tomcat/webapps/manager

logs/catalina.2015-07-10.log:10-Jul-2015 11:20:55.973 INFO 
[localhost-startStop-1] 
org.apache.catalina.startup.HostConfig.deployDirectory Deployment of web 
application directory /opt/tomcat/webapps/manager has finished in 427 ms

logs/catalina.2015-07-10.log:10-Jul-2015 11:20:55.980 INFO [main] 
org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler 
[http-nio-10080]

logs/catalina.2015-07-10.log:10-Jul-2015 11:20:55.990 INFO [main] 
org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler 
[ajp-nio-10009]

logs/catalina.2015-07-10.log:10-Jul-2015 11:20:55.990 INFO [main] 
org.apache.catalina.startup.Catalina.start Server startup in 58884 ms

logs/localhost.2015-07-10.log:10-Jul-2015 11:20:42.779 INFO 
[localhost-startStop-1] org.apache.catalina.core.ApplicationContext.log 
Initializing Spring embedded WebApplicationContext

logs/localhost.2015-07-10.log:10-Jul-2015 11:20:54.547 FINE 
[localhost-startStop-1] 
org.apache.catalina.core.StandardContext.listenerStart Sending application 
start events

logs/localhost.2015-07-10.log:10-Jul-2015 11:20:54.551 FINE 
[localhost-startStop-1] 
org.apache.catalina.core.StandardContext.filterStart Starting filters

logs/localhost.2015-07-10.log:10-Jul-2015 11:20:54.552 FINE 
[localhost-startStop-1] 
org.apache.catalina.core.StandardContext.filterStart  Starting filter 
'characterEncodingFilter'

logs/localhost.2015-07-10.log:10-Jul-2015 11:20:54.554 FINE 
[localhost-startStop-1] 
org.apache.catalina.core.StandardContext.filterStart  Starting filter 
'hiddenHttpMethodFilter'

logs/localhost.2015-07-10.log:10-Jul-2015 11:20:54.554 FINE 
[localhost-startStop-1] 
org.apache.catalina.core.StandardContext.filterStart  Starting filter 
'Tomcat WebSocket (JSR356) Filter'

logs/localhost.2015-07-10.log:10-Jul-2015 11:20:54.555 FINE 
[localhost-startStop-1] 
org.apache.catalina.core.StandardContext.filterStart  Starting filter 
'applicationContextIdFilter'

logs/localhost.2015-07-10.log:10-Jul-2015 11:20:54.555 FINE 
[localhost-startStop-1] 
org.apache.catalina.core.StandardContext.filterStart  Starting filter 
'webRequestLoggingFilter'

logs/localhost.2015-07-10.log:10-Jul-2015 11:20:54.555 FINE 
[localhost-startStop-1] 
org.apache.catalina.core.StandardContext.filterStart  Starting filter 
'errorPageFilter'

logs/localhost.2015-07-10.log:10-Jul-2015 11:20:54.556 FINE 
[localhost-startStop-1] 
org.apache.catalina.core.StandardContext.filterStart  Starting 

Tomcat 8 - Manager Deploy

[Theo . Sweeny]

Hello - currently I'm running a multi instance Tomcat 8 server and wish to 
use Manager to deploy war files via its HTTP API command line interface.

When attempting to deploy there is a continuous issue with the context 
path not being recognised.

Here is an example of the command - 

curl -v -X PUT 
http://user:password@localhost:10080/manager/text/deploy?path=/address-information-ds-1.0war=file:/usr/share/tomcat/deployments/20150706/address-information-ds-1.0
FAIL - Deployed application at context path /address-information-ds-1.0 
but context failed to start

Now check the list of installed webapps - 

$ curl -X GET http://tcsct:cbiw2PXB@localhost:10080/manager/text/list
OK - Listed applications for virtual host localhost
/manager:running:0:manager
/:running:0:ROOT
/address-information-ds-1.0:stopped:0:address-information-ds-1.0.war
/host-manager:running:0:host-manager

Localaccess.log - 

[10/Jul/2015:11:07:54 +0100] 127.0.0.1 - tcsct PUT 
/manager/text/deploy?path=/address-information-ds-1.0 HTTP/1.1 - \   - - - 
\   - ?path=/address-information-ds-1.0 200 111 - 31 26 127.0.0.1 
[10/Jul/2015:11:07:54 +0100]

Catanlina.log
10-Jul-2015 11:20:54.560 INFO [localhost-startStop-1] 
org.apache.catalina.startup.HostConfig.deployWAR Deploying web application 
archive /opt/tomcat/webapps/address-information-ds-1.0.war
/logs/catalina.2015-07-10.log:10-Jul-2015 11:20:54.568 SEVERE 
[localhost-startStop-1] 
org.apache.catalina.startup.ContextConfig.beforeStart Exception fixing 
docBase for context [/address-information-ds-1.0]
 org.apache.catalina.LifecycleException: Failed to start component 
[StandardEngine[Catalina].StandardHost[localhost].StandardContext[/address-information-ds-1.0]]
10-Jul-2015 11:20:54.572 SEVERE [localhost-startStop-1] 
org.apache.catalina.startup.HostConfig.deployWAR Error deploying web 
application archive /opt/tomcat/webapps/address-information-ds-1.0.war
 java.lang.IllegalStateException: ContainerBase.addChild: start: 
org.apache.catalina.LifecycleException: Failed to start component 
[StandardEngine[Catalina].StandardHost[localhost].StandardContext[/address-information-ds-1.0]]
10-Jul-2015 11:20:54.573 INFO [localhost-startStop-1] 
org.apache.catalina.startup.HostConfig.deployWAR Deployment of web 
application archive /opt/tomcat/webapps/address-information-ds-1.0.war has 
finished in 13 ms

Any advice or pointer would be much appreciated.

-
The Mileage Company Limited is a limited company registered in England under 
company number 2260073 whose registered office address is at
Astral Towers, Betts Way, London Road, Crawley, West Sussex, RH10 9XY.

This email and any files transmitted with it are confidential and intended 
solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify the 
system manager.

This footnote also confirms that this email message has been swept by Mimecast 
for the presence of computer viruses. 
-