JBoss not starting

octavianp over 7 years ago

Dear all,
The JBoss application server cannot start on one of the servers. The error on the application server is:
15:12:26,423 INFO [stdout] (Appian Timer - 0) 2016-10-10 15:12:26,422 [Appian Timer - 0] ERROR com.appiancorp.core.timer.timers.TransientTopicHeartbeat - No acknowledgement from TransientTopic, forcing rules cache to be cleared now.

We tried to restart the entire machine, clear the app server cache, increase memory, but without any result. Also the server was stopped using the standard procedure, and while trying to start JBoss, Appian engines were all in OK status.
I also attached the rest of the logs, maybe is useful.

Has anyone encounter something like this?

Thank you in advance,
Octavian

startup.log

Discussion posts and replies are publicly visible

Parents

0 octavianp over 7 years ago

@christopherg indeed the only appian-topology is the appian-topology.xml.example located in C:\\appian\\ear\\suite.ear\\conf which comes with the default installation. Unfortunately I have no idea how to configure this file since we are running on a single server.
@Abhi Jana. Thank you for the suggestion! we will try implementing it at the end of the business day since the affected server is the production one. Now it is running because we restored a shapshot of the VM, but this is a temporary solution, because if we need to shutdown the JBoss, it will not start (as we already tested)...
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Reply

0 octavianp over 7 years ago

@christopherg indeed the only appian-topology is the appian-topology.xml.example located in C:\\appian\\ear\\suite.ear\\conf which comes with the default installation. Unfortunately I have no idea how to configure this file since we are running on a single server.
@Abhi Jana. Thank you for the suggestion! we will try implementing it at the end of the business day since the affected server is the production one. Now it is running because we restored a shapshot of the VM, but this is a temporary solution, because if we need to shutdown the JBoss, it will not start (as we already tested)...
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Children

No Data