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
7 replies
Subscribers
9 subscribers
Views
3882 views
Users
0 members are here
Share
More
Cancel
Related Discussions
Home
»
Discussions
»
Administration
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
OriginalPostID-240135
startup.log
Discussion posts and replies are publicly visible
Parents
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
Reply
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
Children
No Data