RE: Unable to start Pax-Web 8.0.6 by using PFX Certificate.
Grzegorz Grzybek,
Thank you so much for looking into this.
What is you $KARAF_HOME/etc/org.ops4j.pax.web.cfg configuration?
There is no password in org.ops4j.pax.web.cfg file. It was reading external
configuration file. Which is jetty xml file.
$KARAF_HOME/etc/org.ops4j.pax.web.cfg file :-
org.osgi.service.http.port=8181
org.osgi.service.http.secure.enabled=true
org.osgi.service.http.port.secure=8443
org.ops4j.pax.web.listening.addresses=127.0.0.1
org.ops4j.pax.web.config.file = ${karaf.home}/etc/jetty.xml
org.ops4j.pax.web.session.timeout=30
$KARAF_HOME/etc/jetty.xml file :-
/etc/keystores/bems.pfx
/etc/keystores/bems.pfx
OBF: password will generate after
compilation
OBF: : password will generate after
compilation
OBF: : password will generate after
compilation
PKCS12
PKCS12
TLSv1.1
TLSv1
SSL
SSLv2
SSLv2Hello
SSLv3
Thanks,
Vamsi Krishna.
From: Vamsikrishna Koka
Sent: 13 January 2023 00:42
To: u...@karaf.apache.org; iss...@karaf.apache.org; dev@karaf.apache.org
Subject: RE: Unable to start Pax-Web 8.0.6 by using PFX Certificate.
Hi Team,
I have migrated karaf version 4.4.1 and OpenJDK 11 also. Tried to using PFX
file but it was failed due to given below stack trace.
Please can anyone take look at once.
2023-01-12T12:53:03.265-0500 CEF:1 | org.eclipse.jetty.util | 9.4.48.v20220622
| WARN | ID=245 THR=ange controller) CAT=AbstractLifeCycle
MSG=FAILED
Server@21d6680d{FAILED}[9.4.48.v20220622<mailto:Server@21d6680d%7bFAILED%7d[9.4.48.v20220622>]:
java.lang.NullPointerException
java.lang.NullPointerException: null
at
org.eclipse.jetty.util.ssl.SslContextFactory.getKeyManagers(SslContextFactory.java:1249)
~[?:?]
at
org.eclipse.jetty.util.ssl.SslContextFactory$Server.getKeyManagers(SslContextFactory.java:2364)
~[?:?]
at
org.eclipse.jetty.util.ssl.SslContextFactory.load(SslContextFactory.java:373)
~[?:?]
at
org.eclipse.jetty.util.ssl.SslContextFactory.doStart(SslContextFactory.java:244)
~[?:?]
at
org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:73)
~[?:?]
at
org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:169)
~[?:?]
at
org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:117)
~[?:?]
at
org.eclipse.jetty.server.SslConnectionFactory.doStart(SslConnectionFactory.java:97)
~[?:?]
at
org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:73)
~[?:?]
at
org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:169)
~[?:?]
at
org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:117)
~[?:?]
at
org.eclipse.jetty.server.AbstractConnector.doStart(AbstractConnector.java:323)
~[?:?]
at
org.eclipse.jetty.server.AbstractNetworkConnector.doStart(AbstractNetworkConnector.java:81)
~[?:?]
at
org.eclipse.jetty.server.ServerConnector.doStart(ServerConnector.java:234)
~[?:?]
at
org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:73)
~[?:?]
at org.eclipse.jetty.server.Server.doStart(Server.java:401) ~[?:?]
at
org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:73)
~[?:?]
at
org.ops4j.pax.web.service.jetty.internal.JettyServerWrapper.start(JettyServerWrapper.java:623)
~[?:?]
at
org.ops4j.pax.web.service.jetty.internal.JettyServerController.start(JettyServerController.java:109)
~[?:?]
at
org.ops4j.pax.web.service.internal.Activator.performConfiguration(Activator.java:551)
~[?:?]
at
org.ops4j.pax.web.service.internal.Activator.updateController(Activator.java:441)
~[?:?]
at
org.ops4j.pax.web.service.internal.Activator.lambda$updateServerControllerFactory$1(Activator.java:347)
~[?:?]
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515) ~[?:?]
at java.util.concurrent.FutureTask.run(FutureTask.java:264) ~[?:?]
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304)
~[?:?]
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
~[?:?]
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
~[?:?]
at java.lang.Thread.run(Thread.java:829) ~[?:?]
2023-01-12T12:53:03.281-0500 CEF:1 | org.ops4j.pax.web.pax-web-runtime | 8.0.6
| ERROR | ID=274 THR=ange controller) CAT=Activator
MSG=Unable to start P
RE: Unable to start Pax-Web 8.0.6 by using PFX Certificate.
va:323)
~[?:?]
at
org.eclipse.jetty.server.AbstractNetworkConnector.doStart(AbstractNetworkConnector.java:81)
~[?:?]
at
org.eclipse.jetty.server.ServerConnector.doStart(ServerConnector.java:234)
~[?:?]
at
org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:73)
~[?:?]
at org.eclipse.jetty.server.Server.doStart(Server.java:401) ~[?:?]
at
org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:73)
~[?:?]
at
org.ops4j.pax.web.service.jetty.internal.JettyServerWrapper.start(JettyServerWrapper.java:623)
~[?:?]
at
org.ops4j.pax.web.service.jetty.internal.JettyServerController.start(JettyServerController.java:109)
~[?:?]
at
org.ops4j.pax.web.service.internal.Activator.performConfiguration(Activator.java:551)
~[?:?]
at
org.ops4j.pax.web.service.internal.Activator.updateController(Activator.java:441)
~[?:?]
at
org.ops4j.pax.web.service.internal.Activator.lambda$updateServerControllerFactory$1(Activator.java:347)
~[?:?]
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515) ~[?:?]
at java.util.concurrent.FutureTask.run(FutureTask.java:264) ~[?:?]
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304)
~[?:?]
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
~[?:?]
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
~[?:?]
at java.lang.Thread.run(Thread.java:829) ~[?:?]
Thanks,
Vamsi Krishna.
From: Vamsikrishna Koka
Sent: Friday, January 13, 2023 12:38 AM
To: u...@karaf.apache.org; iss...@karaf.apache.org
Subject: Unable to start Pax-Web 8.0.6 due to PFX Certificate.
Hi Team,
I have migrated karaf version 4.4.1 and OpenJDK 11 also. Tried to using PFX
file but it was failed due to given below stack trace.
Please can anyone take look at once.
2023-01-12T12:53:03.265-0500 CEF:1 | org.eclipse.jetty.util | 9.4.48.v20220622
| WARN | ID=245 THR=ange controller) CAT=AbstractLifeCycle
MSG=FAILED
Server@21d6680d{FAILED}[9.4.48.v20220622<mailto:Server@21d6680d%7bFAILED%7d[9.4.48.v20220622>]:
java.lang.NullPointerException
java.lang.NullPointerException: null
at
org.eclipse.jetty.util.ssl.SslContextFactory.getKeyManagers(SslContextFactory.java:1249)
~[?:?]
at
org.eclipse.jetty.util.ssl.SslContextFactory$Server.getKeyManagers(SslContextFactory.java:2364)
~[?:?]
at
org.eclipse.jetty.util.ssl.SslContextFactory.load(SslContextFactory.java:373)
~[?:?]
at
org.eclipse.jetty.util.ssl.SslContextFactory.doStart(SslContextFactory.java:244)
~[?:?]
at
org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:73)
~[?:?]
at
org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:169)
~[?:?]
at
org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:117)
~[?:?]
at
org.eclipse.jetty.server.SslConnectionFactory.doStart(SslConnectionFactory.java:97)
~[?:?]
at
org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:73)
~[?:?]
at
org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:169)
~[?:?]
at
org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:117)
~[?:?]
at
org.eclipse.jetty.server.AbstractConnector.doStart(AbstractConnector.java:323)
~[?:?]
at
org.eclipse.jetty.server.AbstractNetworkConnector.doStart(AbstractNetworkConnector.java:81)
~[?:?]
at
org.eclipse.jetty.server.ServerConnector.doStart(ServerConnector.java:234)
~[?:?]
at
org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:73)
~[?:?]
at org.eclipse.jetty.server.Server.doStart(Server.java:401) ~[?:?]
at
org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:73)
~[?:?]
at
org.ops4j.pax.web.service.jetty.internal.JettyServerWrapper.start(JettyServerWrapper.java:623)
~[?:?]
at
org.ops4j.pax.web.service.jetty.internal.JettyServerController.start(JettyServerController.java:109)
~[?:?]
at
org.ops4j.pax.web.service.internal.Activator.performConfiguration(Activator.java:551)
~[?:?]
at
org.ops4j.pax.web.service.internal.Activator.updateController(Activator.java:441)
~[?:?]
at
org.ops4j.pax.web.service.internal.Activator.lambda$updateServerControllerFactory$1(Activator.java:347)
~[?:?]
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515) ~[?:?]
at java.util.concurrent.FutureTask.run(FutureTask.java:264) ~[?:?]
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304)
~[?:?]
at
java.util.concurrent.ThreadPoolExecut
RE: Issue with KARAF 4.4.1 And OpenJDK 11 (JAX-WS)
Thank you so much Matt for looking into this. Yes, I'm using Apache CXF. "The CXF feature has xml-specs feature that it installs by default that covers this for you." The CXF feature has Xml-specs feature by default installation, when we expect this. From: Vamsikrishna Koka Sent: Wednesday, December 7, 2022 1:04 PM To: iss...@karaf.apache.org; u...@karaf.apache.org; dev@karaf.apache.org Subject: Issue with KARAF 4.4.1 And OpenJDK 11 (JAX-WS) Hi Team, I have tried to migrating from KARAF 4.2.15 to KARAF 4.4.1 version along with OpenJDK also. From OpenJDK 8 to OpenJDK 11 (JAX-WS). In OpenJDK 11 removed support of JAX-WS, So I have added explicitly in pom xml. After adding I'm getting the above wiring issue. which is given below. Caused by: org.apache.felix.resolver.reason.ReasonException: Unable to resolve adapter/51.0.0.SNAPSHOT: missing requirement [adapter/51.0.0.SNAPSHOT] osgi.wiring.package; filter:="(&(osgi.wiring.package=javax.jws). Please can anyone take look at once. Thanks, Vamsi Krishna.
Issue with KARAF 4.4.1 And OpenJDK 11 (JAX-WS)
Hi Team, I have tried to migrating from KARAF 4.2.15 to KARAF 4.4.1 version along with OpenJDK also. From OpenJDK 8 to OpenJDK 11 (JAX-WS). In OpenJDK 11 removed support of JAX-WS, So I have added explicitly in pom xml. After adding I'm getting the above wiring issue. which is given below. Caused by: org.apache.felix.resolver.reason.ReasonException: Unable to resolve adapter/51.0.0.SNAPSHOT: missing requirement [adapter/51.0.0.SNAPSHOT] osgi.wiring.package; filter:="(&(osgi.wiring.package=javax.jws). Please can anyone take look at once. Thanks, Vamsi Krishna.
Issue with KARAF 4.4.1 And OpenJDK 11 (JAX-WS)
Hi Team, I have tried to migrating from KARAF 4.2.15 to KARAF 4.4.1 version along with OpenJDK also. From OpenJDK 8 to OpenJDK 11 (JAX-WS). In OpenJDK 11 removed support of JAX-WS, So I have added explicitly in pom xml. After adding I'm getting the above wiring issue. which is given below. Caused by: org.apache.felix.resolver.reason.ReasonException: Unable to resolve adapter/51.0.0.SNAPSHOT: missing requirement [adapter/51.0.0.SNAPSHOT] osgi.wiring.package; filter:="(&(osgi.wiring.package=javax.jws). Please can any one take look at once. Thanks, Vamsi Krishna.
RE: Issue with org.eclipse.jetty.server (9.4.46.v20220331) and Pax Web (8.0.6) in KARAF 4.4.1
r.java:80)
~[?:?]
at
org.eclipse.jetty.server.ServerConnector.doStart(ServerConnector.java:234)
~[?:?]
at
org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:73)
~[?:?]
at org.eclipse.jetty.server.Server.doStart(Server.java:401) ~[?:?]
at
org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:73)
~[?:?]
at
org.ops4j.pax.web.service.jetty.internal.JettyServerWrapper.start(JettyServerWrapper.java:623)
~[?:?]
at
org.ops4j.pax.web.service.jetty.internal.JettyServerController.start(JettyServerController.java:109)
~[?:?]
at
org.ops4j.pax.web.service.internal.Activator.performConfiguration(Activator.java:551)
~[?:?]
at
org.ops4j.pax.web.service.internal.Activator.updateController(Activator.java:441)
~[?:?]
at
org.ops4j.pax.web.service.internal.Activator.lambda$updateServerControllerFactory$1(Activator.java:347)
~[?:?]
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515) ~[?:?]
at java.util.concurrent.FutureTask.run(FutureTask.java:264) ~[?:?]
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304)
~[?:?]
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
~[?:?]
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
~[?:?]
at java.lang.Thread.run(Thread.java:834) ~[?:?]
Caused by: java.net.BindException: Address already in use: bind
at sun.nio.ch.Net.bind0(Native Method) ~[?:?]
at sun.nio.ch.Net.bind(Net.java:461) ~[?:?]
at sun.nio.ch.Net.bind(Net.java:453) ~[?:?]
at
sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:227) ~[?:?]
at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:80)
~[?:?]
at
org.eclipse.jetty.server.ServerConnector.openAcceptChannel(ServerConnector.java:344)
~[?:?]
... 17 more
Thanks
From: Vamsikrishna Koka
Sent: Monday, November 7, 2022 3:55 PM
To: iss...@karaf.apache.org; dev@karaf.apache.org
Subject: Issue with org.eclipse.jetty.server (9.4.46.v20220331) and Pax Web
(8.0.6) in KARAF 4.4.1
Hi Team,
I have migrated KARAF (from 4.2.15 to 4.4.1) and JDK (Open JDK 8 to OpenJDK 11)
along with required dependency also. As per KARAF release NOTE.
There is issue with jetty xml configuration and org.ops4j.pax.web.cfg.
Jetty.xml file
127.0.0.1:8443
org.ops4j.pax.web.cfg
org.osgi.service.http.port=8181
org.osgi.service.http.secure.enabled=true
org.osgi.service.http.port.secure=8443
org.ops4j.pax.web.listening.addresses=127.0.0.1
org.ops4j.pax.web.config.file = ${karaf.home}/etc/jetty.xml
org.ops4j.pax.web.session.timeout=30
The above configuration perfectly working on KARAF 4.2.15 version both jetty
9.4.43 and pax web 7.2.29. So, I have migrated jetty and Pax web dependency
part of the KARAF upgrade 4.4.1 version.
Tried to start KARAF 4.4.1 server on console logs, I have seen More than one
HttpConfiguration found in external Jetty configuration. Using
HttpConfiguration and Failed to bind to /127.0.0.1:8443. Understand some where
latest PAX Web also started container with port 8443. If I change port my login
page does not able to land on browser.
Difference b/w Pax-Web 7.2.29 and 8.0.6 version.
Pax-Web 7.2.29
OPS4J Pax Web - APIorg.ops4j.pax.web.pax-web-api
7.2.29 Active
OPS4J Pax Web - Deployment Descriptor Modelorg.ops4j.pax.web.pax-web-descriptor
7.2.29 Active
OPS4J Pax Web - Extender - WARorg.ops4j.pax.web.pax-web-extender-war
7.2.29 Active
OPS4J Pax Web - Extender -
Whiteboardorg.ops4j.pax.web.pax-web-extender-whiteboard 7.2.29 Active
OPS4J Pax Web - FileInstall Deployerorg.ops4j.pax.web.pax-web-deployer
7.2.29 Active
OPS4J Pax Web - Jettyorg.ops4j.pax.web.pax-web-jetty
7.2.29 Active
OPS4J Pax Web - Jsp Supportorg.ops4j.pax.web.pax-web-jsp7.2.29
Active
OPS4J Pax Web - Runtimeorg.ops4j.pax.web.pax-web-runtime 7.2.29
Active
OPS4J Pax Web - Service SPIorg.ops4j.pax.web.pax-web-spi 7.2.29
Active
karaf@root()> list -s -t 0 | grep "org.ops4j.pax.web"
252 | Active | 30 | 8.0.6 | org.ops4j.pax.web.pax-web-api
253 |
Issue with org.eclipse.jetty.server (9.4.46.v20220331) and Pax Web (8.0.6) in KARAF 4.4.1
Hi Team,
I have migrated KARAF (from 4.2.15 to 4.4.1) and JDK (Open JDK 8 to OpenJDK 11)
along with required dependency also. As per KARAF release NOTE.
There is issue with jetty xml configuration and org.ops4j.pax.web.cfg.
Jetty.xml file
127.0.0.1:8443
org.ops4j.pax.web.cfg
org.osgi.service.http.port=8181
org.osgi.service.http.secure.enabled=true
org.osgi.service.http.port.secure=8443
org.ops4j.pax.web.listening.addresses=127.0.0.1
org.ops4j.pax.web.config.file = ${karaf.home}/etc/jetty.xml
org.ops4j.pax.web.session.timeout=30
The above configuration perfectly working on KARAF 4.2.15 version both jetty
9.4.43 and pax web 7.2.29. So, I have migrated jetty and Pax web dependency
part of the KARAF upgrade 4.4.1 version.
Tried to start KARAF 4.4.1 server on console logs, I have seen More than one
HttpConfiguration found in external Jetty configuration. Using
HttpConfiguration and Failed to bind to /127.0.0.1:8443. Understand some where
latest PAX Web also started container with port 8443. If I change port my login
page does not able to land on browser.
Difference b/w Pax-Web 7.2.29 and 8.0.6 version.
Pax-Web 7.2.29
OPS4J Pax Web - APIorg.ops4j.pax.web.pax-web-api
7.2.29 Active
OPS4J Pax Web - Deployment Descriptor Modelorg.ops4j.pax.web.pax-web-descriptor
7.2.29 Active
OPS4J Pax Web - Extender - WARorg.ops4j.pax.web.pax-web-extender-war
7.2.29 Active
OPS4J Pax Web - Extender -
Whiteboardorg.ops4j.pax.web.pax-web-extender-whiteboard 7.2.29 Active
OPS4J Pax Web - FileInstall Deployerorg.ops4j.pax.web.pax-web-deployer
7.2.29 Active
OPS4J Pax Web - Jettyorg.ops4j.pax.web.pax-web-jetty
7.2.29 Active
OPS4J Pax Web - Jsp Supportorg.ops4j.pax.web.pax-web-jsp7.2.29
Active
OPS4J Pax Web - Runtimeorg.ops4j.pax.web.pax-web-runtime 7.2.29
Active
OPS4J Pax Web - Service SPIorg.ops4j.pax.web.pax-web-spi 7.2.29
Active
karaf@root()> list -s -t 0 | grep "org.ops4j.pax.web"
252 | Active | 30 | 8.0.6 | org.ops4j.pax.web.pax-web-api
253 | Resolved | 30 | 8.0.6 |
org.ops4j.pax.web.pax-web-compatibility-el2
254 | Resolved | 30 | 8.0.6 |
org.ops4j.pax.web.pax-web-compatibility-servlet31
255 | Active | 30 | 8.0.6 |
org.ops4j.pax.web.pax-web-extender-war
256 | Active | 30 | 8.0.6 | org.ops4j.pax.web.pax-web-jetty
257 | Active | 30 | 8.0.6 | org.ops4j.pax.web.pax-web-jsp
258 | Active | 30 | 8.0.6 | org.ops4j.pax.web.pax-web-runtime
259 | Active | 30 | 8.0.6 | org.ops4j.pax.web.pax-web-spi
260 | Active | 30 | 8.0.6 |
org.ops4j.pax.web.pax-web-tomcat-common
261 | Active | 30 | 8.0.6 |
org.ops4j.pax.web.pax-web-websocket
ERROR : Tried to restart the above bundle 253 AND 254. I got the an error
Caused by: org.osgi.framework.BundleException: Fragment bundles can not be
started.
karaf@root()> start 253
15:52:07.302 [Karaf local console user karaf] ERROR
org.apache.karaf.shell.support.ShellUtil - Exception caught while executing
command
org.apache.karaf.shell.support.MultiException: Error executing command on
bundles:
Error starting bundle 253: Fragment bundles can not be started.
at
org.apache.karaf.shell.support.MultiException.throwIf(MultiException.java:61)
~[?:?]
at
org.apache.karaf.bundle.command.BundlesCommand.doExecute(BundlesCommand.java:70)
~[?:?]
at
org.apache.karaf.bundle.command.BundlesCommand.execute(BundlesCommand.java:55)
~[?:?]
at
org.apache.karaf.shell.impl.action.command.ActionCommand.execute(ActionCommand.java:84)
~[?:?]
at
org.apache.karaf.shell.impl.console.osgi.secured.SecuredCommand.execute(SecuredCommand.java:68)
~[?:?]
at
org.apache.karaf.shell.impl.console.osgi.secured.SecuredCommand.execute(SecuredCommand.java:86)
~[?:?]
at org.apache.felix.gogo.runtime.Closure.executeCmd(Closure.java:599)
~[?:?]
at
org.apache.felix.gogo.runtime.Closure.executeStatement(Closure.java:526) ~[?:?]
at org.apache.felix.gogo.runtime.Closure.execute(Closure.java:415)
~[?:?]
at org.apache.felix.gogo.runtime.Pipe.doCall(Pipe.java:416) ~[?:?]
at org.apache.felix.gogo.runtime.Pipe.call(Pipe.java:229)
Issue karaf 4.4.1 with org.eclipse.jetty.security.jaspi
Hi Team, I have tried with plain KARAF 4.4.1 binary with "org.eclipse.jetty/jetty-server/9.4.46.v20220331" along with required dependency also deployed into deploy folder (*\apache-karaf-4.4.1\deploy). Now my question is all the bundles or jar's up and running except this "org.eclipse.jetty.security.jaspi" bundle or jar. The ERROR message showing on karaf-shell-console. 00:28:17.230 [FelixDispatchQueue] ERROR Events.Framework - FrameworkEvent ERROR org.osgi.framework.BundleException: Unable to resolve org.eclipse.jetty.security.jaspi [68](R 68.0): missing requirement [org.eclipse.jetty.security.jaspi [68](R 68.0)] osgi.extender; (osgi.extender=osgi.serviceloader.registrar) Unresolved requirements: [[org.eclipse.jetty.security.jaspi [68](R 68.0)] osgi.extender; (osgi.extender=osgi.serviceloader.registrar)] Please any take a look at once and suggest me. Thanks, VamsiKrishna
Recall: karaf 4.4.1 issue with osgi.contract; osgi.contract=JavaJPA; (&(osgi.contract=JavaJPA)(version=2.2.0))
Vamsikrishna Koka would like to recall the message, "karaf 4.4.1 issue with osgi.contract; osgi.contract=JavaJPA; (&(osgi.contract=JavaJPA)(version=2.2.0)) ".
Recall: karaf 4.4.1 issue with osgi.contract; osgi.contract=JavaJPA; (&(osgi.contract=JavaJPA)(version=2.2.0))
Vamsikrishna Koka would like to recall the message, "karaf 4.4.1 issue with osgi.contract; osgi.contract=JavaJPA; (&(osgi.contract=JavaJPA)(version=2.2.0)) ".
karaf 4.4.1 issue with osgi.contract; osgi.contract=JavaJPA; (&(osgi.contract=JavaJPA)(version=2.2.0))
Hi Team,
I have been using "org.eclipse.persistence/javax.persistence/2.1.0" dependency
and upgrade JPA dependency as per KARAF release note 4.4.1 (from
org.apache.openjpa/org.apache.openjpa/ 3.1.1 TO 3.2.2) then I have tried to
bring it karaf server, it was failed due to Caused by:
org.apache.felix.resolver.reason.ReasonException: Unable to resolve
${bundle_name}/3.2.0.SNAPSHOT: missing requirement [core-db/51.0.0.SNAPSHOT]
osgi.contract; osgi.contract=JavaJPA;
filter:="(&(osgi.contract=JavaJPA)(version=2.2.0))".
Please can any one take a look at once and suggested.
Thanks,
VamsiKrishna
Senior Software Engineer
Mob: +91 9381078936
[Motivitylabs - Enabling Mobile Enterprises]
US: 222 W. Las Colinas Blvd.
Suite 755 East
Irving, TX 75039
Ph:+1-214-730-0798
INDIA: 9th & 10th floor, Water Mark Building, Kondapur, Hitech City,
Hyderabad 500 084, Telangana.
Ph:+91-40-4651-5454
Confidentiality Note: This message is confidential. It may also be privileged
or otherwise protected by work product immunity or other legal rules. This
email and any files transmitted with it are confidential and intended solely
for the use of the individual or entity to whom they ar
karaf 4.4.1 issue with osgi.contract; osgi.contract=JavaJPA; (&(osgi.contract=JavaJPA)(version=2.2.0))
Hi Team,
I have been using "org.eclipse.persistence/javax.persistence/2.1.0" dependency
and upgraded JPA dependency as per KARAF release note 4.4.1 (from
org.apache.openjpa/org.apache.openjpa/ 3.1.1 TO 3.2.2) then I have tried to
bring it up karaf server, it was failed due to Caused by:
org.apache.felix.resolver.reason.ReasonException: Unable to resolve
${bundle_name}/3.2.0.SNAPSHOT: missing requirement [core-db/51.0.0.SNAPSHOT]
osgi.contract; osgi.contract=JavaJPA;
filter:="(&(osgi.contract=JavaJPA)(version=2.2.0))".
Please can any one take a look at once and suggested.
Thanks,
VamsiKrishna
Senior Software Engineer
Mob: +91 9381078936
[Motivitylabs - Enabling Mobile Enterprises]
US: 222 W. Las Colinas Blvd.
Suite 755 East
Irving, TX 75039
Ph:+1-214-730-0798
INDIA: 9th & 10th floor, Water Mark Building, Kondapur, Hitech City,
Hyderabad 500 084, Telangana.
Ph:+91-40-4651-5454
Confidentiality Note: This message is confidential. It may also be privileged
or otherwise protected by work product immunity or other legal rules. This
email and any files transmitted with it are confidential and intended solely
for the use of the individual or entity to whom they ar
Recall: karaf 4.4.1 issue with osgi.contract; osgi.contract=JavaJPA; (&(osgi.contract=JavaJPA)(version=2.2.0))
Vamsikrishna Koka would like to recall the message, "karaf 4.4.1 issue with osgi.contract; osgi.contract=JavaJPA; (&(osgi.contract=JavaJPA)(version=2.2.0)) ".
Recall: karaf 4.4.1 issue with osgi.contract; osgi.contract=JavaJPA; (&(osgi.contract=JavaJPA)(version=2.2.0))
Vamsikrishna Koka would like to recall the message, "karaf 4.4.1 issue with osgi.contract; osgi.contract=JavaJPA; (&(osgi.contract=JavaJPA)(version=2.2.0)) ".
karaf 4.4.1 issue with osgi.contract; osgi.contract=JavaJPA; (&(osgi.contract=JavaJPA)(version=2.2.0))
Hi Team,
I have been using "org.eclipse.persistence/javax.persistence/2.1.0" dependency
and upgrade JPA dependency as per KARAF release note 4.4.1 (from
org.apache.openjpa/org.apache.openjpa/ 3.1.1 TO 3.2.2) then I have tried to
bring it karaf server, it was failed due to Caused by:
org.apache.felix.resolver.reason.ReasonException: Unable to resolve
${bundle_name}/3.2.0.SNAPSHOT: missing requirement [core-db/51.0.0.SNAPSHOT]
osgi.contract; osgi.contract=JavaJPA;
filter:="(&(osgi.contract=JavaJPA)(version=2.2.0))".
Please can anyone take a look at once and suggest me.
Thanks,
VamsiKrishna
Senior Software Engineer
Mob: +91 9381078936
[Motivitylabs - Enabling Mobile Enterprises]
US: 222 W. Las Colinas Blvd.
Suite 755 East
Irving, TX 75039
Ph:+1-214-730-0798
INDIA: 9th & 10th floor, Water Mark Building, Kondapur, Hitech City,
Hyderabad 500 084, Telangana.
Ph:+91-40-4651-5454
Confidentiality Note: This message is confidential. It may also be privileged
or otherwise protected by work product immunity or other legal rules. This
email and any files transmitted with it are confidential and intended solely
for the use of the individual or entity to whom they ar
Latest karaf 4.4.1 issue with java.base package import issue(OpenJDK11)
Hi Team,
We are tried to upgrade latest KARAF from KARAF 4.2.15 to KARAF 4.4.1 version
with OpenJDK 11. And tried osgi.annotation/7.0.0 or 8.1.0 both version .
Release Note KARAF 4.4.1
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311140=12351548
While doing maven build our product, the build was failed due to package
sun.security.krb5.internal is not visible
[ERROR] (package sun.security.krb5.internal is declared in module
java.security.jgss, which does not export it to the unnamed module).
The above issue for fixing, I have added given below compilerArgs tag then only
maven build working. We do have any best solution the above issue? without
adding the given below compilerArgs tags.
${java.version}
${java.version}
--add-exportsjava.base/sun.nio.ch=ALL-UNNAMED
--add-exportsjava.base/jdk.internal.ref=ALL-UNNAMED
Thanks,
VamsiKrishna
Software Engineer
Mob: +91 9381078936
[Motivitylabs - Enabling Mobile Enterprises]
US: 222 W. Las Colinas Blvd.
Suite 755 East
Irving, TX 75039
Ph:+1-214-730-0798
INDIA: 9th & 10th floor, Water Mark Building, Kondapur, Hitech City,
Hyderabad 500 084, Telangana.
Ph:+91-40-4651-5454
Confidentiality Note: This message is confidential. It may also be privileged
or otherwise protected by work product immunity or other legal rules. This
email and any files transmitted with it are confidential and intended solely
for the use of the individual or entity to whom they ar
Issue karaf 4.2.15 with OpenJDK 11
Hi Team, Currently, We are using KRAF 4.2.15 with JDK 8. Now we are trying to upgrade OpenJDK 11 but I could able to bring it up karaf due to given below issue. karaf.bat: Enabling Java debug options: -agentlib:jdwp=transport=dt_socket,server=y,suspend=n,address=5005 WARNING: package org.apache.karaf.specs.locator not in java.base Listening for transport dt_socket at address: 5005 Error: Could not find or load main class Krishna\Downloads\apache-karaf-4.2.15\bin\..\lib\endorsed\org.apache.karaf.specs.locator-4.2.15.jar Caused by: java.lang.ClassNotFoundException: Krishna\Downloads\apache-karaf-4/2/15\bin\//\lib\endorsed\org/apache/karaf/specs/locator-4/2/15/jar Thanks, VamsiKrishna Software Engineer Mob: +91 9381078936 [Motivitylabs - Enabling Mobile Enterprises] US: 222 W. Las Colinas Blvd. Suite 755 East Irving, TX 75039 Ph:+1-214-730-0798 INDIA: 9th & 10th floor, Water Mark Building, Kondapur, Hitech City, Hyderabad 500 084, Telangana. Ph:+91-40-4651-5454 Confidentiality Note: This message is confidential. It may also be privileged or otherwise protected by work product immunity or other legal rules. This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they ar
RE: Issue karaf 4.2.15 with OpenJDK 11
+ us...@infra.apache.org<mailto:us...@infra.apache.org> From: Vamsikrishna Koka Sent: Tuesday, August 30, 2022 10:54 PM To: dev@karaf.apache.org Subject: Issue karaf 4.2.15 with OpenJDK 11 Hi Team, Currently, We are using KRAF 4.2.15 with JDK 8. Now we are trying to upgrade OpenJDK 11 but I could able to bring it up karaf due to given below issue. karaf.bat: Enabling Java debug options: -agentlib:jdwp=transport=dt_socket,server=y,suspend=n,address=5005 WARNING: package org.apache.karaf.specs.locator not in java.base Listening for transport dt_socket at address: 5005 Error: Could not find or load main class Krishna\Downloads\apache-karaf-4.2.15\bin\..\lib\endorsed\org.apache.karaf.specs.locator-4.2.15.jar Caused by: java.lang.ClassNotFoundException: Krishna\Downloads\apache-karaf-4/2/15\bin\//\lib\endorsed\org/apache/karaf/specs/locator-4/2/15/jar Thanks, VamsiKrishna Software Engineer Mob: +91 9381078936 [Motivitylabs - Enabling Mobile Enterprises] US: 222 W. Las Colinas Blvd. Suite 755 East Irving, TX 75039 Ph:+1-214-730-0798 INDIA: 9th & 10th floor, Water Mark Building, Kondapur, Hitech City, Hyderabad 500 084, Telangana. Ph:+91-40-4651-5454 Confidentiality Note: This message is confidential. It may also be privileged or otherwise protected by work product immunity or other legal rules. This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they ar
Issue with SSH Client in karaf 4.2.8 by using SSHD library
Hi,
Sorry, I'm not sure this is right platform to posting my question.
My question is some reason in my project, I have shut down and restarted KARAF
Server.
After restated KARAF server tried to connect KARAF SSH client through code as
well as external tool also like putty, I'm getting access denied with admin
credentials.
We are re tried some time to connect SSH client.
This given blow code for create Sshclient session.
try {
SshClient client = SshClient.setUpDefaultClient();
client.start();
ConnectFuture future = client.connect(localhost,"8101");
future.await();
session = future.getSession();
session.authPassword(username, password);
}catch (Exception e) {
//Handling exception
}
Once done, We are closing resource correct by using session.close(false);
client.stop();
There is waitFor method in ClientSessionImpl.java file, it's return 4 ||
WAIT_AUTH, which given below code.
[cid:image001.png@01D732D5.30976510]
Please can you help anyone what exactly happened.
Thanks,
Vamshi Krishna
Issue with SSH Client in karaf 4.2.8 by using SSHD library
Hi,
Sorry, I'm not sure this is right platform to posting my question.
My question is some reason in my project, I have shut down and restarted KARAF
Server.
After restated KARAF server tried to connect KARAF SSH client through code as
well as external tool also like putty, I'm getting access denied with admin
credentials.
We are re tried some time to connect SSH client.
This given blow code for create Sshclient session.
try {
SshClient client = SshClient.setUpDefaultClient();
client.start();
ConnectFuture future = client.connect(localhost,"8101");
future.await();
session = future.getSession();
session.authPassword(username, password);
}catch (Exception e) {
//Handling exception
}
Once done, We are closing resource correct by using session.close(false);
client.stop();
There is waitFor method in ClientSessionImpl.java file, it's return 4 ||
WAIT_AUTH, which given below code.
[cid:image001.png@01D732D5.30976510]
Please can you help anyone what exactly happened.
Thanks,
Vamshi Krishna
Karaf Release 4.2.11
Hi I have following karaf website, For me so excitement when I heard news for announcement of KARAF 4.2.11, Still don't see any update KARAF web site except this comment [HEADS UP] Apache Karaf 4.2.11 release to vote today. Please can anyone help me, When we excepted to release KARAF 4.2.11 RELEASE. Thank you. Vamsi Krishna
