Ayache,
I’ve experienced this too and have mitigated it by overriding the
getCamelContextCreationTimeout method and specifying a larger amount of time
(say 30 or 60 seconds). This will allow for an extended period of time for the
Camel Context to come up in slower environments.
--
Andrew
Hi Henryk
Thank you for the above suggestion. I have applied the fix, but
unfortunately tests still failing randomly on Gave up waiting for service.
Thanks
Ayache
On 17 February 2015 at 16:48, Henryk Konsek hekon...@gmail.com wrote:
Hi,
Check out this [1] solution. It worked for one of
Hi,
Check out this [1] solution. It worked for one of ours customer. He
suffered from the intermittent failing CamelBlueprintTests as well.
Cheers.
[1] https://access.redhat.com/solutions/640943
On Tue, Feb 17, 2015 at 12:30 PM, Ayache Khettar
ayache.khet...@googlemail.com wrote:
I've added
Here is sample project: https://github.com/akhettar/message-connector.
There are other component failings too, but randomly and not frequently.
But it's becoming really annoying to see these random failures happening 4
to 6 times a day (depending on how often we check in). Rarely fails on my
dev
Hi,
Does your QA box have the internet access?
--
Willem Jiang
Red Hat, Inc.
Web: http://www.redhat.com
Blog: http://willemjiang.blogspot.com (English)
http://jnn.iteye.com (Chinese)
Twitter: willemjiang
Weibo: 姜宁willem
On February 6, 2015 at 6:35:47 PM, Ayache Khettar
Hi Ayache, what version of Camel do you use?
There was a fix to camel-blueprint tests a while ago (see
https://issues.apache.org/jira/browse/CAMEL-7469)
regards
Grzegorz Grzybek
2015-02-17 9:39 GMT+01:00 Willem Jiang willem.ji...@gmail.com:
Hi,
Does your QA box have the internet access?
Ayache - do you try to run one of Camel's own tests, or your own?
regards
Grzegorz
2015-02-17 11:35 GMT+01:00 Ayache Khettar ayache.khet...@googlemail.com:
Hi Grzegorz
I am using Camel version 2.13.2, which I think it should have the fixe you
pointed below.
Thanks
Ayache
On 17
I've added the
https://github.com/akhettar/message-connector/blob/master/test/MHSTestFixture.java
incase you want to see the parent test class.
On 17 February 2015 at 11:15, Ayache Khettar ayache.khet...@googlemail.com
wrote:
Here is sample project: https://github.com/akhettar/message-connector.
Ayache, could you share it? via github maybe?
~Grzegorz
2015-02-17 11:54 GMT+01:00 Ayache Khettar ayache.khet...@googlemail.com:
My own Unit Test
Ayache
On 17 February 2015 at 10:42, Grzegorz Grzybek gr.grzy...@gmail.com
wrote:
Ayache - do you try to run one of Camel's own tests, or
Hi Willem
I am afraid not and never will I was told :)
Ayache
On 17 February 2015 at 08:39, Willem Jiang willem.ji...@gmail.com wrote:
Hi,
Does your QA box have the internet access?
--
Willem Jiang
Red Hat, Inc.
Web: http://www.redhat.com
Blog: http://willemjiang.blogspot.com
My own Unit Test
Ayache
On 17 February 2015 at 10:42, Grzegorz Grzybek gr.grzy...@gmail.com wrote:
Ayache - do you try to run one of Camel's own tests, or your own?
regards
Grzegorz
2015-02-17 11:35 GMT+01:00 Ayache Khettar ayache.khet...@googlemail.com:
Hi Grzegorz
I am using Camel
Hi Grzegorz
I am using Camel version 2.13.2, which I think it should have the fixe you
pointed below.
Thanks
Ayache
On 17 February 2015 at 08:58, Grzegorz Grzybek gr.grzy...@gmail.com wrote:
Hi Ayache, what version of Camel do you use?
There was a fix to camel-blueprint tests a while ago
Hi
I am seeing random Unit tests failures - see below. These failures are
happening randomly on QA box (bit slower than dev machines). Looks
like the test hangs waiting for namespace handlers - see below.
I am testing camel blueprint using CamelBlueprintTests. Has anyone
experienced such
13 matches
Mail list logo
