Appian Community
Site
Search
Sign In/Register
Site
Search
User
DISCUSS
LEARN
SUCCESS
SUPPORT
Documentation
AppMarket
More
Cancel
I'm looking for ...
State
Not Answered
Replies
23 replies
Subscribers
9 subscribers
Views
9139 views
Users
0 members are here
Share
More
Cancel
Related Discussions
Home
»
Discussions
»
Administration
#Installation and Administration of Appian 7.9 in Linux Getting the
vamsib
over 8 years ago
#Installation and Administration of Appian 7.9 in Linux
Getting the following error during JBOSS EAP 6.3 Application Server Startup
===========================================================================
09:24:36,151 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) JBAS013412: 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" => "native-interface")
]'
09:24:41,162 ERROR [org.jboss.as.controller.client] (Controller Boot Thread) JBAS014781: Step handler org.jboss.as.server.DeployerChainAddHandler$FinalRuntimeStepHandler@42b41d88 for operation {"operation" => "add-deployer-chains","address" => []} at address [] failed handling operation rollback -- java.util.concurrent.TimeoutException
09:24:43,924 ERROR [org.apache.catalina.c...
files.7z
OriginalPostID-160387
OriginalPostID-160387
Discussion posts and replies are publicly visible
Parents
0
Eduardo Fuentes
Appian Employee
over 8 years ago
Definitely something happened with your standalone.conf. Can you find it in your repository and manually deploy it to <JBOSS_HOME>\\standalone\\bin?
If you look at the one you sent me, that's the JBoss default one, it's not the one with the Appian settings (see _admin\\_scripts\\configure\ emplates\\bin\\jboss\\jboss-eap-6.3\\bin\\standalone.conf.example). I don't know yours was replaced with the out of the box one but that's the root cause.
If you can't find it, simply copy _admin\\_scripts\\configure\ emplates\\bin\\jboss\\jboss-eap-6.3\\bin\\standalone.conf.example to <JBOSS_HOME>\\standalone\\bin and rename it to standalone.conf, then open it and update the variable APPIAN_HOME_EAR accordingly.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
Reply
0
Eduardo Fuentes
Appian Employee
over 8 years ago
Definitely something happened with your standalone.conf. Can you find it in your repository and manually deploy it to <JBOSS_HOME>\\standalone\\bin?
If you look at the one you sent me, that's the JBoss default one, it's not the one with the Appian settings (see _admin\\_scripts\\configure\ emplates\\bin\\jboss\\jboss-eap-6.3\\bin\\standalone.conf.example). I don't know yours was replaced with the out of the box one but that's the root cause.
If you can't find it, simply copy _admin\\_scripts\\configure\ emplates\\bin\\jboss\\jboss-eap-6.3\\bin\\standalone.conf.example to <JBOSS_HOME>\\standalone\\bin and rename it to standalone.conf, then open it and update the variable APPIAN_HOME_EAR accordingly.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
Children
No Data