Greetings, I am upgrading my Jetty Jars and OSGI Jars from *R-Neon.1-201609071200* drop versions to *R-4.9-201809060745, *Both Artifacts used in the link below:
*https://archive.eclipse.org/equinox/drops/R-Neon.1-201609071200/index.php <https://archive.eclipse.org/equinox/drops/R-Neon.1-201609071200/index.php> * *https://download.eclipse.org/equinox/drops/R-4.9-201809060745/index.php <https://download.eclipse.org/equinox/drops/R-4.9-201809060745/index.php>* Later, I found in below forums, Jetty 9.4.X will work with ServiceLoader: *https://blog.osgi.org/2013/02/javautilserviceloader-in-osgi.html <https://blog.osgi.org/2013/02/javautilserviceloader-in-osgi.html>* *http://aries.apache.org/modules/spi-fly.html <http://aries.apache.org/modules/spi-fly.html>* So I included below-mentioned JARS in my bundles to: *org.apache.aries.spifly.dynamic.bundle(1.2.0)* *org.apache.aries.util(1.1.1)* *org.objectweb.asm.all(5.0.4)* *Now, *my bundles are satisfied in "Validate Bundles"* except this ne*wly message *org.eclipse.jetty.util:* *Missing Constraint: Require-Capability: osgi.serviceloader; filter= "(osgi.serviceloader=org.eclipse.jetty.util.security.CredentialProvider)"* However, I am ignoring this message currently, as in below bug(532294), its mentioned that* "This is an optional requirement, it shows up in diag as an unresolved requirement, but that is fine because it is optional"* https://bugs.eclipse.org/bugs/show_bug.cgi?id=532294 Now, when I am trying to boot my system with newly mentioned artifacts, after booting initial 4-5 minutes, with NO ERROR and WARNING message, its suddenly stops processing further with below message in the console *:30:04.217:WARN:oejsh.ContextHandler:ManagedServiceFactory Update Queue: Empty contextPath* *2019-02-21 19:30:04.221:INFO:oejs.session:ManagedServiceFactory Update Queue: DefaultSessionIdManager workerName=node0* *2019-02-21 19:30:04.221:INFO:oejs.session:ManagedServiceFactory Update Queue: No SessionScavenger set, using defaults* *2019-02-21 19:30:04.221:INFO:oejs.session:ManagedServiceFactory Update Queue: node0 Scavenging every 600000ms* *2019-02-21 19:30:04.237:INFO:oejs.AbstractConnector:ManagedServiceFactory Update Queue: Started ServerConnector@3493d25a{HTTP/1.1,[http/1.1]}{0.0.0.0:10022 <http://0.0.0.0:10022>}* *2019-02-21 19:30:04.238:WARN:oejsh.ContextHandler:ManagedServiceFactory Update Queue: Empty contextPath* *2019-02-21 19:30:06.077:INFO:oejs.session:ManagedServiceFactory Update Queue: DefaultSessionIdManager workerName=node0* *2019-02-21 19:30:06.077:INFO:oejs.session:ManagedServiceFactory Update Queue: No SessionScavenger set, using defaults* *2019-02-21 19:30:06.077:INFO:oejs.session:ManagedServiceFactory Update Queue: node0 Scavenging every 600000ms* *2019-02-21 19:30:06.083:INFO:oejs.AbstractConnector:ManagedServiceFactory Update Queue: Started ServerConnector@3c77ec09{HTTP/1.1,[http/1.1]}{0.0.0.0:10000 <http://0.0.0.0:10000>}* *2019-02-21 19:30:06.084:WARN:oejsh.ContextHandler:ManagedServiceFactory Update Queue: Empty contextPath* *2019-02-21 19:30:06.087:INFO:oejs.session:ManagedServiceFactory Update Queue: DefaultSessionIdManager workerName=node0* *2019-02-21 19:30:06.087:INFO:oejs.session:ManagedServiceFactory Update Queue: No SessionScavenger set, using defaults* *2019-02-21 19:30:06.087:INFO:oejs.session:ManagedServiceFactory Update Queue: node0 Scavenging every 600000ms* *2019-02-21 19:30:06.092:INFO:oejs.AbstractConnector:ManagedServiceFactory Update Queue: Started ServerConnector@35d79abf{HTTP/1.1,[http/1.1]}{0.0.0.0:10020 <http://0.0.0.0:10020>}* Earlier, in my previous version during initial bootup console screen displays these messages 2019-02-22 09:42:40.379 INFO org.eclipse.jetty.util.log - Logging initialized @20492ms 2019-02-22 09:42:40.645 INFO org.eclipse.jetty.server.Server - jetty-9.3.9.v20160517 2019-02-22 09:42:40.780 INFO o.e.j.server.handler.ContextHandler - Started o.e.j.s.ServletContextHandler@1706d9a8{/,null,AVAILABLE} 2019-02-22 09:42:40.790 INFO o.e.jetty.server.AbstractConnector - Started ServerConnector@4b8a93fd{HTTP/1.1,[http/1.1]}{0.0.0.0:8080} 2019-02-22 09:42:40.790 INFO org.eclipse.jetty.server.Server - Started @20903ms 2019-02-22 09:42:40.794 WARN o.e.j.server.handler.ContextHandler - Empty contextPath 2019-02-22 09:42:40.799 INFO org.eclipse.jetty.server.Server - jetty-9.3.9.v20160517 2019-02-22 09:42:40.913 INFO o.e.j.server.handler.ContextHandler - Started o.e.j.s.ServletContextHandler@679ed188{/,null,AVAILABLE} 2019-02-22 09:42:40.914 INFO o.e.jetty.server.AbstractConnector - Started ServerConnector@3d0e585f{HTTP/1.1,[http/1.1]}{0.0.0.0:10022} 2019-02-22 09:42:40.914 INFO org.eclipse.jetty.server.Server - Started @21028ms 2019-02-22 09:42:40.916 WARN o.e.j.server.handler.ContextHandler - Empty contextPath 2019-02-22 09:42:40.916 INFO org.eclipse.jetty.server.Server - jetty-9.3.9.v20160517 2019-02-22 09:42:40.922 INFO o.e.j.server.handler.ContextHandler - Started o.e.j.s.ServletContextHandler@6740daa6{/,null,AVAILABLE} 2019-02-22 09:42:40.923 INFO o.e.jetty.server.AbstractConnector - Started ServerConnector@57c40a65{HTTP/1.1,[http/1.1]}{0.0.0.0:10020} 2019-02-22 09:42:40.924 INFO org.eclipse.jetty.server.Server - Started @21037ms 2019-02-22 09:42:40.929 WARN o.e.j.server.handler.ContextHandler - Empty contextPath 2019-02-22 09:42:40.929 INFO org.eclipse.jetty.server.Server - jetty-9.3.9.v20160517 2019-02-22 09:42:40.942 INFO o.e.j.server.handler.ContextHandler - Started o.e.j.s.ServletContextHandler@559e4070{/,null,AVAILABLE} 2019-02-22 09:42:40.943 INFO o.e.jetty.server.AbstractConnector - Started ServerConnector@26fb16a0{HTTP/1.1,[http/1.1]}{0.0.0.0:10000} 2019-02-22 09:42:40.943 INFO org.eclipse.jetty.server.Server - Started @21056ms but, now with newly artifacts, I am getting below messages during initial bootUp 2019-02-21 19:27:30.510 INFO c.e.b.system.equinox.EquinoxHandler - ------------- START ------------- 2019-02-21 19:27:33.642:INFO::Start Level: Equinox Container: cbc14040-db64-4b47-96cd-8b61d50a80c0: Logging initialized @5683ms to org.eclipse.jetty.util.log.StdErrLog osgi> 2019-02-21 19:27:34.031:INFO:oejs.session:Start Level: Equinox Container: cbc14040-db64-4b47-96cd-8b61d50a80c0: DefaultSessionIdManager workerName=node0 2019-02-21 19:27:34.031:INFO:oejs.session:Start Level: Equinox Container: cbc14040-db64-4b47-96cd-8b61d50a80c0: No SessionScavenger set, using defaults 2019-02-21 19:27:34.033:INFO:oejs.session:Start Level: Equinox Container: cbc14040-db64-4b47-96cd-8b61d50a80c0: node0 Scavenging every 600000ms 2019-02-21 19:27:34.308 INFO o.a.s.c.IniSecurityManagerFactory - Realms have been explicitly set on the SecurityManager instance - auto-setting of realms will not occur. Configuration File not found! Skipping file based startup!! Inside Updated configuration Feb 21, 2019 7:27:34 PM org.apache.aries.spifly.BaseActivator log INFO: Examining bundle for SPI provider: org.eclipse.jetty.http Feb 21, 2019 7:27:34 PM org.apache.aries.spifly.BaseActivator log INFO: Found SPI resource: bundleentry://132.fwk504527234/META-INF/services/org.eclipse.jetty.http.HttpFieldPreEncoder Feb 21, 2019 7:27:34 PM org.apache.aries.spifly.BaseActivator log INFO: Loaded SPI provider: class org.eclipse.jetty.http.Http1FieldPreEncoder Feb 21, 2019 7:27:34 PM org.apache.aries.spifly.BaseActivator log INFO: Registered service: {org.eclipse.jetty.http.HttpFieldPreEncoder}={serviceloader.mediator=65, service.id=87, service.bundleid=132, service.scope=bundle, .org.apache.aries.spifly.provider.implclass=org.eclipse.jetty.http.Http1FieldPreEncoder} Feb 21, 2019 7:27:34 PM org.apache.aries.spifly.BaseActivator log INFO: Registered provider: org.eclipse.jetty.http.HttpFieldPreEncoder in bundle org.eclipse.jetty.http As mentioned, There is no error except this logs, Please do let me know if I am missing anything or any pointer to look into -- *Thanks\* *Abhijeet Banerjee+919910512611*
_______________________________________________ platform-dev mailing list [email protected] To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/platform-dev
