Lots of weird behavior as of Wildfire 3.0.0

Openfire Plugins Asterisk-IM
1

Hi!

I don’‘t actively use Asterisk-IM right now, but I tend to keep a lot of the plugins installed just to look at them and such. As of 3.0.0, the Asterisk-IM plugin does not seem to function at all. I’'ll go into the various -isms individually:

Using the new plugin manager, if I go to restart or delete this plugin, I get:

cut

HTTP ERROR: 500

Internal Server Error

RequestURI=/plugin-admin.jsp

Powered by Jetty://

/cut

If I go to auto-upgrade it (I had a 1.1 to 1.1.1 upgrade pending), it says Upgrade complete, but then nothing happens.

In my info logs, I get this over and over again:

2006.07.03 21:38:30 unloading asterisk-im plugin resources

2006.07.03 21:38:30 Unregistering asterisk-im plugin as a component

2006.07.03 21:38:51 unloading asterisk-im plugin resources

2006.07.03 21:38:51 Unregistering asterisk-im plugin as a component

2006.07.03 21:39:11 unloading asterisk-im plugin resources

2006.07.03 21:39:11 Unregistering asterisk-im plugin as a component

2006.07.03 21:39:31 unloading asterisk-im plugin resources

2006.07.03 21:39:31 Unregistering asterisk-im plugin as a component

2006.07.03 21:39:51 unloading asterisk-im plugin resources

2006.07.03 21:39:51 Unregistering asterisk-im plugin as a component

2006.07.03 21:41:14 unloading asterisk-im plugin resources

2006.07.03 21:41:14 Unregistering asterisk-im plugin as a component

Similar message in debug log. Nothing else really useful in that regard.

No Asterisk tab like what used to exist.

I tried removing the plugin entirely and then using the web interface to install the latest version. Same thing happens.

I’'m going to remove the plugin for now so it stops bothering me logs, but hey. =) Any ideas?

2

I’'ve also had issues trying to get the Asterisk-IM plugin to work in both Wildfire 3.0.0 and Wildfire 3.0.0 Beta. Here is a snippet of the log information from my server:

2006.06.29 00:45:11 org.jivesoftware.wildfire.container.PluginManager.loadPlugin(PluginManager.java: 417 ) Error loading plugin

java.lang.NoSuchMethodError: org.jivesoftware.database.DbConnectionManager.isSQLCommandPart(Ljava/lang/Strin g;)Z

at org.jivesoftware.phone.database.DatabaseUtil.applyScript(DatabaseUtil.java:158)

at org.jivesoftware.phone.database.DatabaseUtil.upgradeDatabase(DatabaseUtil.java: 59)

at org.jivesoftware.phone.asterisk.AsteriskPlugin.init(AsteriskPlugin.java:97)

at org.jivesoftware.phone.asterisk.AsteriskPlugin.initializePlugin(AsteriskPlugin. java: 87)

at org.jivesoftware.wildfire.container.PluginManager.loadPlugin(PluginManager.java :343)

at org.jivesoftware.wildfire.container.PluginManager.access$200(PluginManager.java :46)

at org.jivesoftware.wildfire.container.PluginManager$PluginMonitor.run(PluginManag er.ja va:755)

at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:417)

at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:280)

at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:135)

at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101 (Sche duledThreadPoolExecutor.java:65)

at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodi c(Sch eduledThreadPoolExecutor.java:142)

at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Schedu ledTh readPoolExecutor.java:166)

at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java: 650)

at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)

at java.lang.Thread.run(Thread.java:595)

In addition, the plugin attempts to initialize every 20 seconds.

…

2006.06.29 00:48:32 Initializing Asterisk-IM Plugin

2006.06.29 00:48:52 Initializing Asterisk-IM Plugin

2006.06.29 00:49:12 Initializing Asterisk-IM Plugin

…

The Asterisk IM tab (and related options) are not displayed.

If it helps any, my Wildfire 3.0.0 server is running on a Gentoo 2006.0 Linux machine with Java version 1.5.0_06.

Message was edited by: gbobeck

3

This doesn’'t appear to be happening anymore. Calling it closed.

4

There was a bug that was introduced between 3.0.0 and 3.1.0 beta that broke the plugin upgrade process. I would guess this is what you were seeing, it has been fixed now. JM-818

Thanks,

Alex