powered by Jive Software

SSL Problem

Hi there,

I’‘m a newbie with JM but was able to successfully install the server and configure AD integration. Now I’'m trying to setup SSL for encrypted connection and followed the SSL guide with all self-signed cert only. The problem is, the SSL module of JM is not starting with “Access denied” error, I attached here the log for your reference.

Can someone tell me what I missed? ''will appreciate your help.

Thanks.

(sorry for my English)

2005.06.02 09:39:49 [org.jivesoftware.messenger.container.AdminConsolePlugin.initializePlugin(Admin ConsolePlugin.java:176)

] Trouble initializing admin console

org.mortbay.util.MultiException[java.io.FileNotFoundException: D:\Jive Messenger Server\resources\security (Access is denied)]

at org.mortbay.http.HttpServer.doStart(HttpServer.java:673)

at org.mortbay.util.Container.start(Container.java:72)

at org.jivesoftware.messenger.container.AdminConsolePlugin.initializePlugin(AdminC onsolePlugin.java:146)

at org.jivesoftware.messenger.container.PluginManager.loadPlugin(PluginManager.jav a:179)

at org.jivesoftware.messenger.container.PluginManager.access$300(PluginManager.jav a:57)

at org.jivesoftware.messenger.container.PluginManager$PluginMonitor.run(PluginMana ger.java:408)

at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)

at java.util.concurrent.FutureTask$Sync.innerRunAndReset(Unknown Source)

at java.util.concurrent.FutureTask.runAndReset(Unknown Source)

at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101 (Unknown Source)

at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodi c(Unknown Source)

at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknow n Source)

at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)

at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)

at java.lang.Thread.run(Unknown Source)

You may disregard my previous post.

It seems JM’'s SSL listener is already enabled after installation. I noticed it when I installed on another machine and tried ssl connection with my client.

Since we only require light security, perhaps the default ssl configuration is okay for us.

Thanks anyway.