Sending exchange through Pulsar endpoint, exchange properties disappear

2023-04-13 Thread Steve973
Hello.  I am sending an exchange with a FluentProducerTemplate to a pulsar
endpoint.  When a route reads from that endpoint, the exchange property
that I set is no longer there.  This is how I am sending the message:

Exchange exchange = ExchangeBuilder.anExchange(camelContext)
.withProperty("command", MessageTypes.GENERATE_NUMBERS_COMMAND)
.withBody(generateNumbersCommandMessage.toByteArray())
.build();
fluentProducerTemplate.withExchange(exchange)
.to(commandUri)
.send();

I am reading from the same URI to feed a route where I log the exchange:

from(mainRouterConfig.commandEntrypoint())
.to("log:to.dynamic-router.command.route?showAll=true=true")
.to("%s:%s?recipientMode=%s".formatted(
COMPONENT_SCHEME, mainRouterConfig.routingChannel(), mainRouterConfig
.recipientMode()));

The exchange property is absent in the log message:

  Id: 453CF424AB353C4-
 ExchangePattern: InOnly
 Properties:
{CamelToEndpoint=log://to.dynamic-router.command.route?multiline=true=true}

 Headers: {CamelMessageTimestamp=1681420673229,
CamelPulsarRedeliveryCount=0, event_time=0, key=null, key_bytes=null,
message_id=0:0:-1, producer_name=standalone-0-11, properties={},
publish_time=1681420673229
, sequence_id=0,
topic_name=non-persistent://public/default/numbers/command}
 BodyType: byte[]
 Body: generateNumberstypesequentialstart0limit100

Am I doing anything obviously wrong?  Or is the Pulsar component eating
exchange properties?

Thanks,
Steve


RE: FTPS consumer stops polling / listing

2023-04-13 Thread Petr Kuzel
Hi Camel community,

I have progressed a tiny bit.

My understanding for:

> #1 Is there a use case when the remote polling
> consumer stops by the (Camel) design
> while the route is in the started state, please?

is that the scheduler triggers the FTP poll every 

Meanwhile I got extract of the FTP log and it confirmed
that every 20 seconds there was connection.

At the timestamp matching the client log exception, the (IIS) FTP log contains:

   2023-04-04 11:54:50 10.99.148.243 EU50APVP926\FTPS_IN01_EESB_SIT 
10.99.250.43 38 134 60
/GI/Outbound/foo/bar

Client+IP+on+the+control+channel+didn't+match+the+client+IP+on+the+data+channel.
  

BUT after that, with 20 s period, there are connection logs
that are not followed by any list attempt. At the client log,
there are no INFO or higher severity messages. 

The periodic list-less connections disappear after
the route restart. After the restart
the periodic connections are followed by listing,
... and the file consuming continues as expected.  

So let me reformulate the first question. 

#1 Does the FTPS endpoint consumer maintain
a state to skip listing the remote in certain, namely
post-error, cases, please? 

I speculate that the route restart discarded some
internal (likely corrupted) state.

  Hope it helps
  Cc.

--
  Mr. Petr Kužel, Software Engineer
  Eurofins International Support Services s.à r.l.
  Val Fleuri 23
  L-1526 LUXEMBOURG

-Original Message-
From: Petr Kuzel  
Sent: Thursday, April 6, 2023 16:45
To: users@camel.apache.org
Subject: FTPS consumer stops polling 



CAUTION: EXTERNAL EMAIL - Sent from an email domain that is not formally 
trusted by Eurofins.

Do not click on links or open attachments unless you recognise the sender and 
are certain that the content is safe.

Hi Camel community,

I have a route with a from( FTPS component ).

Recently it happened that the FTP server closed
connection in middle of polling and on a next
attempt PASV failed to open data connection.

The route onException(Exception.class) logged
two exchanges, two exceptions. It  sets
handled( false ) so continuing by the 

Then the route got silent.

Later I noticed many unprocessed files on the FTP
server so I have stopped the route, removed it,
added back its copy and started it.
Then the FTP polling continued as usually.

When I try to reproduce locally, the logs include:

WARN  o.a.c.c.f.r.RemoteFilePollingConsumerPollStrategy
 Trying to recover by force disconnecting from remote server
 and re-connecting at next poll: ftps://admin@localhost:21

which is not present in the logs from incident.

I'd have two questions.

#1 Is there a use case when the remote polling
consumer stops by the (Camel) design
while the route is in the started state, please?

#2 What is expected behaviour of the 
in case of connection issues, please?
(I know that "${file:onlyname}" logged "")

more context:

Camel: 3.14.3

Consumer params: minDepth=2=true=$simple{file:size} < 
1073741825=changed=3000=2=2=false=true=true=false=true=true=foo=bar=2


First exchange log (in reverse order):

message=2023-04-04T11:54:46.247Z ERROR 1 --- [NVOICE/Outbound] 
o.a.c.p.e.DefaultErrorHandler : Failed delivery for (MessageId: 
AD84EFA6423B77A-0321 on ExchangeId: 
AD84EFA6423B77A-0321). Exhausted after delivery attempt: 1 caught: 
org.apache.camel.component.file.GenericFileOperationFailedException: File 
operation failed: 150 Opening BINARY mode data connection. Remote host 
terminated the handshake. Code: 150. Processed by failure processor: 
FatalFallbackErrorHandler[null] Message History (complete message history is 
disabled) 
---
 RouteId ProcessorId Processor Elapsed (ms) [FTPSConsumerFor-GE] 
[FTPSConsumerFor-GE] [from[ftps://foo] [ 27] Stacktrace 
---
 org.apache.camel.component.file.GenericFileOperationFailedException: File 
operation failed: 150 Opening BINARY mode data connection. Remote host 
terminated the handshake. Code: 150 at 
org.apache.camel.component.file.remote.FtpOperations.listFiles(FtpOperations.java:954)
 ~[camel-ftp-3.14.3.jar!/:3.14.3] at 
org.apache.camel.component.file.remote.FtpOperations.listFiles(FtpOperations.java:55)
 ~[camel-ftp-3.14.3.jar!/:3.14.3] at 
org.apache.camel.component.file.remote.strategy.ExclusiveReadLockCheck.getFtpFilesByFilter(ExclusiveReadLockCheck.java:115)
 ~[camel-ftp-3.14.3.jar!/:3.14.3] at 
org.apache.camel.component.file.remote.strategy.ExclusiveReadLockCheck.getFtpFiles(ExclusiveReadLockCheck.java:97)
 ~[camel-ftp-3.14.3.jar!/:3.14.3] at 
org.apache.camel.component.file.remote.strategy.ExclusiveReadLockCheck.tryAcquireExclusiveReadLock(ExclusiveReadLockCheck.java:55)
 ~[camel-ftp-3.14.3.jar!/:3.14.3] at 

Re: [VOTE] Release Apache Camel Kamelets 3.20.3

2023-04-13 Thread Otavio Rodolfo Piske
+1 (binding)

Thanks Andrea

On Thu, Apr 13, 2023 at 2:53 PM Claudio Miranda 
wrote:

> +1 (non binding)
>
> --
>   Claudio Miranda
>
> clau...@claudius.com.br
> http://www.claudius.com.br
>


-- 
Otavio R. Piske
http://orpiske.net


Re: [VOTE] Release Apache Camel Kamelets 3.20.3

2023-04-13 Thread Claudio Miranda
+1 (non binding)

-- 
  Claudio Miranda

clau...@claudius.com.br
http://www.claudius.com.br


Re: [VOTE] Release Apache Camel Kamelets 3.20.3

2023-04-13 Thread Jean-Baptiste Onofré
+1 (binding)

Regards
JB

On Thu, Apr 13, 2023 at 2:41 PM Andrea Cosentino  wrote:
>
> Hello all:
>
> This is a vote for releasing camel-kamelets 3.20.3
>
> This release contains bug fixes and upgrade to latest camel 3.20.3
>
> Kamelets release files:
> https://dist.apache.org/repos/dist/dev/camel/camel-kamelets/3.20.3
> Kamelets staging repository:
> https://repository.apache.org/content/repositories/orgapachecamel-1545
> Kamelets Tag:
> https://gitbox.apache.org/repos/asf?p=camel-kamelets.git;a=shortlog;h=refs/tags/v3.20.3
>
> Please cast your vote.
>
> [ ] +1 Release camel-kamelets 3.20.3
> [ ] -1 Veto the release (provide specific comments)
>
> The vote is open for at least 72 hours.
>
> Here's my +1.
>
> Thanks,
> Andrea Cosentino


Re: [VOTE] Release Apache Camel Kamelets 4.0.0-M2

2023-04-13 Thread Jean-Baptiste Onofré
+1 (binding)

Regards
JB

On Thu, Apr 13, 2023 at 2:40 PM Andrea Cosentino  wrote:
>
> Hello all:
>
> This is a vote for releasing camel-kamelets 4.0.0-M2
>
> Kamelets release files:
> https://dist.apache.org/repos/dist/dev/camel/camel-kamelets/4.0.0-M2
> Kamelets staging repository:
> https://repository.apache.org/content/repositories/orgapachecamel-1544
> Kamelets Tag:
> https://gitbox.apache.org/repos/asf?p=camel-kamelets.git;a=shortlog;h=refs/tags/v4.0.0-M2
>
> Please cast your vote.
>
> [ ] +1 Release camel-kamelets 4.0.0-M2
> [ ] -1 Veto the release (provide specific comments)
>
> The vote is open for at least 72 hours.
>
> Here's my +1.
>
> Thanks,
> Andrea Cosentino


[VOTE] Release Apache Camel Kamelets 3.20.3

2023-04-13 Thread Andrea Cosentino
Hello all:

This is a vote for releasing camel-kamelets 3.20.3

This release contains bug fixes and upgrade to latest camel 3.20.3

Kamelets release files:
https://dist.apache.org/repos/dist/dev/camel/camel-kamelets/3.20.3
Kamelets staging repository:
https://repository.apache.org/content/repositories/orgapachecamel-1545
Kamelets Tag:
https://gitbox.apache.org/repos/asf?p=camel-kamelets.git;a=shortlog;h=refs/tags/v3.20.3

Please cast your vote.

[ ] +1 Release camel-kamelets 3.20.3
[ ] -1 Veto the release (provide specific comments)

The vote is open for at least 72 hours.

Here's my +1.

Thanks,
Andrea Cosentino


[VOTE] Release Apache Camel Kamelets 4.0.0-M2

2023-04-13 Thread Andrea Cosentino
Hello all:

This is a vote for releasing camel-kamelets 4.0.0-M2

Kamelets release files:
https://dist.apache.org/repos/dist/dev/camel/camel-kamelets/4.0.0-M2
Kamelets staging repository:
https://repository.apache.org/content/repositories/orgapachecamel-1544
Kamelets Tag:
https://gitbox.apache.org/repos/asf?p=camel-kamelets.git;a=shortlog;h=refs/tags/v4.0.0-M2

Please cast your vote.

[ ] +1 Release camel-kamelets 4.0.0-M2
[ ] -1 Veto the release (provide specific comments)

The vote is open for at least 72 hours.

Here's my +1.

Thanks,
Andrea Cosentino