Hi All, Matt,
I've been holding off using Slack because I didn't feel I understood enough of the system to be useful. And the more I learnt the less I could imagine this being an ActiveMQ error. Finally, today, someone found an error in a local library which probably explains things (although I still have no idea why it should show up now). So it looks like this was a non-issue. Thanks for the support and sorry for the noise, Andrew On Tue, Oct 03, 2023 at 11:31:27AM -0500, Matt Pavlovich wrote: > Hi Andrew- > > You are correct, the activemq-camel component was removed since it was > largely redundant with the camel-jms component. > > Troubleshooting code over the mailing list is not really feasible. I sent you > an invite to the #activemq slack channel and you are always welcome to > checkout Commercial Support providers: https://activemq.apache.org/support > > One thing that does stand out is that the password has double ${ } macro > braces, and doesn’t look correct. > > > <property name="password" value="${${sa_broker1.user}}”/> > > Perhaps should be?: > > > <property name="password" value="${sa_broker1.user}”/ > > > Thanks, > Matt Pavlovich > > > > On Oct 3, 2023, at 10:45 AM, andrew cooke <andrewco...@isti.com> wrote: > > > > > > Hi All, > > > > I have been asked to help with an upgrade to an existing system that > > uses ActiveMQ and is being moved from version 5.14 to 5.18. > > Unfortunately I don't know much about the system (or ActiveMQ) and > > everyone else seems to know even less. > > > > When the new ActiveMQ version is deployed there are errors because the > > ActiveMQComponent class (and activemq-camel.jar) no longer exists. To > > fix this, I changed the XML configuration files to use JSMComponent. > > This was fairly simple, but I had to explicitly add a connection > > factory to some beans (it seems that on ActiveMQComponent you could > > specify the username, password and bokerURL directly on the > > component). > > > > With that done, the system starts. However, we seem to be missing a > > lot of messages (in fact, it looks like only the first message sent to > > any topic appears in the logs). > > > > Does anyone have any suggestion of what might be wrong? I apologise > > for my cluelessness here. > > > > If it's any help, here is an example of a fragment of XML that was > > changed: > > > > <bean id="sa-broker1" > > class="org.apache.activemq.camel.component.ActiveMQComponent" > > > <property name="brokerURL" value="${sa_broker1.URL}"/> > > <property name="username" value="${sa_broker1.user}"/> > > <property name="password" value="${${sa_broker1.user}}"/> > > </bean> > > > > was changed to > > > > <bean id="sa-broker1" > > class="org.apache.camel.component.jms.JmsComponent" > > > <property name="connectionFactory"> > > <bean class="org.apache.activemq.ActiveMQConnectionFactory"> > > <property name="brokerURL" value="${sa_broker1.URL}"/> > > <property name="userName" value="${sa_broker1.user}"/> > > <property name="password" value="${${sa_broker1.user}}"/> > > </bean> > > </property> > > </bean> > > > > Finally, I tried to start jconsole as that seemed to be a way to > > examine what was hapening internally. While I got jconsole to start > > (over ssh) there was no local connection visible, despite useJmx being > > "true". Also, there is no error in the AMQ logs (the brokers - the > > system uses 3 - seem to start and run with as before). > > > > Thanks, > > Andrew > > > > PS Maybe this is more a Camel issue than an ActiveMQ issue? If so, > > more apologies, and where should I be looking for support? > > > > -- > > > > > > > > > > > > > > > > > > *To follow ISTI news and updates please subscribe to our newsletter > > "the isti letter" at https://www.isti.com/newsletter-sign-up > > <https://www.isti.com/newsletter-sign-up>.* > > > > > > > > > > > > > -- > > > > > > > > > *To follow ISTI news and updates please subscribe to our newsletter > "the isti letter" at https://www.isti.com/newsletter-sign-up > <https://www.isti.com/newsletter-sign-up>.* > > > > > -- *To follow ISTI news and updates please subscribe to our newsletter "the isti letter" at https://www.isti.com/newsletter-sign-up <https://www.isti.com/newsletter-sign-up>.*
