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
10 replies
Subscribers
7 subscribers
Views
3787 views
Users
0 members are here
Share
More
Cancel
Related Discussions
Home
»
Discussions
»
Administration
We've had an error occur a couple times now on different days with different
jaredw
over 9 years ago
We've had an error occur a couple times now on different days with different plugins. We have a scheduled task setup to restart Jboss every morning we received the following error:
11:33:03,879 INFO [stdout] (ServerService Thread Pool -- 92) 2015-12-21 11:33:03,879 [ServerService Thread Pool -- 92] ERROR com.atlassian.plugin.manager.PluginEnabler - Unable to start the following plugins due to timeout while waiting for plugin to enable: psshared.htmldisplay
Any Ideas on what could cause this?
Thank you in advance.
OriginalPostID-185556
OriginalPostID-185556
Discussion posts and replies are publicly visible
Parents
0
Eliot Gerson
Appian Employee
over 9 years ago
Jared, there are various reasons this can happen, but the general idea is that if the application server is taking too long to start, some plugin deployments may time-out and get skipped. One thing that might prolong application server start up and cause this to happen is if you are trying to load a large number of plugins. Frequently, plugins that were skipped will be loaded after the application server has started as a hot-deployment, but it is best to check the server log or console output to be sure. If plugin is not loaded automatically after the application server has started (assuming you have enabled hot-deployment of plugins), you can hot-deploy the plugin manually.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
Reply
0
Eliot Gerson
Appian Employee
over 9 years ago
Jared, there are various reasons this can happen, but the general idea is that if the application server is taking too long to start, some plugin deployments may time-out and get skipped. One thing that might prolong application server start up and cause this to happen is if you are trying to load a large number of plugins. Frequently, plugins that were skipped will be loaded after the application server has started as a hot-deployment, but it is best to check the server log or console output to be sure. If plugin is not loaded automatically after the application server has started (assuming you have enabled hot-deployment of plugins), you can hot-deploy the plugin manually.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
Children
No Data