Posts tagged JBoss

Working around a “Turnkey service JBoss for Adobe LiveCycle does not exist” error

Waldo Smeets

Disease:
After installing a new Jboss turnkey instance of Adobe LiveCycle, some people run into an issue when the LiveCycle Configuration Manager is doing it’s work. At about 40%, the configuration manager might display the following error:

 

Failed on ‘Verifying JBoss for Adobe LiveCycle ES service is installed’
Windows turnkey service JBoss for Adobe LiveCycle ES does not exist

When checking in the Windows Service Panel, indeed there is no such service defined, even though the installer should have created it. I have not been able to replicate this issue, but it happened to me at a customer site and by searching Google it seems that others have run into it as well.

Prescription:
The Google search results tells us that some people forget to set the Java_Home system variable and that you should be using the right version of the JDK. However, this did not seem to be the problem in this case.

Through the install documentation you can find the steps needed to re-create the JBoss for Adobe LiveCycle ES service (page 62). You can use those to try and create the service ‘manually’. For our install, the problem seemed to be in the [LC_INSTALL_ROOT]jbossInstallJBossService.bat script file. Somehow the username / password did not seem to work, whatever we tried it failed. Well, sort off: strangely enought the command prompt output first mentions that there was an error, though still reports that the script was executed succesfully. Still no service created though.

The solution was too simple to come up with: just remove the username / password parameters from the script and execute it. This time the script did not fail and as expected created the service for us. Next thing to do is go into the service panel, select the ‘JBoss for Adobe LiveCycle’ service, right click to go to it’s Properties and in the Log On tab specify Log In As This Account. Then specify the username password (in my case “.administrator” and the password), click OK and you are done.

Now run the LiveCycle Configuration Manager again and most likely it won’t fail anymore cause of the missing service. This seemed to have overcome our issue.

Tip to stay healthy:
When installing the turnkey solution, it is highly recommended to keep the right documentation at hand: Installing and Deploying LiveCycle® ES Using Turnkey.

Did you run into this issue as well? Please let us know if this worked for you or if you have additional tips for our readers.

—-
Original article at http://www.drflex.eu/2009/03/turnkey-service-jboss-for-adobe-livecycle-does-not-exist/.

Setting up JBoss to auto reconnect after database outage

Darren Melanson

If you had a database outage or failure while JBoss was up, you’re likely in a situation where you would have to restart JBoss because the database connections didn’t get reconnected for you. You’re likely also faced with a massive set of log files due to the data source complaining about it not being able to connect to the database.

If you want JBoss to automatically reconnect the data source pool(s) for you, here’s some settings to use (only valid if using a “local-tx-datasource”):

1) <autoReconnect>true</autoReconnect>
2) <check-valid-connection-sql>an efficient select statement</check-valid-connection-sql>
3) <failOverReadOnly>false</failOverReadOnly>
4) <maxReconnects>50</maxReconnects>
5) <initialTimeout>15</initialTimeout>

In the above settings, if the data source connectivity is lost (database down or network failure) – then JBoss will automatically attempt to reconnect 50 times every 15 seconds. You can obviously set those numbers to values suitable to your environment. It’s also important to set the failOverReadOnly flag to false as it ensures that recovered connections are writable.

Additionally, some people prefer to include a valid and efficient SQL statement in the “check-valid-connection”, it’s completely optional but a good practice in environments where stale connections are common. Optionally, there’s also “new-connection-sql” which will check on newly created connections.

——-
Original article at http://blogs.adobe.com/livecycle/2011/03/setting-up-jboss-to-auto-reconnect-after-database-outage.html.

Go to Top