• Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Critical Critical
    • _unsorted
    • None
    • java version "1.8.0_171"
      tomcat: 8.0.28
      jenkins 2.134
      centos7
      LDAP plugin : 1.2.0

      For the first time,it will be normal when I restart the tomcat.

      It didn't take long to hang on.

      I executed the command: jstack [tomcat_pid], find my access is blocked.

      "Handling POST /jenkins/view/%E6%95%B0%E6%8D%AE%E4%B8%9A%E5%8A%A1%E7%BA%BF/ajaxExecutors from [MY IP] : http-nio-8080-exec-3" #56 daemon prio=5 os_prio=0 tid=0x00007f1810004800 nid=0x3ad waiting for monitor entry [0x00007f189e460000]
      java.lang.Thread.State: BLOCKED (on object monitor)

       

      It takes a long time for normal access and then is wait for response.I don't know how to slove it.

      Is it due to insufficient memory?

      Looking forward to your reply

       

       

        1. systemlog.txt
          38 kB
        2. jstack2.txt
          77 kB
        3. jstack1.txt
          51 kB
        4. free_h.png
          free_h.png
          9 kB

          [JENKINS-55102] jenkins is waitingf for response

          Oleg Nenashev added a comment -

          Something weird is going on with the LDAP plugin, but it may be a normal behavior as well (maybe LDAP availability issue). It's hard to say anuthing without the Jenkins version and system logs

          Oleg Nenashev added a comment - Something weird is going on with the LDAP plugin, but it may be a normal behavior as well (maybe LDAP availability issue). It's hard to say anuthing without the Jenkins version and system logs

          tang alby added a comment - - edited

          jenkins version is 2.134.

          jenkins systemlog  is uploaded.But there is no information about [MY IP] in the system information

          Thanks~

           

          tang alby added a comment - - edited jenkins version is 2.134. jenkins systemlog  is upload ed. But there is no information about [MY IP] in the system information Thanks~  

          tang alby added a comment -

          add “ou=” in LDAP settings

          tang alby added a comment - add “ou=” in LDAP settings

            Unassigned Unassigned
            alby tang alby
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: