Plugin constantly loads and unloads itself

Has anyone seen this yet? Just downloaded the plugin today, running on 3.1.0 beta 2, Redhat linux.

From the info log:

2006.10.04 16:24:27 Stopping transport service: msn

2006.10.04 16:24:27 Stopping transport service: irc

2006.10.04 16:24:27 Stopping transport service: icq

2006.10.04 16:24:27 Stopping transport service: yahoo

2006.10.04 16:24:27 Stopping transport service: aim

2006.10.04 16:24:30 Starting transport service: aim

2006.10.04 16:24:30 Starting transport service: icq

2006.10.04 16:24:30 Starting transport service: irc

2006.10.04 16:24:30 Starting transport service: yahoo

2006.10.04 16:24:30 Starting transport service: msn

2006.10.04 16:24:50 Stopping transport service: msn

2006.10.04 16:24:50 Stopping transport service: irc

2006.10.04 16:24:50 Stopping transport service: icq

2006.10.04 16:24:50 Stopping transport service: yahoo

2006.10.04 16:24:50 Stopping transport service: aim

2006.10.04 16:24:54 Starting transport service: aim

2006.10.04 16:24:54 Starting transport service: icq

2006.10.04 16:24:54 Starting transport service: irc

2006.10.04 16:24:54 Starting transport service: yahoo

2006.10.04 16:24:54 Starting transport service: msn

2006.10.04 16:25:14 Stopping transport service: msn

2006.10.04 16:25:14 Stopping transport service: irc

2006.10.04 16:25:14 Stopping transport service: icq

2006.10.04 16:25:14 Stopping transport service: yahoo

2006.10.04 16:25:14 Stopping transport service: aim

… and so on…

The configuration options for the plugin appear and disappear when it loads / unloads. The jabber browser from the client (using jajc) can see the transports but the option to register to them is disabled (even though I have enabled registration on all transports from the config.)

I’'m lost on this one. No errors appear… etc.

Ok, restarting wildfire seems to have stopped the service from bouncing but I still can’'t register against the transports they I would with the python transports.

dont suppose you’'ve got the same prob as me?

http://www.jivesoftware.org/community/thread.jspa?threadID=22308&tstart=0

Ian

I don’‘t think it’‘s the same problem. I can connect to MSN through the transport if I manually register the account from the plugin page on wildfire’‘s console. I just couldn’'t register with the transport from the client side.

Now that I think about it, this might be a wildfire issue and not a transport issue as I couldn’'t register with the MSN python 11.1 transport earlier today. (Was running pymsn 10.3 previously.)

I believe that this is the same issue, just seeing it from the other end. What is causing it? Unclear so far. Did you have debug logs turned on? Anything in error? debug? warning? Any stacktraces?