February 2011 Archives
There are of course many things that could cause this issue, but I would like to bring up an interesting case I encountered. The system was running ES2 on Jboss/MySQL. The issue presented itself as rights enabled documents taking 30-40 seconds to open. Upon examining the logs we found several recurring errors, the following being the most noteworthy:
WARN [org.jboss.resource.connectionmanager.TxConnectionManager] Connection error occured: org.jboss.resource.connectionmanager.TxConnectionManager$TxConnectionEventListener@178c7cf[state=NORMAL mc=org.jboss.resource.adapter.jdbc.local.LocalManagedConnection@1b9c3be handles=0 .....
The last packet successfully received from the server was XXXXX milliseconds ago. The last packet sent successfully to the server was 0 milliseconds ago.
When we restarted the server, the logs were clean for 10 minutes or so when connection errors started appearing at increasing rates. This of course pointed to a database connectivity issue, but the connectors appeared to be in good order, and more importantly, we were able to login to the adminUI with no delays. We then disabled security software, reviewed permissions and redeployed all components to Jboss yet the issue persisted.
Upon closer inspection of the clients MySQL installation I found that several .ini files were missing. How these files went missing aside, my expectation is that MySQL would fail to start in such a scenario (which would have generated very different errors). Based on this, it would be safe to assume that this error could also be caused by damaged/corrupted .ini files.
From there it was just a matter of backing up the clients
tables through the command prompt, reinstalling, and then restoring the tables.
If you're experiencing this issue and on 4Point Support be sure to give us a call and we'll make the hotfix available to you.
We have a new hotfix available from Adobe. This one addresses an issue when running a query against a database using
the JDBC component in Workbench/Livecycle 9.5. If any of the returned values are null the component
will return a null pointer exception (java.lang.NullPointerException) instead of simply returning blank values. The hotfix installs easily into Workbench 9.5.
If you're currently experiencing this issue (and on a maintenance and support plan) just give us a call and we'll make the hotfix available to you.
When attempting to add a new user in : adminui -> services -> LiveCycle PDF Generator ES2 -> User Accounts, it results in the following error:
ALC-PDG-030-003-User account information for user pdfg1 is not valid for the machine......
The system.log shows this:
ERROR [STDERROR] sudo
ERROR [STDERROR] : sorry, you must have a TTY to run sudo
The reason for this is an update along the way with sudo locked it down further by adding the below line to /etc/sudoers configuration file:
1 Defaults requiretty
To allow a remote script to login and run a command via sudo simply comment out that line as shown below:
1 # Commented out so remote script can login and run a command without a tty
2 # Defaults requiretty
1. Create a new keystore using the same name and password as the existing one running on the system (note: CN, the user's first and last name, must be the URL for which the keystore is being created):
keytool -genkey -keyalg RSA -alias tomcat -keystore <keystore_name>.keystore
2. Create a certificate request (CSR):
keytool -certreq -alias tomcat -keyalg RSA -file <cert_request_name>.csr -keystore <keystore_name>.keystore
3. Send the CSR to a CA and in return you will receive the CA's root cert path and the cert for your URL.
4. Import into the keystore the CA's root cert (for the certification path):
keytool -import -file <CA_cert>.crt -keystore <keystore_name>.keystore
5. Import into the keystore the cert that the CA generated in response to the CSR:
keytool -import -alias tomcat -trustcacerts -file <new_cert_from_CA>.crt -keystore <keystore_name>.keystore
6. Copy the resulting keystore into jboss/server/all/conf
7. Modify the server.xml by adding the name of and password for the keystore. In your server.xml file, the keystore and keystorePass should look something like the following:
8. Restart JBoss.