The first few results for this search (
https://www.google.com/search?q=activemq+%22Transport+scheme+NOT+recognized%22+ws&ie=utf-8&oe=utf-8)
all point to you not having the right JARs on the classpath. Have you
confirmed that the right JARs are in fact on your classpath?
Tim
On Wed, May 3, 2017
Hi All,
We are upgrading Activemq 5.9 to 5.14.4, messages are getting processed but
web console is not getting up. below exceptions are throwing. can any one
please help on this.
2017-05-04 00:32:21,714 | WARN | Async error occurred: |
org.apache.activemq.broker.TransportConnection.Service | Ac
I can attest to the embedded camel for ActiveMQ we have been running a route
in production for 3 years+ with no issues.
I use it for message routing based on content.
Mike
--
View this message in context:
http://activemq.2283324.n4.nabble.com/broker-to-broker-testing-scenario-tp4725331p472555
I'm trying to setup a replicated failover cluster I can't seem to get them to
connect.
Can someone please review the broker.xml below and let me know if I'm doing
this right.
Thanks
Mike
Enviroment:
AWS EC2
Windows 2016
Java 1.8.0_131
Testing using Artemis.cmd run
I am able to connect using SS
I Integrated activeMQ in jboss in such a way that when I start a project
deployed in jboss, activeMQ broker start.
The broker serverUrl defined in the ra.xml file is "vm://localhost" and my
broker-config file:
http://www.springframework.org/schema/beans";
xmlns:amq="http://activemq.apache.org/s
I found the solution. The trick is the "useJndi" ActivationConfigProperty
@MessageDriven(
activationConfig = {
@ActivationConfigProperty(propertyName = "destination", propertyValue =
"java://activemq/Queue.Notifications.Project"),
@ActivationConfigProperty(propertyName = "destinationTy
As Clebert mentioned, this is more of an application server question. The
broker and/or resource adapter don't control the deployment of the MDB, that's
the EJB container's job.
That said, I believe the latest versions of Wildfly support using a system
property in the annotation itself rather
> I'd use embedded Camel routes
P.S. I forgot to say that we are using Camel, but have not yet tried
enabling it in an ActiveMQ message broker. Your reply confirms that this is
probably the way to go. It looks fairly straightforward (there is an example
in the activemq examples folder).
--
V
Thanks for the reassurance -- it's easy to miss things.
(Sorry I didn't get back to you sooner -- a long weekend -- but the reply is
appreciated.)
Jonathan
--
View this message in context:
http://activemq.2283324.n4.nabble.com/broker-to-broker-testing-scenario-tp4725331p4725502.html
Sent fro