B Appendix: RIB Installer Common Errors

This appendix provides some common errors encountered during installation to aid in troubleshooting.

Unreadable Buttons in the Installer

If you are unable to read the text within the installer buttons, it could mean that your JAVA_HOME is pointed to an older version of the JDK than is supported by the installer. Set JAVA_HOME to a 1.7.0 64 bit with latest security updates (64 bit for Linux and Solaris OS only) and run the installer again.

Warning: Could not Create System Preferences Directory

Symptom:

The following text appears in the installer Errors tab:

May 22, 2010 11:16:39 AM java.util.prefs.FileSystemPreferences$3 run
WARNING: Could not create system preferences directory. System preferences are
unusable.
May 22, 2010 11:17:09 AM java.util.prefs.FileSystemPreferences
checkLockFile0ErrorCode
WARNING: Could not lock System prefs. Unix error code -264946424.

Solution:

This is related to Java bug 4838770. The /etc/.java/.systemPrefs directory may not have been created on your system. See http://bugs.sun.com for details.

This is an issue with your installation of Java and does not affect the Oracle Retail product installation.

ConcurrentModificationException in Installer GUI

Symptom:

In GUI mode, the Errors tab shows the following error:

java.util.ConcurrentModificationException
........at
 java.util.AbstractList$Itr.checkForComodification(AbstractList.java:448)
........at java.util.AbstractList$Itr.next(AbstractList.java:419)
........etc.

Solution:

You can ignore this error. It is related to third-party Java Swing code for rendering of the installer GUI and does not affect the retail product installation.

Warning: Could Not Find X Input Context

Symptom:

The following text appears in the console window during execution of the installer in GUI mode:

Couldn't find X Input Context

Solution:

This message is harmless and can be ignored.

Message: Problem Occurred during Parsing Input XML Files

Symptom:

The following text appears in the console window during execution of the installer:

ERROR oracle.retail.rib.compiler.Main - Problem occurred during parsing input xml files. Please check the log file(../../../rib-home/application-assembly-home/log) for more details.
.....
Caused by: ValidationException:
.....

Solution:

The rib-deployment-env-info.xml file is validated during the Assembly Phase using stricter criteria than is enforced by the installer input screens. If the validation fails, the installer will print an error message to help you determine the cause of the validation failure. It is recommended that you fix the rib-deployment-env-info.xml file manually, and then re-run the installer with the "Use existing rib-deployment-env-info.xml" option.

rib-app-builder Hangs if a User is Logged in to the Administration Console during Deployment

If the WebLogic server is installed in development mode, the rib-app-builder may "hang" if a user is already logged into the admin console. Click Activate Changes in the admin console to continue with rib-app-builder process every time it happens. To prevent this from occurring, use the option in the WebLogic admin console.

Click the Preferences link on the admin console.
Uncheck the Automatically Acquire Lock and Activate Changes check box.
Click Release Configuration.

The above process will enable only one user to make admin changes to the server. For making admin changes to the console, the user must explicitly acquire the lock, make changes, and release configuration.

Make sure the Release Configuration button in the admin console is disabled before starting to deploy rib apps. So even if you navigate to other screens while deploying RIB apps, the rib deployer will not hang.

Note:

If the WebLogic server is installed in production mode, by default it acquires the lock before making any changes to the server. Therefore, the above steps need not be followed when deploying rib-apps to a WebLogic server running in production mode.