Dear Tim
I can't find a word to thank you!!
> In the meantime, did anything actually fail when you did the restart?
> Restarting the broker should definitely work without this error, but did
> it
> have any negative effect other than the scary-sounding message showing up
> in the logs? I'm jus
1) Those JARs should all be compatible with one another, since they're all
packaged as part of the ActiveMQ installation bundle. I was trying to see
if maybe you'd added your own Spring JARs to the classpath in addition to
the ones from ActiveMQ's lib directory, but that's clearly not the case,
and
Thanks Tim!
(1)
I made sure if my activemq loaded Spring-related JARs by booting activemq
with -verbose:class option.
There seem to be several Spring-related JARs as follows.
/opt/apache-activemq/lib/activemq-spring-5.14.3.jar
/opt/apache-activemq/lib/optional/spring-beans-4.1.9.RELEASE.jar
/opt/
No problem, many people are off work for Golden Week.
What Spring-related JARs are on your broker's classpath? Have you added any
Spring-related JARs other than the one that came with the ActiveMQ
installation?
Tim
On Sun, May 7, 2017 at 8:40 PM, Hidekazu wrote:
> Thanks a lot!
> I’m sorry for
Thanks a lot!
I’m sorry for not responding for a while but I don’t forget the feeling of
gratitude.
In Japan, we had a long holiday called Golden Week and that’s the reason I
couldn’t respond to you. Anyway,sorry.
I’m running a standalone broker from a clean install.
Does my answer make sense?
Jav
LifecycleProcessor is a Spring class used to process lifecycle events such
as start, stop, restart, etc.
The first few results of
https://www.google.com/search?q=spring+lifecycleprocessor+not+initialized&oq=spring+LifecycleProcessor
all point to incompatible versions of the various Spring JARs. Ar
