TIBCO MDM server start-up failure on JBoss clustered setup
|
Issue 1
|
The following ClassNotFoundException is displayed while starting TIBCO MDM server with ActiveSpaces on JBoss clustered environment.
INF-7508: com.tibco.as.space.ASException: remote_exception Caused by: com.tibco.as.space.ASRemoteException: java.lang.ClassNotFoundException:
|
Start the as-agent by passing the
Djava.ext.dirs=$AS_HOME/lib
parameter.
|
Issue 2
|
The following UnsatisfiedLinkError is displayed while starting TIBCO MDM server with ActiveSpaces on JBoss clustered environment.
Caused by: com.tibco.as.space.RuntimeASException: java.lang.UnsatisfiedLinkError: $AS_HOME/lib/libas-common.so: ld.so.1: java: fatal: $AS_HOME/lib/libas-common.so: wrong ELF data format: ELFDATA2LSB (Possible cause: endianness mismatch)
|
where metaspace_name is the value of com.tibco.cache.as.metaspace property from Configurator and Discovery URL is the value of com.tibco.cim.cache.as.discoveryurl property. This is applicable if the value for the com.tibco.cim.cache.as.distributionrole property is specified as
LEECH.
|
Incorrect cache configuration
|
The following java.lang.RuntimeException is displayed on Linux environment and Windows cluster environment:
:java.lang.RuntimeException: Incorrect configuration for cache. See exception:INVALID_ARG (command_line_arg_invalid - -listen argument tcp://localhost:9805, none of the listen URL is available)
|
For UNIX or Linux:
- On the command line, type
cd etc.
- Type ll.
- Type vi hosts.
The IP address and host name are displayed.
- Type localhost after the host name.
- Save the changes.
For Windows:
- Navigate to
C:\Windows\System32\drivers\etc.
- Open the hosts file. The file contains the mappings of IP addresses to host names.
- Type localhost after host name. For example,
102.54.94.97 rhino.acme.com localhost.
- Save the file.
|
Some Cache operations throw an exception.
|
Some Cache operations, such as, Get, Put, Take, and Update throw an exception. These exceptions are handled by the application.
|
If any errors occur in the Cache Server, restart the Cache server, and then restart TIBCO MDM.
|