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
4 replies
Subscribers
7 subscribers
Views
1483 views
Users
0 members are here
Share
More
Cancel
Related Discussions
Home
»
Discussions
»
Administration
Migrating from 7.8 to 7.9 Hotfix A. I have engines and search server start
Jim Schweitzer
Certified Lead Developer
over 9 years ago
Migrating from 7.8 to 7.9 Hotfix A.
I have engines and search server started properly.
Attempting to start jboss (EAP 6.4) - Getting an error about premature end of file, but it doesn't say exactly which file. Looks like it might be referring to appian-topology.xml. server.log attached
I created the configuration using the configuration using the configure script before I deployed HF A. I see there's an issue addressed in HF A: AN-60118 about invalid default topology being fixed.
Is this the symptom of that? Best way to fix it? I tried creating a new "environment" after the installing hotfix but the generated topology file looks the same.
server.log
OriginalPostID-150670
OriginalPostID-150670
Discussion posts and replies are publicly visible
0
Jim Schweitzer
Certified Lead Developer
over 9 years ago
I removed the topology file that was created by default from the ear folder, and jboss is starting now. would still like confirmation that this is the AN-60118 issue and best way to fix it.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
Jim Schweitzer
Certified Lead Developer
over 9 years ago
Also, FYI, Search Server didn't actually start properly earlier like i thought. Said it was started, but the java process had died immediately with no log. had to adjust the ss copy of topology file too.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
Eduardo Fuentes
Appian Employee
over 9 years ago
This is because you skipped the required step of properly configure the appian-topology.xml file. The one that comes by default is all commented out and will be deployed as-is by the Configure Script if not updated beforehand.
An all-commented-out appian-topology.xml results in the error you were seeing since it's not valid.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
Eduardo Fuentes
Appian Employee
over 9 years ago
Finally, yes, this is handled now in a graceful way as part of the fix for AN-60118
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel