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
10 replies
Subscribers
8 subscribers
Views
5480 views
Users
0 members are here
Share
More
Cancel
Related Discussions
Home
»
Discussions
»
Administration
Hi, just migrating a 7.3 environment to 7.4 and getting the following error in t
David Williams
over 10 years ago
Hi, just migrating a 7.3 environment to 7.4 and getting the following error in the jboss log ...
20:24:51,958 WARN [com.arjuna.ats.jta] (Periodic Recovery) ARJUNA016027: Local XARecoveryModule.xaRecovery got XA exception XAException.XAER_RMERR: javax.transaction.xa.XAException: com.microsoft.sqlserver.jdbc.SQLServerException: Failed to create the XA control connection. Error: "Could not find stored procedure 'master..xp_sqljdbc_xa_init_ex'."
at com.microsoft.sqlserver.jdbc.SQLServerXAResource.DTC_XA_Interface(SQLServerXAResource.java:642)
at com.microsoft.sqlserver.jdbc.SQLServerXAResource.recover(SQLServerXAResource.java:723)
at org.jboss.jca.adapters.jdbc.xa.XAManagedConnection.recover(XAManagedConnection.java:358)
at org.jboss.jca.core.tx.jbossts.XAResourceWrapperImpl.recover(XAResourceWrapperImpl.java:165)
at com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.xaRecoveryFirstPass(XARecoveryModule.java:534) [jbos...
OriginalPostID-95457
OriginalPostID-95457
Discussion posts and replies are publicly visible
Parents
0
Eduardo Fuentes
Appian Employee
over 10 years ago
Definitely no. In order to determine what's wrong:
0. Solve this issue to reduce the noise in the server.log
1. Stop JBoss
2. Delete <JBOSS_HOME>\\standalone\\log\\server.log
3. Start JBoss
4. Wait for the CPU usage to go down
5. Review from top to bottom until you find the first error.
6. If you do not see any errors and only see the deployment of appian-ds.xml
INFO [org.jboss.as.server] (ServerService Thread Pool -- 27) JBAS018559: Deployed "appian-ds.xml" (runtime-name : "appian-ds.xml")
but you don't see the ear/runtime_ear directory being deployed
INFO [org.jboss.as.server] (ServerService Thread Pool -- 27) JBAS018559: Deployed "suite.ear" (runtime-name : "suite.ear")
then you may need to follow these steps:
1. Stop JBoss
2. Delete <JBOSS_HOME>\\standalone\\log\\server.log
3. Place the following file (to instruct JBoss to deploy your suite.ear) under runtime_ear or ear (if not using the Appian Configuration Manager) at the same level as suite.ear
forum.appian.com/.../92745
4. Start JBoss
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
Reply
0
Eduardo Fuentes
Appian Employee
over 10 years ago
Definitely no. In order to determine what's wrong:
0. Solve this issue to reduce the noise in the server.log
1. Stop JBoss
2. Delete <JBOSS_HOME>\\standalone\\log\\server.log
3. Start JBoss
4. Wait for the CPU usage to go down
5. Review from top to bottom until you find the first error.
6. If you do not see any errors and only see the deployment of appian-ds.xml
INFO [org.jboss.as.server] (ServerService Thread Pool -- 27) JBAS018559: Deployed "appian-ds.xml" (runtime-name : "appian-ds.xml")
but you don't see the ear/runtime_ear directory being deployed
INFO [org.jboss.as.server] (ServerService Thread Pool -- 27) JBAS018559: Deployed "suite.ear" (runtime-name : "suite.ear")
then you may need to follow these steps:
1. Stop JBoss
2. Delete <JBOSS_HOME>\\standalone\\log\\server.log
3. Place the following file (to instruct JBoss to deploy your suite.ear) under runtime_ear or ear (if not using the Appian Configuration Manager) at the same level as suite.ear
forum.appian.com/.../92745
4. Start JBoss
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
Children
No Data