Hi, Chris. No worries on delays.

And first, to explain the differences we saw about the jrun4 folder, the
install I was looking at was in fact one implemented by a particular variant
of ColdFusion (multi-server mode, which deploys atop a JRun install that it
implements). If you didn't know, both JRun and ColdFusion where Macromedia
products, then bought by Adobe.

So I mistakenly presumed that a native install of JRun had that same JRE
directory, or perhaps there was at one time a choice of installers, one that
did and one that did not include a JVM. Either way, I guess the CF team
chose to implement it with its own JVM. Sorry for the confusion.

Fortunately, the rest of what I said stands. And yes (as I had alluded to)
you can tell JRun to point to any other JVM (true even in the CF-implemented
version of JRun), but if you're saying you point at the ones you have, and
they are 32-bit, and JRun comes up and yet STILL doesn't support the cert
(and you had imported to the cacerts under the one you pointed to), then
that's a stumper.

But was fun seeing JRun-talk being used again. I suppose this could be the
last thread ever, and these perhaps the last words. :-) We'll see.

/charlie


-----Original Message-----
From: Chris Parker [mailto:[email protected]] 
Sent: Monday, February 02, 2015 12:51 PM
To: jrun-talk
Subject: Re: JRun4 SSL "peer not authenticated"

First off, I apologize for taking so long to respond.  We had an "all hands
on deck" issue late Friday and over the weekend, and I'm only now getting
back to normal business...

> Chris, you mention several places you tried to import the cert to. The 
> first
two are in JVMs that you say you couldn't get JRun to use, right? 

No.  I'm sorry, my original wording could have been a bit more clear: When I
said I could not get a newer JVM to work, what I meant was that 1.6 was the
latest version that appears to work - in case someone answered with "1.6 is
old, why not use a newer JVM?"

JRun is configured to use the JVM that's at C:\Programs\jdk1.6.0\jre , and
that one definitely works.  There is *NO* JVM directly inside the JRun
folder.  That is to say that the path you mention -
"C:\JRun4\jre\lib\security\cacerts" - does not exist.
<snip>



~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
Order the Adobe Coldfusion Anthology now!
http://www.amazon.com/Adobe-Coldfusion-Anthology/dp/1430272155/?tag=houseoffusion
Archive: 
http://www.houseoffusion.com/groups/jrun-talk/message.cfm/messageid:5858
Subscription: http://www.houseoffusion.com/groups/jrun-talk/subscribe.cfm
Unsubscribe: http://www.houseoffusion.com/groups/jrun-talk/unsubscribe.cfm

Reply via email to