subject:"tomcat is not coming Up"

Re: Tomcat is not Coming Up

2023-01-13 Thread Christopher Schultz


Prabu,

Please don't hijack threads. Start a new thread instead of replying to 
an old message. Your question will get better visibility that way.


Keep reading.

On 1/11/23 10:19, Ganesan, Prabu wrote:

Our Production Server Was Down, We have not Done any changes on this tomcat 
Level

But we are seeing this Message.
Old : INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command 
line argument: -Djava.library.path=/usr/local/apr/lib

New : INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command 
line argument: -Xmx3072m


These command-line options are completely different. I would review all 
lines with "Command line argument" in them together.



Old : INFO [main] org.apache.catalina.core.AprLifecycleListener.lifecycleEvent 
Loaded APR based Apache Tomcat Native library [1.2.23] using APR version [1.6.3]

New : INFO [main] org.apache.catalina.core.AprLifecycleListener.lifecycleEvent 
Loaded APR based Apache Tomcat Native library [1.2.17] using APR version [1.4.8]


It appears that without "any changes" your environment has suddenly been 
downgraded from tcnative 1.2.23 to tcnative 1.2.17 and from APR 1.6.3 to 
APR 1.4.8.


What version of Tomcat are you trying to launch? Has that version also 
changed from "Old" to "New"?



Is That could be reason to Not coming up the server?


Maybe. We need more information.

-chris

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

Re: tomcat is not coming Up

2023-01-12 Thread Zero


On 1/12/23 11:46, Ganesan, Prabu wrote:


Hi Team,

This is the only message we are receiving while starting the services. 
Can some one help on this .


11-Jan-2023 18:21:58.101 INFO [main] 
org.apache.catalina.startup.VersionLoggerListener.log Command line 
argument: -Djava.io.tmpdir=/srv/tomcats/tomcat1/temp
11-Jan-2023 18:21:58.101 INFO [main] 
org.apache.catalina.core.AprLifecycleListener.lifecycleEvent An older 
version [1.2.17] of the APR based Apache Tomcat Native library is 
installed, while Tomcat recommends a minimum version of [1.2.23]
11-Jan-2023 18:21:58.101 INFO [main] 
org.apache.catalina.core.AprLifecycleListener.lifecycleEvent Loaded 
APR based Apache Tomcat Native library [1.2.17] using APR version [1.4.8].
11-Jan-2023 18:21:58.101 INFO [main] 
org.apache.catalina.core.AprLifecycleListener.lifecycleEvent APR 
capabilities: IPv6 [true], sendfile [true], accept filters [false], 
random [true].
11-Jan-2023 18:21:58.101 INFO [main] 
org.apache.catalina.core.AprLifecycleListener.lifecycleEvent 
APR/OpenSSL configuration: useAprConnector [false], useOpenSSL [true]
11-Jan-2023 18:21:58.105 INFO [main] 
org.apache.catalina.core.AprLifecycleListener.initializeSSL OpenSSL 
successfully initialized [OpenSSL 1.0.2k-fips  26 Jan 2017]

LunaNamedSystemMutex: open() failed: Permission denied

Thanks & Regards,

_Email_CBE.gif

*PrabuGanesan***

*Consultant|MS-Nordics*

capgemini India Pvt. Ltd. | Bangalore **

Contact: +91 8526554535

Email: prabhu.c.gane...@capgemini.com





Out of curiosity looked at the loggings.

What does LunaNamedSystemMutex open() failed (for Luna Cloud?) mean ?

~Z



*From:*Hiran CHAUDHURI 
*Sent:* 11 January 2023 21:36
*To:* Tomcat Users List 
*Subject:* RE: tomcat is not coming Up

This mail has been sent from an external source

CONFIDENTIAL & RESTRICTED

If on the old command line the apr libs were referenced but on the new 
one it is not, I believe that could make the process not find the 
libraries to communicate.


Enough of a reason to terminate with an error, but maybe it is on 
stderr and nowhere in the logs.


  * Check where the jvm’s stderr/stdout goes to (could be cron,
system, syslog, a docker container, …). If it has an error
message, share it or act on it.
  * Check what caused the changes that you are noticing
  * Check what else it may have impacted (e.g. JVM version, keystores,
startup scripts, …)

*From:*Ganesan, Prabu 
*Sent:* Wednesday, January 11, 2023 16:25
*To:* Tomcat Users List 
*Subject:* tomcat is not coming Up

EXTERNAL Email. Be careful with links and attachments! If in doubt, 
click the Report Mail button.


Hi team

Our Production Servers are down, Not Coming up When we are trying to 
start the services


In logs we couldn’t see Any Errors only I can see Info.

Though I can see some changes in this. But we have not made any changes

*Old :* INFO [main] 
org.apache.catalina.startup.VersionLoggerListener.log Command line 
argument: -Djava.library.path=/usr/local/apr/lib


*New : *INFO [main] 
org.apache.catalina.startup.VersionLoggerListener.log Command line 
argument: -Xmx3072m



*Old : *INFO [main] 
org.apache.catalina.core.AprLifecycleListener.lifecycleEvent Loaded 
APR based Apache Tomcat Native library [1.2.23] using APR version [1.6.3]


*New :* INFO [main] 
org.apache.catalina.core.AprLifecycleListener.lifecycleEvent Loaded 
APR based Apache Tomcat Native library [1.2.17] using APR version [1.4.8]


Could you please confirm. Is this could be the reason to not start up?

We have not done any changes from our end.

Please help us what more required I ll Provide logs

Thanks & Regards,

_Email_CBE.gif

*PrabuGanesan*

*Consultant|MS-Nordics*

capgemini India Pvt. Ltd. | Bangalore **

Contact: +91 8526554535

Email: prabhu.c.gane...@capgemini.com

RE: tomcat is not coming Up

2023-01-12 Thread Simon Matter

> Hi team
>
>
> You mean to say, need to use native library version should be version
> 1.2.23??
>
>
> But we have not made any changes in this library is that Possible to  auto
> change in Version?

No, things usually don't change automagically on serious operating systems :)

But, in you old config you had '-Djava.library.path=/usr/local/apr/lib'
and maybe this is where the newer Tomcat native library is installed.
The new config seems to miss this path and it's likely that now Tomcat
uses the older library in one of the standard paths.

Regards,
Simon

>
> Thanks & Regards,
> _
> PrabuGanesan
> Consultant|MS-Nordics
> capgemini India Pvt. Ltd. | Bangalore 
> Contact: +91 8526554535
> Email: prabhu.c.gane...@capgemini.com
>
> www.capgemini.com
> People matter, results count.
> __
> Connect with Capgemini:
>
>  
> Please consider the environment and do not print this email unless
> absolutely necessary.
> Capgemini encourages environmental awareness.
>
> -Original Message-
> From: Simon Matter 
> Sent: 12 January 2023 16:24
> To: Tomcat Users List 
> Subject: RE: tomcat is not coming Up
>
> ***This mail has been sent by an external source***
>
>> Hi Team,
>>
>>
>> This is the only message we are receiving while starting the services.
>> Can some one help on this .
>>
>> 11-Jan-2023 18:21:58.101 INFO [main]
>> org.apache.catalina.startup.VersionLoggerListener.log Command line
>> argument: -Djava.io.tmpdir=/srv/tomcats/tomcat1/temp
>> 11-Jan-2023 18:21:58.101 INFO [main]
>> org.apache.catalina.core.AprLifecycleListener.lifecycleEvent An older
>> version [1.2.17] of the APR based Apache Tomcat Native library is
>> installed, while Tomcat recommends a minimum version of [1.2.23]
>
> Maybe the problem is that you have Apache Tomcat Native library 1.2.17
> installed/referenced but you should likely have version 1.2.23?
>
> Regards,
> Simon
>
>> 11-Jan-2023 18:21:58.101 INFO [main]
>> org.apache.catalina.core.AprLifecycleListener.lifecycleEvent Loaded
>> APR based Apache Tomcat Native library [1.2.17] using APR version
>> [1.4.8].
>> 11-Jan-2023 18:21:58.101 INFO [main]
>> org.apache.catalina.core.AprLifecycleListener.lifecycleEvent APR
>> capabilities: IPv6 [true], sendfile [true], accept filters [false],
>> random [true].
>> 11-Jan-2023 18:21:58.101 INFO [main]
>> org.apache.catalina.core.AprLifecycleListener.lifecycleEvent
>> APR/OpenSSL
>> configuration: useAprConnector [false], useOpenSSL [true]
>> 11-Jan-2023 18:21:58.105 INFO [main]
>> org.apache.catalina.core.AprLifecycleListener.initializeSSL OpenSSL
>> successfully initialized [OpenSSL 1.0.2k-fips  26 Jan 2017]
>> LunaNamedSystemMutex: open() failed: Permission denied
>>
>> Thanks & Regards,
>> _[Email_CBE.gi
>> f]
>> PrabuGanesan
>> Consultant|MS-Nordics
>> capgemini India Pvt. Ltd. | Bangalore
>> Contact: +91 8526554535
>> Email:
>> prabhu.c.gane...@capgemini.com<mailto:prabhu.c.gane...@capgemini.com>
>>
>> www.capgemini.com<http://www.capgemini.com/>
>> People matter, results count.
>> __
>> Connect with Capgemini:
>> [cid:image003.gif@01D926A1.46D89710]<http://www.capgemini.com/insights
>> -and-resources/blogs>[cid:image004.gif@01D926A1.46D89710]<http://www.t
>> witter.com/capgemini>[cid:image005.gif@01D926A1.46D89710]<http://www.f
>> acebook.com/capgemini>[cid:image006.gif@01D926A1.46D89710]<http://www.
>> linkedin.com/company/capgemini>[cid:image007.gif@01D926A1.46D89710]> tp://www.slideshare.net/capgemini>[cid:image008.gif@01D926A1.46D89710]
>> <http://www.youtube.com/capgeminimedia>
>>
>> Please consider the environment and do not print this email unless
>> absolutely necessary.
>> Capgemini encourages environmental awareness.
>>
>> From: Hiran CHAUDHURI 
>> Sent: 11 January 2023 21:36
>> To: Tomcat Users List 
>> Subject: RE: tomcat is not coming Up
>>
>> This mail has been sent from an external source
>>
>> CONFIDENTIAL & RESTRICTED
>>
>> If on the old command line the apr libs were referenced but on the new
>> one it is not, I believe that could make the process not find the
>> libraries to communicate.
>> Enough of a reason to terminate with an error, but maybe it is on
>> stderr and nowhere in the logs.
>

RE: tomcat is not coming Up

2023-01-12 Thread Ganesan, Prabu

Hi team


You mean to say, need to use native library version should be version 1.2.23??


But we have not made any changes in this library is that Possible to  auto 
change in Version?

Thanks & Regards,
_
PrabuGanesan
Consultant|MS-Nordics
capgemini India Pvt. Ltd. | Bangalore 
Contact: +91 8526554535
Email: prabhu.c.gane...@capgemini.com

www.capgemini.com
People matter, results count.
__
Connect with Capgemini:

 
Please consider the environment and do not print this email unless absolutely 
necessary.
Capgemini encourages environmental awareness.

-Original Message-
From: Simon Matter  
Sent: 12 January 2023 16:24
To: Tomcat Users List 
Subject: RE: tomcat is not coming Up

***This mail has been sent by an external source***

> Hi Team,
>
>
> This is the only message we are receiving while starting the services. 
> Can some one help on this .
>
> 11-Jan-2023 18:21:58.101 INFO [main]
> org.apache.catalina.startup.VersionLoggerListener.log Command line
> argument: -Djava.io.tmpdir=/srv/tomcats/tomcat1/temp
> 11-Jan-2023 18:21:58.101 INFO [main]
> org.apache.catalina.core.AprLifecycleListener.lifecycleEvent An older 
> version [1.2.17] of the APR based Apache Tomcat Native library is 
> installed, while Tomcat recommends a minimum version of [1.2.23]

Maybe the problem is that you have Apache Tomcat Native library 1.2.17 
installed/referenced but you should likely have version 1.2.23?

Regards,
Simon

> 11-Jan-2023 18:21:58.101 INFO [main]
> org.apache.catalina.core.AprLifecycleListener.lifecycleEvent Loaded 
> APR based Apache Tomcat Native library [1.2.17] using APR version [1.4.8].
> 11-Jan-2023 18:21:58.101 INFO [main]
> org.apache.catalina.core.AprLifecycleListener.lifecycleEvent APR
> capabilities: IPv6 [true], sendfile [true], accept filters [false], 
> random [true].
> 11-Jan-2023 18:21:58.101 INFO [main]
> org.apache.catalina.core.AprLifecycleListener.lifecycleEvent 
> APR/OpenSSL
> configuration: useAprConnector [false], useOpenSSL [true]
> 11-Jan-2023 18:21:58.105 INFO [main]
> org.apache.catalina.core.AprLifecycleListener.initializeSSL OpenSSL 
> successfully initialized [OpenSSL 1.0.2k-fips  26 Jan 2017]
> LunaNamedSystemMutex: open() failed: Permission denied
>
> Thanks & Regards,
> _[Email_CBE.gi
> f]
> PrabuGanesan
> Consultant|MS-Nordics
> capgemini India Pvt. Ltd. | Bangalore
> Contact: +91 8526554535
> Email:
> prabhu.c.gane...@capgemini.com<mailto:prabhu.c.gane...@capgemini.com>
>
> www.capgemini.com<http://www.capgemini.com/>
> People matter, results count.
> __
> Connect with Capgemini:
> [cid:image003.gif@01D926A1.46D89710]<http://www.capgemini.com/insights
> -and-resources/blogs>[cid:image004.gif@01D926A1.46D89710]<http://www.t
> witter.com/capgemini>[cid:image005.gif@01D926A1.46D89710]<http://www.f
> acebook.com/capgemini>[cid:image006.gif@01D926A1.46D89710]<http://www.
> linkedin.com/company/capgemini>[cid:image007.gif@01D926A1.46D89710] tp://www.slideshare.net/capgemini>[cid:image008.gif@01D926A1.46D89710]
> <http://www.youtube.com/capgeminimedia>
>
> Please consider the environment and do not print this email unless 
> absolutely necessary.
> Capgemini encourages environmental awareness.
>
> From: Hiran CHAUDHURI 
> Sent: 11 January 2023 21:36
> To: Tomcat Users List 
> Subject: RE: tomcat is not coming Up
>
> This mail has been sent from an external source
>
> CONFIDENTIAL & RESTRICTED
>
> If on the old command line the apr libs were referenced but on the new 
> one it is not, I believe that could make the process not find the 
> libraries to communicate.
> Enough of a reason to terminate with an error, but maybe it is on 
> stderr and nowhere in the logs.
>
>
>   *   Check where the jvm's stderr/stdout goes to (could be cron, system,
> syslog, a docker container, ...). If it has an error message, share it 
> or act on it.
>   *   Check what caused the changes that you are noticing
>   *   Check what else it may have impacted (e.g. JVM version, keystores,
> startup scripts, ...)
>
> From: Ganesan, Prabu
> mailto:prabhu.c.ganesan@capgem
> ini.com.INVALID>>
> Sent: Wednesday, January 11, 2023 16:25
> To: Tomcat Users List
> mailto:users@tomcat.apache.org>>
> Subject: tomcat is not coming Up
>
> EXTERNAL Email. Be careful with links and attachments! If in doubt, 
> click the Report Mail button.
>
> Hi team
>
> Our Production Servers are down, Not Coming up When we are tryi

RE: tomcat is not coming Up

2023-01-12 Thread Simon Matter

> Hi Team,
>
>
> This is the only message we are receiving while starting the services. Can
> some one help on this .
>
> 11-Jan-2023 18:21:58.101 INFO [main]
> org.apache.catalina.startup.VersionLoggerListener.log Command line
> argument: -Djava.io.tmpdir=/srv/tomcats/tomcat1/temp
> 11-Jan-2023 18:21:58.101 INFO [main]
> org.apache.catalina.core.AprLifecycleListener.lifecycleEvent An older
> version [1.2.17] of the APR based Apache Tomcat Native library is
> installed, while Tomcat recommends a minimum version of [1.2.23]

Maybe the problem is that you have Apache Tomcat Native library 1.2.17
installed/referenced but you should likely have version 1.2.23?

Regards,
Simon

> 11-Jan-2023 18:21:58.101 INFO [main]
> org.apache.catalina.core.AprLifecycleListener.lifecycleEvent Loaded APR
> based Apache Tomcat Native library [1.2.17] using APR version [1.4.8].
> 11-Jan-2023 18:21:58.101 INFO [main]
> org.apache.catalina.core.AprLifecycleListener.lifecycleEvent APR
> capabilities: IPv6 [true], sendfile [true], accept filters [false], random
> [true].
> 11-Jan-2023 18:21:58.101 INFO [main]
> org.apache.catalina.core.AprLifecycleListener.lifecycleEvent APR/OpenSSL
> configuration: useAprConnector [false], useOpenSSL [true]
> 11-Jan-2023 18:21:58.105 INFO [main]
> org.apache.catalina.core.AprLifecycleListener.initializeSSL OpenSSL
> successfully initialized [OpenSSL 1.0.2k-fips  26 Jan 2017]
> LunaNamedSystemMutex: open() failed: Permission denied
>
> Thanks & Regards,
> _[Email_CBE.gif]
> PrabuGanesan
> Consultant|MS-Nordics
> capgemini India Pvt. Ltd. | Bangalore
> Contact: +91 8526554535
> Email:
> prabhu.c.gane...@capgemini.com<mailto:prabhu.c.gane...@capgemini.com>
>
> www.capgemini.com<http://www.capgemini.com/>
> People matter, results count.
> __
> Connect with Capgemini:
> [cid:image003.gif@01D926A1.46D89710]<http://www.capgemini.com/insights-and-resources/blogs>[cid:image004.gif@01D926A1.46D89710]<http://www.twitter.com/capgemini>[cid:image005.gif@01D926A1.46D89710]<http://www.facebook.com/capgemini>[cid:image006.gif@01D926A1.46D89710]<http://www.linkedin.com/company/capgemini>[cid:image007.gif@01D926A1.46D89710]<http://www.slideshare.net/capgemini>[cid:image008.gif@01D926A1.46D89710]<http://www.youtube.com/capgeminimedia>
>
> Please consider the environment and do not print this email unless
> absolutely necessary.
> Capgemini encourages environmental awareness.
>
> From: Hiran CHAUDHURI 
> Sent: 11 January 2023 21:36
> To: Tomcat Users List 
> Subject: RE: tomcat is not coming Up
>
> This mail has been sent from an external source
>
> CONFIDENTIAL & RESTRICTED
>
> If on the old command line the apr libs were referenced but on the new one
> it is not, I believe that could make the process not find the libraries to
> communicate.
> Enough of a reason to terminate with an error, but maybe it is on stderr
> and nowhere in the logs.
>
>
>   *   Check where the jvm's stderr/stdout goes to (could be cron, system,
> syslog, a docker container, ...). If it has an error message, share it
> or act on it.
>   *   Check what caused the changes that you are noticing
>   *   Check what else it may have impacted (e.g. JVM version, keystores,
> startup scripts, ...)
>
> From: Ganesan, Prabu
> mailto:prabhu.c.gane...@capgemini.com.INVALID>>
> Sent: Wednesday, January 11, 2023 16:25
> To: Tomcat Users List
> mailto:users@tomcat.apache.org>>
> Subject: tomcat is not coming Up
>
> EXTERNAL Email. Be careful with links and attachments! If in doubt, click
> the Report Mail button.
>
> Hi team
>
> Our Production Servers are down, Not Coming up When we are trying to start
> the services
>
> In logs we couldn't see Any Errors only I can see Info.
>
>
> Though I can see some changes in this. But we have not made any changes
>
>
>
>
> Old : INFO [main] org.apache.catalina.startup.VersionLoggerListener.log
> Command line argument: -Djava.library.path=/usr/local/apr/lib
>
>
>
> New : INFO [main] org.apache.catalina.startup.VersionLoggerListener.log
> Command line argument: -Xmx3072m
>
>
>
> Old : INFO [main]
> org.apache.catalina.core.AprLifecycleListener.lifecycleEvent Loaded APR
> based Apache Tomcat Native library [1.2.23] using APR version [1.6.3]
>
>
>
> New : INFO [main]
> org.apache.catalina.core.AprLifecycleListener.lifecycleEvent Loaded APR
> based Apache Tomcat Native library [1.2.17] using APR version [1.4.8]
>
>
>
>
>
>
> Could you please confirm. Is this could be the reason to not start up

RE: tomcat is not coming Up

2023-01-12 Thread Ganesan, Prabu

Please some one help on this.


In middle services are came up again. Gone down.

Thanks & Regards,
_[Email_CBE.gif]
PrabuGanesan
Consultant|MS-Nordics
capgemini India Pvt. Ltd. | Bangalore
Contact: +91 8526554535
Email: prabhu.c.gane...@capgemini.com<mailto:prabhu.c.gane...@capgemini.com>

www.capgemini.com<http://www.capgemini.com/>
People matter, results count.
__
Connect with Capgemini:
[cid:image003.gif@01D926A1.6427A450]<http://www.capgemini.com/insights-and-resources/blogs>[cid:image004.gif@01D926A1.6427A450]<http://www.twitter.com/capgemini>[cid:image005.gif@01D926A1.6427A450]<http://www.facebook.com/capgemini>[cid:image006.gif@01D926A1.6427A450]<http://www.linkedin.com/company/capgemini>[cid:image007.gif@01D926A1.6427A450]<http://www.slideshare.net/capgemini>[cid:image008.gif@01D926A1.6427A450]<http://www.youtube.com/capgeminimedia>

Please consider the environment and do not print this email unless absolutely 
necessary.
Capgemini encourages environmental awareness.

From: Hiran CHAUDHURI 
Sent: 11 January 2023 21:36
To: Tomcat Users List 
Subject: RE: tomcat is not coming Up

This mail has been sent from an external source

CONFIDENTIAL & RESTRICTED

If on the old command line the apr libs were referenced but on the new one it 
is not, I believe that could make the process not find the libraries to 
communicate.
Enough of a reason to terminate with an error, but maybe it is on stderr and 
nowhere in the logs.


  *   Check where the jvm's stderr/stdout goes to (could be cron, system, 
syslog, a docker container, ...). If it has an error message, share it or act 
on it.
  *   Check what caused the changes that you are noticing
  *   Check what else it may have impacted (e.g. JVM version, keystores, 
startup scripts, ...)

From: Ganesan, Prabu 
mailto:prabhu.c.gane...@capgemini.com.INVALID>>
Sent: Wednesday, January 11, 2023 16:25
To: Tomcat Users List mailto:users@tomcat.apache.org>>
Subject: tomcat is not coming Up

EXTERNAL Email. Be careful with links and attachments! If in doubt, click the 
Report Mail button.

Hi team

Our Production Servers are down, Not Coming up When we are trying to start the 
services

In logs we couldn't see Any Errors only I can see Info.


Though I can see some changes in this. But we have not made any changes




Old : INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command 
line argument: -Djava.library.path=/usr/local/apr/lib



New : INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command 
line argument: -Xmx3072m



Old : INFO [main] org.apache.catalina.core.AprLifecycleListener.lifecycleEvent 
Loaded APR based Apache Tomcat Native library [1.2.23] using APR version [1.6.3]



New : INFO [main] org.apache.catalina.core.AprLifecycleListener.lifecycleEvent 
Loaded APR based Apache Tomcat Native library [1.2.17] using APR version [1.4.8]






Could you please confirm. Is this could be the reason to not start up?

We have not done any changes from our end.


Please help us what more required I ll Provide logs

Thanks & Regards,
_[Email_CBE.gif]
PrabuGanesan
Consultant|MS-Nordics
capgemini India Pvt. Ltd. | Bangalore
Contact: +91 8526554535
Email: prabhu.c.gane...@capgemini.com<mailto:prabhu.c.gane...@capgemini.com>

www.capgemini.com<https://eur01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.capgemini.com%2F=05%7C01%7C%7Ce6125a557f204176387108daf3e84162%7Cb3f4f7c272ce4192aba4d6c7719b5766%7C0%7C0%7C638090476104668282%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=OuRPBo1TUADmKbCC%2F1PZ7UDPow2dBSMIaAJ%2BSoirPmw%3D=0>
People matter, results count.
__
Connect with Capgemini:
[cid:image002.gif@01D925FE.A0045660]<https://eur01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.capgemini.com%2Finsights-and-resources%2Fblogs=05%7C01%7C%7Ce6125a557f204176387108daf3e84162%7Cb3f4f7c272ce4192aba4d6c7719b5766%7C0%7C0%7C638090476104668282%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=y8xcNMrV11XNOvzmts3hXL%2Fqr%2FzJNqQOr16goDKiwcI%3D=0>[cid:image003.gif@01D925FE.A0045660]<https://eur01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.twitter.com%2Fcapgemini=05%7C01%7C%7Ce6125a557f204176387108daf3e84162%7Cb3f4f7c272ce4192aba4d6c7719b5766%7C0%7C0%7C638090476104668282%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=%2By3z7iKi%2Bvx3hcAUYPI%2BDbmsCUN49GTX2bWBZRJs%2Bsg%3D=0>[cid:image004.gif@01D925FE.A0045660]<https://eur01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.facebook.com%2Fcapgemini=05%7C01%7C%7Ce6125a5

RE: tomcat is not coming Up

2023-01-12 Thread Ganesan, Prabu

Hi Team,


This is the only message we are receiving while starting the services. Can some 
one help on this .

11-Jan-2023 18:21:58.101 INFO [main] 
org.apache.catalina.startup.VersionLoggerListener.log Command line argument: 
-Djava.io.tmpdir=/srv/tomcats/tomcat1/temp
11-Jan-2023 18:21:58.101 INFO [main] 
org.apache.catalina.core.AprLifecycleListener.lifecycleEvent An older version 
[1.2.17] of the APR based Apache Tomcat Native library is installed, while 
Tomcat recommends a minimum version of [1.2.23]
11-Jan-2023 18:21:58.101 INFO [main] 
org.apache.catalina.core.AprLifecycleListener.lifecycleEvent Loaded APR based 
Apache Tomcat Native library [1.2.17] using APR version [1.4.8].
11-Jan-2023 18:21:58.101 INFO [main] 
org.apache.catalina.core.AprLifecycleListener.lifecycleEvent APR capabilities: 
IPv6 [true], sendfile [true], accept filters [false], random [true].
11-Jan-2023 18:21:58.101 INFO [main] 
org.apache.catalina.core.AprLifecycleListener.lifecycleEvent APR/OpenSSL 
configuration: useAprConnector [false], useOpenSSL [true]
11-Jan-2023 18:21:58.105 INFO [main] 
org.apache.catalina.core.AprLifecycleListener.initializeSSL OpenSSL 
successfully initialized [OpenSSL 1.0.2k-fips  26 Jan 2017]
LunaNamedSystemMutex: open() failed: Permission denied

Thanks & Regards,
_[Email_CBE.gif]
PrabuGanesan
Consultant|MS-Nordics
capgemini India Pvt. Ltd. | Bangalore
Contact: +91 8526554535
Email: prabhu.c.gane...@capgemini.com<mailto:prabhu.c.gane...@capgemini.com>

www.capgemini.com<http://www.capgemini.com/>
People matter, results count.
__
Connect with Capgemini:
[cid:image003.gif@01D926A1.46D89710]<http://www.capgemini.com/insights-and-resources/blogs>[cid:image004.gif@01D926A1.46D89710]<http://www.twitter.com/capgemini>[cid:image005.gif@01D926A1.46D89710]<http://www.facebook.com/capgemini>[cid:image006.gif@01D926A1.46D89710]<http://www.linkedin.com/company/capgemini>[cid:image007.gif@01D926A1.46D89710]<http://www.slideshare.net/capgemini>[cid:image008.gif@01D926A1.46D89710]<http://www.youtube.com/capgeminimedia>

Please consider the environment and do not print this email unless absolutely 
necessary.
Capgemini encourages environmental awareness.

From: Hiran CHAUDHURI 
Sent: 11 January 2023 21:36
To: Tomcat Users List 
Subject: RE: tomcat is not coming Up

This mail has been sent from an external source

CONFIDENTIAL & RESTRICTED

If on the old command line the apr libs were referenced but on the new one it 
is not, I believe that could make the process not find the libraries to 
communicate.
Enough of a reason to terminate with an error, but maybe it is on stderr and 
nowhere in the logs.


  *   Check where the jvm's stderr/stdout goes to (could be cron, system, 
syslog, a docker container, ...). If it has an error message, share it or act 
on it.
  *   Check what caused the changes that you are noticing
  *   Check what else it may have impacted (e.g. JVM version, keystores, 
startup scripts, ...)

From: Ganesan, Prabu 
mailto:prabhu.c.gane...@capgemini.com.INVALID>>
Sent: Wednesday, January 11, 2023 16:25
To: Tomcat Users List mailto:users@tomcat.apache.org>>
Subject: tomcat is not coming Up

EXTERNAL Email. Be careful with links and attachments! If in doubt, click the 
Report Mail button.

Hi team

Our Production Servers are down, Not Coming up When we are trying to start the 
services

In logs we couldn't see Any Errors only I can see Info.


Though I can see some changes in this. But we have not made any changes




Old : INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command 
line argument: -Djava.library.path=/usr/local/apr/lib



New : INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command 
line argument: -Xmx3072m



Old : INFO [main] org.apache.catalina.core.AprLifecycleListener.lifecycleEvent 
Loaded APR based Apache Tomcat Native library [1.2.23] using APR version [1.6.3]



New : INFO [main] org.apache.catalina.core.AprLifecycleListener.lifecycleEvent 
Loaded APR based Apache Tomcat Native library [1.2.17] using APR version [1.4.8]






Could you please confirm. Is this could be the reason to not start up?

We have not done any changes from our end.


Please help us what more required I ll Provide logs

Thanks & Regards,
_[Email_CBE.gif]
PrabuGanesan
Consultant|MS-Nordics
capgemini India Pvt. Ltd. | Bangalore
Contact: +91 8526554535
Email: prabhu.c.gane...@capgemini.com<mailto:prabhu.c.gane...@capgemini.com>

www.capgemini.com<https://eur01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.capgemini.com%2F=05%7C01%7C%7Ce6125a557f204176387108daf3e84162%7Cb3f4f7c272ce4192aba4d6c7719b5766%7C0%7C0%7C638090476104668282%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn

AW: Tomcat is not Coming Up

2023-01-11 Thread Thomas Hoffmann (Speed4Trade GmbH)

Hello,

> -Ursprüngliche Nachricht-
> Von: Ganesan, Prabu 
> Gesendet: Mittwoch, 11. Januar 2023 16:19
> An: Tomcat Users List 
> Betreff: Tomcat is not Coming Up
> 
> Hi Team
> 
> Need Emergency Help,
> 
> 
> 
> Our Production Server Was Down, We have not Done any changes on this
> tomcat Level
> 
> But we are seeing this Message.
> 
> 
> 
> Old : INFO [main] org.apache.catalina.startup.VersionLoggerListener.log
> Command line argument: -Djava.library.path=/usr/local/apr/lib
> 
> 
> 
> New : INFO [main] org.apache.catalina.startup.VersionLoggerListener.log
> Command line argument: -Xmx3072m
> 
> 
> 
> 
> 
> Old : INFO [main] org.apache.catalina.core.AprLifecycleListener.lifecycleEvent
> Loaded APR based Apache Tomcat Native library [1.2.23] using APR version
> [1.6.3]
> 
> 
> 
> New : INFO [main] org.apache.catalina.core.AprLifecycleListener.lifecycleEvent
> Loaded APR based Apache Tomcat Native library [1.2.17] using APR version
> [1.4.8]
> 
> 
> 
> Is That could be reason to Not coming up the server?
> 
> 
> Can someone Help me Please. We are not able to Start the services.
> 
> 
> 
> Thanks & Regards,
> _

There is no error visible in the provided snippet.
Usually, there are errors logged in other logfiles.
Please check every logfile in tomcat/logs folder and also check syslog for 
related errors.

Greetings,
Thomas

RE: tomcat is not coming Up

2023-01-11 Thread Hiran CHAUDHURI

CONFIDENTIAL & RESTRICTED

If on the old command line the apr libs were referenced but on the new one it 
is not, I believe that could make the process not find the libraries to 
communicate.
Enough of a reason to terminate with an error, but maybe it is on stderr and 
nowhere in the logs.


  *   Check where the jvm's stderr/stdout goes to (could be cron, system, 
syslog, a docker container, ...). If it has an error message, share it or act 
on it.
  *   Check what caused the changes that you are noticing
  *   Check what else it may have impacted (e.g. JVM version, keystores, 
startup scripts, ...)

From: Ganesan, Prabu 
Sent: Wednesday, January 11, 2023 16:25
To: Tomcat Users List 
Subject: tomcat is not coming Up

EXTERNAL Email. Be careful with links and attachments! If in doubt, click the 
Report Mail button.

Hi team

Our Production Servers are down, Not Coming up When we are trying to start the 
services

In logs we couldn't see Any Errors only I can see Info.


Though I can see some changes in this. But we have not made any changes




Old : INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command 
line argument: -Djava.library.path=/usr/local/apr/lib



New : INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command 
line argument: -Xmx3072m



Old : INFO [main] org.apache.catalina.core.AprLifecycleListener.lifecycleEvent 
Loaded APR based Apache Tomcat Native library [1.2.23] using APR version [1.6.3]



New : INFO [main] org.apache.catalina.core.AprLifecycleListener.lifecycleEvent 
Loaded APR based Apache Tomcat Native library [1.2.17] using APR version [1.4.8]






Could you please confirm. Is this could be the reason to not start up?

We have not done any changes from our end.


Please help us what more required I ll Provide logs

Thanks & Regards,
_[Email_CBE.gif]
PrabuGanesan
Consultant|MS-Nordics
capgemini India Pvt. Ltd. | Bangalore
Contact: +91 8526554535
Email: prabhu.c.gane...@capgemini.com<mailto:prabhu.c.gane...@capgemini.com>

www.capgemini.com<https://eur01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.capgemini.com%2F=05%7C01%7C%7Ce6125a557f204176387108daf3e84162%7Cb3f4f7c272ce4192aba4d6c7719b5766%7C0%7C0%7C638090476104668282%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=OuRPBo1TUADmKbCC%2F1PZ7UDPow2dBSMIaAJ%2BSoirPmw%3D=0>
People matter, results count.
__
Connect with Capgemini:
[cid:image002.gif@01D925FE.A0045660]<https://eur01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.capgemini.com%2Finsights-and-resources%2Fblogs=05%7C01%7C%7Ce6125a557f204176387108daf3e84162%7Cb3f4f7c272ce4192aba4d6c7719b5766%7C0%7C0%7C638090476104668282%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=y8xcNMrV11XNOvzmts3hXL%2Fqr%2FzJNqQOr16goDKiwcI%3D=0>[cid:image003.gif@01D925FE.A0045660]<https://eur01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.twitter.com%2Fcapgemini=05%7C01%7C%7Ce6125a557f204176387108daf3e84162%7Cb3f4f7c272ce4192aba4d6c7719b5766%7C0%7C0%7C638090476104668282%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=%2By3z7iKi%2Bvx3hcAUYPI%2BDbmsCUN49GTX2bWBZRJs%2Bsg%3D=0>[cid:image004.gif@01D925FE.A0045660]<https://eur01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.facebook.com%2Fcapgemini=05%7C01%7C%7Ce6125a557f204176387108daf3e84162%7Cb3f4f7c272ce4192aba4d6c7719b5766%7C0%7C0%7C638090476104668282%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=qIiBm7KNOsgwEWbi3sOPOU%2FYhNdqkZSotLusq3BMeoQ%3D=0>[cid:image005.gif@01D925FE.A0045660]<https://eur01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.linkedin.com%2Fcompany%2Fcapgemini=05%7C01%7C%7Ce6125a557f204176387108daf3e84162%7Cb3f4f7c272ce4192aba4d6c7719b5766%7C0%7C0%7C638090476104824491%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=XKuCntgPlDh2fC8nicqZF4H6cBPMrhorkokizx3lmPg%3D=0>[cid:image006.gif@01D925FE.A0045660]<https://eur01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.slideshare.net%2Fcapgemini=05%7C01%7C%7Ce6125a557f204176387108daf3e84162%7Cb3f4f7c272ce4192aba4d6c7719b5766%7C0%7C0%7C638090476104824491%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=f7CO9sFovtCSeOCnlH4FoNf9c3iviKjk5u6ht9s9dDQ%3D=0>[cid:image007.gif@01D925FE.A0045660]<https://eur01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.youtube.com%2Fcapgeminimedia=05%7C01%7C%7Ce6125a557f204176387108daf3e84162%7Cb3f4f7c272ce4192aba4d6c7719b5766%7C0%7C0%7C638090476104824491%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C

Re: tomcat is not coming Up

2023-01-11 Thread Simon Matter

Hi

> Hi team
>
> Our Production Servers are down, Not Coming up When we are trying to start
> the services
>
> In logs we couldn't see Any Errors only I can see Info.
>
>
> Though I can see some changes in this. But we have not made any changes
>
>
>
>
> Old : INFO [main] org.apache.catalina.startup.VersionLoggerListener.log
> Command line argument: -Djava.library.path=/usr/local/apr/lib
>
>
>
> New : INFO [main] org.apache.catalina.startup.VersionLoggerListener.log
> Command line argument: -Xmx3072m
>
>
>
> Old : INFO [main]
> org.apache.catalina.core.AprLifecycleListener.lifecycleEvent Loaded APR
> based Apache Tomcat Native library [1.2.23] using APR version [1.6.3]
>
>
>
> New : INFO [main]
> org.apache.catalina.core.AprLifecycleListener.lifecycleEvent Loaded APR
> based Apache Tomcat Native library [1.2.17] using APR version [1.4.8]

You really didn't provide a lot of info but one thing is strange: Tomcat
native and APR are now an older version than before. Are you sure this is
really on the same host? Or was the whole Tomcat environment moved to
another server (VM?) and now things don't work anymore?

Regards,
Simon


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

Re: tomcat is not coming Up

2023-01-11 Thread Suvendu Sekhar Mondal

Hello Prabu,

On Wed, Jan 11, 2023, 8:56 PM Ganesan, Prabu
 wrote:

> Hi team
>
>
>
> Our Production Servers are down, Not Coming up When we are trying to start
> the services
>
Which OS are you using? Please provide some basic details ( like OS, Tomcat
version, JRE version ) about your environment so that this community can
provide some help.

>
>
> In logs we couldn’t see Any Errors only I can see Info.
>
>
>
These logs are normal but indicates change in APR version.

>
>
> Though I can see some changes in this. But we have not made any changes
>
>
>
>
>
> *Old :* INFO [main] org.apache.catalina.startup.VersionLoggerListener.log
> Command line argument: -Djava.library.path=/usr/local/apr/lib
>
>
>
> *New : *INFO [main] org.apache.catalina.startup.VersionLoggerListener.log
> Command line argument: -Xmx3072m
>
>
>
>
> *Old : *INFO [main]
> org.apache.catalina.core.AprLifecycleListener.lifecycleEvent Loaded APR
> based Apache Tomcat Native library [1.2.23] using APR version [1.6.3]
>
>
>
> *New :* INFO [main]
> org.apache.catalina.core.AprLifecycleListener.lifecycleEvent Loaded APR
> based Apache Tomcat Native library [1.2.17] using APR version [1.4.8]
>
>
>
>
>
>
>
>
>
> Could you please confirm. Is this could be the reason to not start up?
>
>
>
> We have not done any changes from our end.
>
>
>
>
>
> Please help us what more required I ll Provide logs
>
>
>
> Thanks & Regards,
>
> _[image:
> Email_CBE.gif]
>
> *PrabuGanesan*
>
> *Consultant|MS-Nordics*
>
> capgemini India Pvt. Ltd. | Bangalore
>
> Contact: +91 8526554535
>
> Email: prabhu.c.gane...@capgemini.com
>
>
>
> www.capgemini.com
>
> *People matter, results count.*
>
> __
>
> *Connect with Capgemini:*
> 
>  
> 
> 
> 
>
>
>
> Please consider the environment and do not print this email unless
> absolutely necessary.
>
> Capgemini encourages environmental awareness.
>
>
> This message contains information that may be privileged or confidential
> and is the property of the Capgemini Group. It is intended only for the
> person to whom it is addressed. If you are not the intended recipient, you
> are not authorized to read, print, retain, copy, disseminate, distribute,
> or use this message or any part thereof. If you receive this message in
> error, please notify the sender immediately and delete all copies of this
> message.
>

Re: Tomcat is not Coming Up

2023-01-11 Thread RAVIRAJ SHAH

Check your server.xml file
APR related commented config seems changed.

On Wed, 11 Jan, 2023, 20:51 Ganesan, Prabu,
 wrote:

> Hi Team
>
> Need Emergency Help,
>
>
>
> Our Production Server Was Down, We have not Done any changes on this
> tomcat Level
>
> But we are seeing this Message.
>
>
>
> Old : INFO [main] org.apache.catalina.startup.VersionLoggerListener.log
> Command line argument: -Djava.library.path=/usr/local/apr/lib
>
>
>
> New : INFO [main] org.apache.catalina.startup.VersionLoggerListener.log
> Command line argument: -Xmx3072m
>
>
>
>
>
> Old : INFO [main]
> org.apache.catalina.core.AprLifecycleListener.lifecycleEvent Loaded APR
> based Apache Tomcat Native library [1.2.23] using APR version [1.6.3]
>
>
>
> New : INFO [main]
> org.apache.catalina.core.AprLifecycleListener.lifecycleEvent Loaded APR
> based Apache Tomcat Native library [1.2.17] using APR version [1.4.8]
>
>
>
> Is That could be reason to Not coming up the server?
>
>
> Can someone Help me Please. We are not able to Start the services.
>
>
>
> Thanks & Regards,
> _
> PrabuGanesan
> Consultant|MS-Nordics
> capgemini India Pvt. Ltd. | Bangalore
> Contact: +91 8526554535
> Email: prabhu.c.gane...@capgemini.com
>
> www.capgemini.com
> People matter, results count.
> __
> Connect with Capgemini:
>
>
> Please consider the environment and do not print this email unless
> absolutely necessary.
> Capgemini encourages environmental awareness.
>
> -Original Message-
> From: Rob Sargent 
> Sent: 31 December 2022 08:33
> To: users@tomcat.apache.org
> Subject: Re: Tomcat 10 on Windows 11 error
>
> ***This mail has been sent by an external source***
>
>
> On 12/30/22 17:59, Shawn Heisey wrote:
> > On 12/30/22 17:03, Carles Franquesa wrote:
> >> Once downloaded, installed, and configured in the settings of the
> >> netbeans project, the error has changed, what always is very hopeful.
> >>
> >> Now, the thing is that the compiler gives this new output:
> >>
> >> image.png
> >>
> >> Tried to modify the compiler options in the project properties,
> >> image.png but, obviously, is not the place.
> >>
> >> Do you now where should I modify the compiler option Xbootclasspath?
> >>
> >> And I feel sorry for not having checked exactly "URLEncoder.encode
> >> TomcatManagerImpl". Trust me when I say I have been googling so far
> >> as extenuation...
> >
> > The mailing list ate your image attachments.  Nobody can see them.
> >
> > You need to put the images on a file sharing site and provide a URL
> > like you did for the first message on the thread.
> >
> > The later message says you got it working, so I guess the images are
> > no longer needed.
> >
> Better yet, copy as text, paste here.  You're just dealing with compiler
> output and a config file after all.
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: users-h...@tomcat.apache.org
>
> This message contains information that may be privileged or confidential
> and is the property of the Capgemini Group. It is intended only for the
> person to whom it is addressed. If you are not the intended recipient, you
> are not authorized to read, print, retain, copy, disseminate, distribute,
> or use this message or any part thereof. If you receive this message in
> error, please notify the sender immediately and delete all copies of this
> message.
>
> -
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: users-h...@tomcat.apache.org
>

tomcat is not coming Up

2023-01-11 Thread Ganesan, Prabu

Hi team

Our Production Servers are down, Not Coming up When we are trying to start the 
services

In logs we couldn't see Any Errors only I can see Info.


Though I can see some changes in this. But we have not made any changes




Old : INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command 
line argument: -Djava.library.path=/usr/local/apr/lib



New : INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command 
line argument: -Xmx3072m



Old : INFO [main] org.apache.catalina.core.AprLifecycleListener.lifecycleEvent 
Loaded APR based Apache Tomcat Native library [1.2.23] using APR version [1.6.3]



New : INFO [main] org.apache.catalina.core.AprLifecycleListener.lifecycleEvent 
Loaded APR based Apache Tomcat Native library [1.2.17] using APR version [1.4.8]






Could you please confirm. Is this could be the reason to not start up?

We have not done any changes from our end.


Please help us what more required I ll Provide logs

Thanks & Regards,
_[Email_CBE.gif]
PrabuGanesan
Consultant|MS-Nordics
capgemini India Pvt. Ltd. | Bangalore
Contact: +91 8526554535
Email: prabhu.c.gane...@capgemini.com

www.capgemini.com
People matter, results count.
__
Connect with Capgemini:
[cid:image002.gif@01D925FE.A0045660][cid:image003.gif@01D925FE.A0045660][cid:image004.gif@01D925FE.A0045660][cid:image005.gif@01D925FE.A0045660][cid:image006.gif@01D925FE.A0045660][cid:image007.gif@01D925FE.A0045660]

Please consider the environment and do not print this email unless absolutely 
necessary.
Capgemini encourages environmental awareness.

This message contains information that may be privileged or confidential and is 
the property of the Capgemini Group. It is intended only for the person to whom 
it is addressed. If you are not the intended recipient, you are not authorized 
to read, print, retain, copy, disseminate, distribute, or use this message or 
any part thereof. If you receive this message in error, please notify the 
sender immediately and delete all copies of this message.

Tomcat is not Coming Up

2023-01-11 Thread Ganesan, Prabu

Hi Team 

Need Emergency Help,

Our Production Server Was Down, We have not Done any changes on this tomcat 
Level

But we are seeing this Message.

Old : INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command 
line argument: -Djava.library.path=/usr/local/apr/lib

New : INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command 
line argument: -Xmx3072m

Old : INFO [main] org.apache.catalina.core.AprLifecycleListener.lifecycleEvent 
Loaded APR based Apache Tomcat Native library [1.2.23] using APR version [1.6.3]

New : INFO [main] org.apache.catalina.core.AprLifecycleListener.lifecycleEvent 
Loaded APR based Apache Tomcat Native library [1.2.17] using APR version [1.4.8]

Is That could be reason to Not coming up the server?

Can someone Help me Please. We are not able to Start the services.

Thanks & Regards,
_
PrabuGanesan
Consultant|MS-Nordics
capgemini India Pvt. Ltd. | Bangalore 
Contact: +91 8526554535
Email: prabhu.c.gane...@capgemini.com

www.capgemini.com
People matter, results count.
__
Connect with Capgemini:

Please consider the environment and do not print this email unless absolutely 
necessary.
Capgemini encourages environmental awareness.

-Original Message-
From: Rob Sargent  
Sent: 31 December 2022 08:33
To: users@tomcat.apache.org
Subject: Re: Tomcat 10 on Windows 11 error

***This mail has been sent by an external source***

On 12/30/22 17:59, Shawn Heisey wrote:
> On 12/30/22 17:03, Carles Franquesa wrote:
>> Once downloaded, installed, and configured in the settings of the 
>> netbeans project, the error has changed, what always is very hopeful.
>>
>> Now, the thing is that the compiler gives this new output:
>>
>> image.png
>>
>> Tried to modify the compiler options in the project properties, 
>> image.png but, obviously, is not the place.
>>
>> Do you now where should I modify the compiler option Xbootclasspath?
>>
>> And I feel sorry for not having checked exactly "URLEncoder.encode 
>> TomcatManagerImpl". Trust me when I say I have been googling so far 
>> as extenuation...
>
> The mailing list ate your image attachments.  Nobody can see them.
>
> You need to put the images on a file sharing site and provide a URL 
> like you did for the first message on the thread.
>
> The later message says you got it working, so I guess the images are 
> no longer needed.
>
Better yet, copy as text, paste here.  You're just dealing with compiler output 
and a config file after all.

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

This message contains information that may be privileged or confidential and is 
the property of the Capgemini Group. It is intended only for the person to whom 
it is addressed. If you are not the intended recipient, you are not authorized 
to read, print, retain, copy, disseminate, distribute, or use this message or 
any part thereof. If you receive this message in error, please notify the 
sender immediately and delete all copies of this message.

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

Re: Tomcat 8.5.73 not coming up on customer box. "Bind failed."

2022-04-15 Thread Christopher Schultz


James,

On 4/15/22 14:24, James H. H. Lampert wrote:

On 4/15/22 10:37 AM, Christopher Schultz (of the Tomcat Users' List) wrote:
. . .
Try specifying the "address" attribute of  along with the 
port. Give it a concrete IP address instead of "localhost" and see if 
that improves things.

. . .

My Dear Mr. Schultz:


I think we know each other well enough to dispense with the formalities. 
Your Majesty is just fine.



That did it!


\o/

Not knowing whether to give it 127.0.0.1 or give it the box's actual IP 
address, I gave it the former.


There is an important difference between the two, and I would encourage 
you to continue to use 127.0.0.1, especially for the "shutdown port". If 
you pick 127.0.0.1 then only loopback connections can connect to that 
port. If you choose the server's public IP, then anyone on the network 
knowing the secret shutdown phrase (you'll never guess what the default 
is!) can simply connect and cause a shutdown of your service.


For the HTTP port, you probably want the public IP and not the loopback, 
but there are plenty of reasons to use the loopback only, as well. 
Usually you want to use 0.0.0.0 or :: to mean "all interfaces" so anyone 
anywhere can reach you.


It works. And the connector is configured to listen on anything, so it 
came up just fine, and is entirely visible from the outside world.


Cool.

But that still leaves open the question of why an IBM Midrange box would 
suddenly start disregarding its own host table. I've never heard of a 
scenario in which *any* box with a TCP stack would disregard its own 
host table (and indeed, on any box under my control that can browse the 
Web, in which the host table is user-modifiable, I use host table 
entries to ensure that I can't be tricked [it's happened, more than 
once] into accessing Facebook, Twitter, LinkedIn, or a few other noisome 
domains).


What can make a box disregard its own host table?


I have no idea. AS/400 always seems to be yelling about everything, so 
maybe the TCP stack just finally lost its hearing.


-chris

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

Re: Tomcat 8.5.73 not coming up on customer box. "Bind failed."

2022-04-15 Thread James H. H. Lampert

In response to my question about what could cause a system to disregard 
its own host table,


On 4/15/22 11:31 AM, Jack Woehr (of the Midrange List) wrote:

Which order the search happens, DNS or hosts table first, is an option in
IBM i TCP configuration. CFGTCP option 12.


Fascinating. I can't begin to imagine how setting it to "*REMOTE" could 
possibly be useful (or that the OS would *allow* LOCALHOST or LOOPBACK 
to be overridden), but I see that at least one other customer box has 
this setting.


I will note that this, by itself, wasn't enough to kill Tomcat. It was a 
combination of this, and a DNS (presumably a "house DNS" rather than a 
public one) that recognized LOCALHOST and LOOPBACK, and responded with 
"LOCALHOST." or "LOOPBACK.," and an 
address that was something other than 127.0.0.1, that did it.


--
JHHL

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

Re: Tomcat 8.5.73 not coming up on customer box. "Bind failed."

2022-04-15 Thread James H. H. Lampert


On 4/15/22 10:37 AM, Christopher Schultz (of the Tomcat Users' List) wrote:
. . .
Try specifying the "address" attribute of  along with the port. 
Give it a concrete IP address instead of "localhost" and see if that 
improves things.

. . .

My Dear Mr. Schultz:

That did it!

Not knowing whether to give it 127.0.0.1 or give it the box's actual IP 
address, I gave it the former.


It works. And the connector is configured to listen on anything, so it 
came up just fine, and is entirely visible from the outside world.


But that still leaves open the question of why an IBM Midrange box would 
suddenly start disregarding its own host table. I've never heard of a 
scenario in which *any* box with a TCP stack would disregard its own 
host table (and indeed, on any box under my control that can browse the 
Web, in which the host table is user-modifiable, I use host table 
entries to ensure that I can't be tricked [it's happened, more than 
once] into accessing Facebook, Twitter, LinkedIn, or a few other noisome 
domains).


What can make a box disregard its own host table?

--
JHHL

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

Re: Tomcat 8.5.73 not coming up on customer box. "Bind failed."

2022-04-15 Thread James H. H. Lampert


On 4/15/22 10:37 AM, Christopher Schultz (on the Tomcat Users' List) wrote:
. . .
if "localhost" doesn't resolve to 127.0.0.1 on your system, you 
may get this error. Can you quickly check it's not a DNS resolution 
failure?


THIS is interesting.

If I look at the host table entries, I see
   ::1 IPV6-LOOPBACK
   IPV6-LOCALHOST
   127.0.0.1   LOOPBACK
   LOCALHOST

Now if I ping '127.0.0.1' on this box, I get a normal response.

If I ping localhost on our box, or another customer box, I get

Verifying connection to host system LOOPBACK at address 127.0.0.1.


followed by a normal response.

But if I ping localhost or loopback on this box, I get

Verifying connection to host system LOOPBACK. at address .

or

Verifying connection to host system LOCALHOST. at address .


Somehow, this box is DISREGARDING ITS OWN HOST TABLE!

--
JHHL

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

Re: Tomcat 8.5.73 not coming up on customer box. "Bind failed."

2022-04-15 Thread Christopher Schultz

James,

On 4/15/22 12:24, James H. H. Lampert wrote:
This morning, I arrived at work to find that a customer was complaining
about their Tomcat server (running on an IBM Midrange box).

It had locked up last night, while being shut down, and now, if you try
to start it, it fails with
15-Apr-2022 10:35:34.867 SEVERE [main]
org.apache.catalina.core.StandardServer.await StandardServer.await:
create[localhost:8005]:
java.net.BindException: The socket name is not available on this
system. (Bind failed)

This is an interesting error message.

Usually you'd get this one if the port were already in use:

Exception in thread "main" java.net.BindException: Address already in
use (Bind failed)

You can also get this:

Exception in thread "main" java.net.BindException: Can't assign
requested address (Bind failed)

This is what happens when you try to bind to a port using an
unrecognized hostname (like trying to bind to www.google.com:8009 on
your own server).

But "The socket name is not available on this system" is a different
beast. I did some quick Googling and found this which may or may not be
relevant:

https://www.ibm.com/support/pages/infosphere-change-data-capture-dmconfigurets-error-socket-name-not-available-system

tldr; if "localhost" doesn't resolve to 127.0.0.1 on your system, you
may get this error. Can you quickly check it's not a DNS resolution failure?

It might also be an IPv4-vs-IPv6 thing, if "host localhost" (or
equivalent on AS/400) returns ::1 instead of 127.0.0.1 (or both).

Try specifying the "address" attribute of along with the port.
Give it a concrete IP address instead of "localhost" and see if that
improves things.

It's possible you'll still get a failure when the HTTP connector tries
to bind. If that happens, make the same change on the and
you should be good to go.

-chris

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

Re: Tomcat 8.5.73 not coming up on customer box. "Bind failed."

2022-04-15 Thread James H. H. Lampert


On 4/15/22 9:54 AM, Jim Oberholtzer wrote:

On a modern system if you're contemplating stopping/starting TCP you might
just as well IPL.  Seems like using a nuke when a 100# bomb might work
though.


Looking at the QSYSOPR messages, I see that the system was taken down to 
restricted condition at 01:04 this morning, system time, for a backup, 
which completed at 02:03, with the subsystems, and TCP, starting.


Looking at catalina.out for *YESTERDAY* shows Tomcat being shut down at 
01:04 yesterday morning, and coming back up at 02:04 that morning, 
without incident.


Today, however, catalina.out shows the same thing up to the point where 
8005 shows up as unavailable.


Looking back at the QSYSOPR messages, I see TWO OVERLAPPING STRTCPs, 
initiated within seconds of each other. That doesn't make any sense to 
me. And yet I see it happening every day this week.


So far, nothing is making any sense. TCP can't be in *that bad* of a 
shape, since I'm able to get terminal sessions via TN5250. And WRKTCPSTS 
shows 59 servers waiting for connections, and 61 established connections.


--
JHHL

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

Re: Tomcat 8.5.73 not coming up on customer box. "Bind failed."

2022-04-15 Thread James H. H. Lampert


On 4/15/22 9:39 AM, Jack Woehr wrote:

Not sure about the particular pathology in this instance, but it's the Java
runtime itself telling you something already has hold of the socket, and
it's not lying.


But it could be deluded into *thinking* something already has hold of 
the socket.


WRKTCPSTS shows *nothing* on 8005, 8009, 443, or 8443. I've tried 
changing 8005 to 8009. No joy. I then tried changing 443 to 8443. No joy.


I'm seriously considering having them do an ENDTCP followed by a STRTCP 
(although I haven't a clue how that can even be done on a box that 
presumably isn't old enough to have Twinax). And if that doesn't work, 
re-IPL the system.


--
JHHL

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

Re: Tomcat 8.5.73 not coming up on customer box. "Bind failed."

2022-04-15 Thread James H. H. Lampert


On 4/15/22 9:24 AM, James H. H. Lampert wrote:
This morning, I arrived at work to find that a customer was complaining 
about their Tomcat server (running on an IBM Midrange box).


It had locked up last night, while being shut down, and now, if you try 
to start it, it fails . . . 


I tried changing the port number from 8005 to 8009 (not in use for its 
usual purpose), since it appears to be specifically failing when trying 
to open 8005.


And it behaves exactly the same: it throws the same error, only this 
time on 8009.


This makes no sense.

--
JHHL

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

Tomcat 8.5.73 not coming up on customer box. "Bind failed."

2022-04-15 Thread James H. H. Lampert

This morning, I arrived at work to find that a customer was complaining 
about their Tomcat server (running on an IBM Midrange box).


It had locked up last night, while being shut down, and now, if you try 
to start it, it fails with

15-Apr-2022 10:35:34.867 SEVERE [main] 
org.apache.catalina.core.StandardServer.await StandardServer.await: 
create[localhost:8005]:
  java.net.BindException: The socket name is not available on this system. (Bind failed)   
  at java.net.PlainSocketImpl.socketBind(Native Method)   
  at java.net.AbstractPlainSocketImpl.bind(AbstractPlainSocketImpl.java:417)  
  at java.net.ServerSocket.bind(ServerSocket.java:444)
  at java.net.ServerSocket.(ServerSocket.java:258)  
  at org.apache.catalina.core.StandardServer.await(StandardServer.java:414)   
  at org.apache.catalina.startup.Catalina.await(Catalina.java:776)
  at org.apache.catalina.startup.Catalina.start(Catalina.java:722)
  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)  
  at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:90)
  at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55)


Catalina.out shows "Starting ProtocolHandler ["https-jsse-nio-443"]," 
then "Server startup in 20227 ms," then it blows up as above.


According to the server.xml, the only ports it is listening on are 8005 
and 443. And according to a WRKTCPSTS *CNN (the AS/400 equivalent of a 
"super netstat"), there is nothing currently grabbing hold of either of 
those two ports.


Any insights as to what could be happening?

--
James H. H. Lampert
Touchtone Corporation

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

Re: [OT] Tomcat listener not coming up - no stuck threads

2016-12-29 Thread John D. Ament

So I wanted to make sure I didn't lose track of this.  Did you want me to
revise what I put out there, or were you going to bring in your changes?

On Thu, Dec 15, 2016 at 5:06 PM Christopher Schultz <
ch...@christopherschultz.net> wrote:

> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> John,
>
> On 12/15/16 5:03 PM, John D. Ament wrote:
> > On Thu, Dec 15, 2016 at 4:06 PM Christopher Schultz <
> > ch...@christopherschultz.net> wrote:
> >
> > Mark,
> >
> > On 12/15/16 2:44 PM, Mark Thomas wrote:
>  On 15/12/2016 19:35, Christopher Schultz wrote:
> > John,
> >
> > On 12/14/16 10:01 PM, John D. Ament wrote:
> >> I was feeling ambitious so I gave this a shot.  Here's
> >> what I changed:
> >> https://github.com/johnament/tomcat85/commit/a0281b2d4e0fea7cb0f7
> a9d 
> >
> >>
> 3c
> >  c>
> >
> >>
> >
> >
> d1e750b48498ff2
> 
>  That was pretty much what I was thinking.
> >
> >
> >> If you want it, let me know.  I can provide a patch.  I'm not
> >> sure what tests to add, other than verify no extra threads were
> >> created.  I need to setup a bugzilla account too.
> >
> >
> >
> 
> > My
> >
> > tack was going to be to create an ExecutorService that
> > didn't dispatch. That way, less code has to change.
> 
>  Seems like more work. And doesn't solve the original problem
>  of the main thread holding a lock.
> >
> > No, it won't hold a lock. The (Abstract)ExecutorService just
> > dispatches to the execute(Runnable job) method which can simply
> > be:
> >
> > job.run()
> >
> > In that case, only one thread is ever involved: the thread that
> > submitted the job.
> >
> >
> >> The problem is that tomcat is expecting a ThreadPoolExecutor.  It
> >> may make sense to wrap it in a delegate that just handles the
> >> calls you need, since you're only calling one method on the
> >> executor.  That would simplify this logic as well.
>
> That was exactly what I was going to do: create a class that would do
> double-duty. So rather than if/else blocks behaving differently for
> the case where 1 thread is being used rather than >1, the
> ExecutorService (ThreadPoolExecutor) would handle the difference. So
> it would be a one-line change to the ContainerBase class.
>
> - -chris
> -BEGIN PGP SIGNATURE-
> Comment: GPGTools - http://gpgtools.org
> Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
>
> iQIcBAEBCAAGBQJYUxPwAAoJEBzwKT+lPKRYmlwP/A/3F64wo3nJ46if8Ldm72hG
> 1zCUHD+ticxSX/wnjxjjItpy24jLw74d7ub/zuEGdXbcz0FZkL7HkX7uBqsoq/5K
> SR3fS4Vukz7h4aohDrkGFqMYcI48xZOBj2qPP26PNxKgBD4JbGGA/5kP2g1ItVbC
> EWhKRhHUJbP+sPqbyw6EGgxuGFczen/nXXhiTgDY5J5heG/4UoAOzCMJSbWzmywG
> lpPsa3UPvrErf43WE5AH8TijwxSOOSMCQDgVSDWgo5obqPRUzYE69f1h4pap7j5M
> HJlJZyaR+/5H3epfgyim1D4G6+LudvbS8chLIl0Dq9cPcFfbUny118ZSd9zs1n2D
> Np0q03wL4fTSfZTe95q8OWTdmGdwpg++GIoL8hsDg6wzkkPnWOX0mC3qc4TZ5Z8P
> cr+jW5VW12INwKyJROqe3KfX0IJQHS+MfddO+VDaItumibAeDeNEY+TTRsOWSq7k
> MSFH8Uic/S7EoWCTrGILTVgiZ5swAZIgIYSThSEukE3smltdnjZoR9juqwqz8ZgC
> ivIhrHx0lyHr36kbtebCgC/G9IRmv1oO5zNSUglCOmB4fsssxX84CUZXrcx1jxA2
> rdxgImaDw1igiLyhA++RUEL33t38wFzzqk0yfuNSZIa3jX7Obs89LY+wS6Oi6lMI
> bmjL4dBBuzbKbDgnTn26
> =JFw5
> -END PGP SIGNATURE-
>
> -
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: users-h...@tomcat.apache.org
>
>

Re: [OT] Tomcat listener not coming up - no stuck threads

2016-12-15 Thread Christopher Schultz

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

John,

On 12/15/16 5:03 PM, John D. Ament wrote:
> On Thu, Dec 15, 2016 at 4:06 PM Christopher Schultz < 
> ch...@christopherschultz.net> wrote:
> 
> Mark,
> 
> On 12/15/16 2:44 PM, Mark Thomas wrote:
 On 15/12/2016 19:35, Christopher Schultz wrote:
> John,
> 
> On 12/14/16 10:01 PM, John D. Ament wrote:
>> I was feeling ambitious so I gave this a shot.  Here's
>> what I changed: 
>> https://github.com/johnament/tomcat85/commit/a0281b2d4e0fea7cb0f7
a9d
>
>> 
3c
> 
>
>>
>
> 
d1e750b48498ff2
 
 That was pretty much what I was thinking.
> 
> 
>> If you want it, let me know.  I can provide a patch.  I'm not
>> sure what tests to add, other than verify no extra threads were
>> created.  I need to setup a bugzilla account too.
> 
> 
> 
 
> My
> 
> tack was going to be to create an ExecutorService that
> didn't dispatch. That way, less code has to change.
 
 Seems like more work. And doesn't solve the original problem
 of the main thread holding a lock.
> 
> No, it won't hold a lock. The (Abstract)ExecutorService just 
> dispatches to the execute(Runnable job) method which can simply
> be:
> 
> job.run()
> 
> In that case, only one thread is ever involved: the thread that 
> submitted the job.
> 
> 
>> The problem is that tomcat is expecting a ThreadPoolExecutor.  It
>> may make sense to wrap it in a delegate that just handles the
>> calls you need, since you're only calling one method on the
>> executor.  That would simplify this logic as well.

That was exactly what I was going to do: create a class that would do
double-duty. So rather than if/else blocks behaving differently for
the case where 1 thread is being used rather than >1, the
ExecutorService (ThreadPoolExecutor) would handle the difference. So
it would be a one-line change to the ContainerBase class.

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

iQIcBAEBCAAGBQJYUxPwAAoJEBzwKT+lPKRYmlwP/A/3F64wo3nJ46if8Ldm72hG
1zCUHD+ticxSX/wnjxjjItpy24jLw74d7ub/zuEGdXbcz0FZkL7HkX7uBqsoq/5K
SR3fS4Vukz7h4aohDrkGFqMYcI48xZOBj2qPP26PNxKgBD4JbGGA/5kP2g1ItVbC
EWhKRhHUJbP+sPqbyw6EGgxuGFczen/nXXhiTgDY5J5heG/4UoAOzCMJSbWzmywG
lpPsa3UPvrErf43WE5AH8TijwxSOOSMCQDgVSDWgo5obqPRUzYE69f1h4pap7j5M
HJlJZyaR+/5H3epfgyim1D4G6+LudvbS8chLIl0Dq9cPcFfbUny118ZSd9zs1n2D
Np0q03wL4fTSfZTe95q8OWTdmGdwpg++GIoL8hsDg6wzkkPnWOX0mC3qc4TZ5Z8P
cr+jW5VW12INwKyJROqe3KfX0IJQHS+MfddO+VDaItumibAeDeNEY+TTRsOWSq7k
MSFH8Uic/S7EoWCTrGILTVgiZ5swAZIgIYSThSEukE3smltdnjZoR9juqwqz8ZgC
ivIhrHx0lyHr36kbtebCgC/G9IRmv1oO5zNSUglCOmB4fsssxX84CUZXrcx1jxA2
rdxgImaDw1igiLyhA++RUEL33t38wFzzqk0yfuNSZIa3jX7Obs89LY+wS6Oi6lMI
bmjL4dBBuzbKbDgnTn26
=JFw5
-END PGP SIGNATURE-

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

Re: [OT] Tomcat listener not coming up - no stuck threads

2016-12-15 Thread John D. Ament

On Thu, Dec 15, 2016 at 4:06 PM Christopher Schultz <
ch...@christopherschultz.net> wrote:

> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Mark,
>
> On 12/15/16 2:44 PM, Mark Thomas wrote:
> > On 15/12/2016 19:35, Christopher Schultz wrote:
> >> John,
> >>
> >> On 12/14/16 10:01 PM, John D. Ament wrote:
> >>> I was feeling ambitious so I gave this a shot.  Here's what I
> >>> changed:
> >>> https://github.com/johnament/tomcat85/commit/a0281b2d4e0fea7cb0f7a9d
> 3c
> 
> >>
> >>>
> d1e750b48498ff2
> >
> > That was pretty much what I was thinking.
>

If you want it, let me know.  I can provide a patch.  I'm not sure what
tests to add, other than verify no extra threads were created.  I need to
setup a bugzilla account too.



> >
> >> My
> >>
> >> tack was going to be to create an ExecutorService that didn't
> >> dispatch. That way, less code has to change.
> >
> > Seems like more work. And doesn't solve the original problem of the
> > main thread holding a lock.
>
> No, it won't hold a lock. The (Abstract)ExecutorService just
> dispatches to the execute(Runnable job) method which can simply be:
>
>job.run()
>
> In that case, only one thread is ever involved: the thread that
> submitted the job.
>

The problem is that tomcat is expecting a ThreadPoolExecutor.  It may make
sense to wrap it in a delegate that just handles the calls you need, since
you're only calling one method on the executor.  That would simplify this
logic as well.


>
> >> The problem with that approach is that, technically, the thread
> >> count can change for a variety of reasons and it should behave
> >> correctly at the time the contexts are started/stopped.
> >>
> >> I'd be interested in some comments on changing the behavior of
> >> Tomcat based upon the documentation of startStopThreads. For a
> >> value of "1", it explicitly says that 1 thread will be used. I'd
> >> be surprised if Tomcat were not to use a single (separate) thread
> >> rather than the main thread.
> >>
> >> Thing about this use-case: you have an embedded scenario where
> >> you want to launch Tomcat and you expect the start() call to
> >> return fairly soon so you can continue doing whatever you wanted
> >> to do. But instead of using the "1 thread" to start all the
> >> contexts, it's using the current thread and blocking you.
> >
> > That isn't what happens. The main thread always blocks until all
> > the container start threads have completed.
>
> Oh, well, then my use-case seems moot. Or, at least, no
> currently-running code will expect that behavior.
>
> >> I'm wondering if we need to invent a new magic number for this.
> >> Unfortunately, 0 is already taken. Perhaps we could use a
> >> non-numeric value for this special case.
> >
> > I don't see a need for that.
>
> I could imagine a need for that behavior, but there's an easier way
> for client code to handle it: launch Tomcat.start() from a separate
> thread.
>
> - -chris
> -BEGIN PGP SIGNATURE-
> Comment: GPGTools - http://gpgtools.org
> Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
>
> iQIcBAEBCAAGBQJYUwXHAAoJEBzwKT+lPKRYYNwP/36ZY+6XsIU2GgsihjHxCIPe
> kixjLj6GZXtc8mhoBWRVg3D16dhG62PhCSt813JIKFZMQQMd/zjuYFV6qqkZlv4D
> 4k0+wxVGLC9oWZA0awuAfWOiAYeHDUEe6Rwr67oUrmpxNcanvv9uk0URxYWEZjzj
> YS5ogX/lxJ/EuYIxz2aOptQ8q6W/fARQTsAdiIL3KWy2kjrDvWH/8V46oQxUwdXJ
> ilqnMPvCkTwAyKqeCug4bsDr4V/Xk7gjdqttb0qlntfLYay1WmWx1mAnTCD77V/H
> 6iCSviICy7dFrif4dfTHJ8SS2a8WxXMPR+ng8daCCaZE4GcNqs7bp1z254626xSw
> f/Ob2JPlD8aAsjM6WwAhtdlsE/0DzwkKm0Ski3ejt/A2Uh8V5KfaECyNgg1dRoak
> czJxxegVyUotkUjx7nL8nqW3dwb2wFJjhUVb/KKiZrl6TC8ME0Ix8UvcCx+Ldaoe
> KDVyJjqDSvEECwHLkCUTMbdX0wCJ2qMoH3ULDXMIEHpot9tkDQEa8iUAC9oS7dP0
> zUmPY9syYwTBueRT0taSnpumrZ+iZkQIGPGEfX52kf90O9e8uGTFFSBMCoPpwI0M
> OfoH6A7g0I69tHiO05fFicj16Rf5BqoNQvKfn8CCzEJA41Uek9yTETGdlHUcbIZy
> NwWg49KyTN9G3o851TmW
> =QY5c
> -END PGP SIGNATURE-
>
> -
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: users-h...@tomcat.apache.org
>
>

Re: [OT] Tomcat listener not coming up - no stuck threads

2016-12-15 Thread Christopher Schultz

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Mark,

On 12/15/16 2:44 PM, Mark Thomas wrote:
> On 15/12/2016 19:35, Christopher Schultz wrote:
>> John,
>> 
>> On 12/14/16 10:01 PM, John D. Ament wrote:
>>> I was feeling ambitious so I gave this a shot.  Here's what I 
>>> changed: 
>>> https://github.com/johnament/tomcat85/commit/a0281b2d4e0fea7cb0f7a9d
3c
>>
>>> 
d1e750b48498ff2
> 
> That was pretty much what I was thinking.
> 
>> My
>> 
>> tack was going to be to create an ExecutorService that didn't 
>> dispatch. That way, less code has to change.
> 
> Seems like more work. And doesn't solve the original problem of the
> main thread holding a lock.

No, it won't hold a lock. The (Abstract)ExecutorService just
dispatches to the execute(Runnable job) method which can simply be:

   job.run()

In that case, only one thread is ever involved: the thread that
submitted the job.

>> The problem with that approach is that, technically, the thread
>> count can change for a variety of reasons and it should behave
>> correctly at the time the contexts are started/stopped.
>> 
>> I'd be interested in some comments on changing the behavior of
>> Tomcat based upon the documentation of startStopThreads. For a
>> value of "1", it explicitly says that 1 thread will be used. I'd
>> be surprised if Tomcat were not to use a single (separate) thread
>> rather than the main thread.
>> 
>> Thing about this use-case: you have an embedded scenario where
>> you want to launch Tomcat and you expect the start() call to
>> return fairly soon so you can continue doing whatever you wanted
>> to do. But instead of using the "1 thread" to start all the
>> contexts, it's using the current thread and blocking you.
> 
> That isn't what happens. The main thread always blocks until all
> the container start threads have completed.

Oh, well, then my use-case seems moot. Or, at least, no
currently-running code will expect that behavior.

>> I'm wondering if we need to invent a new magic number for this. 
>> Unfortunately, 0 is already taken. Perhaps we could use a
>> non-numeric value for this special case.
> 
> I don't see a need for that.

I could imagine a need for that behavior, but there's an easier way
for client code to handle it: launch Tomcat.start() from a separate
thread.

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

iQIcBAEBCAAGBQJYUwXHAAoJEBzwKT+lPKRYYNwP/36ZY+6XsIU2GgsihjHxCIPe
kixjLj6GZXtc8mhoBWRVg3D16dhG62PhCSt813JIKFZMQQMd/zjuYFV6qqkZlv4D
4k0+wxVGLC9oWZA0awuAfWOiAYeHDUEe6Rwr67oUrmpxNcanvv9uk0URxYWEZjzj
YS5ogX/lxJ/EuYIxz2aOptQ8q6W/fARQTsAdiIL3KWy2kjrDvWH/8V46oQxUwdXJ
ilqnMPvCkTwAyKqeCug4bsDr4V/Xk7gjdqttb0qlntfLYay1WmWx1mAnTCD77V/H
6iCSviICy7dFrif4dfTHJ8SS2a8WxXMPR+ng8daCCaZE4GcNqs7bp1z254626xSw
f/Ob2JPlD8aAsjM6WwAhtdlsE/0DzwkKm0Ski3ejt/A2Uh8V5KfaECyNgg1dRoak
czJxxegVyUotkUjx7nL8nqW3dwb2wFJjhUVb/KKiZrl6TC8ME0Ix8UvcCx+Ldaoe
KDVyJjqDSvEECwHLkCUTMbdX0wCJ2qMoH3ULDXMIEHpot9tkDQEa8iUAC9oS7dP0
zUmPY9syYwTBueRT0taSnpumrZ+iZkQIGPGEfX52kf90O9e8uGTFFSBMCoPpwI0M
OfoH6A7g0I69tHiO05fFicj16Rf5BqoNQvKfn8CCzEJA41Uek9yTETGdlHUcbIZy
NwWg49KyTN9G3o851TmW
=QY5c
-END PGP SIGNATURE-

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

Re: [OT] Tomcat listener not coming up - no stuck threads

2016-12-15 Thread Mark Thomas

On 15/12/2016 19:35, Christopher Schultz wrote:
> John,
> 
> On 12/14/16 10:01 PM, John D. Ament wrote:
>> I was feeling ambitious so I gave this a shot.  Here's what I
>> changed: 
>> https://github.com/johnament/tomcat85/commit/a0281b2d4e0fea7cb0f7a9d3c
> d1e750b48498ff2

That was pretty much what I was thinking.

> My
> 
> tack was going to be to create an ExecutorService that didn't
> dispatch. That way, less code has to change.

Seems like more work. And doesn't solve the original problem of the main
thread holding a lock.

> The problem with that approach is that, technically, the thread count
> can change for a variety of reasons and it should behave correctly at
> the time the contexts are started/stopped.
> 
> I'd be interested in some comments on changing the behavior of Tomcat
> based upon the documentation of startStopThreads. For a value of "1",
> it explicitly says that 1 thread will be used. I'd be surprised if
> Tomcat were not to use a single (separate) thread rather than the main
> thread.
> 
> Thing about this use-case: you have an embedded scenario where you
> want to launch Tomcat and you expect the start() call to return fairly
> soon so you can continue doing whatever you wanted to do. But instead
> of using the "1 thread" to start all the contexts, it's using the
> current thread and blocking you.

That isn't what happens. The main thread always blocks until all the
container start threads have completed.

> I'm wondering if we need to invent a new magic number for this.
> Unfortunately, 0 is already taken. Perhaps we could use a non-numeric
> value for this special case.

I don't see a need for that.

Mark

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

Re: [OT] Tomcat listener not coming up - no stuck threads

2016-12-15 Thread Christopher Schultz

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

John,

On 12/14/16 10:01 PM, John D. Ament wrote:
> I was feeling ambitious so I gave this a shot.  Here's what I
> changed: 
> https://github.com/johnament/tomcat85/commit/a0281b2d4e0fea7cb0f7a9d3c
d1e750b48498ff2

My
> 
tack was going to be to create an ExecutorService that didn't
dispatch. That way, less code has to change.

The problem with that approach is that, technically, the thread count
can change for a variety of reasons and it should behave correctly at
the time the contexts are started/stopped.

I'd be interested in some comments on changing the behavior of Tomcat
based upon the documentation of startStopThreads. For a value of "1",
it explicitly says that 1 thread will be used. I'd be surprised if
Tomcat were not to use a single (separate) thread rather than the main
thread.

Thing about this use-case: you have an embedded scenario where you
want to launch Tomcat and you expect the start() call to return fairly
soon so you can continue doing whatever you wanted to do. But instead
of using the "1 thread" to start all the contexts, it's using the
current thread and blocking you.

I'm wondering if we need to invent a new magic number for this.
Unfortunately, 0 is already taken. Perhaps we could use a non-numeric
value for this special case.

> I get some failed tests, but generallys eems good (I broke it
> earlier, and lots of things failed).
> 
> [concat] Testsuites with failed tests: [concat] 
> TEST-org.apache.catalina.session.TestStandardSessionIntegration.NIO.tx
t
>
> 
[concat]
> TEST-org.apache.catalina.session.TestStandardSessionIntegration.NIO2.t
xt
>
> 
[concat]
> TEST-org.apache.catalina.startup.TestHostConfigAutomaticDeployment.NIO
.txt
>
> 
[concat]
> TEST-org.apache.catalina.startup.TestHostConfigAutomaticDeployment.NIO
2.txt
>
> 
[concat]
> TEST-org.apache.catalina.tribes.group.TestGroupChannelMemberArrival.NI
O.txt
>
> 
[concat]
> TEST-org.apache.catalina.tribes.group.TestGroupChannelMemberArrival.NI
O2.txt
>
> 
[concat]
> TEST-org.apache.catalina.tribes.group.TestGroupChannelStartStop.NIO.tx
t
>
> 
[concat]
> TEST-org.apache.catalina.tribes.group.TestGroupChannelStartStop.NIO2.t
xt
>
> 
[concat]
> TEST-org.apache.catalina.tribes.group.interceptors.TestOrderIntercepto
r.NIO.txt
>
> 
[concat]
> TEST-org.apache.catalina.tribes.group.interceptors.TestOrderIntercepto
r.NIO2.txt
>
> 
[concat]
> TEST-org.apache.catalina.tribes.group.interceptors.TestTcpFailureDetec
tor.NIO.txt
>
> 
[concat]
> TEST-org.apache.catalina.tribes.group.interceptors.TestTcpFailureDetec
tor.NIO2.txt
>
> 
[concat]
> TEST-org.apache.tomcat.util.net.openssl.ciphers.TestCipher.NIO.txt 
> [concat] 
> TEST-org.apache.tomcat.util.net.openssl.ciphers.TestCipher.NIO2.txt
>
> 
[concat]
> TEST-org.apache.tomcat.util.net.openssl.ciphers.TestOpenSSLCipherConfi
gurationParser.NIO.txt
>
> 
[concat]
> TEST-org.apache.tomcat.util.net.openssl.ciphers.TestOpenSSLCipherConfi
gurationParser.NIO2.txt

These
> 
tests are very sensitive to environment. They always fail for me :)

> I'm wondering, can I publish local maven artifacts using the ant
> build?

You can always copy JARs from place to place. That's the extent of my
knowledge of Maven... really at all.

> Would be good to see if this fixes or changes my behavior.

You can take the catalina.jar from the output/build/lib directory and
overwrite the one in your test harness. That should work.

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

iQIcBAEBCAAGBQJYUvCCAAoJEBzwKT+lPKRYaBsQAMYXGyxbek5K1h5cGSlH8uCh
Lqj/c0yLEbCeFaLcqqUGw9zuDMs7VyfmARFFfYz/gezfs/bHOMFFlznbH4j3iTv9
K2JxsdvNzSbng/Pc/AjhnjKZz7bXM8Abg/hh0icRs8fUY16mZFNrdC3XGT9Mdcfj
clhbTlQPT582+EEVaOwwjEdZLQEk5iKuPleR9yzJSWqW9At/R3Nu8kA6ZuDP2o/v
tf3hir9nafWfFTrmHJatHrQUfQ+R+QBpOgHjVR+yStoHkGl6NACCy5WQqwy8FQ1f
+FgKq5qVE4aeSNXJ+l0wqqnwCNHZvXrqPLMcBbfqY7DWC5uOoSVtFQI/k9S8AE7v
YRq52G1ALzActhgCPQh4xmbnSkxsvRisl6q4NHTztNGMW1OgxYBUajr8gtKSAZ57
Iu4LvxATkc/xkr/Fs/qgMkNO+maIrxtGBm+RXrxm1pNmvNMz3xZfSUcHc6Jqii4e
2Tbur27Quz0qU6ZVurNiSPRSpZwWYhJVtZNeDsC8UB17gabppMzOOtyKY3n6bYrr
fpp4oW/91FLNAPpclUTmwBe0tZVDTnTvTfMZAUXAuXIYpgzijdAYh38xC17iqIYl
7VJiSMZVe1ajCyS8SmfCvVvi2Rvky1b8gy52fZ313auq7QzTv6NMGBOYwcV6Mzxh
pluxK0iMaMeC+rn1warX
=Ov3Q
-END PGP SIGNATURE-

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

Re: [OT] Tomcat listener not coming up - no stuck threads

2016-12-14 Thread John D. Ament

I was feeling ambitious so I gave this a shot.  Here's what I changed:
https://github.com/johnament/tomcat85/commit/a0281b2d4e0fea7cb0f7a9d3cd1e750b48498ff2
.
I get some failed tests, but generallys eems good (I broke it earlier, and
lots of things failed).

   [concat] Testsuites with failed tests:
   [concat]
TEST-org.apache.catalina.session.TestStandardSessionIntegration.NIO.txt
   [concat]
TEST-org.apache.catalina.session.TestStandardSessionIntegration.NIO2.txt
   [concat]
TEST-org.apache.catalina.startup.TestHostConfigAutomaticDeployment.NIO.txt
   [concat]
TEST-org.apache.catalina.startup.TestHostConfigAutomaticDeployment.NIO2.txt
   [concat]
TEST-org.apache.catalina.tribes.group.TestGroupChannelMemberArrival.NIO.txt
   [concat]
TEST-org.apache.catalina.tribes.group.TestGroupChannelMemberArrival.NIO2.txt
   [concat]
TEST-org.apache.catalina.tribes.group.TestGroupChannelStartStop.NIO.txt
   [concat]
TEST-org.apache.catalina.tribes.group.TestGroupChannelStartStop.NIO2.txt
   [concat]
TEST-org.apache.catalina.tribes.group.interceptors.TestOrderInterceptor.NIO.txt
   [concat]
TEST-org.apache.catalina.tribes.group.interceptors.TestOrderInterceptor.NIO2.txt
   [concat]
TEST-org.apache.catalina.tribes.group.interceptors.TestTcpFailureDetector.NIO.txt
   [concat]
TEST-org.apache.catalina.tribes.group.interceptors.TestTcpFailureDetector.NIO2.txt
   [concat]
TEST-org.apache.tomcat.util.net.openssl.ciphers.TestCipher.NIO.txt
   [concat]
TEST-org.apache.tomcat.util.net.openssl.ciphers.TestCipher.NIO2.txt
   [concat]
TEST-org.apache.tomcat.util.net.openssl.ciphers.TestOpenSSLCipherConfigurationParser.NIO.txt
   [concat]
TEST-org.apache.tomcat.util.net.openssl.ciphers.TestOpenSSLCipherConfigurationParser.NIO2.txt


I'm wondering, can I publish local maven artifacts using the ant build?
Would be good to see if this fixes or changes my behavior.

John

On Wed, Dec 14, 2016 at 12:22 PM Mark Thomas  wrote:

> On 14/12/2016 16:23, Christopher Schultz wrote:
> > Mark,
> >
> > On 12/8/16 4:19 AM, Mark Thomas wrote:
> >> On 07/12/2016 15:21, Christopher Schultz wrote:
> >>>
> >>> Hmm... there is the "startStopThreads" setting on the Engine,
> >>> but unfortunately there is not (currently available) setting that
> >>> says "don't use multiple threads at all". It looks like Tomcat is
> >>> always going to use at least one (separate) thread to launch the
> >>> various Hosts (and webapps).
> >
> >> It wouldn't be too hard to change that to not use an executor if
> >> the default of startStopThreads="1" was being used.
> >
> > +1 to running start on the main thread if startStopThreads="1".
> >
> > Where would I look to start working on a proposed patch? The Tomcat
> > Lifecycle isn't my strong suit.
>
> ContainerBase. Look for uses of startStopThreads.#
>
> >> However...
> >
> > Even if this doesn't solve John's problem, I think it's worth doing.
> >
> > Comments?
>
> No objections. I'd thought about it previously but it wasn't an itch I
> felt the urge to scratch.
>
> Mark
>
> -
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: users-h...@tomcat.apache.org
>
>

Re: [OT] Tomcat listener not coming up - no stuck threads

2016-12-14 Thread Mark Thomas

On 14/12/2016 16:23, Christopher Schultz wrote:
> Mark,
> 
> On 12/8/16 4:19 AM, Mark Thomas wrote:
>> On 07/12/2016 15:21, Christopher Schultz wrote:
>>>
>>> Hmm... there is the "startStopThreads" setting on the Engine,
>>> but unfortunately there is not (currently available) setting that
>>> says "don't use multiple threads at all". It looks like Tomcat is
>>> always going to use at least one (separate) thread to launch the
>>> various Hosts (and webapps).
> 
>> It wouldn't be too hard to change that to not use an executor if
>> the default of startStopThreads="1" was being used.
> 
> +1 to running start on the main thread if startStopThreads="1".
> 
> Where would I look to start working on a proposed patch? The Tomcat
> Lifecycle isn't my strong suit.

ContainerBase. Look for uses of startStopThreads.#

>> However...
> 
> Even if this doesn't solve John's problem, I think it's worth doing.
> 
> Comments?

No objections. I'd thought about it previously but it wasn't an itch I
felt the urge to scratch.

Mark

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

Re: [OT] Tomcat listener not coming up - no stuck threads

2016-12-14 Thread John D. Ament

On Wed, Dec 14, 2016 at 11:23 AM Christopher Schultz <
ch...@christopherschultz.net> wrote:

> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Mark,
>
> On 12/8/16 4:19 AM, Mark Thomas wrote:
> > On 07/12/2016 15:21, Christopher Schultz wrote:
> >>
> >> Hmm... there is the "startStopThreads" setting on the Engine,
> >> but unfortunately there is not (currently available) setting that
> >> says "don't use multiple threads at all". It looks like Tomcat is
> >> always going to use at least one (separate) thread to launch the
> >> various Hosts (and webapps).
> >
> > It wouldn't be too hard to change that to not use an executor if
> > the default of startStopThreads="1" was being used.
>
> +1 to running start on the main thread if startStopThreads="1".
>
> Where would I look to start working on a proposed patch? The Tomcat
> Lifecycle isn't my strong suit.
>
> > However...
>
> Even if this doesn't solve John's problem, I think it's worth doing.
>

Having an option to startStop on the main thread would fix my issue.
However would that be when startStopThreads = 1 or some other parameter (to
not break compatibility) ?

John


>
> Comments?
>
> - -chris
> -BEGIN PGP SIGNATURE-
> Comment: GPGTools - http://gpgtools.org
> Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
>
> iQIcBAEBCAAGBQJYUXIcAAoJEBzwKT+lPKRYuWsQAMhrAt3mFLGio4u16ZABWLyG
> vPwlNRH24l9AnXu2yJ2FALS0ydIB8RTKW7BlwsdrlVAINQ8I0tWXFY4cn7jnMox3
> GLyg0ABmSIYqO/Qxqd4YIILBWWycNmvWn8BBgfLvqJaVDO/VB8vrsGClBnVbuqh8
> UetcFoCuIjXWpSQFBI7NhPouE4C145eMrmSmbz0Go7jtBPEfib5dgF26QepfX56M
> +ds8CDJc9OLusGSCvNgzYu7HXo3fBAFr52LoykQn6IqJbfv0PduiX8ySbLceBXpa
> VGlD9Fb9P/08wgANgBs7cbgkmxaEU/PnpXB/B5Mx8QbBV08Ajch3Rxedc2ikqMgi
> GP0n8xYzk0GaeEl8VSEwIQCbkib8kz4cR8s+nsiDwcq1WkFrIUqqr0UapN3dyRAS
> ySlfFyYN+Wbhe37lRjjQrMDsVcS8mX7t9ELKYRQ3difkmKeeme6D60tyNX/gEUPp
> NqHFeOknpgNw/Orj3KM6v1b9BAeRstFelx+kAffrc0G9Gz9GG8+BY7ThBvdfrSZO
> wp/ufXhmyVta57qVmmpwR7ua3b5npbCvgkIos6GTu2dKRMqRj2pBPBA3f9HyT82S
> 1IsYM72RhCTimrmskIb2/G6okRNa1aft5f3iypwsG6J1+ZLxgYROZVWfTbdA9WRS
> 2/n3/Gtg2yi9GhED0luy
> =FbNM
> -END PGP SIGNATURE-
>
> -
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: users-h...@tomcat.apache.org
>
>

Re: [OT] Tomcat listener not coming up - no stuck threads

2016-12-14 Thread Christopher Schultz

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Mark,

On 12/8/16 4:19 AM, Mark Thomas wrote:
> On 07/12/2016 15:21, Christopher Schultz wrote:
>> 
>> Hmm... there is the "startStopThreads" setting on the Engine,
>> but unfortunately there is not (currently available) setting that
>> says "don't use multiple threads at all". It looks like Tomcat is
>> always going to use at least one (separate) thread to launch the
>> various Hosts (and webapps).
> 
> It wouldn't be too hard to change that to not use an executor if
> the default of startStopThreads="1" was being used.

+1 to running start on the main thread if startStopThreads="1".

Where would I look to start working on a proposed patch? The Tomcat
Lifecycle isn't my strong suit.

> However...

Even if this doesn't solve John's problem, I think it's worth doing.

Comments?

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

iQIcBAEBCAAGBQJYUXIcAAoJEBzwKT+lPKRYuWsQAMhrAt3mFLGio4u16ZABWLyG
vPwlNRH24l9AnXu2yJ2FALS0ydIB8RTKW7BlwsdrlVAINQ8I0tWXFY4cn7jnMox3
GLyg0ABmSIYqO/Qxqd4YIILBWWycNmvWn8BBgfLvqJaVDO/VB8vrsGClBnVbuqh8
UetcFoCuIjXWpSQFBI7NhPouE4C145eMrmSmbz0Go7jtBPEfib5dgF26QepfX56M
+ds8CDJc9OLusGSCvNgzYu7HXo3fBAFr52LoykQn6IqJbfv0PduiX8ySbLceBXpa
VGlD9Fb9P/08wgANgBs7cbgkmxaEU/PnpXB/B5Mx8QbBV08Ajch3Rxedc2ikqMgi
GP0n8xYzk0GaeEl8VSEwIQCbkib8kz4cR8s+nsiDwcq1WkFrIUqqr0UapN3dyRAS
ySlfFyYN+Wbhe37lRjjQrMDsVcS8mX7t9ELKYRQ3difkmKeeme6D60tyNX/gEUPp
NqHFeOknpgNw/Orj3KM6v1b9BAeRstFelx+kAffrc0G9Gz9GG8+BY7ThBvdfrSZO
wp/ufXhmyVta57qVmmpwR7ua3b5npbCvgkIos6GTu2dKRMqRj2pBPBA3f9HyT82S
1IsYM72RhCTimrmskIb2/G6okRNa1aft5f3iypwsG6J1+ZLxgYROZVWfTbdA9WRS
2/n3/Gtg2yi9GhED0luy
=FbNM
-END PGP SIGNATURE-

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

Re: Tomcat listener not coming up - no stuck threads

2016-12-13 Thread John D. Ament

On Thu, Dec 8, 2016 at 4:20 AM Mark Thomas  wrote:

> On 07/12/2016 15:21, Christopher Schultz wrote:
> > John,
> >
> > On 12/7/16 7:19 AM, John D. Ament wrote:
> >> On Wed, Dec 7, 2016 at 3:58 AM Mark Thomas 
> >> wrote:
> >
> >>> On 06/12/2016 02:59, John D. Ament wrote:
> >>>
> >>> 
> >>>
>  So I was able to identify my issue.  It's not specifically a
>  tomcat problem, but tomcat's bootstrapping makes it unique.
> 
>  one of the issues I've observed is that Tomcat's use of
>  multithreading causes some thread deadlocking with some
>  synchronized blocks.  I was wondering if there's a way to turn
>  that off?  Make tomcat's bootstrap happen in the same thread as
>  the original invocation?
> >>>
> >>> What exactly do you mean by Tomcat's bootstrapping? Can you give
> >>> an example of concurrent execution that is causing issues?
> >>>
> >
> >> I instantiate the Tomcat object and invoke start() on the "main"
> >> thread. The invocation of ServletContextListeners happens on a
> >> "localhost-startStop-1" thread.  I would like to have that
> >> invocation happen on the main thread instead.
> >
> > Hmm... there is the "startStopThreads" setting on the Engine, but
> > unfortunately there is not (currently available) setting that says
> > "don't use multiple threads at all". It looks like Tomcat is always
> > going to use at least one (separate) thread to launch the various
> > Hosts (and webapps).
>
> It wouldn't be too hard to change that to not use an executor if the
> default of startStopThreads="1" was being used. However...
>
> >> Its nothing within tomcat that is deadlocking, but under the covers
> >> weld has a synchronized block, its inside that synchronized block
> >> where Tomcat is instantiated.  There's a later point where Weld
> >> tries getting a lock again.  In that case, when its single threaded
> >> (in other containers) it passes since it has a lock, but in this
> >> case it can't get that lock.
>
> The Weld documentation suggests that it is initialized per web
> application with a ServletContainerInitializer. This would be fine with
> Tomcat's current use of an Executor for container start/stop.
>
> I don't, therefore, understand how Weld is instantiating Tomcat. Can you
> expand on this?
>
>
There's two ways to make this work.  The documentation you're reading is
referring to standard servlet containers.  E.g. someone's installed tomcat
somewhere and has a WAR with weld-servlet in it.

In my case, I'm using weld-se to bootstrap a JVM, wrote a CDI extension
that bootstraps Tomcat embedded, pointing to the embedded weld instance.
Its not designed for multiple apps, but a single service in that JVM.
Since I'm using an extension, weld isn't 100% started yet.  Since it hasn't
started yet, some of the bootstrap logic is trying to fire an event.  That
event shouldn't be fired quite yet, and its not able to coordinate that
between the threads, hence where I got this problem.

I ended up working around the issue by delaying Tomcat's bootstrap even
further, ensuring that the container is 100% up before trying to launch
tomcat.



> Mark
>
> > Is there any way for you to remove the required monitor on your own
> > code? Or is Weld so intricately-involved in the whole process that
> > unwinding it isn't possible?
> >
> > -chris
>
> -
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: users-h...@tomcat.apache.org
>
>

Re: Tomcat listener not coming up - no stuck threads

2016-12-08 Thread Mark Thomas

On 07/12/2016 15:21, Christopher Schultz wrote:
> John,
> 
> On 12/7/16 7:19 AM, John D. Ament wrote:
>> On Wed, Dec 7, 2016 at 3:58 AM Mark Thomas 
>> wrote:
> 
>>> On 06/12/2016 02:59, John D. Ament wrote:
>>>
>>> 
>>>
 So I was able to identify my issue.  It's not specifically a
 tomcat problem, but tomcat's bootstrapping makes it unique.

 one of the issues I've observed is that Tomcat's use of
 multithreading causes some thread deadlocking with some
 synchronized blocks.  I was wondering if there's a way to turn
 that off?  Make tomcat's bootstrap happen in the same thread as
 the original invocation?
>>>
>>> What exactly do you mean by Tomcat's bootstrapping? Can you give
>>> an example of concurrent execution that is causing issues?
>>>
> 
>> I instantiate the Tomcat object and invoke start() on the "main"
>> thread. The invocation of ServletContextListeners happens on a 
>> "localhost-startStop-1" thread.  I would like to have that
>> invocation happen on the main thread instead.
> 
> Hmm... there is the "startStopThreads" setting on the Engine, but
> unfortunately there is not (currently available) setting that says
> "don't use multiple threads at all". It looks like Tomcat is always
> going to use at least one (separate) thread to launch the various
> Hosts (and webapps).

It wouldn't be too hard to change that to not use an executor if the
default of startStopThreads="1" was being used. However...

>> Its nothing within tomcat that is deadlocking, but under the covers
>> weld has a synchronized block, its inside that synchronized block
>> where Tomcat is instantiated.  There's a later point where Weld
>> tries getting a lock again.  In that case, when its single threaded
>> (in other containers) it passes since it has a lock, but in this
>> case it can't get that lock.

The Weld documentation suggests that it is initialized per web
application with a ServletContainerInitializer. This would be fine with
Tomcat's current use of an Executor for container start/stop.

I don't, therefore, understand how Weld is instantiating Tomcat. Can you
expand on this?

Mark

> Is there any way for you to remove the required monitor on your own
> code? Or is Weld so intricately-involved in the whole process that
> unwinding it isn't possible?
> 
> -chris

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

Re: Tomcat listener not coming up - no stuck threads

2016-12-07 Thread Christopher Schultz

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

John,

On 12/7/16 7:19 AM, John D. Ament wrote:
> On Wed, Dec 7, 2016 at 3:58 AM Mark Thomas 
> wrote:
> 
>> On 06/12/2016 02:59, John D. Ament wrote:
>> 
>> 
>> 
>>> So I was able to identify my issue.  It's not specifically a
>>> tomcat problem, but tomcat's bootstrapping makes it unique.
>>> 
>>> one of the issues I've observed is that Tomcat's use of
>>> multithreading causes some thread deadlocking with some
>>> synchronized blocks.  I was wondering if there's a way to turn
>>> that off?  Make tomcat's bootstrap happen in the same thread as
>>> the original invocation?
>> 
>> What exactly do you mean by Tomcat's bootstrapping? Can you give
>> an example of concurrent execution that is causing issues?
>> 
> 
> I instantiate the Tomcat object and invoke start() on the "main"
> thread. The invocation of ServletContextListeners happens on a 
> "localhost-startStop-1" thread.  I would like to have that
> invocation happen on the main thread instead.

Hmm... there is the "startStopThreads" setting on the Engine, but
unfortunately there is not (currently available) setting that says
"don't use multiple threads at all". It looks like Tomcat is always
going to use at least one (separate) thread to launch the various
Hosts (and webapps).

> Its nothing within tomcat that is deadlocking, but under the covers
> weld has a synchronized block, its inside that synchronized block
> where Tomcat is instantiated.  There's a later point where Weld
> tries getting a lock again.  In that case, when its single threaded
> (in other containers) it passes since it has a lock, but in this
> case it can't get that lock.

Is there any way for you to remove the required monitor on your own
code? Or is Weld so intricately-involved in the whole process that
unwinding it isn't possible?

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

iQIcBAEBCAAGBQJYSCkWAAoJEBzwKT+lPKRYIUcP/2lSnNrqoW4XXUKuFVLJXijl
w/+TiQz58pjo7KCpXzRC6ubBPIQNO5Hj5HbukXuglNJfaWbEnoIdf9zlSOElg13a
t+Pc4OFvdFYc0uzMf5E824AvXeLR5A4SAuMxzzg86DEdJZiAW4MwEoY/UduPN1b6
PQM74JS5iXNTGQjaNZQfonS26Gsrwi69fnC+evcJ/RDGZxUIq/NAZVU1zD0wjAAh
p0dzvRqkO5XjirCF8xyUgoUIHn1LdygZrOMkDby3XY23/nQVN+JxmlPDc/Lwl+nt
a2Ywkw0D5ATkHBzqZC8ksmkFVWIiGKMZacOBKci5sv+APdTzohpAUicleZ+bQB6l
tYkTwhmqkAn27B1Zj+ev7efAz+LbjyKzBGHLztD3r+lhkfBRJrotprEIA5MWXLiD
SLrBwXcJqSLkipoKDpCwrkBHrMnHTUi1M7NyLDXSgRw/ynJfoUnN/FjssNft7K09
RtxMktXqD3FBX74tIbEUmdU5OmEGAuSIiOrjKyYgH8vXmyqo44kIw9c8EapY1mVS
FQurOjEOXO+rk5TnWWOvT22pcH3sgfH486YaaiUJ0tW7DraQFOIqVq2jlb/tSwW7
Yai218JiEQJRR1ps+ZZyXqhsSVfTJ8CSnGDsWROJuMSO7roBJQXbutftAJjxHC0M
V7Mfo/Q2YhRhrL1fPcuW
=jiLD
-END PGP SIGNATURE-

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

Re: Tomcat listener not coming up - no stuck threads

2016-12-07 Thread John D. Ament

On Wed, Dec 7, 2016 at 3:58 AM Mark Thomas  wrote:

> On 06/12/2016 02:59, John D. Ament wrote:
>
> 
>
> > So I was able to identify my issue.  It's not specifically a tomcat
> > problem, but tomcat's bootstrapping makes it unique.
> >
> > one of the issues I've observed is that Tomcat's use of multithreading
> > causes some thread deadlocking with some synchronized blocks.  I was
> > wondering if there's a way to turn that off?  Make tomcat's bootstrap
> > happen in the same thread as the original invocation?
>
> What exactly do you mean by Tomcat's bootstrapping? Can you give an
> example of concurrent execution that is causing issues?
>

I instantiate the Tomcat object and invoke start() on the "main" thread.
The invocation of ServletContextListeners happens on a
"localhost-startStop-1" thread.  I would like to have that invocation
happen on the main thread instead.

Its nothing within tomcat that is deadlocking, but under the covers weld
has a synchronized block, its inside that synchronized block where Tomcat
is instantiated.  There's a later point where Weld tries getting a lock
again.  In that case, when its single threaded (in other containers) it
passes since it has a lock, but in this case it can't get that lock.

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

Re: Tomcat listener not coming up - no stuck threads

2016-12-07 Thread Mark Thomas

On 06/12/2016 02:59, John D. Ament wrote:



> So I was able to identify my issue.  It's not specifically a tomcat
> problem, but tomcat's bootstrapping makes it unique.
> 
> one of the issues I've observed is that Tomcat's use of multithreading
> causes some thread deadlocking with some synchronized blocks.  I was
> wondering if there's a way to turn that off?  Make tomcat's bootstrap
> happen in the same thread as the original invocation?

What exactly do you mean by Tomcat's bootstrapping? Can you give an
example of concurrent execution that is causing issues?

Mark


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

Re: Tomcat listener not coming up - no stuck threads

2016-12-05 Thread John D. Ament

On Sat, Dec 3, 2016 at 2:28 PM Mark Thomas  wrote:

> On 03/12/2016 17:39, John D. Ament wrote:
> > Sorry missed a response..
> >
> > On Sat, Dec 3, 2016 at 12:36 PM John D. Ament 
> > wrote:
> >
> >> On Wed, Nov 30, 2016 at 8:50 PM Christopher Schultz <
> >> ch...@christopherschultz.net> wrote:
> >>
> > John,
> >
> > On 11/26/16 7:29 PM, John D. Ament wrote:
>  Hi,
> 
>  Looking for some external input.  I've put together a simple
>  tomcat embedded instance designed to deploy an arbitrary set of
>  servlets, filters, etc.
> 
>  For some reason, when I run tests with Tomcat the server never
>  fully launches.  I can see the port in use, but connections to the
>  server are not answered by the instance.  When I debug the start
>  up, I see what appears to be a loop attempting to start services
>  that never returns, in LifecycleBase.
> >
> > So you see a busy-loop? What's the stack trace?
> >
> >
> >> I am probably seeing a busy-loop, however I  see no stack traces.
>
> Take a thread dump.
>
> Better, take 3 ~10s apart and compare.
>
> > Tomcat version?
> >
> >
> > 8.5.8 and a few older ones, so 8.0.30 and 8.5.3 as well (that I can
> recall
> > recently)
> >
> >
> >
>  Easiest way to reproduce it with this project is to clone
>  https://github.com/hammock-project/hammock/ and run a local build
>  (to get snapshots) and then run 'mvn clean install -Ptomcat-test'
>  from rest-resteasy (or spark or jersey).
> >
> > Er... sorry, I'm not going to do that, and it doesn't look like anyone
> > else is going to do that, either.
> >
> >
> > Its always worth a shot.
> >
> >
> >
>  I'm sure there's something simple I'm over looking.
> >
> > I browsed your github repo for about 15 seconds until I realized that
> > there are like 10k files and I'd never find the embedded driver
> > without asking. So, where is it?
> >
> > Can you compare your driver with any of the many Tomcat test cases
> > that launch an embedded server instance? Those test classes do exactly
> > what it sounds like you are trying to do.
> >
> >
> > Happily, can you point me to some of these test cases?
>
> Most of them under trunk/test
>
> This one has several variations:
>
> http://svn.apache.org/viewvc/tomcat/trunk/test/org/apache/catalina/connector/TestRequest.java?view=annotate
>
>
> > On a related note, documentation for tomcat embedded is scarce.  I
> usually
> > have to find it on non-apache channels.  What would be the best way to
> get
> > a document page started, maybe linked off of
> > http://tomcat.apache.org/tomcat-8.5-doc/index.html ?  What repo contains
> > your site?  I'd be happy to provide some patches from my own learnings.
>
> The docs are taken from the releases so you need to start here:
>
> http://svn.apache.org/viewvc/tomcat/trunk/webapps/docs/
>
>
So I was able to identify my issue.  It's not specifically a tomcat
problem, but tomcat's bootstrapping makes it unique.

one of the issues I've observed is that Tomcat's use of multithreading
causes some thread deadlocking with some synchronized blocks.  I was
wondering if there's a way to turn that off?  Make tomcat's bootstrap
happen in the same thread as the original invocation?


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

Re: Tomcat listener not coming up - no stuck threads

2016-12-03 Thread Mark Thomas

On 03/12/2016 17:39, John D. Ament wrote:
> Sorry missed a response..
> 
> On Sat, Dec 3, 2016 at 12:36 PM John D. Ament 
> wrote:
> 
>> On Wed, Nov 30, 2016 at 8:50 PM Christopher Schultz <
>> ch...@christopherschultz.net> wrote:
>>
> John,
> 
> On 11/26/16 7:29 PM, John D. Ament wrote:
 Hi,

 Looking for some external input.  I've put together a simple
 tomcat embedded instance designed to deploy an arbitrary set of
 servlets, filters, etc.

 For some reason, when I run tests with Tomcat the server never
 fully launches.  I can see the port in use, but connections to the
 server are not answered by the instance.  When I debug the start
 up, I see what appears to be a loop attempting to start services
 that never returns, in LifecycleBase.
> 
> So you see a busy-loop? What's the stack trace?
> 
> 
>> I am probably seeing a busy-loop, however I  see no stack traces.

Take a thread dump.

Better, take 3 ~10s apart and compare.

> Tomcat version?
> 
> 
> 8.5.8 and a few older ones, so 8.0.30 and 8.5.3 as well (that I can recall
> recently)
> 
> 
> 
 Easiest way to reproduce it with this project is to clone
 https://github.com/hammock-project/hammock/ and run a local build
 (to get snapshots) and then run 'mvn clean install -Ptomcat-test'
 from rest-resteasy (or spark or jersey).
> 
> Er... sorry, I'm not going to do that, and it doesn't look like anyone
> else is going to do that, either.
> 
> 
> Its always worth a shot.
> 
> 
> 
 I'm sure there's something simple I'm over looking.
> 
> I browsed your github repo for about 15 seconds until I realized that
> there are like 10k files and I'd never find the embedded driver
> without asking. So, where is it?
> 
> Can you compare your driver with any of the many Tomcat test cases
> that launch an embedded server instance? Those test classes do exactly
> what it sounds like you are trying to do.
> 
> 
> Happily, can you point me to some of these test cases?

Most of them under trunk/test

This one has several variations:
http://svn.apache.org/viewvc/tomcat/trunk/test/org/apache/catalina/connector/TestRequest.java?view=annotate


> On a related note, documentation for tomcat embedded is scarce.  I usually
> have to find it on non-apache channels.  What would be the best way to get
> a document page started, maybe linked off of
> http://tomcat.apache.org/tomcat-8.5-doc/index.html ?  What repo contains
> your site?  I'd be happy to provide some patches from my own learnings.

The docs are taken from the releases so you need to start here:

http://svn.apache.org/viewvc/tomcat/trunk/webapps/docs/


Mark

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

Re: Tomcat listener not coming up - no stuck threads

2016-12-03 Thread John D. Ament

Sorry missed a response..

On Sat, Dec 3, 2016 at 12:36 PM John D. Ament 
wrote:

> On Wed, Nov 30, 2016 at 8:50 PM Christopher Schultz <
> ch...@christopherschultz.net> wrote:
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> John,
>
> On 11/26/16 7:29 PM, John D. Ament wrote:
> > Hi,
> >
> > Looking for some external input.  I've put together a simple
> > tomcat embedded instance designed to deploy an arbitrary set of
> > servlets, filters, etc.
> >
> > For some reason, when I run tests with Tomcat the server never
> > fully launches.  I can see the port in use, but connections to the
> > server are not answered by the instance.  When I debug the start
> > up, I see what appears to be a loop attempting to start services
> > that never returns, in LifecycleBase.
>
> So you see a busy-loop? What's the stack trace?
>
>
I am probably seeing a busy-loop, however I  see no stack traces.


>
> Tomcat version?
>
>
> 8.5.8 and a few older ones, so 8.0.30 and 8.5.3 as well (that I can recall
> recently)
>
>
>
> > Easiest way to reproduce it with this project is to clone
> > https://github.com/hammock-project/hammock/ and run a local build
> > (to get snapshots) and then run 'mvn clean install -Ptomcat-test'
> > from rest-resteasy (or spark or jersey).
>
> Er... sorry, I'm not going to do that, and it doesn't look like anyone
> else is going to do that, either.
>
>
> Its always worth a shot.
>
>
>
> > I'm sure there's something simple I'm over looking.
>
> I browsed your github repo for about 15 seconds until I realized that
> there are like 10k files and I'd never find the embedded driver
> without asking. So, where is it?
>
> Can you compare your driver with any of the many Tomcat test cases
> that launch an embedded server instance? Those test classes do exactly
> what it sounds like you are trying to do.
>
>
> Happily, can you point me to some of these test cases?
>
> On a related note, documentation for tomcat embedded is scarce.  I usually
> have to find it on non-apache channels.  What would be the best way to get
> a document page started, maybe linked off of
> http://tomcat.apache.org/tomcat-8.5-doc/index.html ?  What repo contains
> your site?  I'd be happy to provide some patches from my own learnings.
>
> John
>
>
>
> - -chris
> -BEGIN PGP SIGNATURE-
> Comment: GPGTools - http://gpgtools.org
> Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
>
> iQIcBAEBCAAGBQJYP4HoAAoJEBzwKT+lPKRYOL8P/A5MQFuVMK0kbgsAzbYVWx81
> yLsIN5BgjMBwPCxr2S2KIg40/P8dq256+VFYkwLI/Y3kKi206IK0KQdRJCTQFEO9
> avTOSFTgY3IXCCEEijSh5HeM8ofO7AgFrjcUGYZ6PI5PmnkCx/bN+sCAmbIL4SuE
> hpOdA+A6zaV7TFFqjk2b71dVeijCTO3B/nUjkwOY7lP56jOX4bM2YDZoZj1o0SsV
> bLsR3hjIlyZX1q83XNGPNYicueMZv9EsoUuZkwN3N/9CwTIbn27ck9xWfs3zOsOr
> DLppYHdcKQNByd630cL0xhgYEHShJJcUcRddXWCeuEJOQ0urFYvfiOW2H5Py86lE
> jwlA8XqIhvK5nmG5fOjwInSN3v+Fhd5A9rAhZrPZpP4+J1tGK37FvVhPJa9xXFWz
> OYgtUxP2y1zwYyq+qs5jCYy628HE3Y++YSUSK+mWSN8Id/jDBqKUzZkZWuc7750B
> wRy/8rb6F9L47sAVkg4gj8XqQF/gQ3gbS3ujf+eYuIf4GS4h1pmI4xCmuoZo0LLt
> NJo2k4jAfwx2l48BpjO9Ry8MaSft2a9vE0uBQR/jwY5dvn5Y0mYX8Dr2JgdFYpeW
> Skxf9+U2U/IzB2qePvdmo5u5QUyl40fu6/ndMjoEk/AXycwfodr6/UG9fLOG7uDR
> kLSU4n1jBzwEf+9WMtFA
> =7GKl
> -END PGP SIGNATURE-
>
> -
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: users-h...@tomcat.apache.org
>
>

Re: Tomcat listener not coming up - no stuck threads

2016-12-03 Thread John D. Ament

On Wed, Nov 30, 2016 at 8:50 PM Christopher Schultz <
ch...@christopherschultz.net> wrote:

> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> John,
>
> On 11/26/16 7:29 PM, John D. Ament wrote:
> > Hi,
> >
> > Looking for some external input.  I've put together a simple
> > tomcat embedded instance designed to deploy an arbitrary set of
> > servlets, filters, etc.
> >
> > For some reason, when I run tests with Tomcat the server never
> > fully launches.  I can see the port in use, but connections to the
> > server are not answered by the instance.  When I debug the start
> > up, I see what appears to be a loop attempting to start services
> > that never returns, in LifecycleBase.
>
> So you see a busy-loop? What's the stack trace?
>
> Tomcat version?
>

8.5.8 and a few older ones, so 8.0.30 and 8.5.3 as well (that I can recall
recently)


>
> > Easiest way to reproduce it with this project is to clone
> > https://github.com/hammock-project/hammock/ and run a local build
> > (to get snapshots) and then run 'mvn clean install -Ptomcat-test'
> > from rest-resteasy (or spark or jersey).
>
> Er... sorry, I'm not going to do that, and it doesn't look like anyone
> else is going to do that, either.
>

Its always worth a shot.


>
> > I'm sure there's something simple I'm over looking.
>
> I browsed your github repo for about 15 seconds until I realized that
> there are like 10k files and I'd never find the embedded driver
> without asking. So, where is it?
>
> Can you compare your driver with any of the many Tomcat test cases
> that launch an embedded server instance? Those test classes do exactly
> what it sounds like you are trying to do.
>

Happily, can you point me to some of these test cases?

On a related note, documentation for tomcat embedded is scarce.  I usually
have to find it on non-apache channels.  What would be the best way to get
a document page started, maybe linked off of
http://tomcat.apache.org/tomcat-8.5-doc/index.html ?  What repo contains
your site?  I'd be happy to provide some patches from my own learnings.

John


>
> - -chris
> -BEGIN PGP SIGNATURE-
> Comment: GPGTools - http://gpgtools.org
> Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
>
> iQIcBAEBCAAGBQJYP4HoAAoJEBzwKT+lPKRYOL8P/A5MQFuVMK0kbgsAzbYVWx81
> yLsIN5BgjMBwPCxr2S2KIg40/P8dq256+VFYkwLI/Y3kKi206IK0KQdRJCTQFEO9
> avTOSFTgY3IXCCEEijSh5HeM8ofO7AgFrjcUGYZ6PI5PmnkCx/bN+sCAmbIL4SuE
> hpOdA+A6zaV7TFFqjk2b71dVeijCTO3B/nUjkwOY7lP56jOX4bM2YDZoZj1o0SsV
> bLsR3hjIlyZX1q83XNGPNYicueMZv9EsoUuZkwN3N/9CwTIbn27ck9xWfs3zOsOr
> DLppYHdcKQNByd630cL0xhgYEHShJJcUcRddXWCeuEJOQ0urFYvfiOW2H5Py86lE
> jwlA8XqIhvK5nmG5fOjwInSN3v+Fhd5A9rAhZrPZpP4+J1tGK37FvVhPJa9xXFWz
> OYgtUxP2y1zwYyq+qs5jCYy628HE3Y++YSUSK+mWSN8Id/jDBqKUzZkZWuc7750B
> wRy/8rb6F9L47sAVkg4gj8XqQF/gQ3gbS3ujf+eYuIf4GS4h1pmI4xCmuoZo0LLt
> NJo2k4jAfwx2l48BpjO9Ry8MaSft2a9vE0uBQR/jwY5dvn5Y0mYX8Dr2JgdFYpeW
> Skxf9+U2U/IzB2qePvdmo5u5QUyl40fu6/ndMjoEk/AXycwfodr6/UG9fLOG7uDR
> kLSU4n1jBzwEf+9WMtFA
> =7GKl
> -END PGP SIGNATURE-
>
> -
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: users-h...@tomcat.apache.org
>
>

Re: Tomcat listener not coming up - no stuck threads

2016-11-30 Thread Christopher Schultz

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

John,

On 11/26/16 7:29 PM, John D. Ament wrote:
> Hi,
> 
> Looking for some external input.  I've put together a simple
> tomcat embedded instance designed to deploy an arbitrary set of
> servlets, filters, etc.
> 
> For some reason, when I run tests with Tomcat the server never
> fully launches.  I can see the port in use, but connections to the
> server are not answered by the instance.  When I debug the start
> up, I see what appears to be a loop attempting to start services
> that never returns, in LifecycleBase.

So you see a busy-loop? What's the stack trace?

Tomcat version?

> Easiest way to reproduce it with this project is to clone 
> https://github.com/hammock-project/hammock/ and run a local build
> (to get snapshots) and then run 'mvn clean install -Ptomcat-test'
> from rest-resteasy (or spark or jersey).

Er... sorry, I'm not going to do that, and it doesn't look like anyone
else is going to do that, either.

> I'm sure there's something simple I'm over looking.

I browsed your github repo for about 15 seconds until I realized that
there are like 10k files and I'd never find the embedded driver
without asking. So, where is it?

Can you compare your driver with any of the many Tomcat test cases
that launch an embedded server instance? Those test classes do exactly
what it sounds like you are trying to do.

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

iQIcBAEBCAAGBQJYP4HoAAoJEBzwKT+lPKRYOL8P/A5MQFuVMK0kbgsAzbYVWx81
yLsIN5BgjMBwPCxr2S2KIg40/P8dq256+VFYkwLI/Y3kKi206IK0KQdRJCTQFEO9
avTOSFTgY3IXCCEEijSh5HeM8ofO7AgFrjcUGYZ6PI5PmnkCx/bN+sCAmbIL4SuE
hpOdA+A6zaV7TFFqjk2b71dVeijCTO3B/nUjkwOY7lP56jOX4bM2YDZoZj1o0SsV
bLsR3hjIlyZX1q83XNGPNYicueMZv9EsoUuZkwN3N/9CwTIbn27ck9xWfs3zOsOr
DLppYHdcKQNByd630cL0xhgYEHShJJcUcRddXWCeuEJOQ0urFYvfiOW2H5Py86lE
jwlA8XqIhvK5nmG5fOjwInSN3v+Fhd5A9rAhZrPZpP4+J1tGK37FvVhPJa9xXFWz
OYgtUxP2y1zwYyq+qs5jCYy628HE3Y++YSUSK+mWSN8Id/jDBqKUzZkZWuc7750B
wRy/8rb6F9L47sAVkg4gj8XqQF/gQ3gbS3ujf+eYuIf4GS4h1pmI4xCmuoZo0LLt
NJo2k4jAfwx2l48BpjO9Ry8MaSft2a9vE0uBQR/jwY5dvn5Y0mYX8Dr2JgdFYpeW
Skxf9+U2U/IzB2qePvdmo5u5QUyl40fu6/ndMjoEk/AXycwfodr6/UG9fLOG7uDR
kLSU4n1jBzwEf+9WMtFA
=7GKl
-END PGP SIGNATURE-

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

Tomcat listener not coming up - no stuck threads

2016-11-26 Thread John D. Ament

Hi,

Looking for some external input.  I've put together a simple tomcat
embedded instance designed to deploy an arbitrary set of servlets, filters,
etc.

For some reason, when I run tests with Tomcat the server never fully
launches.  I can see the port in use, but connections to the server are not
answered by the instance.  When I debug the start up, I see what appears to
be a loop attempting to start services that never returns, in LifecycleBase.

Easiest way to reproduce it with this project is to clone
https://github.com/hammock-project/hammock/ and run a local build (to get
snapshots) and then run 'mvn clean install -Ptomcat-test' from
rest-resteasy (or spark or jersey).

I'm sure there's something simple I'm over looking.

John

44 matches

Mail list logo