0 Replies Latest reply: Oct 26, 2012 5:19 AM by 970853 RSS

    http requests between cluster member on WLS10.3.6

    970853
      Problem Description
      ---------------------------------------------------
      We observed that there are some HTTP requests between 2 cluster members with “GET wls_does_not_exist_url”
      command and we found the responses from different managed servers are different.

      We would like to confirm what this is and we observed that if the response was 500, such request will
      be generated every 3 second and error log was generated.

      2012-09-05 18:15:31 GET wls_does_not_exist_url 404
      2012-09-06 17:16:57 GET wls_does_not_exist_url 200

      what's the purpose for this request, what will be impacted if the return is 500
      instead of 200 or 404 (e.g will the state replication among cluster member be broken or suspended?).

      In WLS 10.3.4 Cluster , this only occur once when startup manager , (in WLS10.3.4 or 10.3.6 standalone server , this stuff no occurs)
      Now in WLS 10.3.6 Cluster , when we startup the manager server , the message " GET wls_does_not_exist_url 500 " will display in access log about 3 seconds until the space used out .

      I checked that the code in Weblogic.jar implements that when detect 500 , then throws the error code every 10 seconds that will
      make our storage out of space .

      Access.log
      =========
      - 2012-09-14 18:01:04 - GET wls_does_not_exist_url
      - 500 0 0.0010
      - 2012-09-14 18:01:07 - GET wls_does_not_exist_url
      500 0 0.0
      - 2012-09-14 18:01:10 - GET wls_does_not_exist_url
      - 500 0 0.0010
      ........................
      Therefore , any solution ?

      ### Recent Changes to this Environment ###
      upgrade from WLS 10.3.4 to 10.3.6

      ### Workaround ###
      in application just catch the exception without throw to upper level with hardcode the url
      (e.g. the 2 WLS cluster just communicate each other but return 500 and then throws error on the access log with the application deploy to context root path )
      If no application deploy to root path , then will display 404 and no more message display again

      ### Impact on Business ###
      in prod env , we can't hardcode this url . That will impact to deploy our application to production env using WLS 10.3.6 in cluster .

      in Summary :
      WLS 10.3.4 - deployed application to context root path and start the managed server only display once for 500
      if not deploy app to context root path , only 404 occur
      there is no message display when using WLS standalone server (10.3.4 and 10.3.6)
      WLS 10.3.6 - deployed application to context root path and start the managed server display many time for 500 error .