I suggest the following additional params:
-Dcom.sun.management.jmxremote.host=ip-address
-Djava.rmi.server.hostname=ip-address, same as above
For me, this (with the options below, of course) works as expected.
wbr Johann
From: Adrien RUFFIE
Sent: Thursday, December 06, 2012 4:03 PM
To:
As I unterstand the mails before, you are merging Java-Certificates with
OpenSSL ones.
In the Tomcat connector you should use a SUN-JKS keystore instead of
PEM-Files (usually created by OpenSSL utilities).
Enter Tomcat SSL keystore in Google to get the recommended how-to.
Be aware of the
If you are still looking for a solution:
There is a mismatch in your informations: you wrote, the keystore file would
be located in your home directory but in the connector properties the
keystore is referenced to be located at /user/machine/.keystore: are you
aware of this difference?
We are running into some issues on a shared hosting machine. Basically
Java
is eating too much memory! :-)
Is it possible to set the amount of memory that a virtual host is allowed
to
consume? Perhaps in the server.xml
We have the overall JVM set to use 1024mb of ram, but it is getting
Richard Reyes wrote:
I have not had the chance to try the heap size and class reloading
thing, but would still like to learn on other might be areas of
improvements.
To be able to influence the memory consumption (e.g. to tune the
PermGen-Space) is the main criteria and most efficient way
To ensure you have a valid keystore with the included private key and a
refer to an alias 'tomcat' I recommend strongly to create a new keystore as
described in the reference (see links in other answer mails). At least you
can create a self-signed certificate if you don't need one signed by a
Schadler Johann wrote:
I would prefer to use an explicit method to define a context, not only
the
implicit possibility by naming the WAR file to something which doesn't
refer
anyway to the service provided in the physical directory ROOT. Is there
a
possibility to do this in may
We usually use Tomcat instances without Apache connector and we could do
this without problems with Tomcat 4.x until now by defining a docBase to the
path= in a context located in the server.xml. (Usually we configure
virtualhosts for a service with the default path - no additional context
must
