[
https://issues.apache.org/jira/browse/TS-947?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13107719#comment-13107719
]
mohan_zl commented on TS-947:
-
One question:
The variable sleep_wait in struct AIOThreadInfo is no
[
https://issues.apache.org/jira/browse/TS-915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13088251#comment-13088251
]
mohan_zl commented on TS-915:
-
Remember i have discussed with weijin, these functions have no prob
[
https://issues.apache.org/jira/browse/TS-844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
mohan_zl closed TS-844.
---
Resolution: Fixed
Seems not reproduced now, and close it temporarily.
> ReadFromWriter fail in CacheRead.cc
> --
[
https://issues.apache.org/jira/browse/TS-880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13086737#comment-13086737
]
mohan_zl commented on TS-880:
-
@William
1. I think function initialize_thread_for_net will assign
[
https://issues.apache.org/jira/browse/TS-880?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
mohan_zl updated TS-880:
Attachment: performance_2nd_req_another_version.patch
Thank you William for your work, we tested your first diff file,
[
https://issues.apache.org/jira/browse/TS-844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
mohan_zl updated TS-844:
Attachment: TS-844-2.patch
> ReadFromWriter fail in CacheRead.cc
> ---
>
>
[
https://issues.apache.org/jira/browse/TS-844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
mohan_zl updated TS-844:
Attachment: (was: TS-844-2.patch)
> ReadFromWriter fail in CacheRead.cc
> ---
>
>
[
https://issues.apache.org/jira/browse/TS-844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
mohan_zl updated TS-844:
Attachment: TS-844-2.patch
> ReadFromWriter fail in CacheRead.cc
> ---
>
>
[
https://issues.apache.org/jira/browse/TS-844?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13082981#comment-13082981
]
mohan_zl commented on TS-844:
-
@John Plevyak
The crash resulted from "ink_assert (w->alternate.val
[
https://issues.apache.org/jira/browse/TS-844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
mohan_zl updated TS-844:
Attachment: (was: TS-844-2.patch)
> ReadFromWriter fail in CacheRead.cc
> ---
>
>
[
https://issues.apache.org/jira/browse/TS-844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
mohan_zl updated TS-844:
Comment: was deleted
(was: @John Plevyak
This problem is hard to reproduce now, but i think the reason is because: when
[
https://issues.apache.org/jira/browse/TS-844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
mohan_zl updated TS-844:
Attachment: TS-844-2.patch
> ReadFromWriter fail in CacheRead.cc
> ---
>
>
[
https://issues.apache.org/jira/browse/TS-844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
mohan_zl updated TS-844:
Attachment: (was: TS-844-2.patch)
> ReadFromWriter fail in CacheRead.cc
> ---
>
>
[
https://issues.apache.org/jira/browse/TS-844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
mohan_zl updated TS-844:
Attachment: TS-844-2.patch
@John Plevyak
This problem is hard to reproduce now, but i think the reason is because: when
code cleanup for format
---
Key: TS-909
URL: https://issues.apache.org/jira/browse/TS-909
Project: Traffic Server
Issue Type: Bug
Reporter: mohan_zl
Attachments: TS-format-fix_1.patch
--
This messa
[
https://issues.apache.org/jira/browse/TS-909?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
mohan_zl updated TS-909:
Attachment: TS-format-fix_1.patch
Fix the net format error
> code cleanup for format
> ---
>
>
[
https://issues.apache.org/jira/browse/TS-887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
mohan_zl updated TS-887:
Attachment: code_cleanup3.patch
I don't know why current codes is implemented like this, in linux, kernel
2.6.38, i th
[
https://issues.apache.org/jira/browse/TS-887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
mohan_zl updated TS-887:
Attachment: code_cleanup2.patch
I think the enum structure is not used, so nuke it.
> Code cleanup
>
>
>
[
https://issues.apache.org/jira/browse/TS-887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
mohan_zl updated TS-887:
Attachment: code_cleanup1.patch
Correct the code format
> Code cleanup
>
>
> Key: TS-887
Code cleanup
Key: TS-887
URL: https://issues.apache.org/jira/browse/TS-887
Project: Traffic Server
Issue Type: Bug
Reporter: mohan_zl
Try to nuke some unused codes, not changing current logic.
--
This message is a
[
https://issues.apache.org/jira/browse/TS-654?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
mohan_zl updated TS-654:
Attachment: hc.patch
> request for support of Layer7 http health checking for Origin Servers
>
[
https://issues.apache.org/jira/browse/TS-654?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
mohan_zl updated TS-654:
Attachment: (was: health_check.patch)
> request for support of Layer7 http health checking for Origin Servers
> ---
[
https://issues.apache.org/jira/browse/TS-857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
mohan_zl updated TS-857:
Fix Version/s: (was: 3.1.0)
3.1.1
> Crash Report: HttpTunnel::chain_abort_all -> HttpServerSessi
[
https://issues.apache.org/jira/browse/TS-848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
mohan_zl updated TS-848:
Fix Version/s: (was: 3.1.0)
3.1.1
> Crash Report: ShowNet::showConnectionsOnThread -> ShowCont::
[
https://issues.apache.org/jira/browse/TS-851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
mohan_zl closed TS-851.
---
Resolution: Fixed
> unable to run TS without a real interface
> -
>
>
[
https://issues.apache.org/jira/browse/TS-835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
mohan_zl closed TS-835.
---
Resolution: Fixed
Not reproduce this problem again, now first close it and wait for another
report.
> Crash Report: hea
[
https://issues.apache.org/jira/browse/TS-801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
mohan_zl updated TS-801:
Fix Version/s: (was: 3.1.0)
3.1.1
> Crash Report: enable update will triger Segmentation fault
>
[
https://issues.apache.org/jira/browse/TS-832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
mohan_zl updated TS-832:
Fix Version/s: (was: 3.1.0)
3.1.1
> Crash Report: RecMessageMarshal_Realloc in cluster mode 2
>
[
https://issues.apache.org/jira/browse/TS-725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
mohan_zl updated TS-725:
Fix Version/s: (was: 3.1.0)
3.1.1
> Crash Report: url_host_set in 2.1.6
> --
[
https://issues.apache.org/jira/browse/TS-726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
mohan_zl closed TS-726.
---
Resolution: Fixed
Never reproduce this problem, close and wait for another issue.
> Crash Report: DNSEntry::post in 2.1.
[
https://issues.apache.org/jira/browse/TS-852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
mohan_zl closed TS-852.
---
Resolution: Fixed
This issue is covered by TS-833
> hostdb and dns system hangup
>
>
>
[
https://issues.apache.org/jira/browse/TS-796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
mohan_zl updated TS-796:
Fix Version/s: (was: 3.1.0)
3.1.1
> Crash Report: mime_str_u16_set, possible
> -
[
https://issues.apache.org/jira/browse/TS-849?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
mohan_zl updated TS-849:
Fix Version/s: (was: 3.1.0)
3.1.1
> proxy.config.http.slow.log.threshold is unable to set from t
[
https://issues.apache.org/jira/browse/TS-813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
mohan_zl updated TS-813:
Fix Version/s: (was: 3.1.0)
3.1.1
> http_ui /stat/ should response with content type
> -
[
https://issues.apache.org/jira/browse/TS-874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
mohan_zl resolved TS-874.
-
Resolution: Fixed
fixed, and closed
> asf-dist should be git nice
> ---
>
>
[
https://issues.apache.org/jira/browse/TS-745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
mohan_zl updated TS-745:
Attachment: TS-ssd-2.patch
TS-ssd-2.patch correct the log stats, and add a
"proxy.config.cache.ram_cache.ssd_percent"
[
https://issues.apache.org/jira/browse/TS-873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
mohan_zl updated TS-873:
Attachment: TS-net2.patch
In iocore/net/UnixNet.cc, line95, s/read_ready_list/write_read_list
> Wrong code in iocore/n
Wrong code in iocore/net/UnixNet.cc
---
Key: TS-873
URL: https://issues.apache.org/jira/browse/TS-873
Project: Traffic Server
Issue Type: Bug
Reporter: mohan_zl
I think somebody write a wrong cod
[
https://issues.apache.org/jira/browse/TS-869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
mohan_zl updated TS-869:
Comment: was deleted
(was: The attached patch fixes this problem.)
> The stat code for ram_cache miss is lost
> --
[
https://issues.apache.org/jira/browse/TS-869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13060436#comment-13060436
]
mohan_zl commented on TS-869:
-
The attached patch fixes this problem.
> The stat code for ram_cac
[
https://issues.apache.org/jira/browse/TS-870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
mohan_zl updated TS-870:
Attachment: TS-evacuate-correct.patch
Try to fix this problem, the default behavior is not use this feature.
> Somethi
[
https://issues.apache.org/jira/browse/TS-870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13060434#comment-13060434
]
mohan_zl commented on TS-870:
-
Try to fix this problem, the default behavior is not use the evacua
Something wrong with the evacuate relevant codes in cache
-
Key: TS-870
URL: https://issues.apache.org/jira/browse/TS-870
Project: Traffic Server
Issue Type: Bug
Reporter: m
[
https://issues.apache.org/jira/browse/TS-869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
mohan_zl updated TS-869:
Attachment: ram_cache_miss.patch
The patch have fixed this problem.
> The stat code for ram_cache miss is lost
> -
The stat code for ram_cache miss is lost
Key: TS-869
URL: https://issues.apache.org/jira/browse/TS-869
Project: Traffic Server
Issue Type: Bug
Reporter: mohan_zl
Use echo "show:cache-sta
[
https://issues.apache.org/jira/browse/TS-857?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13058160#comment-13058160
]
mohan_zl edited comment on TS-857 at 7/1/11 12:55 AM:
--
The following stac
[
https://issues.apache.org/jira/browse/TS-857?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13058160#comment-13058160
]
mohan_zl commented on TS-857:
-
#0 ink_stack_trace_get (stack=, len=, signalhandler_frame=) at ink
[
https://issues.apache.org/jira/browse/TS-745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13056348#comment-13056348
]
mohan_zl commented on TS-745:
-
I have been testing this patch for some days, and now it looks stab
[
https://issues.apache.org/jira/browse/TS-745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
mohan_zl updated TS-745:
Attachment: TS-ssd.patch
> Support ssd
> ---
>
> Key: TS-745
> URL: https://iss
[
https://issues.apache.org/jira/browse/TS-745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
mohan_zl updated TS-745:
Attachment: (was: ssd_cache2.patch)
> Support ssd
> ---
>
> Key: TS-745
> U
[
https://issues.apache.org/jira/browse/TS-745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
mohan_zl updated TS-745:
Attachment: TS-ssd.patch
> Support ssd
> ---
>
> Key: TS-745
> URL: https://iss
[
https://issues.apache.org/jira/browse/TS-745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
mohan_zl updated TS-745:
Attachment: (was: ssd_cache.patch)
> Support ssd
> ---
>
> Key: TS-745
> UR
[
https://issues.apache.org/jira/browse/TS-745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
mohan_zl updated TS-745:
Attachment: (was: TS-ssd.patch)
> Support ssd
> ---
>
> Key: TS-745
> URL:
[
https://issues.apache.org/jira/browse/TS-745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
mohan_zl updated TS-745:
Attachment: (was: TS-ssd.patch)
> Support ssd
> ---
>
> Key: TS-745
> URL:
[
https://issues.apache.org/jira/browse/TS-745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
mohan_zl updated TS-745:
Attachment: TS-ssd.patch
Latest ssd patch.
> Support ssd
> ---
>
> Key: TS-745
>
[
https://issues.apache.org/jira/browse/TS-833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13053568#comment-13053568
]
mohan_zl commented on TS-833:
-
{code}
#0 ink_stack_trace_get (stack=, len=, signalhandler_frame=)
[
https://issues.apache.org/jira/browse/TS-844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
mohan_zl updated TS-844:
Attachment: TS-844.patch
Use TS-844.patch and test again, now no related problem coming.
> ReadFromWriter fail in Cach
[
https://issues.apache.org/jira/browse/TS-833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13052302#comment-13052302
]
mohan_zl commented on TS-833:
-
{code}
#0 0x0063f9f5 in get_dns (h=0x18ea3070, id=27816) a
[
https://issues.apache.org/jira/browse/TS-833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13051784#comment-13051784
]
mohan_zl commented on TS-833:
-
By the way, now we found an interesting problem, we use 20 machines
[
https://issues.apache.org/jira/browse/TS-833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13051761#comment-13051761
]
mohan_zl commented on TS-833:
-
@John, when i use your patch TS-833-3.diff in latest trunk, with de
[
https://issues.apache.org/jira/browse/TS-844?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13051760#comment-13051760
]
mohan_zl edited comment on TS-844 at 6/20/11 1:38 AM:
--
The enviroment is
[
https://issues.apache.org/jira/browse/TS-844?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13051760#comment-13051760
]
mohan_zl commented on TS-844:
-
The enviroment is like this:
{quota}
[root@cache180 ~]# uname -a
Li
ReadFromWriter fail in CacheRead.cc
---
Key: TS-844
URL: https://issues.apache.org/jira/browse/TS-844
Project: Traffic Server
Issue Type: Bug
Reporter: mohan_zl
{code}
#6 0x006ab4d7 in
[
https://issues.apache.org/jira/browse/TS-833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13050861#comment-13050861
]
mohan_zl commented on TS-833:
-
@John, is there any possibilities that these problem is caused by s
[
https://issues.apache.org/jira/browse/TS-833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13050836#comment-13050836
]
mohan_zl commented on TS-833:
-
@John yeah, i use TS-833-3.diff with the latest trunk.
> Crash Rep
[
https://issues.apache.org/jira/browse/TS-833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13050173#comment-13050173
]
mohan_zl edited comment on TS-833 at 6/16/11 1:08 AM:
--
{code}
#0 0x
[
https://issues.apache.org/jira/browse/TS-833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13050174#comment-13050174
]
mohan_zl commented on TS-833:
-
@John I think this bug has not been fixed yet.
> Crash Report: Con
[
https://issues.apache.org/jira/browse/TS-833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13050173#comment-13050173
]
mohan_zl commented on TS-833:
-
{quote}
#0 0x004d2c5c in Continuation::handleEvent (this=
[
https://issues.apache.org/jira/browse/TS-833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13049666#comment-13049666
]
mohan_zl commented on TS-833:
-
John, i wanna know where can i get your theory paper?
> Crash Repo
[
https://issues.apache.org/jira/browse/TS-745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13040598#comment-13040598
]
mohan_zl commented on TS-745:
-
I'm considering the multi-fragment problem, i wanna know besides la
[
https://issues.apache.org/jira/browse/TS-745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13038374#comment-13038374
]
mohan_zl commented on TS-745:
-
My boss have give me another passport to visit http://codereview.ap
[
https://issues.apache.org/jira/browse/TS-745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13038371#comment-13038371
]
mohan_zl commented on TS-745:
-
In my thoughts, if we use the same CacheVC to write after calling b
[
https://issues.apache.org/jira/browse/TS-745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
mohan_zl updated TS-745:
Attachment: ssd_cache2.patch
I'm sorry John, maybe we could not use http://codereview.appspot.com/ for
detailed review
[
https://issues.apache.org/jira/browse/TS-745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13035178#comment-13035178
]
mohan_zl commented on TS-745:
-
+1 on a branch. I am busy on preparing ts for online use these days
[
https://issues.apache.org/jira/browse/TS-654?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
mohan_zl updated TS-654:
Attachment: (was: Passive-L7-Health-Check.patch)
> request for support of Layer7 http health checking for Origin Se
[
https://issues.apache.org/jira/browse/TS-654?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
mohan_zl updated TS-654:
Attachment: (was: TS-654-v2.patch)
> request for support of Layer7 http health checking for Origin Servers
> --
[
https://issues.apache.org/jira/browse/TS-654?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
mohan_zl updated TS-654:
Attachment: health_check.patch
Add a new patch to keep up with trunk, right now the autoconfig is not
supported, that
[
https://issues.apache.org/jira/browse/TS-745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
mohan_zl updated TS-745:
Attachment: (was: ssd_support.patch)
> Support ssd
> ---
>
> Key: TS-745
>
[
https://issues.apache.org/jira/browse/TS-745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
mohan_zl updated TS-745:
Attachment: ssd_cache.patch
> Support ssd
> ---
>
> Key: TS-745
> URL: https://
[
https://issues.apache.org/jira/browse/TS-745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
mohan_zl updated TS-745:
Attachment: (was: ssd_support2.patch)
> Support ssd
> ---
>
> Key: TS-745
>
[
https://issues.apache.org/jira/browse/TS-745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
mohan_zl updated TS-745:
Attachment: ssd_support2.patch
Add missing file
> Support ssd
> ---
>
> Key: TS-745
>
[
https://issues.apache.org/jira/browse/TS-745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
mohan_zl updated TS-745:
Attachment: ssd_support.patch
The demand is described in https://cwiki.apache.org/TS/ssdsupport.html, now i
write a si
Support ssd
---
Key: TS-745
URL: https://issues.apache.org/jira/browse/TS-745
Project: Traffic Server
Issue Type: New Feature
Components: Cache
Reporter: mohan_zl
Assignee: mohan_zl
A patch for sup
[
https://issues.apache.org/jira/browse/TS-567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
mohan_zl updated TS-567:
Attachment: clear_memory.patch
in build/aux/ltmain.sh, i wanna know whether or not should we support xfree
like xmallo
[
https://issues.apache.org/jira/browse/TS-654?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13011903#comment-13011903
]
mohan_zl commented on TS-654:
-
Right now i don't want to push the new patch, because in current pa
[
https://issues.apache.org/jira/browse/TS-654?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
mohan_zl updated TS-654:
Attachment: TS-654-v2.patch
Keep up with latest trunk
> request for support of Layer7 http health checking for Origin
[
https://issues.apache.org/jira/browse/TS-685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13003772#comment-13003772
]
mohan_zl commented on TS-685:
-
Why not use cache_partition.config directly, because the structure
[
https://issues.apache.org/jira/browse/TS-676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
mohan_zl updated TS-676:
Attachment: TS676.patch
The attached patch modify some logic in these method.
> Logic wrong in the method of class Sto
Logic wrong in the method of class Store
Key: TS-676
URL: https://issues.apache.org/jira/browse/TS-676
Project: Traffic Server
Issue Type: Bug
Reporter: mohan_zl
The logic of method Stor
[
https://issues.apache.org/jira/browse/TS-489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12992262#comment-12992262
]
mohan_zl commented on TS-489:
-
I'm sorry, i think that is not a bug in the old code, just my fault
[
https://issues.apache.org/jira/browse/TS-489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
mohan_zl updated TS-489:
Attachment: code_clean_up.patch
The logic with connection collapsing break the logic of proxy/http and
iocore/cache, a
[
https://issues.apache.org/jira/browse/TS-654?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
mohan_zl updated TS-654:
Attachment: Passive-L7-Health-Check.patch
Imitating the http state machine, we write a l7 health check module.
Trying o
[
https://issues.apache.org/jira/browse/TS-489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12985104#action_12985104
]
mohan_zl commented on TS-489:
-
Besides, i placed the hashtable which is used for ConnectionCollaps
[
https://issues.apache.org/jira/browse/TS-489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
mohan_zl updated TS-489:
Attachment: TS-489.patch
I think there are two tasks for us to fix this problem:
(1) There seems to be something wrong
[
https://issues.apache.org/jira/browse/TS-608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
mohan_zl updated TS-608:
Attachment: TS-608.patch
change the logic:
1 if we trigger "max server connections", remove one keep-alive connections
[
https://issues.apache.org/jira/browse/TS-489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12980522#action_12980522
]
mohan_zl commented on TS-489:
-
Just leave it to ming_zym, he has time to do it:D
> Seg Fault with
[
https://issues.apache.org/jira/browse/TS-608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12976179#action_12976179
]
mohan_zl commented on TS-608:
-
Now we are writing a l7 health check module, and i agree with your i
[
https://issues.apache.org/jira/browse/TS-541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
mohan_zl updated TS-541:
Attachment: TS-541.patch
> SplitDNS cleanup in project HostDBandDNS
>
>
>
[
https://issues.apache.org/jira/browse/TS-541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
mohan_zl updated TS-541:
Attachment: (was: TS-541SplitDNS-cleanup-in-project-HostDBandDNS.patch)
> SplitDNS cleanup in project HostDBandDNS
[
https://issues.apache.org/jira/browse/TS-541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
mohan_zl updated TS-541:
Attachment: TS-541SplitDNS-cleanup-in-project-HostDBandDNS.patch
> SplitDNS cleanup in project HostDBandDNS
> -
1 - 100 of 104 matches
Mail list logo
