RE: Salesforce streaming issue
Hi Thanks I got the details. I may try it out tomorrow after ci/cd does the build. Thanks and Regards, Hemang Ajmera -Original Message- From: Claus Ibsen Sent: 18 December 2020 18:50 To: users@camel.apache.org Cc: Jean-Baptiste Onofre ; Dev ; Andy Stebbing Subject: Re: Salesforce streaming issue EXTERNAL SENDER: Do not click any links or open any attachments unless you trust the sender and know the content is safe. EXPÉDITEUR EXTERNE:Ne cliquez sur aucun lien et n’ouvrez aucune pièce jointe à moins qu’ils ne proviennent d’un expéditeur fiable, ou que vous ayez l'assurance que le contenu provient d'une source sûre. There are standard apache snapshot maven repos, you can find details from ASF website. But mind that it takes overnight for CI server to build and publish to it - so its often quicker to build yourself. On Fri, Dec 18, 2020 at 2:18 PM Ajmera, Hemang C wrote: > > Hi >Can you please share maven repo setting using which I can directly use > snapshot version of compiled jar file. I found compiling camel was a big task > which I want to avoid. I will also give it a try. If possible springboot > camel-salesforce-starter will be preferred, then I can try running the > production code directly with snapshot version in lower environment. > > > Thanks and Regards, > Hemang Ajmera > > > -Original Message- > From: Jean-Baptiste Onofre > Sent: 18 December 2020 18:24 > To: Dev > Cc: users@camel.apache.org; Andy Stebbing ; > Ajmera, Hemang C > Subject: Re: Salesforce streaming issue > > > EXTERNAL SENDER: Do not click any links or open any attachments unless you > trust the sender and know the content is safe. > EXPÉDITEUR EXTERNE:Ne cliquez sur aucun lien et n’ouvrez aucune pièce > jointe à moins qu’ils ne proviennent d’un expéditeur fiable, ou que vous ayez > l'assurance que le contenu provient d'une source sûre. > > Thanks for the update Zoran. > > I gonna take a look and test. > > Regards > JB > > > Le 18 déc. 2020 à 13:12, Zoran Regvart a écrit : > > > > Hi Cameleers, > > this has been targeted for releases 3.7.1 and 3.8.0, if you can, it > > would be of great help to test this before we release. > > > > zoran > > > > On Wed, Dec 16, 2020 at 3:44 PM Zoran Regvart wrote: > >> > >> Hi Cameleers, > >> I've created a PR[1], which I think fixes the problem, I encourage > >> folk to provide feedback and test on your end if possible. > >> > >> I've tested with the `SubscriptionHelperIntegrationTest`. And manually by: > >> > >> 1/ Starting a streaming app with the route: > >> > >> from("salesforce:Account?sObjectName=Account&rawPayload=true&sObjec > >> tQ > >> uery=SELECT > >> Id, Name FROM Account")¬ > >> .log(LoggingLevel.INFO, "salesforce", "${body}") > >> > >> 2/ creating an Account record, and noticing the output in the > >> log/console from the `log` component > >> > >> 3/ rejecting traffic to Salesforce using iptables: > >> $ iptables -A OUTPUT -d 85.222.0.0/16 -j REJECT > >> > >> 4/ disrupting the established connection using ss: > >> $ ss -K dst 85.222.154.145 # or whatever IP was in the output of > >> lsof -p $PID -a -i 6 -n > >> > >> 5/ noticing the messages in the log with back-off like: > >> > >> Connect failure: {failure={exception=java.io.EOFException: > >> HttpConnectionOverHTTP@45d7880c::DecryptedEndPoint@621bd87d{l=/192.168.1.76:43432,r=eu18.salesforce.com/85.222.155.145:443... > >> Restarting on unexpected disconnect from Salesforce... > >> Handshake failure: {failure={exception=java.net.ConnectException: > >> Connection refused, message={... > >> Handshake failure: {failure={exception=java.net.ConnectException: > >> Connection refused, message={... > >> > >> 5/ allowing traffic to Salesforce (removing the rule): > >> $ iptables -D OUTPUT 4 # happens to be 4th rule that I've added in > >> 3/, check with iptables -L OUTPUT --line-numbers > >> > >> 6/ seeing consumer reconnecting: > >> > >> Set Replay extension to replay from `-1` for channel > >> `/topic/Account` Subscribing to channel /topic/Account... > >> Successfully restarted! > >> Subscribed to channel /topic/Account > >> > >> 7/ creating a new Account record, and seeing the message logged > >> from the `log` component. > >> > >> zoran > >> > >> [1] > >> https://urldefense.com/v3/__https://github.com/apache/camel/pull/47 > >> 78 > >> __;!!AaIhyw!_Vo0r3EhR2gpAnmiN1U-XwM3Z9ZaLIrFENHuHqbcLNhiY9FIm8ffp1i > >> 8c > >> EVEwBZG$ > >> > >> -- > >> Zoran Regvart > > > > > > > > -- > > Zoran Regvart > -- Claus Ibsen - https://urldefense.com/v3/__http://davsclaus.com__;!!AaIhyw!5kJ7zs-QkcZ5_SZ9pvMUap5xAsp64UeZDINCVbIww8HcBME_pFACTMnc0mauqbia$ @davsclaus Camel in Action 2: https://urldefense.com/v3/__https://www.manning.com/ibsen2__;!!AaIhyw!5kJ7zs-QkcZ5_SZ9pvMUap5xAsp64UeZDINCVbIww8HcBME_pFACTMnc0kghjrc4$
Re: Salesforce streaming issue
There are standard apache snapshot maven repos, you can find details from ASF website. But mind that it takes overnight for CI server to build and publish to it - so its often quicker to build yourself. On Fri, Dec 18, 2020 at 2:18 PM Ajmera, Hemang C wrote: > > Hi >Can you please share maven repo setting using which I can directly use > snapshot version of compiled jar file. I found compiling camel was a big task > which I want to avoid. I will also give it a try. If possible springboot > camel-salesforce-starter will be preferred, then I can try running the > production code directly with snapshot version in lower environment. > > > Thanks and Regards, > Hemang Ajmera > > > -Original Message- > From: Jean-Baptiste Onofre > Sent: 18 December 2020 18:24 > To: Dev > Cc: users@camel.apache.org; Andy Stebbing ; Ajmera, > Hemang C > Subject: Re: Salesforce streaming issue > > > EXTERNAL SENDER: Do not click any links or open any attachments unless you > trust the sender and know the content is safe. > EXPÉDITEUR EXTERNE:Ne cliquez sur aucun lien et n’ouvrez aucune pièce > jointe à moins qu’ils ne proviennent d’un expéditeur fiable, ou que vous ayez > l'assurance que le contenu provient d'une source sûre. > > Thanks for the update Zoran. > > I gonna take a look and test. > > Regards > JB > > > Le 18 déc. 2020 à 13:12, Zoran Regvart a écrit : > > > > Hi Cameleers, > > this has been targeted for releases 3.7.1 and 3.8.0, if you can, it > > would be of great help to test this before we release. > > > > zoran > > > > On Wed, Dec 16, 2020 at 3:44 PM Zoran Regvart wrote: > >> > >> Hi Cameleers, > >> I've created a PR[1], which I think fixes the problem, I encourage > >> folk to provide feedback and test on your end if possible. > >> > >> I've tested with the `SubscriptionHelperIntegrationTest`. And manually by: > >> > >> 1/ Starting a streaming app with the route: > >> > >> from("salesforce:Account?sObjectName=Account&rawPayload=true&sObjectQ > >> uery=SELECT > >> Id, Name FROM Account")¬ > >> .log(LoggingLevel.INFO, "salesforce", "${body}") > >> > >> 2/ creating an Account record, and noticing the output in the > >> log/console from the `log` component > >> > >> 3/ rejecting traffic to Salesforce using iptables: > >> $ iptables -A OUTPUT -d 85.222.0.0/16 -j REJECT > >> > >> 4/ disrupting the established connection using ss: > >> $ ss -K dst 85.222.154.145 # or whatever IP was in the output of lsof > >> -p $PID -a -i 6 -n > >> > >> 5/ noticing the messages in the log with back-off like: > >> > >> Connect failure: {failure={exception=java.io.EOFException: > >> HttpConnectionOverHTTP@45d7880c::DecryptedEndPoint@621bd87d{l=/192.168.1.76:43432,r=eu18.salesforce.com/85.222.155.145:443... > >> Restarting on unexpected disconnect from Salesforce... > >> Handshake failure: {failure={exception=java.net.ConnectException: > >> Connection refused, message={... > >> Handshake failure: {failure={exception=java.net.ConnectException: > >> Connection refused, message={... > >> > >> 5/ allowing traffic to Salesforce (removing the rule): > >> $ iptables -D OUTPUT 4 # happens to be 4th rule that I've added in > >> 3/, check with iptables -L OUTPUT --line-numbers > >> > >> 6/ seeing consumer reconnecting: > >> > >> Set Replay extension to replay from `-1` for channel `/topic/Account` > >> Subscribing to channel /topic/Account... > >> Successfully restarted! > >> Subscribed to channel /topic/Account > >> > >> 7/ creating a new Account record, and seeing the message logged from > >> the `log` component. > >> > >> zoran > >> > >> [1] > >> https://urldefense.com/v3/__https://github.com/apache/camel/pull/4778 > >> __;!!AaIhyw!_Vo0r3EhR2gpAnmiN1U-XwM3Z9ZaLIrFENHuHqbcLNhiY9FIm8ffp1i8c > >> EVEwBZG$ > >> > >> -- > >> Zoran Regvart > > > > > > > > -- > > Zoran Regvart > -- Claus Ibsen - http://davsclaus.com @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
RE: Salesforce streaming issue
Hi Can you please share maven repo setting using which I can directly use snapshot version of compiled jar file. I found compiling camel was a big task which I want to avoid. I will also give it a try. If possible springboot camel-salesforce-starter will be preferred, then I can try running the production code directly with snapshot version in lower environment. Thanks and Regards, Hemang Ajmera -Original Message- From: Jean-Baptiste Onofre Sent: 18 December 2020 18:24 To: Dev Cc: users@camel.apache.org; Andy Stebbing ; Ajmera, Hemang C Subject: Re: Salesforce streaming issue EXTERNAL SENDER: Do not click any links or open any attachments unless you trust the sender and know the content is safe. EXPÉDITEUR EXTERNE:Ne cliquez sur aucun lien et n’ouvrez aucune pièce jointe à moins qu’ils ne proviennent d’un expéditeur fiable, ou que vous ayez l'assurance que le contenu provient d'une source sûre. Thanks for the update Zoran. I gonna take a look and test. Regards JB > Le 18 déc. 2020 à 13:12, Zoran Regvart a écrit : > > Hi Cameleers, > this has been targeted for releases 3.7.1 and 3.8.0, if you can, it > would be of great help to test this before we release. > > zoran > > On Wed, Dec 16, 2020 at 3:44 PM Zoran Regvart wrote: >> >> Hi Cameleers, >> I've created a PR[1], which I think fixes the problem, I encourage >> folk to provide feedback and test on your end if possible. >> >> I've tested with the `SubscriptionHelperIntegrationTest`. And manually by: >> >> 1/ Starting a streaming app with the route: >> >> from("salesforce:Account?sObjectName=Account&rawPayload=true&sObjectQ >> uery=SELECT >> Id, Name FROM Account")¬ >> .log(LoggingLevel.INFO, "salesforce", "${body}") >> >> 2/ creating an Account record, and noticing the output in the >> log/console from the `log` component >> >> 3/ rejecting traffic to Salesforce using iptables: >> $ iptables -A OUTPUT -d 85.222.0.0/16 -j REJECT >> >> 4/ disrupting the established connection using ss: >> $ ss -K dst 85.222.154.145 # or whatever IP was in the output of lsof >> -p $PID -a -i 6 -n >> >> 5/ noticing the messages in the log with back-off like: >> >> Connect failure: {failure={exception=java.io.EOFException: >> HttpConnectionOverHTTP@45d7880c::DecryptedEndPoint@621bd87d{l=/192.168.1.76:43432,r=eu18.salesforce.com/85.222.155.145:443... >> Restarting on unexpected disconnect from Salesforce... >> Handshake failure: {failure={exception=java.net.ConnectException: >> Connection refused, message={... >> Handshake failure: {failure={exception=java.net.ConnectException: >> Connection refused, message={... >> >> 5/ allowing traffic to Salesforce (removing the rule): >> $ iptables -D OUTPUT 4 # happens to be 4th rule that I've added in >> 3/, check with iptables -L OUTPUT --line-numbers >> >> 6/ seeing consumer reconnecting: >> >> Set Replay extension to replay from `-1` for channel `/topic/Account` >> Subscribing to channel /topic/Account... >> Successfully restarted! >> Subscribed to channel /topic/Account >> >> 7/ creating a new Account record, and seeing the message logged from >> the `log` component. >> >> zoran >> >> [1] >> https://urldefense.com/v3/__https://github.com/apache/camel/pull/4778 >> __;!!AaIhyw!_Vo0r3EhR2gpAnmiN1U-XwM3Z9ZaLIrFENHuHqbcLNhiY9FIm8ffp1i8c >> EVEwBZG$ >> >> -- >> Zoran Regvart > > > > -- > Zoran Regvart
Re: Salesforce streaming issue
Thanks for the update Zoran. I gonna take a look and test. Regards JB > Le 18 déc. 2020 à 13:12, Zoran Regvart a écrit : > > Hi Cameleers, > this has been targeted for releases 3.7.1 and 3.8.0, if you can, it > would be of great help to test this before we release. > > zoran > > On Wed, Dec 16, 2020 at 3:44 PM Zoran Regvart wrote: >> >> Hi Cameleers, >> I've created a PR[1], which I think fixes the problem, I encourage >> folk to provide feedback and test on your end if possible. >> >> I've tested with the `SubscriptionHelperIntegrationTest`. And manually by: >> >> 1/ Starting a streaming app with the route: >> >> from("salesforce:Account?sObjectName=Account&rawPayload=true&sObjectQuery=SELECT >> Id, Name FROM Account")¬ >> .log(LoggingLevel.INFO, "salesforce", "${body}") >> >> 2/ creating an Account record, and noticing the output in the >> log/console from the `log` component >> >> 3/ rejecting traffic to Salesforce using iptables: >> $ iptables -A OUTPUT -d 85.222.0.0/16 -j REJECT >> >> 4/ disrupting the established connection using ss: >> $ ss -K dst 85.222.154.145 # or whatever IP was in the output of lsof >> -p $PID -a -i 6 -n >> >> 5/ noticing the messages in the log with back-off like: >> >> Connect failure: {failure={exception=java.io.EOFException: >> HttpConnectionOverHTTP@45d7880c::DecryptedEndPoint@621bd87d{l=/192.168.1.76:43432,r=eu18.salesforce.com/85.222.155.145:443... >> Restarting on unexpected disconnect from Salesforce... >> Handshake failure: {failure={exception=java.net.ConnectException: >> Connection refused, message={... >> Handshake failure: {failure={exception=java.net.ConnectException: >> Connection refused, message={... >> >> 5/ allowing traffic to Salesforce (removing the rule): >> $ iptables -D OUTPUT 4 # happens to be 4th rule that I've added in 3/, >> check with iptables -L OUTPUT --line-numbers >> >> 6/ seeing consumer reconnecting: >> >> Set Replay extension to replay from `-1` for channel `/topic/Account` >> Subscribing to channel /topic/Account... >> Successfully restarted! >> Subscribed to channel /topic/Account >> >> 7/ creating a new Account record, and seeing the message logged from >> the `log` component. >> >> zoran >> >> [1] https://github.com/apache/camel/pull/4778 >> >> -- >> Zoran Regvart > > > > -- > Zoran Regvart
Re: Salesforce streaming issue
Hi Cameleers, this has been targeted for releases 3.7.1 and 3.8.0, if you can, it would be of great help to test this before we release. zoran On Wed, Dec 16, 2020 at 3:44 PM Zoran Regvart wrote: > > Hi Cameleers, > I've created a PR[1], which I think fixes the problem, I encourage > folk to provide feedback and test on your end if possible. > > I've tested with the `SubscriptionHelperIntegrationTest`. And manually by: > > 1/ Starting a streaming app with the route: > > from("salesforce:Account?sObjectName=Account&rawPayload=true&sObjectQuery=SELECT > Id, Name FROM Account")¬ > .log(LoggingLevel.INFO, "salesforce", "${body}") > > 2/ creating an Account record, and noticing the output in the > log/console from the `log` component > > 3/ rejecting traffic to Salesforce using iptables: > $ iptables -A OUTPUT -d 85.222.0.0/16 -j REJECT > > 4/ disrupting the established connection using ss: > $ ss -K dst 85.222.154.145 # or whatever IP was in the output of lsof > -p $PID -a -i 6 -n > > 5/ noticing the messages in the log with back-off like: > > Connect failure: {failure={exception=java.io.EOFException: > HttpConnectionOverHTTP@45d7880c::DecryptedEndPoint@621bd87d{l=/192.168.1.76:43432,r=eu18.salesforce.com/85.222.155.145:443... > Restarting on unexpected disconnect from Salesforce... > Handshake failure: {failure={exception=java.net.ConnectException: > Connection refused, message={... > Handshake failure: {failure={exception=java.net.ConnectException: > Connection refused, message={... > > 5/ allowing traffic to Salesforce (removing the rule): > $ iptables -D OUTPUT 4 # happens to be 4th rule that I've added in 3/, > check with iptables -L OUTPUT --line-numbers > > 6/ seeing consumer reconnecting: > > Set Replay extension to replay from `-1` for channel `/topic/Account` > Subscribing to channel /topic/Account... > Successfully restarted! > Subscribed to channel /topic/Account > > 7/ creating a new Account record, and seeing the message logged from > the `log` component. > > zoran > > [1] https://github.com/apache/camel/pull/4778 > > -- > Zoran Regvart -- Zoran Regvart
Re: Salesforce streaming issue
Nice work! On Wed, Dec 16, 2020 at 8:44 AM Zoran Regvart wrote: > Hi Cameleers, > I've created a PR[1], which I think fixes the problem, I encourage > folk to provide feedback and test on your end if possible. > > I've tested with the `SubscriptionHelperIntegrationTest`. And manually by: > > 1/ Starting a streaming app with the route: > > > from("salesforce:Account?sObjectName=Account&rawPayload=true&sObjectQuery=SELECT > Id, Name FROM Account")¬ > .log(LoggingLevel.INFO, "salesforce", "${body}") > > 2/ creating an Account record, and noticing the output in the > log/console from the `log` component > > 3/ rejecting traffic to Salesforce using iptables: > $ iptables -A OUTPUT -d 85.222.0.0/16 -j REJECT > > 4/ disrupting the established connection using ss: > $ ss -K dst 85.222.154.145 # or whatever IP was in the output of lsof > -p $PID -a -i 6 -n > > 5/ noticing the messages in the log with back-off like: > > Connect failure: {failure={exception=java.io.EOFException: > HttpConnectionOverHTTP@45d7880c::DecryptedEndPoint@621bd87d{l=/ > 192.168.1.76:43432,r=eu18.salesforce.com/85.222.155.145:443... > Restarting on unexpected disconnect from Salesforce... > Handshake failure: {failure={exception=java.net.ConnectException: > Connection refused, message={... > Handshake failure: {failure={exception=java.net.ConnectException: > Connection refused, message={... > > 5/ allowing traffic to Salesforce (removing the rule): > $ iptables -D OUTPUT 4 # happens to be 4th rule that I've added in 3/, > check with iptables -L OUTPUT --line-numbers > > 6/ seeing consumer reconnecting: > > Set Replay extension to replay from `-1` for channel `/topic/Account` > Subscribing to channel /topic/Account... > Successfully restarted! > Subscribed to channel /topic/Account > > 7/ creating a new Account record, and seeing the message logged from > the `log` component. > > zoran > > [1] https://github.com/apache/camel/pull/4778 > > -- > Zoran Regvart >
Re: Salesforce streaming issue
Hi Cameleers, I've created a PR[1], which I think fixes the problem, I encourage folk to provide feedback and test on your end if possible. I've tested with the `SubscriptionHelperIntegrationTest`. And manually by: 1/ Starting a streaming app with the route: from("salesforce:Account?sObjectName=Account&rawPayload=true&sObjectQuery=SELECT Id, Name FROM Account")¬ .log(LoggingLevel.INFO, "salesforce", "${body}") 2/ creating an Account record, and noticing the output in the log/console from the `log` component 3/ rejecting traffic to Salesforce using iptables: $ iptables -A OUTPUT -d 85.222.0.0/16 -j REJECT 4/ disrupting the established connection using ss: $ ss -K dst 85.222.154.145 # or whatever IP was in the output of lsof -p $PID -a -i 6 -n 5/ noticing the messages in the log with back-off like: Connect failure: {failure={exception=java.io.EOFException: HttpConnectionOverHTTP@45d7880c::DecryptedEndPoint@621bd87d{l=/192.168.1.76:43432,r=eu18.salesforce.com/85.222.155.145:443... Restarting on unexpected disconnect from Salesforce... Handshake failure: {failure={exception=java.net.ConnectException: Connection refused, message={... Handshake failure: {failure={exception=java.net.ConnectException: Connection refused, message={... 5/ allowing traffic to Salesforce (removing the rule): $ iptables -D OUTPUT 4 # happens to be 4th rule that I've added in 3/, check with iptables -L OUTPUT --line-numbers 6/ seeing consumer reconnecting: Set Replay extension to replay from `-1` for channel `/topic/Account` Subscribing to channel /topic/Account... Successfully restarted! Subscribed to channel /topic/Account 7/ creating a new Account record, and seeing the message logged from the `log` component. zoran [1] https://github.com/apache/camel/pull/4778 -- Zoran Regvart