date:20160413

Re: Proton 0.12.2 release

2016-04-13 Thread Robbie Gemmell

Hi Frank,

That isn't one I can be much help with, being proton-c and Messenger,
neither of which I'm much use with. If someone looks at it in time,
great, but it seems more likely it won't squeeze into 0.12.2 at this
point. I was really just calling for any previously-committed bug
fixes folks wanted to have considered ahead of 0.13.0 (due later in
the month).

As an aside, it might be useful (but also might not..) if you put up
protocol trace logs of a run showing the issue you are seeing
(environment variable PN_TRACE_FRM=1 for proton-c, I think).

Robbie

On 13 April 2016 at 17:02, Frank Quinn  wrote:
> Hi Robbie,
>
> Would appreciate if someone could take a look at this one:
> https://issues.apache.org/jira/browse/PROTON-1169
>
> Cheers,
> Frank
>
> On Wed, Apr 13, 2016 at 3:11 PM, Robbie Gemmell 
> wrote:
>
>> Hi folks,
>>
>> I'd like to do a 0.12.2 release to incorporate a proton-j fix for
>> https://issues.apache.org/jira/browse/PROTON-1171. If all goes well
>> with feedback on that change I would propose to spin a release
>> candidate in the next day or so.
>>
>> If you have any targetted bug fixes you would like to include ahead of
>> the imminent 0.13.0 release cycle, now would be the time to think
>> about it.
>>
>> Robbie
>>

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

[jira] [Commented] (DISPATCH-237) Dispatch Router overwrites delivery tag for link-routed deliveries

2016-04-13 Thread ASF subversion and git services (JIRA)


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

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

Commit d8afd516a6de954ca9f827049891fd8464f2eca4 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=d8afd51 ]

DISPATCH-237 - Updated core handling of delivery tags to support link-routing.


> Dispatch Router overwrites delivery tag for link-routed deliveries
> --
>
> Key: DISPATCH-237
> URL: https://issues.apache.org/jira/browse/DISPATCH-237
> Project: Qpid Dispatch
>  Issue Type: Bug
>  Components: Router Node
>Affects Versions: 0.5
>Reporter: Ted Ross
>Assignee: Ted Ross
> Fix For: 0.6
>
>
> Dispatch Router overwrites the delivery tags for messages that flow along 
> routed links.  The original delivery tags need to be preserved for link 
> routes.



--
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] [Closed] (DISPATCH-221) Initial release of hawtio console plugin

2016-04-13 Thread Ernest Allen (JIRA)


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

Ernest Allen closed DISPATCH-221.
-
Resolution: Duplicate

Duplicate of DISPATCH-201

> Initial release of hawtio console plugin
> 
>
> Key: DISPATCH-221
> URL: https://issues.apache.org/jira/browse/DISPATCH-221
> Project: Qpid Dispatch
>  Issue Type: Improvement
>  Components: Console
>Affects Versions: 0.6
>Reporter: Ernest Allen
>Assignee: Ernest Allen
>
> Check in the code for the hawtio plugin. It should be checked in under the 
> qpid-dispatch/console 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] [Resolved] (DISPATCH-217) Make the UI more consistant with other hawtio plugins

2016-04-13 Thread Ernest Allen (JIRA)


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

Ernest Allen resolved DISPATCH-217.
---
   Resolution: Fixed
Fix Version/s: 0.6

This was fixed in a commit for the DISPATCH-201 Jira.

> Make the UI more consistant with other hawtio plugins 
> --
>
> Key: DISPATCH-217
> URL: https://issues.apache.org/jira/browse/DISPATCH-217
> Project: Qpid Dispatch
>  Issue Type: Improvement
>  Components: Console
>Affects Versions: 0.6
>Reporter: Ernest Allen
>Assignee: Ernest Allen
>Priority: Minor
> Fix For: 0.6
>
>
> Make the UI consistant with other hawtio plugins. This includes the following 
> subtasks:
> 1. Use the hawtio dashboard for saving charts
> 2. Allow the charts to be resized
> 3. Rearrange the List page
> 3a. Use a dynatree on a resizable panel on the left to display entities 
> and attribute names.
> 3b. Rename the page to 'Attributes'
> 3c. Move that page before Topology



--
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-271) Handle single router

2016-04-13 Thread Ernest Allen (JIRA)


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

Ernest Allen resolved DISPATCH-271.
---
   Resolution: Fixed
Fix Version/s: 0.6

> Handle single router
> 
>
> Key: DISPATCH-271
> URL: https://issues.apache.org/jira/browse/DISPATCH-271
> Project: Qpid Dispatch
>  Issue Type: Bug
>  Components: Console
>Affects Versions: 0.6
>Reporter: Ernest Allen
>Assignee: Ernest Allen
> Fix For: 0.6
>
>
> When the is only one router (stand-alone) the GET-MGMT-NODES call will return 
> an empty list. Since this is by design, the console should handle this case.
> When the call to GET-MGMT-NODES returns an empty list, the console should 
> QUERY the connected router to get its id.



--
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-271) Handle single router

2016-04-13 Thread ASF subversion and git services (JIRA)


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

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

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

DISPATCH-271 When GET-MGMT-NODES returns an empty list, use receiver's source 
address to derive the current router ID


> Handle single router
> 
>
> Key: DISPATCH-271
> URL: https://issues.apache.org/jira/browse/DISPATCH-271
> Project: Qpid Dispatch
>  Issue Type: Bug
>  Components: Console
>Affects Versions: 0.6
>Reporter: Ernest Allen
>Assignee: Ernest Allen
>
> When the is only one router (stand-alone) the GET-MGMT-NODES call will return 
> an empty list. Since this is by design, the console should handle this case.
> When the call to GET-MGMT-NODES returns an empty list, the console should 
> QUERY the connected router to get its id.



--
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

Re: Dropping proton-dump; Moving to newer minimum CMake version

2016-04-13 Thread Chuck Rolke

A multi-frame issues showed up at 
https://issues.apache.org/jira/browse/DISPATCH-263 and I think proton-dump was 
useful in figuring it out. 

Wireshark marked dozens of frames with decode errors. proton-dump[1] came to 
the rescue was able to grind through the packets without complaining. Problem 
analysis could immediately move beyond figuring out what's wrong with the data 
stream because it was fine.

I don't need to add proton-dump back into the source tree but I have it built 
and ready for the occasional need.

-Chuck

[1] proton-dump was opening the dump files in text mode and causing a confusing 
truncation error. If you plan to use proton-dump you should apply this:

diff --git a/proton-c/src/proton-dump.c b/proton-c/src/proton-dump.c
index 1ce577d..f0718ac 100644
--- a/proton-c/src/proton-dump.c
+++ b/proton-c/src/proton-dump.c
@@ -39,7 +39,7 @@ void fatal_error(const char *msg, const char *arg, int err)

 int dump(const char *file)
 {
-  FILE *in = fopen(file, "r");
+  FILE *in = fopen(file, "rb");
   if (!in) fatal_error("proton-dump: dump: opening %s", file, errno);

   pn_buffer_t *buf = pn_buffer(1024);

- Original Message -
> From: "Andrew Stitcher" 
> To: pro...@qpid.apache.org, "Qpid Developers" 
> Sent: Friday, February 19, 2016 10:04:40 AM
> Subject: Re: Dropping proton-dump; Moving to newer minimum CMake version
> 
> Well I left it 3 days, heard no objections so I will remove proton-dump
> and up the minimum version of cmake to 2.8.7.
> 
> Andrew
> 
> 

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

[jira] [Closed] (DISPATCH-215) The topology diagram initially draws off the bottom of the visible page.

2016-04-13 Thread Ernest Allen (JIRA)


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

Ernest Allen closed DISPATCH-215.
-
   Resolution: Fixed
Fix Version/s: 0.6

> The topology diagram initially draws off the bottom of the visible page.
> 
>
> Key: DISPATCH-215
> URL: https://issues.apache.org/jira/browse/DISPATCH-215
> Project: Qpid Dispatch
>  Issue Type: Bug
>  Components: Console
>Affects Versions: 0.6
>Reporter: Ernest Allen
>Assignee: Ernest Allen
> Fix For: 0.6
>
>
> The first time you display the toplogy page from a browser, the diagram is 
> drawn at the very bottom of the page. Well below what is visible. 
> To view the diagram, you need to scroll down and drag it up to the top of the 
> page.
> The diagram should initially display at the top of the page adjacent to the 
> Router/Connection details grid.



--
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-263) Router crash when requesting log

2016-04-13 Thread Ernest Allen (JIRA)


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

Ernest Allen commented on DISPATCH-263:
---

I concur. With the latest patches applied, I can no longer crash the router by 
requesting the log entries.

> Router crash when requesting log
> 
>
> Key: DISPATCH-263
> URL: https://issues.apache.org/jira/browse/DISPATCH-263
> Project: Qpid Dispatch
>  Issue Type: Bug
>  Components: Management Agent
>Affects Versions: 0.6
>Reporter: Ernest Allen
>Assignee: Ganesh Murthy
>Priority: Blocker
> Fix For: 0.6
>
>
> Router crashes when requesting latest log entries
> - Start 2 nodes from qpid-dispatch/tests/config-2
> - let routers run for about 5 minutes (problem does not occur unless I wait)
> - qdmanage GET-LOG -b 0.0.0.0:20100 -r QDR.B
> {quote}
> #0  0x76ba7a98 in __GI_raise (sig=sig@entry=6)
> at ../sysdeps/unix/sysv/linux/raise.c:55
> #1  0x76ba969a in __GI_abort () at abort.c:89
> #2  0x76ba0227 in __assert_fail_base (fmt=, 
> assertion=assertion@entry=0x77bcbaa8 "*((uint32_t*) (p + 
> desc->total_size)) == 0xbabecafe", 
> file=file@entry=0x77bcb880 
> "/home/eallen/workspace/qpid-dispatch/src/alloc_pool.c", line=line@entry=213, 
> function=function@entry=0x77bcbcc0 <__PRETTY_FUNCTION__.9429> 
> "qd_dealloc") at assert.c:92
> #3  0x76ba02d2 in __GI___assert_fail (
> assertion=0x77bcbaa8 "*((uint32_t*) (p + desc->total_size)) == 
> 0xbabecafe", 
> file=0x77bcb880 
> "/home/eallen/workspace/qpid-dispatch/src/alloc_pool.c", line=213, 
> function=0x77bcbcc0 <__PRETTY_FUNCTION__.9429> "qd_dealloc")
> at assert.c:101
> #4  0x77bc1cf0 in qd_dealloc (
> desc=0x77dd9fc0 <__desc_qdr_delivery_t>, tpool=0x7fffea9cc658, 
> p=0x7fffdc0092b0)
> at /home/eallen/workspace/qpid-dispatch/src/alloc_pool.c:213
> #5  0x77bb06f8 in free_qdr_delivery_t (p=0x7fffdc0092b0)
> at /home/eallen/workspace/qpid-dispatch/src/router_core/router_core.c:26
> ---Type  to continue, or q  to quit---
> #6  0x77bb6c54 in qdr_delivery_free (delivery=0x7fffdc0092b0)
> at /home/eallen/workspace/qpid-dispatch/src/router_core/transfer.c:207
> #7  0x77bb789f in qdr_update_delivery_CT (core=0x8cb5d0, 
> action=0x7fffd4003d00, discard=false)
> at /home/eallen/workspace/qpid-dispatch/src/router_core/transfer.c:499
> #8  0x77bb2799 in router_core_thread (arg=0x8cb5d0)
> at 
> /home/eallen/workspace/qpid-dispatch/src/router_core/router_core_thread.c:71
> #9  0x7771060a in start_thread (arg=0x7fffea9cc700)
> at pthread_create.c:334
> #10 0x76c75a4d in clone ()
> at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109
> {quote}



--
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-6983) [Web Management Console] Add UI support for queries

2016-04-13 Thread Alex Rudyy (JIRA)


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

Alex Rudyy commented on QPID-6983:
--

Remediation progress

1) -Tick a field within the Field popup and then click Cancel. Expected: tick 
forgotten, actual: tick retained.- (/)
2) -Remove the pagination options within Field/Condition popups. Keep the 
count.- (/)
3) -Remove the ‘not; from the list of options on the clause’s dropdown.- (/)
4) Removing a clause from a Condition closed the Condition popup. Expected: 
clause removed.
5) Categories should have a default set of fields (LATER)
6) -Rename Fields to Columns- (/)
7) -Conditions for attributes that have valid values should allow the user to 
choose multiple items (Requires QPID-7157)- (/)
8) Conditions for attributes that are Dates should use date/time picker 
(Requires QPID-7158)
9) -Select and where text fields are too short.- (/)
10) An advance search where the select part contained an expression failed
11) Ability to re-order columns (LATER)
12) -Columns were not properly reset when switching between standard/advanced- 
(/)
13) Add support for queries involving attributes that are not basic types (e.g 
Queue.alternativeExchange) (LATER)
14) Add support for queries involving attributes that are collections. (LATER)
15) User should be able to specify the page size (LATER)


> [Web Management Console] Add UI support for queries
> ---
>
> Key: QPID-6983
> URL: https://issues.apache.org/jira/browse/QPID-6983
> Project: Qpid
>  Issue Type: Improvement
>  Components: Java Broker
>Reporter: Keith Wall
>Assignee: Alex Rudyy
> Attachments: query-ui-prototype.tar.gz, query-ui-prototype.tar.gz
>
>
> Add the ability to the Web Management Console to submit queries (using the 
> feature added by QPID-6969) and view the results.  The results may need to be 
> paginated for display.



--
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-179) Refactor Router Core

2016-04-13 Thread ASF subversion and git services (JIRA)


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

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

Commit 8b1b7b979d1536b92c105f95e479a64cd87dd2db in qpid-dispatch's branch 
refs/heads/master from [~ganeshmurthy]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-dispatch.git;h=8b1b7b9 ]

DISPATCH-179 - Added some extra documentation for connectionRole


> Refactor Router Core
> 
>
> Key: DISPATCH-179
> URL: https://issues.apache.org/jira/browse/DISPATCH-179
> Project: Qpid Dispatch
>  Issue Type: Improvement
>  Components: Router Node
>Reporter: Ted Ross
>Assignee: Ted Ross
> Fix For: 0.6
>
>
> Refactor the core router function to clean up the architecture and to fix the 
> significant lock contention issue that exists in 0.5.



--
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-6983) [Web Management Console] Add UI support for queries

2016-04-13 Thread ASF subversion and git services (JIRA)


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

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

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

QPID-6983: Add ability to select multiple values for fields having validValues 
set

> [Web Management Console] Add UI support for queries
> ---
>
> Key: QPID-6983
> URL: https://issues.apache.org/jira/browse/QPID-6983
> Project: Qpid
>  Issue Type: Improvement
>  Components: Java Broker
>Reporter: Keith Wall
>Assignee: Alex Rudyy
> Attachments: query-ui-prototype.tar.gz, query-ui-prototype.tar.gz
>
>
> Add the ability to the Web Management Console to submit queries (using the 
> feature added by QPID-6969) and view the results.  The results may need to be 
> paginated for display.



--
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-263) Router crash when requesting log

2016-04-13 Thread Ganesh Murthy (JIRA)


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

Ganesh Murthy commented on DISPATCH-263:


After downloading Ted's fix, I ran Ernie's test and was unable to crash the 
router.

> Router crash when requesting log
> 
>
> Key: DISPATCH-263
> URL: https://issues.apache.org/jira/browse/DISPATCH-263
> Project: Qpid Dispatch
>  Issue Type: Bug
>  Components: Management Agent
>Affects Versions: 0.6
>Reporter: Ernest Allen
>Assignee: Ganesh Murthy
>Priority: Blocker
> Fix For: 0.6
>
>
> Router crashes when requesting latest log entries
> - Start 2 nodes from qpid-dispatch/tests/config-2
> - let routers run for about 5 minutes (problem does not occur unless I wait)
> - qdmanage GET-LOG -b 0.0.0.0:20100 -r QDR.B
> {quote}
> #0  0x76ba7a98 in __GI_raise (sig=sig@entry=6)
> at ../sysdeps/unix/sysv/linux/raise.c:55
> #1  0x76ba969a in __GI_abort () at abort.c:89
> #2  0x76ba0227 in __assert_fail_base (fmt=, 
> assertion=assertion@entry=0x77bcbaa8 "*((uint32_t*) (p + 
> desc->total_size)) == 0xbabecafe", 
> file=file@entry=0x77bcb880 
> "/home/eallen/workspace/qpid-dispatch/src/alloc_pool.c", line=line@entry=213, 
> function=function@entry=0x77bcbcc0 <__PRETTY_FUNCTION__.9429> 
> "qd_dealloc") at assert.c:92
> #3  0x76ba02d2 in __GI___assert_fail (
> assertion=0x77bcbaa8 "*((uint32_t*) (p + desc->total_size)) == 
> 0xbabecafe", 
> file=0x77bcb880 
> "/home/eallen/workspace/qpid-dispatch/src/alloc_pool.c", line=213, 
> function=0x77bcbcc0 <__PRETTY_FUNCTION__.9429> "qd_dealloc")
> at assert.c:101
> #4  0x77bc1cf0 in qd_dealloc (
> desc=0x77dd9fc0 <__desc_qdr_delivery_t>, tpool=0x7fffea9cc658, 
> p=0x7fffdc0092b0)
> at /home/eallen/workspace/qpid-dispatch/src/alloc_pool.c:213
> #5  0x77bb06f8 in free_qdr_delivery_t (p=0x7fffdc0092b0)
> at /home/eallen/workspace/qpid-dispatch/src/router_core/router_core.c:26
> ---Type  to continue, or q  to quit---
> #6  0x77bb6c54 in qdr_delivery_free (delivery=0x7fffdc0092b0)
> at /home/eallen/workspace/qpid-dispatch/src/router_core/transfer.c:207
> #7  0x77bb789f in qdr_update_delivery_CT (core=0x8cb5d0, 
> action=0x7fffd4003d00, discard=false)
> at /home/eallen/workspace/qpid-dispatch/src/router_core/transfer.c:499
> #8  0x77bb2799 in router_core_thread (arg=0x8cb5d0)
> at 
> /home/eallen/workspace/qpid-dispatch/src/router_core/router_core_thread.c:71
> #9  0x7771060a in start_thread (arg=0x7fffea9cc700)
> at pthread_create.c:334
> #10 0x76c75a4d in clone ()
> at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109
> {quote}



--
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-188) Dispatch needs a policy mechanism to limit user connections and activity

2016-04-13 Thread ASF subversion and git services (JIRA)


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

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

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

DISPATCH-188: Update policy documentation.


> Dispatch needs a policy mechanism to limit user connections and activity
> 
>
> Key: DISPATCH-188
> URL: https://issues.apache.org/jira/browse/DISPATCH-188
> Project: Qpid Dispatch
>  Issue Type: Improvement
>  Components: Container, Management Agent
>Affects Versions: 0.5
>Reporter: Chuck Rolke
>Assignee: Chuck Rolke
> Fix For: 0.6
>
>
> At a minimum this should support 
> * a framework for a Policy Authority external to Dispatch
> ** holds policy configuration
> ** provides policy allow/deny decisions at run time
> * connection approval/denial based on authorized user name
> * per-user connection count limits and grand total connection count limits
> * management interface to expose statistics and live connection state
> Further enhancements to connection limits should support
> * connections limited by
> ** user host IP
> ** Dispatch router name and port
> ** AMQP Open frame contents
> Further enhancements to policy should support
> * limits to link creation source and target address names
> * multitenancy



--
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

Re: Proton 0.12.2 release

2016-04-13 Thread Frank Quinn

Hi Robbie,

Would appreciate if someone could take a look at this one:
https://issues.apache.org/jira/browse/PROTON-1169

Cheers,
Frank

On Wed, Apr 13, 2016 at 3:11 PM, Robbie Gemmell 
wrote:

> Hi folks,
>
> I'd like to do a 0.12.2 release to incorporate a proton-j fix for
> https://issues.apache.org/jira/browse/PROTON-1171. If all goes well
> with feedback on that change I would propose to spin a release
> candidate in the next day or so.
>
> If you have any targetted bug fixes you would like to include ahead of
> the imminent 0.13.0 release cycle, now would be the time to think
> about it.
>
> Robbie
>

[jira] [Commented] (DISPATCH-263) Router crash when requesting log

2016-04-13 Thread ASF subversion and git services (JIRA)


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

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

Commit eee4fa29672d43865cb4c2e8d8cca75c793fac6a 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=eee4fa2 ]

DISPATCH-263 - Fixed again, with proper use of the pn_record facility and a 
test that runs multi-framed pre-settled deliveries.


> Router crash when requesting log
> 
>
> Key: DISPATCH-263
> URL: https://issues.apache.org/jira/browse/DISPATCH-263
> Project: Qpid Dispatch
>  Issue Type: Bug
>  Components: Management Agent
>Affects Versions: 0.6
>Reporter: Ernest Allen
>Assignee: Ganesh Murthy
>Priority: Blocker
> Fix For: 0.6
>
>
> Router crashes when requesting latest log entries
> - Start 2 nodes from qpid-dispatch/tests/config-2
> - let routers run for about 5 minutes (problem does not occur unless I wait)
> - qdmanage GET-LOG -b 0.0.0.0:20100 -r QDR.B
> {quote}
> #0  0x76ba7a98 in __GI_raise (sig=sig@entry=6)
> at ../sysdeps/unix/sysv/linux/raise.c:55
> #1  0x76ba969a in __GI_abort () at abort.c:89
> #2  0x76ba0227 in __assert_fail_base (fmt=, 
> assertion=assertion@entry=0x77bcbaa8 "*((uint32_t*) (p + 
> desc->total_size)) == 0xbabecafe", 
> file=file@entry=0x77bcb880 
> "/home/eallen/workspace/qpid-dispatch/src/alloc_pool.c", line=line@entry=213, 
> function=function@entry=0x77bcbcc0 <__PRETTY_FUNCTION__.9429> 
> "qd_dealloc") at assert.c:92
> #3  0x76ba02d2 in __GI___assert_fail (
> assertion=0x77bcbaa8 "*((uint32_t*) (p + desc->total_size)) == 
> 0xbabecafe", 
> file=0x77bcb880 
> "/home/eallen/workspace/qpid-dispatch/src/alloc_pool.c", line=213, 
> function=0x77bcbcc0 <__PRETTY_FUNCTION__.9429> "qd_dealloc")
> at assert.c:101
> #4  0x77bc1cf0 in qd_dealloc (
> desc=0x77dd9fc0 <__desc_qdr_delivery_t>, tpool=0x7fffea9cc658, 
> p=0x7fffdc0092b0)
> at /home/eallen/workspace/qpid-dispatch/src/alloc_pool.c:213
> #5  0x77bb06f8 in free_qdr_delivery_t (p=0x7fffdc0092b0)
> at /home/eallen/workspace/qpid-dispatch/src/router_core/router_core.c:26
> ---Type  to continue, or q  to quit---
> #6  0x77bb6c54 in qdr_delivery_free (delivery=0x7fffdc0092b0)
> at /home/eallen/workspace/qpid-dispatch/src/router_core/transfer.c:207
> #7  0x77bb789f in qdr_update_delivery_CT (core=0x8cb5d0, 
> action=0x7fffd4003d00, discard=false)
> at /home/eallen/workspace/qpid-dispatch/src/router_core/transfer.c:499
> #8  0x77bb2799 in router_core_thread (arg=0x8cb5d0)
> at 
> /home/eallen/workspace/qpid-dispatch/src/router_core/router_core_thread.c:71
> #9  0x7771060a in start_thread (arg=0x7fffea9cc700)
> at pthread_create.c:334
> #10 0x76c75a4d in clone ()
> at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109
> {quote}



--
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-263) Router crash when requesting log

2016-04-13 Thread Ted Ross (JIRA)


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

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

> Router crash when requesting log
> 
>
> Key: DISPATCH-263
> URL: https://issues.apache.org/jira/browse/DISPATCH-263
> Project: Qpid Dispatch
>  Issue Type: Bug
>  Components: Management Agent
>Affects Versions: 0.6
>Reporter: Ernest Allen
>Assignee: Ganesh Murthy
>Priority: Blocker
> Fix For: 0.6
>
>
> Router crashes when requesting latest log entries
> - Start 2 nodes from qpid-dispatch/tests/config-2
> - let routers run for about 5 minutes (problem does not occur unless I wait)
> - qdmanage GET-LOG -b 0.0.0.0:20100 -r QDR.B
> {quote}
> #0  0x76ba7a98 in __GI_raise (sig=sig@entry=6)
> at ../sysdeps/unix/sysv/linux/raise.c:55
> #1  0x76ba969a in __GI_abort () at abort.c:89
> #2  0x76ba0227 in __assert_fail_base (fmt=, 
> assertion=assertion@entry=0x77bcbaa8 "*((uint32_t*) (p + 
> desc->total_size)) == 0xbabecafe", 
> file=file@entry=0x77bcb880 
> "/home/eallen/workspace/qpid-dispatch/src/alloc_pool.c", line=line@entry=213, 
> function=function@entry=0x77bcbcc0 <__PRETTY_FUNCTION__.9429> 
> "qd_dealloc") at assert.c:92
> #3  0x76ba02d2 in __GI___assert_fail (
> assertion=0x77bcbaa8 "*((uint32_t*) (p + desc->total_size)) == 
> 0xbabecafe", 
> file=0x77bcb880 
> "/home/eallen/workspace/qpid-dispatch/src/alloc_pool.c", line=213, 
> function=0x77bcbcc0 <__PRETTY_FUNCTION__.9429> "qd_dealloc")
> at assert.c:101
> #4  0x77bc1cf0 in qd_dealloc (
> desc=0x77dd9fc0 <__desc_qdr_delivery_t>, tpool=0x7fffea9cc658, 
> p=0x7fffdc0092b0)
> at /home/eallen/workspace/qpid-dispatch/src/alloc_pool.c:213
> #5  0x77bb06f8 in free_qdr_delivery_t (p=0x7fffdc0092b0)
> at /home/eallen/workspace/qpid-dispatch/src/router_core/router_core.c:26
> ---Type  to continue, or q  to quit---
> #6  0x77bb6c54 in qdr_delivery_free (delivery=0x7fffdc0092b0)
> at /home/eallen/workspace/qpid-dispatch/src/router_core/transfer.c:207
> #7  0x77bb789f in qdr_update_delivery_CT (core=0x8cb5d0, 
> action=0x7fffd4003d00, discard=false)
> at /home/eallen/workspace/qpid-dispatch/src/router_core/transfer.c:499
> #8  0x77bb2799 in router_core_thread (arg=0x8cb5d0)
> at 
> /home/eallen/workspace/qpid-dispatch/src/router_core/router_core_thread.c:71
> #9  0x7771060a in start_thread (arg=0x7fffea9cc700)
> at pthread_create.c:334
> #10 0x76c75a4d in clone ()
> at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109
> {quote}



--
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-6983) [Web Management Console] Add UI support for queries

2016-04-13 Thread ASF subversion and git services (JIRA)


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

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

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

QPID-6983: Increase length of input widgets for entering select and where 
expressions in advanced mode

> [Web Management Console] Add UI support for queries
> ---
>
> Key: QPID-6983
> URL: https://issues.apache.org/jira/browse/QPID-6983
> Project: Qpid
>  Issue Type: Improvement
>  Components: Java Broker
>Reporter: Keith Wall
>Assignee: Alex Rudyy
> Attachments: query-ui-prototype.tar.gz, query-ui-prototype.tar.gz
>
>
> Add the ability to the Web Management Console to submit queries (using the 
> feature added by QPID-6969) and view the results.  The results may need to be 
> paginated for display.



--
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] [Reopened] (DISPATCH-263) Router crash when requesting log

2016-04-13 Thread Ganesh Murthy (JIRA)


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

Ganesh Murthy reopened DISPATCH-263:


> Router crash when requesting log
> 
>
> Key: DISPATCH-263
> URL: https://issues.apache.org/jira/browse/DISPATCH-263
> Project: Qpid Dispatch
>  Issue Type: Bug
>  Components: Management Agent
>Affects Versions: 0.6
>Reporter: Ernest Allen
>Assignee: Ganesh Murthy
>Priority: Blocker
> Fix For: 0.6
>
>
> Router crashes when requesting latest log entries
> - Start 2 nodes from qpid-dispatch/tests/config-2
> - let routers run for about 5 minutes (problem does not occur unless I wait)
> - qdmanage GET-LOG -b 0.0.0.0:20100 -r QDR.B
> {quote}
> #0  0x76ba7a98 in __GI_raise (sig=sig@entry=6)
> at ../sysdeps/unix/sysv/linux/raise.c:55
> #1  0x76ba969a in __GI_abort () at abort.c:89
> #2  0x76ba0227 in __assert_fail_base (fmt=, 
> assertion=assertion@entry=0x77bcbaa8 "*((uint32_t*) (p + 
> desc->total_size)) == 0xbabecafe", 
> file=file@entry=0x77bcb880 
> "/home/eallen/workspace/qpid-dispatch/src/alloc_pool.c", line=line@entry=213, 
> function=function@entry=0x77bcbcc0 <__PRETTY_FUNCTION__.9429> 
> "qd_dealloc") at assert.c:92
> #3  0x76ba02d2 in __GI___assert_fail (
> assertion=0x77bcbaa8 "*((uint32_t*) (p + desc->total_size)) == 
> 0xbabecafe", 
> file=0x77bcb880 
> "/home/eallen/workspace/qpid-dispatch/src/alloc_pool.c", line=213, 
> function=0x77bcbcc0 <__PRETTY_FUNCTION__.9429> "qd_dealloc")
> at assert.c:101
> #4  0x77bc1cf0 in qd_dealloc (
> desc=0x77dd9fc0 <__desc_qdr_delivery_t>, tpool=0x7fffea9cc658, 
> p=0x7fffdc0092b0)
> at /home/eallen/workspace/qpid-dispatch/src/alloc_pool.c:213
> #5  0x77bb06f8 in free_qdr_delivery_t (p=0x7fffdc0092b0)
> at /home/eallen/workspace/qpid-dispatch/src/router_core/router_core.c:26
> ---Type  to continue, or q  to quit---
> #6  0x77bb6c54 in qdr_delivery_free (delivery=0x7fffdc0092b0)
> at /home/eallen/workspace/qpid-dispatch/src/router_core/transfer.c:207
> #7  0x77bb789f in qdr_update_delivery_CT (core=0x8cb5d0, 
> action=0x7fffd4003d00, discard=false)
> at /home/eallen/workspace/qpid-dispatch/src/router_core/transfer.c:499
> #8  0x77bb2799 in router_core_thread (arg=0x8cb5d0)
> at 
> /home/eallen/workspace/qpid-dispatch/src/router_core/router_core_thread.c:71
> #9  0x7771060a in start_thread (arg=0x7fffea9cc700)
> at pthread_create.c:334
> #10 0x76c75a4d in clone ()
> at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109
> {quote}



--
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-263) Router crash when requesting log

2016-04-13 Thread Ganesh Murthy (JIRA)


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

Ganesh Murthy commented on DISPATCH-263:


This issue is not fixed yet. We are looking at an include issue.

> Router crash when requesting log
> 
>
> Key: DISPATCH-263
> URL: https://issues.apache.org/jira/browse/DISPATCH-263
> Project: Qpid Dispatch
>  Issue Type: Bug
>  Components: Management Agent
>Affects Versions: 0.6
>Reporter: Ernest Allen
>Assignee: Ganesh Murthy
>Priority: Blocker
> Fix For: 0.6
>
>
> Router crashes when requesting latest log entries
> - Start 2 nodes from qpid-dispatch/tests/config-2
> - let routers run for about 5 minutes (problem does not occur unless I wait)
> - qdmanage GET-LOG -b 0.0.0.0:20100 -r QDR.B
> {quote}
> #0  0x76ba7a98 in __GI_raise (sig=sig@entry=6)
> at ../sysdeps/unix/sysv/linux/raise.c:55
> #1  0x76ba969a in __GI_abort () at abort.c:89
> #2  0x76ba0227 in __assert_fail_base (fmt=, 
> assertion=assertion@entry=0x77bcbaa8 "*((uint32_t*) (p + 
> desc->total_size)) == 0xbabecafe", 
> file=file@entry=0x77bcb880 
> "/home/eallen/workspace/qpid-dispatch/src/alloc_pool.c", line=line@entry=213, 
> function=function@entry=0x77bcbcc0 <__PRETTY_FUNCTION__.9429> 
> "qd_dealloc") at assert.c:92
> #3  0x76ba02d2 in __GI___assert_fail (
> assertion=0x77bcbaa8 "*((uint32_t*) (p + desc->total_size)) == 
> 0xbabecafe", 
> file=0x77bcb880 
> "/home/eallen/workspace/qpid-dispatch/src/alloc_pool.c", line=213, 
> function=0x77bcbcc0 <__PRETTY_FUNCTION__.9429> "qd_dealloc")
> at assert.c:101
> #4  0x77bc1cf0 in qd_dealloc (
> desc=0x77dd9fc0 <__desc_qdr_delivery_t>, tpool=0x7fffea9cc658, 
> p=0x7fffdc0092b0)
> at /home/eallen/workspace/qpid-dispatch/src/alloc_pool.c:213
> #5  0x77bb06f8 in free_qdr_delivery_t (p=0x7fffdc0092b0)
> at /home/eallen/workspace/qpid-dispatch/src/router_core/router_core.c:26
> ---Type  to continue, or q  to quit---
> #6  0x77bb6c54 in qdr_delivery_free (delivery=0x7fffdc0092b0)
> at /home/eallen/workspace/qpid-dispatch/src/router_core/transfer.c:207
> #7  0x77bb789f in qdr_update_delivery_CT (core=0x8cb5d0, 
> action=0x7fffd4003d00, discard=false)
> at /home/eallen/workspace/qpid-dispatch/src/router_core/transfer.c:499
> #8  0x77bb2799 in router_core_thread (arg=0x8cb5d0)
> at 
> /home/eallen/workspace/qpid-dispatch/src/router_core/router_core_thread.c:71
> #9  0x7771060a in start_thread (arg=0x7fffea9cc700)
> at pthread_create.c:334
> #10 0x76c75a4d in clone ()
> at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109
> {quote}



--
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

Proton 0.12.2 release

2016-04-13 Thread Robbie Gemmell

Hi folks,

I'd like to do a 0.12.2 release to incorporate a proton-j fix for
https://issues.apache.org/jira/browse/PROTON-1171. If all goes well
with feedback on that change I would propose to spin a release
candidate in the next day or so.

If you have any targetted bug fixes you would like to include ahead of
the imminent 0.13.0 release cycle, now would be the time to think
about it.

Robbie

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

[jira] [Commented] (QPID-6983) [Web Management Console] Add UI support for queries

2016-04-13 Thread ASF subversion and git services (JIRA)


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

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

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

QPID-6983: Fix 'deleted' attribute getter in WhereCriteria widget

> [Web Management Console] Add UI support for queries
> ---
>
> Key: QPID-6983
> URL: https://issues.apache.org/jira/browse/QPID-6983
> Project: Qpid
>  Issue Type: Improvement
>  Components: Java Broker
>Reporter: Keith Wall
>Assignee: Alex Rudyy
> Attachments: query-ui-prototype.tar.gz, query-ui-prototype.tar.gz
>
>
> Add the ability to the Web Management Console to submit queries (using the 
> feature added by QPID-6969) and view the results.  The results may need to be 
> paginated for display.



--
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-263) Router crash when requesting log

2016-04-13 Thread Ted Ross (JIRA)


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

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

Good work, Ganesh and Ernie.

> Router crash when requesting log
> 
>
> Key: DISPATCH-263
> URL: https://issues.apache.org/jira/browse/DISPATCH-263
> Project: Qpid Dispatch
>  Issue Type: Bug
>  Components: Management Agent
>Affects Versions: 0.6
>Reporter: Ernest Allen
>Assignee: Ganesh Murthy
>Priority: Blocker
> Fix For: 0.6
>
>
> Router crashes when requesting latest log entries
> - Start 2 nodes from qpid-dispatch/tests/config-2
> - let routers run for about 5 minutes (problem does not occur unless I wait)
> - qdmanage GET-LOG -b 0.0.0.0:20100 -r QDR.B
> {quote}
> #0  0x76ba7a98 in __GI_raise (sig=sig@entry=6)
> at ../sysdeps/unix/sysv/linux/raise.c:55
> #1  0x76ba969a in __GI_abort () at abort.c:89
> #2  0x76ba0227 in __assert_fail_base (fmt=, 
> assertion=assertion@entry=0x77bcbaa8 "*((uint32_t*) (p + 
> desc->total_size)) == 0xbabecafe", 
> file=file@entry=0x77bcb880 
> "/home/eallen/workspace/qpid-dispatch/src/alloc_pool.c", line=line@entry=213, 
> function=function@entry=0x77bcbcc0 <__PRETTY_FUNCTION__.9429> 
> "qd_dealloc") at assert.c:92
> #3  0x76ba02d2 in __GI___assert_fail (
> assertion=0x77bcbaa8 "*((uint32_t*) (p + desc->total_size)) == 
> 0xbabecafe", 
> file=0x77bcb880 
> "/home/eallen/workspace/qpid-dispatch/src/alloc_pool.c", line=213, 
> function=0x77bcbcc0 <__PRETTY_FUNCTION__.9429> "qd_dealloc")
> at assert.c:101
> #4  0x77bc1cf0 in qd_dealloc (
> desc=0x77dd9fc0 <__desc_qdr_delivery_t>, tpool=0x7fffea9cc658, 
> p=0x7fffdc0092b0)
> at /home/eallen/workspace/qpid-dispatch/src/alloc_pool.c:213
> #5  0x77bb06f8 in free_qdr_delivery_t (p=0x7fffdc0092b0)
> at /home/eallen/workspace/qpid-dispatch/src/router_core/router_core.c:26
> ---Type  to continue, or q  to quit---
> #6  0x77bb6c54 in qdr_delivery_free (delivery=0x7fffdc0092b0)
> at /home/eallen/workspace/qpid-dispatch/src/router_core/transfer.c:207
> #7  0x77bb789f in qdr_update_delivery_CT (core=0x8cb5d0, 
> action=0x7fffd4003d00, discard=false)
> at /home/eallen/workspace/qpid-dispatch/src/router_core/transfer.c:499
> #8  0x77bb2799 in router_core_thread (arg=0x8cb5d0)
> at 
> /home/eallen/workspace/qpid-dispatch/src/router_core/router_core_thread.c:71
> #9  0x7771060a in start_thread (arg=0x7fffea9cc700)
> at pthread_create.c:334
> #10 0x76c75a4d in clone ()
> at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109
> {quote}



--
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-263) Router crash when requesting log

2016-04-13 Thread ASF GitHub Bot (JIRA)


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

ASF GitHub Bot commented on DISPATCH-263:
-

Github user asfgit closed the pull request at:

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


> Router crash when requesting log
> 
>
> Key: DISPATCH-263
> URL: https://issues.apache.org/jira/browse/DISPATCH-263
> Project: Qpid Dispatch
>  Issue Type: Bug
>  Components: Management Agent
>Affects Versions: 0.6
>Reporter: Ernest Allen
>Assignee: Ganesh Murthy
>Priority: Blocker
> Fix For: 0.6
>
>
> Router crashes when requesting latest log entries
> - Start 2 nodes from qpid-dispatch/tests/config-2
> - let routers run for about 5 minutes (problem does not occur unless I wait)
> - qdmanage GET-LOG -b 0.0.0.0:20100 -r QDR.B
> {quote}
> #0  0x76ba7a98 in __GI_raise (sig=sig@entry=6)
> at ../sysdeps/unix/sysv/linux/raise.c:55
> #1  0x76ba969a in __GI_abort () at abort.c:89
> #2  0x76ba0227 in __assert_fail_base (fmt=, 
> assertion=assertion@entry=0x77bcbaa8 "*((uint32_t*) (p + 
> desc->total_size)) == 0xbabecafe", 
> file=file@entry=0x77bcb880 
> "/home/eallen/workspace/qpid-dispatch/src/alloc_pool.c", line=line@entry=213, 
> function=function@entry=0x77bcbcc0 <__PRETTY_FUNCTION__.9429> 
> "qd_dealloc") at assert.c:92
> #3  0x76ba02d2 in __GI___assert_fail (
> assertion=0x77bcbaa8 "*((uint32_t*) (p + desc->total_size)) == 
> 0xbabecafe", 
> file=0x77bcb880 
> "/home/eallen/workspace/qpid-dispatch/src/alloc_pool.c", line=213, 
> function=0x77bcbcc0 <__PRETTY_FUNCTION__.9429> "qd_dealloc")
> at assert.c:101
> #4  0x77bc1cf0 in qd_dealloc (
> desc=0x77dd9fc0 <__desc_qdr_delivery_t>, tpool=0x7fffea9cc658, 
> p=0x7fffdc0092b0)
> at /home/eallen/workspace/qpid-dispatch/src/alloc_pool.c:213
> #5  0x77bb06f8 in free_qdr_delivery_t (p=0x7fffdc0092b0)
> at /home/eallen/workspace/qpid-dispatch/src/router_core/router_core.c:26
> ---Type  to continue, or q  to quit---
> #6  0x77bb6c54 in qdr_delivery_free (delivery=0x7fffdc0092b0)
> at /home/eallen/workspace/qpid-dispatch/src/router_core/transfer.c:207
> #7  0x77bb789f in qdr_update_delivery_CT (core=0x8cb5d0, 
> action=0x7fffd4003d00, discard=false)
> at /home/eallen/workspace/qpid-dispatch/src/router_core/transfer.c:499
> #8  0x77bb2799 in router_core_thread (arg=0x8cb5d0)
> at 
> /home/eallen/workspace/qpid-dispatch/src/router_core/router_core_thread.c:71
> #9  0x7771060a in start_thread (arg=0x7fffea9cc700)
> at pthread_create.c:334
> #10 0x76c75a4d in clone ()
> at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109
> {quote}



--
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-263) Router crash when requesting log

2016-04-13 Thread ASF subversion and git services (JIRA)


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

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

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

DISPATCH-263 - Added a record with key PN_DELIVERY_CTX to hold the message. 
Dont accept the disposition until the full message has been received


> Router crash when requesting log
> 
>
> Key: DISPATCH-263
> URL: https://issues.apache.org/jira/browse/DISPATCH-263
> Project: Qpid Dispatch
>  Issue Type: Bug
>  Components: Management Agent
>Affects Versions: 0.6
>Reporter: Ernest Allen
>Assignee: Ganesh Murthy
>Priority: Blocker
> Fix For: 0.6
>
>
> Router crashes when requesting latest log entries
> - Start 2 nodes from qpid-dispatch/tests/config-2
> - let routers run for about 5 minutes (problem does not occur unless I wait)
> - qdmanage GET-LOG -b 0.0.0.0:20100 -r QDR.B
> {quote}
> #0  0x76ba7a98 in __GI_raise (sig=sig@entry=6)
> at ../sysdeps/unix/sysv/linux/raise.c:55
> #1  0x76ba969a in __GI_abort () at abort.c:89
> #2  0x76ba0227 in __assert_fail_base (fmt=, 
> assertion=assertion@entry=0x77bcbaa8 "*((uint32_t*) (p + 
> desc->total_size)) == 0xbabecafe", 
> file=file@entry=0x77bcb880 
> "/home/eallen/workspace/qpid-dispatch/src/alloc_pool.c", line=line@entry=213, 
> function=function@entry=0x77bcbcc0 <__PRETTY_FUNCTION__.9429> 
> "qd_dealloc") at assert.c:92
> #3  0x76ba02d2 in __GI___assert_fail (
> assertion=0x77bcbaa8 "*((uint32_t*) (p + desc->total_size)) == 
> 0xbabecafe", 
> file=0x77bcb880 
> "/home/eallen/workspace/qpid-dispatch/src/alloc_pool.c", line=213, 
> function=0x77bcbcc0 <__PRETTY_FUNCTION__.9429> "qd_dealloc")
> at assert.c:101
> #4  0x77bc1cf0 in qd_dealloc (
> desc=0x77dd9fc0 <__desc_qdr_delivery_t>, tpool=0x7fffea9cc658, 
> p=0x7fffdc0092b0)
> at /home/eallen/workspace/qpid-dispatch/src/alloc_pool.c:213
> #5  0x77bb06f8 in free_qdr_delivery_t (p=0x7fffdc0092b0)
> at /home/eallen/workspace/qpid-dispatch/src/router_core/router_core.c:26
> ---Type  to continue, or q  to quit---
> #6  0x77bb6c54 in qdr_delivery_free (delivery=0x7fffdc0092b0)
> at /home/eallen/workspace/qpid-dispatch/src/router_core/transfer.c:207
> #7  0x77bb789f in qdr_update_delivery_CT (core=0x8cb5d0, 
> action=0x7fffd4003d00, discard=false)
> at /home/eallen/workspace/qpid-dispatch/src/router_core/transfer.c:499
> #8  0x77bb2799 in router_core_thread (arg=0x8cb5d0)
> at 
> /home/eallen/workspace/qpid-dispatch/src/router_core/router_core_thread.c:71
> #9  0x7771060a in start_thread (arg=0x7fffea9cc700)
> at pthread_create.c:334
> #10 0x76c75a4d in clone ()
> at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109
> {quote}



--
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-dispatch pull request: DISPATCH-263 - Added a record with key...

2016-04-13 Thread asfgit

Github user asfgit closed the pull request at:

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


---
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-dispatch pull request: DISPATCH-263 - Added a record with key...

2016-04-13 Thread ganeshmurthy

GitHub user ganeshmurthy opened a pull request:

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

DISPATCH-263 - Added a record with key PN_DELIVERY_CTX to hold the meâ¦

â¦ssage. Dont accept the disposition until the full message has been 
received

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

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

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

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


commit df9f69c1279ad22a6b5f30565d850028337e231a
Author: Ganesh Murthy 
Date:   2016-04-13T13:20:37Z

DISPATCH-263 - Added a record with key PN_DELIVERY_CTX to hold the message. 
Dont accept the disposition until the full message has been received




---
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] [Commented] (DISPATCH-263) Router crash when requesting log

2016-04-13 Thread ASF GitHub Bot (JIRA)


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

ASF GitHub Bot commented on DISPATCH-263:
-

GitHub user ganeshmurthy opened a pull request:

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

DISPATCH-263 - Added a record with key PN_DELIVERY_CTX to hold the me…

…ssage. Dont accept the disposition until the full message has been received

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

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

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

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


commit df9f69c1279ad22a6b5f30565d850028337e231a
Author: Ganesh Murthy 
Date:   2016-04-13T13:20:37Z

DISPATCH-263 - Added a record with key PN_DELIVERY_CTX to hold the message. 
Dont accept the disposition until the full message has been received




> Router crash when requesting log
> 
>
> Key: DISPATCH-263
> URL: https://issues.apache.org/jira/browse/DISPATCH-263
> Project: Qpid Dispatch
>  Issue Type: Bug
>  Components: Management Agent
>Affects Versions: 0.6
>Reporter: Ernest Allen
>Assignee: Ganesh Murthy
>Priority: Blocker
> Fix For: 0.6
>
>
> Router crashes when requesting latest log entries
> - Start 2 nodes from qpid-dispatch/tests/config-2
> - let routers run for about 5 minutes (problem does not occur unless I wait)
> - qdmanage GET-LOG -b 0.0.0.0:20100 -r QDR.B
> {quote}
> #0  0x76ba7a98 in __GI_raise (sig=sig@entry=6)
> at ../sysdeps/unix/sysv/linux/raise.c:55
> #1  0x76ba969a in __GI_abort () at abort.c:89
> #2  0x76ba0227 in __assert_fail_base (fmt=, 
> assertion=assertion@entry=0x77bcbaa8 "*((uint32_t*) (p + 
> desc->total_size)) == 0xbabecafe", 
> file=file@entry=0x77bcb880 
> "/home/eallen/workspace/qpid-dispatch/src/alloc_pool.c", line=line@entry=213, 
> function=function@entry=0x77bcbcc0 <__PRETTY_FUNCTION__.9429> 
> "qd_dealloc") at assert.c:92
> #3  0x76ba02d2 in __GI___assert_fail (
> assertion=0x77bcbaa8 "*((uint32_t*) (p + desc->total_size)) == 
> 0xbabecafe", 
> file=0x77bcb880 
> "/home/eallen/workspace/qpid-dispatch/src/alloc_pool.c", line=213, 
> function=0x77bcbcc0 <__PRETTY_FUNCTION__.9429> "qd_dealloc")
> at assert.c:101
> #4  0x77bc1cf0 in qd_dealloc (
> desc=0x77dd9fc0 <__desc_qdr_delivery_t>, tpool=0x7fffea9cc658, 
> p=0x7fffdc0092b0)
> at /home/eallen/workspace/qpid-dispatch/src/alloc_pool.c:213
> #5  0x77bb06f8 in free_qdr_delivery_t (p=0x7fffdc0092b0)
> at /home/eallen/workspace/qpid-dispatch/src/router_core/router_core.c:26
> ---Type  to continue, or q  to quit---
> #6  0x77bb6c54 in qdr_delivery_free (delivery=0x7fffdc0092b0)
> at /home/eallen/workspace/qpid-dispatch/src/router_core/transfer.c:207
> #7  0x77bb789f in qdr_update_delivery_CT (core=0x8cb5d0, 
> action=0x7fffd4003d00, discard=false)
> at /home/eallen/workspace/qpid-dispatch/src/router_core/transfer.c:499
> #8  0x77bb2799 in router_core_thread (arg=0x8cb5d0)
> at 
> /home/eallen/workspace/qpid-dispatch/src/router_core/router_core_thread.c:71
> #9  0x7771060a in start_thread (arg=0x7fffea9cc700)
> at pthread_create.c:334
> #10 0x76c75a4d in clone ()
> at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109
> {quote}



--
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-7158) [Java Broker] Change type of datetime management attributes from Long to java.util.Date

2016-04-13 Thread ASF subversion and git services (JIRA)


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

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

Commit 1738935 from [~k-wall] in branch 'java/trunk'
[ https://svn.apache.org/r1738935 ]

QPID-7158: [Java Broker] Support attribute values of type java.util.Date

> [Java Broker] Change type of datetime management attributes from Long to 
> java.util.Date
> ---
>
> Key: QPID-7158
> URL: https://issues.apache.org/jira/browse/QPID-7158
> Project: Qpid
>  Issue Type: Improvement
>  Components: Java Broker
>Reporter: Alex Rudyy
> Fix For: qpid-java-6.1
>
>
> It is unclear from metadata that datetime attribute having type Long  
> actually represent  datetime values. We need to change datetime attributes 
> type from Long to java.util.Date which can still be serialized into json as 
> long values



--
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-6983) [Web Management Console] Add UI support for queries

2016-04-13 Thread ASF subversion and git services (JIRA)


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

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

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

QPID-6983: Add query building UI

> [Web Management Console] Add UI support for queries
> ---
>
> Key: QPID-6983
> URL: https://issues.apache.org/jira/browse/QPID-6983
> Project: Qpid
>  Issue Type: Improvement
>  Components: Java Broker
>Reporter: Keith Wall
>Assignee: Alex Rudyy
> Attachments: query-ui-prototype.tar.gz, query-ui-prototype.tar.gz
>
>
> Add the ability to the Web Management Console to submit queries (using the 
> feature added by QPID-6969) and view the results.  The results may need to be 
> paginated for display.



--
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-263) Router crash when requesting log

2016-04-13 Thread Ted Ross (JIRA)


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

Ted Ross commented on DISPATCH-263:
---

This is a really good find...
This can be reproduced by sending a multi-frame (frames >> 2) pre-settled 
message through the router.  Proton sets the _updated_ flag on the delivery 
(because it's settled) before the last frame is read from the delivery.  
Dispatch interprets this as a disposition change prior to the reception of the 
message and doesn't properly handle this case.


> Router crash when requesting log
> 
>
> Key: DISPATCH-263
> URL: https://issues.apache.org/jira/browse/DISPATCH-263
> Project: Qpid Dispatch
>  Issue Type: Bug
>  Components: Management Agent
>Affects Versions: 0.6
>Reporter: Ernest Allen
>Assignee: Ganesh Murthy
>Priority: Blocker
> Fix For: 0.6
>
>
> Router crashes when requesting latest log entries
> - Start 2 nodes from qpid-dispatch/tests/config-2
> - let routers run for about 5 minutes (problem does not occur unless I wait)
> - qdmanage GET-LOG -b 0.0.0.0:20100 -r QDR.B
> {quote}
> #0  0x76ba7a98 in __GI_raise (sig=sig@entry=6)
> at ../sysdeps/unix/sysv/linux/raise.c:55
> #1  0x76ba969a in __GI_abort () at abort.c:89
> #2  0x76ba0227 in __assert_fail_base (fmt=, 
> assertion=assertion@entry=0x77bcbaa8 "*((uint32_t*) (p + 
> desc->total_size)) == 0xbabecafe", 
> file=file@entry=0x77bcb880 
> "/home/eallen/workspace/qpid-dispatch/src/alloc_pool.c", line=line@entry=213, 
> function=function@entry=0x77bcbcc0 <__PRETTY_FUNCTION__.9429> 
> "qd_dealloc") at assert.c:92
> #3  0x76ba02d2 in __GI___assert_fail (
> assertion=0x77bcbaa8 "*((uint32_t*) (p + desc->total_size)) == 
> 0xbabecafe", 
> file=0x77bcb880 
> "/home/eallen/workspace/qpid-dispatch/src/alloc_pool.c", line=213, 
> function=0x77bcbcc0 <__PRETTY_FUNCTION__.9429> "qd_dealloc")
> at assert.c:101
> #4  0x77bc1cf0 in qd_dealloc (
> desc=0x77dd9fc0 <__desc_qdr_delivery_t>, tpool=0x7fffea9cc658, 
> p=0x7fffdc0092b0)
> at /home/eallen/workspace/qpid-dispatch/src/alloc_pool.c:213
> #5  0x77bb06f8 in free_qdr_delivery_t (p=0x7fffdc0092b0)
> at /home/eallen/workspace/qpid-dispatch/src/router_core/router_core.c:26
> ---Type  to continue, or q  to quit---
> #6  0x77bb6c54 in qdr_delivery_free (delivery=0x7fffdc0092b0)
> at /home/eallen/workspace/qpid-dispatch/src/router_core/transfer.c:207
> #7  0x77bb789f in qdr_update_delivery_CT (core=0x8cb5d0, 
> action=0x7fffd4003d00, discard=false)
> at /home/eallen/workspace/qpid-dispatch/src/router_core/transfer.c:499
> #8  0x77bb2799 in router_core_thread (arg=0x8cb5d0)
> at 
> /home/eallen/workspace/qpid-dispatch/src/router_core/router_core_thread.c:71
> #9  0x7771060a in start_thread (arg=0x7fffea9cc700)
> at pthread_create.c:334
> #10 0x76c75a4d in clone ()
> at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109
> {quote}



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

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

[jira] [Updated] (DISPATCH-263) Router crash when requesting log

2016-04-13 Thread Ted Ross (JIRA)


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

Ted Ross updated DISPATCH-263:
--
Priority: Blocker  (was: Major)

> Router crash when requesting log
> 
>
> Key: DISPATCH-263
> URL: https://issues.apache.org/jira/browse/DISPATCH-263
> Project: Qpid Dispatch
>  Issue Type: Bug
>  Components: Management Agent
>Affects Versions: 0.6
>Reporter: Ernest Allen
>Assignee: Ganesh Murthy
>Priority: Blocker
> Fix For: 0.6
>
>
> Router crashes when requesting latest log entries
> - Start 2 nodes from qpid-dispatch/tests/config-2
> - let routers run for about 5 minutes (problem does not occur unless I wait)
> - qdmanage GET-LOG -b 0.0.0.0:20100 -r QDR.B
> {quote}
> #0  0x76ba7a98 in __GI_raise (sig=sig@entry=6)
> at ../sysdeps/unix/sysv/linux/raise.c:55
> #1  0x76ba969a in __GI_abort () at abort.c:89
> #2  0x76ba0227 in __assert_fail_base (fmt=, 
> assertion=assertion@entry=0x77bcbaa8 "*((uint32_t*) (p + 
> desc->total_size)) == 0xbabecafe", 
> file=file@entry=0x77bcb880 
> "/home/eallen/workspace/qpid-dispatch/src/alloc_pool.c", line=line@entry=213, 
> function=function@entry=0x77bcbcc0 <__PRETTY_FUNCTION__.9429> 
> "qd_dealloc") at assert.c:92
> #3  0x76ba02d2 in __GI___assert_fail (
> assertion=0x77bcbaa8 "*((uint32_t*) (p + desc->total_size)) == 
> 0xbabecafe", 
> file=0x77bcb880 
> "/home/eallen/workspace/qpid-dispatch/src/alloc_pool.c", line=213, 
> function=0x77bcbcc0 <__PRETTY_FUNCTION__.9429> "qd_dealloc")
> at assert.c:101
> #4  0x77bc1cf0 in qd_dealloc (
> desc=0x77dd9fc0 <__desc_qdr_delivery_t>, tpool=0x7fffea9cc658, 
> p=0x7fffdc0092b0)
> at /home/eallen/workspace/qpid-dispatch/src/alloc_pool.c:213
> #5  0x77bb06f8 in free_qdr_delivery_t (p=0x7fffdc0092b0)
> at /home/eallen/workspace/qpid-dispatch/src/router_core/router_core.c:26
> ---Type  to continue, or q  to quit---
> #6  0x77bb6c54 in qdr_delivery_free (delivery=0x7fffdc0092b0)
> at /home/eallen/workspace/qpid-dispatch/src/router_core/transfer.c:207
> #7  0x77bb789f in qdr_update_delivery_CT (core=0x8cb5d0, 
> action=0x7fffd4003d00, discard=false)
> at /home/eallen/workspace/qpid-dispatch/src/router_core/transfer.c:499
> #8  0x77bb2799 in router_core_thread (arg=0x8cb5d0)
> at 
> /home/eallen/workspace/qpid-dispatch/src/router_core/router_core_thread.c:71
> #9  0x7771060a in start_thread (arg=0x7fffea9cc700)
> at pthread_create.c:334
> #10 0x76c75a4d in clone ()
> at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109
> {quote}



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

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

[jira] [Updated] (DISPATCH-263) Router crash when requesting log

2016-04-13 Thread Ted Ross (JIRA)


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

Ted Ross updated DISPATCH-263:
--
Fix Version/s: 0.6

> Router crash when requesting log
> 
>
> Key: DISPATCH-263
> URL: https://issues.apache.org/jira/browse/DISPATCH-263
> Project: Qpid Dispatch
>  Issue Type: Bug
>  Components: Management Agent
>Affects Versions: 0.6
>Reporter: Ernest Allen
>Assignee: Ganesh Murthy
> Fix For: 0.6
>
>
> Router crashes when requesting latest log entries
> - Start 2 nodes from qpid-dispatch/tests/config-2
> - let routers run for about 5 minutes (problem does not occur unless I wait)
> - qdmanage GET-LOG -b 0.0.0.0:20100 -r QDR.B
> {quote}
> #0  0x76ba7a98 in __GI_raise (sig=sig@entry=6)
> at ../sysdeps/unix/sysv/linux/raise.c:55
> #1  0x76ba969a in __GI_abort () at abort.c:89
> #2  0x76ba0227 in __assert_fail_base (fmt=, 
> assertion=assertion@entry=0x77bcbaa8 "*((uint32_t*) (p + 
> desc->total_size)) == 0xbabecafe", 
> file=file@entry=0x77bcb880 
> "/home/eallen/workspace/qpid-dispatch/src/alloc_pool.c", line=line@entry=213, 
> function=function@entry=0x77bcbcc0 <__PRETTY_FUNCTION__.9429> 
> "qd_dealloc") at assert.c:92
> #3  0x76ba02d2 in __GI___assert_fail (
> assertion=0x77bcbaa8 "*((uint32_t*) (p + desc->total_size)) == 
> 0xbabecafe", 
> file=0x77bcb880 
> "/home/eallen/workspace/qpid-dispatch/src/alloc_pool.c", line=213, 
> function=0x77bcbcc0 <__PRETTY_FUNCTION__.9429> "qd_dealloc")
> at assert.c:101
> #4  0x77bc1cf0 in qd_dealloc (
> desc=0x77dd9fc0 <__desc_qdr_delivery_t>, tpool=0x7fffea9cc658, 
> p=0x7fffdc0092b0)
> at /home/eallen/workspace/qpid-dispatch/src/alloc_pool.c:213
> #5  0x77bb06f8 in free_qdr_delivery_t (p=0x7fffdc0092b0)
> at /home/eallen/workspace/qpid-dispatch/src/router_core/router_core.c:26
> ---Type  to continue, or q  to quit---
> #6  0x77bb6c54 in qdr_delivery_free (delivery=0x7fffdc0092b0)
> at /home/eallen/workspace/qpid-dispatch/src/router_core/transfer.c:207
> #7  0x77bb789f in qdr_update_delivery_CT (core=0x8cb5d0, 
> action=0x7fffd4003d00, discard=false)
> at /home/eallen/workspace/qpid-dispatch/src/router_core/transfer.c:499
> #8  0x77bb2799 in router_core_thread (arg=0x8cb5d0)
> at 
> /home/eallen/workspace/qpid-dispatch/src/router_core/router_core_thread.c:71
> #9  0x7771060a in start_thread (arg=0x7fffea9cc700)
> at pthread_create.c:334
> #10 0x76c75a4d in clone ()
> at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109
> {quote}



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

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

[jira] [Updated] (QPID-6983) [Web Management Console] Add UI support for queries

2016-04-13 Thread Alex Rudyy (JIRA)


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

Alex Rudyy updated QPID-6983:
-
Attachment: query-ui-prototype.tar.gz

> [Web Management Console] Add UI support for queries
> ---
>
> Key: QPID-6983
> URL: https://issues.apache.org/jira/browse/QPID-6983
> Project: Qpid
>  Issue Type: Improvement
>  Components: Java Broker
>Reporter: Keith Wall
>Assignee: Alex Rudyy
> Attachments: query-ui-prototype.tar.gz, query-ui-prototype.tar.gz
>
>
> Add the ability to the Web Management Console to submit queries (using the 
> feature added by QPID-6969) and view the results.  The results may need to be 
> paginated for display.



--
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-7196) [Java Broker] ConcurrentModificationException can occur on Broker startup when virtual host is activated

2016-04-13 Thread Keith Wall (JIRA)


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

Keith Wall commented on QPID-7196:
--

I think we need to review all the places in the code where we call 
System#setProperty or System#setProperties.On the Broker side we will 
probably want to ensure that we mutate all system properties early in the 
Broker life when it is still single threaded and then from that point forward 
treat System properties as read-only.   With the example above, we are mutating 
the environment every time we start a Derby VNN/VH.

On client is harder, as we can't predicate when in an application's life it 
will load the Qpid client library and know what the application's thread may be 
doing.  Perhaps all we can do it ensure that System properties are mutated from 
a single point and document what the user needs to do in order to know all 
initialisation is complete.


> [Java Broker] ConcurrentModificationException can occur on Broker startup 
> when virtual host is activated
> 
>
> Key: QPID-7196
> URL: https://issues.apache.org/jira/browse/QPID-7196
> Project: Qpid
>  Issue Type: Bug
>  Components: Java Broker
>Affects Versions: qpid-java-6.0.1, qpid-java-6.1
>Reporter: Alex Rudyy
> Fix For: qpid-java-6.1
>
>
> ConcurrentModificationException is observed on broker start-up having 2 
> virtual hosts with hundreds of queues. One host was DERBY VH and the other 
> was BDB VH. 
> {noformat}
> 2016-04-12 15:25:40,391 ERROR [VirtualHostNode-test-Config] 
> (o.a.q.s.m.AbstractConfiguredObject) - Failed to open object with name 
> 'test'.  Object will be put into ERROR state.
> java.util.ConcurrentModificationException: null
> at java.util.Hashtable$Enumerator.next(Hashtable.java:1367) 
> ~[na:1.8.0_66]
> at java.util.HashMap.putMapEntries(HashMap.java:511) ~[na:1.8.0_66]
> at java.util.HashMap.putAll(HashMap.java:784) ~[na:1.8.0_66]
> at 
> org.apache.qpid.server.model.AbstractConfiguredObject.getContextKeys(AbstractConfiguredObject.java:2758)
>  [classes/:na]
> at 
> org.apache.qpid.server.store.berkeleydb.BDBUtils.getCacheMode(BDBUtils.java:161)
>  ~[classes/:na]
> at 
> org.apache.qpid.server.store.berkeleydb.StandardEnvironmentFacadeFactory$1.getCacheMode(StandardEnvironmentFacadeFactory.java:66)
>  ~[classes/:na]
> at 
> org.apache.qpid.server.store.berkeleydb.StandardEnvironmentFacade.(StandardEnvironmentFacade.java:110)
>  ~[classes/:na]
> at 
> org.apache.qpid.server.store.berkeleydb.StandardEnvironmentFacadeFactory.createEnvironmentFacade(StandardEnvironmentFacadeFactory.java:82)
>  ~[classes/:na]
> at 
> org.apache.qpid.server.store.berkeleydb.BDBMessageStore.openMessageStore(BDBMessageStore.java:80)
>  ~[classes/:na]
> at 
> org.apache.qpid.server.virtualhost.AbstractVirtualHost.onActivate(AbstractVirtualHost.java:1871)
>  ~[classes/:na]
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 
> ~[na:1.8.0_66]
> at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) 
> ~[na:1.8.0_66]
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>  ~[na:1.8.0_66]
> at java.lang.reflect.Method.invoke(Method.java:497) ~[na:1.8.0_66]
> at 
> org.apache.qpid.server.model.AbstractConfiguredObject.attainState(AbstractConfiguredObject.java:1308)
>  [classes/:na]
> at 
> org.apache.qpid.server.model.AbstractConfiguredObject.attainState(AbstractConfiguredObject.java:1287)
>  [classes/:na]
> at 
> org.apache.qpid.server.model.AbstractConfiguredObject$8.onSuccess(AbstractConfiguredObject.java:908)
>  [classes/:na]
> at 
> org.apache.qpid.server.model.AbstractConfiguredObject$8.onSuccess(AbstractConfiguredObject.java:902)
>  [classes/:na]
> at com.google.common.util.concurrent.Futures$6.run(Futures.java:1319) 
> [guava-18.0.jar:na]
> at 
> com.google.common.util.concurrent.MoreExecutors$DirectExecutor.execute(MoreExecutors.java:457)
>  [guava-18.0.jar:na]
> at 
> com.google.common.util.concurrent.ExecutionList.executeListener(ExecutionList.java:156)
>  [guava-18.0.jar:na]
> at 
> com.google.common.util.concurrent.ExecutionList.add(ExecutionList.java:101) 
> [guava-18.0.jar:na]
> at 
> com.google.common.util.concurrent.AbstractFuture.addListener(AbstractFuture.java:170)
>  [guava-18.0.jar:na]
> at 
> com.google.common.util.concurrent.Futures.addCallback(Futures.java:1322) 
> [guava-18.0.jar:na]
> at 
> com.google.common.util.concurrent.Futures.addCallback(Futures.java:1258) 
> [guava-18.0.jar:na]
> at 
>

[jira] [Updated] (QPID-7196) [Java Broker] ConcurrentModificationException can occur on Broker startup when virtual host is activated

2016-04-13 Thread Keith Wall (JIRA)


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

Keith Wall updated QPID-7196:
-
Fix Version/s: qpid-java-6.1

> [Java Broker] ConcurrentModificationException can occur on Broker startup 
> when virtual host is activated
> 
>
> Key: QPID-7196
> URL: https://issues.apache.org/jira/browse/QPID-7196
> Project: Qpid
>  Issue Type: Bug
>  Components: Java Broker
>Affects Versions: qpid-java-6.0.1, qpid-java-6.1
>Reporter: Alex Rudyy
> Fix For: qpid-java-6.1
>
>
> ConcurrentModificationException is observed on broker start-up having 2 
> virtual hosts with hundreds of queues. One host was DERBY VH and the other 
> was BDB VH. 
> {noformat}
> 2016-04-12 15:25:40,391 ERROR [VirtualHostNode-test-Config] 
> (o.a.q.s.m.AbstractConfiguredObject) - Failed to open object with name 
> 'test'.  Object will be put into ERROR state.
> java.util.ConcurrentModificationException: null
> at java.util.Hashtable$Enumerator.next(Hashtable.java:1367) 
> ~[na:1.8.0_66]
> at java.util.HashMap.putMapEntries(HashMap.java:511) ~[na:1.8.0_66]
> at java.util.HashMap.putAll(HashMap.java:784) ~[na:1.8.0_66]
> at 
> org.apache.qpid.server.model.AbstractConfiguredObject.getContextKeys(AbstractConfiguredObject.java:2758)
>  [classes/:na]
> at 
> org.apache.qpid.server.store.berkeleydb.BDBUtils.getCacheMode(BDBUtils.java:161)
>  ~[classes/:na]
> at 
> org.apache.qpid.server.store.berkeleydb.StandardEnvironmentFacadeFactory$1.getCacheMode(StandardEnvironmentFacadeFactory.java:66)
>  ~[classes/:na]
> at 
> org.apache.qpid.server.store.berkeleydb.StandardEnvironmentFacade.(StandardEnvironmentFacade.java:110)
>  ~[classes/:na]
> at 
> org.apache.qpid.server.store.berkeleydb.StandardEnvironmentFacadeFactory.createEnvironmentFacade(StandardEnvironmentFacadeFactory.java:82)
>  ~[classes/:na]
> at 
> org.apache.qpid.server.store.berkeleydb.BDBMessageStore.openMessageStore(BDBMessageStore.java:80)
>  ~[classes/:na]
> at 
> org.apache.qpid.server.virtualhost.AbstractVirtualHost.onActivate(AbstractVirtualHost.java:1871)
>  ~[classes/:na]
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 
> ~[na:1.8.0_66]
> at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) 
> ~[na:1.8.0_66]
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>  ~[na:1.8.0_66]
> at java.lang.reflect.Method.invoke(Method.java:497) ~[na:1.8.0_66]
> at 
> org.apache.qpid.server.model.AbstractConfiguredObject.attainState(AbstractConfiguredObject.java:1308)
>  [classes/:na]
> at 
> org.apache.qpid.server.model.AbstractConfiguredObject.attainState(AbstractConfiguredObject.java:1287)
>  [classes/:na]
> at 
> org.apache.qpid.server.model.AbstractConfiguredObject$8.onSuccess(AbstractConfiguredObject.java:908)
>  [classes/:na]
> at 
> org.apache.qpid.server.model.AbstractConfiguredObject$8.onSuccess(AbstractConfiguredObject.java:902)
>  [classes/:na]
> at com.google.common.util.concurrent.Futures$6.run(Futures.java:1319) 
> [guava-18.0.jar:na]
> at 
> com.google.common.util.concurrent.MoreExecutors$DirectExecutor.execute(MoreExecutors.java:457)
>  [guava-18.0.jar:na]
> at 
> com.google.common.util.concurrent.ExecutionList.executeListener(ExecutionList.java:156)
>  [guava-18.0.jar:na]
> at 
> com.google.common.util.concurrent.ExecutionList.add(ExecutionList.java:101) 
> [guava-18.0.jar:na]
> at 
> com.google.common.util.concurrent.AbstractFuture.addListener(AbstractFuture.java:170)
>  [guava-18.0.jar:na]
> at 
> com.google.common.util.concurrent.Futures.addCallback(Futures.java:1322) 
> [guava-18.0.jar:na]
> at 
> com.google.common.util.concurrent.Futures.addCallback(Futures.java:1258) 
> [guava-18.0.jar:na]
> at 
> org.apache.qpid.server.model.AbstractConfiguredObject.doAttainState(AbstractConfiguredObject.java:901)
>  [classes/:na]
> at 
> org.apache.qpid.server.model.AbstractConfiguredObject.access$300(AbstractConfiguredObject.java:80)
>  [classes/:na]
> at 
> org.apache.qpid.server.model.AbstractConfiguredObject$1.execute(AbstractConfiguredObject.java:513)
>  [classes/:na]
> at 
> org.apache.qpid.server.model.AbstractConfiguredObject$1.execute(AbstractConfiguredObject.java:500)
>  [classes/:na]
> at 
> org.apache.qpid.server.model.AbstractConfiguredObject$2.execute(AbstractConfiguredObject.java:561)
>  [classes/:na]
> at 
> org.apache.qpid.server.model.AbstractConfiguredObject$2.execute(AbstractConfiguredObject.java:554)
>  [classes/:na]
> at 
>

[jira] [Resolved] (QPID-7157) [Java Broker] Change metadata for management attributes having enum types to list all possible enum values in validValues property

2016-04-13 Thread Alex Rudyy (JIRA)


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

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

The changes look reasonable to me

> [Java Broker] Change metadata for management attributes having enum types to 
> list all possible enum values in validValues property
> --
>
> Key: QPID-7157
> URL: https://issues.apache.org/jira/browse/QPID-7157
> Project: Qpid
>  Issue Type: Improvement
>  Components: Java Broker
>Affects Versions: qpid-java-6.0.1
>Reporter: Alex Rudyy
>Assignee: Alex Rudyy
> Fix For: qpid-java-6.1
>
>
> metadata information should drive implementation of UI widgets for rendering 
> attribute values.We need to change metadata of attributes having  enum types 
> to list enum values in validValues property. That would allow creation of 
> widgets which can represent enum attribute editor as a "select" widget with 
> options containing all possible enum values 



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

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

[jira] [Updated] (QPID-7157) [Java Broker] Change metadata for management attributes having enum types to list all possible enum values in validValues property

2016-04-13 Thread Keith Wall (JIRA)


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

Keith Wall updated QPID-7157:
-
Assignee: Alex Rudyy  (was: Keith Wall)

> [Java Broker] Change metadata for management attributes having enum types to 
> list all possible enum values in validValues property
> --
>
> Key: QPID-7157
> URL: https://issues.apache.org/jira/browse/QPID-7157
> Project: Qpid
>  Issue Type: Improvement
>  Components: Java Broker
>Affects Versions: qpid-java-6.0.1
>Reporter: Alex Rudyy
>Assignee: Alex Rudyy
> Fix For: qpid-java-6.1
>
>
> metadata information should drive implementation of UI widgets for rendering 
> attribute values.We need to change metadata of attributes having  enum types 
> to list enum values in validValues property. That would allow creation of 
> widgets which can represent enum attribute editor as a "select" widget with 
> options containing all possible enum values 



--
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-7157) [Java Broker] Change metadata for management attributes having enum types to list all possible enum values in validValues property

2016-04-13 Thread Keith Wall (JIRA)


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

Keith Wall reassigned QPID-7157:


Assignee: Keith Wall

> [Java Broker] Change metadata for management attributes having enum types to 
> list all possible enum values in validValues property
> --
>
> Key: QPID-7157
> URL: https://issues.apache.org/jira/browse/QPID-7157
> Project: Qpid
>  Issue Type: Improvement
>  Components: Java Broker
>Affects Versions: qpid-java-6.0.1
>Reporter: Alex Rudyy
>Assignee: Keith Wall
> Fix For: qpid-java-6.1
>
>
> metadata information should drive implementation of UI widgets for rendering 
> attribute values.We need to change metadata of attributes having  enum types 
> to list enum values in validValues property. That would allow creation of 
> widgets which can represent enum attribute editor as a "select" widget with 
> options containing all possible enum values 



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

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

[jira] [Updated] (QPID-7157) [Java Broker] Change metadata for management attributes having enum types to list all possible enum values in validValues property

2016-04-13 Thread Keith Wall (JIRA)


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

Keith Wall updated QPID-7157:
-
Status: Reviewable  (was: In Progress)

> [Java Broker] Change metadata for management attributes having enum types to 
> list all possible enum values in validValues property
> --
>
> Key: QPID-7157
> URL: https://issues.apache.org/jira/browse/QPID-7157
> Project: Qpid
>  Issue Type: Improvement
>  Components: Java Broker
>Affects Versions: qpid-java-6.0.1
>Reporter: Alex Rudyy
>Assignee: Keith Wall
> Fix For: qpid-java-6.1
>
>
> metadata information should drive implementation of UI widgets for rendering 
> attribute values.We need to change metadata of attributes having  enum types 
> to list enum values in validValues property. That would allow creation of 
> widgets which can represent enum attribute editor as a "select" widget with 
> options containing all possible enum values 



--
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-7157) [Java Broker] Change metadata for management attributes having enum types to list all possible enum values in validValues property

2016-04-13 Thread ASF subversion and git services (JIRA)


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

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

Commit 1738906 from [~k-wall] in branch 'java/trunk'
[ https://svn.apache.org/r1738906 ]

QPID-7157: [Java Broker] Automatically populate valid values for attributes 
that are of an enumerated type, unless otherwise restricted.

> [Java Broker] Change metadata for management attributes having enum types to 
> list all possible enum values in validValues property
> --
>
> Key: QPID-7157
> URL: https://issues.apache.org/jira/browse/QPID-7157
> Project: Qpid
>  Issue Type: Improvement
>  Components: Java Broker
>Affects Versions: qpid-java-6.0.1
>Reporter: Alex Rudyy
> Fix For: qpid-java-6.1
>
>
> metadata information should drive implementation of UI widgets for rendering 
> attribute values.We need to change metadata of attributes having  enum types 
> to list enum values in validValues property. That would allow creation of 
> widgets which can represent enum attribute editor as a "select" widget with 
> options containing all possible enum values 



--
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

41 matches

Mail list logo