Re: Apache Log4j 1.x Multiple Vulnerabilities--Apache ActiveMQ classic version upgrade

2024-02-27 Thread Matt Pavlovich
This looks like you are referencing a log handler that is not shipped as part of the Apache ActiveMQ distribution. Possibly a Fuse or Red Hat A-MQ build? That part of the ActiveMQ configuration needs to be removed and/or modified. Thanks, Matt Pavlovich > On Feb 1, 2024, at 5:03 PM, Vishnu

RE: Apache Log4j 1.x Multiple Vulnerabilities--Apache ActiveMQ classic version upgrade

2024-02-01 Thread Vishnu Middela
(XBeanQNameHelper.java:75) Thanks & Regards Vishnu Middela -Original Message- From: Vishnu Middela Sent: Wednesday, January 31, 2024 9:13 AM To: users@activemq.apache.org Subject: RE: Apache Log4j 1.x Multiple Vulnerabilities--Apache ActiveMQ classic version upgrade Hi, Current Java ver

RE: Apache Log4j 1.x Multiple Vulnerabilities--Apache ActiveMQ classic version upgrade

2024-01-31 Thread Paul McCulloch
4 2:13 PM > To: users@activemq.apache.org > Subject: RE: Apache Log4j 1.x Multiple Vulnerabilities--Apache ActiveMQ > classic version upgrade > > IFS Security Notice - External Email - Don't be too quick to click! > Think carefully before clicking on links or attachments. Never pro

RE: Apache Log4j 1.x Multiple Vulnerabilities--Apache ActiveMQ classic version upgrade

2024-01-31 Thread Vishnu Middela
t see anything in the logs either.. > > > > > > > > > > Thanks & Regards > > Vishnu Middela > > > > -Original Message- > From: Justin Bertram > Sent: Monday, January 29, 2024 7:47 PM > To: users@activemq.apache.org > S

RE: Apache Log4j 1.x Multiple Vulnerabilities--Apache ActiveMQ classic version upgrade

2024-01-30 Thread Vishnu Middela
t; > > > > > > > > Thanks & Regards > > Vishnu Middela > > > > -Original Message- > From: Justin Bertram > Sent: Monday, January 29, 2024 7:47 PM > To: users@activemq.apache.org > Subject: Re: Apache Log4j 1.x Multiple Vul

Re: Apache Log4j 1.x Multiple Vulnerabilities--Apache ActiveMQ classic version upgrade

2024-01-29 Thread Justin Bertram
Regards > > Vishnu Middela > > > > -Original Message- > From: Justin Bertram > Sent: Monday, January 29, 2024 7:47 PM > To: users@activemq.apache.org > Subject: Re: Apache Log4j 1.x Multiple Vulnerabilities--Apache ActiveMQ > classic version upgrade

RE: Apache Log4j 1.x Multiple Vulnerabilities--Apache ActiveMQ classic version upgrade

2024-01-29 Thread Vishnu Middela
apache.org<mailto:users@activemq.apache.org> Subject: Re: Apache Log4j 1.x Multiple Vulnerabilities--Apache ActiveMQ classic version upgrade CAUTION - EXTERNAL: Your output doesn't indicate any problems. Everything looks normal as far as I can tell. This is the same output I se

Re: Apache Log4j 1.x Multiple Vulnerabilities--Apache ActiveMQ classic version upgrade

2024-01-29 Thread Justin Bertram
Your output doesn't indicate any problems. Everything looks normal as far as I can tell. This is the same output I see when I execute "activemq start" on a default instance of ActiveMQ Classic 5.18.3. I recommend you check the output in data/activemq.log to see if the broker started up properly.

RE: Apache Log4j 1.x Multiple Vulnerabilities--Apache ActiveMQ classic version upgrade

2024-01-29 Thread Vishnu Middela
Hi, Attached are the steps that are followed to upgrade ApacheMQ classic from 5.15.8 to 5.18.3 Only message I see is as below after trying to start activemq. Please let me know if I missed any steps and how to debug this issue. [bodi@aoedw-e-app3009 bin]$ ./activemq start INFO:

RE: Apache Log4j 1.x Multiple Vulnerabilities--Apache ActiveMQ classic version upgrade

2024-01-24 Thread Vishnu Middela
Hi, Any update on below request is appreciated..thanks Thanks & Regards Vishnu Middela -Original Message- From: Vishnu Middela Sent: Tuesday, January 23, 2024 2:23 PM To: users@activemq.apache.org Subject: RE: Apache Log4j 1.x Multiple Vulnerabilities Hi, If I want