VBE 6.5: idl2java/idl2cpp hangs on multi-cpu Linux machines

Problem:

• Product Name: VisiBroker
• Product Version: 6.5
• Product Component: idl2java, idl2cpp
• Platform/OS Version: RedHat Linux 3.0/4.0
• JDK/Compiler Version: 1.4.2

VBE 6.5: idl2java/idl2cpp hangs on multi-cpu Linux machines

When running idl2cpp or idl2java with or without arguments, the process never returns and utilizes 100% of one CPU (shows as 25% in the output of top).

When run under gdb,

#0 0x00bdf514 in JVM_handle_linux_signal ()
from /terra/sw_local/visigenic/Visibroker/6.5p1/Linux/2.x/bin/../jdk/jdk1.4.2/jre/lib/i386/client/libjvm.so
#1 0x00bde728 in signalHandler ()
from /terra/sw_local/visigenic/Visibroker/6.5p1/Linux/2.x/bin/../jdk/jdk1.4.2/jre/lib/i386/client/libjvm.so
#2 
#3 0x0013fd96 in pthread_getspecific () from /lib/tls/libpthread.so.0
#4 0x00bdf0f8 in os::thread_local_storage_at ()
from /terra/sw_local/visigenic/Visibroker/6.5p1/Linux/2.x/bin/../jdk/jdk1.4.2/jre/lib/i386/client/libjvm.so
#5 0x00c2b865 in ThreadLocalStorage::get_thread_slow ()
from /terra/sw_local/visigenic/Visibroker/6.5p1/Linux/2.x/bin/../jdk/jdk1.4.2/jre/lib/i386/client/libjvm.so
#6 0x00bdf42d in JVM_handle_linux_signal ()
from /terra/sw_local/visigenic/Visibroker/6.5p1/Linux/2.x/bin/../jdk/jdk1.4.2/jre/lib/i386/client/libjvm.so
#7 0x00bde728 in signalHandler ()
from /terra/sw_local/visigenic/Visibroker/6.5p1/Linux/2.x/bin/../jdk/jdk1.4.2/jre/lib/i386/client/libjvm.so
#8 
#9 0x00bdf514 in JVM_handle_linux_signal ()
from /terra/sw_local/visigenic/Visibroker/6.5p1/Linux/2.x/bin/../jdk/jdk1.4.2/jre/lib/i386/client/libjvm.so
#10 0x00bde728 in signalHandler ()
from /terra/sw_local/visigenic/Visibroker/6.5p1/Linux/2.x/bin/../jdk/jdk1.4.2/jre/lib/i386/client/libjvm.so
#11 
#12 0x00bdf514 in JVM_handle_linux_signal ()
from /terra/sw_local/visigenic/Visibroker/6.5p1/Linux/2.x/bin/../jdk/jdk1.4.2/jre/lib/i386/client/libjvm.so
#13 0x00bde728 in signalHandler ()
from /terra/sw_local/visigenic/Visibroker/6.5p1/Linux/2.x/bin/../jdk/jdk1.4.2/jre/lib/i386/client/libjvm.so
#14 
#15 0x00bdf514 in JVM_handle_linux_signal ()
from /terra/sw_local/visigenic/Visibroker/6.5p1/Linux/2.x/bin/../jdk/jdk1.4.2/jre/lib/i386/client/libjvm.so
#16 0x00bde728 in signalHandler ()
from /terra/sw_local/visigenic/Visibroker/6.5p1/Linux/2.x/bin/../jdk/jdk1.4.2/jre/lib/i386/client/libjvm.so
#17 
#18 0x00bdf514 in JVM_handle_linux_signal ()
from /terra/sw_local/visigenic/Visibroker/6.5p1/Linux/2.x/bin/../jdk/jdk1.4.2/jre/lib/i386/client/libjvm.so
#19 0x00bde728 in signalHandler ()
from /terra/sw_local/visigenic/Visibroker/6.5p1/Linux/2.x/bin/../jdk/jdk1.4.2/jre/lib/i386/client/libjvm.so

Resolution:

This is due to a known jdk bug and can be resolved by installing a later version of the jdk. The resolution is given on Sun's website as per the link given below.

http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6178600

Author:Meghana Rao