wood burning stoves 2.0*
The moose likes JBoss/WildFly and the fly likes libdmcl40.so: wrong ELF class: ELFCLASS32 (architecture word width mismatch) Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of OCM Java EE 6 Enterprise Architect Exam Guide this week in the OCMJEA forum!
JavaRanch » Java Forums » Products » JBoss/WildFly
Bookmark "libdmcl40.so: wrong ELF class: ELFCLASS32 (architecture word width mismatch)" Watch "libdmcl40.so: wrong ELF class: ELFCLASS32 (architecture word width mismatch)" New topic
Author

libdmcl40.so: wrong ELF class: ELFCLASS32 (architecture word width mismatch)

Ramakanta Sahoo
Ranch Hand

Joined: Aug 23, 2008
Posts: 254

Hi All,

*Dont know where to post it so posted it in JBoss.*
We are using Documentum content server 5.x and 6.5SP1 for Linux Oracle.
Our Application is onJBOSS EAP 4.3 in RHEL 5.1 64-bit Intel Xeon Processor.
I have configured every variable like LD_LIBRARY_PATH,DOCUMENTUM,DM_HOME,DOCUMENTUM_SHARED,etc and libdmcl40.so is in CLASSPATH also.

When am doing a file libdmcl40.so its giving me following details
"libdmcl40.so: ELF 32-bit LSB shared object, Intel 80386, version 1 (SYSV), not stripped"

Though all configurations are correct my documentum session manager could not be created. when I'm starting its throwing below error.

The same configuration and file is working fine in 32-bit Linux environment.


I'm suspecting this error is because of a 32-bit libdmcl40.so lib file instead of 64-bit.
If its correct then please point me where to get a 64-bit libdmcl40.so file.

Or if there is any work around to make this work then please do suggest me.
Please help me as its urgent requirement for one of our client.

Thanks and regards.
Ricky


Regards, Ricky
Oracle Weblogic 10g Certified Expert TechPaste.Com
Peter Johnson
author
Bartender

Joined: May 14, 2008
Posts: 5823
    
    7

You guessed it correctly - you cannot load 32-bit shared object into the 64-bit process. There are two ways to fix this:

a) You could install and use a 32-bit JVM. You will have to get the JVM from the Sun web site and install it yourself; do not use your distro's package manager (as far as I know, all of it's JVMs will be 64-bit if the OS is 64-bit).)

b) You need to get a 64-bit shared object. This means checking with the shared object's vendor to see if they have one for 64-bit.


JBoss In Action
Ramakanta Sahoo
Ranch Hand

Joined: Aug 23, 2008
Posts: 254

Ya Peter .

I tried with the standalone 32-bit 1.5.0_15 Sun Java and now the error for 64-bit compatibility is gone but ma still not able to start the documentum session.

its giving me a new error:


So as suggested i checked the dmcl.ini file and everything is fine there.
I also checked whether it pinging and telnet on that port Documentum server absolutely fine.

I googled and found THIS link but there is not have much to learn. I checked the server.log also but didnt fint any trace about documentum.

I dont know now what to do .
Please help me.

Thanks,
Ricky
Peter Johnson
author
Bartender

Joined: May 14, 2008
Posts: 5823
    
    7

This looks like a problem with documentum, you will have to ask them.
Ramakanta Sahoo
Ranch Hand

Joined: Aug 23, 2008
Posts: 254

Yeh Peter I think same also.

But am in a confusion as our admin's told me that the same server is working fine for other 32 bit instances.

May be for 64bit instances documentum is not working fine.

Anyway am not also getting any suggestion's about resolving the same in the documentum forum also.

Thanks for the inputs.

-Ricky
Peter Johnson
author
Bartender

Joined: May 14, 2008
Posts: 5823
    
    7

the same server is working fine for other 32 bit instances.


Go back and read my option "a)" again...

You cannot load a 32-bit shared objects into a 64-bit executable. However, 32-bit executables run fine in and x64 operating system.
 
 
subject: libdmcl40.so: wrong ELF class: ELFCLASS32 (architecture word width mismatch)