[
https://issues.apache.org/jira/browse/DISPATCH-337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15556144#comment-15556144
]
Vishal Sharda commented on DISPATCH-337:
----------------------------------------
1. The router is reachable and shows "Accepting incoming connection ..." from
one of the client machines in the logs. It is not clear what causes connection
failure.
2. Yes, there are few TCP connections to the bad router:
vsharda@millennium-qpid-deploy-lnp-1-5129:~$ netstat -at | grep 5670
tcp 0 0 *:5670 *:* LISTEN
tcp 0 0 millennium-qpid-de:5670 userstage114828.c:36758 ESTABLISHED
tcp 0 0 localhost:5670 localhost:33894 ESTABLISHED
tcp 0 0 millennium-qpid-de:5670 userstage118169.c:38132 ESTABLISHED
tcp 0 0 millennium-qpid-de:5670 10.22.99.81:40080 ESTABLISHED
tcp 0 0 millennium-qpid-de:5670 10.22.102.215:50594 ESTABLISHED
tcp6 0 0 localhost:33894 localhost:5670 ESTABLISHED
3. Other routers say that the bad router (Router.A.0) does not exist in the
network:
vsharda@millennium-qpid-deploy-lnp-2-7131:/$ qdstat -nv
Routers in the Network
router-id next-hop link cost neighbors
valid-origins
=============================================================================================
Router.A.1 (self) - ['Router.A.2', 'Router.A.3', 'Router.A.4']
[]
Router.A.2 - 1 1 ['Router.A.1', 'Router.A.3', 'Router.A.4']
[]
Router.A.3 - 2 1 ['Router.A.1', 'Router.A.2', 'Router.A.4']
[]
Router.A.4 - 3 1 ['Router.A.1', 'Router.A.2', 'Router.A.3']
[]
4. On 2016-10-02 13:28:30, it was 620 MB. On 2016-10-07 13:16:00, it is 2.127
GB.
5. Bad router cannot be checked from the good routers:
vsharda@millennium-qpid-deploy-lnp-2-7131:/$ qdstat -b 10.24.170.251 -c
Timeout: Connection amqp://10.24.170.251:amqp/$management timed out: Opening
link 9809b66a-1f2d-4952-92f1-c6c5c8b35680-$management
> Huge memory leaks in Qpid Dispatch router
> -----------------------------------------
>
> Key: DISPATCH-337
> URL: https://issues.apache.org/jira/browse/DISPATCH-337
> Project: Qpid Dispatch
> Issue Type: Bug
> Affects Versions: 0.6.0
> Environment: Debian 8.3, Apache Qpid Proton 0.12.2 for drivers and
> dependencies, Hardware: 2 CPUs, 15 GB RAM, 60 GB HDD on 2 separate machines
> Reporter: Vishal Sharda
> Priority: Critical
> Attachments: LNP-1_Huge_memory.png, LNP-1_Leak_starts.png,
> LNP-1_not_accepting_connections.png, Memory_usage_first_run_no_SSL.png,
> Memory_usage_subsequent_run_no_SSL.png, Rapid_perm_memory_increase.png,
> Subsequent_memory_increase.png, Tim-Router-3-huge-memory-usage.png,
> Tim_Router_3.png, Tim_Routers_3_and_6_further_leaks.png, config1.conf,
> config2.conf, val2_receiver.txt, val2_sender.txt
>
>
> Valgrind shows huge memory leaks while running 2 interconnected routers with
> 2 parallel senders connected to the one router and 2 parallel receivers
> connected to the other router.
> The CRYPTO leak that is coming from Qpid Proton 0.12.2 is already fixed here:
> https://issues.apache.org/jira/browse/PROTON-1115
> However, the rest of the leaks are from qdrouterd.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
