The problem occurs in master too. We could upgrade to ActiveMQ 5.10.0 (as it seem not to introduce new problems) and wait for next Karaf version fixing the deploy issue. I haven't tested it with Karaf 3.0.0, but I think we can simple wait for new Karaf as we can release 6.0.0 later.
On 13.06.2014 13:12, Jean-Baptiste Onofré wrote: > Hi Krzysztof > > I just tested and it looks better, thanks. > > +1 to commit/push. > > Regards > JB > > On 06/12/2014 09:33 PM, Krzysztof Sobkowiak wrote: >> Hi >> >> I have pushed in my Github repo a new branch >> (https://github.com/sobkowiak/servicemix/tree/ActiveMQ-5.10.0) >> containing following changes >> >> * downgrade Karaf to 2.3.4 (to avoid the issue introduced with 2.3.5) >> * upgraded ActiveMQ to 2.10.0 >> * remove the ActiveMQ web console workaround (SM-2303 >> <https://issues.apache.org/jira/browse/SM-2303>) >> >> Please feel free to checkout this branch and test. We can find eventual >> new issues introduced with 2.10.0. >> >> Best regards >> Krzysztof >> >> >> On 12.06.2014 11:30, Benjamin Graf (JIRA) wrote: >>> Benjamin Graf created SM-2328: >>> --------------------------------- >>> >>> Summary: Upgrade to ActiveMQ 5.10.0 >>> Key: SM-2328 >>> URL: https://issues.apache.org/jira/browse/SM-2328 >>> Project: ServiceMix >>> Issue Type: Task >>> Components: assemblies >>> Reporter: Benjamin Graf >>> >>> >>> >>> >>> >>> >>> -- >>> This message was sent by Atlassian JIRA >>> (v6.2#6252) >> >> > -- 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 Calendar: goo.gl/yvsebC
