Prev: BufferedReader vs NIO Buffer
Next: Jetty 5.1 Multiple Contexts with 1 war
From: Peter Horlock on 13 Apr 2010 02:20
On 10 Apr., 01:34, EJP <esmond.not.p...(a)not.bigpond.com> wrote:
> On 9/04/2010 10:20 PM, Peter Horlock wrote:
>
> > Maybe you have another idea?
>
> No, I have the *same* idea. The truststore you specified couldn't be
> opened. Nothing you have done specifically addresses that problem.

The application (as far as I know) does not specify the truststore
location.
In the meantime, I've fixed the problem - I had to add the trustore
(cacerts file)
to the tomcat logs folder - this was missing on the server it was
working already,
as I said I had a complete copy. However, when I added the store to
the logs folder, it was working on the other server, too. I am really
confused now. How can it be that the trustore must be in the logs
folder??? Where does Java look for the store if no location is
specified?

Thanks in advance,

Peter
From: Peter Horlock on 13 Apr 2010 02:33
P.s.: This behaviour is reproducable - if I remove the cacerts file /
trustore, it won't work anymore, if I move it again into tomcat/logs
it's working again.
Maybe the file was in the logs folder of tomcat1 when it was started,
then removed. Only this could explain why it was working on Tomcat 1
but not on Tomcat2 which was a copy of 1.
I should restart Tomcat1 and see if it will still be working then.

Really strange!

Peter
From: EJP on 14 Apr 2010 05:34
On 13/04/2010 4:33 PM, Peter Horlock wrote:
> Really strange!

Nothing strange about it. Clearly Tomcat is configured to look for its
truststore in the logs folder, which BTW is a really stupid place for
it, and when it isn't there it can't be opened so you get this exception.

Exactly as I said really.
From: Peter Horlock on 14 Apr 2010 07:01
EJP schrieb:
> On 13/04/2010 4:33 PM, Peter Horlock wrote:
>> Really strange!
>
> Nothing strange about it. Clearly Tomcat is configured to look for its
> truststore in the logs folder, which BTW is a really stupid place for
> it, and when it isn't there it can't be opened so you get this exception.
>
> Exactly as I said really.

I finally found the reason - there was a starup.sh skript
which did a cd into the logs folder just before the app was started.
Seems like Java looks for the cacerts file in the current working directory.

(I still don't know why it was working once and out of the blue stopped
from working, but I guess I will never find out - someone must somehow
have deleted the file from the logs folder, probably because she/he
thought this cacerts file in the logs folder wasn't in use anymore...

Also, I still don't know why Tomcat ignored my System property which
should have told it where to look for the cacerts file instead...

Peter
From: Lew on 14 Apr 2010 17:24
EJP wrote:
> Nothing strange about it. Clearly Tomcat is configured to look for its
> truststore in the logs folder, which BTW is a really stupid place for

That's not true by default.

> it, and when it isn't there it can't be opened so you get this exception.
>
> Exactly as I said really.

--
Lew
First  |  Prev  |  Next  |  Last
Pages: 1 2 3 4
Prev: BufferedReader vs NIO Buffer
Next: Jetty 5.1 Multiple Contexts with 1 war