mod_jk on windows 64 bit - apache

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.

Related

Run ColdFusion 9.02 on Apache 2.4 x64

I've inherited an application server which I need to maintain/upgrade.
It's currently running Windows Server 2008R2, ColdFusion 9.02 32-bit and Apache 2.4 32-bit.
Because I want to upgrade/debug/alter the CF source code, I want to use FusionReactor to help me, especially the (line)debugging part.
Unfortunately, FusionReactor only runs (well, the debugging part) on 64bit java. Because the CF application is quite old, it's not ready to run on a newer CF version yet (and I want to port it to Lucee eventually). So, that leaves me the option of CF 9.02 64bit. Problem there is, that it won't run out of the box on Apache 2.4 (only 2.2).
CF 9.02 32bit is currently running on Apache 2.4 because I compiled/patched an Apache 2.2 module (mod_jrun22.so) so it works on Apache 2.4 (with the help of this https://g0blin.co.uk/mod_jrun-on-apache-2-4-ubuntu-14-04-coldfusion-9/ )
Unfortunately, I'm unable to do the same for Apache 2.4 64bit, because there seems to be no apxs 64bit available.
I could downgrade Apache 2.4 -> 2.2, but that's only my last resort.
Now my question. Is somebody able to recompile this module for 64bit, or give me some guidelines to do so? Is apxs available for 64bit? If not, Is there a simple way to compile (custom) modules for Apache 2.4 64bit?
Thanks!
http://www.gpickin.com/index.cfm/blog/multi-cfml-engine-install-extracting-the-coldfusion-9-connector-for-apache
Run it by ./apache_connectors.sh
If you get a GCC not found error, you might have to install some development tools,
to allow you to build the connector.
yum groupinstall 'Development Tools'
You might reach out to Gavin, the author of that article to see if he has any further notes. It's been forever and a day since I had to deal w/ 32-bit CF. I know I managed to get CF 8 to run on 64-bit, which was never officially supported IIRC, but I don't have any of those notes anymore.
You might look to using CommandBox to run your server instead of Apache. It might make your conversion to Lucee easier too. The only reason to convert the engine depends on how much new code is being written for this application. You can get away with CF 9 without the effort of upgrading or converting.

Can 32 bit version of Apache load a 64 bit module?

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.

unable to load mod_wsgi in apache

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

Starting weblogic domain in 32 bit jdk

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

Installing Apache Web Server on 64 Bit Mac

I know that MAC OS X 10.5 comes with Apache installed but I would like to install the latest Apache without touching the OS Defaults incase it causes problems in the future with other udpates. So I have used the details located at: http://diymacserver.com/installing-apache/compiling-apache-on-leopard/ But I'm unsure how to make this the 64 Bit version of Apache as it seems to still install the 32 bit version.
Any help is appreciated
Cheers
Add this to your ~/.bash_profile which means that your architecture is 64-bit ant you’d like to compile Universal binaries.
export CFLAGS="-arch x86_64"
This page claims that a flag for gcc (maix64) should do the trick. Give it a whirl, and if you need any more help, post back here.
Be aware that you may run into issues with your apache modules. If they are compiled in 32-bit mode, then you will not be able to load them into a 64-bit apache.
I had this issue with mod_python, took a bit of thinking to figure out this was the reason.
Don't export CFLAGS from your .bash_profile or any other dot file. Your home directory could live on for decades, the system you're currently using is transient.
There's a guide on Apple's web site, Porting UNIX/Linux Applications to Mac OS X, that talks specifically about how to make autoconf and make and other similar build systems fit into the Mac OS X Universal Binary scheme. If you're going to build cross-Unix applications on Mac OS X, you need to read and understand this guide.
That said, I strongly question why you want to build Apache 64-bit. Just because Leopard can run 64-bit software doesn't mean you want all software on your system to be 64-bit. (It's not Linux.) In fact, virtually none of the software that ships with Leopard runs 64-bit by default, and most of the applications included with Leopard only ship 32-bit.
Unless you have a pressing need to run Apache 64-bit, I wouldn't bother trying to build it that way.
If you would have read a bit further on the same site there is some information on compiling Apache in 64 bits mode!
http://diymacserver.com/2008/10/04/update-on-64-bits-compilation/