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 Pa
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 us
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
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 follow
Hi,
I note that since the last set of logs/trace the version of EclipseLink has
increased from 2.6.x to 2.7.x. This changes the JPA version from 2.1 to 2.2,
which currently isn’t supported by Aries JPA or the Tx Control JPA provider.
This will be one of the issues.
The other issues that I see
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/
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/feature
