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]
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
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
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
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
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
Thomas,
On 4/15/22 14:11, Thomas Hoffmann (Speed4Trade GmbH) wrote:
-Ursprüngliche Nachricht-
Von: Christopher Schultz
Gesendet: Freitag, 15. April 2022 19:21
An: users@tomcat.apache.org
Betreff: Re: AW: [OT] Getting TLS handshake details
Thomas,
On 4/15/22 02:25, Thomas Hoffmann
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.
. . .
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
> -Ursprüngliche Nachricht-
> Von: Christopher Schultz
> Gesendet: Freitag, 15. April 2022 19:21
> An: users@tomcat.apache.org
> Betreff: Re: AW: [OT] Getting TLS handshake details
>
> Thomas,
>
> On 4/15/22 02:25, Thomas Hoffmann (Speed4Trade GmbH) wrote:
> > Hello Chris,
> >
> >>
Thomas,
On 4/15/22 02:25, Thomas Hoffmann (Speed4Trade GmbH) wrote:
Hello Chris,
-Ursprüngliche Nachricht-
Von: Christopher Schultz
Gesendet: Donnerstag, 14. April 2022 23:15
An: users@tomcat.apache.org
Betreff: Re: [OT] Getting TLS handshake details
Peter,
On 4/14/22 03:45, Peter
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.
Hello Chris,
> -Ursprüngliche Nachricht-
> Von: Christopher Schultz
> Gesendet: Freitag, 15. April 2022 21:28
> An: users@tomcat.apache.org
> Betreff: Re: AW: AW: [OT] Getting TLS handshake details
>
> Thomas,
>
> On 4/15/22 14:11, Thomas Hoffmann (Speed4Trade GmbH) wrote:
> >
> >
> >>
Chris,
> Am 14.04.2022 um 23:21 schrieb Christopher Schultz
> :
>
> Peter,
>
>> On 4/14/22 03:45, Peter Kreuser wrote:
>> Chris,
Am 13.04.2022 um 21:37 schrieb Christopher Schultz
:
>>> All,
>>> I asked this question a few years ago on SO and I didn't really get an
>>> answer:
Hello Chris,
> -Ursprüngliche Nachricht-
> Von: Christopher Schultz
> Gesendet: Donnerstag, 14. April 2022 23:15
> An: users@tomcat.apache.org
> Betreff: Re: [OT] Getting TLS handshake details
>
> Peter,
>
> On 4/14/22 03:45, Peter Kreuser wrote:
> > Chris,
> >
> >> Am 13.04.2022 um
On Thu, 14 Apr, 2022, 01:06 Christopher Schultz, <
ch...@christopherschultz.net> wrote:
> All,
>
> I asked this question a few years ago on SO and I didn't really get an
> answer:
>
>
16 matches
Mail list logo
