Uploaded image for project: 'JBoss Core Services'
  1. JBoss Core Services
  2. JBCS-355

Solaris zips contain dead symlink libnghttp2.so -> libnghttp2.so.14.8.0 yet mod_http2.so still works

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • httpd 2.4.29 DR4
    • httpd 2.4.23 GA, httpd 2.4.23 SP1 ER1, httpd 2.4.29 DR2
    • None
    • None

      It came to our attention (credit: jonderka@redhat.com, preichl@redhat.com) that Soalris zips contain dead symlink to libnghttp2 (libnghttp2.so.14.8.0). It would have meant that h2 tests for 2.4.23 GA somehow executed with different zips or another distribution.

      I checked archived test results where I can see that H/2 worked with the GA zip at the time just fine:

      [Mon Jan 30 15:46:09.011076 2017] [http2:info] [pid 17441] AH03090: mod_http2 (v1.5.11, feats=CHPRIO+SHA256, nghttp2 1.12.0), initializing...
      ...
      [Mon Jan 30 15:46:10.679904 2017] [http2:debug] [pid 17443] h2_session.c(947): [client 10.16.179.24:49738] AH03200: h2_session(1) created, max_streams=100, stream_mem=65536, workers_limit=4, workers_max=1, push_diary(type=1,N=256)
      [Mon Jan 30 15:46:10.680105 2017] [http2:debug] [pid 17443] h2_session.c(1055): [client 10.16.179.24:49738] AH03201: h2_session(1): start, INITIAL_WINDOW_SIZE=65535, MAX_CONCURRENT_STREAMS=100
      [Mon Jan 30 15:46:10.680266 2017] [http2:debug] [pid 17443] h2_session.c(2078): [client 10.16.179.24:49738] AH03079: h2_session(1): started on assigned-ips-service:8747
      [Mon Jan 30 15:46:10.680327 2017] [http2:debug] [pid 17443] h2_session.c(1701): [client 10.16.179.24:49738] AH03078: h2_session(1): transit [INIT] -- init --> [BUSY]
      ...
      10.16.179.24 - - [30/Jan/2017:15:46:10 +0000] "GET /many-tomcats-come-to-kill-your-browser/ HTTP/2.0" 200 128626 "-" "NOE Test Suite - OKHttp3"
      ...
      

      So, I checked with ldd and it looks as if the mod_http2.so does not depend on libnghttp2. It is somewhat bewildering.

      Is it statically linked? If it is the case, could we check the build environment and have the dead symlink removed?

      [hudson@jwssol01-01 modules]$ ldd mod_http2.so 
              libssl.so.10 =>  /tmp/X/jbcs-httpd24-2.4/lib64//libssl.so.10
              libcrypto.so.10 =>       /tmp/X/jbcs-httpd24-2.4/lib64//libcrypto.so.10
              libsocket.so.1 =>        /lib/64/libsocket.so.1
              libnsl.so.1 =>   /lib/64/libnsl.so.1
              libdl.so.1 =>    /lib/64/libdl.so.1
              libuuid.so.1 =>  /lib/64/libuuid.so.1
              libsendfile.so.1 =>      /lib/64/libsendfile.so.1
              librt.so.1 =>    /lib/64/librt.so.1
              libpthread.so.1 =>       /lib/64/libpthread.so.1
              libc.so.1 =>     /lib/64/libc.so.1
              libmp.so.2 =>    /lib/64/libmp.so.2
              libucrypto.so.1 =>       /lib/64/libucrypto.so.1
              libelf.so.1 =>   /lib/64/libelf.so.1
              libcryptoutil.so.1 =>    /lib/64/libcryptoutil.so.1
              libz.so.1 =>     /tmp/X/jbcs-httpd24-2.4/lib64//libz.so.1
      

      WDYT about the issue, gzaronik@redhat.com?

              gzaronik@redhat.com George Zaronikas
              mbabacek1@redhat.com Karm Karm
              Karm Karm Karm Karm
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: