[jira] [Resolved] (PROTON-2518) Installing Python bindings via pip in a venv causes an ImportError
[
https://issues.apache.org/jira/browse/PROTON-2518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Stitcher resolved PROTON-2518.
-
Resolution: Cannot Reproduce
> Installing Python bindings via pip in a venv causes an ImportError
> --
>
> Key: PROTON-2518
> URL: https://issues.apache.org/jira/browse/PROTON-2518
> Project: Qpid Proton
> Issue Type: Bug
> Components: python-binding
>Affects Versions: proton-c-0.36.0
> Environment: CentOS 7
> Python 3.8.12 (Anaconda 4.11.0)
> Using a standard venv within that. That is I created a python virtual
> environment inside an anaconda environment. (Not my choice but if it makes a
> difference I've run into the same issue without it)
>Reporter: Paul Banks
>Priority: Major
> Attachments: image-2022-03-17-11-01-58-867.png,
> image-2022-03-17-11-14-04-350.png
>
>
> When attempting to use the Qpid Proton libraries by installing the
> `python-qpid-proton` package in pip an ImportError appears related to the
> _cproton shared object.
> I was able to recreate it with a python 3.6.8 virtual environment. The error
> is the same in my python 3.8.12 environment. I am attempting to run one of
> the provided examples.
> {code:java}
> Traceback (most recent call last):
> File
> "/export/home/pbanks/Downloads/qpid-proton-0.36.0/python/examples/simple_recv.py",
> line 22, in
> from proton.handlers import MessagingHandler
> File
> "/export/home/pbanks/anaconda3/envs/testEnviron/lib/python3.6/site-packages/proton/__init__.py",
> line 35, in
> from cproton import PN_VERSION_MAJOR, PN_VERSION_MINOR, PN_VERSION_POINT
> File
> "/export/home/pbanks/anaconda3/envs/testEnviron/lib/python3.6/site-packages/cproton.py",
> line 15, in
> import _cproton
> ImportError:
> /export/home/pbanks/anaconda3/envs/testEnviron/lib/python3.6/site-packages/_cproton.cpython-36m-x86_64-linux-gnu.so:
> undefined symbol: CRYPTO_set_locking_callback{code}
> Normally in CentOS7 I would use the Fedora provided yum package
> `python36-qpid-proton` as that works without issue.
> My current workaround is to replace the shared object provided by the pip
> package with the yum package.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (DISPATCH-2326) Remove HTTP1/HTTP2/TCP Adaptors from the source code.
[ https://issues.apache.org/jira/browse/DISPATCH-2326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17508314#comment-17508314 ] ASF subversion and git services commented on DISPATCH-2326: --- Commit ec62cb2e6f1cd1cdf367103a8ad7dc9e21b21cff in qpid-dispatch's branch refs/heads/dependabot/npm_and_yarn/console/react/react-scripts-5.0.0 from Ganesh Murthy [ https://gitbox.apache.org/repos/asf?p=qpid-dispatch.git;h=ec62cb2 ] DISPATCH-2326: Additional fix. Remove the nghttp2 library from CMakeLists.txt and other files > Remove HTTP1/HTTP2/TCP Adaptors from the source code. > -- > > Key: DISPATCH-2326 > URL: https://issues.apache.org/jira/browse/DISPATCH-2326 > Project: Qpid Dispatch > Issue Type: Task >Reporter: Ganesh Murthy >Assignee: Ganesh Murthy >Priority: Major > Fix For: 1.19.0 > > > Remove all adaptor code and all supporting adaptor tests. Do not remove the > adaptor code API. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (DISPATCH-2336) Dockerfile-ubuntu not building
[
https://issues.apache.org/jira/browse/DISPATCH-2336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17508318#comment-17508318
]
ASF subversion and git services commented on DISPATCH-2336:
---
Commit 2fe2fe7feb1655bc446c05b8ef5d741068089770 in qpid-dispatch's branch
refs/heads/dependabot/npm_and_yarn/console/react/react-scripts-5.0.0 from Jiri
Daněk
[ https://gitbox.apache.org/repos/asf?p=qpid-dispatch.git;h=2fe2fe7 ]
DISPATCH-2336: Fix Dockerfiles in the dockerfile folder (#1536)
> Dockerfile-ubuntu not building
> --
>
> Key: DISPATCH-2336
> URL: https://issues.apache.org/jira/browse/DISPATCH-2336
> Project: Qpid Dispatch
> Issue Type: Bug
>Affects Versions: 1.18.0
>Reporter: Birgen Geelen
>Assignee: Jiri Daněk
>Priority: Minor
> Fix For: 1.20.0
>
>
> 2 issues while building the docker image using command:
> sudo docker build -t docker-image-name --file=Dockerfile-ubuntu
> * 1st Error raised is:
> {code:java}
> STEP 5/13: RUN pip3 install quart selectors grpcio protobuf h2
> /bin/sh: 1: pip3: not found
> Error: error building at STEP "RUN pip3 install quart selectors grpcio
> protobuf h2": error while running runtime: exit status 127 {code}
> Can be fixed by adding python3-pip to the list of packages to be installed
> Dockerfile-ubuntu.
>
>
> * 2nd error: incorrect change directory statement
> Diff for fix:
> diff Dockerfile-ubuntu Dockerfile-ubuntu.old
> 29c29
> < apt-get install -y curl gcc g++ automake libwebsockets-dev libtool
> zlib1g-dev cmake libsasl2-dev libssl-dev libnghttp2-dev python3-dev
> *_+python3-pip+_* libuv1-dev sasl2-bin swig maven git && \
> —
> > apt-get install -y curl gcc g++ automake libwebsockets-dev libtool
> > zlib1g-dev cmake libsasl2-dev libssl-dev libnghttp2-dev python3-dev
> > libuv1-dev sasl2-bin swig maven git && \
> 34c34
> < RUN git clone [https://gitbox.apache.org/repos/asf/qpid-dispatch.git] && cd
> *_+qpid-dispatch+_* && git submodule add
> [https://gitbox.apache.org/repos/asf/qpid-proton.git] && git submodule update
> --init
> —
> > RUN git clone [https://gitbox.apache.org/repos/asf/qpid-dispatch.git] && cd
> > *{color:#FF}/qpid-dispatch{color}* && git submodule add
> > [https://gitbox.apache.org/repos/asf/qpid-proton.git] && git submodule
> > update --init
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (DISPATCH-2234) Update JavaScript console packages for the 1.19.0 release
[ https://issues.apache.org/jira/browse/DISPATCH-2234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17508317#comment-17508317 ] ASF subversion and git services commented on DISPATCH-2234: --- Commit f0c7e9323b80741c53d6a8c7c230349e4fc49e89 in qpid-dispatch's branch refs/heads/dependabot/npm_and_yarn/console/react/react-scripts-5.0.0 from Jiri Daněk [ https://gitbox.apache.org/repos/asf?p=qpid-dispatch.git;h=f0c7e93 ] DISPATCH-2234: Update JavaScript console packages for the 1.19.0 release (round 2) (#1537) > Update JavaScript console packages for the 1.19.0 release > - > > Key: DISPATCH-2234 > URL: https://issues.apache.org/jira/browse/DISPATCH-2234 > Project: Qpid Dispatch > Issue Type: Task > Components: Console >Reporter: Jiri Daněk >Assignee: Jiri Daněk >Priority: Major > Fix For: 1.19.0 > > -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (DISPATCH-2276) The latest release of proton (pre-0.37.0) breaks scraper
[ https://issues.apache.org/jira/browse/DISPATCH-2276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17508315#comment-17508315 ] ASF subversion and git services commented on DISPATCH-2276: --- Commit 6f75d1f3dc1600204289e54ed395a22e5e486f26 in qpid-dispatch's branch refs/heads/dependabot/npm_and_yarn/console/react/react-scripts-5.0.0 from Chuck Rolke [ https://gitbox.apache.org/repos/asf?p=qpid-dispatch.git;h=6f75d1f ] DISPATCH-2276: Accomodate hex values in 0.36+ qpid-proton logging (#1525) * DISPATCH-2276: Accomodate hex values in 0.36+ qpid-proton logging * Fix code that extracts integer values during AMQP analysis * Convert ints from hex to decimal for web display of values line link and session numbers and credit. * DISPATCH-2276: Topology disposition test does not need to import proton Co-authored-by: chug Co-authored-by: Chuck Rolke > The latest release of proton (pre-0.37.0) breaks scraper > > > Key: DISPATCH-2276 > URL: https://issues.apache.org/jira/browse/DISPATCH-2276 > Project: Qpid Dispatch > Issue Type: Bug >Reporter: Ken Giusti >Assignee: Charles E. Rolke >Priority: Major > > The next version of proton changes the format of the message tracing log > messages. > Scraper needs to be updated to work with these new log formats. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (DISPATCH-2333) Fix assert that is always true (detected by Coverity Scan)
[ https://issues.apache.org/jira/browse/DISPATCH-2333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17508313#comment-17508313 ] ASF subversion and git services commented on DISPATCH-2333: --- Commit b58ce50bee634e4dd2155d19ae68ad5184eea0ed in qpid-dispatch's branch refs/heads/dependabot/npm_and_yarn/console/react/react-scripts-5.0.0 from Ken Giusti [ https://gitbox.apache.org/repos/asf?p=qpid-dispatch.git;h=b58ce50 ] DISPATCH-2333: fix incorrect assertion check This closes #1528 > Fix assert that is always true (detected by Coverity Scan) > -- > > Key: DISPATCH-2333 > URL: https://issues.apache.org/jira/browse/DISPATCH-2333 > Project: Qpid Dispatch > Issue Type: Bug > Components: Policy Engine >Affects Versions: 1.18.0 >Reporter: Ken Giusti >Assignee: Ken Giusti >Priority: Trivial > Fix For: 1.19.0 > > > In policy.c: > 292uint64_t nc = n_connections; > 293assert (n_connections >= 0); > > n_connections >= 0 is always true regardless of the values of its operands. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (DISPATCH-2144) Fatal Python error: _PyMem_DebugMalloc: Python memory allocator called without holding the GIL
[
https://issues.apache.org/jira/browse/DISPATCH-2144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17508316#comment-17508316
]
ASF subversion and git services commented on DISPATCH-2144:
---
Commit c3b4ea2d464a42906c624abe11498651f591053a in qpid-dispatch's branch
refs/heads/dependabot/npm_and_yarn/console/react/react-scripts-5.0.0 from Jiri
Daněk
[ https://gitbox.apache.org/repos/asf?p=qpid-dispatch.git;h=c3b4ea2 ]
DISPATCH-2144 Remove Python lock on the router's side; use the lock Python
itself created (#1521)
> Fatal Python error: _PyMem_DebugMalloc: Python memory allocator called
> without holding the GIL
> --
>
> Key: DISPATCH-2144
> URL: https://issues.apache.org/jira/browse/DISPATCH-2144
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Policy Engine
>Affects Versions: 1.16.0
>Reporter: Jiri Daněk
>Assignee: Jiri Daněk
>Priority: Major
> Fix For: 1.19.0
>
>
> To reproduce, install python3-debug on Fedora, then use it to build and run
> Dispatch
> https://github.com/jiridanek/qpid-dispatch/runs/2629007367?check_suite_focus=true#step:25:7044
> {noformat}
> 25: Router QDR.Policy output file:
> 25:
> 25:
> /home/runner/work/qpid-dispatch/qpid-dispatch/qpid-dispatch/python/qpid_dispatch_internal/policy/policy_util.py:65:
> ResourceWarning: unclosed family=AddressFamily.AF_INET6, type=SocketKind.SOCK_STREAM, proto=0,
> laddr=('::', 0, 0, 0)>
> 25: if is_ipv6_enabled():
> 25: ResourceWarning: Enable tracemalloc to get the object allocation traceback
> 25: Fatal Python error: _PyMem_DebugMalloc: Python memory allocator called
> without holding the GIL
> 25: Python runtime state: initialized
> 25:
> 25: Thread 0x7f0e8fffcec0 (most recent call first):
> 25:
> {noformat}
> Unrelated error in the same log that I noticed at random
> {noformat}
> 23: E /builddir/build/BUILD/Python-3.9.5/Modules/gcmodule.c:114:
> gc_decref: Assertion "gc_get_refs(g) > 0" failed: refcount is too small
> 23: E Enable tracemalloc to get the memory block allocation
> traceback
> 23: E
> 23: E object address : 0x7fd3e1b90cd0
> 23: E object refcount : 117
> 23: E object type : 0x7b695c30
> 23: E object type name: Agent
> 23: E object repr :
>
> 23: E
> 23: E Fatal Python error: _PyObject_AssertFailed:
> _PyObject_AssertFailed
> 23: E Python runtime state: initialized
> 23: E
> 23: E Current thread 0x7fd3e39e3ec0 (most recent call first):
> 23: E
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (DISPATCH-1487) Improve the parsing of message annotations
[ https://issues.apache.org/jira/browse/DISPATCH-1487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17508312#comment-17508312 ] ASF subversion and git services commented on DISPATCH-1487: --- Commit 32ddaa1a9bd38f867aebe4bebbf4c9bf6177c106 in qpid-dispatch's branch refs/heads/dependabot/npm_and_yarn/console/react/react-scripts-5.0.0 from Ken Giusti [ https://gitbox.apache.org/repos/asf?p=qpid-dispatch.git;h=32ddaa1 ] DISPATCH-1487: Message annotations re-write This patch completely refactors how message annotations are processed by the router. The primary changes done in this re-design are: - Removal of the old parse_turbo functionality. - Avoid all annotation process for link-routed messages - Avoid composing all outgoing annotations on the receive path. This is now done during qd_message_send(). - Avoid composing the trace list and ingress manually in various parts of the code. This is now done once at qd_message_send(). - Optimize parsing of incoming annotations using the buffer_field API. - Consolidate message compose functions into a message constructor. - Optimize the composing of outgoing annotations by: - pre-encoding all static key values and router id - in-line more of the encoding code > Improve the parsing of message annotations > -- > > Key: DISPATCH-1487 > URL: https://issues.apache.org/jira/browse/DISPATCH-1487 > Project: Qpid Dispatch > Issue Type: Improvement > Components: Router Node >Affects Versions: 1.9.0 >Reporter: Ken Giusti >Assignee: Ken Giusti >Priority: Major > Fix For: 1.19.0 > > > ToDo: Refactor inbound MA parsing on inbound inter-router links to improve > throughput and reduce latency. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-2518) Installing Python bindings via pip in a venv causes an ImportError
[
https://issues.apache.org/jira/browse/PROTON-2518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17508303#comment-17508303
]
Paul Banks commented on PROTON-2518:
The second environment is just a straight up anaconda environment. I did not
install openSSL in there though. I think you're probably right though because
installing it fresh on an anaconda install on a new server instance works. So
I'm not sure exactly what's going on in my environment. You can probably close
the bug.
> Installing Python bindings via pip in a venv causes an ImportError
> --
>
> Key: PROTON-2518
> URL: https://issues.apache.org/jira/browse/PROTON-2518
> Project: Qpid Proton
> Issue Type: Bug
> Components: python-binding
>Affects Versions: proton-c-0.36.0
> Environment: CentOS 7
> Python 3.8.12 (Anaconda 4.11.0)
> Using a standard venv within that. That is I created a python virtual
> environment inside an anaconda environment. (Not my choice but if it makes a
> difference I've run into the same issue without it)
>Reporter: Paul Banks
>Priority: Major
> Attachments: image-2022-03-17-11-01-58-867.png,
> image-2022-03-17-11-14-04-350.png
>
>
> When attempting to use the Qpid Proton libraries by installing the
> `python-qpid-proton` package in pip an ImportError appears related to the
> _cproton shared object.
> I was able to recreate it with a python 3.6.8 virtual environment. The error
> is the same in my python 3.8.12 environment. I am attempting to run one of
> the provided examples.
> {code:java}
> Traceback (most recent call last):
> File
> "/export/home/pbanks/Downloads/qpid-proton-0.36.0/python/examples/simple_recv.py",
> line 22, in
> from proton.handlers import MessagingHandler
> File
> "/export/home/pbanks/anaconda3/envs/testEnviron/lib/python3.6/site-packages/proton/__init__.py",
> line 35, in
> from cproton import PN_VERSION_MAJOR, PN_VERSION_MINOR, PN_VERSION_POINT
> File
> "/export/home/pbanks/anaconda3/envs/testEnviron/lib/python3.6/site-packages/cproton.py",
> line 15, in
> import _cproton
> ImportError:
> /export/home/pbanks/anaconda3/envs/testEnviron/lib/python3.6/site-packages/_cproton.cpython-36m-x86_64-linux-gnu.so:
> undefined symbol: CRYPTO_set_locking_callback{code}
> Normally in CentOS7 I would use the Fedora provided yum package
> `python36-qpid-proton` as that works without issue.
> My current workaround is to replace the shared object provided by the pip
> package with the yum package.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-2518) Installing Python bindings via pip in a venv causes an ImportError
[
https://issues.apache.org/jira/browse/PROTON-2518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17508274#comment-17508274
]
Andrew Stitcher commented on PROTON-2518:
-
I think the issue when using anaconda is that you build it in an anaconda
environment which sets up the anaconda internal 1.1 ssl libraries to be found
during the pip install. But you don't run it in the anaconda environment so the
anaconda ssl libraries are no longer found. I'm not sure there is anything we
can do about this.
> Installing Python bindings via pip in a venv causes an ImportError
> --
>
> Key: PROTON-2518
> URL: https://issues.apache.org/jira/browse/PROTON-2518
> Project: Qpid Proton
> Issue Type: Bug
> Components: python-binding
>Affects Versions: proton-c-0.36.0
> Environment: CentOS 7
> Python 3.8.12 (Anaconda 4.11.0)
> Using a standard venv within that. That is I created a python virtual
> environment inside an anaconda environment. (Not my choice but if it makes a
> difference I've run into the same issue without it)
>Reporter: Paul Banks
>Priority: Major
> Attachments: image-2022-03-17-11-01-58-867.png,
> image-2022-03-17-11-14-04-350.png
>
>
> When attempting to use the Qpid Proton libraries by installing the
> `python-qpid-proton` package in pip an ImportError appears related to the
> _cproton shared object.
> I was able to recreate it with a python 3.6.8 virtual environment. The error
> is the same in my python 3.8.12 environment. I am attempting to run one of
> the provided examples.
> {code:java}
> Traceback (most recent call last):
> File
> "/export/home/pbanks/Downloads/qpid-proton-0.36.0/python/examples/simple_recv.py",
> line 22, in
> from proton.handlers import MessagingHandler
> File
> "/export/home/pbanks/anaconda3/envs/testEnviron/lib/python3.6/site-packages/proton/__init__.py",
> line 35, in
> from cproton import PN_VERSION_MAJOR, PN_VERSION_MINOR, PN_VERSION_POINT
> File
> "/export/home/pbanks/anaconda3/envs/testEnviron/lib/python3.6/site-packages/cproton.py",
> line 15, in
> import _cproton
> ImportError:
> /export/home/pbanks/anaconda3/envs/testEnviron/lib/python3.6/site-packages/_cproton.cpython-36m-x86_64-linux-gnu.so:
> undefined symbol: CRYPTO_set_locking_callback{code}
> Normally in CentOS7 I would use the Fedora provided yum package
> `python36-qpid-proton` as that works without issue.
> My current workaround is to replace the shared object provided by the pip
> package with the yum package.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (PROTON-2518) Installing Python bindings via pip in a venv causes an ImportError
[
https://issues.apache.org/jira/browse/PROTON-2518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paul Banks updated PROTON-2518:
---
Attachment: image-2022-03-17-11-14-04-350.png
> Installing Python bindings via pip in a venv causes an ImportError
> --
>
> Key: PROTON-2518
> URL: https://issues.apache.org/jira/browse/PROTON-2518
> Project: Qpid Proton
> Issue Type: Bug
> Components: python-binding
>Affects Versions: proton-c-0.36.0
> Environment: CentOS 7
> Python 3.8.12 (Anaconda 4.11.0)
> Using a standard venv within that. That is I created a python virtual
> environment inside an anaconda environment. (Not my choice but if it makes a
> difference I've run into the same issue without it)
>Reporter: Paul Banks
>Priority: Major
> Attachments: image-2022-03-17-11-01-58-867.png,
> image-2022-03-17-11-14-04-350.png
>
>
> When attempting to use the Qpid Proton libraries by installing the
> `python-qpid-proton` package in pip an ImportError appears related to the
> _cproton shared object.
> I was able to recreate it with a python 3.6.8 virtual environment. The error
> is the same in my python 3.8.12 environment. I am attempting to run one of
> the provided examples.
> {code:java}
> Traceback (most recent call last):
> File
> "/export/home/pbanks/Downloads/qpid-proton-0.36.0/python/examples/simple_recv.py",
> line 22, in
> from proton.handlers import MessagingHandler
> File
> "/export/home/pbanks/anaconda3/envs/testEnviron/lib/python3.6/site-packages/proton/__init__.py",
> line 35, in
> from cproton import PN_VERSION_MAJOR, PN_VERSION_MINOR, PN_VERSION_POINT
> File
> "/export/home/pbanks/anaconda3/envs/testEnviron/lib/python3.6/site-packages/cproton.py",
> line 15, in
> import _cproton
> ImportError:
> /export/home/pbanks/anaconda3/envs/testEnviron/lib/python3.6/site-packages/_cproton.cpython-36m-x86_64-linux-gnu.so:
> undefined symbol: CRYPTO_set_locking_callback{code}
> Normally in CentOS7 I would use the Fedora provided yum package
> `python36-qpid-proton` as that works without issue.
> My current workaround is to replace the shared object provided by the pip
> package with the yum package.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-2518) Installing Python bindings via pip in a venv causes an ImportError
[
https://issues.apache.org/jira/browse/PROTON-2518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17508273#comment-17508273
]
Paul Banks commented on PROTON-2518:
My terminal set up right now isn't allowing copy paste so I took screenshots.
Apologies lol. But it seems the issue is targeting the wrong SSL lib.
The first so is the original when I installed it in my virtual environment
within my anaconda environment. The second is the one that works; the replaced
so from my CentOS7 package. Clearly targeting different libraries.
!image-2022-03-17-11-01-58-867.png!
This is a clean install in an anaconda environment. Could just be an issue with
using pip in anaconda though
!image-2022-03-17-11-14-04-350.png!
> Installing Python bindings via pip in a venv causes an ImportError
> --
>
> Key: PROTON-2518
> URL: https://issues.apache.org/jira/browse/PROTON-2518
> Project: Qpid Proton
> Issue Type: Bug
> Components: python-binding
>Affects Versions: proton-c-0.36.0
> Environment: CentOS 7
> Python 3.8.12 (Anaconda 4.11.0)
> Using a standard venv within that. That is I created a python virtual
> environment inside an anaconda environment. (Not my choice but if it makes a
> difference I've run into the same issue without it)
>Reporter: Paul Banks
>Priority: Major
> Attachments: image-2022-03-17-11-01-58-867.png,
> image-2022-03-17-11-14-04-350.png
>
>
> When attempting to use the Qpid Proton libraries by installing the
> `python-qpid-proton` package in pip an ImportError appears related to the
> _cproton shared object.
> I was able to recreate it with a python 3.6.8 virtual environment. The error
> is the same in my python 3.8.12 environment. I am attempting to run one of
> the provided examples.
> {code:java}
> Traceback (most recent call last):
> File
> "/export/home/pbanks/Downloads/qpid-proton-0.36.0/python/examples/simple_recv.py",
> line 22, in
> from proton.handlers import MessagingHandler
> File
> "/export/home/pbanks/anaconda3/envs/testEnviron/lib/python3.6/site-packages/proton/__init__.py",
> line 35, in
> from cproton import PN_VERSION_MAJOR, PN_VERSION_MINOR, PN_VERSION_POINT
> File
> "/export/home/pbanks/anaconda3/envs/testEnviron/lib/python3.6/site-packages/cproton.py",
> line 15, in
> import _cproton
> ImportError:
> /export/home/pbanks/anaconda3/envs/testEnviron/lib/python3.6/site-packages/_cproton.cpython-36m-x86_64-linux-gnu.so:
> undefined symbol: CRYPTO_set_locking_callback{code}
> Normally in CentOS7 I would use the Fedora provided yum package
> `python36-qpid-proton` as that works without issue.
> My current workaround is to replace the shared object provided by the pip
> package with the yum package.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (PROTON-2518) Installing Python bindings via pip in a venv causes an ImportError
[
https://issues.apache.org/jira/browse/PROTON-2518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paul Banks updated PROTON-2518:
---
Attachment: image-2022-03-17-11-01-58-867.png
> Installing Python bindings via pip in a venv causes an ImportError
> --
>
> Key: PROTON-2518
> URL: https://issues.apache.org/jira/browse/PROTON-2518
> Project: Qpid Proton
> Issue Type: Bug
> Components: python-binding
>Affects Versions: proton-c-0.36.0
> Environment: CentOS 7
> Python 3.8.12 (Anaconda 4.11.0)
> Using a standard venv within that. That is I created a python virtual
> environment inside an anaconda environment. (Not my choice but if it makes a
> difference I've run into the same issue without it)
>Reporter: Paul Banks
>Priority: Major
> Attachments: image-2022-03-17-11-01-58-867.png
>
>
> When attempting to use the Qpid Proton libraries by installing the
> `python-qpid-proton` package in pip an ImportError appears related to the
> _cproton shared object.
> I was able to recreate it with a python 3.6.8 virtual environment. The error
> is the same in my python 3.8.12 environment. I am attempting to run one of
> the provided examples.
> {code:java}
> Traceback (most recent call last):
> File
> "/export/home/pbanks/Downloads/qpid-proton-0.36.0/python/examples/simple_recv.py",
> line 22, in
> from proton.handlers import MessagingHandler
> File
> "/export/home/pbanks/anaconda3/envs/testEnviron/lib/python3.6/site-packages/proton/__init__.py",
> line 35, in
> from cproton import PN_VERSION_MAJOR, PN_VERSION_MINOR, PN_VERSION_POINT
> File
> "/export/home/pbanks/anaconda3/envs/testEnviron/lib/python3.6/site-packages/cproton.py",
> line 15, in
> import _cproton
> ImportError:
> /export/home/pbanks/anaconda3/envs/testEnviron/lib/python3.6/site-packages/_cproton.cpython-36m-x86_64-linux-gnu.so:
> undefined symbol: CRYPTO_set_locking_callback{code}
> Normally in CentOS7 I would use the Fedora provided yum package
> `python36-qpid-proton` as that works without issue.
> My current workaround is to replace the shared object provided by the pip
> package with the yum package.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Assigned] (PROTON-2121) python-qpid-proton 0.28 BlockingConnection leaks connections (does not close file descriptors)
[
https://issues.apache.org/jira/browse/PROTON-2121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Ross reassigned PROTON-2121:
---
Assignee: Clifford Jansen
> python-qpid-proton 0.28 BlockingConnection leaks connections (does not close
> file descriptors)
> --
>
> Key: PROTON-2121
> URL: https://issues.apache.org/jira/browse/PROTON-2121
> Project: Qpid Proton
> Issue Type: Bug
> Components: python-binding
>Affects Versions: proton-c-0.28.0, proton-c-0.30.0
>Reporter: Lukas
>Assignee: Clifford Jansen
>Priority: Major
> Labels: leak
>
> Starting in proton 0.28.0 and verified in 0.29.0b1 (pre-release) I can
> confirm following issue:
>
> {code:java}
> from proton.utils import BlockingConnection
> c = BlockingConnection(YOUR_ADDRESS)
> c.close()
> # ^^ FINE, all file descriptors closed properly
> from proton.utils import BlockingConnection
> c = BlockingConnection(YOUR_ADDRESS)
> s = c.create_sender(YOUR_EXCHANGE)
> s.close()
> c.close()
> # ^^ leaks the socket file descriptor - connection not closed properly (ls
> /proc/YOUR_PID/fd to verify){code}
>
> Version 0.27.0 is *not* affected by this issue.
>
> Having a quick look at the proton bindings, this very well might be bug in
> the qpid proton library itself, not the python bindings!
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Reopened] (PROTON-2176) CLOSE_WAIT after BlockingSender close
[ https://issues.apache.org/jira/browse/PROTON-2176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross reopened PROTON-2176: - Assignee: Clifford Jansen > CLOSE_WAIT after BlockingSender close > - > > Key: PROTON-2176 > URL: https://issues.apache.org/jira/browse/PROTON-2176 > Project: Qpid Proton > Issue Type: Bug > Components: python-binding > Environment: Linux >Reporter: Stefan Rijnhart >Assignee: Clifford Jansen >Priority: Major > Attachments: 20200130-proton_close_wait.log > > > from proton.utils import BlockingConnection > connection = BlockingConnection(url) > sender = connection.create_sender(queue_name) > sender.send(message) > sender.close() > connection.close() > Leaves a CLOSE_WAIT lingering indefinitely every time, leading to ValueError: > filedescriptor out of range in select() when ulimit is reached. > python_qpid_proton-0.30.0-py2.7-linux-x86_64 talking to ActiveMQ 5.14.5. > Problem also occurs in 0.29.0, 0.28.0 but not in 0.27.0. > Debug log attached. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Closed] (DISPATCH-1994) [http2] Use PN_RAW_CONNECTION_DRAIN_BUFFERS in http2 adaptor
[ https://issues.apache.org/jira/browse/DISPATCH-1994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell closed DISPATCH-1994. > [http2] Use PN_RAW_CONNECTION_DRAIN_BUFFERS in http2 adaptor > > > Key: DISPATCH-1994 > URL: https://issues.apache.org/jira/browse/DISPATCH-1994 > Project: Qpid Dispatch > Issue Type: Improvement > Components: Protocol Adaptors >Reporter: Ganesh Murthy >Assignee: Ganesh Murthy >Priority: Minor > -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (DISPATCH-1994) [http2] Use PN_RAW_CONNECTION_DRAIN_BUFFERS in http2 adaptor
[ https://issues.apache.org/jira/browse/DISPATCH-1994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated DISPATCH-1994: - Fix Version/s: (was: 1.20.0) > [http2] Use PN_RAW_CONNECTION_DRAIN_BUFFERS in http2 adaptor > > > Key: DISPATCH-1994 > URL: https://issues.apache.org/jira/browse/DISPATCH-1994 > Project: Qpid Dispatch > Issue Type: Improvement > Components: Protocol Adaptors >Reporter: Ganesh Murthy >Assignee: Ganesh Murthy >Priority: Minor > -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (DISPATCH-1967) TCP adaptor connections not counted against policy global count
[ https://issues.apache.org/jira/browse/DISPATCH-1967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated DISPATCH-1967: - Fix Version/s: (was: 1.20.0) > TCP adaptor connections not counted against policy global count > --- > > Key: DISPATCH-1967 > URL: https://issues.apache.org/jira/browse/DISPATCH-1967 > Project: Qpid Dispatch > Issue Type: Bug > Components: Policy Engine, Protocol Adaptors >Affects Versions: 1.15.0 >Reporter: Charles E. Rolke >Assignee: Charles E. Rolke >Priority: Major > > After many thousand TCP connections the router Policy Status shows > _Connections Processed = 1_. That connection is the management connection > that read the count. > Adaptor connections must be counted by policy and subjected to global count > limits. > This same problem probably exists in the other protocol adaptors. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (DISPATCH-1993) [http1] Use PN_RAW_CONNECTION_DRAIN_BUFFERS in http1 adaptor
[ https://issues.apache.org/jira/browse/DISPATCH-1993?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated DISPATCH-1993: - Fix Version/s: (was: 1.20.0) > [http1] Use PN_RAW_CONNECTION_DRAIN_BUFFERS in http1 adaptor > > > Key: DISPATCH-1993 > URL: https://issues.apache.org/jira/browse/DISPATCH-1993 > Project: Qpid Dispatch > Issue Type: Improvement > Components: Protocol Adaptors >Reporter: Ganesh Murthy >Assignee: Ken Giusti >Priority: Minor > Labels: HTTP/1.x > -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (DISPATCH-2288) Network-centric logging facility for protocol adaptors
[ https://issues.apache.org/jira/browse/DISPATCH-2288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated DISPATCH-2288: - Fix Version/s: (was: 1.20.0) > Network-centric logging facility for protocol adaptors > -- > > Key: DISPATCH-2288 > URL: https://issues.apache.org/jira/browse/DISPATCH-2288 > Project: Qpid Dispatch > Issue Type: New Feature > Components: Protocol Adaptors >Reporter: Ted Ross >Assignee: Ted Ross >Priority: Major > > A separate logging/tracing facility is needed for the protocol adaptors to > serve users that are more accustomed to network/firewall/router logs and are > not concerned with AMQP/messaging/link-protocol details. > This feature will make the use of the protocol adaptors more observable and > debuggable to network-familiar developers and operators. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (DISPATCH-2066) [http1] In system_tests_http1_adaptor Http1AdaptorQ2Standalone backpressure tests, block_ct != unblock_ct
[
https://issues.apache.org/jira/browse/DISPATCH-2066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robbie Gemmell updated DISPATCH-2066:
-
Fix Version/s: (was: 1.20.0)
> [http1] In system_tests_http1_adaptor Http1AdaptorQ2Standalone backpressure
> tests, block_ct != unblock_ct
> -
>
> Key: DISPATCH-2066
> URL: https://issues.apache.org/jira/browse/DISPATCH-2066
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Protocol Adaptors
>Affects Versions: 1.16.0
>Reporter: Jiri Daněk
>Assignee: Ken Giusti
>Priority: Major
> Labels: HTTP/1.x
>
> https://travis-ci.com/github/apache/qpid-dispatch/jobs/46271#L11501
> {noformat}
> test 70
> Start 70: system_tests_http1_adaptor
> 70: Test command: /usr/bin/python3.8
> "/home/travis/build/apache/qpid-dispatch/build/tests/run.py" "-m" "unittest"
> "-v" "system_tests_http1_adaptor"
> 70: Test timeout computed to be: 500
> 70: test_01_unsolicited_response
> (system_tests_http1_adaptor.Http1AdaptorBadEndpointsTest)
> 70: Create a server that sends an immediate Request Timeout response ... ok
> 70: test_02_bad_request_message
> (system_tests_http1_adaptor.Http1AdaptorBadEndpointsTest)
> 70: Test various improperly constructed request messages ... ok
> 70: test_03_bad_response_message
> (system_tests_http1_adaptor.Http1AdaptorBadEndpointsTest)
> 70: Test various improperly constructed response messages ... ok
> 70:
> 70: Router TestBadEndpoints output file:
> 70:
> 70: -
> 70: Suppressions used:
> 70: count bytes template
> 70: 1 24 ^pn_condition$
> 70: 1 1536 ^pn_raw_connection$
> 70: 1 56 qdr_core_subscribe
> 70: 2112 ^pn_string_grow$
> 70: 7328 ^pn_object_new$
> 70: 1128 ^pn_list$
> 70: 2 48 ^pni_record_create$
> 70: 597 926857 /libpython3.*.so
> 70: -
> 70:
> 70:
> 70:
> 70: test_01_concurrent_requests
> (system_tests_http1_adaptor.Http1AdaptorEdge2EdgeTest)
> 70: Test multiple concurrent clients sending streaming messages ... ok
> 70: test_02_credit_replenish
> (system_tests_http1_adaptor.Http1AdaptorEdge2EdgeTest)
> 70: Verify credit is replenished by sending > the default credit window ... ok
> 70: test_03_server_reconnect
> (system_tests_http1_adaptor.Http1AdaptorEdge2EdgeTest)
> 70: Verify server reconnect logic. ... ok
> 70: test_04_server_pining_for_the_fjords
> (system_tests_http1_adaptor.Http1AdaptorEdge2EdgeTest)
> 70: Test permanent loss of server ... ok
> 70: test_05_large_streaming_msg
> (system_tests_http1_adaptor.Http1AdaptorEdge2EdgeTest)
> 70: Verify large streaming message transfer ... ok
> 70:
> 70: Router EA2 output file:
> 70:
> 70: -
> 70: Suppressions used:
> 70: count bytes template
> 70: 7 59 ^load_server_config$
> 70: 6401 ^qd_dispatch_configure_connector$
> 70: 1 24 ^pn_condition$
> 70: 1 1536 ^pn_raw_connection$
> 70: 1 64 sys_mutex
> 70: 1 56 qdr_core_subscribe
> 70: 2112 ^pn_string_grow$
> 70: 7328 ^pn_object_new$
> 70: 1128 ^pn_list$
> 70: 2 48 ^pni_record_create$
> 70: 601 929697 /libpython3.*.so
> 70: -
> 70:
> 70:
> 70:
> 70:
> 70: Router EA2 debug dump file:
> 70:
> 70: alloc.c: Items of type 'qd_timer_t' remain allocated at shutdown: 1
> (SUPPRESSED)
> 70: alloc.c: Items of type 'qd_connector_t' remain allocated at shutdown: 1
> (SUPPRESSED)
> 70:
> 70:
> 70:
> 70: Router EA1 output file:
> 70:
> 70: -
> 70: Suppressions used:
> 70: count bytes template
> 70: 7 59 ^load_server_config$
> 70: 6401 ^qd_dispatch_configure_connector$
> 70: 1 64 sys_mutex
> 70: 1 56 qdr_core_subscribe
> 70: 601 929697 /libpython3.*.so
> 70: -
> 70:
> 70:
> 70:
> 70:
> 70: Router EA1 debug dump file:
> 70:
> 70: alloc.c: Items of type 'qd_timer_t' remain allocated at shutdown: 1
> (SUPPRESSED)
> 70: alloc.c: Items of type 'qd_connector_t' remain allocated at shutdown: 1
> (SUPPRESSED)
> 70:
> 70:
> 70:
> 70: Router INT.A output file:
> 70:
> 70: -
> 70: Suppressions used:
> 70: count bytes template
> 70: 6336 qdr_core_subscribe
> 70: 633 956953 /libpython3.*
[jira] [Updated] (DISPATCH-2087) TCP adaptor listener connections hang if no connectors are defined
[ https://issues.apache.org/jira/browse/DISPATCH-2087?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated DISPATCH-2087: - Fix Version/s: (was: 1.20.0) > TCP adaptor listener connections hang if no connectors are defined > -- > > Key: DISPATCH-2087 > URL: https://issues.apache.org/jira/browse/DISPATCH-2087 > Project: Qpid Dispatch > Issue Type: Bug >Reporter: Charles E. Rolke >Assignee: Ken Giusti >Priority: Major > > The proposed 1.16.0 freeze version of the TCP adaptor may have two start up > problems: > * a connector is defined but the server is absent > * no connector is defined > If a connector is defined but the server is absent: > * A client connects to the listener. Listener starts with SYN, SYN/ACK, ACK. > * The client sends the first payload bytes; listener ACKs > * The server connection fails with SYN, RST/ACK, ACK. > * The client connection is closed with FIN, FIN/ACK, ACK > If a connector is not defined: > * A client connects to the listener. Listener starts with SYN, SYN/ACK, ACK. > * The client sends the first payload bytes > * No further traffic is passed on the client connection > * Even if the server is started while the client is waiting no further > traffic is passed on the to the client. > Leaving the client connected forever with no hope of ever passing data is a > bug. Two approaches that would improve service for the client: > * If there is no connector then close the client connection immediately > * If the client connection is left open then when a tcpConnector is defined > attach that connector's server to the in-progress listener connection. > -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (DISPATCH-1892) http1 json aggregation does not handle large messages
[ https://issues.apache.org/jira/browse/DISPATCH-1892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated DISPATCH-1892: - Fix Version/s: (was: 1.20.0) > http1 json aggregation does not handle large messages > - > > Key: DISPATCH-1892 > URL: https://issues.apache.org/jira/browse/DISPATCH-1892 > Project: Qpid Dispatch > Issue Type: Bug > Components: Protocol Adaptors > Environment: At some point above 8k the conversion of the message > into a python message is truncating data. >Reporter: Gordon Sim >Assignee: Ken Giusti >Priority: Major > Labels: HTTP/1.x > -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (DISPATCH-2093) [tcp] TCP deliveries are counted as modified
[
https://issues.apache.org/jira/browse/DISPATCH-2093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robbie Gemmell updated DISPATCH-2093:
-
Fix Version/s: (was: 1.20.0)
> [tcp] TCP deliveries are counted as modified
>
>
> Key: DISPATCH-2093
> URL: https://issues.apache.org/jira/browse/DISPATCH-2093
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Protocol Adaptors
>Affects Versions: 1.15.0, 1.16.0
>Reporter: Ken Giusti
>Assignee: Ken Giusti
>Priority: Major
>
> TCP deliveries that pass over inter router links are being counted as
> 'modified' once the TCP connections complete. Since the inter router links
> survive much longer than the TCP links, the "modified" counters are visible
> long after TCP i done.
>
> Proposed fix:
> Add to void handle_disconnected(qdr_tcp_connection_t* conn):
> {{qd_log(tcp_adaptor->log_source, QD_LOG_DEBUG, "[C%"PRIu64"][L%"PRIu64"]
> handle_disconnected - close outstream", conn->conn_id, conn->outgoing_id);}}
> {{+ qdr_delivery_remote_state_updated(tcp_adaptor->core,}}
> {{+ conn->outstream,}}
> {{+ PN_ACCEPTED,}}
> {{+ true, // settled,}}
> {{+ 0, // delivery state}}
> {{+ false);}}
> {{qdr_delivery_decref(tcp_adaptor->core, conn->outstream,
> "tcp-adaptor.handle_disconnected - outstream");}}
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (DISPATCH-1890) need tests for http1 multicast
[ https://issues.apache.org/jira/browse/DISPATCH-1890?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated DISPATCH-1890: - Fix Version/s: (was: 1.20.0) > need tests for http1 multicast > -- > > Key: DISPATCH-1890 > URL: https://issues.apache.org/jira/browse/DISPATCH-1890 > Project: Qpid Dispatch > Issue Type: Improvement > Components: Protocol Adaptors >Reporter: Gordon Sim >Assignee: Ken Giusti >Priority: Major > Labels: HTTP/1.x > -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
