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
225 replies
Subscribers
8 subscribers
Views
18562 views
Users
0 members are here
Share
More
Cancel
Related Discussions
Home
»
Discussions
»
Administration
Hi, I;m upgrading Appian 7.7 to 7.8. I finished migrtion instruction
adams
over 9 years ago
Hi,
I;m upgrading Appian 7.7 to 7.8. I finished migrtion instruction and after running jboss it does not start Appian web application. Log from server is:
12:17:48,059 INFO [org.jboss.modules] (main) JBoss Modules version 1.3.0.Final-redhat-2
12:17:48,526 INFO [org.jboss.msc] (main) JBoss MSC version 1.0.4.GA-redhat-1
12:17:48,623 INFO [org.jboss.as] (MSC service thread 1-6) JBAS015899: JBoss EAP 6.2.0.GA (AS 7.3.0.Final-redhat-14) starting
12:17:48,632 DEBUG [org.jboss.as.config] (MSC service thread 1-6) Configured system properties:
appian.home.ear = C:/appian/ear
appian.home.search-server = C:/appian/search-server
awt.toolkit = sun.awt.windows.WToolkit
file.encoding = Cp1250
file.encoding.pkg = sun.io
file.separator = \\
java.awt.graphicsenv = sun.awt.Win32GraphicsEnvironment
java.awt.headless = true
java.awt.printerjob = sun.awt.windows.WPrinterJob
java.class.path = C:\\jboss-eap-6.2\\jboss-modules.jar
java.class.vers...
OriginalPostID-135017
OriginalPostID-135017
Discussion posts and replies are publicly visible
0
adams
over 9 years ago
... loyment directory. To trigger deployment create a file called ss.ear.dodeploy
12:46:25,210 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015003: Found suite.ear in deployment directory. To trigger deployment create a file called suite.ear.dodeploy
12:46:25,243 INFO [org.xnio] (MSC service thread 1-6) XNIO Version 3.0.7.GA-redhat-1
12:46:25,245 INFO [org.jboss.as.server] (Controller Boot Thread) JBAS015888: Creating http management service using socket-binding (management-http)
12:46:25,251 INFO [org.xnio.nio] (MSC service thread 1-6) XNIO NIO Implementation Version 3.0.7.GA-redhat-1
12:46:25,261 INFO [org.jboss.remoting] (MSC service thread 1-6) JBoss Remoting version 3.2.18.GA-redhat-1
12:46:25,317 INFO [org.jboss.as.security] (...
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
adams
over 9 years ago
... ServerService Thread Pool -- 43) JBAS013171: Activating Security Subsystem
12:46:25,324 INFO [org.jboss.as.security] (MSC service thread 1-4) JBAS013170: Current PicketBox version=4.0.19.SP2-redhat-1
12:46:25,324 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 30) JBAS010280: Activating Infinispan subsystem.
12:46:25,329 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 38) JBAS011800: Activating Naming Subsystem
12:46:25,351 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 47) JBAS015537: Activating WebServices Extension
12:46:25,353 INFO [org.jboss.as.jsf] (ServerService Thread Pool -- 36) JBAS012605: Activated the following JSF Implementations: [main, 1.2]
12:46:25,418 INFO [org.jboss.as.connector.logging] (MSC servic...
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
adams
over 9 years ago
... e thread 1-8) JBAS010408: Starting JCA Subsystem (IronJacamar 1.0.23.Final-redhat-1)
12:46:25,429 INFO [org.jboss.as.naming] (MSC service thread 1-7) JBAS011802: Starting Naming Service
12:46:25,435 INFO [org.jboss.as.mail.extension] (MSC service thread 1-7) JBAS015400: Bound mail session [java:jboss/mail/Default]
12:46:25,580 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 26) JBAS010403: Deploying JDBC-compliant driver class com.microsoft.sqlserver.jdbc.SQLServerDriver (version 4.0)
12:46:25,846 WARN [org.jboss.as.messaging] (MSC service thread 1-4) JBAS011600: AIO wasn't located on this platform, it will fall back to using pure Java NIO. If your platform is Linux, install LibAIO to enable the AIO journal
12:46:25,852 INFO [org...
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
adams
over 9 years ago
... .apache.coyote.http11] (MSC service thread 1-6) JBWEB003001: Coyote HTTP/1.1 initializing on : http-/0.0.0.0:8080
12:46:25,854 INFO [org.apache.coyote.http11] (MSC service thread 1-6) JBWEB003000: Coyote HTTP/1.1 starting on: http-/0.0.0.0:8080
12:46:25,852 INFO [org.apache.coyote.ajp] (MSC service thread 1-8) JBWEB003046: Starting Coyote AJP/1.3 on ajp-/0.0.0.0:8009
12:46:25,936 INFO [org.jboss.ws.common.management] (MSC service thread 1-2) JBWS022052: Starting JBoss Web Services - Stack CXF Server 4.2.3.Final-redhat-1
12:46:25,980 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-6) JBAS015012: Started FileSystemDeploymentService for directory C:\\appian\\search-server
12:46:25,980 INFO [org.jboss.as.server.deployment.scanner] (MSC service threa...
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
adams
over 9 years ago
... d 1-1) JBAS015012: Started FileSystemDeploymentService for directory C:\\jboss-eap-6.2\\standalone\\deployments
12:46:25,981 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-2) JBAS015012: Started FileSystemDeploymentService for directory C:\\appian\\ear
12:46:26,002 INFO [org.jboss.as.remoting] (MSC service thread 1-4) JBAS017100: Listening on 127.0.0.1:9999
12:46:26,002 INFO [org.jboss.as.remoting] (MSC service thread 1-3) JBAS017100: Listening on 0.0.0.0:4447
12:46:26,007 INFO [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015876: Starting deployment of "appian-ds.xml" (runtime-name: "appian-ds.xml")
12:46:26,005 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 50) HQ221000: live server is starting with configuration H...
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
adams
over 9 years ago
... ornetQ Configuration (clustered=false,backup=false,sharedStore=true,journalDirectory=C:\\jboss-eap-6.2\\standalone\\data\\messagingjournal,bindingsDirectory=C:\\jboss-eap-6.2\\standalone\\data\\messagingbindings,largeMessagesDirectory=C:\\jboss-eap-6.2\\standalone\\data\\messaginglargemessages,pagingDirectory=C:\\jboss-eap-6.2\\standalone\\data\\messagingpaging)
12:46:26,079 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 50) HQ221006: Waiting to obtain live lock
12:46:26,108 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 50) HQ221013: Using NIO Journal
12:46:26,186 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 50) HQ221034: Waiting to obtain live lock
12:46:26,190 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 50) HQ22103...
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
adams
over 9 years ago
... 5: Live Server Obtained live lock
12:46:26,488 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-7) JBAS010400: Bound data source [java:/jdbc/SqlAppianPrimaryDS]
12:46:26,488 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-2) JBAS010400: Bound data source [java:/jdbc/CPowerUKDS]
12:46:26,488 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-6) JBAS010400: Bound data source [java:/jdbc/SqlAppianBusinessDS1]
12:46:26,488 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-3) JBAS010400: Bound data source [java:/jdbc/SqlAppianBusinessDS2]
12:46:26,509 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 50) HQ221020: Started Netty Acceptor version 3.6.6.Fin...
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
adams
over 9 years ago
... al-redhat-1-fd3c6b7 0.0.0.0:5445 for CORE protocol
12:46:26,513 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 50) HQ221020: Started Netty Acceptor version 3.6.6.Final-redhat-1-fd3c6b7 0.0.0.0:5455 for CORE protocol
12:46:26,519 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 50) HQ221007: Server is now live
12:46:26,521 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 50) HQ221001: HornetQ Server version 2.3.12.Final (2.3.12, 123) [d3bc2d34-285a-11e4-b07a-d1156e1ce2a9]
12:46:26,526 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 50) HQ221003: trying to deploy queue jms.topic.jms/TransientTopic
12:46:26,532 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 50) JBAS011601: Bound messaging object to...
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
adams
over 9 years ago
... jndi name java:/comp/suite/jms-transient-topic-handler/JmsTransientTopicHandlerBean/env/jms/AppianTransientTopic
12:46:26,534 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 50) JBAS011601: Bound messaging object to jndi name java:/module/suite/web/env/jms/AppianTransientTopic
12:46:26,536 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 50) JBAS011601: Bound messaging object to jndi name java:/jms/AppianTransientTopic
12:46:26,541 INFO [org.hornetq.jms.server] (ServerService Thread Pool -- 52) HQ121005: Invalid "host" value "0.0.0.0" detected for "netty" connector. Switching to "CF-VM-JBOSS2". If this new address is incorrect please manually configure the connector to use the proper one.
12:46:26,559 INFO [org.jboss.as.messaging] (Ser...
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
adams
over 9 years ago
... verService Thread Pool -- 52) JBAS011601: Bound messaging object to jndi name java:/module/suite/web/env/ClusteredConnectionFactory
12:46:26,560 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 52) JBAS011601: Bound messaging object to jndi name java:/ClusteredConnectionFactory
12:46:26,562 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 52) JBAS011601: Bound messaging object to jndi name java:/comp/suite/jms-transient-topic-handler/JmsTransientTopicHandlerBean/env/ClusteredConnectionFactory
12:46:26,564 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 51) HQ221003: trying to deploy queue jms.queue.jms/ProcessQueue
12:46:26,573 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 51) JBAS011601: Bound messaging objec...
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
<
>