Additionally you may want to make sure that the keystore file can be found
by the user account that the tomcat service will run under.
For my installation I do an explict:
In the SSL connector and make sure I have a the file "mykeystore.ks" in the
conf folder.
Anthony
-Original Message---
the
custom Realm. You just create your own mbeans-descriptors.xml file with
your Realm, and in "server.xml" set:
and all of your custom classes will be registered. It works great for me.
"Anthony Mutiso 2" <[EMAIL PROTECTED]> wrote in message
[EMAIL PROTECTED]"
Hi,
I am trying to configure two tomcat servers on a single win2k host with two
nic with 4 ip addresses.
A 4.0.6 server configured on IP 192.168.1.1 and 192.168.2.1 on port 80 and
443 with no AJP connector activated.
A 4.1.12 server configured on IP 192.168.1.2 and 192.168.2.2 on port 8080
and 84
I have a webapp with a custom realm class.
The webapp worked fine in TC 4.0.5.
When I migrate my webapp to 4.1.12 I get Managed Bean errors which fail my
realm initialization.
On searching the mail-list I found suggestions that I need to register the
realm class in the mbeans-discriptors.xml file.