Details
-
Bug
-
Resolution: Fixed
-
Low
-
2.6.1
-
None
-
Bamboo Version Information
Version:
2.6.1
Build Number:
1902
Build Date:
6/4/10Java / JVM Information
Java Version:
1.6.0_20
Java Vendor:
Sun Microsystems Inc.
JVM Spec. Version:
1.0
JVM Spec. Vendor:
Sun Microsystems Inc.
JVM Version:
16.3-b01
JVM Vendor:
Sun Microsystems Inc.
JVM Name:
Java HotSpot(TM) 64-Bit Server VM
JRE Version:
1.6.0_20-b02
JRE Name:
Java(TM) SE Runtime Environmentejabberd 2.1.3
Bamboo Version Information Version: 2.6.1 Build Number: 1902 Build Date: 6/4/10 Java / JVM Information Java Version: 1.6.0_20 Java Vendor: Sun Microsystems Inc. JVM Spec. Version: 1.0 JVM Spec. Vendor: Sun Microsystems Inc. JVM Version: 16.3-b01 JVM Vendor: Sun Microsystems Inc. JVM Name: Java HotSpot(TM) 64-Bit Server VM JRE Version: 1.6.0_20-b02 JRE Name: Java(TM) SE Runtime Environment ejabberd 2.1.3
Description
Since upgrading our eJabberd application to 2.1.3 Bamboo has been unable to connect to the eJabberd XMPP service. The "Test" function returns the following error:
XMPP Error encountered while attempting to send message as [bamboo] using [im.xxxxxx.com/Bamboo], error message is: service-unavailable(503)
Looking at errors through the logfile again - including errors related to gss.conf - and I came to the conclusion that the XMPP client Bamboo is using is trying to negotiate authentication that is leading to an authentication mechanism which is not supported by our ejabberd 2.1.3 server.
We did some research and found that ejabberd had addressed a few spec-related issues such as this in recent versions of ejabberd 2.1.3:
https://support.process-one.net/browse/EJAB-1132
- "SASL PLAIN authentication message not compliant with RFC4616"
The quick summary of the issue is that the XMPP specification has some areas that are vague and open to interpretation. Unless clients and servers interpret the specification the same way - interop problems can exist.
This particular issue was fixed in ejabberd 2.1.2. We reverted our ejabberd installation to 2.0.5 and Bamboo is working again immediately. This tells us that some fix in ejabberd 2.1.0, 2.1.1, 2.1.2, or 2.1.3, possibly the one refered to above, has lead to an interop problem with the XMPP client used in Bamboo.
Pidgin, Exodus, and various other XMPP clients are working fine with our ejabberd 2.1.3 server. This tells us that it is something particular about the XMPP client Bamboo is using. Also, ejabberd is one of the main open source Jabber implementations available with one of the largest user bases of XMPP clients. Putting these together tells us that the XMPP client Bamboo is using is doing something odd. Perhaps not wrong - but at least different from the other clients out there that are working fine.
This issue was initially reported here:
https://support.atlassian.com/browse/BSP-3056