Re: Remote shell?
That got me to: java.lang.NullPointerException at java.util.Objects.requireNonNull(Objects.java:203) at org.jline.reader.impl.LineReaderImpl.(LineReaderImpl.java:262) at org.jline.reader.LineReaderBuilder.build(LineReaderBuilder.java:90) at org.apache.felix.gogo.jline.Shell.gosh(Shell.java:297) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:497) at org.apache.felix.gogo.runtime.Reflective.invoke(Reflective.java:136) at org.apache.felix.gogo.runtime.CommandProxy.execute(CommandProxy.java:82) at org.apache.felix.gogo.runtime.Closure.executeCmd(Closure.java:548) at org.apache.felix.gogo.runtime.Closure.executeStatement(Closure.java:474) at org.apache.felix.gogo.runtime.Closure.execute(Closure.java:363) at org.apache.felix.gogo.runtime.Pipe.doCall(Pipe.java:417) at org.apache.felix.gogo.runtime.Pipe.call(Pipe.java:227) at org.apache.felix.gogo.runtime.Pipe.call(Pipe.java:59) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) Let me try adding the non-jline bundle, but I really want jline for local usage. On Thu, Nov 17, 2016 at 1:19 AM, Benson Margulieswrote: > Caused by: java.lang.ClassNotFoundException: *** Class > 'org.apache.felix.service.command.CommandProcessor' was not found > because bundle org.apache.felix.shell.remote [210] does not import > 'org.apache.felix.service.command' even though bundle > [org.apache.felix.gogo.runtime [6](R 6.0)] osgi.wiring.package; > {bundle-symbolic-name=org.apache.felix.gogo.runtime, > bundle-version=1.0.0, version=1.0.0, > osgi.wiring.package=org.apache.felix.service.command} does export it. > To resolve this issue, add an import for > 'org.apache.felix.service.command' to bundle > org.apache.felix.shell.remote [210]. *** > > So, there's a dynamic import there. Maybe I just need to remove > 'provisional' from it? > > > On Thu, Nov 17, 2016 at 1:09 AM, Benson Margulies > wrote: >> Any chance of a remote shell release that supports 1.0.0 of the rest of gogo? >> >> I could make some commits, but it's not neighborhood I've been seen in. - To unsubscribe, e-mail: users-unsubscr...@felix.apache.org For additional commands, e-mail: users-h...@felix.apache.org
Re: Remote shell?
Caused by: java.lang.ClassNotFoundException: *** Class 'org.apache.felix.service.command.CommandProcessor' was not found because bundle org.apache.felix.shell.remote [210] does not import 'org.apache.felix.service.command' even though bundle [org.apache.felix.gogo.runtime [6](R 6.0)] osgi.wiring.package; {bundle-symbolic-name=org.apache.felix.gogo.runtime, bundle-version=1.0.0, version=1.0.0, osgi.wiring.package=org.apache.felix.service.command} does export it. To resolve this issue, add an import for 'org.apache.felix.service.command' to bundle org.apache.felix.shell.remote [210]. *** So, there's a dynamic import there. Maybe I just need to remove 'provisional' from it? On Thu, Nov 17, 2016 at 1:09 AM, Benson Margulieswrote: > Any chance of a remote shell release that supports 1.0.0 of the rest of gogo? > > I could make some commits, but it's not neighborhood I've been seen in. - To unsubscribe, e-mail: users-unsubscr...@felix.apache.org For additional commands, e-mail: users-h...@felix.apache.org
Remote shell?
Any chance of a remote shell release that supports 1.0.0 of the rest of gogo? I could make some commits, but it's not neighborhood I've been seen in. - To unsubscribe, e-mail: users-unsubscr...@felix.apache.org For additional commands, e-mail: users-h...@felix.apache.org
Re: webconsole and felix http not getting along.
Thanks to inspect, I ee that that the http service offers itself twice, once on each port. In fact, it is not listening on 8080. org.apache.felix.http.jetty [66] provides: -- service; org.osgi.service.metatype.MetaTypeProvider with properties: metatype.pid = org.apache.felix.http service.bundleid = 66 service.description = Metatype provider for Jetty Http Service service.id = 70 service.scope = bundle service.vendor = The Apache Software Foundation Used by: org.apache.felix.metatype [7] service; org.osgi.service.http.HttpService, org.apache.felix.http.api.ExtHttpService with properties: org.apache.felix.http.enable = true org.apache.felix.https.enable = false org.osgi.service.http.port = 8080 org.osgi.service.http.port.secure = 8443 osgi.http.endpoint = http://10.1.224.6:8080/, http://172.16.2.223:8080/ osgi.http.service.endpoints = http://10.1.224.6:8080/, http://172.16.2.223:8080/ service.bundleid = 66 service.id = 71 service.scope = bundle service; org.osgi.service.http.runtime.HttpServiceRuntime with properties: org.apache.felix.http.enable = true org.apache.felix.https.enable = false org.osgi.service.http.port = 8080 org.osgi.service.http.port.secure = 8443 osgi.http.endpoint = http://10.1.224.6:8080/, http://172.16.2.223:8080/ osgi.http.service.id = [71] service.bundleid = 66 service.id = 72 service.scope = singleton service; org.osgi.service.http.context.ServletContextHelper with properties: osgi.http.whiteboard.context.name = default osgi.http.whiteboard.context.path = / service.bundleid = 66 service.id = 73 service.ranking = -2147483648 service.scope = bundle Used by: org.apache.felix.http.jetty [66] service; javax.servlet.Servlet with properties: felix.webconsole.configprinter.modes = always felix.webconsole.label = httpservice felix.webconsole.title = HTTP Service service.bundleid = 66 service.description = HTTP Service Web Console Plugin service.id = 74 service.scope = singleton service.vendor = Apache Software Foundation service; org.osgi.service.cm.ManagedService with properties: service.bundleid = 66 service.id = 75 service.pid = org.apache.felix.http service.scope = bundle Used by: org.apache.felix.metatype [7] org.apache.felix.configadmin [4] service; org.apache.felix.http.jetty.LoadBalancerCustomizerFactory with properties: service.bundleid = 66 service.description = Load Balancer Customizer Factory for Jetty Http Service service.id = 76 service.scope = bundle service.vendor = The Apache Software Foundation service; org.osgi.service.cm.ManagedServiceFactory with properties: service.bundleid = 66 service.id = 77 service.pid = org.apache.felix.http service.scope = singleton Used by: org.apache.felix.metatype [7] service; org.osgi.service.http.HttpService, org.apache.felix.http.api.ExtHttpService with properties: org.apache.felix.http.enable = true org.apache.felix.https.enable = false org.osgi.service.http.port = 8183 org.osgi.service.http.port.secure = 8443 osgi.http.endpoint = http://10.1.224.6:8182/, http://172.16.2.223:8182/ osgi.http.service.endpoints = http://10.1.224.6:8182/, http://172.16.2.223:8182/ service.bundleid = 66 service.id = 78 service.scope = bundle service; org.osgi.service.http.runtime.HttpServiceRuntime with properties: org.apache.felix.http.enable = true org.apache.felix.https.enable = false org.osgi.service.http.port = 8183 org.osgi.service.http.port.secure = 8443 osgi.http.endpoint = http://10.1.224.6:8182/, http://172.16.2.223:8182/ osgi.http.service.id = [78] service.bundleid = 66 service.id = 79 service.scope = singleton service; org.osgi.service.http.context.ServletContextHelper with properties: osgi.http.whiteboard.context.name = default osgi.http.whiteboard.context.path = / service.bundleid = 66 service.id = 80 service.ranking = -2147483648 service.scope = bundle service; javax.servlet.Servlet with properties: felix.webconsole.configprinter.modes = always felix.webconsole.label = httpservice felix.webconsole.title = HTTP Service service.bundleid = 66 service.description = HTTP Service Web Console Plugin service.id = 81 service.scope = singleton service.vendor = Apache Software Foundation On Wed, Nov 16, 2016 at 8:10 AM, Benson Margulieswrote: > I've got the latest version of Felix HTTP and the web console loaded > in 5.6.1 of the framework. > > The web console's tracker is never notified of the HTTP service. > > I note that the HTTP service first starts on 8080, then notices the > config admin config, shuts down 8080, and starts where desired. This > is, however, probably not what's causing the problem. > > I wonder if I've managed to get two different bundles to export the > http service interface somehow;
webconsole and felix http not getting along.
I've got the latest version of Felix HTTP and the web console loaded in 5.6.1 of the framework. The web console's tracker is never notified of the HTTP service. I note that the HTTP service first starts on 8080, then notices the config admin config, shuts down 8080, and starts where desired. This is, however, probably not what's causing the problem. I wonder if I've managed to get two different bundles to export the http service interface somehow; using the stock gogo commands, is there any way to explore that? - To unsubscribe, e-mail: users-unsubscr...@felix.apache.org For additional commands, e-mail: users-h...@felix.apache.org