[Adding list back]

In that case it's most likely you've made some mistakes. Try using the standalone server dist and add your changes one at a time to find out what it is that's breaking it.

On 30 August 2016 at 09:36, Aman Jaiswal <aman.jaiswal@arvindinternet.com> wrote:
I am using standalone-ha.xml with some changes . 

On Tue, Aug 30, 2016 at 1:04 PM, Stian Thorgersen <sthorger@redhat.com> wrote:
Looks like there's something wrong in your standalone.xml. Did you use the standalone server distro?

On 30 August 2016 at 09:15, Aman Jaiswal <aman.jaiswal@arvindinternet.com> wrote:
Hi Stian

I am getting an error while starting keycloak-2.1.0.Final server .... error is mentions bellow
I am all ready added the file layers.conf with content "layers=keycloak"
  

=========================================================================

 

 

  JBoss Bootstrap Environment

 

 

  JBOSS_HOME: /home/ubuntu/keycloak/keycloak-2.1.0.Final

 

 

  JAVA: java

 

 

  JAVA_OPTS:  -server -Xms64m -Xmx512m -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true

 

 

=========================================================================

 

 

05:54:22,401 INFO  [org.jboss.modules] (main) JBoss Modules version 1.5.1.Final

05:54:22,654 INFO  [org.jboss.msc] (main) JBoss MSC version 1.2.6.Final

05:54:22,743 INFO  [org.jboss.as] (MSC service thread 1-2) WFLYSRV0049: Keycloak 2.1.0.Final (WildFly Core 2.0.10.Final) starting

05:54:23,647 ERROR [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0055: Caught exception during boot: org.jboss.as.controller.persistence.ConfigurationPersistenceException: WFLYCTL0085: Failed to parse configuration

  at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:131) [wildfly-controller-2.0.10.Final.jar:2.0.10.Final]

  at org.jboss.as.server.ServerService.boot(ServerService.java:356) [wildfly-server-2.0.10.Final.jar:2.0.10.Final]

  at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:299) [wildfly-controller-2.0.10.Final.jar:2.0.10.Final]

  at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_91]

Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[285,5]

Message: Unexpected element '{urn:jboss:domain:4.0}subsystem'

  at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:108) [staxmapper-1.2.0.Final.jar:1.2.0.Final]

  at org.jboss.staxmapper.XMLExtendedStreamReaderImpl.handleAny(XMLExtendedStreamReaderImpl.java:69) [staxmapper-1.2.0.Final.jar:1.2.0.Final]

  at org.jboss.as.server.parsing.StandaloneXml_4.parseServerProfile(StandaloneXml_4.java:546) [wildfly-server-2.0.10.Final.jar:2.0.10.Final]

  at org.jboss.as.server.parsing.StandaloneXml_4.readServerElement(StandaloneXml_4.java:242) [wildfly-server-2.0.10.Final.jar:2.0.10.Final]

  at org.jboss.as.server.parsing.StandaloneXml_4.readElement(StandaloneXml_4.java:141) [wildfly-server-2.0.10.Final.jar:2.0.10.Final]

  at org.jboss.as.server.parsing.StandaloneXml.readElement(StandaloneXml.java:103) [wildfly-server-2.0.10.Final.jar:2.0.10.Final]

  at org.jboss.as.server.parsing.StandaloneXml.readElement(StandaloneXml.java:49) [wildfly-server-2.0.10.Final.jar:2.0.10.Final]

  at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:110) [staxmapper-1.2.0.Final.jar:1.2.0.Final]

  at org.jboss.staxmapper.XMLMapperImpl.parseDocument(XMLMapperImpl.java:69) [staxmapper-1.2.0.Final.jar:1.2.0.Final]

  at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:123) [wildfly-controller-2.0.10.Final.jar:2.0.10.Final]

  ... 3 more

 

 

05:54:23,651 FATAL [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0056: Server boot has failed in an unrecoverable manner; exiting. See previous messages for details.

05:54:23,659 INFO  [org.jboss.as.server] (Thread-2) WFLYSRV0220: Server shutdown has been requested.

05:54:23,683 INFO  [org.jboss.as] (MSC service thread 1-3) WFLYSRV0050: Keycloak 2.1.0.Final (WildFly Core 2.0.10.Final) stopped in 18ms


 

On Mon, Aug 29, 2016 at 4:29 PM, Stian Thorgersen <sthorger@redhat.com> wrote:
I'd say your DB is going pretty slow then. It takes me ~60 second to boot Keycloak here, which is well within the 300 second limit. Can't really answer why it's that slow as it's most likely your DB not behaving very well.

On 29 August 2016 at 12:53, Aman Jaiswal <aman.jaiswal@arvindinternet.com> wrote:
hi
I am talking about the time limit which is  mention in the following error.
ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) 
WFLYCTL0348: Timeout after [300] seconds waiting for service container stability. 
Operation will roll back. Step that first updated the service container was 'add' at address '[
    ("core-service" => "management"),
    ("management-interface" => "http-interface")
]'

On Mon, Aug 29, 2016 at 4:19 PM, Aman Jaiswal <aman.jaiswal@arvindinternet.com> wrote:
hi

time when keycloak is trying to connect the database which is on the server.

On Mon, Aug 29, 2016 at 4:16 PM, Stian Thorgersen <sthorger@redhat.com> wrote:
What time limit?

On 26 August 2016 at 11:15, Aman Jaiswal <aman.jaiswal@arvindinternet.com> wrote:
Hi Stian

Hi  I  changed the time limit from 300 to 600 and it's work but I want to know that why it is not working on 300 sec of default time ?

On Fri, Aug 26, 2016 at 2:43 PM, Stian Thorgersen <sthorger@redhat.com> wrote:
Looks like maybe you haven't setup the datasource correctly or there's some other configuration issue. Maybe try Googling for it?

On 23 August 2016 at 12:33, Aman Jaiswal <aman.jaiswal@arvindinternet.com> wrote:
Hi  Team 

I am getting an error while connecting my local keycloak to DB which is on server.
error is in attached file . please give me solution to resolve this issue..  
--
Thanks,
Aman Jaiswal

_______________________________________________
keycloak-user mailing list
keycloak-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/keycloak-user




--
Thanks,
Aman Jaiswal




--
Thanks,
Aman Jaiswal



--
Thanks,
Aman Jaiswal




--
Thanks,
Aman Jaiswal




--
Thanks,
Aman Jaiswal