Any solution to fix this problem? it is happening to the latest 6.1.0-RC4
On Thursday, March 28, 2019 at 9:04:33 AM UTC-4, magicserverpixiedust wrote:
>
> Still haven't found a resolution for this either.
>
> On Thu, Mar 28, 2019 at 7:15 AM Rob Blais >
> wrote:
>
>> Has there been any resolution
Still haven't found a resolution for this either.
On Thu, Mar 28, 2019 at 7:15 AM Rob Blais wrote:
> Has there been any resolution to this? I've run into the exact same
> problem with CAS 6.0.1 and 6.1.0-RC2. It worked fine in 5.2.x and previous
> versions I've used.
>
> On Tuesday, September
Has there been any resolution to this? I've run into the exact same
problem with CAS 6.0.1 and 6.1.0-RC2. It worked fine in 5.2.x and previous
versions I've used.
On Tuesday, September 25, 2018 at 3:00:47 PM UTC-4, magicserverpixiedust
wrote:
>
> If I start cas.war and wait for it to complet
If I start cas.war and wait for it to complete, then start
cas-management.war - then CAS Management app starts fine without the hang
up during Tomcat start.
--
- Website: https://apereo.github.io/cas
- Gitter Chatroom: https://gitter.im/apereo/cas
- List Guidelines: https://goo.gl/1VRrw7
-
I've deployed CAS Management 5.3.3-SNAPSHOT and its hangs during Tomcat
startup as well.
--
- Website: https://apereo.github.io/cas
- Gitter Chatroom: https://gitter.im/apereo/cas
- List Guidelines: https://goo.gl/1VRrw7
- Contributions: https://goo.gl/mh7qDG
---
You received this message bec
A CAS Management 5.3.3-SNAPSHOT should be available soon in the snapshot
repo. Change your pom.xml/gradle.build to use this snapshot for CAS
Management and 5.3.3 for CAS server modules.
Will get a release out next week. With options to run on the same server in
the config.
On Thu, Sep 13, 2018 a
OK, good to know.
Is it possible to allow CAS and CAS management App deployed on the same
host, without the order of which one starts first? I can do that with
CAS4, that makes our deployment a lot simpler, without such dependencies.
Can we turn off discovery mode in CAS 5.3 management to all
What I meant to go on and say is that the management app tries to call the
discovery endpoint on the configured cas server when trying to startup. If
you are running both the server and the management app on the same server,
I think it is stalling cause it can't reach the CAS server, because it is
Looks like you have configured your CAS server and the management app to
run on the same host and the same port.
On Wed, Sep 12, 2018, 12:52 PM Yan Zhou wrote:
> Hello,
>
> I am running CAS 5.3.3, but latest management web app is 5.3.1.
>
> My management web app will not start up. It just hangs
Hello,
I am running CAS 5.3.3, but latest management web app is 5.3.1.
My management web app will not start up. It just hangs there. What did I
miss?
Here is the log file.
2018-09-12 15:48:11,936 INFO
[org.apereo.cas.configuration.DefaultCasConfigurationPropertiesSourceLocator]
-
2018-09-1
10 matches
Mail list logo