Is this a confirmed statement regarding the support of JMS and from which
component?
If Yes then the documentation is flawed and needs updating.
I was under the impression that SJMS2 was built to be a new all non-spring with
built in features like pooling and stuff, faster and more efficient ,
Camel support 4 JMS Broker clients
1) ActiveMQ Component
2) JMS Component (based on Spring)
3) SJMS Component
4) SJMS2 Component
ActivMQ Classic supports JMS 1.1. For this you should not use SJMS2
component as this is for JMS2.0. So this should be implemented with on of
the first three components
Well would that be the same as ?keepAlive=true on the broker URL?
ttl is default to -1 on the sjms2 component
M
> On 21 Oct 2019, at 14:47, ski n wrote:
>
> Can you tell more about broker and connection?
>
> 1) Are you connecting to ActiveMQ Classic or Artemis
> 2) Which version of ActiveMQ i
ActiveMQ Classic 5.15.1
As example below, as a bean in a Camel Spring Boot application
I’ll test the TTL feature!
Thx
M
> On 21 Oct 2019, at 14:47, ski n wrote:
>
> Can you tell more about broker and connection?
>
> 1) Are you connecting to ActiveMQ Classic or Artemis
> 2) Which version of
Can you tell more about broker and connection?
1) Are you connecting to ActiveMQ Classic or Artemis
2) Which version of ActiveMQ is used?
3) How does the connectionFactory is setup?
For ActivMQ classic I use the ActiveMQ Component (
https://camel.apache.org/components/latest/activemq-component.ht
We have similar issues as per this jira issue:
https://issues.apache.org/jira/browse/CAMEL-10912
Our route receives a file once a day and shall process this and send a message
to a queue.
We get too many Session closed issues now.
We are only using a ConnectionFactory
@Bean
public void sjms2C
