Installation Guide for IBM Db2 with Red Hat JBoss

10.4 HotFix 1

Back Next

Troubleshooting the Installation Process

If the installation fails, use the following information to troubleshoot the failure.

Cannot launch the Hub Console

After installation, the Hub Console fails to launch and generates the following error in the log file:

SIP-09131: General Decryption failure and [ERROR] com.delos.util.StringUtil: Unable to decrypt

Encrypt and update the MDM Hub Master Database password or Operational Reference Store password.

To encrypt a database schema password, run the following command from a command prompt:

java -classpath siperian-api.jar;siperian-common.jar;siperian-server.jar com.delos.util.PublicKeyBasedEncryptionHelper <plain text password> <Hub Server
installation directory>

The results are echoed to the terminal window.

To update your Master Database password or Operational Reference Store password, connect as the

cmx_system

user and run the following statement:

UPDATE C_REPOS_DATABASE SET PASSWORD = '<new_password>' WHERE USER_NAME =
<user_name>;
COMMIT;

Run the

postInstallSetup

script.

Hub Server EAR file deployment fails with
concurrent.RejectedExecutionException

The Hub Server EAR file deployment might fail with the exception

concurrent.RejectedExecutionException

To resolve the issue, increase the length of the task queue in the

standalone-full.xml

file.

The following sample shows the

queue-length count

parameter to modify:

<long-running-threads>
  <core-threads count="50"/>
  <queue-length count="300"/>
  <max-threads count="50"/>
  <keepalive-time time="10" unit="seconds"/>
</long-running-threads>

Cannot start JBoss or launch the Hub Console after installation

After installation, JBoss might not restart after you stop JBoss. When you launch the Hub Console, the Hub Console fails to launch and generates the following error:

SIP-09070: Failed to initialize repository layer.

To resolve the issue, run the following code in a batch file to restart JBoss:

rmdir C:\<JBoss installation directory>\standalone\tmp /s /q 
\mkdir C:\<JBoss installation directory>\standalone\tmp 
C:\<JBoss installation directory>\bin\standalone.bat -c standalone-full.xml -b 0.0.0.0

MDM Hub users cannot login

If you re-create the CMX_SYSTEM schema after installation of the Hub Server, the MDM Hub cannot recognize the hashed passwords. As a result, users cannot log in to the MDM Hub.

To resolve the issue, run the

postInstallSetup

script again manually. This script ensures that the passwords of the MDM Hub users are hashed again and users can log in.

Alternatively, if you do not want to run the

postInstallSetup

script again, run the following commands to migrate the user passwords to hashed passwords and create application users.

On UNIX.

cd <MDM Hub installation directory>/server/bin
./sip_ant.sh hash_users_passwords
./sip_ant.sh add_application_users

On Windows.

cd <MDM Hub installation directory>\server\bin
sip_ant.bat hash_users_passwords
sip_ant.bat add_application_users

PostInstallSetUp script fails because the ActiveVOS server deployment times out

When you install the Hub Server, the post-installation setup process might fail after trying to deploy the ActiveVOS server.

To resolve the issue, increase the value of the

deploy.wait.time

property in the

build.properties

file in the following directory:

On UNIX.

<infamdm installation directory>/hub/server/bin

On Windows.

<infamdm installation directory>\hub\server\bin

Operational Reference Store registration fails because the connection times out

When you register the Operational Reference Store (ORS) in a JBoss cluster node, the ORS registration fails with a connection timeout error similar to the following:

SIP-10313: SIP-09061: Failed connecting with provider url abc03.
java.net.ConnectException: JBAS012144: Could not connect to remote://abc03:9999. The connection timed out.

To resolve the issue, when you register an ORS, disable the JBoss administrative security, and then enable the JBoss administrative security after ORS registration.

Hub Server deployment fails because JBoss composite operation fails

When you deploy the Hub Server in the JBoss application server, the Hub Server deployment fails with the following error:

JBAS014653: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-2" => {
			"JBAS014671: Failed services" => {"jboss.web.deployment.default-host./cmx" => "org.jboss.msc.service.StartException in service jboss.web.deployment.default-host./cmx:
			org.jboss.msc.service.StartException in anonymous service: JBAS018040: Failed to start context
Caused by: org.jboss.msc.service.StartException in anonymous service: JBAS018040: Failed to start context"

To resolve the issue, perform the following steps:

Stop the JBoss application server.

Use a text editor to open the

standalone.xml

file in the following directory:

On UNIX.

<JBoss Installation Directory>/standalone/configuration

On Windows.

<JBoss Installation Directory>\standalone\configuration

Find the following code:

<subsystem xmlns="urn:jboss:domain:deployment-scanner:1.1">
        <deployment-scanner path="deployments" relative-to="jboss.server.base.dir" scan-interval="5000"/>
</subsystem>

Add the

deployment-timeout="300"

attribute as shown in the following sample code:

<subsystem xmlns="urn:jboss:domain:deployment-scanner:1.1">
        <deployment-scanner path="deployments" relative-to="jboss.server.base.dir" scan-interval="5000" deployment-timeout="300"/>
</subsystem>

Save changes, and start the JBoss application server.

The default deployment timeout value is

, which is changed to

300

Deploy the Hub Server.

The Hub Server cannot connect to the cmx_system schema

To verify that the Hub Server cannot connect to the cmx_system schema, review the application server log.

To resolve the issue, resolve the database connection issue. Use the application server console to test the connection to the database. If you cannot resolve the connection to the cmx_system schema, re-create the cmx_system schema.

Failed to verify the need to tokenize records

When you run the match process, you might receive the following error:

SIP-16062: Failed to verify the need to tokenize records.

Verify the following environment variable settings:

The library path environment variable must contain the following path:

On UNIX.

<infamdm_install_directory>/hub/cleanse/lib

On Windows.

<infamdm_install_directory>\hub\cleanse\lib

The library path environment variable depends on the operating system:

AIX.

LIBPATH

Suse or RedHat Linux.

LD_LIBRARY_PATH

Windows.

PATH

The

SSAPR

environment variable must include the following path for all users:

On UNIX.

<infamdm_install_directory>/server_install_dir>/cleanse/resources

On Windows.

<infamdm_install_directory>\server_install_dir>\cleanse\resources

If you use the JDBC file loader instead of an SQL loader, verify that the required Process Server properties are set in the

cmxcleanse.properties

file.

The match process requires the following Process Server properties:

cmx.server.java_jdbc_loader=true

cmx.server.tokenize.file_load=false

cmx.server.match.file_load=false

major.minor version errors when loading the Process Server

If you see multiple

major.minor

console errors when you try to load the

Process Server

, check that the system has the correct Java version installed.

Java XAException

When you restart JBoss after you install the Hub Server, the following exception might be generated:

javax.transaction.xa.XAException

You can ignore the exception.

Informatica Address Verification
exception during certification

Informatica Address Verification

generates an exception during certification. Ensure that the stack size for the JVM is sufficient.

Navigate to the bin directory under the JBoss root directory.

Open the following file in a text editor.

On UNIX.

run.sh

On Windows.

run.bat

Set the JAVA_OPTS variable as follows:

JAVA_OPTS=${JAVA_OPTS} -Xss2000k

Save and close the file.

Operational Reference Store does not have a workflow engine configured

If you install the

MDM Hub

and then import an

Operational Reference Store

(ORS) from a previous version, you see a fatal error that indicates that the ORS does not have a workflow engine configured. This error occurs because the Siperian BPM workflow engine is not registered by default. Use the Workflow Manager to register the Siperian BPM workflow engine with the name that the ORS expects to find.

After you deploy the Process Server .ear files, an error occurs

On a Linux environment with WebSphere 8.5.5.9, after you deploy the

Process Server

, the following error occurs:

Too many open files. Unable to start cleanse ear.

Increase the value of the

ulimit

parameter in Linux, and deploy the

Process Server

Troubleshooting the MDM Hub

Download Guide

Watch

Comments

Communities

Knowledge Base

Success Portal

0 COMMENTS

We’d like to hear from you! Log in to comment.

Rename Saved Search

Table of Contents

Installation Guide for IBM Db2 with Red Hat JBoss

Installation Guide for IBM Db2 with Red Hat JBoss

Troubleshooting the Installation Process

Troubleshooting the Installation Process

Cannot launch the Hub Console

Hub Server EAR file deployment fails with concurrent.RejectedExecutionException

Cannot start JBoss or launch the Hub Console after installation

MDM Hub users cannot login

PostInstallSetUp script fails because the ActiveVOS server deployment times out

Operational Reference Store registration fails because the connection times out

Hub Server deployment fails because JBoss composite operation fails

The Hub Server cannot connect to the cmx_system schema

Failed to verify the need to tokenize records

major.minor version errors when loading the Process Server

Java XAException

Informatica Address Verification exception during certification

Operational Reference Store does not have a workflow engine configured

After you deploy the Process Server .ear files, an error occurs

Hub Server EAR file deployment fails with
concurrent.RejectedExecutionException

Informatica Address Verification
exception during certification