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
5 replies
Subscribers
7 subscribers
Views
1865 views
Users
0 members are here
Share
More
Cancel
Related Discussions
Home
»
Discussions
»
General
JAR file in JBOSS lib folder resulting in Appian Error
parthajitp
A Score Level 1
over 7 years ago
Hi All,
We have a requirement where an application will monitor the JBOSS server to check Appian's interaction with the database. We have placed the JAR file in the lib folder of the JBOSS home and have also added JAVA_TOOL_OPTIONS in the standalone.bat file . But after restarting the Appian engines/ search-server/JBOSS when we try to open Appian Tempo we are seeing nothing inside the page (not even the tabs), just the sky blue color background. Also if we try to open any interface/process models we get to see the "Error-404 page not found" error(attached screenshot). Any help is much appreciated.
OriginalPostID-247830
Discussion posts and replies are publicly visible
0
Eduardo Fuentes
Appian Employee
over 7 years ago
What did you add in JAVA_TOOL_OPTIONS ? You might be introducing a class loader error.
Check the server.log during the start-up, if you see a NoClassDefFoundError or similar then it means Appian is not compatible with this tool.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
parthajitp
A Score Level 1
over 7 years ago
Hi Eduardo,
We added the path of the jar file in JAVA_TOOL_OPTIONS.
Yes, that is the error which we are getting in the server log. Thanks a ton Eduardo!
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
Eduardo Fuentes
Appian Employee
over 7 years ago
What's the exact error?
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
parthajitp
A Score Level 1
over 7 years ago
Here is an extract from the server log pointing out the errors.
Agenterrorlog.txt
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
Eduardo Fuentes
Appian Employee
over 7 years ago
Ok my first answer was correct then. I can clearly see the agent is causing a class loader issue that impacts the OSGI framework needed for plug-in deployment and some modern UI components of Appian.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel