0

When I introduced activemq-all in jetty and deployed the application, a NoSuchMethodException error occurred. However, when I introduced the activemq-client dependency, the error disappeared. The following is an error.

Caused by: java.lang.NoSuchMethodException: org.springframework.jms.annotation.JmsBootstrapConfiguration$$EnhancerBySpringCGLIB$$17cf8886.CGLIB$SET_THREAD_CALLBACKS([Lorg.springframework.cglib.proxy.Callback;)
    at java.lang.Class.getDeclaredMethod(Class.java:2130)
    at org.springframework.cglib.proxy.Enhancer.getCallbacksSetter(Enhancer.java:912)
    at org.springframework.cglib.proxy.Enhancer.access$000(Enhancer.java:93)
    at org.springframework.cglib.proxy.Enhancer$EnhancerFactoryData.<init>(Enhancer.java:502)
1
  • Any feedback here? Commented Jan 17 at 19:36

1 Answer 1

0

As the name suggests, the activemq-all dependency contains all the dependencies for the ActiveMQ Classic broker and client including its own Spring dependencies. You definitely should not be including it in your Spring application as it is likely to cause conflicts. That is, in fact, why you're seeing the NoSuchMethodException.

You should only need to depend on activemq-client if you're integrating via JMS.

Sign up to request clarification or add additional context in comments.

Comments

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.