Trying to setup a Camel application to use liberty profile
jmsConnectionFactory, being able to do commits to the producer queue.
So then we don't want a local jms transaction, but there still is one, how
should this be handled?
--
View this message in context:
http://camel.465427.n5.nabbl
Another edit:
This is not a problem with Websphere, but a *bug with multicast and
PROPAGATION_REQUIRES_NEW*!
Camel version: 2.15.1
--
View this message in context:
http://camel.465427.n5.nabble.com/Multicast-with-Transaction-and-PROPAGATION-REQUIRES-NEW-does-not-work-tp5766013p5766054.html
Se
Little note,
PROPAGATION_REQUIRES_NEW does work when being in the same route, but once I
send it to a direct: queue it fails. And yes, the seda:queue I did since I
didn't get the deadLetterQueue to work...
from("seda:abc").log("Seda sent to error queue").to(errorQueue);
from(inbound_queue)
Hi,
I'm trying to get the transactions to work, have been through the
documentation and the book.
WMQ = websphere message queue
My goal:
* Get a message from the inbound queue
* Multicast it to 2 direct-queues <-- should be transactional, if something
fails the message should go to error queue
So well, this can be handled by using transacted() after picking up the
message from direct:inbound, making it look like:
from("direct:inbound")
.transacted()
.multicast().parallelProcessing().to("direct:a", "direct:b");
But there's another issue then.
If I have
onException(Exception.class
from("direct:inbound")
.multicast().parallelProcessing().to("direct:a", "direct:b");
//message a
from("direct:a").processRef("processor_a").to("validator:a.xsd")
.multicast().parallelProcessing().to("jms:q1", "jms:q2");
//message b
from("direct:b").processRef("processor_b").to("validator:b.xs
Sorry about that.
Yes its a (transactional) JmsComponent for websphere message queue
--
View this message in context:
http://camel.465427.n5.nabble.com/Possible-to-check-that-endpoints-exist-tp5764884p5764887.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Is it possible to verify that all outgoing endpoints exists?
For example
from("wmq:queue:A").to("wmq:queue:B")
It will validate A on the fly, since it tries to get data from the A queue.
But B is "validated" once it tries to send the message to that endpoint. Is
it possible validate that queue so
That does not help as I can see it.
What I would like to do is to set the ID, since the
objectName=...name="bean-2", the name is the ID
--
View this message in context:
http://camel.465427.n5.nabble.com/JMX-objectname-of-processors-MBeans-tp5764684p5764696.html
Sent from the Camel - Users mail
Hi,
I have a Processor defined as the following,
@ManagedResource(description = "Wiretap value")
public class WiretapValue implements Processor {
But to actually be able to see this in Jconsole, I can't use .process() in
my routebuilder but need to use
.bean((WiretapValue)
getContext().getRegis
Is there a reason why this does not work? If I remove the persistent=false it
does work the first time but when running the test again the message will
already be there, so i will get "collection size was <2>"
java.lang.AssertionError:
Expected: a collection with size <1>
but: collection siz
Hi,
So I have a XML data which i will split, transform every item, send every
item to validator and then send to an endpoint.
But I want to be sure all items validate before sending them to the
endpoint, so its All or None, if an error would arise on any item I want to
send the XML data(before spl
And the alternative would be using this?
But then I still get an error.. I'm using the same version for all my
dependencies and so on
org.apache.camel
camel-spring
${camel-version}
org.apache.maven.plugins
maven-jar-plugin
Hi,
I want to package my project as a JAR file with all dependencies.
* Or should I actually solve it in another way? We haven't decided how it
should be hosted yet
* Anyhow, I use maven-shade-plugin to package my project.
1. Get loads of warnings: "[WARNING] We have a duplicate"
2. Any improveme
14 matches
Mail list logo
