https://bz.apache.org/bugzilla/show_bug.cgi?id=60607

--- Comment #14 from Philippe Mouawad <[email protected]> ---
(In reply to Sean Chang from comment #13)
> 1)$ ulimit -a
> core file size          (blocks, -c) 0
> data seg size           (kbytes, -d) unlimited
> scheduling priority             (-e) 0
> file size               (blocks, -f) unlimited
> pending signals                 (-i) 386013
> max locked memory       (kbytes, -l) 64
> max memory size         (kbytes, -m) unlimited
> open files                      (-n) 1024
> pipe size            (512 bytes, -p) 8
> POSIX message queues     (bytes, -q) 819200
> real-time priority              (-r) 0
> stack size              (kbytes, -s) 8192
> cpu time               (seconds, -t) unlimited
> max user processes              (-u) 4096
> virtual memory          (kbytes, -v) unlimited
> file locks                      (-x) unlimited
> 
> 2)the running threads is 100
> 
> 3)I did not compare any version, I just using latest nightly build from
> Jenkins and modify HEAP and NEW size. What kind of version do you want me to
> compare?
> 
> When I tried same test plan on 2.13, I did not remember we meet this issue.

1/ Would you mind checking again on 2.13 ?
We just want to be sure there is no regression in 3.2
2/ Then run with nighlty build and do a 
lsof -p <pid of jmeter> 

Thank you

-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to