top button
Flag Notify
    Connect to us
      Facebook Login
      Site Registration

Facebook Login
Site Registration

Apache: HTTP support for RDMA implementation

+1 vote

I am working on an assignment which involves enabling RDMA (Remote Direct Memory Access) using HTTP protocol. I came across multiple RFCs which theoretically states that rdma can be implemented via any TCP protocol, but I was not getting enough resources or knowledge base on the practical implementations with respective to http and rdma.

I would like to know if any of you have any suggestions?

posted Dec 26, 2013 by Ahmed Patel

Looking for an answer?  Promote on:
Facebook Share Button Twitter Share Button LinkedIn Share Button

Similar Questions
+1 vote

I am planning to upgrade my apache2.2 to 2.4., i have 2 questions before where i need your help.

Former SPDY Implementation conflicts with non-threadsafe Modules like mod_php. To use SPDY it is necessary to use worker-mpm and php-cgi.
Now HTTP/2 is new standard and i would like to know if HTTP/2 Implementation has same conflicts with non-threadsafe Modules like mod_php. As far as I know HTTP/2 is based on SPDY.

I have some non-standard Modules compiled and packaged for Apache2.2. Is it possible to use these Modules again on Apache2.4 or is it necessary to compile all new for new Apacheversion?

+2 votes

I want the images should be accessible as part of http page only not by any other mean, no clue any suggestion would have great help.

+1 vote

We have a set up like Apahce (80,443) redirects the request to Tomcat (8080) using mod_jk.

The new requirement is to route the request from the same apache to another tomcat (8090). Hence I made the different config file for apache with different ports (86,4444) and different worker for mod_jk which routes the request to tomcat.

Now the issue is when I hit the url http://:86 and after providing the credentials, it is redirecting to https://:86 and throwing the below error.

Error in browser:

Secure Connection Failed

An error occurred during a connection to x.x.x.x:86. SSL received a record that exceeded the maximum permissible length. (Error code: ssl_error_rx_record_too_long)

Error in logs:

"x16x03x01" 501

[Thu Jan 08 08:22:46 2015] [debug] ssl_engine_io.c(1523): OpenSSL: I/O error, 11 bytes expected to read on BIO#1bf568 [mem: 1f3930]
[Thu Jan 08 08:22:46 2015] [debug] ssl_engine_kernel.c(1806): OpenSSL: Exit: error in SSLv2/v3 read client hello A
[Thu Jan 08 08:22:46 2015] [info] (70014)End of file found: SSL handshake interrupted by system [Hint: Stop button pressed in browser?!]
[Thu Jan 08 08:22:46 2015] [info] Connection to child 3 closed with abortive shutdown(server [2], client
[Thu Jan 08 08:23:53 2015] [error] [client] Invalid method in request x16x03x01

Could you please suggest where it might went wrong and the way forward..

+1 vote

I am facing the issue while building apache on Window machine with the help of apache source code and got below error

[ 92%] Building C object CMakeFiles/mod_ssl.dir/modules/ssl/ssl_engine_init.c.obj 
C:apacheBuildapache2.4buildhttpd-2.4.33modulessslssl_engine_init.c(33) : fatal error C1083: Cannot open include file: 'mod_md.h': No such file or directory 
NMAKE : fatal error U1077: 'c:PROGRA~2MICROS~2.0VCbinamd64cl.exe' : return code '0x2' 

I did some investigation and found that with new version of apache we added a new module called MOD_MD which is experimental basis, I don't know why experimental module added as a dependency and it will cause a build failure,

Can you please help me out to fix above issue?

Contact Us
+91 9880187415
#280, 3rd floor, 5th Main
6th Sector, HSR Layout
Karnataka INDIA.