Re: Microkernel Karaf fit...
Hi Ranx, I realy like your point about the overhead of running a JVM in a Docker world ;) I think Karaf is a very good alternative to reduce this overhead and all the tooling provided by Karaf make it the perfect solution :) "Server->hypervisor->microkernel->JVM->Karaf(!)" Regards, François Papon fpa...@apache.org Le 06/02/2019 à 19:06, r...@enjekt.org a écrit : > > Is anyone aware of a microkernel running a JVM/Karaf? I think Karaf > could really take advantage of microkernels avoiding the need for > Kubernetes, Docker and so on. Karaf is uniquely qualified for this by > the fact that it has its own hooks to repositories, a console and > monitoring with things like HawtIO. If the JVM/Karaf/Felix is running > in the kernel itself and that is running on the hypervisor, there’s > not a lot of overhead. That’s a stark contrast to the world of > Kubernetes/Docker/VM/hypervisor. > > > > With microkernels and rump kernels getting a lot of attention and > development these days, there seems to be a great opportunity for > Karaf running in a microkernel’s > > > > Camel->Spring > Boot->JVM->Docker->Kubernetes->Linux->VM->hypervisor->server. > > Camel K->JVM->Docker->Kubernetes->Linux->VM->hypervisor->server. > > > > Server->hypervisor->microkernel->JVM->Karaf(!) > > > > Recently I was reading a bit more about Camel K. That’s Camel running > directly on Kubernettes sans container – no Spring Boot, Karaf/Felix, > or EAP. It’s a move in the right direction, I think, but as I think > about it Karaf seems uniquely poised to really jump to the front of > the line. James Strachan recently commented that he was concerned > about the future of the JVM due to the enormous overhead of running it > in a Docker world. > > > > It isn’t simply that Karaf/Felix can run on a JVM in the kernel space > and avoid all the other overhead. OSGi bundles and Karaf features > essentially allow one to create microservices as groups of bundles > that can be deployed to separate Karaf instances or to the same Karaf > instances. That simply isn’t possible with Spring Boot, Camel K or > other stacks. > > > > If anyone is aware of a microkernel or rump kernel or exokernel > running a JVM/Karaf I’d really appreciate a pointer. > > > > Brad > > > > >
Re: Karaf connecting via SSL Activemq
Thanks Jean Baptiste, We will perfom the changes on our connection factory and see how it goes. We use authentication on the AMQ side. Appreciate it. Best, Xavier On Wed, Feb 13, 2019 at 7:54 AM Jean-Baptiste Onofré wrote: > Hi > > The connection factory doesn't use jaas, it directly use username/password > provided in cf configuration. > > Do you use mutual authentication on amq side ? > > I just tried without problem locally. I will try with same version as > yours. > > Regards > JB > Le 12 févr. 2019, à 22:23, Xavier Medina a écrit: > >> Hi, >> >>We are using Karaf 3.0.4 , openjdk u8, ActiveMQ 5.11 as standalone on >> AWS via ssl://a.amazonaws:61617. >> >> Provide broker, userName and Pasword via features.xml >> >> >> > class="org.apache.activemq.ActiveMQConnectionFactory"> >> >> >> >> >> >> >> >> >> However when we start the bundle we are getting the following issues: >> >> ... 15 more >> 20:36:24,219 | ERROR | [xxxCreateQueue] | >> .DefaultMessageListenerContainer 904 | 164 - >> org.apache.servicemix.bundles.spring-jms - 3.2.11.RELEASE_1 | Could not >> refresh JMS Connection for destination 'xxxKaCreateQueue' - retrying in >> 5000 ms. Cause: User name [mquser] or password is invalid. >> javax.jms.JMSSecurityException: User name [mquser] or password is invalid. >> at >> org.apache.activemq.util.JMSExceptionSupport.create(JMSExceptionSupport.java:52)[115:org.apache.activemq.activemq-osgi:5.11.1] >> at >> org.apache.activemq.ActiveMQConnection.syncSendPacket(ActiveMQConnection.java:1420)[115:org.apache.activemq.activemq-osgi:5.11.1] >> at >> org.apache.activemq.ActiveMQConnection.ensureConnectionInfoSent(ActiveMQConnection.java:1521)[115:org.apache.activemq.activemq-osgi:5.11.1] >> at >> org.apache.activemq.ActiveMQConnection.start(ActiveMQConnection.java:528)[115:org.apache.activemq.activemq-osgi:5.11.1] >> at >> org.springframework.jms.listener.AbstractJmsListeningContainer.refreshSharedConnection(AbstractJmsListeningContainer.java:392)[164:org.apache.servicemix.bundles.spring-jms:3.2.11.RELEASE_1] >> at >> org.springframework.jms.listener.DefaultMessageListenerContainer.refreshConnectionUntilSuccessful(DefaultMessageListenerContainer.java:885)[164:org.apache.servicemix.bundles.spring-jms:3.2.11.RELEASE_1] >> at >> org.springframework.jms.listener.DefaultMessageListenerContainer.recoverAfterListenerSetupFailure(DefaultMessageListenerContainer.java:861)[164:org.apache.servicemix.bundles.spring-jms:3.2.11.RELEASE_1] >> at >> org.springframework.jms.listener.DefaultMessageListenerContainer$AsyncMessageListenerInvoker.run(DefaultMessageListenerContainer.java:1012)[164:org.apache.servicemix.bundles.spring-jms:3.2.11.RELEASE_1] >> at >> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)[:1.8.0_191] >> at >> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)[:1.8.0_191] >> at java.lang.Thread.run(Thread.java:748)[:1.8.0_191] >> Caused by: java.lang.SecurityException: User name [mquser] or password is >> invalid. >> at >> org.apache.activemq.security.JaasAuthenticationBroker.authenticate(JaasAuthenticationBroker.java:97) >> at >> org.apache.activemq.security.JaasAuthenticationBroker.addConnection(JaasAuthenticationBroker.java:68) >> at >> org.apache.activemq.broker.BrokerFilter.addConnection(BrokerFilter.java:99) >> at >> org.apache.activemq.broker.TransportConnection.processAddConnection(TransportConnection.java:843) >> at >> org.apache.activemq.broker.jmx.ManagedTransportConnection.processAddConnection(ManagedTransportConnection.java:77) >> at >> org.apache.activemq.command.ConnectionInfo.visit(ConnectionInfo.java:139)[115:org.apache.activemq.activemq-osgi:5.11.1] >> at >> org.apache.activemq.broker.TransportConnection.service(TransportConnection.java:330) >> at >> org.apache.activemq.broker.TransportConnection$1.onCommand(TransportConnection.java:194) >> at >> org.apache.activemq.transport.MutexTransport.onCommand(MutexTransport.java:50) >> at >> org.apache.activemq.transport.WireFormatNegotiator.onCommand(WireFormatNegotiator.java:125) >> at >> org.apache.activemq.transport.AbstractInactivityMonitor.onCommand(AbstractInactivityMonitor.java:301) >> at >> org.apache.activemq.transport.TransportSupport.doConsume(TransportSupport.java:83) >> at >> org.apache.activemq.transport.tcp.SslTransport.doConsume(SslTransport.java:145) >> at >> org.apache.activemq.transport.tcp.TcpTransport.doRun(TcpTransport.java:233)[115:org.apache.activemq.activemq-osgi:5.11.1] >> at >> org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:215)[115:org.apache.activemq.activemq-osgi:5.11.1] >> ... 1 more >> Caused by:
Re: Karaf connecting via SSL Activemq
Hi The connection factory doesn't use jaas, it directly use username/password provided in cf configuration. Do you use mutual authentication on amq side ? I just tried without problem locally. I will try with same version as yours. Regards JB Le 12 févr. 2019 à 22:23, à 22:23, Xavier Medina a écrit: >Hi, > > We are using Karaf 3.0.4 , openjdk u8, ActiveMQ 5.11 as standalone on >AWS via ssl://a.amazonaws:61617. > >Provide broker, userName and Pasword via features.xml > > >class="org.apache.activemq.ActiveMQConnectionFactory"> > > > > > > > > >However when we start the bundle we are getting the following issues: > >... 15 more >20:36:24,219 | ERROR | [xxxCreateQueue] | >.DefaultMessageListenerContainer >904 | 164 - org.apache.servicemix.bundles.spring-jms - 3.2.11.RELEASE_1 >| >Could not refresh JMS Connection for destination 'xxxKaCreateQueue' - >retrying in 5000 ms. Cause: User name [mquser] or password is invalid. >javax.jms.JMSSecurityException: User name [mquser] or password is >invalid. >at >org.apache.activemq.util.JMSExceptionSupport.create(JMSExceptionSupport.java:52)[115:org.apache.activemq.activemq-osgi:5.11.1] >at >org.apache.activemq.ActiveMQConnection.syncSendPacket(ActiveMQConnection.java:1420)[115:org.apache.activemq.activemq-osgi:5.11.1] >at >org.apache.activemq.ActiveMQConnection.ensureConnectionInfoSent(ActiveMQConnection.java:1521)[115:org.apache.activemq.activemq-osgi:5.11.1] >at >org.apache.activemq.ActiveMQConnection.start(ActiveMQConnection.java:528)[115:org.apache.activemq.activemq-osgi:5.11.1] >at >org.springframework.jms.listener.AbstractJmsListeningContainer.refreshSharedConnection(AbstractJmsListeningContainer.java:392)[164:org.apache.servicemix.bundles.spring-jms:3.2.11.RELEASE_1] >at >org.springframework.jms.listener.DefaultMessageListenerContainer.refreshConnectionUntilSuccessful(DefaultMessageListenerContainer.java:885)[164:org.apache.servicemix.bundles.spring-jms:3.2.11.RELEASE_1] >at >org.springframework.jms.listener.DefaultMessageListenerContainer.recoverAfterListenerSetupFailure(DefaultMessageListenerContainer.java:861)[164:org.apache.servicemix.bundles.spring-jms:3.2.11.RELEASE_1] >at >org.springframework.jms.listener.DefaultMessageListenerContainer$AsyncMessageListenerInvoker.run(DefaultMessageListenerContainer.java:1012)[164:org.apache.servicemix.bundles.spring-jms:3.2.11.RELEASE_1] >at >java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)[:1.8.0_191] >at >java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)[:1.8.0_191] >at java.lang.Thread.run(Thread.java:748)[:1.8.0_191] >Caused by: java.lang.SecurityException: User name [mquser] or password >is >invalid. >at >org.apache.activemq.security.JaasAuthenticationBroker.authenticate(JaasAuthenticationBroker.java:97) >at >org.apache.activemq.security.JaasAuthenticationBroker.addConnection(JaasAuthenticationBroker.java:68) >at >org.apache.activemq.broker.BrokerFilter.addConnection(BrokerFilter.java:99) >at >org.apache.activemq.broker.TransportConnection.processAddConnection(TransportConnection.java:843) >at >org.apache.activemq.broker.jmx.ManagedTransportConnection.processAddConnection(ManagedTransportConnection.java:77) >at >org.apache.activemq.command.ConnectionInfo.visit(ConnectionInfo.java:139)[115:org.apache.activemq.activemq-osgi:5.11.1] >at >org.apache.activemq.broker.TransportConnection.service(TransportConnection.java:330) >at >org.apache.activemq.broker.TransportConnection$1.onCommand(TransportConnection.java:194) >at >org.apache.activemq.transport.MutexTransport.onCommand(MutexTransport.java:50) >at >org.apache.activemq.transport.WireFormatNegotiator.onCommand(WireFormatNegotiator.java:125) >at >org.apache.activemq.transport.AbstractInactivityMonitor.onCommand(AbstractInactivityMonitor.java:301) >at >org.apache.activemq.transport.TransportSupport.doConsume(TransportSupport.java:83) >at >org.apache.activemq.transport.tcp.SslTransport.doConsume(SslTransport.java:145) >at >org.apache.activemq.transport.tcp.TcpTransport.doRun(TcpTransport.java:233)[115:org.apache.activemq.activemq-osgi:5.11.1] >at >org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:215)[115:org.apache.activemq.activemq-osgi:5.11.1] >... 1 more >Caused by: javax.security.auth.login.FailedLoginException: Password >does >not match >at >org.apache.activemq.jaas.PropertiesLoginModule.login(PropertiesLoginModule.java:92) > at sun.reflect.GeneratedMethodAccessor170.invoke(Unknown Source) >at >sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)[:1.8.0_191] >at java.lang.reflect.Method.invoke(Method.java:498)[:1.8.0_191] >at
Karaf connecting via SSL Activemq
Hi, We are using Karaf 3.0.4 , openjdk u8, ActiveMQ 5.11 as standalone on AWS via ssl://a.amazonaws:61617. Provide broker, userName and Pasword via features.xml However when we start the bundle we are getting the following issues: ... 15 more 20:36:24,219 | ERROR | [xxxCreateQueue] | .DefaultMessageListenerContainer 904 | 164 - org.apache.servicemix.bundles.spring-jms - 3.2.11.RELEASE_1 | Could not refresh JMS Connection for destination 'xxxKaCreateQueue' - retrying in 5000 ms. Cause: User name [mquser] or password is invalid. javax.jms.JMSSecurityException: User name [mquser] or password is invalid. at org.apache.activemq.util.JMSExceptionSupport.create(JMSExceptionSupport.java:52)[115:org.apache.activemq.activemq-osgi:5.11.1] at org.apache.activemq.ActiveMQConnection.syncSendPacket(ActiveMQConnection.java:1420)[115:org.apache.activemq.activemq-osgi:5.11.1] at org.apache.activemq.ActiveMQConnection.ensureConnectionInfoSent(ActiveMQConnection.java:1521)[115:org.apache.activemq.activemq-osgi:5.11.1] at org.apache.activemq.ActiveMQConnection.start(ActiveMQConnection.java:528)[115:org.apache.activemq.activemq-osgi:5.11.1] at org.springframework.jms.listener.AbstractJmsListeningContainer.refreshSharedConnection(AbstractJmsListeningContainer.java:392)[164:org.apache.servicemix.bundles.spring-jms:3.2.11.RELEASE_1] at org.springframework.jms.listener.DefaultMessageListenerContainer.refreshConnectionUntilSuccessful(DefaultMessageListenerContainer.java:885)[164:org.apache.servicemix.bundles.spring-jms:3.2.11.RELEASE_1] at org.springframework.jms.listener.DefaultMessageListenerContainer.recoverAfterListenerSetupFailure(DefaultMessageListenerContainer.java:861)[164:org.apache.servicemix.bundles.spring-jms:3.2.11.RELEASE_1] at org.springframework.jms.listener.DefaultMessageListenerContainer$AsyncMessageListenerInvoker.run(DefaultMessageListenerContainer.java:1012)[164:org.apache.servicemix.bundles.spring-jms:3.2.11.RELEASE_1] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)[:1.8.0_191] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)[:1.8.0_191] at java.lang.Thread.run(Thread.java:748)[:1.8.0_191] Caused by: java.lang.SecurityException: User name [mquser] or password is invalid. at org.apache.activemq.security.JaasAuthenticationBroker.authenticate(JaasAuthenticationBroker.java:97) at org.apache.activemq.security.JaasAuthenticationBroker.addConnection(JaasAuthenticationBroker.java:68) at org.apache.activemq.broker.BrokerFilter.addConnection(BrokerFilter.java:99) at org.apache.activemq.broker.TransportConnection.processAddConnection(TransportConnection.java:843) at org.apache.activemq.broker.jmx.ManagedTransportConnection.processAddConnection(ManagedTransportConnection.java:77) at org.apache.activemq.command.ConnectionInfo.visit(ConnectionInfo.java:139)[115:org.apache.activemq.activemq-osgi:5.11.1] at org.apache.activemq.broker.TransportConnection.service(TransportConnection.java:330) at org.apache.activemq.broker.TransportConnection$1.onCommand(TransportConnection.java:194) at org.apache.activemq.transport.MutexTransport.onCommand(MutexTransport.java:50) at org.apache.activemq.transport.WireFormatNegotiator.onCommand(WireFormatNegotiator.java:125) at org.apache.activemq.transport.AbstractInactivityMonitor.onCommand(AbstractInactivityMonitor.java:301) at org.apache.activemq.transport.TransportSupport.doConsume(TransportSupport.java:83) at org.apache.activemq.transport.tcp.SslTransport.doConsume(SslTransport.java:145) at org.apache.activemq.transport.tcp.TcpTransport.doRun(TcpTransport.java:233)[115:org.apache.activemq.activemq-osgi:5.11.1] at org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:215)[115:org.apache.activemq.activemq-osgi:5.11.1] ... 1 more Caused by: javax.security.auth.login.FailedLoginException: Password does not match at org.apache.activemq.jaas.PropertiesLoginModule.login(PropertiesLoginModule.java:92) at sun.reflect.GeneratedMethodAccessor170.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)[:1.8.0_191] at java.lang.reflect.Method.invoke(Method.java:498)[:1.8.0_191] at javax.security.auth.login.LoginContext.invoke(LoginContext.java:755) at javax.security.auth.login.LoginContext.access$000(LoginContext.java:195) at javax.security.auth.login.LoginContext$4.run(LoginContext.java:682) at javax.security.auth.login.LoginContext$4.run(LoginContext.java:680) at java.security.AccessController.doPrivileged(Native Method)[:1.8.0_191] at
Re: Strange behaviour in karaf shell
Yes, it's the workaround that I talked about (blacklist). It's temporary, I will improve this anyway. Thanks for sharing. Regards JB On 12/02/2019 14:24, Mike wrote: > Thx for the answer. Regarding to the ticket I blocked the hole repository and > fixed the problem... > > Created the file etc/org.apache.karaf.features.xml with > > > > xmlns="http://karaf.apache.org/xmlns/features-processing/v1.0.0;> > > > mvn:org.apache.karaf.features/standard/4.3.0-SNAPSHOT/xml/features > > > > > And it's working perfect again! > > I will attach it to the ticket too. > > > >> On 12. Feb 2019, at 06:51, Jean-Baptiste Onofré wrote: >> >> I checked and I think it's the same cause as >> https://issues.apache.org/jira/browse/KARAF-6151 >> >> A possible workaround is to blacklist the features. >> >> Let me double check. >> >> Regards >> JB >> >> On 12/02/2019 01:14, Mike wrote: >>> Hello, >>> >>> since round about an hour I have a very strange behaviour in the shell >>> after installation of features I can't insert commands. Looks like two (or >>> more) listeners for the stdin are active. In this example I typed 'list' >>> and press multiple times enter: >>> >>> karaf@root()> >>> karaf@root()> >>> karaf@root()> >>> karaf@root()> list >>> Command not found: s >>> karaf@root()> >>> karaf@root()> >>> karaf@root()> >>> Command not found: lit >>> karaf@root()> >>> >>> If I open a ssh console it will be fine. >>> >>> >>> >>> I already tested different features in different orders: >>> >>> feature:repo-add camel 2.20.0 >>> feature:install deployer/4.2.2 camel-blueprint/2.20.0 aries-blueprint/4.2.2 >>> >>> feature:install openjpa3 >>> >>> feature:repo-add activemq 5.15.8 >>> feature:install activemq-client >>> >>> feature:repo-add cxf >>> feature:install cxf/3.2.0 >>> >>> But I can't find a reason. Looks like the behaviour is flipping... >>> >>> >>> >>> I also found some strange karaf 4.3.0-SNAPSHOT features appearing in >>> features:list >>> >>> karaf@root()> feature:list|grep deploy >>> deployer| 4.2.2| x| >>> Started | standard-4.2.2| Karaf Deployer >>> deployer| 4.3.0.SNAPSHOT | | >>> Uninstalled | standard-4.3.0-SNAPSHOT | Karaf Deployer >>> >>> After cleanup and restart I didn't found it any more. >>> >>> >>> >>> And also >>> >>> >>> 00:00:08.331 INFO [features-3-thread-1] Starting bundles: >>> 00:00:08.332 INFO [features-3-thread-1] org.apache.aries.proxy/1.1.4 >>> 00:00:08.340 INFO [features-3-thread-1] >>> org.apache.aries.blueprint.core/1.10.1 >>> 00:00:08.379 INFO [features-3-thread-1] No quiesce support is available, >>> so blueprint components will not participate in quiesce operations >>> 00:00:08.494 INFO [features-3-thread-1] Blueprint bundle >>> org.apache.aries.blueprint.core/1.10.1 has been started >>> 00:00:08.496 INFO [features-3-thread-1] >>> org.apache.aries.blueprint.cm/1.3.1 >>> 00:00:08.515 INFO [features-3-thread-1] Blueprint bundle >>> org.apache.aries.blueprint.cm/1.3.1 has been started >>> 00:00:08.516 INFO [features-3-thread-1] >>> org.apache.karaf.deployer.kar/4.2.2 >>> 00:00:08.535 INFO [features-3-thread-1] org.apache.karaf.shell.core/4.2.2 >>> 00:00:08.582 INFO [features-3-thread-1] Registering commands for bundle >>> org.apache.karaf.deployer.kar/4.2.2 >>> 00:00:08.761 INFO [features-3-thread-1] Blueprint bundle >>> org.apache.karaf.shell.core/4.2.2 has been started >>> 00:00:08.762 INFO [features-3-thread-1] >>> org.apache.karaf.shell.core/4.3.0.SNAPSHOT >>> 00:00:08.811 INFO [features-3-thread-1] Registering commands for bundle >>> org.apache.karaf.deployer.kar/4.2.2 >>> 00:00:08.897 INFO [features-3-thread-1] Blueprint bundle >>> org.apache.karaf.shell.core/4.3.0.SNAPSHOT has been started >>> 00:00:08.899 INFO [features-3-thread-1] >>> org.apache.karaf.bundle.core/4.2.2 >>> 00:00:08.989 INFO [features-3-thread-1] Registering commands for bundle >>> org.apache.karaf.bundle.core/4.2.2 >>> 00:00:08.995 INFO [features-3-thread-1] Registering commands for bundle >>> org.apache.karaf.bundle.core/4.2.2 >>> 00:00:08.997 INFO [features-3-thread-1] >>> org.eclipse.jetty.http/9.4.12.v20180830 >>> 00:00:09.003 INFO [features-3-thread-1] >>> org.eclipse.jetty.client/9.4.12.v20180830 >>> 00:00:09.012 INFO [features-3-thread-1] >>> org.eclipse.jetty.websocket.common/9.4.12.v20180830 >>> 00:00:09.029 INFO [features-3-thread-1] >>> org.eclipse.jetty.websocket.api/9.4.12.v20180830 >>> 00:00:09.031 INFO [features-3-thread-1] >>> org.eclipse.jetty.websocket.client/9.4.12.v20180830 >>> 00:00:09.041 INFO [features-3-thread-1] >>> org.apache.servicemix.bundles.aopalliance/1.0.0.6 >>> 00:00:09.043 INFO [features-3-thread-1] >>> org.apache.servicemix.bundles.spring-core/4.3.21.RELEASE_1 >>> 00:00:09.045 INFO [features-3-thread-1] >>>
Re: Strange behaviour in karaf shell
Thx for the answer. Regarding to the ticket I blocked the hole repository and fixed the problem... Created the file etc/org.apache.karaf.features.xml with http://karaf.apache.org/xmlns/features-processing/v1.0.0;> mvn:org.apache.karaf.features/standard/4.3.0-SNAPSHOT/xml/features And it's working perfect again! I will attach it to the ticket too. > On 12. Feb 2019, at 06:51, Jean-Baptiste Onofré wrote: > > I checked and I think it's the same cause as > https://issues.apache.org/jira/browse/KARAF-6151 > > A possible workaround is to blacklist the features. > > Let me double check. > > Regards > JB > > On 12/02/2019 01:14, Mike wrote: >> Hello, >> >> since round about an hour I have a very strange behaviour in the shell after >> installation of features I can't insert commands. Looks like two (or more) >> listeners for the stdin are active. In this example I typed 'list' and press >> multiple times enter: >> >> karaf@root()> >> karaf@root()> >> karaf@root()> >> karaf@root()> list >> Command not found: s >> karaf@root()> >> karaf@root()> >> karaf@root()> >> Command not found: lit >> karaf@root()> >> >> If I open a ssh console it will be fine. >> >> >> >> I already tested different features in different orders: >> >> feature:repo-add camel 2.20.0 >> feature:install deployer/4.2.2 camel-blueprint/2.20.0 aries-blueprint/4.2.2 >> >> feature:install openjpa3 >> >> feature:repo-add activemq 5.15.8 >> feature:install activemq-client >> >> feature:repo-add cxf >> feature:install cxf/3.2.0 >> >> But I can't find a reason. Looks like the behaviour is flipping... >> >> >> >> I also found some strange karaf 4.3.0-SNAPSHOT features appearing in >> features:list >> >> karaf@root()> feature:list|grep deploy >> deployer| 4.2.2| x| >> Started | standard-4.2.2| Karaf Deployer >> deployer| 4.3.0.SNAPSHOT | | >> Uninstalled | standard-4.3.0-SNAPSHOT | Karaf Deployer >> >> After cleanup and restart I didn't found it any more. >> >> >> >> And also >> >> >> 00:00:08.331 INFO [features-3-thread-1] Starting bundles: >> 00:00:08.332 INFO [features-3-thread-1] org.apache.aries.proxy/1.1.4 >> 00:00:08.340 INFO [features-3-thread-1] >> org.apache.aries.blueprint.core/1.10.1 >> 00:00:08.379 INFO [features-3-thread-1] No quiesce support is available, so >> blueprint components will not participate in quiesce operations >> 00:00:08.494 INFO [features-3-thread-1] Blueprint bundle >> org.apache.aries.blueprint.core/1.10.1 has been started >> 00:00:08.496 INFO [features-3-thread-1] >> org.apache.aries.blueprint.cm/1.3.1 >> 00:00:08.515 INFO [features-3-thread-1] Blueprint bundle >> org.apache.aries.blueprint.cm/1.3.1 has been started >> 00:00:08.516 INFO [features-3-thread-1] >> org.apache.karaf.deployer.kar/4.2.2 >> 00:00:08.535 INFO [features-3-thread-1] org.apache.karaf.shell.core/4.2.2 >> 00:00:08.582 INFO [features-3-thread-1] Registering commands for bundle >> org.apache.karaf.deployer.kar/4.2.2 >> 00:00:08.761 INFO [features-3-thread-1] Blueprint bundle >> org.apache.karaf.shell.core/4.2.2 has been started >> 00:00:08.762 INFO [features-3-thread-1] >> org.apache.karaf.shell.core/4.3.0.SNAPSHOT >> 00:00:08.811 INFO [features-3-thread-1] Registering commands for bundle >> org.apache.karaf.deployer.kar/4.2.2 >> 00:00:08.897 INFO [features-3-thread-1] Blueprint bundle >> org.apache.karaf.shell.core/4.3.0.SNAPSHOT has been started >> 00:00:08.899 INFO [features-3-thread-1] org.apache.karaf.bundle.core/4.2.2 >> 00:00:08.989 INFO [features-3-thread-1] Registering commands for bundle >> org.apache.karaf.bundle.core/4.2.2 >> 00:00:08.995 INFO [features-3-thread-1] Registering commands for bundle >> org.apache.karaf.bundle.core/4.2.2 >> 00:00:08.997 INFO [features-3-thread-1] >> org.eclipse.jetty.http/9.4.12.v20180830 >> 00:00:09.003 INFO [features-3-thread-1] >> org.eclipse.jetty.client/9.4.12.v20180830 >> 00:00:09.012 INFO [features-3-thread-1] >> org.eclipse.jetty.websocket.common/9.4.12.v20180830 >> 00:00:09.029 INFO [features-3-thread-1] >> org.eclipse.jetty.websocket.api/9.4.12.v20180830 >> 00:00:09.031 INFO [features-3-thread-1] >> org.eclipse.jetty.websocket.client/9.4.12.v20180830 >> 00:00:09.041 INFO [features-3-thread-1] >> org.apache.servicemix.bundles.aopalliance/1.0.0.6 >> 00:00:09.043 INFO [features-3-thread-1] >> org.apache.servicemix.bundles.spring-core/4.3.21.RELEASE_1 >> 00:00:09.045 INFO [features-3-thread-1] >> org.apache.servicemix.bundles.spring-beans/4.3.21.RELEASE_1 >> 00:00:09.047 INFO [features-3-thread-1] >> org.apache.servicemix.bundles.spring-aop/4.3.21.RELEASE_1 >> 00:00:09.049 INFO [features-3-thread-1] >> org.apache.servicemix.bundles.spring-expression/4.3.21.RELEASE_1 >> 00:00:09.051 INFO [features-3-thread-1] >>
