On Tue, 7 Sep 2004, Igor Zlatkovic wrote:
| I have found the solution and will share it here incase someone
| encounters a similar problem in the future.
|
| The solution is:
|
| # cd /dev
| # mv random random-old
| # ln -s urandom random
|
| however bizarre that may sound. It seems that
PROTECTED]
Sent: Sunday, September 05, 2004 10:16 AM
To: [EMAIL PROTECTED]
Subject: TLS-Enabled Connector Prevents Startup
Hi there.
On one day, an otherwise perfectly functioning Tomcat stops responding
to requests. The log file says that one of the threads received an
OutOfMemory exception, so I
Has the certificate the SSL/TLS connection uses
expired? This will cause the TLS connection to fail
to come up. Then, if you have a security constraint
defined in your web.xml file that requires TLS for
your initial pages, the redirect from your normal port
to the TLS port will fail (since the
On 07/09/04 15:27, Shapira, Yoav wrote:
Hi,
Is there any additional debug output in the logger, specifically a
ClassNotFoundException or a NoClassDefFoundError for a TLS-related
class? Has the JVM you're using changed?
Unfortunately, there is no additional output. I would have been very
happy
On 07/09/04 17:42, Jason Palmatier wrote:
Has the certificate the SSL/TLS connection uses
expired? This will cause the TLS connection to fail
to come up. Then, if you have a security constraint
defined in your web.xml file that requires TLS for
your initial pages, the redirect from your normal
I have found the solution and will share it here incase someone
encounters a similar problem in the future.
The solution is:
# cd /dev
# mv random random-old
# ln -s urandom random
however bizarre that may sound. It seems that the recent Linux kernel
update wasn't up to Tomcat's liking. For
Hi,
Thanks for posting your solution.
Yoav Shapira
Millennium Research Informatics
-Original Message-
From: Igor Zlatkovic [mailto:[EMAIL PROTECTED]
Sent: Tuesday, September 07, 2004 2:00 PM
To: Tomcat Users List
Subject: Re: TLS-Enabled Connector Prevents Startup
I have found
On Tue, Sep 07, 2004 at 07:59:46PM +0200, Igor Zlatkovic wrote:
: however bizarre that may sound. It seems that the recent Linux kernel
: update wasn't up to Tomcat's liking. For whatever the reason, Tomcat's
: initialising of the TLS connector blocks in a read from /dev/random,
: always.
On 07/09/04 20:12, QM wrote:
You may want to check what the kernel's using as a source of randomness.
I forget the details, but IIRC /dev/urandom never blocks, whereas
/dev/random may block under {some condition I can't recall in detail}.
Well, the server in question is a vServer, a virtual server
Hi there.
On one day, an otherwise perfectly functioning Tomcat stops responding
to requests. The log file says that one of the threads received an
OutOfMemory exception, so I restart the server. Not a big deal, it has
happened before. But this time the server never comes up, it hangs
10 matches
Mail list logo
