I think the options to not have this effect are there in any case. The problem
is that the default is causing the hang.
Probably this can best be solved by the ActiveMQ team. Some warning that no
server could be reached would have saved me.
I will ask on the ActiveMQ list about that problem.
Chr
On Wed, Jan 26, 2011 at 4:52 PM, Christian Schneider
wrote:
> Hi Claus,
>
> I know that at least Tibco EMS does the same like ActiveMQ when using
> failover transport. This is why we did not use failover for test setups so we
> could diagnose problems with the jms server (e.g. wrong URL) easier.
Hi Claus,
I know that at least Tibco EMS does the same like ActiveMQ when using failover
transport. This is why we did not use failover for test setups so we could
diagnose problems with the jms server (e.g. wrong URL) easier.
The option did not work. I think it can not really work. As far as I
I think you should google about the WebSphere error code. And contact your
IBM support for that.
It seems related to using WebSphere with JBoss and not Camel specific per
see.
--
View this message in context:
http://camel.465427.n5.nabble.com/Running-camel-as-webapp-within-JBoss-using-JNDI-to-co
Hmm... That is not nice. But is this not something that should be caught in
the ActiveMQ project. Not sure if there is anything more that Camel could do
here other than what Claus said i.e fail quickly or look for a connect
exception.
Yikes... Never looked into that or tested for that before...
On Wed, Jan 26, 2011 at 4:06 PM, Christian Schneider
wrote:
> That´s a good thing. What do you think ? Should we somewhere document a
> warning about the problem on the wiki page of the jms component?
>
Christian did you try it?
Yeah we could add a TIP to the camel-jms wiki page to highlight th
That´s a good thing. What do you think ? Should we somewhere document a warning
about the problem on the wiki page of the jms component?
Christian
-Ursprüngliche Nachricht-
Von: Claus Ibsen [mailto:claus.ib...@gmail.com]
Gesendet: Mittwoch, 26. Januar 2011 15:07
An: users@camel.apache.
Hi,
Your file poller failover requirement can be addressed very simply.
You need to create a JMX event listener to listen to camel events (see link
below for example)
http://camel.apache.org/camel-jmx.html
http://camel.apache.org/camel-jmx.html
When a camel context, connection or montored ent
Try setting testConnectionOnStartup=true on the jms endpoint. Then it
ought to fail fast.
On Wed, Jan 26, 2011 at 3:03 PM, Christian Schneider
wrote:
> I just found an interesting "problem" with Camel and ActiveMQ.
>
> I defined my connection factory for jms like below without an explicit url:
I just found an interesting "problem" with Camel and ActiveMQ.
I defined my connection factory for jms like below without an explicit url:
I had a @Consume("jms:test") annotion in a class somewhere. I had no ActiveMQ
server running.
When I started the spring context the last line in the
Hi,
we deploy to a Tomcat server. There we bind a JNDI data source in the server
config. This way you get rid of your connection properties in
persistence.xml and camel-context.xml:
java:comp/env/jdbc/MY_DATASOURCE
Quartz suports running in a clustered environment where it can trigger
tasks to only run on one node.
On Tue, Jan 25, 2011 at 6:33 PM, Alfred Hiebl wrote:
>
> Hi,
>
> I'd like to ask for a best practice for a situation which I hope to be a
> common use-case. In our routes we consume data from po
Hi Ashwin,
Agreed. As soon as the messages are in my JMS queue the problem is solved.
But then the question is, how do I failover my single poller in case the one
node goes down that runs it.
And, preferrably, the single poller is also a Camel route. This implies that
I have differing route co
Thank you but it seems smooks is to blame.
Smooks should change the encoding to the one instructed in the edifact file.
It does so only if it gets a markable stream. And mine (from servicemix ftp
component) was not markable...
Thanks anyway!
On Mon, Jan 24, 2011 at 6:25 PM, Hadrian Zbarcea wrote
14 matches
Mail list logo
