IBM Support

SDI Config Editor (ibmditk) crashes on startup.

Troubleshooting


Problem

The Security Directory Integrator Config Editor (ibmditk) crashes on startup. Core, javacore, and Snap files are created at the time of failure.

Symptom

The lines shown in the console where 'ibmditk' was executed:



    JVMDUMP039I Processing dump event "abort", detail "" at 2015/08/13 10:12:55 - please wait.
    JVMDUMP032I JVM requested System dump using '/opt/IBM/TDI/V7.2/core.20150813.101255.2916.0001.dmp' in response to an event
    JVMPORT030W /proc/sys/kernel/core_pattern setting "|/usr/libexec/abrt-hook-ccpp %s %c %p %u %g %t e" specifies that the core dump is to be piped to an external program. Attempting to rename either core or core.2966.
    JVMDUMP010I System dump written to /opt/IBM/TDI/V7.2/core.20150813.101255.2916.0001.dmp
    JVMDUMP032I JVM requested Java dump using '/opt/IBM/TDI/V7.2/javacore.20150813.101255.2916.0002.txt' in response to an event
    JVMDUMP010I Java dump written to /opt/IBM/TDI/V7.2/javacore.20150813.101255.2916.0002.txt
    JVMDUMP032I JVM requested Snap dump using '/opt/IBM/TDI/V7.2/Snap.20150813.101255.2916.0003.trc' in response to an event
    JVMDUMP010I Snap dump written to /opt/IBM/TDI/V7.2/Snap.20150813.101255.2916.0003.trc
    JVMDUMP013I Processed dump event "abort", detail "".


The lines shown in the workspace/.metadata/.log:


    !ENTRY org.eclipse.jface 2 0 2015-08-13 10:12:53.596
    !MESSAGE Ignored reentrant call while viewer is busy. This is only
    logged once per viewer instance, but similar calls will still be
    ignored.
    !STACK 0
    java.lang.RuntimeException
    at org.eclipse.jface.viewers.ColumnViewer.checkBusy(ColumnViewer.java:763)
    at org.eclipse.jface.viewers.ColumnViewer.refresh(ColumnViewer.java:541)
    at org.eclipse.ui.navigator.CommonViewer.refresh(CommonViewer.java:353)
    at org.eclipse.ui.navigator.CommonViewer.refresh(CommonViewer.java:510)
    at org.eclipse.ui.internal.navigator.resources.workbench.ResourceExtensionContentProvider$3.run(ResourceExtensionContentProvider.java:294)
    at org.eclipse.ui.internal.navigator.resources.workbench.ResourceExtensionContentProvider.runUpdates(ResourceExtensionContentProvider.java:306)
    at org.eclipse.ui.internal.navigator.resources.workbench.ResourceExtensionContentProvider.processDelta(ResourceExtensionContentProvider.java:116)
    at org.eclipse.ui.model.WorkbenchContentProvider.resourceChanged(WorkbenchContentProvider.java:106)
    at org.eclipse.core.internal.events.NotificationManager$1.run(NotificationManager.java:291)
    at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
    at org.eclipse.core.internal.events.NotificationManager.notify(NotificationManager.java:285)
    at org.eclipse.core.internal.events.NotificationManager.broadcastChanges(NotificationManager.java:149)
    at org.eclipse.core.internal.resources.Workspace.broadcastPostChange(Workspace.java:395)
    at org.eclipse.core.internal.resources.Workspace.endOperation(Workspace.java:1530)
    at org.eclipse.core.internal.resources.Project.open(Project.java:1169)
    at org.eclipse.core.internal.resources.Project.open(Project.java:1180)
    at com.ibm.tdi.eclipse.Utils.getTDIServersProject(Utils.java:556)
    at com.ibm.tdi.eclipse.Utils.getTDIServer(Utils.java:717)
    at com.ibm.tdi.eclipse.Activator.createDefaultServer(Activator.java:300)
    at com.ibm.tdi.eclipse.Activator.start(Activator.java:157)
    at org.eclipse.osgi.framework.internal.core.BundleContextImpl$1.run(BundleContextImpl.java:711)
    at java.security.AccessController.doPrivileged(AccessController.java:280)
    at org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActivator(BundleContextImpl.java:702)
    at org.eclipse.osgi.framework.internal.core.BundleContextImpl.start(BundleContextImpl.java:683)
    at org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:381)
    at org.eclipse.osgi.framework.internal.core.AbstractBundle.start(AbstractBundle.java:300)
    at org.eclipse.osgi.framework.util.SecureAction.start(SecureAction.java:440)

Environment

The environment consist of the SDI 7.2.0.2 located on RHEL 6.6 x86_64. The end user uses Xming (X Server on Windows) to export the SDI Config Editor to their Windows desktop.

Diagnosing The Problem

1. Will the Config Editor start on the local Linux Console?
2. Will the Config Editor start, if using a different Xwindow Server?

Resolving The Problem

This particular customer found using a different X Server software (Hummingbird) allowed the Config Editor to start successfully.

[{"Product":{"code":"SSCQGF","label":"Tivoli Directory Integrator"},"Business Unit":{"code":"BU008","label":"Security"},"Component":"General","Platform":[{"code":"PF016","label":"Linux"}],"Version":"7.2","Edition":"","Line of Business":{"code":"LOB24","label":"Security Software"}}]

Document Information

Modified date:
16 June 2018

UID

swg21964517