Re: Tomcat is not Coming Up

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

Re: tomcat is not coming Up

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.

RE: tomcat is not coming Up

> 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

RE: tomcat is not coming Up

mail 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, > > >

RE: tomcat is not coming Up

id: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 environ

RE: tomcat is not coming Up

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

RE: tomcat is not coming Up

anges 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&

AW: Tomcat is not Coming Up

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 hav

RE: tomcat is not coming Up

rtup 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 Whe

Re: tomcat is not coming Up

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]

Re: tomcat is not coming Up

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

Re: Tomcat is not Coming Up

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. > > > >

tomcat is not coming Up

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]

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 :

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

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. . . .

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

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

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

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

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

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

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

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

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

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

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

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.

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

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

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

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]

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

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 > >

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

-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

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

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

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

-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: >>>

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

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

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

-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

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

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

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

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 >>>

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

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"

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

-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

Re: Tomcat listener not coming up - no stuck threads

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.

Re: Tomcat listener not coming up - no stuck threads

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

Re: Tomcat listener not coming up - no stuck threads

-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 >>>

Re: Tomcat listener not coming up - no stuck threads

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

Re: Tomcat listener not coming up - no stuck threads

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

Re: Tomcat listener not coming up - no stuck threads

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 < >

Re: Tomcat listener not coming up - no stuck threads

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

Re: Tomcat listener not coming up - no stuck threads

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.

Re: Tomcat listener not coming up - no stuck threads

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

Re: Tomcat listener not coming up - no stuck threads

-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

Tomcat listener not coming up - no stuck threads

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