[jira] [Created] (DISPATCH-441) Support password environment variable in qdrouter config
Eric Leu created DISPATCH-441: - Summary: Support password environment variable in qdrouter config Key: DISPATCH-441 URL: https://issues.apache.org/jira/browse/DISPATCH-441 Project: Qpid Dispatch Issue Type: Improvement Components: Routing Engine Affects Versions: 0.6.1 Reporter: Eric Leu Currently, ssl password is set in qdrouter config file. It would be useful to set an environment variable name where password can be picked up. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (DISPATCH-386) Router crashes in qd_link_pn
[ https://issues.apache.org/jira/browse/DISPATCH-386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15336480#comment-15336480 ] Eric Leu commented on DISPATCH-386: --- Problem not reproducible in 0.6.1 branch. > Router crashes in qd_link_pn > > > Key: DISPATCH-386 > URL: https://issues.apache.org/jira/browse/DISPATCH-386 > Project: Qpid Dispatch > Issue Type: Bug > Components: Routing Engine >Affects Versions: 0.6.0 > Environment: Debian 8.3, Apache Qpid Proton 0.13.0-RC for drivers and > dependencies, Hardware: 2 CPUs, 15 GB RAM, 60 GB HDD each on 3 separate > machines >Reporter: Eric Leu > Attachments: core.gz-1, core.gz-2, core.gz-3, trace > > > Network: A network of 3 interior routers built using the latest trunk and > connected to each other using 2-way SSL, same as in DISPATCH-383. > Run 3 pairs of senders and receivers on three different destination > addresses. Each sender has 60 threads. Each receiver has 60 threads. > Seg fault happened with either of of the two traces: > (1) > Program received signal SIGSEGV, Segmentation fault. > 0x77ab4ee0 in qd_link_pn () from > /usr/local/lib/qpid-dispatch/libqpid-dispatch.so > (gdb) bt > #0 0x77ab4ee0 in qd_link_pn () from > /usr/local/lib/qpid-dispatch/libqpid-dispatch.so > #1 0x77ad70cc in ?? () from > /usr/local/lib/qpid-dispatch/libqpid-dispatch.so > #2 0x77acc906 in qdr_connection_process () from > /usr/local/lib/qpid-dispatch/libqpid- > dispatch.so > #3 0x77ab3b28 in ?? () from > /usr/local/lib/qpid-dispatch/libqpid-dispatch.so > #4 0x77adad55 in ?? () from > /usr/local/lib/qpid-dispatch/libqpid-dispatch.so > #5 0x77adb272 in qd_server_run () from > /usr/local/lib/qpid-dispatch/libqpid- > dispatch.so > #6 0x00401a47 in _start () > (2) > Program received signal SIGSEGV, Segmentation fault. > [Switching to Thread 0x70d1f700 (LWP 27862)] > 0x77ab4ee0 in qd_link_pn () from > /usr/local/lib/qpid-dispatch/libqpid-dispatch.so > (gdb) bt > #0 0x77ab4ee0 in qd_link_pn () from > /usr/local/lib/qpid-dispatch/libqpid-dispatch.so > #1 0x77ad71b3 in ?? () from > /usr/local/lib/qpid-dispatch/libqpid-dispatch.so > #2 0x77acc988 in qdr_connection_process () from > /usr/local/lib/qpid-dispatch/libqpid-dispatch.so > #3 0x77ab3b28 in ?? () from > /usr/local/lib/qpid-dispatch/libqpid-dispatch.so > #4 0x77adad55 in ?? () from > /usr/local/lib/qpid-dispatch/libqpid-dispatch.so > #5 0x775d10a4 in start_thread (arg=0x70d1f700) at > pthread_create.c:309 > #6 0x7697587d in clone () at > ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (DISPATCH-386) Router crashes in qd_link_pn
[ https://issues.apache.org/jira/browse/DISPATCH-386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15330966#comment-15330966 ] Eric Leu commented on DISPATCH-386: --- I was using ssl.While running a different test, got another Segmentation fault in qd_link_pn. Trace and core files are attached. Please do $ cat core.gz-1 core.core.gz-2 core.gz-3 > core.gz Then unzip core.gz We have 3 inter-connected routers: R1, R2, R3. Senders and receivers connect to routers as follows: A sender is defined as sender = Messenger(). A receiver is defined as receiver = Messenger() in python. addr === 30 senders -> R1 amqps://...R1/q1 (send to addr) 40 receivers -> R2 amqps://...R2/q1 (subscribe addr) 30 senders -> R2 amqps://...R2/q2 40 receivers -> R3 amqps://...R3/q2 30 senders -> R3amqps://...R3/q3 40 receivers -> R1amqps://...R1/q3 30 senders -> R1 amqps://...R1/q4 40 receivers -> R2 amqps://...R2/q4 30 senders -> R2 amqps://...R2/q5 40 receivers -> R3 amqps://...R3/q5 30 senders -> R3amqps://...R3/q6 40 receivers -> R1amqps://...R1/q6 Each sender sends 100 messages. For each message received, the receivers sends a reply back. > Router crashes in qd_link_pn > > > Key: DISPATCH-386 > URL: https://issues.apache.org/jira/browse/DISPATCH-386 > Project: Qpid Dispatch > Issue Type: Bug > Components: Routing Engine >Affects Versions: 0.6.0 > Environment: Debian 8.3, Apache Qpid Proton 0.13.0-RC for drivers and > dependencies, Hardware: 2 CPUs, 15 GB RAM, 60 GB HDD each on 3 separate > machines >Reporter: Eric Leu > Attachments: core.gz-1, core.gz-2, core.gz-3, trace > > > Network: A network of 3 interior routers built using the latest trunk and > connected to each other using 2-way SSL, same as in DISPATCH-383. > Run 3 pairs of senders and receivers on three different destination > addresses. Each sender has 60 threads. Each receiver has 60 threads. > Seg fault happened with either of of the two traces: > (1) > Program received signal SIGSEGV, Segmentation fault. > 0x77ab4ee0 in qd_link_pn () from > /usr/local/lib/qpid-dispatch/libqpid-dispatch.so > (gdb) bt > #0 0x77ab4ee0 in qd_link_pn () from > /usr/local/lib/qpid-dispatch/libqpid-dispatch.so > #1 0x77ad70cc in ?? () from > /usr/local/lib/qpid-dispatch/libqpid-dispatch.so > #2 0x77acc906 in qdr_connection_process () from > /usr/local/lib/qpid-dispatch/libqpid- > dispatch.so > #3 0x77ab3b28 in ?? () from > /usr/local/lib/qpid-dispatch/libqpid-dispatch.so > #4 0x77adad55 in ?? () from > /usr/local/lib/qpid-dispatch/libqpid-dispatch.so > #5 0x77adb272 in qd_server_run () from > /usr/local/lib/qpid-dispatch/libqpid- > dispatch.so > #6 0x00401a47 in _start () > (2) > Program received signal SIGSEGV, Segmentation fault. > [Switching to Thread 0x70d1f700 (LWP 27862)] > 0x77ab4ee0 in qd_link_pn () from > /usr/local/lib/qpid-dispatch/libqpid-dispatch.so > (gdb) bt > #0 0x77ab4ee0 in qd_link_pn () from > /usr/local/lib/qpid-dispatch/libqpid-dispatch.so > #1 0x77ad71b3 in ?? () from > /usr/local/lib/qpid-dispatch/libqpid-dispatch.so > #2 0x77acc988 in qdr_connection_process () from > /usr/local/lib/qpid-dispatch/libqpid-dispatch.so > #3 0x77ab3b28 in ?? () from > /usr/local/lib/qpid-dispatch/libqpid-dispatch.so > #4 0x77adad55 in ?? () from > /usr/local/lib/qpid-dispatch/libqpid-dispatch.so > #5 0x775d10a4 in start_thread (arg=0x70d1f700) at > pthread_create.c:309 > #6 0x7697587d in clone () at > ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (DISPATCH-386) Router crashes in qd_link_pn
[ https://issues.apache.org/jira/browse/DISPATCH-386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Leu updated DISPATCH-386: -- Attachment: core.gz-3 core.gz-2 core.gz-1 > Router crashes in qd_link_pn > > > Key: DISPATCH-386 > URL: https://issues.apache.org/jira/browse/DISPATCH-386 > Project: Qpid Dispatch > Issue Type: Bug > Components: Routing Engine >Affects Versions: 0.6.0 > Environment: Debian 8.3, Apache Qpid Proton 0.13.0-RC for drivers and > dependencies, Hardware: 2 CPUs, 15 GB RAM, 60 GB HDD each on 3 separate > machines >Reporter: Eric Leu > Attachments: core.gz-1, core.gz-2, core.gz-3, trace > > > Network: A network of 3 interior routers built using the latest trunk and > connected to each other using 2-way SSL, same as in DISPATCH-383. > Run 3 pairs of senders and receivers on three different destination > addresses. Each sender has 60 threads. Each receiver has 60 threads. > Seg fault happened with either of of the two traces: > (1) > Program received signal SIGSEGV, Segmentation fault. > 0x77ab4ee0 in qd_link_pn () from > /usr/local/lib/qpid-dispatch/libqpid-dispatch.so > (gdb) bt > #0 0x77ab4ee0 in qd_link_pn () from > /usr/local/lib/qpid-dispatch/libqpid-dispatch.so > #1 0x77ad70cc in ?? () from > /usr/local/lib/qpid-dispatch/libqpid-dispatch.so > #2 0x77acc906 in qdr_connection_process () from > /usr/local/lib/qpid-dispatch/libqpid- > dispatch.so > #3 0x77ab3b28 in ?? () from > /usr/local/lib/qpid-dispatch/libqpid-dispatch.so > #4 0x77adad55 in ?? () from > /usr/local/lib/qpid-dispatch/libqpid-dispatch.so > #5 0x77adb272 in qd_server_run () from > /usr/local/lib/qpid-dispatch/libqpid- > dispatch.so > #6 0x00401a47 in _start () > (2) > Program received signal SIGSEGV, Segmentation fault. > [Switching to Thread 0x70d1f700 (LWP 27862)] > 0x77ab4ee0 in qd_link_pn () from > /usr/local/lib/qpid-dispatch/libqpid-dispatch.so > (gdb) bt > #0 0x77ab4ee0 in qd_link_pn () from > /usr/local/lib/qpid-dispatch/libqpid-dispatch.so > #1 0x77ad71b3 in ?? () from > /usr/local/lib/qpid-dispatch/libqpid-dispatch.so > #2 0x77acc988 in qdr_connection_process () from > /usr/local/lib/qpid-dispatch/libqpid-dispatch.so > #3 0x77ab3b28 in ?? () from > /usr/local/lib/qpid-dispatch/libqpid-dispatch.so > #4 0x77adad55 in ?? () from > /usr/local/lib/qpid-dispatch/libqpid-dispatch.so > #5 0x775d10a4 in start_thread (arg=0x70d1f700) at > pthread_create.c:309 > #6 0x7697587d in clone () at > ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (DISPATCH-386) Router crashes in qd_link_pn
[ https://issues.apache.org/jira/browse/DISPATCH-386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Leu updated DISPATCH-386: -- Attachment: trace > Router crashes in qd_link_pn > > > Key: DISPATCH-386 > URL: https://issues.apache.org/jira/browse/DISPATCH-386 > Project: Qpid Dispatch > Issue Type: Bug > Components: Routing Engine >Affects Versions: 0.6.0 > Environment: Debian 8.3, Apache Qpid Proton 0.13.0-RC for drivers and > dependencies, Hardware: 2 CPUs, 15 GB RAM, 60 GB HDD each on 3 separate > machines >Reporter: Eric Leu > Attachments: trace > > > Network: A network of 3 interior routers built using the latest trunk and > connected to each other using 2-way SSL, same as in DISPATCH-383. > Run 3 pairs of senders and receivers on three different destination > addresses. Each sender has 60 threads. Each receiver has 60 threads. > Seg fault happened with either of of the two traces: > (1) > Program received signal SIGSEGV, Segmentation fault. > 0x77ab4ee0 in qd_link_pn () from > /usr/local/lib/qpid-dispatch/libqpid-dispatch.so > (gdb) bt > #0 0x77ab4ee0 in qd_link_pn () from > /usr/local/lib/qpid-dispatch/libqpid-dispatch.so > #1 0x77ad70cc in ?? () from > /usr/local/lib/qpid-dispatch/libqpid-dispatch.so > #2 0x77acc906 in qdr_connection_process () from > /usr/local/lib/qpid-dispatch/libqpid- > dispatch.so > #3 0x77ab3b28 in ?? () from > /usr/local/lib/qpid-dispatch/libqpid-dispatch.so > #4 0x77adad55 in ?? () from > /usr/local/lib/qpid-dispatch/libqpid-dispatch.so > #5 0x77adb272 in qd_server_run () from > /usr/local/lib/qpid-dispatch/libqpid- > dispatch.so > #6 0x00401a47 in _start () > (2) > Program received signal SIGSEGV, Segmentation fault. > [Switching to Thread 0x70d1f700 (LWP 27862)] > 0x77ab4ee0 in qd_link_pn () from > /usr/local/lib/qpid-dispatch/libqpid-dispatch.so > (gdb) bt > #0 0x77ab4ee0 in qd_link_pn () from > /usr/local/lib/qpid-dispatch/libqpid-dispatch.so > #1 0x77ad71b3 in ?? () from > /usr/local/lib/qpid-dispatch/libqpid-dispatch.so > #2 0x77acc988 in qdr_connection_process () from > /usr/local/lib/qpid-dispatch/libqpid-dispatch.so > #3 0x77ab3b28 in ?? () from > /usr/local/lib/qpid-dispatch/libqpid-dispatch.so > #4 0x77adad55 in ?? () from > /usr/local/lib/qpid-dispatch/libqpid-dispatch.so > #5 0x775d10a4 in start_thread (arg=0x70d1f700) at > pthread_create.c:309 > #6 0x7697587d in clone () at > ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (DISPATCH-386) Router crashes in qd_link_pn
Eric Leu created DISPATCH-386: - Summary: Router crashes in qd_link_pn Key: DISPATCH-386 URL: https://issues.apache.org/jira/browse/DISPATCH-386 Project: Qpid Dispatch Issue Type: Bug Components: Routing Engine Affects Versions: 0.6.0 Environment: Debian 8.3, Apache Qpid Proton 0.13.0-RC for drivers and dependencies, Hardware: 2 CPUs, 15 GB RAM, 60 GB HDD each on 3 separate machines Reporter: Eric Leu Network: A network of 3 interior routers built using the latest trunk and connected to each other using 2-way SSL, same as in DISPATCH-383. Run 3 pairs of senders and receivers on three different destination addresses. Each sender has 60 threads. Each receiver has 60 threads. Seg fault happened with either of of the two traces: (1) Program received signal SIGSEGV, Segmentation fault. 0x77ab4ee0 in qd_link_pn () from /usr/local/lib/qpid-dispatch/libqpid-dispatch.so (gdb) bt #0 0x77ab4ee0 in qd_link_pn () from /usr/local/lib/qpid-dispatch/libqpid-dispatch.so #1 0x77ad70cc in ?? () from /usr/local/lib/qpid-dispatch/libqpid-dispatch.so #2 0x77acc906 in qdr_connection_process () from /usr/local/lib/qpid-dispatch/libqpid- dispatch.so #3 0x77ab3b28 in ?? () from /usr/local/lib/qpid-dispatch/libqpid-dispatch.so #4 0x77adad55 in ?? () from /usr/local/lib/qpid-dispatch/libqpid-dispatch.so #5 0x77adb272 in qd_server_run () from /usr/local/lib/qpid-dispatch/libqpid- dispatch.so #6 0x00401a47 in _start () (2) Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x70d1f700 (LWP 27862)] 0x77ab4ee0 in qd_link_pn () from /usr/local/lib/qpid-dispatch/libqpid-dispatch.so (gdb) bt #0 0x77ab4ee0 in qd_link_pn () from /usr/local/lib/qpid-dispatch/libqpid-dispatch.so #1 0x77ad71b3 in ?? () from /usr/local/lib/qpid-dispatch/libqpid-dispatch.so #2 0x77acc988 in qdr_connection_process () from /usr/local/lib/qpid-dispatch/libqpid-dispatch.so #3 0x77ab3b28 in ?? () from /usr/local/lib/qpid-dispatch/libqpid-dispatch.so #4 0x77adad55 in ?? () from /usr/local/lib/qpid-dispatch/libqpid-dispatch.so #5 0x775d10a4 in start_thread (arg=0x70d1f700) at pthread_create.c:309 #6 0x7697587d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (DISPATCH-368) Router in bad state in two inter-connected routers
Eric Leu created DISPATCH-368:
-
Summary: Router in bad state in two inter-connected routers
Key: DISPATCH-368
URL: https://issues.apache.org/jira/browse/DISPATCH-368
Project: Qpid Dispatch
Issue Type: Bug
Components: Routing Engine
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: Eric Leu
The setup of two inter-connected routers is the same as in DISPATCH-358. Let
the routers be A and B. Senders connect to A and receivers connect to B. While
senders are sending messages to A, restart router B every 10 sec. Senders
check tracker status to make sure messages are accepted by the receivers.
After running for some time, router A is in bad state. No messages sent are
accepted. After that point, I keep router B up without restarting. The
problem does not go away. Restart senders and receivers and does not help. I
also notice the error in the log:
2016-06-07 14:13:39.287550 -0700 AGENT (debug) Add entity: RouterNodeEntity
(address=amqp:/_topo/0/Router.A.1, cost=None, id=Router.A.1,
instance=1465333922, linkState=[],
nextHop=None, routerLink=None, type=org.apache.qpid.dispatch.router.node,
validOrigins=None)
2016-06-07 14:13:39.294891 -0700 ROUTER (error) Control message error:
opcode=HELLO body=
{'seen': ['Router.A.0'], 'area': '0', 'id': 'Router.A.1', 'instance':
1465333922L}
Traceback (most recent call last):
File
"/usr/local/lib/qpid-dispatch/python/qpid_dispatch_internal/router/engine.py",
line 137,
in handleControlMessage
self.hello_protocol.handle_hello(msg, now, link_id, cost)
File
"/usr/local/lib/qpid-dispatch/python/qpid_dispatch_internal/router/hello.py",
line 55,
in handle_hello
self.node_tracker.neighbor_refresh(msg.id, msg.instance, link_id, cost, now)
File
"/usr/local/lib/qpid-dispatch/python/qpid_dispatch_internal/router/node.py",
line 207,
in neighbor_refresh
if node.set_link_id(link_id):
File
"/usr/local/lib/qpid-dispatch/python/qpid_dispatch_internal/router/node.py",
line 410,
in set_link_id
self.adapter.set_link(self.maskbit, link_id)
OverflowError: signed integer is greater than maximum
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (DISPATCH-208) Closest semantics forwards improperly in multi-router network
[ https://issues.apache.org/jira/browse/DISPATCH-208?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15118339#comment-15118339 ] Eric Leu commented on DISPATCH-208: --- The two routers case you described works fine after the change. Can you test with three routers case? Three Routers: A, B and C add consumer on A for address "closest/A" add consumer on C for address "closest/A" produce a message to "closest/A" on a producer connected to B My result: Message arrives on both A and C consumers. Should only one consumer receive the message? Thanks. > Closest semantics forwards improperly in multi-router network > - > > Key: DISPATCH-208 > URL: https://issues.apache.org/jira/browse/DISPATCH-208 > Project: Qpid Dispatch > Issue Type: Bug > Components: Router Node >Affects Versions: 0.5 >Reporter: Ted Ross >Assignee: Ted Ross > Fix For: 0.6 > > > Addresses that have "closest" bias are broadcast in certain circumstances > when the consumer is on a different router than the producer. > Reproducer: > Two Routers: A and B > - add consumer on A for address "closest/A" > - add consumer on B for address "closest/A" > - produce a message to "closest/A" on a producer connected to B > Expected result: Message arrives on B consumer only > Seen result: Message arrives on both consumers -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
