Wildfire 3.0.0 Beta released

Openfire Openfire Support
1

How come there is no such thread here or in news? So i really must stick with my web watching program to be up to date I know this is beta and probably there is not much changes since last nightlies, but this is a release. Same with Spark. I just like the idea, when developers are posting thread about new release and you can put all issues you came up with here.

Ok. New Admin Console design Cool. Though i liked old gradient more. A bit softer colors is better, imho And login screen, could be bit bit better

Plugins page. Really nice, now i dont have to download and install them manually. Though i’'m using mainly 2 plugins and they are not updating very often. Maybe plugins page should refresh after plugin upgrade. Cause now to see changes i have to do this manually.

And errors of course I have upgraded some old nightly (3.0.0 Alpha), just overwrited as always. It was starting very long and finally gave me that:

at java.lang.reflect.Method.invoke(Unknown Source)

at com.exe4j.runtime.LauncherEngine.launch(Unknown Source)

at com.exe4j.runtime.WinLauncher.main(Unknown Source)

2006.06.21 23:30:16 [org.jivesoftware.database.EmbeddedConnectionProvider.getConnection(EmbeddedCon nectionProvider.java:46)

] Error: EmbeddedConnectionProvider.getConnection() wascalled before the internal pool has been initialized.

2006.06.21 23:30:16 [org.jivesoftware.database.DbConnectionManager.getConnection(DbConnectionManage r.java:92)

] WARNING: ConnectionManager.getConnection() failed to obtain a connection.

2006.06.21 23:30:16 [org.jivesoftware.wildfire.XMPPServer.verifyDataSource(XMPPServer.java:614)

] Database could not be accessed

java.lang.NullPointerException

at org.jivesoftware.wildfire.XMPPServer.verifyDataSource(XMPPServer.java:604)

at org.jivesoftware.wildfire.XMPPServer.start(XMPPServer.java:366)

at org.jivesoftware.wildfire.XMPPServer.(XMPPServer.java:144)

at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)

at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)

at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)

at java.lang.reflect.Constructor.newInstance(Unknown Source)

at java.lang.Class.newInstance0(Unknown Source)

at java.lang.Class.newInstance(Unknown Source)

at org.jivesoftware.wildfire.starter.ServerStarter.start(ServerStarter.java:88)

at org.jivesoftware.wildfire.starter.ServerStarter.main(ServerStarter.java:49)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)

at java.lang.reflect.Method.invoke(Unknown Source)

at com.exe4j.runtime.LauncherEngine.launch(Unknown Source)

at com.exe4j.runtime.WinLauncher.main(Unknown Source)

Caused by: java.lang.NullPointerException

at org.jivesoftware.wildfire.XMPPServer.verifyDataSource(XMPPServer.java:604)

… 16 more

Second time it started ok and works good so far.

2

And i cant find here JM-666 instructions to turn off connection manager.

3

I also thought the old admin console UI was nicer, I’'m afraid. It was cleaner, fresher.

4

Hey wroot,

In the admin console you will find a “Connection Manager” menu item in the main page. By default, the service is disabled. From that page you can enable/disable the service, specify the port to use and a shared secret.

Regards,

– Gato

5

3.0.0beta installed and running! no problems with the directory users or anything so far

6

How come there is no such thread here or in news?

Sorry about that! I think we were so tired after getting the releases out that we needed a bit of time to get organized and make the official announcements. Thanks for posting this thread.

Ok. New Admin Console design Cool. Though i liked

old gradient more. A bit softer colors is better,

imho And login screen, could be bit bit better

Thanks for the feedback. We’‘re still tinkering with the design and the login screen is definitely not done yet. One idea I really like is the ability to choose different templates for the admin console. I’'m personally lobbying for a Battlestar Galactica theme. Heh heh.

Plugins page. Really nice, now i dont have to

download and install them manually. Though i’'m using

mainly 2 plugins and they are not updating very

often. Maybe plugins page should refresh after plugin

upgrade. Cause now to see changes i have to do this

manually.

Yep, we’‘re still not quite done with those pages. I’‘m attaching some screenshots to show you the UI ideas we’'re thinking about.

Regards,

Matt

7

Gato, thanks, overlooking as always Just some time ago i remember there was only a system property for that. GUI is better

And i have found Manage Updates page now. Notifies for admin will be forwarded to contacts specified in xmpp.forward.admins property i presume?

Matt, different templates for Admin Console would be great. And you can leave some Classic template with old design for those who are addicted already

Screenshots looks great too.

8

Hey guys,

I know you’‘ll hate to hear this question, but any idea when the final version of 3.0 will be released? I’'ve looked at the features and would love to move up to 3.0 from our current 2.6.x install.

Thanks!

Jay

9

Jay,

Assuming the beta goes relatively well, the final release should be out in less than two weeks.

Thanks,

Matt

10

Hey Matt,

Thanks, that should work well for us.

Jay

11

Hello!

Although both of these JMs are registered under “unscheduled” and not 3.0 I think it would be great to see which road you anna go with the two conflicting JM-691 and JM-701?

691 says the docs are wrong

701 says the feature is buggy

Besides this 3.0 looks very promising, thank you for your hard work!

Starry

12

Thanks for reminding. JM-691 is interesting (the same is the last one in JM-701). Some time ago i have tested this with some old nightly and it seemed to work ok with Exodus. Users from the same group wasnt seeing each other when this group wasnt selected in the list of groups. But today i hit that bug. Just had to restart the server. And now Exodus is showing users from the group it belongs to.

As documentation says “Show group in members’’ rosters of these groups - the group will display only in the rosters of the groups you list in the field provided.” it is a bug in shared groups behaviour.

13

Hey guys,

The chat archiving feature in Enterprise looks really interesting. Will that work with the group chat? Only registered WF users will participate in our group chat. Can we get a chat transcript for the entire room from this interface?

Thanks!

Jay

14

Jay,

The archiving feature currently doesn’‘t work with group chats. We’'re planning on extending it to group chat for a future release, but decided to tackle a smaller feature area for the first release. Automated chat transcripts is another cool (and related) feature idea.

Regards,

-Matt

15

i’‘ve tested upgrading wildfire 2.6.2 to 3.0 beta, but the database upgrade doesn’'t work:

2006.06.23 11:00:23 org.jivesoftware.wildfire.pubsub.PubSubPersistenceManager.loadNodes(PubSubPersis tenceManager.java:513)

org.postgresql.util.PSQLException: ERROR: relation “pubsubnodejids” does not exist

at org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl .java:1512)

at org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java: 1297)

at org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:188)

at org.postgresql.jdbc2.AbstractJdbc2Statement.execute(AbstractJdbc2Statement.java :430)

at org.postgresql.jdbc2.AbstractJdbc2Statement.executeWithFlags(AbstractJdbc2State ment.java:346)

at org.postgresql.jdbc2.AbstractJdbc2Statement.executeQuery(AbstractJdbc2Statement .java:250)

at org.jivesoftware.wildfire.pubsub.PubSubPersistenceManager.loadNodes(PubSubPersi stenceManager.java:461)

at org.jivesoftware.wildfire.pubsub.PubSubModule.initialize(PubSubModule.java:389)

at org.jivesoftware.wildfire.XMPPServer.initModules(XMPPServer.java:476)

at org.jivesoftware.wildfire.XMPPServer.start(XMPPServer.java:371)

at org.jivesoftware.wildfire.XMPPServer.(XMPPServer.java:144)

at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)

at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)

at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)

at java.lang.reflect.Constructor.newInstance(Unknown Source)

at java.lang.Class.newInstance0(Unknown Source)

at java.lang.Class.newInstance(Unknown Source)

at org.jivesoftware.wildfire.starter.ServerStarter.start(ServerStarter.java:88)

at org.jivesoftware.wildfire.starter.ServerStarter.main(ServerStarter.java:49)

~/wildfire/bin$ ./wildfire.sh start

…

Found old database version 7 for wildfire. Upgrading to version 9…

Database update successful.

Wildfire 3.0.0 Beta

next time start:

~/wildfire/bin$ ./wildfire.sh start

…

Found old database version 7 for wildfire. Upgrading to version 9…

Database update successful.

Wildfire 3.0.0 Beta

I’'m using PostgreSQL 8.1.4 on debian etch.

Executing the update scripts by hand works fine.

16

another probem are outgoing s2s connections.

2006.06.23 11:33:16 org.jivesoftware.wildfire.server.OutgoingServerSession.createOutgoingSession(Out goingServerSession.java:259) Error trying to connect to remote server: freenet.de(DNS lookup: freenet.de:5269)

java.net.ConnectException: Connection refused

at java.net.PlainSocketImpl.socketConnect(Native Method)

at java.net.PlainSocketImpl.doConnect(Unknown Source)

at java.net.PlainSocketImpl.connectToAddress(Unknown Source)

at java.net.PlainSocketImpl.connect(Unknown Source)

at java.net.SocksSocketImpl.connect(Unknown Source)

at java.net.Socket.connect(Unknown Source)

at org.jivesoftware.wildfire.server.OutgoingServerSession.createOutgoingSession(Ou tgoingServerSession.java:254)

at org.jivesoftware.wildfire.server.OutgoingServerSession.authenticateDomain(Outgo ingServerSession.java:183)

at org.jivesoftware.wildfire.server.OutgoingSessionPromise.createSessionAndSendPac ket(OutgoingSessionPromise.java:130)

at org.jivesoftware.wildfire.server.OutgoingSessionPromise.access$300(OutgoingSess ionPromise.java:40)

at org.jivesoftware.wildfire.server.OutgoingSessionPromise$1$1.run(OutgoingSession Promise.java:95)

at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)

at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)

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

But the hostname ist jabber.freenet.de and not freenet.de, same with jabber.ccc.de -> ccc.de

or google:

Error trying to connect to remote server: googlemail.com(DNS lookup: googlemail.com:5269)

java.net.SocketTimeoutException: connect timed out

at java.net.PlainSocketImpl.socketConnect(Native Method)

at java.net.PlainSocketImpl.doConnect(Unknown Source)

at java.net.PlainSocketImpl.connectToAddress(Unknown Source)

at java.net.PlainSocketImpl.connect(Unknown Source)

at java.net.SocksSocketImpl.connect(Unknown Source)

at java.net.Socket.connect(Unknown Source)

at org.jivesoftware.wildfire.server.OutgoingServerSession.createOutgoingSession(Ou tgoingServerSession.java:254)

at org.jivesoftware.wildfire.server.OutgoingServerSession.authenticateDomain(Outgo ingServerSession.java:140)

at org.jivesoftware.wildfire.server.OutgoingSessionPromise.createSessionAndSendPac ket(OutgoingSessionPromise.java:130)

at org.jivesoftware.wildfire.server.OutgoingSessionPromise.access$300(OutgoingSess ionPromise.java:40)

at org.jivesoftware.wildfire.server.OutgoingSessionPromise$1$1.run(OutgoingSession Promise.java:95)

at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)

at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)

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

another example:

2006.06.23 11:46:16 OS - Trying to connect to ru:5269(DNS lookup: ru:5269)

2006.06.23 11:46:16 Error sending packet to remote server:

iD8DBQBEm7GnCW8YNGJ9dh0RAr6pAJ9up3Nvd7JQoh4VSWE7k2OPKSaACfaUkB zDFaKfXaxOy5flyaFZvXJQ= =Kef

java.lang.Exception: Failed to create connection to remote server

at org.jivesoftware.wildfire.server.OutgoingSessionPromise.createSessionAndSendPac ket(OutgoingSessionPromise.java:143)

at org.jivesoftware.wildfire.server.OutgoingSessionPromise.access$300(OutgoingSess ionPromise.java:40)

at org.jivesoftware.wildfire.server.OutgoingSessionPromise$1$1.run(OutgoingSession Promise.java:95)

at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)

at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)

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

Message was edited by: dna

17

The s2s DNS problem was a problem with the powerdns recursor, it is now fixed:

http://mailman.powerdns.com/pipermail/pdns-users/2006-June/003584.html

18

Hey dna,

Both Wildfire and Smack where modified to search for records of type SRV and class IN. This should work with all DNS servers so the problem should be fixed now. The bug fixes will be available with the next nightly build.

Thanks,

– Gato

19

Since Version 3.0 beta i’'ve the following exceptions in my log:

2006.06.25 12:53:50 Error creating secured outgoing session to remote server: jabber.org(DNS lookup: jabber.org:5269)

org.xmlpull.v1.XmlPullParserException: could not determine namespace bound to element prefix stream (position: START_DOCUMENT seen stream:error… @1:14)

at org.xmlpull.mxp1.MXParser.parseStartTag(MXParser.java:1816)

at org.xmlpull.mxp1.MXParser.parseProlog(MXParser.java:1479)

at org.jivesoftware.wildfire.net.MXParser.nextImpl(MXParser.java:331)

at org.xmlpull.mxp1.MXParser.next(MXParser.java:1093)

at org.jivesoftware.wildfire.server.OutgoingServerSession.createOutgoingSession(Ou tgoingServerSession.java:288)

at org.jivesoftware.wildfire.server.OutgoingServerSession.authenticateDomain(Outgo ingServerSession.java:140)

at org.jivesoftware.wildfire.server.OutgoingSessionPromise.createSessionAndSendPac ket(OutgoingSessionPromise.java:130)

at org.jivesoftware.wildfire.server.OutgoingSessionPromise.access$300(OutgoingSess ionPromise.java:40)

at org.jivesoftware.wildfire.server.OutgoingSessionPromise$1$1.run(OutgoingSession Promise.java:95)

at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)

at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)

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

2006.06.25 12:53:52 Error creating secured outgoing session to remote server: jabber.ru(DNS lookup: jabber.ru:5269)

org.xmlpull.v1.XmlPullParserException: could not determine namespace bound to element prefix stream (position: START_DOCUMENT seen stream:error… @1:14)

at org.xmlpull.mxp1.MXParser.parseStartTag(MXParser.java:1816)

at org.xmlpull.mxp1.MXParser.parseProlog(MXParser.java:1479)

at org.jivesoftware.wildfire.net.MXParser.nextImpl(MXParser.java:331)

at org.xmlpull.mxp1.MXParser.next(MXParser.java:1093)

at org.jivesoftware.wildfire.server.OutgoingServerSession.createOutgoingSession(Ou tgoingServerSession.java:288)

at org.jivesoftware.wildfire.server.OutgoingServerSession.authenticateDomain(Outgo ingServerSession.java:140)

at org.jivesoftware.wildfire.server.OutgoingSessionPromise.createSessionAndSendPac ket(OutgoingSessionPromise.java:130)

at org.jivesoftware.wildfire.server.OutgoingSessionPromise.access$300(OutgoingSess ionPromise.java:40)

at org.jivesoftware.wildfire.server.OutgoingSessionPromise$1$1.run(OutgoingSession Promise.java:95)

at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)

at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)

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

20

Hey dna,

That is an ejabberd problem that has been reported to ejabberd devs. The reason why you are getting it is that Wildfire is trying to use secure s2s connections and ejabberd is not properly handling the namespace being included in the initial stream header. Moreover, ejabberd is sending a stream:error without opening a stream header before. To avoid this problem when connecting to an ejabberd server just log into the admin console and click on security settings, from that page disable TLS for s2s.

Regards,

– Gato