Re: Intermittent test failures
Hi Claus Ibsen, Thanks for your reply. May I request you to please delete my post ASAP from the thread? (or please direct me how to do it). I am talking about below thread http://grokbase.com/t/camel/users/133b5fh1h1/intermittent-test-failures#top Thank you so much, Shency This message contains confidential and proprietary information of the sender, and is intended only for the person(s) to whom it is addressed. Any use, distribution, copying, disclosure or taking of any action in reliance upon it by any other person is strictly prohibited. If you have received this message in error, please notify the e-mail sender immediately, and delete the original message without making a copy. Monitise accepts no liability if this email harms any systems or data of the recipient (including as a result of software virus infection or where this e-mail is modified or amended in any way during or following transmission) or if this email is accessed by anyone other than the person(s) to whom it is addressed. The Monitise group includes Monitise plc (Reg. No. 6011822), Monitise Group Limited (Reg. No. 5590897), Monitise International Limited (Reg. No. 5556711), Monitise Europe Limited (Reg. No. 4831976) and Mobile Money Network Limited (Reg. No. 7153130). These companies are registered in England and Wales and their registered office address is 95 Gresham Street, London, EC2V 7NA United Kingdom.
Re: Intermittent test failures
On Wed, Mar 27, 2013 at 3:24 PM, Shency Revindran shency.revind...@monitise.com wrote: Hi Claus Ibsen, Thanks for your reply. May I request you to please delete my post ASAP from the thread? (or please direct me how to do it). I am talking about below thread http://grokbase.com/t/camel/users/133b5fh1h1/intermittent-test-failures#top Thank you so much, Shency You cannot remove/delete mails posted to the public Apache Camel mailing list. This message contains confidential and proprietary information of the sender, and is intended only for the person(s) to whom it is addressed. Any use, distribution, copying, disclosure or taking of any action in reliance upon it by any other person is strictly prohibited. If you have received this message in error, please notify the e-mail sender immediately, and delete the original message without making a copy. Monitise accepts no liability if this email harms any systems or data of the recipient (including as a result of software virus infection or where this e-mail is modified or amended in any way during or following transmission) or if this email is accessed by anyone other than the person(s) to whom it is addressed. The Monitise group includes Monitise plc (Reg. No. 6011822), Monitise Group Limited (Reg. No. 5590897), Monitise International Limited (Reg. No. 5556711), Monitise Europe Limited (Reg. No. 4831976) and Mobile Money Network Limited (Reg. No. 7153130). These companies are registered in England and Wales and their registered office address is 95 Gresham Street, London, EC2V 7NA United Kingdom. -- Claus Ibsen - Red Hat, Inc. FuseSource is now part of Red Hat Email: cib...@redhat.com Web: http://fusesource.com Twitter: davsclaus Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen
Re: Intermittent test failures
I am facing the same issue but while deploying my containers to FUSE ESB I have 2 containers, out of which any one will fail loading the camel-context. No error appart from the INFO messages below. This issue is inconsistent (rarely both containers load successfully, most time only one will load). 2013-03-23 20:31:07,679 | INFO | -3.12.0-thread-1 | BlueprintCamelContext | e.camel.impl.DefaultCamelContext 1399 | 74 - org.apache.camel.camel-core - 2.10.0.fuse-71-047 | Apache Camel 2.10.0.fuse-71-047 (CamelContext: heartbeatMonitoringContext) is starting 2013-03-23 20:31:07,771 | INFO | -3.12.0-thread-1 | Activator | BundleTypeConverterLoader$Loader 352 | 74 - org.apache.camel.camel-core - 2.10.0.fuse-71-047 | Found 2 @Converter classes to load 2013-03-23 20:31:07,775 | INFO | -3.12.0-thread-1 | Activator | BundleTypeConverterLoader$Loader 352 | 74 - org.apache.camel.camel-core - 2.10.0.fuse-71-047 | Found 0 @Converter classes to load I have the below in my import-packages in both feature's pom.xmls org.osgi.service.blueprint;version=[1.0.0,2.0.0), and dependency groupIdorg.apache.camel/groupId artifactIdcamel-blueprint/artifactId scopeprovided/scope /dependency What am I doing wrong? Gives a feeling that FUSE ESB is not reliable :(
Re: Intermittent test failures
Hi Shency You should use the Fuse Forums to ask about Fuse products, and get help with these products. This is NOT the appropriate mailing list to post these kind of questions. This mailing list is for the public Apache Camel project, and not vendor products. And yeah I say that even as an employeer working for Red Hat, and working on the Fuse products. On Sat, Mar 23, 2013 at 9:53 PM, mostwanted shency.revind...@monitise.com wrote: I am facing the same issue but while deploying my containers to FUSE ESB I have 2 containers, out of which any one will fail loading the camel-context. No error appart from the INFO messages below. This issue is inconsistent (rarely both containers load successfully, most time only one will load). 2013-03-23 20:31:07,679 | INFO | -3.12.0-thread-1 | BlueprintCamelContext | e.camel.impl.DefaultCamelContext 1399 | 74 - org.apache.camel.camel-core - 2.10.0.fuse-71-047 | Apache Camel 2.10.0.fuse-71-047 (CamelContext: heartbeatMonitoringContext) is starting 2013-03-23 20:31:07,771 | INFO | -3.12.0-thread-1 | Activator | BundleTypeConverterLoader$Loader 352 | 74 - org.apache.camel.camel-core - 2.10.0.fuse-71-047 | Found 2 @Converter classes to load 2013-03-23 20:31:07,775 | INFO | -3.12.0-thread-1 | Activator | BundleTypeConverterLoader$Loader 352 | 74 - org.apache.camel.camel-core - 2.10.0.fuse-71-047 | Found 0 @Converter classes to load I have the below in my import-packages in both feature's pom.xmls org.osgi.service.blueprint;version=[1.0.0,2.0.0), and dependency groupIdorg.apache.camel/groupId artifactIdcamel-blueprint/artifactId scopeprovided/scope /dependency What am I doing wrong? Gives a feeling that FUSE ESB is not reliable :( -- Claus Ibsen - Red Hat, Inc. FuseSource is now part of Red Hat Email: cib...@redhat.com Web: http://fusesource.com Twitter: davsclaus Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen
Re: Intermittent test failures
Thanks Claus, that was it! Since the project uses camel-blueprint and camel-blueprint-test, I made the following exclusion and the problem went away: dependency groupIdorg.apache.camel/groupId artifactIdcamel-blueprint/artifactId /dependency dependency groupIdorg.apache.camel/groupId artifactIdcamel-test-blueprint/artifactId scopetest/scope exclusions exclusion artifactIdorg.apache.aries.blueprint/artifactId groupIdorg.apache.aries.blueprint/groupId /exclusion /exclusions /dependency -- View this message in context: http://camel.465427.n5.nabble.com/Intermittent-test-failures-tp5728946p5729079.html Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Intermittent test failures
I've spent a whole day trying to get this to work, including upgrading to the latest Camel (2.11-SNAPSHOT) and ActiveMQ (5.8-SNAPSHOT) to no avail. The exact same tests work perfectly when the routes are configured in a Spring definition and tested with the help of CamelSpringTestSupport. Other posts in this forum seem to suggest that CamelBlueprintTestSupport introduces a race condition when loading the context. Despite a fix being committed for that, I wouldn't be surprised if this is causing my issue - I sometimes see duplicated lines in the log like this: [ Blueprint Extender: 1] ManagementStrategyFactory INFO JMX is disabled. [ Blueprint Extender: 3] ManagementStrategyFactory INFO JMX is disabled. [ Blueprint Extender: 1] BlueprintCamelContext INFO Apache Camel 2.10.0.fuse-71-047 (CamelContext: schedulingContext) is starting [ Blueprint Extender: 3] BlueprintCamelContext INFO Apache Camel 2.10.0.fuse-71-047 (CamelContext: schedulingContext) is starting [ Blueprint Extender: 1] Activator INFO Found 2 @Converter classes to load [ Blueprint Extender: 1] Activator INFO Found 0 @Converter classes to load [ Blueprint Extender: 3] Activator INFO Found 2 @Converter classes to load [ Blueprint Extender: 3] Activator INFO Found 0 @Converter classes to load [ Blueprint Extender: 3] StdSchedulerFactoryINFO Using default implementation for ThreadExecutor [ Blueprint Extender: 1] StdSchedulerFactoryINFO Using default implementation for ThreadExecutor -- View this message in context: http://camel.465427.n5.nabble.com/Intermittent-test-failures-tp5728946p5729024.html Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Intermittent test failures
On Tue, Mar 12, 2013 at 7:07 PM, cheekychops smithcol...@hotmail.com wrote: I've spent a whole day trying to get this to work, including upgrading to the latest Camel (2.11-SNAPSHOT) and ActiveMQ (5.8-SNAPSHOT) to no avail. The exact same tests work perfectly when the routes are configured in a Spring definition and tested with the help of CamelSpringTestSupport. Other posts in this forum seem to suggest that CamelBlueprintTestSupport introduces a race condition when loading the context. Despite a fix being committed for that, I wouldn't be surprised if this is causing my issue - I sometimes see duplicated lines in the log like this: Make sure your classpath do not have 2+ times Aries Blueprint JARs on the classpath. As they register their own blueprint extender, that could lead to 2+ extenders running at runtime, and thus you see the duplicates. [ Blueprint Extender: 1] ManagementStrategyFactory INFO JMX is disabled. [ Blueprint Extender: 3] ManagementStrategyFactory INFO JMX is disabled. [ Blueprint Extender: 1] BlueprintCamelContext INFO Apache Camel 2.10.0.fuse-71-047 (CamelContext: schedulingContext) is starting [ Blueprint Extender: 3] BlueprintCamelContext INFO Apache Camel 2.10.0.fuse-71-047 (CamelContext: schedulingContext) is starting [ Blueprint Extender: 1] Activator INFO Found 2 @Converter classes to load [ Blueprint Extender: 1] Activator INFO Found 0 @Converter classes to load [ Blueprint Extender: 3] Activator INFO Found 2 @Converter classes to load [ Blueprint Extender: 3] Activator INFO Found 0 @Converter classes to load [ Blueprint Extender: 3] StdSchedulerFactoryINFO Using default implementation for ThreadExecutor [ Blueprint Extender: 1] StdSchedulerFactoryINFO Using default implementation for ThreadExecutor -- View this message in context: http://camel.465427.n5.nabble.com/Intermittent-test-failures-tp5728946p5729024.html Sent from the Camel - Users mailing list archive at Nabble.com. -- Claus Ibsen - Red Hat, Inc. FuseSource is now part of Red Hat Email: cib...@redhat.com Web: http://fusesource.com Twitter: davsclaus Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen
Intermittent test failures
I've tried running in eclipse, on the command line, with JDK 1.6 and 1.7, all with similar results. Looking at CamelBlueprintHelper I see this comment: // Note that the tracker is not closed to keep the reference // This is buggy, as the service reference may change i think Object svc = tracker.waitForService(timeout); Is there a workaround? -- View this message in context: http://camel.465427.n5.nabble.com/Intermittent-test-failures-tp5728946.html Sent from the Camel - Users mailing list archive at Nabble.com.
