I have a 64 bit version of Solaris with a 32 bit bundled version of Apache. I am trying to load mod_wl.so which is a 64 bit module for the apache-weblogic proxy but I get this error:
mod_wl.so: wrong ELF class: ELFCLASS64
to me this suggests that the 32 bit Apache is not compatable with 64 bit modules. My UNIX admin suggests otherwise, citing the modules-64.load file as enabling the 64 bit modules to work with 32 bit Apache.
I'm not convinced, I think he needs to rebuild Apache to 64 bit.
Am I right?
You are right, that's not going to work.
As succinctly answered by #Leeft, this doesn't work.
The modules-64.load file sits alongside modules-32.load. In httpd.conf a check is done on the bit size to determine which of these files to use, so a 64 bit build reads from modules-64.load so that 'directives contained in it are actually available before they are used'. In other words, this has nothing to do with enabling 64 bit modules to work with a 32 bit build - my UNIX admin appears to not know what he is talking about.
So the answer is 'yes I am right' - we need a 64 bit build of Apache or a 32 bit build of the weblogic module. Being that Oracle owns both Sun (Solaris) and Weblogic you'd think that they'd have figured that a the 32 bit default install of Apache on a 64 bit machine would need a 32 bit module, but apparently not.
Related
I Have searched a lot to find the solution but i am unable to find one
whenever i add these lines in my httpd.conf file
LoadModule wsgi_module modules/mod_wsgi.so
my wamp just don't turn online.Nor does it shows any error.
I hav added the mod_wsgi.so file in the correct folder.
Although i have 64 bit windows but i tried adding both 32 bit and 64 bit mod_wsgi but both didn't work.
Need a great help.
PS:i just want to run a simple logic in python by taking input from a webpage and showing output on same page.If someone could suggest some other way...
All of Python, Apache and mod_wsgi.so must be either 32 bit or 64 bit. You cannot mix such that some are 32 bit and some are 64 bit. Also, the Python must be installed for all users on the system and not just the user you installed it as. The mod_wsgi.so must be compiled for the Apache version you are using.
Apache 2.4.2 ?
mod_wsgi 3.3 doesn't support Apache 2.4
How to determine whether library is 32 bit or 64 bit from the library file ? I have installed gstreamer from ossbuild for this I know its 32 bit but suppose if someone else installs a library what is the way to find if it is compatible with 32bit or 64bit . Also are the format of the library similar or they differ?
When you said "Library", I guess you mean "runtime Library" aka. Dynamic-Link Library (DLL), is that correct?
In that case, this might be a duplicate of this question
I am using weblogic 10.3 on a 64 bit sparc machine.
The domains on this installation run on a 64 bit jdk version.
I would like to run one domain using a 32 bit jdk version while the rest of the domains run on 64 bit jdk.
Is this possible? If yes, what change needs to be made on the setDomainEnv.sh file ?
Further update
Set domain does not have a -d64 for the weblogic 10.3.5 version. There is a JAVA_USE_BIT variable which is set to 64 bit in the commonEnv.sh. But that is changed, all domain will start in 32 bit jdk.
So there has to be some other way to start only once domain in 32 bit.
Check your setDomainEnv.sh for a -d64 flag passed into the USER_MEM_ARGS or JAVA_OPTIONS
This is to use a 64-bit JDK, try removing that flag for 32-bit.
check the same in the startWeblogic sh
But I'm not sure everything will work okay, there are some reported errors on various forums
our target production environment is Win2003 + SQL2005 + .NET 2.0 (all 32 bit);
Currently We have new developing PCs comming in and they are 64 bit capable.
As a developer PC, we want real raw installation instead of VM solution.
I know 64 bit IDE installation (win7 X64 + VS 2010 X64) will give us bigger RAM and faster response and I know 32 bit application can run in 64 bit environment through WOW (windows 32 on Windows 64) .
My concerns:
(1) 3rd party DLLs are 32 bit and might give us debugging troubles in 64 bit environment.
(2) The production target platform is 32 bit, it might give us some troubles to adjust 64 bit develoment environment to fit the target.
(3) Because the WOW is the mechanisim for 32 bit process running under 64 bit environment, No big performance gain (testing & developing the 32 bit code) just because it's 64 bit IDE environment.
Are my concerns valid?
I really want to know if the 64 bit PC development environment could improve our developing process (for 32 bit target) or might just end up giving us a bunch of troubles instead.
Thanks a lot.
Support for 32 bit development on a 64 bit platform has in my experience been flawless. That said, with a modern computer I doubt you will notice much difference in responsiveness and speed of the development process between the two. You would probably know this better than me, though, as only you know the details of what you are going to develop and how resource hungry said development will be. If you are just writing code, you could probably do that on a Commodore 64.
If you really think there is a reason to pick 64 bit, then I doubt you will run into much trouble. Installing a virtual machine is easy as a backup solution. Even if the 64 bit installation turns out to be a bad decision, you could always set up a dual boot, or just reinstall the OS. To be honest I think you are worrying too much :)
Sorry to contradict you, but information in your question is wrong. VS 2010 is 32-bit IDE. Support for 64-bits is provided by a set of compilers&tools. You can just select an options of not installing them.
You might have some issues with COM servers registration (like necessity to use SysWOW64 version of regsvr32 and use corresponding regedit), but again - if you have more than 3GB of RAM then x64 environments are worth a bit of pain caused by x64 redirection.
But I'd suggest you to move only if you feel that your current performance is not good enough. It might be more reasonable to perform cheap h/w upgrades rather than buying all that expensive stuff like new OS, new Visual Studio, etc
64-bit machine will let you catch virtualized registry errors easier. And also, only commercial virtual machines support 64 bit OSes if I'm not mistaken. I'd recommend 64 bit machine for development. You can really use more RAM too.
Anyone know where to get a windows 64 bit shared object for mod_jk. I've just moved to 64 bit machine. It's not where I would expect to find it: http://www.apache.org/dist/tomcat/tomcat-connectors/jk/binaries/win64/jk-1.2.28/ia64/
I found various binaries for windows here:
http://www.apache.org/dist/tomcat/tomcat-connectors/jk/binaries/windows/
It worked for me in apache 2.2 32-bit.
So far the best place to find 64 bit binaries for mod_jk is Apache Lounge. Otherwise, the only way to do this is to download sources and then compile them for 64 bit platform. The instruction is included in readme file. It will point you to native/building.txt with more details on how to achieve this. Here is also a discussion regarding 64bit download for mod_jk that maybe helpful.