| Startup problems
|
If the normal login page is not displayed and instead you see a message Application is not available, please contact system administrator, it implies that TIBCO MDM startup has failed. This could be due to several reasons, but the most likely are:
- The EMS server did not start up or the connection URL was not provided correctly.
- All queues did not get created.
- The configuration file ConfigValues.xml file has syntax errors and/or the file is missing.
- Values such like JNDI port are not correct.
|
- Use the following link to check the reason for failure.
http://machine:port/eml/Startup
- Refer to the Log file -
$MQ_HOME/log/elink.log - for more detailed information
Notes:
- TIBCO MDM startup failures do not affect the Application server or other applications installed on same container
- All initialization failure cases are handled except database related failures.
- If your database is not connected or if the data source configuration has not been done properly, such errors are not handled or detected. In such cases, TIBCO MDM will not be available, but if database and data source are not configured properly the page
http://machine:port/eml/Startup may be available.
|
| Startup failure due to missing node ID
|
If
NODE_ID is not specified as a JVM argument, the application does not start up.
|
The
NODE_ID should be set at the OS level, otherwise you cannot use any utilities provided by TIBCO MDM, which are located in
$MQ_HOME/bin.
|
| Startup failure on Solaris with JBoss 5.1 GA version
|
When you start the application on Solaris with the JBoss Application Server 5.1 GA version, the JBoss fails to start and the following error message is displayed:
21:55:09,563 ERROR [AbstractKernelController] Error installing to Instantiated: name=AttachmentStore state=Described
java.lang.IllegalArgumentException: Wrong arguments. new for target java.lang.reflect.Constructor expected=[java.net.URI] actual=[java.io.File]
atorg.jboss.reflect.plugins.introspection.ReflectionUtils.handleErrors(ReflectionUtils.java:395)
atorg.jboss.reflect.plugins.introspection.ReflectionUtils.newInstance(ReflectionUtils.java:153)
|
To fix this, specify the parameter type for constructor in the
profile.xml file that is located at
$JBOSS_HOME/server/<configserver_name>/conf/bootstrap.
The
profile.xml file contains the following configuration for AttachmentStore:
<bean name="AttachmentStore" class="org.jboss.system.server.profileservice.repository.AbstractAttachmentStore"> <constructor><parameter><inject bean="BootstrapProfileFactory" property="attachmentStoreRoot" /></parameter></constructor>
Multiple constructors are available for the org.jboss.system.server.profileservice.repository.AbstractAttachmentStore class. MC bean randomly picks up one of the available constructors and shows exceptions. Therefore, replace the AttachmentStore configuration with the following:
<bean name="AttachmentStore" class="org.jboss.system.server.profileservice.repository.AbstractAttachmentStore"> <constructor><parameter class="java.io.File"><inject bean="BootstrapProfileFactory" property="attachmentStoreRoot" /></parameter></constructor>
Notice the use of class="java,io.File" for the constructor parameter in case of JDK 1.7.0_update 22 on Solaris sparc 5.10.
|
| Startup failure on HP-UX WAS
|
If TIBCO MDM is deployed on WebSphere Application Server and on HP-UX operating system, sometimes create_thread_failure error appears during the application initialization. Error message is as follows:
com.tibco.as.space.ASException: TIBAS_SYS_ERROR create_thread_failure - error=11)
at Native.start(Thread.cpp:159)
at Native.start(Actor.cpp:44)
at Native.initialize(SpaceEventBrowser.cpp:52)
at Native.browseEvents(BrowserMessage.cpp:168)
at Native.Java_com_tibco_as_space_impl_NativeImpl_metaspaceCreateEventBrowser(BrowserMessage.cpp:210)
at com.tibco.as.space.impl.NativeImpl.metaspaceCreateEventBrowser(Native Method)
at com.tibco.as.space.impl.ASMetaspace.browseEvents(ASMetaspace.java:290)
at com.tibco.as.space.impl.ASListenerAdapterThread.<init>(ASListenerAdapterThread.java:70)
at com.tibco.as.space.impl.ASMetaspace.listen(ASMetaspace.java:323)
|
To resolve the issue, increase the allocation of threads available for a process by setting the value of the max_thread_proc tunable kernel parameter to 1024.
|
| Startup failure on JBoss Application Server WildFly 10.1.0 version
|
| Issue 1
|
Error while starting JBoss Application Server WildFly 10.1.0.
|
Delete the tmp directory in the JBoss WildFly 10.1.0 instance and restart.
|
| Issue 2
|
The JBoss Application Server fails to start and the following error message is displayed:
Failed to start service jboss.deployment.unit."ECM.ear".POST_MODULE: org.jboss.msc.service.StartException in service jboss.deployment.unit."ECM.ear".POST_MODULE: Failed to process phase POST_MODULE of deployment "ECM.ear"
|
Remove the following jaxrs entries from the
standalone.xml file located in the
$JBOSS_HOME/standalone/configuration directory:
<extension module="org.jboss.as.jaxrs"/>
<subsystem xmlns="urn:jboss:domain:jaxrs:1.0"/>
|
| Issue 3
|
The JBoss Application Server fails to start and the following error message is displayed:
Code: JAV-8001: Unexpected error. Class: 'com.tibco.mdm.infrastructure.globalobj.GlobalObjInitializer' and method name: 'createAndInitObject'. Additional information: java.lang.IllegalStateException: No EJB receiver available for handling [appName:ECM,modulename:DomainSsnDeploy,distinctname:] combination for invocation context org.jboss.ejb.client.EJBClientInvocationContext@4bcf8384.
|
To resolve the issue, define a new pool and increase the EJB pool size as follows:
Open the
standalone.xml file located at
$JBOSS_HOME\standalone\configuration
Navigate to the
<subsystem xmlns="urn:jboss:domain:ejb3:1.2"> section, and define the following new pool and specify its pool size:
<pools> <bean-instance-pools>
<strict-max-pool name="mdm-pool" max-pool-size="500" instance-acquisition-timeout="5" instance-acquisition-timeout-unit="MINUTES"/>
</bean-instance-pools>
</pools>
Save the updated
standalone.xml file.
|
