-
1. Re: and yet another error with JMS and camel...
dead_devil_66 Apr 11, 2011 10:50 PM (in response to dead_devil_66)NOTE: im having the same issue with the project chapter7-jms, from the book "Camel in action".
-
2. Re: and yet another error with JMS and camel...
davsclaus Apr 13, 2011 2:33 AM (in response to dead_devil_66)Hi
You should really spend more time writing down more details about your issue. If the details is left out people is much less able to help you or provide suggestions.
If need need assistance and help immediately then you may consider consultancy, attend virtual or on-site training to get more familiar with the products you use etc.
-
3. Re: and yet another error with JMS and camel...
dead_devil_66 Apr 13, 2011 9:16 AM (in response to davsclaus)Hmmm thanks but no thanks. It's not such an urgency.
well, the only details i could think of are camel-context.xml, the fuse version and myBrokerA-broker.xml (the broker configuration file).
Version: 4.3.1-fuse-00-00
camel-context.xml:
the broker configuration:
I created the broker through servicemix console. After that, i edited the ports to 61617 and 61618. Now that i see the broker file, is it me or the camel namespace is the old one? (please god, not again lol)
-
4. Re: and yet another error with JMS and camel...
davsclaus Apr 13, 2011 11:21 AM (in response to dead_devil_66)Why do you setup 2 ActiveMQ brokers?
In the camel-context.xml file, you should only be the client of the broker, and thus you only need the JmsComponent.
-
5. Re: and yet another error with JMS and camel...
dead_devil_66 Apr 13, 2011 10:03 PM (in response to davsclaus)I didn't even know that i had the setup for two brokers, in the xml files. For camel-context.xml, i basically copied the camel-context.xml from chapter7-jms project. Where did you see that i have two brokers??
-
6. Re: and yet another error with JMS and camel...
davsclaus Apr 14, 2011 1:31 AM (in response to dead_devil_66)In the XML file you embed a broker using the broker namespace.
Also the comment in the XML says so.
<!-- set up ActiveMQ broker --> <broker:broker useJmx="false" persistent="false" brokerName="localhost"> <broker:transportConnectors> <broker:transportConnector name="tcp" uri="tcp://localhost:61617"></broker:transportConnector> </broker:transportConnectors> </broker:broker>
Again I suggest you consider training, or digging into some more getting started, and background material so you get more familiar with the products, and will be much more productive.
-
7. Re: and yet another error with JMS and camel...
dead_devil_66 Apr 15, 2011 4:46 PM (in response to davsclaus)Thanks for alerting me to the configuration, claus.
I have studied Camel for several days. Right now, i can't afford paying a training session. College fees and im doing this work to get a scholarship.
The major issues that i had with camel seemed to be the outdated schemas.
If there is any problem with me posting questions in here, just say it. I won't ask anything more, in here. No hard feelings.
Returning to the subject...
I have uninstalled the other broker that i have created through karaf console. Now i have installed the InOutJMS project again, in servicemix. But i'm getting this error:
The problem with this kind of errors is that, by reading the stack info, i can't tell where the problem is...it doesn't say (at least, i don't see how...) if the error was caused by a wrong configuration file or the route builder class...
-
8. Re: and yet another error with JMS and camel...
dead_devil_66 Apr 16, 2011 2:35 PM (in response to davsclaus)weeeeeell, after many head bangs in the wall, i discovered that the problem was...in the pom.xml
...
soooooooo, it seems that i needed to put the dependencies of the project chapter7-jms.
So, this leads me to my next question, one that i have been asking myself since i started working with maven, ESB's, camel, activemq and spring:
how do i know what dependencies to declare in the pom.xml? I mean, i have the java classes and the xml files configuring the brokers and routers. So, after setting up that, how do i know what to put in the pom.xml?? There must be thousands of dependencies available within maven repository...