Hi
Do you have any backend configured for ticket registry ? This may be the
easiest way to achieve your goal.
Memcache is easy to setup.
Regards.
Le 21 juillet 2017 17:17:29 GMT+02:00, Fabio Martelli
a écrit :
>Hi All, I need your help to understand how I can
Hello,
I messaged earlier this week concerning hazelcast tickets not replicating.
I expect that if I am authenticated through one node, and it becomes un
available, that the connection will failover to the second node and with no
change visible in my client.
For instance, if I log into
Hmmm. I'm using gradle, so I can't quite copy paste that. But that might be
what I'm missing. Where did you find such guidance?
On Friday, July 21, 2017 at 1:35:17 PM UTC-5, cfernand wrote:
>
> Where does project/build/resources/resource/directory in your pom.xml
> point to? In my case I had to
Hi All, I need your help to understand how I can configure my CAS 5.1.X
single instance to control access to a multi instance application with a
load balancer in front.
Each single instance communicates with CAS directly. This latter
communicates with the clustered application through the LB.
Hello all,
I am using the MongoDB Service Registry. Reading from the registry works
fine, also deletion of items is not a problem. However, when I try to
create a new service or when I try to edit an existing service, I get the
following error message.
[1;31m2017-07-21 10:33:02,368 ERROR
I am afraid this does not work for me. AJP port remains dead.
Am Montag, 10. Juli 2017 15:54:53 UTC+2 schrieb Jozef Kotlar - EEA.sk:
>
> I can confirm that putting following snippet in application.yml have
> switched AJP port on
>
> # embedded tomcat
> cas.server.ajp:
> enabled: true
>