When Starting Up Cluster, Subsequent Nodes Fail

Solution Unverified - Updated -

Issue

  • Some times when restarting JBoss cluster nodes, subsequent nodes fail to start up due to the following error:
ERROR [org.jboss.system.server.profileservice.repository.ScopedProfileServiceController] (main) Error installing to Create: name=ProfileKey@48e2fa0e[domain=default, server=default, name=farm] state=Configured mode=On Demand requiredState=Installed
java.lang.reflect.InvocationTargetException
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
...
Caused by: java.lang.IllegalStateException: Must register RepositoryClusteringHandler before calling create()
        at org.jboss.system.server.profileservice.repository.clustered.ClusteredDeploymentRepository.create(ClusteredDeploymentRepository.java:198)
        at org.jboss.system.server.profileservice.repository.clustered.ClusteredDeploymentRepository.load(ClusteredDeploymentRepository.java:226)
        at org.jboss.system.server.profile.repository.AbstractProfile.create(AbstractProfile.java:158)
        ... 22 more

Environment

Red Hat JBoss Enterprise Application Platform (EAP)

  • 5.x

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.