date:20180228

[jira] [Commented] (PROTON-1777) 0.22.0 release tasks

2018-02-28 Thread ASF subversion and git services (JIRA)


[ 
https://issues.apache.org/jira/browse/PROTON-1777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16380905#comment-16380905
 ] 

ASF subversion and git services commented on PROTON-1777:
-

Commit d069b20de8c340ad669418615206e67d18dcdbed in qpid-proton's branch 
refs/heads/master from [~gemmellr]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=d069b20 ]

PROTON-1752, PROTON-1777: update versions for 0.22.0-SNAPSHOT


> 0.22.0 release tasks
> 
>
> Key: PROTON-1777
> URL: https://issues.apache.org/jira/browse/PROTON-1777
> Project: Qpid Proton
>  Issue Type: Task
>  Components: proton-c, release
>Reporter: Robbie Gemmell
>Assignee: Robbie Gemmell
>Priority: Major
> Fix For: proton-c-0.22.0
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Commented] (PROTON-1752) 0.21.0 release tasks

2018-02-28 Thread ASF subversion and git services (JIRA)


[ 
https://issues.apache.org/jira/browse/PROTON-1752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16380903#comment-16380903
 ] 

ASF subversion and git services commented on PROTON-1752:
-

Commit 61c0c03e270001d50225157e123420159ce6bf33 in qpid-proton's branch 
refs/heads/master from [~gemmellr]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=61c0c03 ]

PROTON-1752: update versions for 0.21.0-rc1


> 0.21.0 release tasks
> 
>
> Key: PROTON-1752
> URL: https://issues.apache.org/jira/browse/PROTON-1752
> Project: Qpid Proton
>  Issue Type: Task
>  Components: proton-c, release
>Reporter: Robbie Gemmell
>Assignee: Robbie Gemmell
>Priority: Major
> Fix For: proton-c-0.21.0
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Commented] (PROTON-1752) 0.21.0 release tasks

2018-02-28 Thread ASF subversion and git services (JIRA)


[ 
https://issues.apache.org/jira/browse/PROTON-1752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16380904#comment-16380904
 ] 

ASF subversion and git services commented on PROTON-1752:
-

Commit d069b20de8c340ad669418615206e67d18dcdbed in qpid-proton's branch 
refs/heads/master from [~gemmellr]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=d069b20 ]

PROTON-1752, PROTON-1777: update versions for 0.22.0-SNAPSHOT


> 0.21.0 release tasks
> 
>
> Key: PROTON-1752
> URL: https://issues.apache.org/jira/browse/PROTON-1752
> Project: Qpid Proton
>  Issue Type: Task
>  Components: proton-c, release
>Reporter: Robbie Gemmell
>Assignee: Robbie Gemmell
>Priority: Major
> Fix For: proton-c-0.21.0
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Assigned] (QPID-8115) [Broker-J] Incorrect symbolic descriptor used for no-local filter

2018-02-28 Thread Alex Rudyy (JIRA)


 [ 
https://issues.apache.org/jira/browse/QPID-8115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alex Rudyy reassigned QPID-8115:


Assignee: Alex Rudyy

> [Broker-J] Incorrect symbolic descriptor used for no-local filter
> -
>
> Key: QPID-8115
> URL: https://issues.apache.org/jira/browse/QPID-8115
> Project: Qpid
>  Issue Type: Task
>  Components: Broker-J
>Affects Versions: qpid-java-broker-7.0.2, qpid-java-broker-7.0.0, 
> qpid-java-broker-7.0.1
>Reporter: Alex Rudyy
>Assignee: Alex Rudyy
>Priority: Major
>
> [apache.org amp specification extension for 
> filters|http://www.amqp.org/specification/1.0/filters] declares {{no local 
> filter}} with symbolic descriptor {{apache.org:no-local-filter:list}}. The 
> Broker-J uses incorrect symbolic descriptor 
> {{"apache.org:jms-no-local-filter:list"}}.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Resolved] (QPIDIT-114) [AMQP.NetLite] AMQP char type is not supported, but is not excluded from test

2018-02-28 Thread Kim van der Riet (JIRA)


 [ 
https://issues.apache.org/jira/browse/QPIDIT-114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Kim van der Riet resolved QPIDIT-114.
-
Resolution: Fixed

> [AMQP.NetLite] AMQP char type is not supported, but is not excluded from test
> -
>
> Key: QPIDIT-114
> URL: https://issues.apache.org/jira/browse/QPIDIT-114
> Project: Apache QPID Interoperability Test Suite
>  Issue Type: Bug
>  Components: .Net Lite Shim, AMQP Types Test
>Affects Versions: 0.1.0
>Reporter: Kim van der Riet
>Assignee: Kim van der Riet
>Priority: Major
>
> When the amqp_types_test is run against the ActiveMQ broker (which can handle 
> AMQP type char, unlike several other brokers), the tests of AMQP type 
> {{char}} fail with an error message from the AMQP.NetLite shims:
> {noformat}
> System.ApplicationException: Sender can not encode base type: char{noformat}
> As a mechanism exists in each test to exclude AMQP types based on the client 
> being run, this should be added.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Created] (QPIDIT-114) [AMQP.NetLite] AMQP char type is not supported, but is not excluded from test

2018-02-28 Thread Kim van der Riet (JIRA)

Kim van der Riet created QPIDIT-114:
---

 Summary: [AMQP.NetLite] AMQP char type is not supported, but is 
not excluded from test
 Key: QPIDIT-114
 URL: https://issues.apache.org/jira/browse/QPIDIT-114
 Project: Apache QPID Interoperability Test Suite
  Issue Type: Bug
  Components: .Net Lite Shim, AMQP Types Test
Affects Versions: 0.1.0
Reporter: Kim van der Riet
Assignee: Kim van der Riet


When the amqp_types_test is run against the ActiveMQ broker (which can handle 
AMQP type char, unlike several other brokers), the tests of AMQP type {{char}} 
fail with an error message from the AMQP.NetLite shims:
{noformat}
System.ApplicationException: Sender can not encode base type: char{noformat}
As a mechanism exists in each test to exclude AMQP types based on the client 
being run, this should be added.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Updated] (PROTON-1592) [proton-python] accessing properties of event.receiver in on_link_opened throws exception

2018-02-28 Thread Alan Conway (JIRA)


 [ 
https://issues.apache.org/jira/browse/PROTON-1592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alan Conway updated PROTON-1592:

Fix Version/s: (was: proton-c-future)
   proton-c-0.22.0

> [proton-python] accessing properties of event.receiver in on_link_opened 
> throws exception
> -
>
> Key: PROTON-1592
> URL: https://issues.apache.org/jira/browse/PROTON-1592
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: python-binding
>Reporter: Jiri Daněk
>Assignee: Alan Conway
>Priority: Major
>  Labels: regression
> Fix For: proton-c-0.22.0
>
>
> Apply the following patch to the {{tx-recv.py}} example
> {code}
> diff --git a/examples/python/tx_recv.py b/examples/python/tx_recv.py
> index 4baddcf5..54f3b489 100755
> --- a/examples/python/tx_recv.py
> +++ b/examples/python/tx_recv.py
> @@ -40,6 +40,9 @@ class TxRecv(MessagingHandler, TransactionHandler):
>  self.container.declare_transaction(self.conn, handler=self)
>  self.transaction = None
>  
> + def on_link_opened(self, event):
> + event.receiver.drain_mode = True
> +
>  def on_message(self, event):
>  print(event.message.body)
>  self.transaction.accept(event.delivery)
> {code}
> Now run first {{tx_send.py}}, then this {{tx_recv.py}}. The second command 
> throws exception
> {noformat}
> $ LD_LIBRARY_PATH=`pwd`/lib64 PYTHONPATH=`pwd`/lib64/proton/bindings/python 
> python ../examples/python/tx_recv.py
> Traceback (most recent call last):
>   File "../examples/python/tx_recv.py", line 79, in 
> Container(TxRecv(opts.address, opts.messages, opts.batch_size)).run()
>   File 
> "/home/jdanek/Work/repos/qpid-proton/install/lib64/proton/bindings/python/proton/reactor.py",
>  line 148, in run
> while self.process(): pass
>   File 
> "/home/jdanek/Work/repos/qpid-proton/install/lib64/proton/bindings/python/proton/reactor.py",
>  line 174, in process
> self._check_errors()
>   File 
> "/home/jdanek/Work/repos/qpid-proton/install/lib64/proton/bindings/python/proton/reactor.py",
>  line 170, in _check_errors
> _compat.raise_(exc, value, tb)
>   File 
> "/home/jdanek/Work/repos/qpid-proton/install/lib64/proton/bindings/python/proton/__init__.py",
>  line 4068, in dispatch
> ev.dispatch(self.handler)
>   File 
> "/home/jdanek/Work/repos/qpid-proton/install/lib64/proton/bindings/python/proton/__init__.py",
>  line 3977, in dispatch
> result = dispatch(handler, type.method, self)
>   File 
> "/home/jdanek/Work/repos/qpid-proton/install/lib64/proton/bindings/python/proton/__init__.py",
>  line 3857, in dispatch
> return handler.on_unhandled(method, *args)
>   File 
> "/home/jdanek/Work/repos/qpid-proton/install/lib64/proton/bindings/python/proton/reactor.py",
>  line 876, in on_unhandled
> event.dispatch(handler)
>   File 
> "/home/jdanek/Work/repos/qpid-proton/install/lib64/proton/bindings/python/proton/__init__.py",
>  line 3980, in dispatch
> self.dispatch(h, type)
>   File 
> "/home/jdanek/Work/repos/qpid-proton/install/lib64/proton/bindings/python/proton/__init__.py",
>  line 3977, in dispatch
> result = dispatch(handler, type.method, self)
>   File 
> "/home/jdanek/Work/repos/qpid-proton/install/lib64/proton/bindings/python/proton/__init__.py",
>  line 3855, in dispatch
> return m(*args)
>   File 
> "/home/jdanek/Work/repos/qpid-proton/install/lib64/proton/bindings/python/proton/handlers.py",
>  line 298, in on_link_remote_open
> self.on_link_opened(event)
>   File 
> "/home/jdanek/Work/repos/qpid-proton/install/lib64/proton/bindings/python/proton/handlers.py",
>  line 313, in on_link_opened
> dispatch(self.delegate, 'on_link_opened', event)
>   File 
> "/home/jdanek/Work/repos/qpid-proton/install/lib64/proton/bindings/python/proton/__init__.py",
>  line 3855, in dispatch
> return m(*args)
>   File "../examples/python/tx_recv.py", line 44, in on_link_opened
> event.receiver.drain_mode = True
> AttributeError: 'NoneType' object has no attribute 'drain_mode'
> {noformat}
> To see this is a regression, repeat now with python-qpid-proton 0.17.0 from 
> Pypi. With this previous release, there is success.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Commented] (QPIDIT-114) [AMQP.NetLite] AMQP char type is not supported, but is not excluded from test

2018-02-28 Thread ASF subversion and git services (JIRA)


[ 
https://issues.apache.org/jira/browse/QPIDIT-114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16380800#comment-16380800
 ] 

ASF subversion and git services commented on QPIDIT-114:


Commit 71ea06dfc2a7f29784878593f75ad2dfcd0baaf3 in qpid-interop-test's branch 
refs/heads/master from [~kpvdr]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-interop-test.git;h=71ea06d ]

QPIDIT-114: Added AMQP type char to list of excluded types for AMQP.NetLite 
shims


> [AMQP.NetLite] AMQP char type is not supported, but is not excluded from test
> -
>
> Key: QPIDIT-114
> URL: https://issues.apache.org/jira/browse/QPIDIT-114
> Project: Apache QPID Interoperability Test Suite
>  Issue Type: Bug
>  Components: .Net Lite Shim, AMQP Types Test
>Affects Versions: 0.1.0
>Reporter: Kim van der Riet
>Assignee: Kim van der Riet
>Priority: Major
>
> When the amqp_types_test is run against the ActiveMQ broker (which can handle 
> AMQP type char, unlike several other brokers), the tests of AMQP type 
> {{char}} fail with an error message from the AMQP.NetLite shims:
> {noformat}
> System.ApplicationException: Sender can not encode base type: char{noformat}
> As a mechanism exists in each test to exclude AMQP types based on the client 
> being run, this should be added.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Updated] (PROTON-1775) rubygem doc is not multilib-clean for x86_64 vs i686

2018-02-28 Thread Alan Conway (JIRA)


 [ 
https://issues.apache.org/jira/browse/PROTON-1775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alan Conway updated PROTON-1775:

Fix Version/s: proton-c-0.22.0

> rubygem doc is not multilib-clean for x86_64 vs i686
> 
>
> Key: PROTON-1775
> URL: https://issues.apache.org/jira/browse/PROTON-1775
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: ruby-binding
>Reporter: Irina Boverman
>Assignee: Alan Conway
>Priority: Major
> Fix For: proton-c-0.22.0
>
>
> RHEL 6:
> Subpackage rubygem-qpid_proton-doc is not multilib-clean for x86_64 vs i686: 
> 166 files have non-equal 32/64bit content: 
> /usr/lib/ruby/gems/1.8/doc/qpid_proton-0.20.0/ri/created.rid 
> /usr/lib/ruby/gems/1.8/doc/qpid_proton-0.20.0/ri/Qpid/Proton/cdesc-Proton.yaml
>  
> /usr/lib/ruby/gems/1.8/doc/qpid_proton-0.20.0/ri/Qpid/Proton/Codec/cdesc-Codec.yaml
>  /usr/lib/ruby/gems/1.8/doc/qpid_proton-0.20.0/rdoc/index.html 
> /usr/lib/ruby/gems/1.8/doc/qpid_proton-0.20.0/rdoc/fr_method_index.html 
> /usr/lib/ruby/gems/1.8/doc/qpid_proton-0.20.0/rdoc/files/lib/util/wrapper_rb.html
>  
> /usr/lib/ruby/gems/1.8/doc/qpid_proton-0.20.0/rdoc/files/lib/util/version_rb.html
>  
> /usr/lib/ruby/gems/1.8/doc/qpid_proton-0.20.0/rdoc/files/lib/util/timeout_rb.html
>  
> /usr/lib/ruby/gems/1.8/doc/qpid_proton-0.20.0/rdoc/files/lib/util/error_handler_rb.html
>  
> /usr/lib/ruby/gems/1.8/doc/qpid_proton-0.20.0/rdoc/files/lib/util/deprecation_rb.html



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Updated] (PROTON-1760) [ruby-binding] the package name on rubygems.org does not follow conventions

2018-02-28 Thread Alan Conway (JIRA)


 [ 
https://issues.apache.org/jira/browse/PROTON-1760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alan Conway updated PROTON-1760:

Fix Version/s: proton-c-0.22.0

> [ruby-binding] the package name on rubygems.org does not follow conventions
> ---
>
> Key: PROTON-1760
> URL: https://issues.apache.org/jira/browse/PROTON-1760
> Project: Qpid Proton
>  Issue Type: Wish
>  Components: ruby-binding
>Affects Versions: proton-c-0.21.0
>Reporter: Jiri Daněk
>Assignee: Alan Conway
>Priority: Trivial
> Fix For: proton-c-0.22.0
>
>
> The rubygems.org name is currently {{qpid_proton}}. From a not-so-random 
> sampling, it seems to me use of dashes is more common than that of 
> underscores. Additionally, the package in PyPi is called 
> {{python-qpid-proton}}.
> I propose renaming the ruby package to {{qpid-proton}} or 
> {{ruby-qpid-proton}} or even {{qpid-proton-ruby}}. If possible, which it may 
> not be, by now.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Updated] (PROTON-1615) c++: container leaks if exception thrown by handler.

2018-02-28 Thread Alan Conway (JIRA)


 [ 
https://issues.apache.org/jira/browse/PROTON-1615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alan Conway updated PROTON-1615:

Fix Version/s: proton-c-0.22.0

> c++: container leaks if exception thrown by handler.
> 
>
> Key: PROTON-1615
> URL: https://issues.apache.org/jira/browse/PROTON-1615
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: cpp-binding
>Reporter: Alan Conway
>Assignee: Alan Conway
>Priority: Major
>  Labels: leak
> Fix For: proton-c-0.22.0
>
>
> An exception throw by a handler is re-thrown out of container.run() as 
> expected, however
> the container does not shut down cleanly and many leaks are reported by 
> valgrind or asan. The container should be exception-safe.
> To demonstrate the problem apply this small patch to the helloworld_direct 
> example.
> examples/cpp/helloworld_direct.cpp | 1 +
> modified   examples/cpp/helloworld_direct.cpp
> @@ -53,6 +53,7 @@ class hello_world_direct : public proton::messaging_handler 
> {
>  
>  // Receive one message and stop listener
>  void on_message(proton::delivery &, proton::message ) OVERRIDE {
> +throw std::runtime_error("thrown from on_message");
>  std::cout << m.body() << std::endl;
>  listener.stop();
>  }



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Commented] (PROTON-1760) [ruby-binding] the package name on rubygems.org does not follow conventions

2018-02-28 Thread Alan Conway (JIRA)


[ 
https://issues.apache.org/jira/browse/PROTON-1760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16380823#comment-16380823
 ] 

Alan Conway commented on PROTON-1760:
-

According to http://guides.rubygems.org/name-your-gem/ the gem should be named
"qpid-proton" because Qpid::Proton is a module in a submodule. 

(According to that guide, if the gem is called qpid_proton, then the top-level 
class/module should be  QpidProton.)

For the Gem name I don't think there should be a "ruby" prefix or suffix. (The 
RPM name for downstream packagers might have something, e.g. fedora would be 
rubygem-qpid-proton)

I propose to make the change for 0.22 and leave the 0.21 gem in place for 
backwards compat - anyone know of any other rules to follow for a name change 
like this on rubygems.org?


> [ruby-binding] the package name on rubygems.org does not follow conventions
> ---
>
> Key: PROTON-1760
> URL: https://issues.apache.org/jira/browse/PROTON-1760
> Project: Qpid Proton
>  Issue Type: Wish
>  Components: ruby-binding
>Affects Versions: proton-c-0.21.0
>Reporter: Jiri Daněk
>Assignee: Alan Conway
>Priority: Trivial
> Fix For: proton-c-0.22.0
>
>
> The rubygems.org name is currently {{qpid_proton}}. From a not-so-random 
> sampling, it seems to me use of dashes is more common than that of 
> underscores. Additionally, the package in PyPi is called 
> {{python-qpid-proton}}.
> I propose renaming the ruby package to {{qpid-proton}} or 
> {{ruby-qpid-proton}} or even {{qpid-proton-ruby}}. If possible, which it may 
> not be, by now.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Commented] (PROTON-1760) [ruby-binding] the package name on rubygems.org does not follow conventions

2018-02-28 Thread Alan Conway (JIRA)


[ 
https://issues.apache.org/jira/browse/PROTON-1760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16380824#comment-16380824
 ] 

Alan Conway commented on PROTON-1760:
-

[~iboverma] you should keep an eye on this for downstream packaging.

> [ruby-binding] the package name on rubygems.org does not follow conventions
> ---
>
> Key: PROTON-1760
> URL: https://issues.apache.org/jira/browse/PROTON-1760
> Project: Qpid Proton
>  Issue Type: Wish
>  Components: ruby-binding
>Affects Versions: proton-c-0.21.0
>Reporter: Jiri Daněk
>Assignee: Alan Conway
>Priority: Trivial
> Fix For: proton-c-0.22.0
>
>
> The rubygems.org name is currently {{qpid_proton}}. From a not-so-random 
> sampling, it seems to me use of dashes is more common than that of 
> underscores. Additionally, the package in PyPi is called 
> {{python-qpid-proton}}.
> I propose renaming the ruby package to {{qpid-proton}} or 
> {{ruby-qpid-proton}} or even {{qpid-proton-ruby}}. If possible, which it may 
> not be, by now.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Resolved] (QPIDIT-113) AMQP.NetLite shims produce error message on stderr which should be ignored

2018-02-28 Thread Kim van der Riet (JIRA)


 [ 
https://issues.apache.org/jira/browse/QPIDIT-113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Kim van der Riet resolved QPIDIT-113.
-
Resolution: Fixed

Fixed by checking for and ignoring this error message. A rather ugly but quick 
way to fix this issue.

> AMQP.NetLite shims produce error message on stderr which should be ignored
> --
>
> Key: QPIDIT-113
> URL: https://issues.apache.org/jira/browse/QPIDIT-113
> Project: Apache QPID Interoperability Test Suite
>  Issue Type: Bug
>  Components: .Net Lite Shim
>Affects Versions: 0.1.0
>Reporter: Kim van der Riet
>Assignee: Kim van der Riet
>Priority: Major
>
> While running the AMQP .NetLite shims on CentOS7, the shims produce a single 
> instance of the following error message on stderr:
> {noformat}
> Got a bad hardware address length for an AF_PACKET 20 8{noformat}
> As the tests treat _any_ text on stderr as an error condition, the tests 
> fail. In fact the shims are behaving normally in every other way and complete 
> the tests normally.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Created] (DISPATCH-934) Add a way to annotate configuration as experimental

2018-02-28 Thread Ted Ross (JIRA)

Ted Ross created DISPATCH-934:
-

 Summary: Add a way to annotate configuration as experimental
 Key: DISPATCH-934
 URL: https://issues.apache.org/jira/browse/DISPATCH-934
 Project: Qpid Dispatch
  Issue Type: New Feature
  Components: Management Agent
Reporter: Ted Ross
Assignee: Ganesh Murthy
 Fix For: 1.1.0


Add a management-schema annotation for entities and attributes that labels them 
as "experimental".  Any time an experimental item is used in configuration (or 
via the management protocol) the router shall issue a log warning stating that 
the configuration is experimental and may not be supported in the future.

 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Commented] (QPID-8115) [Broker-J] Incorrect symbolic descriptor used for no-local filter

2018-02-28 Thread ASF subversion and git services (JIRA)


[ 
https://issues.apache.org/jira/browse/QPID-8115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16381011#comment-16381011
 ] 

ASF subversion and git services commented on QPID-8115:
---

Commit 8df4ff38b30e7277706976defdfefb6680d029df in qpid-broker-j's branch 
refs/heads/master from [~alex.rufous]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-broker-j.git;h=8df4ff3 ]

QPID-8115: [Broker-J][AMQP 1.0] Fix symbolic descriptor for 'no local filter'


> [Broker-J] Incorrect symbolic descriptor used for no-local filter
> -
>
> Key: QPID-8115
> URL: https://issues.apache.org/jira/browse/QPID-8115
> Project: Qpid
>  Issue Type: Task
>  Components: Broker-J
>Affects Versions: qpid-java-broker-7.0.2, qpid-java-broker-7.0.0, 
> qpid-java-broker-7.0.1
>Reporter: Alex Rudyy
>Priority: Major
>
> [apache.org amp specification extension for 
> filters|http://www.amqp.org/specification/1.0/filters] declares {{no local 
> filter}} with symbolic descriptor {{apache.org:no-local-filter:list}}. The 
> Broker-J uses incorrect symbolic descriptor 
> {{"apache.org:jms-no-local-filter:list"}}.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Commented] (QPID-8083) [REST] Refactor REST system test suite

2018-02-28 Thread ASF subversion and git services (JIRA)


[ 
https://issues.apache.org/jira/browse/QPID-8083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16381010#comment-16381010
 ] 

ASF subversion and git services commented on QPID-8083:
---

Commit f50be6e3a1fc3a3405a0ce985a768523da25f6d8 in qpid-broker-j's branch 
refs/heads/master from [~alex.rufous]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-broker-j.git;h=f50be6e ]

QPID-8083: [System Tests] [REST/HTTP] Check whether sun.security API is 
available


> [REST] Refactor REST system test suite
> --
>
> Key: QPID-8083
> URL: https://issues.apache.org/jira/browse/QPID-8083
> Project: Qpid
>  Issue Type: Improvement
>  Components: Broker-J
>Reporter: Keith Wall
>Priority: Major
>
> REST is an orthogonal concern within the Broker.  It should be possible for 
> developers of the Broker to easily exclude REST tests from test runs whilst 
> developing other parts of the Broker.  To allow for this, the REST test suite 
> should be separate.
> Also many of the current tests are very repetitious in nature.  Currently 
> each model object is subjected to its own REST test merely testing that model 
> attributes are available over REST, pointlessly retesting the same piece of 
> common mechanism code over and over again.  Such tests should be eliminated.
> Tests that remain should focus on REST concerns such as:
>  * CRUD model access
>  * Model operations
>  * SASL and Preemptive Authentication
>  * Compression/Decompression
>  
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Updated] (QPID-8115) [Broker-J] Incorrect symbolic descriptor used for no-local filter

2018-02-28 Thread Alex Rudyy (JIRA)


 [ 
https://issues.apache.org/jira/browse/QPID-8115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alex Rudyy updated QPID-8115:
-
Status: Reviewable  (was: In Progress)

> [Broker-J] Incorrect symbolic descriptor used for no-local filter
> -
>
> Key: QPID-8115
> URL: https://issues.apache.org/jira/browse/QPID-8115
> Project: Qpid
>  Issue Type: Task
>  Components: Broker-J
>Affects Versions: qpid-java-broker-7.0.2, qpid-java-broker-7.0.0, 
> qpid-java-broker-7.0.1
>Reporter: Alex Rudyy
>Assignee: Alex Rudyy
>Priority: Major
>
> [apache.org amp specification extension for 
> filters|http://www.amqp.org/specification/1.0/filters] declares {{no local 
> filter}} with symbolic descriptor {{apache.org:no-local-filter:list}}. The 
> Broker-J uses incorrect symbolic descriptor 
> {{"apache.org:jms-no-local-filter:list"}}.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Created] (PROTON-1778) [ruby] support for user threads communicating with proton threads

2018-02-28 Thread Alan Conway (JIRA)

Alan Conway created PROTON-1778:
---

 Summary: [ruby] support for user threads communicating with proton 
threads
 Key: PROTON-1778
 URL: https://issues.apache.org/jira/browse/PROTON-1778
 Project: Qpid Proton
  Issue Type: Improvement
  Components: ruby-binding
Affects Versions: proton-c-0.21.0
Reporter: Alan Conway
Assignee: Alan Conway
 Fix For: proton-c-0.22.0


Ruby needs a way to queue data from user threads to be handled in proton 
threads. This is essentially a standard ruby thread-safe Queue that wakes up 
the proton poller as required to service the queues. Similar to the work_queue 
mechanism in C++ or the inject() mechanism in the go binding.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[GitHub] qpid-dispatch pull request #263: DISPATCH-933 - Created new RouterStats enti...

2018-02-28 Thread ganeshmurthy

GitHub user ganeshmurthy opened a pull request:

https://github.com/apache/qpid-dispatch/pull/263

DISPATCH-933 - Created new RouterStats entity. Moved some attributes â¦

â¦from Router entity to RouterStats. Router entity is not handled by the 
Python management agent and the RouterStats entity is handled by the C 
management agent

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/ganeshmurthy/qpid-dispatch DISPATCH-933

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/qpid-dispatch/pull/263.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #263


commit 14339b3339f5ebbd57eb6e5e55204b16771b969f
Author: Ganesh Murthy 
Date:   2018-02-28T18:58:10Z

DISPATCH-933 - Created new RouterStats entity. Moved some attributes from 
Router entity to RouterStats. Router entity is not handled by the Python 
management agent and the RouterStats entity is handled by the C management agent




---

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Commented] (DISPATCH-933) Introduce a new RouterStats entity and move all stats from the RouterEntity to the RouterStats entity

2018-02-28 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/DISPATCH-933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16380999#comment-16380999
 ] 

ASF GitHub Bot commented on DISPATCH-933:
-

GitHub user ganeshmurthy opened a pull request:

https://github.com/apache/qpid-dispatch/pull/263

DISPATCH-933 - Created new RouterStats entity. Moved some attributes …

…from Router entity to RouterStats. Router entity is not handled by the 
Python management agent and the RouterStats entity is handled by the C 
management agent

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/ganeshmurthy/qpid-dispatch DISPATCH-933

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/qpid-dispatch/pull/263.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #263


commit 14339b3339f5ebbd57eb6e5e55204b16771b969f
Author: Ganesh Murthy 
Date:   2018-02-28T18:58:10Z

DISPATCH-933 - Created new RouterStats entity. Moved some attributes from 
Router entity to RouterStats. Router entity is not handled by the Python 
management agent and the RouterStats entity is handled by the C management agent




> Introduce a new RouterStats entity and move all stats from the RouterEntity 
> to the RouterStats entity
> -
>
> Key: DISPATCH-933
> URL: https://issues.apache.org/jira/browse/DISPATCH-933
> Project: Qpid Dispatch
>  Issue Type: Bug
>  Components: Management Agent
>Affects Versions: 1.0.1
>Reporter: Ganesh Murthy
>Assignee: Ganesh Murthy
>Priority: Major
> Fix For: 1.2.0
>
>
> Right now all router statistics attributes like deliveriesIngress, 
> rejectedDeliveries, droppedPresettledDeliveries etc. reside in the router 
> entity..
>  
> Router Config Attributes  like saslConfigPath, saslConfigName, 
> helloIntervalSeconds, helloMaxAgeSeconds etc. also reside in the router entity
>  
> When a qdmanage query is issued, the results do not include the router config 
> attributes. This is because the core does not have access to these attributes
>  
> {noformat}
> [gmurthy@localhost qpid-dispatch]$ qdmanage QUERY --type=router
> [
>   {
>     "linkRouteCount": 0,
>     "droppedPresettledDeliveries": 0,
>     "rejectedDeliveries": 0,
>     "autoLinkCount": 0,
>     "id": "Router.A",
>     "presettledDeliveries": 0,
>     "area": "0",
>     "deliveriesIngress": 1,
>     "deliveriesIngressRouteContainer": 0,
>     "acceptedDeliveries": 1,
>     "version": "1.0.0",
>     "linkCount": 2,
>     "connectionCount": 1,
>     "addrCount": 4,
>     "deliveriesEgressRouteContainer": 0,
>     "nodeCount": 0,
>     "modifiedDeliveries": 0,
>     "identity": "1",
>     "deliveriesEgress": 0,
>     "releasedDeliveries": 0,
>     "name": "Router.A",
>     "type": "org.apache.qpid.dispatch.router",
>     "deliveriesTransit": 0,
>     "mode": "standalone"
>   }
> ]
> {noformat}
>  
> The solution to this problem is to create a new entity called RouterStats and 
> move all the statistics related attributes to RouterStats. This RouterStats 
> entity will be handled by the C management agent.
>  
> The old Router entity which is currently handled by the C agent will be 
> handled by the Python agent instead.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Updated] (QPIDIT-85) Tests don't limit the number of times it tries to connect to a broker

2018-02-28 Thread Kim van der Riet (JIRA)


 [ 
https://issues.apache.org/jira/browse/QPIDIT-85?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Kim van der Riet updated QPIDIT-85:
---
Fix Version/s: 0.2.0

> Tests don't limit the number of times it tries to connect to a broker
> -
>
> Key: QPIDIT-85
> URL: https://issues.apache.org/jira/browse/QPIDIT-85
> Project: Apache QPID Interoperability Test Suite
>  Issue Type: Bug
>Affects Versions: 0.1.0
>Reporter: Kim van der Riet
>Assignee: Kim van der Riet
>Priority: Minor
> Fix For: 0.2.0
>
>
> When no broker is present, or when a misconfiguration prevents communication 
> to the broker, then the test keeps attempting to connect without time or 
> number limit:
> {noformat}
> ERROR:root:proton:io: recv: Connection refused
> ERROR:root:proton:io: recv: Connection refused
> ERROR:root:proton:io: recv: Connection refused
> ERROR:root:proton:io: recv: Connection refused
> ...
> {noformat}
> and will keep trying indefinitely, effectively hanging the test.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Assigned] (QPIDIT-104) Add test for JMS shared subscriptions

2018-02-28 Thread Kim van der Riet (JIRA)


 [ 
https://issues.apache.org/jira/browse/QPIDIT-104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Kim van der Riet reassigned QPIDIT-104:
---

Assignee: Kim van der Riet

> Add test for JMS shared subscriptions
> -
>
> Key: QPIDIT-104
> URL: https://issues.apache.org/jira/browse/QPIDIT-104
> Project: Apache QPID Interoperability Test Suite
>  Issue Type: New Feature
>Affects Versions: 0.1.0
>Reporter: Kim van der Riet
>Assignee: Kim van der Riet
>Priority: Minor
>
> JMS 2.0 allows for shared subscriptions. These are supported in the Artemis 
> and ActiveMQ brokers, and in the Qpid-jms client.
> Add a test which will check interoperability for the JMS client vs other 
> clients (C++ and Python to start with).



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Commented] (QPIDIT-89) Detecting failed shims without elapsing full timeout

2018-02-28 Thread Kim van der Riet (JIRA)


[ 
https://issues.apache.org/jira/browse/QPIDIT-89?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16381142#comment-16381142
 ] 

Kim van der Riet commented on QPIDIT-89:


Recent changes for QPIDIT-79 should solve this. Both shims are started, but if 
the sender shim fails, this is detected and the receiver shim is terminated. 
This will work so long as the shims fail with an error message on stderr, and 
don't just hang. Hung shims will always wait the full timeout before being 
terminated. See QPIDIT-37 for recent changes to the timeout of tests.

I hope this answers this issue. Will leave open for a while for additional 
comments.

> Detecting failed shims without elapsing full timeout
> 
>
> Key: QPIDIT-89
> URL: https://issues.apache.org/jira/browse/QPIDIT-89
> Project: Apache QPID Interoperability Test Suite
>  Issue Type: Bug
>Affects Versions: 0.1.0
>Reporter: Chuck Rolke
>Assignee: Kim van der Riet
>Priority: Minor
>
> If a test has a sender that throws but a receiver that does not then the test 
> may elapse the full timeout period before failing.
> What are the rules for a sender throwing an exception so that it is seen by 
> the test runner?



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Created] (QPIDIT-116) Change unit test behavior so that Ctrl+C will stop the test gracefully and report on test already run

2018-02-28 Thread Kim van der Riet (JIRA)

Kim van der Riet created QPIDIT-116:
---

 Summary: Change unit test behavior so that Ctrl+C will stop the 
test gracefully and report on test already run
 Key: QPIDIT-116
 URL: https://issues.apache.org/jira/browse/QPIDIT-116
 Project: Apache QPID Interoperability Test Suite
  Issue Type: Improvement
Affects Versions: 0.1.0
Reporter: Kim van der Riet
Assignee: Kim van der Riet


Currently, using Ctrl+C on a running test causes it to immediately terminate. 
However, none of the tests already run are reported on, and any errors or 
failures seen up to the point of being terminated are lost.

There is a mechanism in Python's test framework which allows a signal (SIGINT 
in this case) to be caught in such a way that instead of simply terminating, 
the remaining tests are skipped. This will allow the tests already run to be 
reported.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Updated] (QPIDIT-113) AMQP.NetLite shims produce error message on stderr which should be ignored

2018-02-28 Thread Kim van der Riet (JIRA)


 [ 
https://issues.apache.org/jira/browse/QPIDIT-113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Kim van der Riet updated QPIDIT-113:

Fix Version/s: 0.2.0

> AMQP.NetLite shims produce error message on stderr which should be ignored
> --
>
> Key: QPIDIT-113
> URL: https://issues.apache.org/jira/browse/QPIDIT-113
> Project: Apache QPID Interoperability Test Suite
>  Issue Type: Bug
>  Components: .Net Lite Shim
>Affects Versions: 0.1.0
>Reporter: Kim van der Riet
>Assignee: Kim van der Riet
>Priority: Major
> Fix For: 0.2.0
>
>
> While running the AMQP .NetLite shims on CentOS7, the shims produce a single 
> instance of the following error message on stderr:
> {noformat}
> Got a bad hardware address length for an AF_PACKET 20 8{noformat}
> As the tests treat _any_ text on stderr as an error condition, the tests 
> fail. In fact the shims are behaving normally in every other way and complete 
> the tests normally.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Updated] (QPIDIT-114) [AMQP.NetLite] AMQP char type is not supported, but is not excluded from test

2018-02-28 Thread Kim van der Riet (JIRA)


 [ 
https://issues.apache.org/jira/browse/QPIDIT-114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Kim van der Riet updated QPIDIT-114:

Fix Version/s: 0.2.0

> [AMQP.NetLite] AMQP char type is not supported, but is not excluded from test
> -
>
> Key: QPIDIT-114
> URL: https://issues.apache.org/jira/browse/QPIDIT-114
> Project: Apache QPID Interoperability Test Suite
>  Issue Type: Bug
>  Components: .Net Lite Shim, AMQP Types Test
>Affects Versions: 0.1.0
>Reporter: Kim van der Riet
>Assignee: Kim van der Riet
>Priority: Major
> Fix For: 0.2.0
>
>
> When the amqp_types_test is run against the ActiveMQ broker (which can handle 
> AMQP type char, unlike several other brokers), the tests of AMQP type 
> {{char}} fail with an error message from the AMQP.NetLite shims:
> {noformat}
> System.ApplicationException: Sender can not encode base type: char{noformat}
> As a mechanism exists in each test to exclude AMQP types based on the client 
> being run, this should be added.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Commented] (QPIDJMS-364) qpid-jms-client - May hide ClassNotFoundException when setting properties via FactoryFinder

2018-02-28 Thread ASF subversion and git services (JIRA)


[ 
https://issues.apache.org/jira/browse/QPIDJMS-364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16381080#comment-16381080
 ] 

ASF subversion and git services commented on QPIDJMS-364:
-

Commit 7e7cebe50579bc897923599668f2a7ab8067c9a2 in qpid-jms's branch 
refs/heads/master from [~tabish121]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-jms.git;h=7e7cebe ]

QPIDJMS-364 Refactor to present Class not found errors to surface

Allow for class not found for proton resources to surface if jar is
missing or old version is used.

> qpid-jms-client - May hide ClassNotFoundException when setting properties via 
> FactoryFinder
> ---
>
> Key: QPIDJMS-364
> URL: https://issues.apache.org/jira/browse/QPIDJMS-364
> Project: Qpid JMS
>  Issue Type: Improvement
>  Components: qpid-jms-client
>Affects Versions: 0.29.0
>Reporter: Claus Ibsen
>Assignee: Timothy Bish
>Priority: Minor
> Fix For: 0.30.0
>
> Attachments: Screen Shot 2018-02-28 at 09.52.46.png
>
>
> I had a problem in an Apache Camel AMQP example that would not work. It 
> turned out that it was a classpath issues with a missing JAR.
> However the real error I got was hidden as the qpid-jms-client catches a 
> Throwable and ignores the exception.
> See the attached screenshot, and notice the exception about 
> NoClassDefFoundException



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Resolved] (QPIDJMS-364) qpid-jms-client - May hide ClassNotFoundException when setting properties via FactoryFinder

2018-02-28 Thread Timothy Bish (JIRA)


 [ 
https://issues.apache.org/jira/browse/QPIDJMS-364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Timothy Bish resolved QPIDJMS-364.
--
   Resolution: Fixed
Fix Version/s: 0.30.0

> qpid-jms-client - May hide ClassNotFoundException when setting properties via 
> FactoryFinder
> ---
>
> Key: QPIDJMS-364
> URL: https://issues.apache.org/jira/browse/QPIDJMS-364
> Project: Qpid JMS
>  Issue Type: Improvement
>  Components: qpid-jms-client
>Affects Versions: 0.29.0
>Reporter: Claus Ibsen
>Assignee: Timothy Bish
>Priority: Minor
> Fix For: 0.30.0
>
> Attachments: Screen Shot 2018-02-28 at 09.52.46.png
>
>
> I had a problem in an Apache Camel AMQP example that would not work. It 
> turned out that it was a classpath issues with a missing JAR.
> However the real error I got was hidden as the qpid-jms-client catches a 
> Throwable and ignores the exception.
> See the attached screenshot, and notice the exception about 
> NoClassDefFoundException



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Updated] (QPIDIT-100) Check status of broker between tests

2018-02-28 Thread Kim van der Riet (JIRA)


 [ 
https://issues.apache.org/jira/browse/QPIDIT-100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Kim van der Riet updated QPIDIT-100:

Fix Version/s: 0.2.0

> Check status of broker between tests
> 
>
> Key: QPIDIT-100
> URL: https://issues.apache.org/jira/browse/QPIDIT-100
> Project: Apache QPID Interoperability Test Suite
>  Issue Type: Improvement
>Affects Versions: 0.1.0
>Reporter: Kim van der Riet
>Assignee: Kim van der Riet
>Priority: Minor
> Fix For: 0.2.0
>
>
> If the broker should stop during a test, the test will continue to try to run 
> all of the tests.  A check should be made between each test that will ensure 
> the broker is still present. Perhaps a check of the PID will suffice.
> Note that for some broker configurations (such as multi-node dispatch router 
> tests), multiple nodes and/or brokers may be present, and all of them must be 
> checked.
> If one or more of the test nodes is missing, the test should immediately 
> terminate with an error message.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Created] (QPIDIT-115) Print both stderr and stdout output when stderr output is detected on a shim

2018-02-28 Thread Kim van der Riet (JIRA)

Kim van der Riet created QPIDIT-115:
---

 Summary: Print both stderr and stdout output when stderr output is 
detected on a shim
 Key: QPIDIT-115
 URL: https://issues.apache.org/jira/browse/QPIDIT-115
 Project: Apache QPID Interoperability Test Suite
  Issue Type: Improvement
Reporter: Kim van der Riet


The AMQP.NetLite shims sometimes produce spurious error messages on stderr that 
can be ignored (see QPIDIT-113). Fixing this highlighted the fact that when 
stderr output exists, any output on stdout is ignored. If a shim should produce 
messages on stderr, it would be useful to also see any stdout output (if it 
exists).



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Updated] (QPIDIT-111) Optimize jms_hdrs_props_test by combining messages containing the test values into a single test with several messages

2018-02-28 Thread Kim van der Riet (JIRA)


 [ 
https://issues.apache.org/jira/browse/QPIDIT-111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Kim van der Riet updated QPIDIT-111:

Affects Version/s: 0.1.0

> Optimize jms_hdrs_props_test by combining messages containing the test values 
> into a single test with several messages
> --
>
> Key: QPIDIT-111
> URL: https://issues.apache.org/jira/browse/QPIDIT-111
> Project: Apache QPID Interoperability Test Suite
>  Issue Type: Improvement
>Affects Versions: 0.1.0
>Reporter: Kim van der Riet
>Assignee: Kim van der Riet
>Priority: Major
>
> Currently jms_hdrs_props_test is a long test with many test cases. This is 
> true in part because each test value used for the headers and properties is 
> being sent as a separate test.
> Rather find a way to send several messages each containing a different value 
> for the headers and/or properties. This will involve a little refactoring as 
> the current shim interface allows several messages with different body values 
> to be sent with the same set of headers and/or properties, but this is not 
> useful for this test case.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Updated] (QPIDIT-108) [C++ shim] Update use of Json::Reader and Json::FastWriter which are deprecated

2018-02-28 Thread Kim van der Riet (JIRA)


 [ 
https://issues.apache.org/jira/browse/QPIDIT-108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Kim van der Riet updated QPIDIT-108:

Affects Version/s: 0.1.0

> [C++ shim] Update use of Json::Reader and Json::FastWriter which are 
> deprecated
> ---
>
> Key: QPIDIT-108
> URL: https://issues.apache.org/jira/browse/QPIDIT-108
> Project: Apache QPID Interoperability Test Suite
>  Issue Type: Task
>Affects Versions: 0.1.0
>Reporter: Kim van der Riet
>Assignee: Kim van der Riet
>Priority: Major
>
> Recent versions of Fedora are warning that use of {{Json::Reader}} and 
> {{Json::FastWriter}} are now deprecated. Check that whatever replaces this 
> will at a minimum run on RHEL7 / CentOS7.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Assigned] (QPIDIT-115) Print both stderr and stdout output when stderr output is detected on a shim

2018-02-28 Thread Kim van der Riet (JIRA)


 [ 
https://issues.apache.org/jira/browse/QPIDIT-115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Kim van der Riet reassigned QPIDIT-115:
---

Assignee: Kim van der Riet

> Print both stderr and stdout output when stderr output is detected on a shim
> 
>
> Key: QPIDIT-115
> URL: https://issues.apache.org/jira/browse/QPIDIT-115
> Project: Apache QPID Interoperability Test Suite
>  Issue Type: Improvement
>Reporter: Kim van der Riet
>Assignee: Kim van der Riet
>Priority: Major
>
> The AMQP.NetLite shims sometimes produce spurious error messages on stderr 
> that can be ignored (see QPIDIT-113). Fixing this highlighted the fact that 
> when stderr output exists, any output on stdout is ignored. If a shim should 
> produce messages on stderr, it would be useful to also see any stdout output 
> (if it exists).



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Updated] (QPIDIT-115) Print both stderr and stdout output when stderr output is detected on a shim

2018-02-28 Thread Kim van der Riet (JIRA)


 [ 
https://issues.apache.org/jira/browse/QPIDIT-115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Kim van der Riet updated QPIDIT-115:

Affects Version/s: 0.1.0

> Print both stderr and stdout output when stderr output is detected on a shim
> 
>
> Key: QPIDIT-115
> URL: https://issues.apache.org/jira/browse/QPIDIT-115
> Project: Apache QPID Interoperability Test Suite
>  Issue Type: Improvement
>Affects Versions: 0.1.0
>Reporter: Kim van der Riet
>Assignee: Kim van der Riet
>Priority: Major
>
> The AMQP.NetLite shims sometimes produce spurious error messages on stderr 
> that can be ignored (see QPIDIT-113). Fixing this highlighted the fact that 
> when stderr output exists, any output on stdout is ignored. If a shim should 
> produce messages on stderr, it would be useful to also see any stdout output 
> (if it exists).



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Commented] (QPID-8113) [Broker-J] Incorrect symbolic descriptor used for (JMS) selector

2018-02-28 Thread ASF subversion and git services (JIRA)


[ 
https://issues.apache.org/jira/browse/QPID-8113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16380323#comment-16380323
 ] 

ASF subversion and git services commented on QPID-8113:
---

Commit 8dd9bd6cc25d2672d6353e8021986597918ed312 in qpid-broker-j's branch 
refs/heads/master from [~godfrer]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-broker-j.git;h=8dd9bd6 ]

QPID-8113 : Incorrect symbolic descriptor used for (JMS) selector filter


> [Broker-J] Incorrect symbolic descriptor used for (JMS) selector
> 
>
> Key: QPID-8113
> URL: https://issues.apache.org/jira/browse/QPID-8113
> Project: Qpid
>  Issue Type: Bug
>  Components: Broker-J
>Affects Versions: qpid-java-broker-7.0.2, qpid-java-broker-7.0.0, 
> qpid-java-broker-7.0.1
>Reporter: Rob Godfrey
>Assignee: Rob Godfrey
>Priority: Major
>
> As per 
> [this|http://mail-archives.apache.org/mod_mbox/qpid-users/201802.mbox/%3CCACsaS95BJjm8e09xZGEPkp_Wsq801sdLd0fVnR9Tqy-JwJWnhg%40mail.gmail.com%3E]
>  message, the symbolic descriptor for JMS-style selector parsing is 
> incorrectly defined within Broker-J



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Updated] (QPID-8114) [Broker-J] Attempting to use an unknown filter type incorrectly causes connection closure with a decode error

2018-02-28 Thread Rob Godfrey (JIRA)


 [ 
https://issues.apache.org/jira/browse/QPID-8114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Rob Godfrey updated QPID-8114:
--
Description: 
As discovered in QPID-8113 if a client attempts to attach to a source using an 
unknown filter type (i.e. an unrecognised descriptor) the broker responds with 
a decode error similar to 

{{[0x555941994670]:0 <- @close(24) [error=@error(29) 
[condition=:"amqp:decode-error", description="Expected key type is 'Filter' but 
got 'DescribedType'"]]}}

Instead the broker should simply fail to attach (i.e. attach with source=null) 
and then immediately detach with a {{not-implemented}} error.

  was:
As discovered in QPID-8113 if a client attempts to attach to a source using an 
unknown filter type (i.e. an unrecognised descriptor) the broker responds with 
a decode error similar to 

{{[0x555941994670]:0 <- @close(24) [error=@error(29) 
[condition=:"amqp:decode-error", description="Expected key type is 'Filter' but 
got 'DescribedType'"]]
}}

Instead the broker should simply fail to attach (i.e. attach with source=null) 
and then immediately detach with a {{not-implemented}} error.


> [Broker-J] Attempting to use an unknown filter type incorrectly causes 
> connection closure with a decode error
> -
>
> Key: QPID-8114
> URL: https://issues.apache.org/jira/browse/QPID-8114
> Project: Qpid
>  Issue Type: Bug
>  Components: Broker-J
>Reporter: Rob Godfrey
>Priority: Major
>
> As discovered in QPID-8113 if a client attempts to attach to a source using 
> an unknown filter type (i.e. an unrecognised descriptor) the broker responds 
> with a decode error similar to 
> {{[0x555941994670]:0 <- @close(24) [error=@error(29) 
> [condition=:"amqp:decode-error", description="Expected key type is 'Filter' 
> but got 'DescribedType'"]]}}
> Instead the broker should simply fail to attach (i.e. attach with 
> source=null) and then immediately detach with a {{not-implemented}} error.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[GitHub] qpid-dispatch pull request #253: Enhanced link-statistics

2018-02-28 Thread asfgit

Github user asfgit closed the pull request at:

https://github.com/apache/qpid-dispatch/pull/253


---

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Created] (QPID-8114) [Broker-J] Attempting to use an unknown filter type incorrectly causes connection closure with a decode error

2018-02-28 Thread Rob Godfrey (JIRA)

Rob Godfrey created QPID-8114:
-

 Summary: [Broker-J] Attempting to use an unknown filter type 
incorrectly causes connection closure with a decode error
 Key: QPID-8114
 URL: https://issues.apache.org/jira/browse/QPID-8114
 Project: Qpid
  Issue Type: Bug
  Components: Broker-J
Reporter: Rob Godfrey


As discovered in QPID-8113 if a client attempts to attach to a source using an 
unknown filter type (i.e. an unrecognised descriptor) the broker responds with 
a decode error similar to 

{{[0x555941994670]:0 <- @close(24) [error=@error(29) 
[condition=:"amqp:decode-error", description="Expected key type is 'Filter' but 
got 'DescribedType'"]]
}}

Instead the broker should simply fail to attach (i.e. attach with source=null) 
and then immediately detach with a {{not-implemented}} error.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[GitHub] qpid-dispatch issue #262: Crolke 918 vhost hostname

2018-02-28 Thread ChugR

Github user ChugR commented on the issue:

https://github.com/apache/qpid-dispatch/pull/262
  
Close this PR and create a new one using @ganeshmurthy deprecationName


---

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[GitHub] qpid-dispatch pull request #262: Crolke 918 vhost hostname

2018-02-28 Thread ChugR

Github user ChugR closed the pull request at:

https://github.com/apache/qpid-dispatch/pull/262


---

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Created] (QPID-8113) [Broker-J] Incorrect symbolic descriptor used for (JMS) selector

2018-02-28 Thread Rob Godfrey (JIRA)

Rob Godfrey created QPID-8113:
-

 Summary: [Broker-J] Incorrect symbolic descriptor used for (JMS) 
selector
 Key: QPID-8113
 URL: https://issues.apache.org/jira/browse/QPID-8113
 Project: Qpid
  Issue Type: Bug
  Components: Broker-J
Affects Versions: qpid-java-broker-7.0.1, qpid-java-broker-7.0.0, 
qpid-java-broker-7.0.2
Reporter: Rob Godfrey
Assignee: Rob Godfrey


As per 
[this|http://mail-archives.apache.org/mod_mbox/qpid-users/201802.mbox/%3CCACsaS95BJjm8e09xZGEPkp_Wsq801sdLd0fVnR9Tqy-JwJWnhg%40mail.gmail.com%3E]
 message, the symbolic descriptor for JMS-style selector parsing is incorrectly 
defined within Broker-J



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Created] (DISPATCH-932) Provide per-ingress router counts for deliveries on egress links

2018-02-28 Thread Ted Ross (JIRA)

Ted Ross created DISPATCH-932:
-

 Summary: Provide per-ingress router counts for deliveries on 
egress links
 Key: DISPATCH-932
 URL: https://issues.apache.org/jira/browse/DISPATCH-932
 Project: Qpid Dispatch
  Issue Type: New Feature
  Components: Management Agent
Reporter: Ted Ross
Assignee: Ted Ross
 Fix For: 1.1.0


Provide a new attribute for managed links.  The attribute is an array of 
counters, one per router, that counts the deliveries that entered the network 
on a particular router.

This new attribute is called 'ingressHistogram'.  It is only present on 
outgoing links on connections with the 'normal' role.

This histogram can be used to identify patterns of traffic flow by where 
deliveries enter and where the exit.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Commented] (DISPATCH-932) Provide per-ingress router counts for deliveries on egress links

2018-02-28 Thread ASF subversion and git services (JIRA)


[ 
https://issues.apache.org/jira/browse/DISPATCH-932?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16380339#comment-16380339
 ] 

ASF subversion and git services commented on DISPATCH-932:
--

Commit 1134dbae47db0801062a3991553ab07a36b0a861 in qpid-dispatch's branch 
refs/heads/master from [~tr...@redhat.com]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-dispatch.git;h=1134dba ]

DISPATCH-932 - Added counts to correlate the ingress and egress routers of 
deliveries.
This closes #253


> Provide per-ingress router counts for deliveries on egress links
> 
>
> Key: DISPATCH-932
> URL: https://issues.apache.org/jira/browse/DISPATCH-932
> Project: Qpid Dispatch
>  Issue Type: New Feature
>  Components: Management Agent
>Reporter: Ted Ross
>Assignee: Ted Ross
>Priority: Minor
> Fix For: 1.1.0
>
>
> Provide a new attribute for managed links.  The attribute is an array of 
> counters, one per router, that counts the deliveries that entered the network 
> on a particular router.
> This new attribute is called 'ingressHistogram'.  It is only present on 
> outgoing links on connections with the 'normal' role.
> This histogram can be used to identify patterns of traffic flow by where 
> deliveries enter and where the exit.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Resolved] (DISPATCH-932) Provide per-ingress router counts for deliveries on egress links

2018-02-28 Thread Ted Ross (JIRA)


 [ 
https://issues.apache.org/jira/browse/DISPATCH-932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ted Ross resolved DISPATCH-932.
---
Resolution: Fixed

> Provide per-ingress router counts for deliveries on egress links
> 
>
> Key: DISPATCH-932
> URL: https://issues.apache.org/jira/browse/DISPATCH-932
> Project: Qpid Dispatch
>  Issue Type: New Feature
>  Components: Management Agent
>Reporter: Ted Ross
>Assignee: Ted Ross
>Priority: Minor
> Fix For: 1.1.0
>
>
> Provide a new attribute for managed links.  The attribute is an array of 
> counters, one per router, that counts the deliveries that entered the network 
> on a particular router.
> This new attribute is called 'ingressHistogram'.  It is only present on 
> outgoing links on connections with the 'normal' role.
> This histogram can be used to identify patterns of traffic flow by where 
> deliveries enter and where the exit.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Commented] (QPIDJMS-364) qpid-jms-client - May hide ClassNotFoundException when setting properties via FactoryFinder

2018-02-28 Thread Claus Ibsen (JIRA)


[ 
https://issues.apache.org/jira/browse/QPIDJMS-364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16379989#comment-16379989
 ] 

Claus Ibsen commented on QPIDJMS-364:
-

The error you see is

qpid Provider scheme NOT recognized: [amqp]

> qpid-jms-client - May hide ClassNotFoundException when setting properties via 
> FactoryFinder
> ---
>
> Key: QPIDJMS-364
> URL: https://issues.apache.org/jira/browse/QPIDJMS-364
> Project: Qpid JMS
>  Issue Type: Improvement
>  Components: qpid-jms-client
>Affects Versions: 0.29.0
>Reporter: Claus Ibsen
>Priority: Minor
> Attachments: Screen Shot 2018-02-28 at 09.52.46.png
>
>
> I had a problem in an Apache Camel AMQP example that would not work. It 
> turned out that it was a classpath issues with a missing JAR.
> However the real error I got was hidden as the qpid-jms-client catches a 
> Throwable and ignores the exception.
> See the attached screenshot, and notice the exception about 
> NoClassDefFoundException



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Created] (QPIDJMS-364) qpid-jms-client - May hide ClassNotFoundException when setting properties via FactoryFinder

2018-02-28 Thread Claus Ibsen (JIRA)

Claus Ibsen created QPIDJMS-364:
---

 Summary: qpid-jms-client - May hide ClassNotFoundException when 
setting properties via FactoryFinder
 Key: QPIDJMS-364
 URL: https://issues.apache.org/jira/browse/QPIDJMS-364
 Project: Qpid JMS
  Issue Type: Improvement
  Components: qpid-jms-client
Affects Versions: 0.29.0
Reporter: Claus Ibsen
 Attachments: Screen Shot 2018-02-28 at 09.52.46.png

I had a problem in an Apache Camel AMQP example that would not work. It turned 
out that it was a classpath issues with a missing JAR.

However the real error I got was hidden as the qpid-jms-client catches a 
Throwable and ignores the exception.

See the attached screenshot, and notice the exception about 
NoClassDefFoundException



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Updated] (QPIDJMS-364) qpid-jms-client - May hide ClassNotFoundException when setting properties via FactoryFinder

2018-02-28 Thread Claus Ibsen (JIRA)


 [ 
https://issues.apache.org/jira/browse/QPIDJMS-364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Claus Ibsen updated QPIDJMS-364:

Attachment: Screen Shot 2018-02-28 at 09.52.46.png

> qpid-jms-client - May hide ClassNotFoundException when setting properties via 
> FactoryFinder
> ---
>
> Key: QPIDJMS-364
> URL: https://issues.apache.org/jira/browse/QPIDJMS-364
> Project: Qpid JMS
>  Issue Type: Improvement
>  Components: qpid-jms-client
>Affects Versions: 0.29.0
>Reporter: Claus Ibsen
>Priority: Minor
> Attachments: Screen Shot 2018-02-28 at 09.52.46.png
>
>
> I had a problem in an Apache Camel AMQP example that would not work. It 
> turned out that it was a classpath issues with a missing JAR.
> However the real error I got was hidden as the qpid-jms-client catches a 
> Throwable and ignores the exception.
> See the attached screenshot, and notice the exception about 
> NoClassDefFoundException



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Reopened] (DISPATCH-921) Install console dependencies with npm during make install

2018-02-28 Thread Ted Ross (JIRA)


 [ 
https://issues.apache.org/jira/browse/DISPATCH-921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ted Ross reopened DISPATCH-921:
---

I propose that we change this behavior such that the "make install" action 
copies the appropriate contents of the console(s) to a "dist" directory.  Usage 
of npm should be manual.

If npm is automatically invoked on "make install" as it is now, downstream 
packaging systems will have a problem maintaining a reproducible build.  This 
is going to be a problem for downstream distros.

 

> Install console dependencies with npm during make install
> -
>
> Key: DISPATCH-921
> URL: https://issues.apache.org/jira/browse/DISPATCH-921
> Project: Qpid Dispatch
>  Issue Type: Improvement
>  Components: Console
>Affects Versions: 1.0.0
>Reporter: Ernest Allen
>Assignee: Ernest Allen
>Priority: Major
> Fix For: 1.1.0
>
>
> During a make install, the stand-alone console's dependencies should be 
> installed using the command 'npm install' executed from the console's install 
> directory.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Commented] (DISPATCH-209) Three+ router test is needed in the system test suite.

2018-02-28 Thread ASF subversion and git services (JIRA)


[ 
https://issues.apache.org/jira/browse/DISPATCH-209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16380665#comment-16380665
 ] 

ASF subversion and git services commented on DISPATCH-209:
--

Commit 2a5633c431c1769ba45eb7d42a714e24c8f70ece in qpid-dispatch's branch 
refs/heads/master from [~mgoulish]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-dispatch.git;h=2a5633c ]

DISPATCH-209 : additive topology tests


> Three+ router test is needed in the system test suite.
> --
>
> Key: DISPATCH-209
> URL: https://issues.apache.org/jira/browse/DISPATCH-209
> Project: Qpid Dispatch
>  Issue Type: Improvement
>  Components: Tests
>Reporter: Ted Ross
>Assignee: michael goulish
>Priority: Major
> Fix For: 1.0.0
>
>
> There have arisen some issues that would have been caught had there been a 
> three-router test in the regression suite.  This test should be added.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Created] (DISPATCH-933) Introduce a new RouterStats entity and move all stats from the RouterEntity to the RouterStats entity

2018-02-28 Thread Ganesh Murthy (JIRA)

Ganesh Murthy created DISPATCH-933:
--

 Summary: Introduce a new RouterStats entity and move all stats 
from the RouterEntity to the RouterStats entity
 Key: DISPATCH-933
 URL: https://issues.apache.org/jira/browse/DISPATCH-933
 Project: Qpid Dispatch
  Issue Type: Bug
  Components: Management Agent
Affects Versions: 1.0.1
Reporter: Ganesh Murthy
Assignee: Ganesh Murthy
 Fix For: 1.2.0


Right now all router statistics attributes like deliveriesIngress, 
rejectedDeliveries, droppedPresettledDeliveries etc. reside in the router 
entity..

 

Router Config Attributes  like saslConfigPath, saslConfigName, 
helloIntervalSeconds, helloMaxAgeSeconds etc. also reside in the router entity

 

When a qdmanage query is issued, the results do not include the router config 
attributes. This is because the core does not have access to these attributes

 
{noformat}

[gmurthy@localhost qpid-dispatch]$ qdmanage QUERY --type=router
[
  {
    "linkRouteCount": 0,
    "droppedPresettledDeliveries": 0,
    "rejectedDeliveries": 0,
    "autoLinkCount": 0,
    "id": "Router.A",
    "presettledDeliveries": 0,
    "area": "0",
    "deliveriesIngress": 1,
    "deliveriesIngressRouteContainer": 0,
    "acceptedDeliveries": 1,
    "version": "1.0.0",
    "linkCount": 2,
    "connectionCount": 1,
    "addrCount": 4,
    "deliveriesEgressRouteContainer": 0,
    "nodeCount": 0,
    "modifiedDeliveries": 0,
    "identity": "1",
    "deliveriesEgress": 0,
    "releasedDeliveries": 0,
    "name": "Router.A",
    "type": "org.apache.qpid.dispatch.router",
    "deliveriesTransit": 0,
    "mode": "standalone"
  }
]
{noformat}
 

The solution to this problem is to create a new entity called RouterStats and 
move all the statistics related attributes to RouterStats. This RouterStats 
entity will be handled by the C management agent.

 

The old Router entity which is currently handled by the C agent will be handled 
by the Python agent instead.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Created] (QPIDIT-113) AMQP.NetLite shims produce error message on stderr which should be ignored

2018-02-28 Thread Kim van der Riet (JIRA)

Kim van der Riet created QPIDIT-113:
---

 Summary: AMQP.NetLite shims produce error message on stderr which 
should be ignored
 Key: QPIDIT-113
 URL: https://issues.apache.org/jira/browse/QPIDIT-113
 Project: Apache QPID Interoperability Test Suite
  Issue Type: Bug
  Components: .Net Lite Shim
Affects Versions: 0.1.0
Reporter: Kim van der Riet
Assignee: Kim van der Riet


While running the AMQP .NetLite shims on CentOS7, the shims produce a single 
instance of the following error message on stderr:
{noformat}
Got a bad hardware address length for an AF_PACKET 20 8{noformat}
As the tests treat _any_ text on stderr as an error condition, the tests fail. 
In fact the shims are behaving normally in every other way and complete the 
tests normally.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Commented] (QPIDIT-113) AMQP.NetLite shims produce error message on stderr which should be ignored

2018-02-28 Thread ASF subversion and git services (JIRA)


[ 
https://issues.apache.org/jira/browse/QPIDIT-113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16380741#comment-16380741
 ] 

ASF subversion and git services commented on QPIDIT-113:


Commit f92c5ad4758e8e290783a7c1f070524c94384a91 in qpid-interop-test's branch 
refs/heads/master from [~kpvdr]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-interop-test.git;h=f92c5ad ]

QPIDIT-113: Workaround which ignores spurious error message from AMQP.NetLite 
on stderr


> AMQP.NetLite shims produce error message on stderr which should be ignored
> --
>
> Key: QPIDIT-113
> URL: https://issues.apache.org/jira/browse/QPIDIT-113
> Project: Apache QPID Interoperability Test Suite
>  Issue Type: Bug
>  Components: .Net Lite Shim
>Affects Versions: 0.1.0
>Reporter: Kim van der Riet
>Assignee: Kim van der Riet
>Priority: Major
>
> While running the AMQP .NetLite shims on CentOS7, the shims produce a single 
> instance of the following error message on stderr:
> {noformat}
> Got a bad hardware address length for an AF_PACKET 20 8{noformat}
> As the tests treat _any_ text on stderr as an error condition, the tests 
> fail. In fact the shims are behaving normally in every other way and complete 
> the tests normally.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Assigned] (QPIDJMS-364) qpid-jms-client - May hide ClassNotFoundException when setting properties via FactoryFinder

2018-02-28 Thread Timothy Bish (JIRA)


 [ 
https://issues.apache.org/jira/browse/QPIDJMS-364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Timothy Bish reassigned QPIDJMS-364:


Assignee: Timothy Bish

> qpid-jms-client - May hide ClassNotFoundException when setting properties via 
> FactoryFinder
> ---
>
> Key: QPIDJMS-364
> URL: https://issues.apache.org/jira/browse/QPIDJMS-364
> Project: Qpid JMS
>  Issue Type: Improvement
>  Components: qpid-jms-client
>Affects Versions: 0.29.0
>Reporter: Claus Ibsen
>Assignee: Timothy Bish
>Priority: Minor
> Attachments: Screen Shot 2018-02-28 at 09.52.46.png
>
>
> I had a problem in an Apache Camel AMQP example that would not work. It 
> turned out that it was a classpath issues with a missing JAR.
> However the real error I got was hidden as the qpid-jms-client catches a 
> Throwable and ignores the exception.
> See the attached screenshot, and notice the exception about 
> NoClassDefFoundException



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

54 matches

Mail list logo