Hi Carl,
The error is simply telling you the address/port that it is
attempting to connect to is in use. Possibly see what ports your using in
the server.xml, and maybe compare that to a netstat -a command listing of
the ports. Hope that helps some.
Jeremy Davis
Senior Support Analyst
He is referring to the JVM parameters to limit the amount of memory the JVM
is allotted. They are java command line parameters. That will atleast give
you the direction for documentation. java.sun.com search should result in
more detail for you.
Jeremy Davis
Senior Support Analyst
BPI
, it affects any java process on linux, I've checked.
Ryan
-Original Message-
From: Davis, Jeremy [mailto:[EMAIL PROTECTED]
Sent: Monday, March 24, 2003 11:01 AM
To: 'Tomcat Users List'
Subject: RE: Too many processes
He is referring to the JVM parameters to limit the amount of memory
Do you have a webserver already up and listening on port 80? I don't know
for sure, but that would be my first guess, if that helps.
Jeremy Davis
Senior Support Analyst
BPI Marketplace Integration
614.760.8941
1.800.436.8726 - Support Line
-Original Message-
From: Lisa Foister
I got red hat 8.0, jdk 1.3.1_07, and tomcat 3.3.1a installed. If on the
server, I do localhost:8080, it works ok and comes up with the welcome page,
but when I do machinename:8080 it comes back telling me the connection was
refused?
Thanks,
Jeremy Davis
Senior Support Analyst
BPI Marketplace
and
none other
Host name=localhost/
Aliasmachinename/Alias - will take requests for localhost + machinename
Host name=machinename... / - will take requests for machinename but not
localhost
John
On Fri, 21 Mar 2003 14:32:17 -0500, Davis, Jeremy
[EMAIL PROTECTED] wrote:
I got red hat 8.0
:39 -0500, Davis, Jeremy
[EMAIL PROTECTED] wrote:
I was wondering, I saw the virtual host configuration documentation, and
was
about to attempt such a thing. So I should add an Alias tag, under a
host
tag in the server.xml?
Jeremy Davis
Senior Support Analyst
BPI Marketplace Integration
the connection
w/ mach inename
Cool. Tomcat still has its own resolution rules, though.
John
On Fri, 21 Mar 2003 15:53:40 -0500, Davis, Jeremy
[EMAIL PROTECTED] wrote:
Thanks, I have found that it was not tomcat at all, the issue is a
networking mismatch between the dns name, and the real ip
. Connection Refused
typically means there's nothing listening on that port, in this case 8007.
John
On Fri, 21 Mar 2003 16:16:42 -0500, Davis, Jeremy
[EMAIL PROTECTED] wrote:
Maybe you can give me some insight into why I am having problems with the
tomcat.sh stop command. When I do ./tomcat.sh stop
I setup a tomcat 3.3.1 system, with the ssl connector, JSSE, generated cert
and keystore, per documentation.
Every time I attempt to hit https://theserver:8443/ we get the below in the
console window for tomcat...
PoolTcpEndpoint: Handshake failed
javax.net.ssl.SSLException: bad handshake record
You may want to try some JVM tweaks to play with the memory heap size, the
garbage collection size and such?
Jeremy Davis
Senior Support Analyst
BPI Marketplace Integration
614.760.8941
1.800.436.8726 - Support Line
-Original Message-
From: Claudio Pimentel Modesto [mailto:[EMAIL
There is an issue with the JDK 1.3.x and NT running as a service? Maybe try
and upgrade the jdk to 1.4?
Jeremy Davis
Senior Support Analyst
BPI Marketplace Integration
614.760.8941
1.800.436.8726 - Support Line
-Original Message-
From: Strecker, Mark [mailto:[EMAIL PROTECTED]
Sent:
12 matches
Mail list logo