Re: XMPP 2.15.0 vs. 2.15.1 failing
Hi Have you looked at the source code changes in camel-xmpp 2.15.0 and 2.15.1 and also about any JAR upgrades. The best clue would be in any of those changes. On Fri, Apr 3, 2015 at 12:18 PM, Christopher Piggott cpigg...@gmail.com wrote: Hi, Earlier this evening I upgraded my camel project from 2.15.0 to 2.15.1 with no other code changes, and suddenly I was unable to connect to my XMPP server. The error I got was roughly this: SASLauthentication failed using mechanism DIGEST-MD5: I did some brief troubleshooting but was not able to solve the problem, so I just dropped back to 2.15.0. Searching various mailing lists I found a number of people complaining of the same problem; a ton of bad/unhelpful advice; and a good amount of skepticism that it's even really a problem. It certainly appears to be one to me. Permissions, keys, etc. dealing with this kind of stuff (including self-signed certificates on openfire servers) has always been pretty ugly in Java anyway. Most of the time I can fix things by adding various trust providers, or screwing around with keytool - but it's pretty hideous. I am following advice from the camel xmpp page and posting this to the mailing list rather than filing a bug. If someone believes this really is a bug let me know and I'll be happy to fill out the ticket. Or, of course, if you have some workaround that will allow this to continue working, that's great too. Despite the fact that it's trying to use digest, it's still inside of an SSL so I'm not overly concerned about it. (I just don't want to spend my life screwing around working around openfire). -- Claus Ibsen - Red Hat, Inc. Email: cib...@redhat.com Twitter: davsclaus Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen hawtio: http://hawt.io/ fabric8: http://fabric8.io/
Re: XMPP 2.15.0 vs. 2.15.1 failing
No, I haven't, and you're right - I should have. I'm an easily distracted type though and I'm trying to get some ZCL stuff pushed to maven central asap. I use camel for a ton of testing of that kind of thing, and shortly I'll be pushing out an xbee camel component I wrote (and am now testing). Sorry for the lame answer. If nobody knows what's going on here off the top of their heads I'll dig into it in a little bit and report back. On Fri, Apr 3, 2015 at 6:40 AM, Claus Ibsen claus.ib...@gmail.com wrote: Hi Have you looked at the source code changes in camel-xmpp 2.15.0 and 2.15.1 and also about any JAR upgrades. The best clue would be in any of those changes. On Fri, Apr 3, 2015 at 12:18 PM, Christopher Piggott cpigg...@gmail.com wrote: Hi, Earlier this evening I upgraded my camel project from 2.15.0 to 2.15.1 with no other code changes, and suddenly I was unable to connect to my XMPP server. The error I got was roughly this: SASLauthentication failed using mechanism DIGEST-MD5: I did some brief troubleshooting but was not able to solve the problem, so I just dropped back to 2.15.0. Searching various mailing lists I found a number of people complaining of the same problem; a ton of bad/unhelpful advice; and a good amount of skepticism that it's even really a problem. It certainly appears to be one to me. Permissions, keys, etc. dealing with this kind of stuff (including self-signed certificates on openfire servers) has always been pretty ugly in Java anyway. Most of the time I can fix things by adding various trust providers, or screwing around with keytool - but it's pretty hideous. I am following advice from the camel xmpp page and posting this to the mailing list rather than filing a bug. If someone believes this really is a bug let me know and I'll be happy to fill out the ticket. Or, of course, if you have some workaround that will allow this to continue working, that's great too. Despite the fact that it's trying to use digest, it's still inside of an SSL so I'm not overly concerned about it. (I just don't want to spend my life screwing around working around openfire). -- Claus Ibsen - Red Hat, Inc. Email: cib...@redhat.com Twitter: davsclaus Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen hawtio: http://hawt.io/ fabric8: http://fabric8.io/
Re: XMPP 2.15.0 vs. 2.15.1 failing
I just find the recent change[1] by using the gitk components/camel-xmpp” command. The work around could be change the smack version to 4.0.6. [1]https://issues.apache.org/jira/browse/CAMEL-8520 -- Willem Jiang Red Hat, Inc. Web: http://www.redhat.com Blog: http://willemjiang.blogspot.com (English) http://jnn.iteye.com (Chinese) Twitter: willemjiang Weibo: 姜宁willem On April 3, 2015 at 6:48:24 PM, Christopher Piggott (cpigg...@gmail.com) wrote: No, I haven't, and you're right - I should have. I'm an easily distracted type though and I'm trying to get some ZCL stuff pushed to maven central asap. I use camel for a ton of testing of that kind of thing, and shortly I'll be pushing out an xbee camel component I wrote (and am now testing). Sorry for the lame answer. If nobody knows what's going on here off the top of their heads I'll dig into it in a little bit and report back. On Fri, Apr 3, 2015 at 6:40 AM, Claus Ibsen wrote: Hi Have you looked at the source code changes in camel-xmpp 2.15.0 and 2.15.1 and also about any JAR upgrades. The best clue would be in any of those changes. On Fri, Apr 3, 2015 at 12:18 PM, Christopher Piggott wrote: Hi, Earlier this evening I upgraded my camel project from 2.15.0 to 2.15.1 with no other code changes, and suddenly I was unable to connect to my XMPP server. The error I got was roughly this: SASLauthentication failed using mechanism DIGEST-MD5: I did some brief troubleshooting but was not able to solve the problem, so I just dropped back to 2.15.0. Searching various mailing lists I found a number of people complaining of the same problem; a ton of bad/unhelpful advice; and a good amount of skepticism that it's even really a problem. It certainly appears to be one to me. Permissions, keys, etc. dealing with this kind of stuff (including self-signed certificates on openfire servers) has always been pretty ugly in Java anyway. Most of the time I can fix things by adding various trust providers, or screwing around with keytool - but it's pretty hideous. I am following advice from the camel xmpp page and posting this to the mailing list rather than filing a bug. If someone believes this really is a bug let me know and I'll be happy to fill out the ticket. Or, of course, if you have some workaround that will allow this to continue working, that's great too. Despite the fact that it's trying to use digest, it's still inside of an SSL so I'm not overly concerned about it. (I just don't want to spend my life screwing around working around openfire). -- Claus Ibsen - Red Hat, Inc. Email: cib...@redhat.com Twitter: davsclaus Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen hawtio: http://hawt.io/ fabric8: http://fabric8.io/
XMPP 2.15.0 vs. 2.15.1 failing
Hi, Earlier this evening I upgraded my camel project from 2.15.0 to 2.15.1 with no other code changes, and suddenly I was unable to connect to my XMPP server. The error I got was roughly this: SASLauthentication failed using mechanism DIGEST-MD5: I did some brief troubleshooting but was not able to solve the problem, so I just dropped back to 2.15.0. Searching various mailing lists I found a number of people complaining of the same problem; a ton of bad/unhelpful advice; and a good amount of skepticism that it's even really a problem. It certainly appears to be one to me. Permissions, keys, etc. dealing with this kind of stuff (including self-signed certificates on openfire servers) has always been pretty ugly in Java anyway. Most of the time I can fix things by adding various trust providers, or screwing around with keytool - but it's pretty hideous. I am following advice from the camel xmpp page and posting this to the mailing list rather than filing a bug. If someone believes this really is a bug let me know and I'll be happy to fill out the ticket. Or, of course, if you have some workaround that will allow this to continue working, that's great too. Despite the fact that it's trying to use digest, it's still inside of an SSL so I'm not overly concerned about it. (I just don't want to spend my life screwing around working around openfire).
