java.lang.OutOfMemoryError from ymsg

Openfire Plugins Kraken - IM Gateway
1

First of all, thanks for the great plugin!

Here’'s a little problem I have with the plugin, hope this post will be of help to your development.

I’'m the only user logged on to the Wildfire server, after running the gateway plugin with MSN and Yahoo enabled, I get 60-100+ notifications on my PSI client in 1 shot, and the client gets non-responsive.

At the same time, the following message is displayed on the Wildfire admin program:

Exception in thread “Network Input” java.lang.OutOfMemoryError: unable to create new native thread

at java.lang.Thread.start0(Native Method)

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

at ymsg.network.Session$FireEvent.start(Session.java:2444)

at ymsg.network.Session$FireEvent.fire(Session.java:2443)

at ymsg.network.Session$InputThread.run(Session.java:2272)

I’'m using Wildfire 3.1.0 Beta, the same problem occured with both plugin beta 1 and 2.

Anyway, great job creating this plugin! Saved me from the python nightmares

2

Out of memory? Well that’'s not cool. How much memory do you have on the machine that is running Wildfire?

3

It’'s an old machine, 1.2Ghz Celeron with 384Mb RAM (256+128) on Win2k.

Is there any way I can set the memory allocated when starting Wildfire?

Thanks.

4

Daniel,

I think the root cause is the flood of messages. I saw this when I was testing the ymsg library patch. Something goes into a loop and both the client and server become unresponsive and have to be killed. I think it’‘s subscription related but I wasn’'t able to recreate the problem on command. I can try again this afternoon.

george

5

How are you seeing the flood of messages? Are they between Yahoo and the plugin? XMPP client and the plugin? Something else?

6

XMPP client and the plugin. I didn’'t think to get an ethereal trace but I will.

7

Yikes, yeah I’‘d be quite interested in seeing what’'s going on!

8

It figures. I can’'t reproduce it at all now. IIRC, the problem happened when a yahoo user added me to their roster. I got a flood of “input error” messages which continued until I bounced the server. I wonder if it was fixed in what you did over the past few days.

kkttt: You might want to download the nightly build for tonight and see if thiat fixes the problem.

9

Thanks, will give that a try

10

Hi guys,

I’‘ve done a clean install of wildfire_3_1_0_beta_2 and gateway plugin beta 2, but I’'m still getting the same OutOfMemory error 30 minutes into running both MSN and Yahoo plugins. Is there any way for me to generate more debugging information?

After the error occurred, I restarted Wildfire and enabled the MSN gateway only. I tried to remove the Yahoo registration via the admin console and got the stacktrace below:

???error.exception???

java.lang.NullPointerException

at org.jivesoftware.wildfire.plugin.gateway.gateway_002dregistrations_jsp._jspServ ice(gateway_002dregistrations_jsp.java:94)

at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:94)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:689)

at org.jivesoftware.wildfire.container.PluginServlet.handleJSP(PluginServlet.java: 234)

at org.jivesoftware.wildfire.container.PluginServlet.service(PluginServlet.java:92 )

at javax.servlet.http.HttpServlet.service(HttpServlet.java:689)

at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:428)

at org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(WebApplica tionHandler.java:830)

at org.jivesoftware.admin.PluginFilter.doFilter(PluginFilter.java:69)

at org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(WebApplica tionHandler.java:821)

at org.jivesoftware.admin.AuthCheckFilter.doFilter(AuthCheckFilter.java:98)

at org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(WebApplica tionHandler.java:821)

at com.opensymphony.module.sitemesh.filter.PageFilter.parsePage(PageFilter.java:11 8)

at com.opensymphony.module.sitemesh.filter.PageFilter.doFilter(PageFilter.java:52)

at org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(WebApplica tionHandler.java:821)

at org.jivesoftware.util.LocaleFilter.doFilter(LocaleFilter.java:65)

at org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(WebApplica tionHandler.java:821)

at org.jivesoftware.util.SetCharacterEncodingFilter.doFilter(SetCharacterEncodingF ilter.java:41)

at org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(WebApplica tionHandler.java:821)

at org.jivesoftware.admin.PluginFilter.doFilter(PluginFilter.java:69)

at org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(WebApplica tionHandler.java:821)

at org.jivesoftware.admin.AuthCheckFilter.doFilter(AuthCheckFilter.java:98)

at org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(WebApplica tionHandler.java:821)

at org.mortbay.jetty.servlet.WebApplicationHandler.dispatch(WebApplicationHandler. java:471)

at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:568)

at org.mortbay.http.HttpContext.handle(HttpContext.java:1530)

at org.mortbay.jetty.servlet.WebApplicationContext.handle(WebApplicationContext.ja va:633)

at org.mortbay.http.HttpContext.handle(HttpContext.java:1482)

at org.mortbay.http.HttpServer.service(HttpServer.java:909)

at org.mortbay.http.HttpConnection.service(HttpConnection.java:816)

at org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:982)

at org.mortbay.http.HttpConnection.handle(HttpConnection.java:833)

at org.mortbay.http.SocketListener.handleConnection(SocketListener.java:244)

at org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:357)

at org.mortbay.util.ThreadPool$PoolThread.run(ThreadPool.java:534)

Hope the above information helps

11

This exception is a know problem. It happens everey time you try to remove a transport that is not active.

12

kkitt, did you try the nightly build from last night? It looks like you reinstalled the latest beta releases, not the nightly build. You can find them at http://www.jivesoftware.org/nightly.jsp. (you will want wildfire server). I must admit I’‘ve never tried a nightly, so I’'m only assuming it comes with the plugins.

13

Also yeah, definitely a known problem. Need to rearchitect certain pieces to get that fixed. Thanks for bringing it up again though as I hadn’'t remembered to create an issue for it. GATE-72

14

Hi guys,

I’'ve tried out the latest nightly build (wildfire_2006-09-26.zip), but I still got the memory error message 15 minutes into logging in. I have 8 Yahoo contacts and 12 MSN contacts in my list.

Anyway, I thought it could be due to the old machine having insufficient RAM, so I did a clean installation of the nightly build on another machine (Xeon 2.8Ghz, 1 Gb RAM). The same error occurred again but at a later time (approx 1 hr after logging in).

15

Strange.

The latest plugin code doesn’'t come with the nightly builds I just figured out. Can you try the nightly build from last night, then grab the plugin from http://www.peakin.com/download/gateway.jar You can just pace the jar file in wildfire/plugins.

Then without running the admin console at all, see how long it takes to get the error and post the stack trace.

16

You can actually try beta 3 at this point as well. Will probably be the same as what George built though, except that it says 1.0 Beta 3.

17

Hi,

Will try that out, but where can I download it from? Couldn’'t find it on the download or nightly build pages.

Thanks.

18

There’'s a link in the release post, but if you look on the downloads page, look for the plugins link, then look for a “beta plugins” link.

19

Hi,

I’'ve tried using both the plugin downloaded from http://www.peakin.com/download/gateway.jar as well as beta 3, but I am got the same stack trace.

How do I run without the admin console? The stack trace I get now is still the same as the one I posted in the first post, is there any ways to provide more debug info?

Seems like I am the only one with this problem, perhaps it’'s a configuration mistake on my part

Thanks.

20

It might be interesting to see what kind of memory wildfire is using up when you are seeing this message and such. Like “top” on unix would be useful to see. Not sure about other OS’'s.