So here is my Jabber settings from our Hudson build server: Jabber ID: hudson-dev Password: ********* (this doesn't really matter) Initial group chats: [EMAIL PROTECTED] Server: jmsserver Port: 61222 Expose Presence: true
ActiveMQ is running on the server 'jmsserver' and the XMPP protocol is listening on port 61222. When the Jabber plug-in running on Hudson connects, it will join a group chat named 'hudsontalk'. It knows that this is a group chat because of the suffix of '@conference'. For the build job configuration, I tell the plugin to broadcast notifications to "[EMAIL PROTECTED]". If I wanted to send to a particular person, I would use a destination such as "[EMAIL PROTECTED]". This would send a message directly to me if my IM client were connected to the jmsserver. I then configure Pidgin 2.4.3 account settings to connect with the following settings: In the Account dialog on the basic tab in the Login Options area, set the Protocol to be XMPP. Enter your username (jgomes for me), domain settings and whatever Password you want. I left the User Options area blank. On the Advanced tab, I have the following settings: XMPP Options - Require SSL/TLS: unchecked Force old (port 5223) SSL: unchecked Allow plantext auth over unencrypted streams: checked Connect port: 61222 Connect server: jmsserver File transfer proxies: proxy.jabber.org:7777 Proxy type: Use Global Proxy Settings With the client account settings created. From the main window, I select Buddies -> Join a Chat. Set the following values: Account: (Choose the account that was created above) Room: hudsontalk Server: jmsserver Handle: jgomes Password: (doesn't matter) Then click on Join button. This sets up both ends of the communication with ActiveMQ operating as the instant messaging server. I don't know if that will help or not, but maybe it will get you going with some ideas on how to approach using XMPP with ActiveMQ. Best, Jim semog wrote: > > I use Pidgin connected to ActiveMQ. I then have our Hudson build > server publish its build results over XMPP to ActiveMQ and I get the > instant message sent to my Pidgin client. Pretty slick. > > I can't send screen shots right now since I am on my web-phone. > However, ActiveMQ does work well as a chat server over XMPP. I am > using 5.2.0 and am about to update to today's build of 5.3-SNAPSHOT. > > On 11/25/08, jeevanpd <[EMAIL PROTECTED]> wrote: >> >> >> I also spent good couple of hours to sort this out but no luck yet.. >> Anybody >> succeeded? >> >> >> Thanks, >> Jeevan >> >> >> Michael Franz wrote: >>> >>> I don't think it works anymore. At least it does not work as >>> documented. >>> I posted about my issues here. >>> http://www.nabble.com/ActiveMQ-and-XMPP-not-functioning-tt16147069ef2356.html#a17536302 >>> >>> >>> Graham Leggett wrote: >>>> >>>> Hi all, >>>> >>>> I have spent over a day trying to get a jabber client (any jabber >>>> client) to successfully connect to activemq's XMPP connector, either >>>> with or without SSL, and so far I have got nowhere. >>>> >>>> I know that activemq is listening on an XMPP port, because when I >>>> telnet >>>> there, I get an XMPP header. So far so good. >>>> >>>> Apple's iChat refuses to connect with the message "Could not connect to >>>> Jabber". iChat feels it unnecessary to give any more detail than that, >>>> so I gave up on iChat and tried Spark. >>>> >>>> The Spark login sequence is too unreliable to draw any clear >>>> conclusions >>>> as to whether problems occur on the server or the client. Spark goes >>>> through all the motions of allowing you to log in, while simultaneously >>>> the server logs and exception complaining that login failed. Attempts >>>> to >>>> create a channel (which should in theory cause a queue to be created) >>>> are ignored. >>>> >>>> Abandoning Spark as a lost cause, and trying PSI instead, gives me >>>> errors that are a little more sensible. This time round the error "No >>>> appropriate mechanism available for given security settings (eg SASL >>>> library too weak, or plaintext authentication not enabled). Nothing is >>>> logged on the activemq side giving any clue as to why the login attempt >>>> failed. >>>> >>>> When I read that activemq supports XMPP, at the very least I expect the >>>> following to be true: >>>> >>>> - SSL is supported >>>> - Login is supported >>>> >>>> In the case of activemq, I am not seeing any evidence that either of >>>> these features are supported, which to me means that XMPP *isn't* >>>> supported by activemq properly at all. >>>> >>>> Can somebody confirm whether XMPP is used by anybody in a real live >>>> situation at all? The ability to look inside your queue server with a >>>> chat client and see what your system is (or isn't) doing is a killer >>>> feature in any message driven application, however it looks like the >>>> XMPP implementation inside activemq was never completed. >>>> >>>> Can anyone shed any light as to whether what I am trying to achieve is >>>> even achievable at all? >>>> >>>> Regards, >>>> Graham >>>> -- >>>> >>>> >>>> >>> >>> >> >> -- >> View this message in context: >> http://www.nabble.com/XMPP%3A-does-it-work-for-anybody--tp17709952p20682151.html >> Sent from the ActiveMQ - User mailing list archive at Nabble.com. >> >> > > -- View this message in context: http://www.nabble.com/XMPP%3A-does-it-work-for-anybody--tp17709952p20691274.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
