The sentence 'I'll open an issue today in the evening.' was for the problem with with activiti itests, not for SM-2285 - this issue we have already :)
-------- Original Message -------- Subject: Re: How about a 5.0.1 and 5.1.0 release? Date: Wed, 30 Apr 2014 12:06:00 +0200 From: Sobkowiak, Krzysztof <[email protected]> To: [email protected] Hi Gert I have found this problem too. There is another reason. The problem with intermittent test failures can be solved by setting the PerMethod reactor strategy. I'm testing it locally by starting more test runs in itests and I can not reprodice this problem anymore (after changing the strategy). It looks like there is a timing problem with the new Camel. In the log you can see the example bundle is started. The bundle is next stopped, but the routes are not started before. The problem with freezing ServiceMix when installing the Drools example is caused by installed eventadmin (SM-2282 <https://issues.apache.org/jira/browse/SM-2282>) feature. From the same reason the activiti feature freezes the ServiceMix too. In both cases ServiceMix freezes when the refresh of the Spring bundles starts. I think we should revert the change from SM-2282 <https://issues.apache.org/jira/browse/SM-2282> (if we want to release soon) to solve the problem with installing the drools and activiti bundles and try to solve the problem with eventadmin later (eventadmin is necessary for the activemq console). I wanted to open a new issue but I had last days no time for it. The installed eventadmin has probably no impact on the Camel Drools sampmle itest, because the failure happens also when the eventadmin is not installed. Eventadmin should have no impact because the bundle refresh is disabled in itests. I'm going to open issue for this problem I have tried to solve the problem with activemq console but with no success. After fresh install of the console it works. After restart the properties from the cfg file are ignored. I tried to change the default user in Karaf and install the console in Karaf. I had the same effect. It is probably a problem in activemq console. I have found also this AMQ-4949 <https://issues.apache.org/jira/browse/AMQ-4949> which can be connected with this problem. But there is another problem which looks similar (SM-2285) After ServiceMix restart the properties from ConfigAdmin are not used. I haven't to much time to analyse this problem. *I'll open an issue today in the evening.* I have found one additional problem. The activiti sample has also intermittent failures (with eventadmin or without eventadmin installed). But I can see in the log file the log entries which the test case thinks are missing. Is it possible that the test case waits to short time for the log entry? This problem happens very intermittently. I think, we should release soon to get feedback for the Camel and Karaf upgrade. Best regards Krzysztof On 30.04.2014 11:31, Gert Vanthienen wrote: > L.S., > > > How about doing a 5.0.1 release somewhere in the next few days? It's > a bit over a month since we did 5.0.0 and in the meanwhile, we fixed a > few bugs and have upgraded Karaf and Activiti, so that's worth a new > release imho. > > Also, I'd like to be able to wrap up for the 5.1.0 release and get a > ServiceMix release with Camel 2.13 out. One of the main things > remaining there appears to be the problem with the Camel Drools > example - that example not only causes the itests to fail > intermittently, it looks like we also have a problem when installing > the example in the actual container. > > > Regards, > > Gert Vanthienen -- Krzysztof Sobkowiak JEE & OSS Architect | Technical Architect @ Capgemini Capgemini <http://www.pl.capgemini.com/> | Software Solutions Center <http://www.pl.capgemini-sdm.com/> | Wroclaw e-mail: [email protected] <mailto:[email protected]> | Twitter: @KSobkowiak
