Hi Joerg, Thanks for sharing. I will update camel-jms documentation, you are right it’s confusing ;)
Regards JB > Le 25 mai 2021 à 15:41, Jörg Jansen <[email protected]> a > écrit : > > Hi JB, > > once again, thanks for your reply. > Replacing camel-activemq by camel-jms solved the memory consumption. > > There were only two items, whichI would like to share, or anyone who might > be affected: > > When using pax-jms in combination with the maven-bundle-plugin, I had to > remove the headers Import-Service,Export-Service. Otherwise the connection > factory could not be found. > The camel-jms documentation still recommends to use camel-activemq, which is > quite confusing. > > Also the provided example > (https://github.com/apache/karaf/tree/main/examples/karaf-jms-example/karaf-jms-example-features > > <https://github.com/apache/karaf/tree/main/examples/karaf-jms-example/karaf-jms-example-features>) > was very helpful. > > Thanks again, > Joerg > > From: Jörg Jansen > Sent: Donnerstag, 20. Mai 2021 08:00 > To: user <[email protected]> > Subject: RE: Memory usage camel-activemq & karaf 4.3.1 > > Hi JB, > > thanks for your feedback. > > Currently, we are using both, camel-activemq and the activemqbroker. > But the displayed difference is only when adding the camel-activemq feature. > > As the application was based on servicemix before, this behavior is still an > old relict 😉. > I’ll try to change everything to jms and come back with the result. > > If camel-activemq is still based on camel2, might it be a good idea, to mark > it as deprecated, with the hint to replace it by camel-jms? > > Kind regards, > Joerg > > From: Jean-Baptiste Onofre <[email protected] <mailto:[email protected]>> > Sent: Donnerstag, 20. Mai 2021 06:06 > To: user <[email protected] <mailto:[email protected]>> > Subject: Re: Memory usage camel-activemq & karaf 4.3.1 > > Hi Joerg, > > Do you install "just" camel-activemq feature or activemq-broker one as well ? > > I guess it doesn’t happen if you use camel-jms ? > > Generally speaking, I recommend to use camel-jms instead of camel-activemq. > The main reason is that camel-activemq is still Camel 2.x and you are using > Camel 3.x. You can achieve quite the same thing with camel-jms. > > Regards > JB > > > Le 19 mai 2021 à 20:44, Jörg Jansen <[email protected] > <mailto:[email protected]>> a écrit : > > Good evening everybody, > > Currently I’m using camel-3.7.4 and karaf 4.3.1. > I’ve recognized a strange behavior, when using camel-activemq feature. > > It seems, that from karaf version 4.3.1 the memory usage “explodes”, as soon > as the temporary data are created during startup. > After a while, the memory usage is decreasing again but at startup it > rexerved up to ~2GB of memory. > > In the picture below, you can see the occupied memory, in case I startup > karaf without the camel-activemq feature. Here, the allocated memory is 512MB > wihch is fine. > <image002.png> > > In the following picture, you can see the startup with camel-activemq as a > boo feature. > <image001.png> > > I hope this is the correct mailing list, or should belong the camel one? > In that case please bothering you 😊 > > Wondering if anyone else recognized this behavior. > > Any help would be very appreciated! > > Kind regards, > Joerg
