[
https://issues.apache.org/jira/browse/CAMEL-12484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16578083#comment-16578083
]
Hemang Ajmera edited comment on CAMEL-12484 at 8/13/18 12:06 PM:
-----------------------------------------------------------------
We have being running this component with debug logging for
org.apache.camel.component.salesforce.internal.streaming.SubscriptionHelper
I have two logs, one before restart and one after restart...
Here are my observations.
# In the logs before restart the component is running but not picking up
message.We can see that after every 110 seconds it is polling message. However
there are not messages being picked after 2018-08-06 02:01:36.024. Message with
replayId = 11341 is the last one, after which it has not been able to pick any
message.
# Logs after restart where component picks up the messages without any
changes. Since the component was started after 4 days there are few messages
which are missing and the first message which it could get is 11485 and we have
lost all the messages in between.
# We are using camel springboot starter component for salesforce
# We are using initial replay is as -2 and we are saving all the replayid to
avoid duplicates.
was (Author: hemangajmera):
We have being running this component with debug logging for
org.apache.camel.component.salesforce.internal.streaming.SubscriptionHelper
I will be attaching two logs by tomorrow end of the day...
1. where the component is running but not picking up message.
2. Logs after restart where component picks up the messages without any
changes.
I am just doing some cleanup on the logs to remove all internal details.
> Camel-salesforce component does not try to reconnect on specific error
> ----------------------------------------------------------------------
>
> Key: CAMEL-12484
> URL: https://issues.apache.org/jira/browse/CAMEL-12484
> Project: Camel
> Issue Type: Bug
> Components: camel-salesforce
> Affects Versions: 2.21.0
> Reporter: Hemang Ajmera
> Priority: Major
> Attachments: logs.zip
>
>
> The issue is very much identical to CAMEL-10238 where camel component does
> not try to reconnect. It was resolved for that particular case, however there
> is additional scenario where we are facing exactly similar problem.
> Here is the key log message after which component stops retrying
> {{2018-05-03 17:19:50.257 WARN 7636 — [nt@911561694-23]
> o.a.c.c.s.i.s.SubscriptionHelper : Connect failure:
> {clientId=3qi3g4psrtqrntt15ockewu0a59q, advice=
> {reconnect=none, interval=0}
> , channel=/meta/connect, id=154, error=403::Unknown client,
> successful=false}}}
> Please note that we are getting Connect failure multiple times but it is able
> to reconnect where there is exception or when the advice is to do handshake
> again. Here are those sample which works...
> * The one with exceptions
> {quote}2018-05-03 17:19:17.965 WARN 7636 — [nt@911561694-23]
> o.a.c.c.s.i.s.SubscriptionHelper : Connect failure: {failure=
> Unknown macro: \{exception=java.io.EOFException}
> ],recv=HttpReceiverOverHTTP@144e8ebb(rsp=IDLE,failure=null)[HttpParser
> Unknown macro: \{s=CLOSED,0 of -1}
> ]]<-DecryptedEndPoint@245db684
> Unknown macro: \{telia-fi--dev.cs88.my.salesforce.com/85.222.137.144}
> ->HttpConnectionOverHTTP@69f41507(l:/0:0:0:0:0:0:0:1:60369 <->
> r:telia-fi--dev.cs88.my.salesforce.com/85.222.137.144:443,closed=false)=>HttpChannelOverHTTP@3109c579(exchange=HttpExchange@76b96e24
> req=TERMINATED/null@null
> res=PENDING/null@null)[send=HttpSenderOverHTTP@5d6efa04(req=QUEUED,snd=COMPLETED,failure=null)[HttpGenerator@43ac2f18
> Unknown macro: \{s=START}
> ],recv=HttpReceiverOverHTTP@144e8ebb(rsp=IDLE,failure=null)[HttpParser
> ]]->SocketChannelEndPoint@6b93b346
> Unknown macro: \{telia-fi--dev.cs88.my.salesforce.com/85.222.137.144}
> Unknown macro: \{io=0/0,kio=0,kro=1}
>
> ->SslConnection@53bc7193\{NEED_WRAP,eio=-1/-1,di=-1}=>HttpConnectionOverHTTP@69f41507(l:/0:0:0:0:0:0:0:1:60369
> <->
> r:telia-fi--dev.cs88.my.salesforce.com/85.222.137.144:443,closed=false)=>HttpChannelOverHTTP@3109c579(exchange=HttpExchange@76b96e24
> req=TERMINATED/null@null
> res=PENDING/null@null)[send=HttpSenderOverHTTP@5d6efa04(req=QUEUED,snd=COMPLETED,failure=null)[HttpGenerator@43ac2f18
> Unknown macro: \{s=START}
> ],recv=HttpReceiverOverHTTP@144e8ebb(rsp=IDLE,failure=null)[HttpParser
> Unknown macro: \{s=CLOSED,0 of -1}
> ]], message=\{clientId=3qi3g4psrtqrntt15ockewu0a59q, channel=/meta/connect,
> id=153, connectionType=long-polling}, connectionType=long-polling},
> channel=/meta/connect, id=153, successful=false}
> {quote}
>
> * The one with advice for new handshake
> {quote}2018-05-03 16:31:08.970 WARN 7636 — [nt@911561694-21]
> o.a.c.c.s.i.s.SubscriptionHelper : Connect failure:
> Unknown macro: \{advice=Unknown macro}
> , channel=/meta/connect, id=83, error=403::Unknown client, successful=false}
> {quote}
>
> One more thing, this log is coming from line 168 {{LOG.warn("Connect failure:
> {}", message);}} of the
> [https://github.com/apache/camel/blob/master/components/camel-salesforce/camel-salesforce-component/src/main/java/org/apache/camel/component/salesforce/internal/streaming/SubscriptionHelper.java#L168].
> I see that there is no attempt to reconnect. If this information helps move
> things faster...
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
