powered by Jive Software

Problems after upgrading Jive 2.3.0 to Wildfire 2.4.2


I’'ve been running Jive messenger for a while now, and it has been running great!

I tried to upgrade my Jive installation to Wildfire 2.4.2, but am stuck. I am running it on a windows 2000 server / JVM 1.5

Here is what i did:

I followed http://www.jivesoftware.org/community/entry.jspa?entryID=481[/i] (Steps for upgrading Jive Messenger to Wildfire), and backed up my embedded-db folder and the jive-messenger.xml file from the conf folder. I do not have a wildfire-service.exe.vmoptions.

I installed wildfire in a separate folder, copied the files into the program files\wildfire\embedded-db and \conf folders, after renaming them as appropriate.

When i start Wildfire, here is what it tells me:

Found old database schema (2.2). Upgrading to latest schema.

Warning: Make sure that database was not modified for release: 2.3. Upgrade script not found: /database/upgrade/2.2_to_2.3/wildfire_hsqldb.sql

Database upgraded successfully.

Wildfire 2.4.2

Admin console listening at:



I dont have a 2.2_to_2.3 folder in /upgrade folder, and I read somewhere in the forums that that is normal.

Now, here is the problem:

None of the users are getting logged in to the wildfire server. I am using Exodus / Jajc / Spark clients. The clients are stuck at the “Authenticated, Getting Contacts” stage, and never go further. The server’'s admin console show that the users indeed have active sessions.

I am able to view the “User Summary” in the admin console. But when i click on “Group Summary”, i get


Illegal JID: satish_b


Powered by Jetty://[/b]

If i go back to Jive 2.3.0 with the same db, all is fine. The username it shows (satish_b) is a valid user. when i try to delete that user from the users list, i get:


java.lang.IllegalArgumentException: Illegal JID: abdul_7641

at org.xmpp.packet.JID.init(JID.java:398)

at org.xmpp.packet.JID.(JID.java:254)

at org.jivesoftware.wildfire.group.DefaultGroupProvider.getMembers(DefaultGroupPro vider.java:433)

at org.jivesoftware.wildfire.group.DefaultGroupProvider.getGroup(DefaultGroupProvi der.java:118)

at org.jivesoftware.wildfire.group.GroupManager.getGroup(GroupManager.java:107)

at org.jivesoftware.wildfire.group.DefaultGroupProvider.getGroups(DefaultGroupProv ider.java:265)

at org.jivesoftware.wildfire.group.GroupManager.getGroups(GroupManager.java:169)

at org.jivesoftware.wildfire.roster.RosterManager.getSharedGroups(RosterManager.ja va:151)

at org.jivesoftware.wildfire.roster.Roster.(Roster.java:85)

at org.jivesoftware.wildfire.roster.RosterManager.deleteRoster(RosterManager.java: 122)

at org.jivesoftware.wildfire.admin.user_002ddelete_jsp._jspService(user_002ddelete _jsp.java:94)

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

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

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

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

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:813)

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Caused by: org.jivesoftware.stringprep.IDNAException: Contains non-LDH characters.

at org.jivesoftware.stringprep.IDNA.toASCII(IDNA.java:106)

at org.jivesoftware.stringprep.IDNA.toASCII(IDNA.java:53)

at org.xmpp.packet.JID.init(JID.java:363)

… 35 more[/b]

I hope someone can help me out. I have gone back to using Jive 2.3.0, but would like to be on Wildfire… Thanks a lot!


that’'s once again the “_” problem. Interesting to know that in 2.3.0 everything was fine and with 2.4.x something changed. Please see http://www.jivesoftware.org/community/thread.jspa?threadID=17305&tstart=0 or search the forum.

Maybe on dev can create an issue, to get this fixed. Seems to be a bug to me.


Hey guys,

I just checked the specifications and it seems that the “_” character is valid when present in the node part of the JID. Therefore, I’'m going to review what the server is doing. JM-520


– Gato

Thanks a million for the responses! I shall gladly wait for a fix

Could you please give a heads-up when this is fixed in a nightly build?

Hey guys,

The problem has been fixed. Today we are going to release Wildfire 2.4.3 that includes many important bug fixes so you can find this fix in today’'s release.


– Gato

Thanks a lot!!! Eagerly awaiting the release of 2.4.3

2.4.3 works like a Gem!!! Thanks a ton