VBE 6.5: Getting segmentation fault on RedHat Linux 5.7

VM should not be an issue here.

Do you get any error before lmadm crashes?

I guess, it might be related to installed jdk as well. You should use respective jdk for VB6.5 installation.i.e. 32-bit jdk for 32-bit VB and 64-bit for 64-bit VB installation.

Please check if <VBROKERDIR>/bin/lmadm.config and toolsjdk.config is pointing to the right jdk installation.

From your issue description, I understand that you are using VB6.5. FYI, VB 6.5 is not certified in RHEL 5.7.

Please refer the supported platforms for various VB versions here: supportline.microfocus.com/.../borplatforminfo.aspx

Sorry for super late reply.

I have checked the configuration for jdk is default one and it's working under 64bit environment.

Several tests have been conducted:

1) copy to a VM and run lmadm <= not working (with segmentation fault error)

2) copy the same package to a physical server and run lmadm <= it WORKS

Debug mode was activated during my test, it looks like there is problem on JVM creation, here are the last few lines of log when i run lmadm command

Physical server

============

-Dborland.enterprise.licenseDir=/usr/local/vbroker/Linux/vbe65/bin/../var

-Djava.io.tmpdir=/usr/local/vbroker/Linux/vbe65/bin/../tmp

-Djava.io.tmpdir.autoclean=true

-Dapplication.home=/usr/local/vbroker/Linux/vbe65/bin/..

-Dborland.enterprise.licenseDefaultDir=/usr/local/vbroker/Linux/vbe65/bin/../license

-Dborland.enterprise.licenseDir=/usr/local/vbroker/Linux/vbe65/bin/../var

-Dvbroker.orb.admDir=/usr/local/vbroker/Linux/vbe65/bin/../adm'

   option[ 9] = '-Dlauncher.config.classpath=/usr/local/vbroker/Linux/vbe65/jdk/jdk1.4.2/lib/tools.jar:/usr/local/vbroker/Linux/vbe65/lib/lm.jar:/usr/local/vbroker/Linux/vbe65/lib/sanct4.jar:/usr/local/vbroker/Linux/vbe65/lib/mail.jar'

   option[10] = '-Djava.class.path=/usr/local/vbroker/Linux/vbe65/jdk/jdk1.4.2/lib/tools.jar:/usr/local/vbroker/Linux/vbe65/lib/lm.jar:/usr/local/vbroker/Linux/vbe65/lib/sanct4.jar:/usr/local/vbroker/Linux/vbe65/lib/mail.jar'

   option[11] = '-Dlauncher.jdk.home=/usr/local/vbroker/Linux/vbe65/jdk/jdk1.4.2'

   option[12] = '-Dlauncher.program=/usr/local/vbroker/Linux/vbe65/bin/lmadm'

   option[13] = 'exit' (JNI Invocation API JVM exit hook)

JVM created

Java version "1.4.2_05"

Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_05-b04)

Java HotSpot(TM) Client VM (build 1.4.2_05-b04, mixed mode)

JVM vendor is "Sun Microsystems Inc."...

VM

============

-Dborland.enterprise.licenseDir=/usr/local/mount/vbroker/Linux/vbe65/bin/../var

-Djava.io.tmpdir=/usr/local/mount/vbroker/Linux/vbe65/bin/../tmp

-Djava.io.tmpdir.autoclean=true

-Dapplication.home=/usr/local/mount/vbroker/Linux/vbe65/bin/..

-Dborland.enterprise.licenseDefaultDir=/usr/local/mount/vbroker/Linux/vbe65/bin/../license

-Dborland.enterprise.licenseDir=/usr/local/mount/vbroker/Linux/vbe65/bin/../var

-Dvbroker.orb.admDir=/usr/local/mount/vbroker/Linux/vbe65/bin/../adm'

   option[ 9] = '-Dlauncher.config.classpath=/usr/local/mount/vbroker/Linux/vbe65/jdk/jdk1.4.2/lib/tools.jar:/usr/local/mount/vbroker/Linux/vbe65/lib/lm.jar:/usr/local/mount/vbroker/Linux/vbe65/lib/sanct4.jar:/usr/local/mount/vbroker/Linux/vbe65/lib/mail.jar'

   option[10] = '-Djava.class.path=/usr/local/mount/vbroker/Linux/vbe65/jdk/jdk1.4.2/lib/tools.jar:/usr/local/mount/vbroker/Linux/vbe65/lib/lm.jar:/usr/local/mount/vbroker/Linux/vbe65/lib/sanct4.jar:/usr/local/mount/vbroker/Linux/vbe65/lib/mail.jar'

   option[11] = '-Dlauncher.jdk.home=/usr/local/mount/vbroker/Linux/vbe65/jdk/jdk1.4.2'

   option[12] = '-Dlauncher.program=/usr/local/mount/vbroker/Linux/vbe65/bin/lmadm'

   option[13] = 'exit' (JNI Invocation API JVM exit hook)

Segmentation fault

Is there any configuration or test I could do for this case?

Thanks for your help

Sorry for late reply. We didn't get notification about your post.

You mentioned, you have copied the VisiBroker package to the VM. Is the VM also a 64-bit one? After you copy VisiBroker to the VM, what are the files you modified to update the JDK?

Can you try to point a different JDK installed in that VM?

Please also send me the "java -d64 -version" output and "vbver lmadm" output taken from <VBROKERDIR>/bin folder from the physical server and VM.