Mickael Remond | 2 Feb 23:37 2006
Picon

J-EAI 1.0 beta 6 released

Hello,

I just wanted to let you know that J-EAI 1.0 beta 6 has been released.

The software is available from Process-one website:
http://www.process-one.net/en/projects/j-eai/

As a reminder, J-EAI is the first XMPP-based Enterprise Application
Integration (EAI) platform (also known as ESB, the Enterprise Service
Bus).

It is composed of several components, including an Erlang XMPP server
core (ejabberd), connectors that support Open Adaptor and XSLT, and
several distribution mechanisms, including publish and subscribe and
content-based routing.
The software includes an advance web console.

J-EAI 1.0 beta 6 now supports node collections in the pub sub module.
Nodes collection support increase the flexibility of the publish and
subscribe model.

The software is available from Process-one website:
http://www.process-one.net/en/projects/j-eai/

J-EAI can be download in source form or in precompiled and preconfigured
Linux binary format:
http://www.process-one.net/en/projects/j-eai/download.html

Best wishes,

(Continue reading)

Peter Millard | 6 Feb 16:08 2006
Picon

Trying to get ejabberd 1.0 + native pgsql

I'm trying to get ejabberd 1.0 setup to use the native postgresql
libs. I've compiled the libs and copied in the .beam files into the
ebin directory, and changed my config to use:

{auth_method, odbc}.
{odbc_server, {pgsql, "localhost", "ejabberd", "jabber", "XXX"}}.

I've also enabled the various odbc modules.. here is my list from ejabberd.cfg:
{modules,
 [
  {mod_register,   [{access, register}]},
  {mod_roster_odbc, []},
  {mod_privacy,    []},
  {mod_configure,  []},
  {mod_configure2, []},
  {mod_disco,      []},
  {mod_stats,      []},
  {mod_vcard_odbc, []},
  {mod_offline_odbc, []},
  {mod_announce,   [{access, announce}]},
  {mod_echo,       [{host, "echo.dustpuppy.corp.jabber.com"}]},
  {mod_private,    []},
  {mod_muc,        [{access, muc},
                            {access_create, muc},
                            {access_admin, muc_admin}]},
  {mod_pubsub,     []},
  {mod_time,       []},
  {mod_last_odbc,  []},
  {mod_version,    []}
 ]}.
(Continue reading)

Peter Millard | 6 Feb 18:43 2006
Picon

Trying to get ejabberd 1.0 + native pgsql

This definitely helped... I needed to copy src/ejabberd_odbc* to my
ebin directory, and my server at least started up :)  Shouldn't make
install copy these files over?? Seems like a deficiency in the
Makefile.

Now, I'm unable to do in-band registration, or create accounts using
the ejabberdctl util. When I do inband reg, I get a CONFLICT error for
some reason:

SENT: <iq id="jcl_5" type="set"><query
xmlns="jabber:iq:register"><username>pgmillard</username><password>test</password></query></iq>

RECV: <iq from='dustpuppy' id='jcl_5' type='error'><query
xmlns='jabber:iq:register'><username>pgmillard</username><password>test</password></query><error
code='409' type='cancel'><conflict
xmlns='urn:ietf:params:xml:ns:xmpp-stanzas'/></error></iq>

When I try to use the ejabberdctl util, it drops an erl_crash.dump
file onto my disk. This file is huge.. I can post relevant bits if you
want, just point me to the right place in the dump file.

pgm.

On 2/6/06, Mickael Remond <mickael.remond <at> process-one.net> wrote:
> you probably do not have the ejabberd_odbc_sup.beam. You need to
> specifically ask for compilation.
>
> Everything is included in the installer (latest version), but if you are
> compiling it by yourself, you need to specifically ask for the ODBC
> elements: The ODBC directory contains everything for external database
(Continue reading)

Staudinger, Ulrich | 6 Feb 19:34 2006

Session / mnesia replication inside ejabberd possible ?

Hi,
 
i am further evaluating ejabberd and i need to know if it is possible to replicate the mnesia database across the nodes - which is quite the opposite of what is used by default right now.... As i understand the whole architecture, there is always one mnesia database master node. In case that node is down, all other nodes inside the cluster can't message among each other (not speaking of rosters, presences, and so on).
 
Now, can i make the other nodes replicate the session table of the master node and work even without the master node  ???
 
Many thanks in advance,
Ulrich
 
 
 
 
 
 

Ulrich B. Staudinger

Senior Developer Lycos Europe Carl-Bertelsmann-Str. 21 D-33311 Gütersloh Tel. +49 (0) 5241 - 80 71 24

 
Attachment (Staudinger, Ulrich.vcf): text/x-vcard, 535 bytes
_______________________________________________
ejabberd mailing list
ejabberd <at> jabber.ru
http://lists.jabber.ru/mailman/listinfo/ejabberd
Bryan Barnes | 6 Feb 19:36 2006

Jab_simul crashing ejabberd service

Hello,

 

I am running Ejabberd 1.0.0 with Erlang 10B-8. I am using Jab_simul to benchmark the system, and am using http://tkabber.jabber.ru/files/badlop/jab_simul.xml.chat60 as a baseline for my testing. I have modified it for my server, and turned off rostering. I can run the test successfully, and as I lower the message frequency my performance degrades as I expected it to. However, I notice that during these tests my server occasionally spikes in memory usage and begins using swap space, then the jabber service refuses all further connections.

 

The test will run with no errors for about an hour with message frequency of 500 ms, then in the space of 5 minutes the memory usage will spike from 400MB to 2GB and the swap space usage will jump from 0MB to 1GB. Then all current connections are dumped and all further connections are refused. Even if I restart the ejabberd service I am unable to log in, and have to restart the server before I can connect again.

 

I am running Gentoo 2.6.14-r5 with 2GB of memory and a 1GB NIC. I have ejabberd starting as a service with the following command line:

 

ulimit -n 15000;/usr/local/bin/erl -pa /var/lib/ejabberd/ebin -sname ejabberd -s ejabberd -env ERL_MAX_PORTS 5000 -env ERL_MAX_ETS_TABLES 20000 -ejabberd config \"/etc/ejabberd/ejabberd.cfg\" log-path \"/var/log/ejabberd.log\" -sasl sasl_error_logger \{file,\"var/log/ejabberd/sasl.log\"\} -mnesia dir \"var/lib/ejabberd/spool\" +P 250000 +K true -detached

 

After troubleshooting:

 

No error messages appear on the ejabberd server, I checked the ejabberd.log, sasl.log, and the server logs. All of the errors appeared on the Jab_simul server.

 

I figured out that every time the server crashed the ejabberd server, the jab_simul server had run out of disk space. I assumed this was unrelated, but setup a cron job to delete the tmp log files. This did make the error go away, and I was able to run a simulation for 70 hours this weekend with no errors. I had 500 users with a message frequency of 100 ms using 160MB of memory.

 

I was able to recreate the error even with these settings by adding an additional 300 users, bringing me to 800 total. The job runs for 5 minutes, then I start getting Kolejka za dluga, pakiet anulowany! errors. Shortly after that I get POLLERR: Connection terminated and POLLERR: Connection refused errors.  All of these errors occur on the Jab_simul server.

 

Checking my ejabberd server, my beam service has become a zombie process, and is still running, but refuses all connections. The memory usage on the server spiked and then came back down after the beam service crashed.

 

If I dial the message frequency back to 500 ms with 800 users, it runs.

 

I don't understand the interaction between ejabberd and jab_simul enough to understand why this is happening, but I am concerned that the POLLERR errors are causing my ejabberd server to crash. I was unable to find any mention of this problem, has anything like it occurred before?

 

After even more troubleshooting:

 

I have discovered that if I restart the ejabberd service, then I am still unable to connect using a Jabber client, but that if I restart the server I am able to connect again.

 

If I leave the Jab_simul simulation running, it will reconnect to Jabber after a server restart, but not a service restart.  For all of the test data above I was using the default message in the .xml file.

 

Any assistance with this would be greatly appreciated.  Thank you.

 

 

Bryan Barnes 

 

_______________________________________________
ejabberd mailing list
ejabberd <at> jabber.ru
http://lists.jabber.ru/mailman/listinfo/ejabberd
Staudinger, Ulrich | 6 Feb 19:40 2006

AW: Jab_simul crashing ejabberd service

That basically matches my experience.
 
Everything goes fine until the server starts to swap. So, ;-), try to not bring it into swapping.
 
We have had 20k users with 1 message per 1 user in 1 minute -> 20k messages/minute on a 1GB machine for days. No problems so far.
 
The restriction that i found is the memory consumption - it goes linear up through the ceiling. With 1GB of Ram, 22k is the max for our linux machine. .
 
 
Cheers,
Ulrich
 

Von: ejabberd-bounces <at> jabber.ru [mailto:ejabberd-bounces <at> jabber.ru] Im Auftrag von Bryan Barnes
Gesendet: Montag, 6. Februar 2006 19:36
An: ejabberd <at> jabber.ru
Betreff: [ejabberd] Jab_simul crashing ejabberd service

Hello,

 

I am running Ejabberd 1.0.0 with Erlang 10B-8. I am using Jab_simul to benchmark the system, and am using http://tkabber.jabber.ru/files/badlop/jab_simul.xml.chat60 as a baseline for my testing. I have modified it for my server, and turned off rostering. I can run the test successfully, and as I lower the message frequency my performance degrades as I expected it to. However, I notice that during these tests my server occasionally spikes in memory usage and begins using swap space, then the jabber service refuses all further connections.

 

The test will run with no errors for about an hour with message frequency of 500 ms, then in the space of 5 minutes the memory usage will spike from 400MB to 2GB and the swap space usage will jump from 0MB to 1GB. Then all current connections are dumped and all further connections are refused. Even if I restart the ejabberd service I am unable to log in, and have to restart the server before I can connect again.

 

I am running Gentoo 2.6.14-r5 with 2GB of memory and a 1GB NIC. I have ejabberd starting as a service with the following command line:

 

ulimit -n 15000;/usr/local/bin/erl -pa /var/lib/ejabberd/ebin -sname ejabberd -s ejabberd -env ERL_MAX_PORTS 5000 -env ERL_MAX_ETS_TABLES 20000 -ejabberd config \"/etc/ejabberd/ejabberd.cfg\" log-path \"/var/log/ejabberd.log\" -sasl sasl_error_logger \{file,\"var/log/ejabberd/sasl.log\"\} -mnesia dir \"var/lib/ejabberd/spool\" +P 250000 +K true -detached

 

After troubleshooting:

 

No error messages appear on the ejabberd server, I checked the ejabberd.log, sasl.log, and the server logs. All of the errors appeared on the Jab_simul server.

 

I figured out that every time the server crashed the ejabberd server, the jab_simul server had run out of disk space. I assumed this was unrelated, but setup a cron job to delete the tmp log files. This did make the error go away, and I was able to run a simulation for 70 hours this weekend with no errors. I had 500 users with a message frequency of 100 ms using 160MB of memory.

 

I was able to recreate the error even with these settings by adding an additional 300 users, bringing me to 800 total. The job runs for 5 minutes, then I start getting Kolejka za dluga, pakiet anulowany! errors. Shortly after that I get POLLERR: Connection terminated and POLLERR: Connection refused errors.  All of these errors occur on the Jab_simul server.

 

Checking my ejabberd server, my beam service has become a zombie process, and is still running, but refuses all connections. The memory usage on the server spiked and then came back down after the beam service crashed.

 

If I dial the message frequency back to 500 ms with 800 users, it runs.

 

I don't understand the interaction between ejabberd and jab_simul enough to understand why this is happening, but I am concerned that the POLLERR errors are causing my ejabberd server to crash. I was unable to find any mention of this problem, has anything like it occurred before?

 

After even more troubleshooting:

 

I have discovered that if I restart the ejabberd service, then I am still unable to connect using a Jabber client, but that if I restart the server I am able to connect again.

 

If I leave the Jab_simul simulation running, it will reconnect to Jabber after a server restart, but not a service restart.  For all of the test data above I was using the default message in the .xml file.

 

Any assistance with this would be greatly appreciated.  Thank you.

 

 

Bryan Barnes 

 

_______________________________________________
ejabberd mailing list
ejabberd <at> jabber.ru
http://lists.jabber.ru/mailman/listinfo/ejabberd
Staudinger, Ulrich | 6 Feb 19:44 2006

AW: Trying to get ejabberd 1.0 + native pgsql

Hi PGM, 

If you weren't using plain text passwords, i'd say it can be that you need to use plain text passwords. 

Cheers,
Ulrich 

-----Urspr√ľngliche Nachricht-----
Von: ejabberd-bounces <at> jabber.ru [mailto:ejabberd-bounces <at> jabber.ru] Im Auftrag von Peter Millard
Gesendet: Montag, 6. Februar 2006 18:43
An: ejabberd <at> jabber.ru
Betreff: [ejabberd] Trying to get ejabberd 1.0 + native pgsql

This definitely helped... I needed to copy src/ejabberd_odbc* to my ebin directory, and my server at least
started up :)  Shouldn't make install copy these files over?? Seems like a deficiency in the Makefile.

Now, I'm unable to do in-band registration, or create accounts using the ejabberdctl util. When I do inband
reg, I get a CONFLICT error for some reason:

SENT: <iq id="jcl_5" type="set"><query
xmlns="jabber:iq:register"><username>pgmillard</username><password>test</password></query></iq>

RECV: <iq from='dustpuppy' id='jcl_5' type='error'><query xmlns='jabber:iq:register'><username>pgmillard</username><password>test</password></query><error
code='409' type='cancel'><conflict
xmlns='urn:ietf:params:xml:ns:xmpp-stanzas'/></error></iq>

When I try to use the ejabberdctl util, it drops an erl_crash.dump file onto my disk. This file is huge.. I can
post relevant bits if you want, just point me to the right place in the dump file.

pgm.

On 2/6/06, Mickael Remond <mickael.remond <at> process-one.net> wrote:
> you probably do not have the ejabberd_odbc_sup.beam. You need to 
> specifically ask for compilation.
>
> Everything is included in the installer (latest version), but if you 
> are compiling it by yourself, you need to specifically ask for the 
> ODBC
> elements: The ODBC directory contains everything for external database 
> and need to be enabled even to use the native driver:
>
> ./configure --enable-odbc
>
> Please, let us know if it helps,
_______________________________________________
ejabberd mailing list
ejabberd <at> jabber.ru
http://lists.jabber.ru/mailman/listinfo/ejabberd
Bryan Barnes | 6 Feb 20:20 2006

RE: Jab_simul crashing ejabberd service

As far as I can tell it crashes even before it uses swap, I had one test where it didn’t use swap space at all.  Were you able to find any reason for the memory usage to shoot up like that?

 

Bryan

 

From: ejabberd-bounces <at> jabber.ru [mailto:ejabberd-bounces <at> jabber.ru] On Behalf Of Staudinger, Ulrich
Sent: Monday, February 06, 2006 12:41 PM
To: ejabberd <at> jabber.ru
Subject: AW: [ejabberd] Jab_simul crashing ejabberd service

 

That basically matches my experience.

 

Everything goes fine until the server starts to swap. So, ;-), try to not bring it into swapping.

 

We have had 20k users with 1 message per 1 user in 1 minute -> 20k messages/minute on a 1GB machine for days. No problems so far.

 

The restriction that i found is the memory consumption - it goes linear up through the ceiling. With 1GB of Ram, 22k is the max for our linux machine. .

 

 

Cheers,

Ulrich

 

 

Von: ejabberd-bounces <at> jabber.ru [mailto:ejabberd-bounces <at> jabber.ru] Im Auftrag von Bryan Barnes
Gesendet: Montag, 6. Februar 2006 19:36
An: ejabberd <at> jabber.ru
Betreff: [ejabberd] Jab_simul crashing ejabberd service

Hello,

 

I am running Ejabberd 1.0.0 with Erlang 10B-8. I am using Jab_simul to benchmark the system, and am using http://tkabber.jabber.ru/files/badlop/jab_simul.xml.chat60 as a baseline for my testing. I have modified it for my server, and turned off rostering. I can run the test successfully, and as I lower the message frequency my performance degrades as I expected it to. However, I notice that during these tests my server occasionally spikes in memory usage and begins using swap space, then the jabber service refuses all further connections.

 

The test will run with no errors for about an hour with message frequency of 500 ms, then in the space of 5 minutes the memory usage will spike from 400MB to 2GB and the swap space usage will jump from 0MB to 1GB. Then all current connections are dumped and all further connections are refused. Even if I restart the ejabberd service I am unable to log in, and have to restart the server before I can connect again.

 

I am running Gentoo 2.6.14-r5 with 2GB of memory and a 1GB NIC. I have ejabberd starting as a service with the following command line:

 

ulimit -n 15000;/usr/local/bin/erl -pa /var/lib/ejabberd/ebin -sname ejabberd -s ejabberd -env ERL_MAX_PORTS 5000 -env ERL_MAX_ETS_TABLES 20000 -ejabberd config \"/etc/ejabberd/ejabberd.cfg\" log-path \"/var/log/ejabberd.log\" -sasl sasl_error_logger \{file,\"var/log/ejabberd/sasl.log\"\} -mnesia dir \"var/lib/ejabberd/spool\" +P 250000 +K true -detached

 

After troubleshooting:

 

No error messages appear on the ejabberd server, I checked the ejabberd.log, sasl.log, and the server logs. All of the errors appeared on the Jab_simul server.

 

I figured out that every time the server crashed the ejabberd server, the jab_simul server had run out of disk space. I assumed this was unrelated, but setup a cron job to delete the tmp log files. This did make the error go away, and I was able to run a simulation for 70 hours this weekend with no errors. I had 500 users with a message frequency of 100 ms using 160MB of memory.

 

I was able to recreate the error even with these settings by adding an additional 300 users, bringing me to 800 total. The job runs for 5 minutes, then I start getting Kolejka za dluga, pakiet anulowany! errors. Shortly after that I get POLLERR: Connection terminated and POLLERR: Connection refused errors.  All of these errors occur on the Jab_simul server.

 

Checking my ejabberd server, my beam service has become a zombie process, and is still running, but refuses all connections. The memory usage on the server spiked and then came back down after the beam service crashed.

 

If I dial the message frequency back to 500 ms with 800 users, it runs.

 

I don't understand the interaction between ejabberd and jab_simul enough to understand why this is happening, but I am concerned that the POLLERR errors are causing my ejabberd server to crash. I was unable to find any mention of this problem, has anything like it occurred before?

 

After even more troubleshooting:

 

I have discovered that if I restart the ejabberd service, then I am still unable to connect using a Jabber client, but that if I restart the server I am able to connect again.

 

If I leave the Jab_simul simulation running, it will reconnect to Jabber after a server restart, but not a service restart.  For all of the test data above I was using the default message in the .xml file.

 

Any assistance with this would be greatly appreciated.  Thank you.

 

 

Bryan Barnes 

 

_______________________________________________
ejabberd mailing list
ejabberd <at> jabber.ru
http://lists.jabber.ru/mailman/listinfo/ejabberd
Adam Hunt | 7 Feb 07:01 2006
Picon

ErLang XMPP client?

I just went looking for an ErLang based XMPP client and was surprised to find only one, Jabberlang.  How is it possible that with arguably the most complete and compliant XMPP server being written in ErLang that there is but one client written in the same language?

 

What are the plans for Jabberlang? Is it an actively developed project or an academic endeavor?

 

--adam

 

_______________________________________________
ejabberd mailing list
ejabberd <at> jabber.ru
http://lists.jabber.ru/mailman/listinfo/ejabberd
Staudinger, Ulrich | 7 Feb 09:00 2006

AW: Jab_simul crashing ejabberd service

Not really, we thought it's propably something like the message delivery stuff... when you pipe in too many messages per second the message queue will slowly fill up ... and if you load tool can't handle the amount of messages it will get in return, the message queue will fill up, too .... just a little bit faster.
 
And once it starts to swap the performance will drop almost immediately.
 
That's the conclusion we came up with.
 
 
Hth,Ulrich
 

Von: ejabberd-bounces <at> jabber.ru [mailto:ejabberd-bounces <at> jabber.ru] Im Auftrag von Bryan Barnes
Gesendet: Montag, 6. Februar 2006 20:21
An: ejabberd <at> jabber.ru
Betreff: RE: [ejabberd] Jab_simul crashing ejabberd service

As far as I can tell it crashes even before it uses swap, I had one test where it didn’t use swap space at all.  Were you able to find any reason for the memory usage to shoot up like that?

 

Bryan

 

From: ejabberd-bounces <at> jabber.ru [mailto:ejabberd-bounces <at> jabber.ru] On Behalf Of Staudinger, Ulrich
Sent: Monday, February 06, 2006 12:41 PM
To: ejabberd <at> jabber.ru
Subject: AW: [ejabberd] Jab_simul crashing ejabberd service

 

That basically matches my experience.

 

Everything goes fine until the server starts to swap. So, ;-), try to not bring it into swapping.

 

We have had 20k users with 1 message per 1 user in 1 minute -> 20k messages/minute on a 1GB machine for days. No problems so far.

 

The restriction that i found is the memory consumption - it goes linear up through the ceiling. With 1GB of Ram, 22k is the max for our linux machine. .

 

 

Cheers,

Ulrich

 

 

Von: ejabberd-bounces <at> jabber.ru [mailto:ejabberd-bounces <at> jabber.ru] Im Auftrag von Bryan Barnes
Gesendet: Montag, 6. Februar 2006 19:36
An: ejabberd <at> jabber.ru
Betreff: [ejabberd] Jab_simul crashing ejabberd service

Hello,

 

I am running Ejabberd 1.0.0 with Erlang 10B-8. I am using Jab_simul to benchmark the system, and am using http://tkabber.jabber.ru/files/badlop/jab_simul.xml.chat60 as a baseline for my testing. I have modified it for my server, and turned off rostering. I can run the test successfully, and as I lower the message frequency my performance degrades as I expected it to. However, I notice that during these tests my server occasionally spikes in memory usage and begins using swap space, then the jabber service refuses all further connections.

 

The test will run with no errors for about an hour with message frequency of 500 ms, then in the space of 5 minutes the memory usage will spike from 400MB to 2GB and the swap space usage will jump from 0MB to 1GB. Then all current connections are dumped and all further connections are refused. Even if I restart the ejabberd service I am unable to log in, and have to restart the server before I can connect again.

 

I am running Gentoo 2.6.14-r5 with 2GB of memory and a 1GB NIC. I have ejabberd starting as a service with the following command line:

 

ulimit -n 15000;/usr/local/bin/erl -pa /var/lib/ejabberd/ebin -sname ejabberd -s ejabberd -env ERL_MAX_PORTS 5000 -env ERL_MAX_ETS_TABLES 20000 -ejabberd config \"/etc/ejabberd/ejabberd.cfg\" log-path \"/var/log/ejabberd.log\" -sasl sasl_error_logger \{file,\"var/log/ejabberd/sasl.log\"\} -mnesia dir \"var/lib/ejabberd/spool\" +P 250000 +K true -detached

 

After troubleshooting:

 

No error messages appear on the ejabberd server, I checked the ejabberd.log, sasl.log, and the server logs. All of the errors appeared on the Jab_simul server.

 

I figured out that every time the server crashed the ejabberd server, the jab_simul server had run out of disk space. I assumed this was unrelated, but setup a cron job to delete the tmp log files. This did make the error go away, and I was able to run a simulation for 70 hours this weekend with no errors. I had 500 users with a message frequency of 100 ms using 160MB of memory.

 

I was able to recreate the error even with these settings by adding an additional 300 users, bringing me to 800 total. The job runs for 5 minutes, then I start getting Kolejka za dluga, pakiet anulowany! errors. Shortly after that I get POLLERR: Connection terminated and POLLERR: Connection refused errors.  All of these errors occur on the Jab_simul server.

 

Checking my ejabberd server, my beam service has become a zombie process, and is still running, but refuses all connections. The memory usage on the server spiked and then came back down after the beam service crashed.

 

If I dial the message frequency back to 500 ms with 800 users, it runs.

 

I don't understand the interaction between ejabberd and jab_simul enough to understand why this is happening, but I am concerned that the POLLERR errors are causing my ejabberd server to crash. I was unable to find any mention of this problem, has anything like it occurred before?

 

After even more troubleshooting:

 

I have discovered that if I restart the ejabberd service, then I am still unable to connect using a Jabber client, but that if I restart the server I am able to connect again.

 

If I leave the Jab_simul simulation running, it will reconnect to Jabber after a server restart, but not a service restart.  For all of the test data above I was using the default message in the .xml file.

 

Any assistance with this would be greatly appreciated.  Thank you.

 

 

Bryan Barnes 

 

_______________________________________________
ejabberd mailing list
ejabberd <at> jabber.ru
http://lists.jabber.ru/mailman/listinfo/ejabberd

Gmane