Hi Alex,
you are right, if the two instances and clients run with the same user.
The workaround is to remove the $HOME/.sshkaraf folder before each
ssh:ssh. ssh:ssh will recreate it with the target instance key.
I can add an option to ssh:ssh and client to "ignore" server key check.
Regards
JB
Hi,
Karaf doesn't have such mechanism out of the box.
However, you can implement your own "controller" for that. It's a bundle
that control others based on configuration.
Regards
JB
On 28/03/2019 20:56, imranrazakhan wrote:
> We have karaf in Openshift and sharing central configuration through
For my integration tests, I launch two separate Karaf instances.
When I try to connect from one instance to the other using the ssh:ssh
command, I always get the error:
org.apache.sshd.common.SshException: Server key did not validate
at
We have karaf in Openshift and sharing central configuration through
configmap. We have to start/stop or make available features/bundles on base
of central configuration.
So if central configuration tag one bundle as enable we will start it or if
central configuration tag feature as disable we
Hi Lukasz,
We don't have such guide for now, but it makes sense as there's some
changes.
About your question, I would recommend to use the features provided by
Karaf as the examples are based on this.
In your case, did you check you don't have different JPA versions ?
(like 2.0/2.1) ?
Regards
Hello again,
i dont use Component Factories i am now using Managed Service Factories...
i am now using this way to discover available factories:
ServiceComponentRuntime scr;
[...]
scr.getComponentDescriptionDTOs(null)
.stream()
.map(componentDescriptionDTO -> String.join(" ",
Hello,
Do you have some guide for upgrading from karaf 4.1.x line to 4.2.x line?
I have a legacy app that wasn't possible to upgrade because of some critical
bugs introduced with library updates (PostgreSQL support issues), now I've
tried to install our app from 4.1.3 to 4.2.4 and I'm getting
