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
7 replies
Subscribers
9 subscribers
Views
2380 views
Users
0 members are here
Share
More
Cancel
Related Discussions
Home
»
Discussions
»
General
Hi, I am getting the following exception when starting my jboss serve
pkate
over 12 years ago
Hi,
I am getting the following exception when starting my jboss server. I haven't changed anything. This used to work smoothly before. Any pointers will be highly appreciated.
2012-09-10 09:10:38,420 [main] ERROR com.appiancorp.common.config.ConfigObject - An error occurred while trying to initialize the config object com.appiancorp.ap2.LocaleConfig using the following resources: /WEB-INF/conf/locale-config.xml
com.appiancorp.kougar.driver.exceptions.SafeRetryException: Unable to acquire a Write connection. Safe to retry.
at com.appiancorp.kougar.driver.pooling.concurrent.Semaphore.acquireConnection(Semaphore.java:435)
at com.appiancorp.kougar.driver.pooling.concurrent.ConcurrentPools.getWriteConnection(ConcurrentPools.java:147)
at com.appiancorp.kougar.driver.pooling.PoolManager.getWriteConnection(PoolManager.java:300)
at com.appiancorp.kougar.driver.KougarConnection.getConnection(KougarConnection.java:135)
at com.appiancorp.kouga...
OriginalPostID-42744
OriginalPostID-42744
Discussion posts and replies are publicly visible
0
pkate
over 12 years ago
...r.driver.KougarConnection.call(KougarConnection.java:200)
at com.appiancorp.kougar.mapper.Mapper.request(Mapper.java:66)
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
Sathya Srinivasan
Appian Employee
over 12 years ago
Which version of Appian are you using?
Couple of things
1. Check if your K license is valid
2. Stop JBOSS and Appian services. Do a reboot and try again. There is a possibility that a socket is locked and not released.
3. If you have a distributed architecture, check if all your services are reachable and no firewall change has impacted loss of connectivity.
4. Check if your disk is full.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
pkate
over 12 years ago
Thanks for the quick response. This is my local server. I tried restarting appian and jboss and finally also tried restarting my m/c. Disk is also not full. License is valid.
Anything else?
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
Sathya Srinivasan
Appian Employee
over 12 years ago
Please try this.
Stop JBOSS and then Appian.
Reboot your machine
Start Appian
Go to /diagnostics and run check-engine.bat
Ensure all engines are OKAY
Start JBoss after that.
I am trying to make sure all your engines are online before you start your App server.
Check under your /logs to see if there are any .l files as well.
Check your appserver log if there are any other error generated around this message that'd give you a clue on what's happening.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
pkate
over 12 years ago
Appian version is 6.5.3
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
Eduardo Fuentes
Appian Employee
over 12 years ago
Did you check what Sathya suggested about running checkengine? The "SafeRetryException: Unable to acquire a Write connection. Safe to retry." will show up if the application server (e.g. JBoss) cannot communicate with the Appian engines. Determining if the engines are up and running is an easy process that consists in the following steps:
1. Open a command prompt
2. Navigate to <APPIAN_HOME>\\server\\_scripts\\diagnostic
3. Execute: checkengine.bat -s
4. The summary should show all engines in Okay
If they do, you may also want to check you didn't misconfigure a file called appian-topology.xml (which usually shouldn't be configured in a local single-box installation) located under <APPIAN_HOME>\\ear|runtime_ear|suite.ear\\conf.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
pkate
over 12 years ago
Sorry for the late reply. Yes i did run checkengine.bat. There was an issue with one of the engines. Tried to repair that. It did not work. As i did not have much data, i did a cleanup. Finally, things are back in place now. Thanks!
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel