hello hassan!

thanks for your input ... i guess i finally found out what it was, though it still seems a little bit strange to me:
the portforwarding is the problem, without it, the right ssl certificate is chosen, otherwise the system takes the one of the ip adress associated with eth0.
hmm - it's strange though as this seems to work with other java servlet engines like jetty.


i will try to find a way to run tomcat as a normal user on priviledged ports, this should fix it.

kind regards

randolph

At 17:52 17.01.2005, you wrote:
Parsons Technical Services wrote:
unfortunately this does not seem to solve the problem ... but results in the following error (as the given keystore cannot be used)

java.io.FileNotFoundException: /home/essence/.keystore (No such file or directory)

First, the give server.xml showed the keystore file (originally) as "/home/essence/essence/KEYS/c.keystore" which doesn't match the reported error above -- check for typos.

Tomcat needs the name of the keystore to be .keystore

No it doesn't. The name (and path) is arbitrary, which is why there *is* a keystoreFile attribute.

As I said before, I haven't done this myself.

I have, and none of my installations use ".keystore" as the file name...

--
Hassan Schroeder ----------------------------- [EMAIL PROTECTED]
Webtuitive Design ===  (+1) 408-938-0567   === http://webtuitive.com

                          dream.  code.



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

----------------------------------------------------------------------- di randolph kepplinger, mba [EMAIL PROTECTED] / 0676-844899-800

metamagix - better online solutions
favoritenstrasse 19 / 1040 wien / +43.1.9902804
buero: hackengasse 27 / 1150 wien / +43.1.9902804
http://www.metamagix.net


--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to