[jira] [Commented] (QPIDJMS-314) java.lang.AssertionError at io.netty.channel.epoll.EpollEventLoop.remove(EpollEventLoop.java:159)
[
https://issues.apache.org/jira/browse/QPIDJMS-314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16144727#comment-16144727
]
Jiri Danek commented on QPIDJMS-314:
After removing SO_LINGER, the tests are now passing for me. The workaround
works.
> java.lang.AssertionError at
> io.netty.channel.epoll.EpollEventLoop.remove(EpollEventLoop.java:159)
> -
>
> Key: QPIDJMS-314
> URL: https://issues.apache.org/jira/browse/QPIDJMS-314
> Project: Qpid JMS
> Issue Type: Bug
> Components: qpid-jms-client
>Affects Versions: 0.24.0
>Reporter: Jiri Danek
>
> I have a test suite which sometimes causes qpid-jms to die on AssertionError
> from netty. Rerunning the single failing test does not seem to reproduce it,
> I have to run the whole suite.
> First, start a broker. I am using ActiveMQ Artemis. The travis build uses a
> docker image with the broker. Then run the test suite in a loop, until it
> fails.
> {noformat}
> git clone g...@github.com:jdanekrh/cli-java.git
> cd cli-java/
> git checkout jd_code_push
> ret=0
> while [[ ret -eq 0 ]]; do mvn test; ret=$?; done
> {noformat}
> Here is log from when it failed in Travis,
> https://travis-ci.org/rh-messaging-qe/cli-java/jobs/267185207
> I do not know how to debug this (it never happened when I was running it
> under debugger). Also, even if I could get it in a debugger, I would not know
> what to do next.
> The relevant part of maven output is
> {noformat}
> [...]
> Receiving:
> 6,1,sendAndReceiveWithAllSenderCLISwitches(String),sendAndReceiveWithAllSenderCLISwitches(String),null,null,null
> 15:36:17.444Connecting: 1 0 1
> 15:36:17.515Sending: {'durable': True, 'priority': 4, 'ttl': 0,
> 'first-acquirer': False, 'delivery-count': 0, 'redelivered': False, 'id':
> 'ID:aConnIdPrefix32a68f56-629b-4111-a36c-aede9135c52c:1:1:1-1', 'user_id':
> None, 'address': 'lalaLand_l6o9ghgpom4jmu15cln21gpoi5', 'subject': None,
> 'reply_to': None, 'correlation_id': None, 'content_type': None,
> 'content_encoding': None, 'absolute-expiry-time': 0, 'creation-time':
> 1503408977545, 'group-id': None, 'group-sequence': 0, 'reply-to-group-id':
> None, 'properties': {'JMSXDeliveryCount': 1}, 'content': None}
> Tests run: 21, Failures: 2, Errors: 0, Skipped: 0, Time elapsed: 10.384 sec
> <<< FAILURE! - in AacMainTest
> sendAndReceiveWithAllSenderCLISwitches(String) Time elapsed: 0.336 sec <<<
> FAILURE!
> java.lang.AssertionError
> at
> io.netty.channel.epoll.EpollEventLoop.remove(EpollEventLoop.java:159)
> at
> io.netty.channel.epoll.AbstractEpollChannel.doDeregister(AbstractEpollChannel.java:142)
> at
> io.netty.channel.epoll.AbstractEpollChannel.doClose(AbstractEpollChannel.java:118)
> at
> io.netty.channel.epoll.AbstractEpollStreamChannel.doClose(AbstractEpollStreamChannel.java:703)
> at
> io.netty.channel.AbstractChannel$AbstractUnsafe.doClose0(AbstractChannel.java:685)
> at
> io.netty.channel.AbstractChannel$AbstractUnsafe.access$700(AbstractChannel.java:419)
> at
> io.netty.channel.AbstractChannel$AbstractUnsafe$5.run(AbstractChannel.java:646)
> at
> io.netty.util.concurrent.GlobalEventExecutor$TaskRunner.run(GlobalEventExecutor.java:233)
> at
> io.netty.util.concurrent.DefaultThreadFactory$DefaultRunnableDecorator.run(DefaultThreadFactory.java:138)
> at java.lang.Thread.run(Thread.java:748)
> sendAndReceiveSingleMessage() Time elapsed: 0.049 sec <<< FAILURE!
> java.lang.AssertionError
> at
> io.netty.channel.epoll.EpollEventLoop.remove(EpollEventLoop.java:159)
> at
> io.netty.channel.epoll.AbstractEpollChannel.doDeregister(AbstractEpollChannel.java:142)
> at
> io.netty.channel.epoll.AbstractEpollChannel.doClose(AbstractEpollChannel.java:118)
> at
> io.netty.channel.epoll.AbstractEpollStreamChannel.doClose(AbstractEpollStreamChannel.java:703)
> at
> io.netty.channel.AbstractChannel$AbstractUnsafe.doClose0(AbstractChannel.java:685)
> at
> io.netty.channel.AbstractChannel$AbstractUnsafe.access$700(AbstractChannel.java:419)
> at
> io.netty.channel.AbstractChannel$AbstractUnsafe$5.run(AbstractChannel.java:646)
> at
> io.netty.util.concurrent.GlobalEventExecutor$TaskRunner.run(GlobalEventExecutor.java:233)
> at
> io.netty.util.concurrent.DefaultThreadFactory$DefaultRunnableDecorator.run(DefaultThreadFactory.java:138)
> at java.lang.Thread.run(Thread.java:748)
> Results :
> Failed tests:
> AbstractMainTest.sendAndReceiveSingleMessage
> sendAndReceiveWithAllSenderCLISwitches(String).sendAndReceiveWithAllSenderCLISwitches(String)
> Run 1: PASS
> Run 2: PASS
> Run 3: PASS
> Run 4: PASS
> Run 5: PASS
> Run 6: PASS
> Run 7:
[jira] [Closed] (QPID-7901) Prevent endless detach cycle
[ https://issues.apache.org/jira/browse/QPID-7901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alan Conway closed QPID-7901. - Resolution: Fixed > Prevent endless detach cycle > > > Key: QPID-7901 > URL: https://issues.apache.org/jira/browse/QPID-7901 > Project: Qpid > Issue Type: Bug > Components: C++ Broker, C++ Client > Environment: In unusual situations it is possible to create a cycle > where each end of a connection replies to a "detach" frame with another > "detach" frame in an endless loop. >Reporter: Alan Conway >Assignee: Alan Conway > -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-7901) Prevent endless detach cycle
[ https://issues.apache.org/jira/browse/QPID-7901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16144424#comment-16144424 ] ASF subversion and git services commented on QPID-7901: --- Commit b3559ee9c66f791c39a4e86f87bc1533b7eb0ba5 in qpid-cpp's branch refs/heads/master from [~aconway] [ https://git-wip-us.apache.org/repos/asf?p=qpid-cpp.git;h=b3559ee ] QPID-7901: Prevent endless detach cycle Don't send a detach when there is an exception on a session that is already detached. Prevents an endless detach loop between the ends of the connection. > Prevent endless detach cycle > > > Key: QPID-7901 > URL: https://issues.apache.org/jira/browse/QPID-7901 > Project: Qpid > Issue Type: Bug > Components: C++ Broker, C++ Client > Environment: In unusual situations it is possible to create a cycle > where each end of a connection replies to a "detach" frame with another > "detach" frame in an endless loop. >Reporter: Alan Conway >Assignee: Alan Conway > -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-1557) c++ example of multi-threaded sending/receivng client
[ https://issues.apache.org/jira/browse/PROTON-1557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16144422#comment-16144422 ] ASF subversion and git services commented on PROTON-1557: - Commit 398f786ba94857b00d052c03232f8f9ef97f3f44 in qpid-proton's branch refs/heads/master from [~aconway] [ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=398f786 ] PROTON-1557: c++ improve multi-threaded clients 2 clients: - multithreaded_client.cpp: simple send thread, receive thread, run thread - multithreaded_client_flow_control: multi-connection, block for flow control Changes: - reduced needless diff between examples - use separate work_queue* to clarify separate thread safety rules from sender - took work_queue->add() out of lock to emphasize it is thread safe - use fixed argument list, same arg order > c++ example of multi-threaded sending/receivng client > - > > Key: PROTON-1557 > URL: https://issues.apache.org/jira/browse/PROTON-1557 > Project: Qpid Proton > Issue Type: Improvement > Components: cpp-binding >Affects Versions: 0.17.0 >Reporter: Alan Conway >Assignee: Alan Conway > Fix For: proton-c-0.18.0 > > > A C++ example of a client that sends and receives in multiple threads. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-1557) c++ example of multi-threaded sending/receivng client
[ https://issues.apache.org/jira/browse/PROTON-1557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16144418#comment-16144418 ] ASF subversion and git services commented on PROTON-1557: - Commit a5f88a1cc6af8d9758edcd76b0b6db8ffca4bd5b in qpid-proton's branch refs/heads/master from [~aconway] [ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=a5f88a1 ] PROTON-1557: c++ improve multi-threaded clients 2 clients: - multithreaded_client.cpp: simple send thread, receive thread, run thread - multithreaded_client_flow_control: multi-connection, block for flow control Changes: - reduced needless diff between examples - use separate work_queue* to clarify separate thread safety rules from sender - took work_queue->add() out of lock to emphasize it is thread safe - use fixed argument list, same arg order > c++ example of multi-threaded sending/receivng client > - > > Key: PROTON-1557 > URL: https://issues.apache.org/jira/browse/PROTON-1557 > Project: Qpid Proton > Issue Type: Improvement > Components: cpp-binding >Affects Versions: 0.17.0 >Reporter: Alan Conway >Assignee: Alan Conway > Fix For: proton-c-0.18.0 > > > A C++ example of a client that sends and receives in multiple threads. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-1554) c++: remove thread_safe and returned templates
[ https://issues.apache.org/jira/browse/PROTON-1554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16144415#comment-16144415 ] ASF subversion and git services commented on PROTON-1554: - Commit f1ee268163ce80c2b9dc3dcb7ec00151f5c6b486 in qpid-proton's branch refs/heads/master from [~aconway] [ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=f1ee268 ] PROTON-1554: Remove thread-safe template, simplify returned<> Removed the thread-safe template. Simplified and documented returned<>: It can *only* be converted to proton object, and only in a single-threaded application. > c++: remove thread_safe and returned templates > -- > > Key: PROTON-1554 > URL: https://issues.apache.org/jira/browse/PROTON-1554 > Project: Qpid Proton > Issue Type: Improvement > Environment: These templates are over complex. Replace with a simpler > unsafe template that can convert to T for single threaded apps, and should > be ignored for multi-threaded apps >Reporter: Alan Conway >Assignee: Alan Conway > -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-1557) c++ example of multi-threaded sending/receivng client
[ https://issues.apache.org/jira/browse/PROTON-1557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16144417#comment-16144417 ] ASF subversion and git services commented on PROTON-1557: - Commit 298e7dba1b8c09781abca0a4a555b90116703a8a in qpid-proton's branch refs/heads/master from [~aconway] [ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=298e7db ] PROTON-1557: c++ improve multi-threaded clients 2 clients: - multithreaded_client.cpp: simple send thread, receive thread, run thread - multithreaded_client_flow_control: multi-connection, block for flow control Changes: - reduced needless diff between examples - use separate work_queue* to clarify separate thread safety rules from sender - took work_queue->add() out of lock to emphasize it is thread safe - use fixed argument list, same arg order > c++ example of multi-threaded sending/receivng client > - > > Key: PROTON-1557 > URL: https://issues.apache.org/jira/browse/PROTON-1557 > Project: Qpid Proton > Issue Type: Improvement > Components: cpp-binding >Affects Versions: 0.17.0 >Reporter: Alan Conway >Assignee: Alan Conway > Fix For: proton-c-0.18.0 > > > A C++ example of a client that sends and receives in multiple threads. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-1553) c++ add support for wake() with MT example
[ https://issues.apache.org/jira/browse/PROTON-1553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16144416#comment-16144416 ] ASF subversion and git services commented on PROTON-1553: - Commit 68c8cf43e51bbe71d7042688fbcda52de1ed5cce in qpid-proton's branch refs/heads/master from [~aconway] [ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=68c8cf4 ] PROTON-1553: c++ wake() events > c++ add support for wake() with MT example > -- > > Key: PROTON-1553 > URL: https://issues.apache.org/jira/browse/PROTON-1553 > Project: Qpid Proton > Issue Type: Improvement > Components: cpp-binding >Affects Versions: 0.17.0 >Reporter: Alan Conway >Assignee: Alan Conway > Fix For: proton-c-0.18.0 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (DISPATCH-800) Hawtio version of the console is unable to connect to a router when running offline
[
https://issues.apache.org/jira/browse/DISPATCH-800?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ernest Allen resolved DISPATCH-800.
---
Resolution: Fixed
Assignee: Ernest Allen
Fix Version/s: 1.0.0
Saved js/css and font files that were being loaded via a cdn. Updated the make
dispatch LICENSE file to contain the licenses.
> Hawtio version of the console is unable to connect to a router when running
> offline
> ---
>
> Key: DISPATCH-800
> URL: https://issues.apache.org/jira/browse/DISPATCH-800
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Console
>Affects Versions: 1.0.0
> Environment: Tested in Internet Explorer 11 on Windows 7 with git tip
> at
> {noformat}
> commit 4dd8764b341cdf9e1d5c06c99697f454d4eaa468
> Author: Ganesh Murthy
> Date: Mon Jul 31 17:09:30 2017 -0400
> DISPATCH-799 - Fixed CMakeLists.txt to set the TEST_RUNNER variable
> correctly
> {noformat}
>Reporter: Jiri Danek
>Assignee: Ernest Allen
>Priority: Minor
> Fix For: 1.0.0
>
>
> My web browser can only connect to the server running the console and to the
> router; the computer does not have unrestricted network access. With this
> setup, the console does not work.
> In Hawtio version of the console running on IE11, I am unable to login. After
> filling in the router ip and port, I see the rotating wheel of dots forever.
> After a while, the following errors appear in browser console
> {noformat}
> HTML1300: Navigation occurred.
> File: hawtio
> DOM7011: The code on this page disabled back and forward caching. For more
> information, see: http://go.microsoft.com/fwlink/?LinkID=291337
> File: list
> [QDR] *creating Dispatch Console
> [QDR] curPath is /
> [RBAC] Using mbean
> hawtio:type=security,area=jmx,rank=0,name=HawtioDummyJMXSecurity for
> client-side role based access control
> [Core] hawtio started
> XML5632: Only one root element is allowed.
> Line: 3, Column 2
> [QDR] testConnect called with reconnect true using ws protocol
> [QDR] got schema after connection
> [QDR] requesting a topology
> SCRIPT438: Object doesn't support property or method 'queue'
> File: eval code (40), Line: 5, Column: 8603
> [Window] Object doesn't support property or method 'queue' ( href=":5">:5:8603)
> {noformat}
> In Chrome, the symptoms and the error is essentially the same:
> {noformat}
> app.js?c8641b2e13788127:4 [Deprecation] Synchronous XMLHttpRequest on the
> main thread is deprecated because of its detrimental effects to the end
> user's experience. For more help, check https://xhr.spec.whatwg.org/.
> send @ app.js?c8641b2e13788127:4
> d3.min.js Failed to load resource: net::ERR_NAME_NOT_RESOLVED
> d3-queue.min.js Failed to load resource: net::ERR_NAME_NOT_RESOLVED
> FileSaver.min.js Failed to load resource: net::ERR_NAME_NOT_RESOLVED
> app.js?c8641b2e13788127:16 [Themes] unknown theme name, using default theme
> app.js?c8641b2e13788127:16 [QDR] *creating Dispatch
> Console
> app.js?c8641b2e13788127:16 [QDR] curPath is /
> cdnjs.cloudflare.com/ajax/libs/jquery.tipsy/1.0.2/jquery.tipsy.css Failed to
> load resource: net::ERR_NAME_NOT_RESOLVED
> maxcdn.bootstrapcdn.com/font-awesome/4.5.0/css/font-awesome.min.css Failed to
> load resource: net::ERR_NAME_NOT_RESOLVED
> app.js?c8641b2e13788127:16 [RBAC] Using mbean
> hawtio:type=security,area=jmx,rank=0,name=HawtioDummyJMXSecurity for
> client-side role based access control
> app.js?c8641b2e13788127:16 [Core] hawtio started
> jquery.tipsy.js Failed to load resource: net::ERR_NAME_NOT_RESOLVED
> tooltipsy.min.js Failed to load resource: net::ERR_NAME_NOT_RESOLVED
> code.jquery.com/ui/1.8.24/themes/base/jquery-ui.css Failed to load resource:
> net::ERR_NAME_NOT_RESOLVED
> app.js?c8641b2e13788127:16 [QDR] testConnect called with reconnect true using
> ws protocol
> app.js?c8641b2e13788127:16 [QDR] got schema after connection
> app.js?c8641b2e13788127:16 [QDR] requesting a topology
> app.js?c8641b2e13788127:16 [Window] Uncaught TypeError: QDR.queue is not a
> function ( href="http://192.168.99.1:8080/hawtio/dispatch_hawtio_console/:5;>http://192.168.99.1:8080/hawtio/dispatch_hawtio_console/:5:8603)
> consoleLogger @ app.js?c8641b2e13788127:16
> {noformat}
> CC [~eallen]
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (DISPATCH-800) Hawtio version of the console is unable to connect to a router when running offline
[
https://issues.apache.org/jira/browse/DISPATCH-800?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16144100#comment-16144100
]
ASF subversion and git services commented on DISPATCH-800:
--
Commit 4efb180c7b01bdf5e25ca6a2452757dd6ce398fe in qpid-dispatch's branch
refs/heads/master from [~eallen]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-dispatch.git;h=4efb180 ]
DISPATCH-800 For Hawtio, copy external js/css/font files locally and update
LICENSE
> Hawtio version of the console is unable to connect to a router when running
> offline
> ---
>
> Key: DISPATCH-800
> URL: https://issues.apache.org/jira/browse/DISPATCH-800
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Console
>Affects Versions: 1.0.0
> Environment: Tested in Internet Explorer 11 on Windows 7 with git tip
> at
> {noformat}
> commit 4dd8764b341cdf9e1d5c06c99697f454d4eaa468
> Author: Ganesh Murthy
> Date: Mon Jul 31 17:09:30 2017 -0400
> DISPATCH-799 - Fixed CMakeLists.txt to set the TEST_RUNNER variable
> correctly
> {noformat}
>Reporter: Jiri Danek
>Priority: Minor
>
> My web browser can only connect to the server running the console and to the
> router; the computer does not have unrestricted network access. With this
> setup, the console does not work.
> In Hawtio version of the console running on IE11, I am unable to login. After
> filling in the router ip and port, I see the rotating wheel of dots forever.
> After a while, the following errors appear in browser console
> {noformat}
> HTML1300: Navigation occurred.
> File: hawtio
> DOM7011: The code on this page disabled back and forward caching. For more
> information, see: http://go.microsoft.com/fwlink/?LinkID=291337
> File: list
> [QDR] *creating Dispatch Console
> [QDR] curPath is /
> [RBAC] Using mbean
> hawtio:type=security,area=jmx,rank=0,name=HawtioDummyJMXSecurity for
> client-side role based access control
> [Core] hawtio started
> XML5632: Only one root element is allowed.
> Line: 3, Column 2
> [QDR] testConnect called with reconnect true using ws protocol
> [QDR] got schema after connection
> [QDR] requesting a topology
> SCRIPT438: Object doesn't support property or method 'queue'
> File: eval code (40), Line: 5, Column: 8603
> [Window] Object doesn't support property or method 'queue' ( href=":5">:5:8603)
> {noformat}
> In Chrome, the symptoms and the error is essentially the same:
> {noformat}
> app.js?c8641b2e13788127:4 [Deprecation] Synchronous XMLHttpRequest on the
> main thread is deprecated because of its detrimental effects to the end
> user's experience. For more help, check https://xhr.spec.whatwg.org/.
> send @ app.js?c8641b2e13788127:4
> d3.min.js Failed to load resource: net::ERR_NAME_NOT_RESOLVED
> d3-queue.min.js Failed to load resource: net::ERR_NAME_NOT_RESOLVED
> FileSaver.min.js Failed to load resource: net::ERR_NAME_NOT_RESOLVED
> app.js?c8641b2e13788127:16 [Themes] unknown theme name, using default theme
> app.js?c8641b2e13788127:16 [QDR] *creating Dispatch
> Console
> app.js?c8641b2e13788127:16 [QDR] curPath is /
> cdnjs.cloudflare.com/ajax/libs/jquery.tipsy/1.0.2/jquery.tipsy.css Failed to
> load resource: net::ERR_NAME_NOT_RESOLVED
> maxcdn.bootstrapcdn.com/font-awesome/4.5.0/css/font-awesome.min.css Failed to
> load resource: net::ERR_NAME_NOT_RESOLVED
> app.js?c8641b2e13788127:16 [RBAC] Using mbean
> hawtio:type=security,area=jmx,rank=0,name=HawtioDummyJMXSecurity for
> client-side role based access control
> app.js?c8641b2e13788127:16 [Core] hawtio started
> jquery.tipsy.js Failed to load resource: net::ERR_NAME_NOT_RESOLVED
> tooltipsy.min.js Failed to load resource: net::ERR_NAME_NOT_RESOLVED
> code.jquery.com/ui/1.8.24/themes/base/jquery-ui.css Failed to load resource:
> net::ERR_NAME_NOT_RESOLVED
> app.js?c8641b2e13788127:16 [QDR] testConnect called with reconnect true using
> ws protocol
> app.js?c8641b2e13788127:16 [QDR] got schema after connection
> app.js?c8641b2e13788127:16 [QDR] requesting a topology
> app.js?c8641b2e13788127:16 [Window] Uncaught TypeError: QDR.queue is not a
> function ( href="http://192.168.99.1:8080/hawtio/dispatch_hawtio_console/:5;>http://192.168.99.1:8080/hawtio/dispatch_hawtio_console/:5:8603)
> consoleLogger @ app.js?c8641b2e13788127:16
> {noformat}
> CC [~eallen]
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPIDJMS-314) java.lang.AssertionError at io.netty.channel.epoll.EpollEventLoop.remove(EpollEventLoop.java:159)
[
https://issues.apache.org/jira/browse/QPIDJMS-314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16143977#comment-16143977
]
Robbie Gemmell commented on QPIDJMS-314:
I believe this is a bug in Netty, which your test is tripping due to its use of
options to configure a TCP SO_LINGER value. I have raised
https://github.com/netty/netty/issues/7159 to report it.
If you are looking for stability in your test suite before this can be
resolved, I'd suggest changing the test (use of so_linger not being that
typical), or perhaps just not enabling assertions for the test run might work.
> java.lang.AssertionError at
> io.netty.channel.epoll.EpollEventLoop.remove(EpollEventLoop.java:159)
> -
>
> Key: QPIDJMS-314
> URL: https://issues.apache.org/jira/browse/QPIDJMS-314
> Project: Qpid JMS
> Issue Type: Bug
> Components: qpid-jms-client
>Affects Versions: 0.24.0
>Reporter: Jiri Danek
>
> I have a test suite which sometimes causes qpid-jms to die on AssertionError
> from netty. Rerunning the single failing test does not seem to reproduce it,
> I have to run the whole suite.
> First, start a broker. I am using ActiveMQ Artemis. The travis build uses a
> docker image with the broker. Then run the test suite in a loop, until it
> fails.
> {noformat}
> git clone g...@github.com:jdanekrh/cli-java.git
> cd cli-java/
> git checkout jd_code_push
> ret=0
> while [[ ret -eq 0 ]]; do mvn test; ret=$?; done
> {noformat}
> Here is log from when it failed in Travis,
> https://travis-ci.org/rh-messaging-qe/cli-java/jobs/267185207
> I do not know how to debug this (it never happened when I was running it
> under debugger). Also, even if I could get it in a debugger, I would not know
> what to do next.
> The relevant part of maven output is
> {noformat}
> [...]
> Receiving:
> 6,1,sendAndReceiveWithAllSenderCLISwitches(String),sendAndReceiveWithAllSenderCLISwitches(String),null,null,null
> 15:36:17.444Connecting: 1 0 1
> 15:36:17.515Sending: {'durable': True, 'priority': 4, 'ttl': 0,
> 'first-acquirer': False, 'delivery-count': 0, 'redelivered': False, 'id':
> 'ID:aConnIdPrefix32a68f56-629b-4111-a36c-aede9135c52c:1:1:1-1', 'user_id':
> None, 'address': 'lalaLand_l6o9ghgpom4jmu15cln21gpoi5', 'subject': None,
> 'reply_to': None, 'correlation_id': None, 'content_type': None,
> 'content_encoding': None, 'absolute-expiry-time': 0, 'creation-time':
> 1503408977545, 'group-id': None, 'group-sequence': 0, 'reply-to-group-id':
> None, 'properties': {'JMSXDeliveryCount': 1}, 'content': None}
> Tests run: 21, Failures: 2, Errors: 0, Skipped: 0, Time elapsed: 10.384 sec
> <<< FAILURE! - in AacMainTest
> sendAndReceiveWithAllSenderCLISwitches(String) Time elapsed: 0.336 sec <<<
> FAILURE!
> java.lang.AssertionError
> at
> io.netty.channel.epoll.EpollEventLoop.remove(EpollEventLoop.java:159)
> at
> io.netty.channel.epoll.AbstractEpollChannel.doDeregister(AbstractEpollChannel.java:142)
> at
> io.netty.channel.epoll.AbstractEpollChannel.doClose(AbstractEpollChannel.java:118)
> at
> io.netty.channel.epoll.AbstractEpollStreamChannel.doClose(AbstractEpollStreamChannel.java:703)
> at
> io.netty.channel.AbstractChannel$AbstractUnsafe.doClose0(AbstractChannel.java:685)
> at
> io.netty.channel.AbstractChannel$AbstractUnsafe.access$700(AbstractChannel.java:419)
> at
> io.netty.channel.AbstractChannel$AbstractUnsafe$5.run(AbstractChannel.java:646)
> at
> io.netty.util.concurrent.GlobalEventExecutor$TaskRunner.run(GlobalEventExecutor.java:233)
> at
> io.netty.util.concurrent.DefaultThreadFactory$DefaultRunnableDecorator.run(DefaultThreadFactory.java:138)
> at java.lang.Thread.run(Thread.java:748)
> sendAndReceiveSingleMessage() Time elapsed: 0.049 sec <<< FAILURE!
> java.lang.AssertionError
> at
> io.netty.channel.epoll.EpollEventLoop.remove(EpollEventLoop.java:159)
> at
> io.netty.channel.epoll.AbstractEpollChannel.doDeregister(AbstractEpollChannel.java:142)
> at
> io.netty.channel.epoll.AbstractEpollChannel.doClose(AbstractEpollChannel.java:118)
> at
> io.netty.channel.epoll.AbstractEpollStreamChannel.doClose(AbstractEpollStreamChannel.java:703)
> at
> io.netty.channel.AbstractChannel$AbstractUnsafe.doClose0(AbstractChannel.java:685)
> at
> io.netty.channel.AbstractChannel$AbstractUnsafe.access$700(AbstractChannel.java:419)
> at
> io.netty.channel.AbstractChannel$AbstractUnsafe$5.run(AbstractChannel.java:646)
> at
> io.netty.util.concurrent.GlobalEventExecutor$TaskRunner.run(GlobalEventExecutor.java:233)
> at
> io.netty.util.concurrent.DefaultThreadFactory$DefaultRunnableDecorator.run(DefaultThreadFactory.java:138)
>
[jira] [Commented] (QPID-7896) Create system tests testing end-to-end message conversion
[ https://issues.apache.org/jira/browse/QPID-7896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16143940#comment-16143940 ] ASF subversion and git services commented on QPID-7896: --- Commit d3ca1343bf95408e23a9563efc98f31121ea3815 in qpid-broker-j's branch refs/heads/master from [~lorenz.quack] [ https://git-wip-us.apache.org/repos/asf?p=qpid-broker-j.git;h=d3ca134 ] QPID-7896: [Java System Tests] Add more conversion tests > Create system tests testing end-to-end message conversion > - > > Key: QPID-7896 > URL: https://issues.apache.org/jira/browse/QPID-7896 > Project: Qpid > Issue Type: New Feature > Components: Java Tests >Reporter: Lorenz Quack > Fix For: qpid-java-broker-7.0.0 > > > Qpid v7 has much matured AMQP 1.0 support. > We expect adoption of AMQP 1.0 to only increase. > Some users might want to perform a staged update of their client from AMQP > 0-x to 1.0. > To support this message conversion becomes more important. > To gain confidence in our message conversion capabilities we should have > system tests testing our main use case (JMS) end-to-end. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (DISPATCH-811) Attributes tab label spelled 'Attriutes'
[ https://issues.apache.org/jira/browse/DISPATCH-811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ernest Allen resolved DISPATCH-811. --- Resolution: Fixed Assignee: Ernest Allen Fix Version/s: 1.0.0 Fix the typo but the commit message did not reference this Jira. That was commit 27665df8909e9d9fad99c9fea914e2c22bdd121b > Attributes tab label spelled 'Attriutes' > > > Key: DISPATCH-811 > URL: https://issues.apache.org/jira/browse/DISPATCH-811 > Project: Qpid Dispatch > Issue Type: Bug > Components: Console >Affects Versions: 0.8.0 >Reporter: Ernest Allen >Assignee: Ernest Allen >Priority: Minor > Fix For: 1.0.0 > > > Using the dispatch web console as launched from AMQ 7 GA if you browse an > address where the 3rd layer down tab's should say 'Attributes Links' it > instead says 'Attriutes Links' -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (DISPATCH-811) Attributes tab label spelled 'Attriutes'
[ https://issues.apache.org/jira/browse/DISPATCH-811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16143849#comment-16143849 ] Ernest Allen commented on DISPATCH-811: --- Fix in commit 27665df8909e9d9fad99c9fea914e2c22bdd121b > Attributes tab label spelled 'Attriutes' > > > Key: DISPATCH-811 > URL: https://issues.apache.org/jira/browse/DISPATCH-811 > Project: Qpid Dispatch > Issue Type: Bug > Components: Console >Affects Versions: 0.8.0 >Reporter: Ernest Allen >Priority: Minor > > Using the dispatch web console as launched from AMQ 7 GA if you browse an > address where the 3rd layer down tab's should say 'Attributes Links' it > instead says 'Attriutes Links' -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (DISPATCH-811) Attributes tab label spelled 'Attriutes'
Ernest Allen created DISPATCH-811: - Summary: Attributes tab label spelled 'Attriutes' Key: DISPATCH-811 URL: https://issues.apache.org/jira/browse/DISPATCH-811 Project: Qpid Dispatch Issue Type: Bug Components: Console Affects Versions: 0.8.0 Reporter: Ernest Allen Priority: Minor Using the dispatch web console as launched from AMQ 7 GA if you browse an address where the 3rd layer down tab's should say 'Attributes Links' it instead says 'Attriutes Links' -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-7902) [Java Client 0-8...0-9-1] setJMSReplyTo() with ADDR Destination is broken
[
https://issues.apache.org/jira/browse/QPID-7902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lorenz Quack updated QPID-7902:
---
Affects Version/s: qpid-java-client-0-x-6.3.0
qpid-java-6.0
qpid-java-6.1
qpid-java-6.1.4
qpid-java-6.0.8
> [Java Client 0-8...0-9-1] setJMSReplyTo() with ADDR Destination is broken
> -
>
> Key: QPID-7902
> URL: https://issues.apache.org/jira/browse/QPID-7902
> Project: Qpid
> Issue Type: Bug
> Components: Java Client
>Affects Versions: qpid-java-6.0, qpid-java-6.1,
> qpid-java-client-0-x-6.3.0, qpid-java-6.1.4, qpid-java-6.0.8
>Reporter: Lorenz Quack
>
> When calling {{setJMSReplyTo}} on a 0-8 message using a ADDR based
> destination it tries to convert the destination into a string by calling
> {{AMQDestination#toURL()}} which assumes a BURL. The result is a
> non-functional ReplyTo field.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-7902) [Java Client 0-8...0-9-1] setJMSReplyTo() with ADDR Destination is broken
[
https://issues.apache.org/jira/browse/QPID-7902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16143837#comment-16143837
]
Lorenz Quack commented on QPID-7902:
This code changed on trunk. QPID-7533 modified this but seems to only preserve
the queue or exchange name and discards all other information (routing key,
options, ...).
> [Java Client 0-8...0-9-1] setJMSReplyTo() with ADDR Destination is broken
> -
>
> Key: QPID-7902
> URL: https://issues.apache.org/jira/browse/QPID-7902
> Project: Qpid
> Issue Type: Bug
> Components: Java Client
>Reporter: Lorenz Quack
>
> When calling {{setJMSReplyTo}} on a 0-8 message using a ADDR based
> destination it tries to convert the destination into a string by calling
> {{AMQDestination#toURL()}} which assumes a BURL. The result is a
> non-functional ReplyTo field.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Comment Edited] (QPID-7902) [Java Client 0-8...0-9-1] setJMSReplyTo() with ADDR Destination is broken
[
https://issues.apache.org/jira/browse/QPID-7902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16143837#comment-16143837
]
Lorenz Quack edited comment on QPID-7902 at 8/28/17 2:34 PM:
-
This code changed on trunk. QPID-7533 modified
{{AMQDestination#getEncodedName}} but seems to only preserve the queue or
exchange name and discards all other information (routing key, options, ...).
was (Author: lorenz.quack):
This code changed on trunk. QPID-7533 modified this but seems to only preserve
the queue or exchange name and discards all other information (routing key,
options, ...).
> [Java Client 0-8...0-9-1] setJMSReplyTo() with ADDR Destination is broken
> -
>
> Key: QPID-7902
> URL: https://issues.apache.org/jira/browse/QPID-7902
> Project: Qpid
> Issue Type: Bug
> Components: Java Client
>Reporter: Lorenz Quack
>
> When calling {{setJMSReplyTo}} on a 0-8 message using a ADDR based
> destination it tries to convert the destination into a string by calling
> {{AMQDestination#toURL()}} which assumes a BURL. The result is a
> non-functional ReplyTo field.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-7902) [Java Client 0-8...0-9-1] setJMSReplyTo() with ADDR Destination is broken
[
https://issues.apache.org/jira/browse/QPID-7902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16143819#comment-16143819
]
Lorenz Quack commented on QPID-7902:
For the record, the reply-to field will contain {{null://null//}}
> [Java Client 0-8...0-9-1] setJMSReplyTo() with ADDR Destination is broken
> -
>
> Key: QPID-7902
> URL: https://issues.apache.org/jira/browse/QPID-7902
> Project: Qpid
> Issue Type: Bug
> Components: Java Client
>Reporter: Lorenz Quack
>
> When calling {{setJMSReplyTo}} on a 0-8 message using a ADDR based
> destination it tries to convert the destination into a string by calling
> {{AMQDestination#toURL()}} which assumes a BURL. The result is a
> non-functional ReplyTo field.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (QPID-7902) [Java Client 0-8...0-9-1] setJMSReplyTo() with ADDR Destination is broken
Lorenz Quack created QPID-7902:
--
Summary: [Java Client 0-8...0-9-1] setJMSReplyTo() with ADDR
Destination is broken
Key: QPID-7902
URL: https://issues.apache.org/jira/browse/QPID-7902
Project: Qpid
Issue Type: Bug
Components: Java Client
Reporter: Lorenz Quack
When calling {{setJMSReplyTo}} on a 0-8 message using a ADDR based destination
it tries to convert the destination into a string by calling
{{AMQDestination#toURL()}} which assumes a BURL. The result is a non-functional
ReplyTo field.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (QPIDJMS-316) set up Travis CI to test on OSX and Linux
[ https://issues.apache.org/jira/browse/QPIDJMS-316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell resolved QPIDJMS-316. Resolution: Fixed > set up Travis CI to test on OSX and Linux > - > > Key: QPIDJMS-316 > URL: https://issues.apache.org/jira/browse/QPIDJMS-316 > Project: Qpid JMS > Issue Type: Task > Components: qpid-jms-client >Reporter: Robbie Gemmell >Assignee: Robbie Gemmell >Priority: Minor > Fix For: 0.25.0 > > > We currently don't test on OSX, however Travis CI also offers OSX build nodes > which we can use, so lets... -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (QPIDJMS-315) Add support for Netty KQueue transport
[ https://issues.apache.org/jira/browse/QPIDJMS-315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell resolved QPIDJMS-315. Resolution: Fixed Assignee: Robbie Gemmell > Add support for Netty KQueue transport > -- > > Key: QPIDJMS-315 > URL: https://issues.apache.org/jira/browse/QPIDJMS-315 > Project: Qpid JMS > Issue Type: New Feature >Affects Versions: 0.24.0 >Reporter: Michael Andre Pearce >Assignee: Robbie Gemmell > Fix For: 0.25.0 > > > Add support for using the Netty KQueue transport when the platform supports > it (x86-64 osx) and provide a transport configuration option to bypass it and > return to using NIO. This change also switches the transport to using the > default Netty allocator on the transports which by default is a pooled > allocator. > To disable kqueue use the URI can be updated to include option: > transport.useKQueue=false -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (QPID-7901) Prevent endless detach cycle
Alan Conway created QPID-7901: - Summary: Prevent endless detach cycle Key: QPID-7901 URL: https://issues.apache.org/jira/browse/QPID-7901 Project: Qpid Issue Type: Bug Components: C++ Broker, C++ Client Environment: In unusual situations it is possible to create a cycle where each end of a connection replies to a "detach" frame with another "detach" frame in an endless loop. Reporter: Alan Conway Assignee: Alan Conway -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Closed] (PROTON-1561) Prevent endless detach cycle
[ https://issues.apache.org/jira/browse/PROTON-1561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alan Conway closed PROTON-1561. --- Resolution: Invalid qpid issue created on proton JIRA in error > Prevent endless detach cycle > > > Key: PROTON-1561 > URL: https://issues.apache.org/jira/browse/PROTON-1561 > Project: Qpid Proton > Issue Type: Bug >Reporter: Alan Conway >Assignee: Alan Conway > > In some unusual situations it is possible to create an endless detach cycle > where each end of a connection responds to a detach with another detach > containing an "unexpected detach" error endlessly. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (PROTON-1561) Prevent endless detach cycle
Alan Conway created PROTON-1561: --- Summary: Prevent endless detach cycle Key: PROTON-1561 URL: https://issues.apache.org/jira/browse/PROTON-1561 Project: Qpid Proton Issue Type: Bug Reporter: Alan Conway Assignee: Alan Conway In some unusual situations it is possible to create an endless detach cycle where each end of a connection responds to a detach with another detach containing an "unexpected detach" error endlessly. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (PROTON-1560) Cannot install qpid_proton-0.18.0.gem
Alan Conway created PROTON-1560:
---
Summary: Cannot install qpid_proton-0.18.0.gem
Key: PROTON-1560
URL: https://issues.apache.org/jira/browse/PROTON-1560
Project: Qpid Proton
Issue Type: Bug
Components: ruby-binding
Reporter: Alan Conway
Assignee: Alan Conway
Snapshot of master at commit 8c3ba5.
When using these specific flags, compilation fails:
CONFIGURE_ARGS='--with-cflags='\''-O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2
-fexceptions -fstack-protector-strong --param=ssp-buffer-size=4
-grecord-gcc-switches -m64 -mtune=generic'\'' '
+ gem install -V --local --install-dir ./usr/share/gems --bindir ./usr/bin
--force --document=ri,rdoc qpid_proton-0.18.0.gem
gcc -I. -I/usr/include -I/usr/include/ruby/backward -I/usr/include -I.
-DHAVE_PROTON_ENGINE_H -DHAVE_PROTON_MESSAGE_H -DHAVE_PROTON_SASL_H
-DHAVE_PROTON_MESSENGER_H-fPIC -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2
-fexceptions -fstack-protector-strong --param=ssp-buffer-size=4
-grecord-gcc-switches -m64 -mtune=generic -DRUBY20 -m64 -o cproton.o -c
cproton.c
Linked Applications
JBoss Issue Tracker
Dashboards
Projects
Issues
Boards
Portfolio
Create
Help
Administration
User profile for Alan Conway
AMQ ClientsIcon indicating the project type
AMQ Clients
A-MQ Clients
Backlog
Active sprints
Releases
Reports
Issues
Components
Uploaded image for project: 'AMQ Clients'
AMQ ClientsENTMQCL-530
Cannot install qpid_proton-0.18.0.gem
Edit
Comment
Assign
More
Ready for Dev
Closed
Export
Details
Type:
Task
Status:
Ready for Triage (View Workflow)
Priority:
Major
Resolution:
Unresolved
Affects Version/s:
Future GA
Fix Version/s:
None
Component/s:
proton-c
Labels:
None
Environment:
RHEL 7, RPM Build
Description
Snapshot of master at commit 8c3ba5.
When using these specific flags, compilation fails:
CONFIGURE_ARGS='--with-cflags='\''-O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2
-fexceptions -fstack-protector-strong --param=ssp-buffer-size=4
-grecord-gcc-switches -m64 -mtune=generic'\'' '
+ gem install -V --local --install-dir ./usr/share/gems --bindir ./usr/bin
--force --document=ri,rdoc qpid_proton-0.18.0.gem
gcc -I. -I/usr/include -I/usr/include/ruby/backward -I/usr/include -I.
-DHAVE_PROTON_ENGINE_H -DHAVE_PROTON_MESSAGE_H -DHAVE_PROTON_SASL_H
-DHAVE_PROTON_MESSENGER_H -fPIC -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2
-fexceptions -fstack-protector-strong --param=ssp-buffer-size=4
-grecord-gcc-switches -m64 -mtune=generic -DRUBY20 -m64 -o cproton.o -c
cproton.c
cproton.c:6540:12: warning: 'check_trace' defined but not used
[-Wunused-function]
static int check_trace(int x) {
^
make: *** [cproton.o] Error 1
ERROR: Error installing qpid_proton-0.18.0.gem:
ERROR: Failed to build gem native extension.
Building has failed. See above output for more information on the failure.
Attachments
Drop files to attach, or
Activity
All
Comments
Work Log
History
Activity
Links Hierarchy
Linked Cases
There are no comments yet on this issue.
Comment
People
Assignee:
aconway Alan Conway
Reporter:
iboverma Irina Boverman
Votes:
0 Vote for this issue
Watchers:
1
Start watching this issue
Dates
Created:
4 days ago
Updated:
2 days ago
Agile
View on Board
cproton.c:6540:12: warning: 'check_trace' defined but not used
[-Wunused-function]
static int check_trace(int x) {
^
make: *** [cproton.o] Error 1
ERROR: Error installing qpid_proton-0.18.0.gem:
ERROR: Failed to build gem native extension.
Building has failed. See above output for more information on the failure.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (QPID-7900) [Java Broker] SASL External mechanism does not respond correctly if no initial response is present
Rob Godfrey created QPID-7900:
-
Summary: [Java Broker] SASL External mechanism does not respond
correctly if no initial response is present
Key: QPID-7900
URL: https://issues.apache.org/jira/browse/QPID-7900
Project: Qpid
Issue Type: Bug
Components: Java Broker
Reporter: Rob Godfrey
As pointed out by [~gemmellr] in PROTON-1555:
{quote}
The client is expected to send data first in the authentication exchange.
Where the client does not provide an initial response data in its request to
initiate the authentication exchange, the server is to respond to the request
with an empty initial challenge and then the client is to provide its initial
response.
{quote}
https://tools.ietf.org/html/rfc4422#page-29
That is to say that if the initial response is not present, then rather than
simply accepting the authentication (which is what the broker will currently
do), an empty challenge should be sent.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (PROTON-1559) Typo in some proactor examples
[
https://issues.apache.org/jira/browse/PROTON-1559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jiri Danek updated PROTON-1559:
---
Description:
Some proactor examples have a typo in the code that reads CLI options. It does
not seem to have effect on functionality, because the {{argv[argc]}} element is
always a NULL.
{code}
diff --git a/examples/c/proactor/direct.c b/examples/c/proactor/direct.c
index 15550e6b..d33010f0 100644
--- a/examples/c/proactor/direct.c
+++ b/examples/c/proactor/direct.c
@@ -308,8 +308,8 @@ int main(int argc, char **argv) {
struct app_data_t app = {0};
int i = 0;
app.container_id = argv[i++]; /* Should be unique */
- app.host = (argc > 1) ? argv[i++] : "";
- app.port = (argc > 1) ? argv[i++] : "amqp";
+ app.host = (argc > i) ? argv[i++] : "";
+ app.port = (argc > i) ? argv[i++] : "amqp";
app.amqp_address = (argc > i) ? argv[i++] : "examples";
app.message_count = (argc > i) ? atoi(argv[i++]) : 10;
diff --git a/examples/c/proactor/receive.c b/examples/c/proactor/receive.c
index 6fd74a51..3f059f56 100644
--- a/examples/c/proactor/receive.c
+++ b/examples/c/proactor/receive.c
@@ -172,8 +172,8 @@ int main(int argc, char **argv) {
struct app_data_t app = {0};
int i = 0;
app.container_id = argv[i++]; /* Should be unique */
- app.host = (argc > 1) ? argv[i++] : "";
- app.port = (argc > 1) ? argv[i++] : "amqp";
+ app.host = (argc > i) ? argv[i++] : "";
+ app.port = (argc > i) ? argv[i++] : "amqp";
app.amqp_address = (argc > i) ? argv[i++] : "examples";
app.message_count = (argc > i) ? atoi(argv[i++]) : 10;
diff --git a/examples/c/proactor/send.c b/examples/c/proactor/send.c
index 43da8b04..a80fbcb5 100644
--- a/examples/c/proactor/send.c
+++ b/examples/c/proactor/send.c
@@ -180,8 +180,8 @@ int main(int argc, char **argv) {
struct app_data_t app = {0};
int i = 0;
app.container_id = argv[i++]; /* Should be unique */
- app.host = (argc > 1) ? argv[i++] : "";
- app.port = (argc > 1) ? argv[i++] : "amqp";
+ app.host = (argc > i) ? argv[i++] : "";
+ app.port = (argc > i) ? argv[i++] : "amqp";
app.amqp_address = (argc > i) ? argv[i++] : "examples";
app.message_count = (argc > i) ? atoi(argv[i++]) : 10;
{code}
was:
Some proactor examples have a typo in the code that loads CLI options. It does
not seem to have effect on functionality, because the {{argv[argc]}} element is
always a NULL.
{code}
diff --git a/examples/c/proactor/direct.c b/examples/c/proactor/direct.c
index 15550e6b..d33010f0 100644
--- a/examples/c/proactor/direct.c
+++ b/examples/c/proactor/direct.c
@@ -308,8 +308,8 @@ int main(int argc, char **argv) {
struct app_data_t app = {0};
int i = 0;
app.container_id = argv[i++]; /* Should be unique */
- app.host = (argc > 1) ? argv[i++] : "";
- app.port = (argc > 1) ? argv[i++] : "amqp";
+ app.host = (argc > i) ? argv[i++] : "";
+ app.port = (argc > i) ? argv[i++] : "amqp";
app.amqp_address = (argc > i) ? argv[i++] : "examples";
app.message_count = (argc > i) ? atoi(argv[i++]) : 10;
diff --git a/examples/c/proactor/receive.c b/examples/c/proactor/receive.c
index 6fd74a51..3f059f56 100644
--- a/examples/c/proactor/receive.c
+++ b/examples/c/proactor/receive.c
@@ -172,8 +172,8 @@ int main(int argc, char **argv) {
struct app_data_t app = {0};
int i = 0;
app.container_id = argv[i++]; /* Should be unique */
- app.host = (argc > 1) ? argv[i++] : "";
- app.port = (argc > 1) ? argv[i++] : "amqp";
+ app.host = (argc > i) ? argv[i++] : "";
+ app.port = (argc > i) ? argv[i++] : "amqp";
app.amqp_address = (argc > i) ? argv[i++] : "examples";
app.message_count = (argc > i) ? atoi(argv[i++]) : 10;
diff --git a/examples/c/proactor/send.c b/examples/c/proactor/send.c
index 43da8b04..a80fbcb5 100644
--- a/examples/c/proactor/send.c
+++ b/examples/c/proactor/send.c
@@ -180,8 +180,8 @@ int main(int argc, char **argv) {
struct app_data_t app = {0};
int i = 0;
app.container_id = argv[i++]; /* Should be unique */
- app.host = (argc > 1) ? argv[i++] : "";
- app.port = (argc > 1) ? argv[i++] : "amqp";
+ app.host = (argc > i) ? argv[i++] : "";
+ app.port = (argc > i) ? argv[i++] : "amqp";
app.amqp_address = (argc > i) ? argv[i++] : "examples";
app.message_count = (argc > i) ? atoi(argv[i++]) : 10;
{code}
> Typo in some proactor examples
> --
>
> Key: PROTON-1559
> URL: https://issues.apache.org/jira/browse/PROTON-1559
> Project: Qpid Proton
> Issue Type: Bug
> Components: examples, proton-c
>Affects Versions: proton-c-0.18.0
>Reporter: Jiri Danek
>Priority: Minor
>
> Some proactor examples have a typo in the code that reads CLI options. It
> does not seem to have effect on functionality, because the {{argv[argc]}}
> element is always a NULL.
> {code}
> diff --git
[jira] [Created] (PROTON-1559) Typo in some proactor examples
Jiri Danek created PROTON-1559:
--
Summary: Typo in some proactor examples
Key: PROTON-1559
URL: https://issues.apache.org/jira/browse/PROTON-1559
Project: Qpid Proton
Issue Type: Bug
Components: examples, proton-c
Affects Versions: proton-c-0.18.0
Reporter: Jiri Danek
Priority: Minor
Some proactor examples have a typo in the code that loads CLI options. It does
not seem to have effect on functionality, because the {{argv[argc]}} element is
always a NULL.
{code}
diff --git a/examples/c/proactor/direct.c b/examples/c/proactor/direct.c
index 15550e6b..d33010f0 100644
--- a/examples/c/proactor/direct.c
+++ b/examples/c/proactor/direct.c
@@ -308,8 +308,8 @@ int main(int argc, char **argv) {
struct app_data_t app = {0};
int i = 0;
app.container_id = argv[i++]; /* Should be unique */
- app.host = (argc > 1) ? argv[i++] : "";
- app.port = (argc > 1) ? argv[i++] : "amqp";
+ app.host = (argc > i) ? argv[i++] : "";
+ app.port = (argc > i) ? argv[i++] : "amqp";
app.amqp_address = (argc > i) ? argv[i++] : "examples";
app.message_count = (argc > i) ? atoi(argv[i++]) : 10;
diff --git a/examples/c/proactor/receive.c b/examples/c/proactor/receive.c
index 6fd74a51..3f059f56 100644
--- a/examples/c/proactor/receive.c
+++ b/examples/c/proactor/receive.c
@@ -172,8 +172,8 @@ int main(int argc, char **argv) {
struct app_data_t app = {0};
int i = 0;
app.container_id = argv[i++]; /* Should be unique */
- app.host = (argc > 1) ? argv[i++] : "";
- app.port = (argc > 1) ? argv[i++] : "amqp";
+ app.host = (argc > i) ? argv[i++] : "";
+ app.port = (argc > i) ? argv[i++] : "amqp";
app.amqp_address = (argc > i) ? argv[i++] : "examples";
app.message_count = (argc > i) ? atoi(argv[i++]) : 10;
diff --git a/examples/c/proactor/send.c b/examples/c/proactor/send.c
index 43da8b04..a80fbcb5 100644
--- a/examples/c/proactor/send.c
+++ b/examples/c/proactor/send.c
@@ -180,8 +180,8 @@ int main(int argc, char **argv) {
struct app_data_t app = {0};
int i = 0;
app.container_id = argv[i++]; /* Should be unique */
- app.host = (argc > 1) ? argv[i++] : "";
- app.port = (argc > 1) ? argv[i++] : "amqp";
+ app.host = (argc > i) ? argv[i++] : "";
+ app.port = (argc > i) ? argv[i++] : "amqp";
app.amqp_address = (argc > i) ? argv[i++] : "examples";
app.message_count = (argc > i) ? atoi(argv[i++]) : 10;
{code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (PROTON-1558) pypi setup.py fails to find openssl un ubuntu
[
https://issues.apache.org/jira/browse/PROTON-1558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Itamar Landsman updated PROTON-1558:
Description:
When installing python-qpid-proton from pip there is no ssl support.
Trying to build the package (pip download, untar and setup.py build) I get a
warning about OpenSSL not installed:
{quote}» python setup.py build
running build
running build_ext
running configure
Warning: command not found: pkg-config
Building the bundled proton-c sources into the extension
Warning: command not found: pkg-config
Warning: OpenSSL not installed - disabling SSL support!
creating build
.
.
.
{quote}
And indeed SSL is not available for the resulting built package.
A hack fix is to go into setup.py and edit the section where the presence of
OpenSSL is verified:
{quote}\# Check whether openssl is installed by poking
\# pkg-config for a minimum version 0. If it's installed, it should
\# return True and we'll use it. Otherwise, we'll use the stub.
if misc.pkg_config_version_installed('openssl', atleast='0'):
libraries += ['ssl', 'crypto']
sources.append(os.path.join(proton_src, 'ssl', 'openssl.c'))
else:
sources.append(os.path.join(proton_src, 'ssl', 'ssl_stub.c'))
log.warn("OpenSSL not installed - disabling SSL support!"){quote}
Change to:
{quote}\# Check whether openssl is installed by poking
\# pkg-config for a minimum version 0. If it's installed, it should
\# return True and we'll use it. Otherwise, we'll use the stub.
if True:
libraries += ['ssl', 'crypto']
sources.append(os.path.join(proton_src, 'ssl', 'openssl.c'))
else:
sources.append(os.path.join(proton_src, 'ssl', 'ssl_stub.c'))
log.warn("OpenSSL not installed - disabling SSL support!"){quote}
Now, package is indeed built with SSL support.
The library discovery mechanism needs to be fixed, I expect.
was:
When installing python-qpid-proton from pip there is no ssl support.
Trying to build the package (pip download, untar and setup.py build) I get a
warning about OpenSSL not installed:
{quote}» python setup.py build
running build
running build_ext
running configure
Warning: command not found: pkg-config
Building the bundled proton-c sources into the extension
Warning: command not found: pkg-config
Warning: OpenSSL not installed - disabling SSL support!
creating build
.
.
.
{quote}
And indeed SSL is not available for the resulting built package.
A hack fix is to go into setup.py and edit the section where the presence of
OpenSSL is verified:
{quote}# Check whether openssl is installed by poking
# pkg-config for a minimum version 0. If it's installed, it should
# return True and we'll use it. Otherwise, we'll use the stub.
if misc.pkg_config_version_installed('openssl', atleast='0'):
libraries += ['ssl', 'crypto']
sources.append(os.path.join(proton_src, 'ssl', 'openssl.c'))
else:
sources.append(os.path.join(proton_src, 'ssl', 'ssl_stub.c'))
log.warn("OpenSSL not installed - disabling SSL support!"){quote}
Change to:
{quote}# Check whether openssl is installed by poking
# pkg-config for a minimum version 0. If it's installed, it should
# return True and we'll use it. Otherwise, we'll use the stub.
if True:
libraries += ['ssl', 'crypto']
sources.append(os.path.join(proton_src, 'ssl', 'openssl.c'))
else:
sources.append(os.path.join(proton_src, 'ssl', 'ssl_stub.c'))
log.warn("OpenSSL not installed - disabling SSL support!"){quote}
Now, package is indeed built with SSL support.
The library discovery mechanism needs to be fixed, I expect.
> pypi setup.py fails to find openssl un ubuntu
> -
>
> Key: PROTON-1558
> URL: https://issues.apache.org/jira/browse/PROTON-1558
> Project: Qpid Proton
> Issue Type: Bug
> Components: python-binding
>Affects Versions: 0.17.0
> Environment: Ubuntu 16.04
>Reporter: Itamar Landsman
>
> When installing python-qpid-proton from pip there is no ssl support.
> Trying to build the package (pip download, untar and setup.py build) I get a
> warning about OpenSSL not installed:
> {quote}» python setup.py build
> running build
> running build_ext
> running configure
> Warning: command not found: pkg-config
> Building the bundled proton-c sources into the extension
> Warning: command not found: pkg-config
> Warning: OpenSSL not installed - disabling SSL support!
> creating build
> .
> .
> .
> {quote}
> And indeed SSL is not available for the resulting built package.
> A hack fix is to go into setup.py and edit the section where the presence of
> OpenSSL is verified:
> {quote}\#
[jira] [Created] (PROTON-1558) pypi setup.py fails to find openssl un ubuntu
Itamar Landsman created PROTON-1558:
---
Summary: pypi setup.py fails to find openssl un ubuntu
Key: PROTON-1558
URL: https://issues.apache.org/jira/browse/PROTON-1558
Project: Qpid Proton
Issue Type: Bug
Components: python-binding
Affects Versions: 0.17.0
Environment: Ubuntu 16.04
Reporter: Itamar Landsman
When installing python-qpid-proton from pip there is no ssl support.
Trying to build the package (pip download, untar and setup.py build) I get a
warning about OpenSSL not installed:
{quote}» python setup.py build
running build
running build_ext
running configure
Warning: command not found: pkg-config
Building the bundled proton-c sources into the extension
Warning: command not found: pkg-config
Warning: OpenSSL not installed - disabling SSL support!
creating build
.
.
.
{quote}
And indeed SSL is not available for the resulting built package.
A hack fix is to go into setup.py and edit the section where the presence of
OpenSSL is verified:
{quote}# Check whether openssl is installed by poking
# pkg-config for a minimum version 0. If it's installed, it should
# return True and we'll use it. Otherwise, we'll use the stub.
if misc.pkg_config_version_installed('openssl', atleast='0'):
libraries += ['ssl', 'crypto']
sources.append(os.path.join(proton_src, 'ssl', 'openssl.c'))
else:
sources.append(os.path.join(proton_src, 'ssl', 'ssl_stub.c'))
log.warn("OpenSSL not installed - disabling SSL support!"){quote}
Change to:
{quote}# Check whether openssl is installed by poking
# pkg-config for a minimum version 0. If it's installed, it should
# return True and we'll use it. Otherwise, we'll use the stub.
if True:
libraries += ['ssl', 'crypto']
sources.append(os.path.join(proton_src, 'ssl', 'openssl.c'))
else:
sources.append(os.path.join(proton_src, 'ssl', 'ssl_stub.c'))
log.warn("OpenSSL not installed - disabling SSL support!"){quote}
Now, package is indeed built with SSL support.
The library discovery mechanism needs to be fixed, I expect.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
