powered by Jive Software

Installing Fastpath Webchat on OpenFire 3.8.2

Hi all,

I am relatively new to OpenFire but have it runing very sucsesfully in a small company about 25 users. I now what to add Fastpath and Webchat to our openfire server. I have installed the main Fastpath plugin but when I come to istall the Webchat plugin I get the folowing in the log and it does not work.

2013.09.20 08:10:09 org.jivesoftware.openfire.container.PluginManager - Error loading plugin: /usr/share/openfire/plugins/webchat
java.lang.NoClassDefFoundError: org/mortbay/jetty/servlet/Context
at java.lang.Class.getDeclaredConstructors0(Native Method)
at java.lang.Class.privateGetDeclaredConstructors(Class.java:2483)
at java.lang.Class.getConstructor0(Class.java:2793)
at java.lang.Class.newInstance(Class.java:345)
at org.jivesoftware.openfire.container.PluginManager.loadPlugin(PluginManager.java :420)
at org.jivesoftware.openfire.container.PluginManager.access$300(PluginManager.java :80)
at org.jivesoftware.openfire.container.PluginManager$PluginMonitor.run(PluginManag er.java:1073)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:351)
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:178)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301 (ScheduledThreadPoolExecutor.java:178)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Schedu ledThreadPoolExecutor.java:293)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:724)
Caused by: java.lang.ClassNotFoundException: org.mortbay.jetty.servlet.Context
at java.net.URLClassLoader$1.run(URLClassLoader.java:366)
at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
… 15 more

All assistance will be very much appreciated.

Hi. try this: http://community.igniterealtime.org/thread/47375

Hi Ivan,

I think I did but I will try again.

Hi all,

Have tryed Ivans sujestion and unfortuanatly it does not work.

Just a quick update. I have installed Tomcat on the same server and after having configured it I have uploaded the webchat.war file and it works.http://www.igniterealtime.org/projects/openfire/plugins/webchat.war

How did you get it to work with Tomcat. I installed, configured,and started Tomcat. I put the webchat folder under the webapps folder in Openfire 3.9.1. Openfire is configured to use port 7070. When I go to the URL http://myserver.com:7070/webchat/, it says it is not found. Do I use a different path?

bricoleur have you installed Tomcat as a seperate install? if so you need to access the tomcat admin panel and installed it through there.

I would have thought this issue was resolved in 3.9.1 but from what you have found it must not be so.

PS I will update this with more info in the next few hours.

tomcat defaults to port 8080

Yes, I did install Tomcat as a separate install. I didn’t use the tomcat admin panel and it installed fine after som configuration.

So, I got it working. Thanks to Jason, I switched ports to 8080 and now have it working. Thanks!

One question, what if I was to install Tomcat on a separate server from Openfire. How would they know about each other?


Thanks. That got me on track!

http://wiki.apache.org/tomcat/FAQ/Connectors#Q3 might be worth reading. It discusses integration of Tomcat and Apache. http://sanketdangi.com/post/43734145363/secure-tomcat-through-apache-using-ajp talks about using AJP with Tomcat and Apache.

when you first configure the Webchat on your tomcat server (by browsering to yourserver.com:8080/webchat… it should ask you for the server details and other setup information. After that, you should be on track