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

0 octavianp over 7 years ago

Please find attached also the rest of the logs .
server.log
application-server.log
hs_err_pid2000.log
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Chris over 7 years ago

Can you check your conf directory to see if your properties or topology file got corrupted, deleted, or edited in some way? It looks like that file cannot be found so it's using application default configuration which may not align to your environment. The application-server.log states: "Could not find appian-topology.xml on the classpath. The default search server topology configuration will be used, but this configuration cannot be hot-reloaded." It seems that it does not have the proper search queue configuration.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 abhi.jana
Appian Employee
over 7 years ago

Try these steps -

1. Stop the environment (app server, engines etc.)
2. delete/the dll files from the folder <appian>/ear/suite.ear/resources/native/sigar
3. Restart the environment

If this doesn't help, i would recommend creating a support case to work with Appian Technical Support
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
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
0 Chris over 7 years ago

@Abhi, is that the path to the OSGI cache folder? I saw a similar issue/error that recommended that posted by vinitl522.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 abhi.jana
Appian Employee
over 7 years ago

That's the path where the dlls for the sigar library are present. Very rare but this has previously caused JVM crashes in a similar way. We can confirm by looking at the problematic frame in the crash log -

# A fatal error has been detected by the Java Runtime Environment:
#
# EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x00000000ef4d4ed4, pid=2000, tid=2900
#
# JRE version: Java(TM) SE Runtime Environment (7.0_75-b13) (build 1.7.0_75-b13)
# Java VM: Java HotSpot(TM) 64-Bit Server VM (24.75-b04 mixed mode windows-amd64 compressed oops)
# Problematic frame:
# C [sigar-amd64-winnt.dll+0x14ed4]

Removing these dlls should not affect the functioning of the product
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 octavianp over 7 years ago

Yesterday at the end of the business day we did the test that Abhi suggested and JBoss started. All things seems to look good for the moment. If this will not lead to unexpected errors in time this is the perfect solution.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel