[jira] [Commented] (DISPATCH-8) Message:user-id must be authenticated on ingress

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on DISPATCH-8:


Commit 6be6e461040808ec9aed75b3213a2f03496a510b in qpid-dispatch's branch 
refs/heads/master from [~chug]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-dispatch.git;h=6be6e46 ]

DISPATCH-8: Authenticate message user-id on ingress

Add proxy check enable setting per vhost user group.
Verify proxy is allowed for incoming messages.
Add self tests to demonstrate proxy check rejecting messages or not.


> Message:user-id must be authenticated on ingress
> 
>
> Key: DISPATCH-8
> URL: https://issues.apache.org/jira/browse/DISPATCH-8
> Project: Qpid Dispatch
>  Issue Type: Bug
>Affects Versions: 0.1
>Reporter: Ted Ross
>Assignee: Chuck Rolke
>Priority: Critical
> Fix For: 0.7.0
>
>
> When a message is received on an ingress link (i.e. from an originating 
> endpoint) and the message has a user-id field in its properties, that user-id 
> must be authenticated.
> At first, this means that the user-id must be the same as that which was used 
> to authenticate the connection.
> There may be other means of authenticating user-ids in the future, but 
> Dispatch must not simply pass them on unchecked.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[jira] [Commented] (QPIDJMS-207) Implement the JMS 2.0 API

[ASF subversion and git services (JIRA)]

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

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

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

QPIDJMS-207 Add tests to validate Exception handling paths

> Implement the JMS 2.0 API
> -
>
> Key: QPIDJMS-207
> URL: https://issues.apache.org/jira/browse/QPIDJMS-207
> Project: Qpid JMS
>  Issue Type: New Feature
>  Components: qpid-jms-client
>Affects Versions: 0.11.0
>Reporter: Timothy Bish
>Assignee: Timothy Bish
> Fix For: 0.20.0
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[jira] [Commented] (QPIDJMS-207) Implement the JMS 2.0 API

[ASF subversion and git services (JIRA)]

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

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

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

QPIDJMS-207 Add additional tests for exception handlers

Test that the session handles throwing the right error on use of invalid
temporary destination values. 

> Implement the JMS 2.0 API
> -
>
> Key: QPIDJMS-207
> URL: https://issues.apache.org/jira/browse/QPIDJMS-207
> Project: Qpid JMS
>  Issue Type: New Feature
>  Components: qpid-jms-client
>Affects Versions: 0.11.0
>Reporter: Timothy Bish
>Assignee: Timothy Bish
> Fix For: 0.20.0
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[jira] [Commented] (QPIDJMS-207) Implement the JMS 2.0 API

[ASF subversion and git services (JIRA)]

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

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

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

QPIDJMS-207 Test for the JMSConsumer implementation

Tests that the JMSConsumer implementation passes most calls through to
the underlying consumer and that the methods convert to valid
JMSRuntimeException instances. 

> Implement the JMS 2.0 API
> -
>
> Key: QPIDJMS-207
> URL: https://issues.apache.org/jira/browse/QPIDJMS-207
> Project: Qpid JMS
>  Issue Type: New Feature
>  Components: qpid-jms-client
>Affects Versions: 0.11.0
>Reporter: Timothy Bish
>Assignee: Timothy Bish
> Fix For: 0.20.0
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[jira] [Commented] (PROTON-1303) Don't use the proton-c url parser

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on PROTON-1303:


Github user alanconway commented on the issue:

https://github.com/apache/qpid-proton/pull/81
  
You're right, godoc takes a host:port  not a URL. Ship It.


> Don't use the proton-c url parser
> -
>
> Key: PROTON-1303
> URL: https://issues.apache.org/jira/browse/PROTON-1303
> Project: Qpid Proton
>  Issue Type: Improvement
>  Components: go-binding
>Reporter: Andrew Stitcher
>Assignee: Andrew Stitcher
>
> Go has it's own standard url parser - it doesn't need to use the rather odd 
> and somewhat error prone parser in proton-c.
> It will be useful to provide some ability to set appropriate defaults for 
> supplied amqp urls though.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[GitHub] qpid-proton issue #81: PROTON-1303: Replace go binding URL parser with versi...

[alanconway]

Github user alanconway commented on the issue:

https://github.com/apache/qpid-proton/pull/81
  
You're right, godoc takes a host:port  not a URL. Ship It.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

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

[jira] [Assigned] (DISPATCH-440) Use the placeholder HTML attribute to communicate default values in the Connect form

[Ernest Allen (JIRA)]

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

Ernest Allen reassigned DISPATCH-440:
-

Assignee: Ernest Allen

> Use the placeholder HTML attribute to communicate default values in the 
> Connect form
> 
>
> Key: DISPATCH-440
> URL: https://issues.apache.org/jira/browse/DISPATCH-440
> Project: Qpid Dispatch
>  Issue Type: Improvement
>  Components: Console
>Affects Versions: 0.6.1
>Reporter: Jiri Danek
>Assignee: Ernest Allen
>Priority: Minor
> Fix For: 0.7.0
>
> Attachments: placeholder.png
>
>
> Default value for the Port field can be communicated to the user with the 
> help of the placeholder HTML attribute.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[jira] [Resolved] (DISPATCH-515) Add example config file for auto starting webbroxy

[Ernest Allen (JIRA)]

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

Ernest Allen resolved DISPATCH-515.
---
   Resolution: Fixed
Fix Version/s: 0.7.0

> Add example config file for auto starting webbroxy
> --
>
> Key: DISPATCH-515
> URL: https://issues.apache.org/jira/browse/DISPATCH-515
> Project: Qpid Dispatch
>  Issue Type: Improvement
>  Components: Console
>Reporter: Ernest Allen
>Assignee: Ernest Allen
> Fix For: 0.7.0
>
>
> Create a router config file illustrates how to start a websockets proxy with 
> the router. 
> Store this config under the tests/ directory.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[jira] [Commented] (DISPATCH-515) Add example config file for auto starting webbroxy

[ASF subversion and git services (JIRA)]

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

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

Commit 39b349a3633ab168eafaf16bcd9666cc7af22d82 in qpid-dispatch's branch 
refs/heads/master from [~eallen]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-dispatch.git;h=39b349a ]

DISPATCH-515 Added example config file to automatically start websockets proxy


> Add example config file for auto starting webbroxy
> --
>
> Key: DISPATCH-515
> URL: https://issues.apache.org/jira/browse/DISPATCH-515
> Project: Qpid Dispatch
>  Issue Type: Improvement
>  Components: Console
>Reporter: Ernest Allen
>Assignee: Ernest Allen
>
> Create a router config file illustrates how to start a websockets proxy with 
> the router. 
> Store this config under the tests/ directory.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[GitHub] qpid-jms issue #4: Provide OSGi metadata for qpid-jms-client

[ctron]

Github user ctron commented on the issue:

https://github.com/apache/qpid-jms/pull/4
  
Sure. I will do that tomorrow. Thanks for that quick review.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

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

[jira] [Updated] (QPID-7408) REST API streams compressed message content without a Content-Encoding header

[Alex Rudyy (JIRA)]

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

Alex Rudyy updated QPID-7408:
-
Attachment: 0001-QPID-7408-Extend-gunzip-output-stream-from-InflaterO.patch

> REST API streams compressed message content without a Content-Encoding header
> -
>
> Key: QPID-7408
> URL: https://issues.apache.org/jira/browse/QPID-7408
> Project: Qpid
>  Issue Type: Bug
>  Components: Java Broker
>Affects Versions: 0.30, 0.32, qpid-java-6.0, qpid-java-6.1
>Reporter: Keith Wall
>Assignee: Keith Wall
>Priority: Minor
> Fix For: qpid-java-6.1
>
> Attachments: 
> 0001-QPID-7408-Extend-gunzip-output-stream-from-InflaterO.patch, 
> new-compression-tests.diff
>
>
> The Broker for Java supports compressed messages.  If I view a compressed 
> message through the management console, the Broker sends the content to the 
> client without a {{Content-Encoding}} header, so the client treats the bytes 
> as if they were uncompressed.  If the message's mime type is {{text/*}}, I 
> see seeming garbage instead of the inlined text content.  If the message's 
> mime type is something else the browser handles the content as if it were 
> uncompressed.  This could confused applications associated with the Browser.
> This could potentially hinder an operator.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[jira] [Created] (DISPATCH-515) Add example config file for auto starting webbroxy

[Ernest Allen (JIRA)]

Ernest Allen created DISPATCH-515:
-

 Summary: Add example config file for auto starting webbroxy
 Key: DISPATCH-515
 URL: https://issues.apache.org/jira/browse/DISPATCH-515
 Project: Qpid Dispatch
  Issue Type: Improvement
  Components: Console
Reporter: Ernest Allen
Assignee: Ernest Allen


Create a router config file illustrates how to start a websockets proxy with 
the router. 

Store this config under the tests/ directory.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[GitHub] qpid-jms issue #4: Provide OSGi metadata for qpid-jms-client

[gemmellr]

Github user gemmellr commented on the issue:

https://github.com/apache/qpid-jms/pull/4
  
Thanks Jens,

The resultant manifest looks to allow for any Netty 4 version, but I 
believe there are some incompatible changes in Netty 4.1.x already so changing 
to allow only 4.0.x would be good. Similarly, its probably wise to restrict 
proton-j to 0.14.x currently as well. If you could also add the JIRA ID 
(QPIDJMS 164, with a - inbetween) to the start of your commit message that will 
associate them and cause a comment on the JIRA with the details when merged. 
Feel free to squash the changes.

In future if creating a PR, if you include the JIRA key in the title then 
the PR will be associated too (doesn't work when updating though so no need 
this time).

Robbie


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

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

[GitHub] qpid-jms pull request #4: Provide OSGi metadata for qpid-jms-client

[ctron]

GitHub user ctron opened a pull request:

https://github.com/apache/qpid-jms/pull/4

Provide OSGi metadata for qpid-jms-client

This change adds the maven-bundle-plugin to the parent project and
activates it in the qpid-jms-client project, generating OSGi meta data
for the project.

The Bundle-SymbolicName is overridden to "org.apache.qpid.jms.client".

The DynamicPackage-Import header is set to "*" since the JMS client can
actually create instances from all kind of classes.

The final MANIFEST.MF no longer contains the following entries though:

```
Implementation-Title: QpidJMS Client
Implementation-Version: 0.20.0-SNAPSHOT
Implementation-Vendor-Id: org.apache.qpid
Implementation-Vendor: The Apache Software Foundation
Specification-Vendor: The Apache Software Foundation
Specification-Title: QpidJMS Client
Specification-Version: 0.20.0-SNAPSHOT
```

Signed-off-by: Jens Reimann 

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

$ git pull https://github.com/ctron/qpid-jms feature/osgi_1

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

https://github.com/apache/qpid-jms/pull/4.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 #4


commit 721cd6db4c9a138b0f9578869a1f3d1d718119b0
Author: Jens Reimann 
Date:   2016-09-19T15:30:28Z

Provide OSGi metadata for qpid-jms-client

This change adds the maven-bundle-plugin to the parent project and
activates it in the qpid-jms-client project, generating OSGi meta data
for the project.

The Bundle-SymbolicName is overridden to "org.apache.qpid.jms.client".

The DynamicPackage-Import header is set to "*" since the JMS client can
actually create instances from all kind of classes.

Signed-off-by: Jens Reimann 




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

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

[jira] [Updated] (DISPATCH-103) Websocket Listeners

[Ted Ross (JIRA)]

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

Ted Ross updated DISPATCH-103:
--
Fix Version/s: (was: 0.7.0)

> Websocket Listeners
> ---
>
> Key: DISPATCH-103
> URL: https://issues.apache.org/jira/browse/DISPATCH-103
> Project: Qpid Dispatch
>  Issue Type: New Feature
>  Components: Container
>Reporter: Ted Ross
>Priority: Minor
>
> Add an option in configured listeners to use websockets encapsulation.  This 
> will allow AMQP clients inside web browsers to directly connect to the 
> message bus.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[jira] [Commented] (QPID-7408) REST API streams compressed message content without a Content-Encoding header

[Keith Wall (JIRA)]

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

Keith Wall commented on QPID-7408:
--

As discussed, I see now this is trickier than it appeared to me.  The fact that 
the API of {{GzipInputStream#read}} has no way to tell you that it hasn't 
received sufficient bytes yet to produce uncompressed output means that 
implementing a GunzipOutputStream in terms of GzipInputStream is not possible.  
 Your implementation relies on your *special* 
org.apache.qpid.server.management.plugin.GZIPOutputStreamAdapter.BufferInputStream#read(byte[],
 int, int)  to return -1  when there are *currently* no more bytes and the fact 
that java.util.zip.InflaterInputStream#fill() encountering a -1 happens to 
leave the java.util.zip.InflaterInputStream in a valid state for further 
reading.  I don't think these are good foundations.

I think we have no choice but implement a GunzipOutputStream in terms of 
Inflater.  As you suggest, we can use Apache Commons Compression as a guide.

> REST API streams compressed message content without a Content-Encoding header
> -
>
> Key: QPID-7408
> URL: https://issues.apache.org/jira/browse/QPID-7408
> Project: Qpid
>  Issue Type: Bug
>  Components: Java Broker
>Affects Versions: 0.30, 0.32, qpid-java-6.0, qpid-java-6.1
>Reporter: Keith Wall
>Assignee: Keith Wall
>Priority: Minor
> Fix For: qpid-java-6.1
>
> Attachments: new-compression-tests.diff
>
>
> The Broker for Java supports compressed messages.  If I view a compressed 
> message through the management console, the Broker sends the content to the 
> client without a {{Content-Encoding}} header, so the client treats the bytes 
> as if they were uncompressed.  If the message's mime type is {{text/*}}, I 
> see seeming garbage instead of the inlined text content.  If the message's 
> mime type is something else the browser handles the content as if it were 
> uncompressed.  This could confused applications associated with the Browser.
> This could potentially hinder an operator.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[jira] [Resolved] (QPID-7382) Message dialogue tries to inline the text of a text message content regardless of the its length

[Alex Rudyy (JIRA)]

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

Alex Rudyy resolved QPID-7382.
--
Resolution: Fixed

The changes look good to me

> Message dialogue tries to inline the text of a text message content 
> regardless of the its length
> 
>
> Key: QPID-7382
> URL: https://issues.apache.org/jira/browse/QPID-7382
> Project: Qpid
>  Issue Type: Bug
>  Components: Java Broker
>Affects Versions: 0.30, 0.32, qpid-java-6.0
>Reporter: Keith Wall
>Assignee: Lorenz Quack
> Fix For: qpid-java-6.0.5, qpid-java-6.1
>
> Attachments: suggested-changes.diff
>
>
> When viewing a message through the WMC, if the message's mime type indicates 
> that the content it text, the message dialogue tries to inline the content, 
> properly escaping the content first.  If the content is very large, this 
> approach is problematic and can cause formatting problems with buttons out of 
> reach, or at worst an unresponsive or crashed client side UI.
> The WMC should display the leading portion of a long text message using 
> ellipses and offer a download button to retrieve the full text content.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[jira] [Commented] (QPID-7422) [Java Tests] Make test timeouts configurable via system properties

[Alex Rudyy (JIRA)]

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

Alex Rudyy commented on QPID-7422:
--

Keith,
Your review comments are addressed in commit under revision [ 
https://svn.apache.org/r1761411 ]

> [Java Tests] Make test timeouts configurable via system properties
> --
>
> Key: QPID-7422
> URL: https://issues.apache.org/jira/browse/QPID-7422
> Project: Qpid
>  Issue Type: Bug
>  Components: Java Tests
>Reporter: Alex Rudyy
>Assignee: Keith Wall
> Fix For: qpid-java-6.1
>
>
> A number of tests have failed on slow environments due to time spent on 
> operations exceeded the expected time hard-coded in the tests.
> Here is the list of the tests and their timeouts which have failed recently 
> doe to bad environment performance:
> *  BDBHAVirtualHostNodeTest.testCreateAndActivateVirtualHostNode (failed due 
> to exceeding of waiting interval for node to became Master/Replica)
> * DBHAVirtualHostNodeTest.testNodeCannotStartWithIntruder (failed due to 
> exceeding of waiting interval for node to became Master/Replica)
> * SortedQueueTest.testReleaseForQueueWithMultipleConsumers (failed due to 
> exceeding of AbstractQueueTestBase.queueRunnerWaitTime as it is cannot be 
> overridden on runtime)
> * TimeToLiveTest.testPassiveTTLWithPrefetch, 
> TimeToLiveTest.testPassiveTTLwithDurableSubscription, 
> TimeToLiveTest.testPassiveTT (failed due to exceeding of receive interval of 
> 5000ms)
> The timeouts should be overriddable via run-time system properties



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[jira] [Commented] (QPID-7422) [Java Tests] Make test timeouts configurable via system properties

[ASF subversion and git services (JIRA)]

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

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

Commit 1761411 from oru...@apache.org in branch 'java/trunk'
[ https://svn.apache.org/r1761411 ]

QPID-7422: [Java Tests] Get test configurable timeouts in test setUp

> [Java Tests] Make test timeouts configurable via system properties
> --
>
> Key: QPID-7422
> URL: https://issues.apache.org/jira/browse/QPID-7422
> Project: Qpid
>  Issue Type: Bug
>  Components: Java Tests
>Reporter: Alex Rudyy
>Assignee: Keith Wall
> Fix For: qpid-java-6.1
>
>
> A number of tests have failed on slow environments due to time spent on 
> operations exceeded the expected time hard-coded in the tests.
> Here is the list of the tests and their timeouts which have failed recently 
> doe to bad environment performance:
> *  BDBHAVirtualHostNodeTest.testCreateAndActivateVirtualHostNode (failed due 
> to exceeding of waiting interval for node to became Master/Replica)
> * DBHAVirtualHostNodeTest.testNodeCannotStartWithIntruder (failed due to 
> exceeding of waiting interval for node to became Master/Replica)
> * SortedQueueTest.testReleaseForQueueWithMultipleConsumers (failed due to 
> exceeding of AbstractQueueTestBase.queueRunnerWaitTime as it is cannot be 
> overridden on runtime)
> * TimeToLiveTest.testPassiveTTLWithPrefetch, 
> TimeToLiveTest.testPassiveTTLwithDurableSubscription, 
> TimeToLiveTest.testPassiveTT (failed due to exceeding of receive interval of 
> 5000ms)
> The timeouts should be overriddable via run-time system properties



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[jira] [Assigned] (QPID-7409) Support preview of maps/list message content

[Alex Rudyy (JIRA)]

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

Alex Rudyy reassigned QPID-7409:


Assignee: Keith Wall  (was: Alex Rudyy)

> Support preview of maps/list message content
> 
>
> Key: QPID-7409
> URL: https://issues.apache.org/jira/browse/QPID-7409
> Project: Qpid
>  Issue Type: Improvement
>Reporter: Keith Wall
>Assignee: Keith Wall
> Fix For: qpid-java-6.1
>
> Attachments: 
> 0001-QPID-7409-WIP-add-support-for-getting-of-message-con.patch
>
>
> When viewing messages through the web management console, if the message is 
> of type such as a list or map currently the user sees the bytes of the 
> underlying AMQP datastructure.  Instead, the preview area should display the 
> data in a human friendly way.
> The managed operation {{Queue#getMessageContent}} will be enhanced to be 
> capable of returning a message in JSON format if possible with an optional 
> parameter {{returnJson}}.  If rather than returning the message's content 
> bytes directly, it should first convert the message to an {{InternalMessage}} 
> (MessageConverterRegistry.getConverter(serverMessage.getClass, 
> InternalMessage.class).convert(...)) then use the JSON serialiser to serial 
> the MessageBody of the resulting internal message.
> Within the WMC, if the resulting object is of a previewable type (string, 
> map, list etc) and the content is not too long, the content should be added 
> to a scrollable preview pane of the message dialogue by traversing the object 
> tree and producing a human readable representation of its structure and 
> content.  (Perhaps an approach such as 
> https://stackoverflow.com/questions/13341373/render-arbitrary-json-in-html 
> will help)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[jira] [Assigned] (QPID-7408) REST API streams compressed message content without a Content-Encoding header

[Alex Rudyy (JIRA)]

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

Alex Rudyy reassigned QPID-7408:


Assignee: Keith Wall  (was: Lorenz Quack)

Keith,
I implemented GZIPOutputStreamAdapter as you suggested and committed the 
changes in the revision [https://svn.apache.org/r1761399]

> REST API streams compressed message content without a Content-Encoding header
> -
>
> Key: QPID-7408
> URL: https://issues.apache.org/jira/browse/QPID-7408
> Project: Qpid
>  Issue Type: Bug
>  Components: Java Broker
>Affects Versions: 0.30, 0.32, qpid-java-6.0, qpid-java-6.1
>Reporter: Keith Wall
>Assignee: Keith Wall
>Priority: Minor
> Fix For: qpid-java-6.1
>
> Attachments: new-compression-tests.diff
>
>
> The Broker for Java supports compressed messages.  If I view a compressed 
> message through the management console, the Broker sends the content to the 
> client without a {{Content-Encoding}} header, so the client treats the bytes 
> as if they were uncompressed.  If the message's mime type is {{text/*}}, I 
> see seeming garbage instead of the inlined text content.  If the message's 
> mime type is something else the browser handles the content as if it were 
> uncompressed.  This could confused applications associated with the Browser.
> This could potentially hinder an operator.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[jira] [Commented] (QPID-7408) REST API streams compressed message content without a Content-Encoding header

[ASF subversion and git services (JIRA)]

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

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

Commit 1761399 from oru...@apache.org in branch 'java/trunk'
[ https://svn.apache.org/r1761399 ]

QPID-7408: Address review comments

> REST API streams compressed message content without a Content-Encoding header
> -
>
> Key: QPID-7408
> URL: https://issues.apache.org/jira/browse/QPID-7408
> Project: Qpid
>  Issue Type: Bug
>  Components: Java Broker
>Affects Versions: 0.30, 0.32, qpid-java-6.0, qpid-java-6.1
>Reporter: Keith Wall
>Assignee: Lorenz Quack
>Priority: Minor
> Fix For: qpid-java-6.1
>
> Attachments: new-compression-tests.diff
>
>
> The Broker for Java supports compressed messages.  If I view a compressed 
> message through the management console, the Broker sends the content to the 
> client without a {{Content-Encoding}} header, so the client treats the bytes 
> as if they were uncompressed.  If the message's mime type is {{text/*}}, I 
> see seeming garbage instead of the inlined text content.  If the message's 
> mime type is something else the browser handles the content as if it were 
> uncompressed.  This could confused applications associated with the Browser.
> This could potentially hinder an operator.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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