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
3 replies
Subscribers
7 subscribers
Views
1467 views
Users
0 members are here
Share
More
Cancel
Related Discussions
Home
»
Discussions
»
Administration
Trying to Install Appian 7.8 on Linux- Jboss eap 6.3 and facing the below issue.
Hari Rusum
over 10 years ago
Trying to Install Appian 7.8 on Linux- Jboss eap 6.3 and facing the below issue. I have attached server.log file.
Installation is done through "Appian Configuration Manager".
[ServerService Thread Pool -- 64] ERROR com.appiancorp.core.persist.JmsCacheUpdateDistributor - Could not propagate: [DistributedCacheUpdate cacheName="types.datatypeEcoreIds" keys=[516]]
19:45:53,084 INFO [stdout] (ServerService Thread Pool -- 64) javax.jms.JMSException: Failed to create session factory
Caused by: HornetQException[errorType=NOT_CONNECTED message=HQ119007: Cannot connect to server(s). Tried with all available servers.]
HQ214016: Failed to create netty connection: java.net.SocketTimeoutException: connect timed out
server.log
OriginalPostID-146463
OriginalPostID-146463
Discussion posts and replies are publicly visible
Parents
0
Eduardo Fuentes
Appian Employee
over 10 years ago
Actually the 9300 port is used by the Search Server not by HornetHQ.
For information about the messaging ports and other ports that need to be open review the section <socket-binding-group name="standard-sockets" default-interface="public" port-offset="${jboss.socket.binding.port-offset:0}"> in your standalone.xml and follow the advice of the user above; review firewall rules to make sure the ports are accessible.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
Reply
0
Eduardo Fuentes
Appian Employee
over 10 years ago
Actually the 9300 port is used by the Search Server not by HornetHQ.
For information about the messaging ports and other ports that need to be open review the section <socket-binding-group name="standard-sockets" default-interface="public" port-offset="${jboss.socket.binding.port-offset:0}"> in your standalone.xml and follow the advice of the user above; review firewall rules to make sure the ports are accessible.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
Children
No Data