[GitHub] qpid-proton issue #98: PROTON-1434: add test blacklist to tox tests

[astitcher]

Github user astitcher commented on the issue:

https://github.com/apache/qpid-proton/pull/98
  
Looks like a good idea to me


---
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] (PROTON-1434) filter long-running python tests when running under tox

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on PROTON-1434:


Github user astitcher commented on the issue:

https://github.com/apache/qpid-proton/pull/98
  
Looks like a good idea to me


> filter long-running python tests when running under tox
> ---
>
> Key: PROTON-1434
> URL: https://issues.apache.org/jira/browse/PROTON-1434
> Project: Qpid Proton
>  Issue Type: Test
>  Components: python-binding
>Affects Versions: 0.17.0
>Reporter: Ken Giusti
>Assignee: Ken Giusti
>Priority: Trivial
> Fix For: 0.18.0
>
>
> Running the entire python test suite under tox is largely redundant - these 
> tests have already been run as the python-test suite.
> The tox tests should really just exercise the binding layer - not the full 
> functionality of proton.
> Let's pare down the number of tox tests executed by filtering the 
> longer-running system tests.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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

[jira] [Closed] (QPID-6855) [Web Socket AMQP 1.0 Client] Web socket AMQP 1.0 client cannot receive large binary frame exceeding default size for the binary frames set in jetty websocket library

[Keith Wall (JIRA)]

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

Keith Wall closed QPID-6855.

Resolution: Won't Fix

This client is no longer maintained.  Marking this JIRA as Won't Fix.  For a 
supported JMS client see:  https://qpid.apache.org/components/jms/

> [Web Socket AMQP 1.0 Client] Web socket AMQP 1.0 client cannot receive large 
> binary frame exceeding default size for the binary frames set in jetty 
> websocket library
> -
>
> Key: QPID-6855
> URL: https://issues.apache.org/jira/browse/QPID-6855
> Project: Qpid
>  Issue Type: Bug
>  Components: JMS AMQP 1.0 Client
>Affects Versions: 0.32
>Reporter: Alex Rudyy
>
> Web Socket AMQP 1.0 cannot receive WS binary frames of size greater then 
> default jetty max binary frame size (8192 B). Thus, it cannot be used with 
> 6.0 Java Broker as Broker WS layer was modified to send binary frames of any 
> size 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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

[jira] [Commented] (QPIDJMS-273) Unable to send more than 2048 messages (async + persistent)

[Rob Godfrey (JIRA)]

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

Rob Godfrey commented on QPIDJMS-273:
-

In the JMS client, doing a MessageProducer.close() waits for all outstanding 
async messages to be sent to the broker (and acknowledged?).  Doing a 
Connection.close(), in contrast, does not wait for outstanding transfers to be 
sent.  This may be by design, but should probably be documented somewhere if it 
is not already.

> Unable to send more than 2048 messages (async + persistent)
> ---
>
> Key: QPIDJMS-273
> URL: https://issues.apache.org/jira/browse/QPIDJMS-273
> Project: Qpid JMS
>  Issue Type: Bug
>  Components: qpid-jms-client
>Reporter: Antonin Vyborny
>Priority: Minor
>
> When I use jms.forceAsyncSend=True flag along with DeliveryMode.PERSISTENT I 
> am unable to receive more than 2048 messages in the queue. I am not receiving 
> any warning/error so from client it looks like all messages are sent, but 
> only 2048 messages are actually found in the queue.
> There is unfortunately nothing in the log either.
> Steps to reproduce: 
> 1) Use the Sender example (org.apache.qpid.jms.example.Sender)
> 2) Set the following in Sender class:
> private static final int DEFAULT_COUNT = 3000;
> private static final int DELIVERY_MODE = DeliveryMode.PERSISTENT;
> 3) Set async sending in jndi.properties:
> amqp://localhost:5672?jms.forceAsyncSend=True
> 4) run the example...



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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

[jira] [Moved] (QPIDJMS-273) Unable to send more than 2048 messages (async + persistent)

[Rob Godfrey (JIRA)]

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

Rob Godfrey moved QPID-7704 to QPIDJMS-273:
---

Affects Version/s: (was: qpid-java-6.1.1)
  Component/s: (was: Java Broker)
   qpid-jms-client
 Workflow: classic default workflow  (was: QPid Workflow)
  Key: QPIDJMS-273  (was: QPID-7704)
  Project: Qpid JMS  (was: Qpid)

> Unable to send more than 2048 messages (async + persistent)
> ---
>
> Key: QPIDJMS-273
> URL: https://issues.apache.org/jira/browse/QPIDJMS-273
> Project: Qpid JMS
>  Issue Type: Bug
>  Components: qpid-jms-client
>Reporter: Antonin Vyborny
>Priority: Minor
>
> When I use jms.forceAsyncSend=True flag along with DeliveryMode.PERSISTENT I 
> am unable to receive more than 2048 messages in the queue. I am not receiving 
> any warning/error so from client it looks like all messages are sent, but 
> only 2048 messages are actually found in the queue.
> There is unfortunately nothing in the log either.
> Steps to reproduce: 
> 1) Use the Sender example (org.apache.qpid.jms.example.Sender)
> 2) Set the following in Sender class:
> private static final int DEFAULT_COUNT = 3000;
> private static final int DELIVERY_MODE = DeliveryMode.PERSISTENT;
> 3) Set async sending in jndi.properties:
> amqp://localhost:5672?jms.forceAsyncSend=True
> 4) run the example...



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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

[jira] [Commented] (QPID-7704) Unable to send more than 2048 messages (async + persistent)

[Rob Godfrey (JIRA)]

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

Rob Godfrey commented on QPID-7704:
---

So having looked at this, it doesn't appear to be an issue in the Java Broker, 
but possibly in the JMS client instead.  To start off with I found that if I 
changed the number of messages sent I could get more messages to arrive in the 
broker (e.g. if I sent 9000 the broker received 4096, if I sent 1 I got 
5120 messages into the queue).

Then I turned on protocol level debugging and saw this...

{noformat}
2017-03-13 23:12:46,268 DEBUG [IO-/127.0.0.1:49435] (o.a.q.s.p.frame) - 
RECV[/127.0.0.1:49435|1] : 
Attach{name=qpid-jms:sender:ID:ba820261-32d3-4c23-a0d2-7adc2bd63db5:1:1:1:queue,handle=0,role=sender,sndSettleMode=unsettled,rcvSettleMode=first,source=Source{address=ID:ba820261-32d3-4c23-a0d2-7adc2bd63db5:1:1:1,durable=none,expiryPolicy=session-end,timeout=0,dynamic=false,outcomes=[amqp:accepted:list,
 amqp:rejected:list, amqp:released:list, 
amqp:modified:list]},target=Target{address=queue,durable=none,expiryPolicy=session-end,timeout=0,dynamic=false,capabilities=[queue]},incompleteUnsettled=false,initialDeliveryCount=0,desiredCapabilities=[DELAYED_DELIVERY]}
2017-03-13 23:12:46,273 DEBUG [IO-/127.0.0.1:49435] (o.a.q.s.p.frame) - 
SEND[/127.0.0.1:49435|1] : 
Attach{name=qpid-jms:sender:ID:ba820261-32d3-4c23-a0d2-7adc2bd63db5:1:1:1:queue,handle=0,role=receiver,sndSettleMode=unsettled,rcvSettleMode=first,source=Source{address=ID:ba820261-32d3-4c23-a0d2-7adc2bd63db5:1:1:1,durable=none,expiryPolicy=session-end,timeout=0,dynamic=false,outcomes=[amqp:accepted:list,
 amqp:rejected:list, amqp:released:list, 
amqp:modified:list]},target=Target{address=queue,dynamic=false,capabilities=[REJECT_UNROUTABLE,
 DELAYED_DELIVERY]},offeredCapabilities=[REJECT_UNROUTABLE, 
DELAYED_DELIVERY],properties={}}
2017-03-13 23:12:46,274 DEBUG [IO-/127.0.0.1:49435] (o.a.q.s.p.frame) - 
SEND[/127.0.0.1:49435|1] : 
Flow{nextIncomingId=1,incomingWindow=2048,nextOutgoingId=0,outgoingWindow=2048,handle=0,deliveryCount=0,linkCredit=2,echo=false}
{noformat}
...
{noformat}
2017-03-13 23:12:50,315 DEBUG [IO-/127.0.0.1:49435] (o.a.q.s.p.frame) - 
RECV[/127.0.0.1:49435|1] : 
Transfer{handle=0,deliveryId=1023,deliveryTag=32e,messageFormat=0}
2017-03-13 23:12:50,315 DEBUG [IO-/127.0.0.1:49435] (o.a.q.s.p.frame) - 
SEND[/127.0.0.1:49435|1] : 
Disposition{role=receiver,first=1023,last=1023,settled=true,state=Accepted{}}
2017-03-13 23:12:50,315 DEBUG [IO-/127.0.0.1:49435] (o.a.q.s.p.frame) - 
SEND[/127.0.0.1:49435|1] : 
Flow{nextIncomingId=1025,incomingWindow=2048,nextOutgoingId=0,outgoingWindow=2048}
2017-03-13 23:12:50,315 DEBUG [IO-/127.0.0.1:49435] (o.a.q.s.p.frame) - 
RECV[/127.0.0.1:49435|1] : 
Transfer{handle=0,deliveryId=1024,deliveryTag=32f,messageFormat=0}
2017-03-13 23:12:50,316 DEBUG [IO-/127.0.0.1:49435] (o.a.q.s.p.frame) - 
SEND[/127.0.0.1:49435|1] : 
Disposition{role=receiver,first=1024,last=1024,settled=true,state=Accepted{}}
{noformat}
...
{noformat}
2017-03-13 23:12:52,253 DEBUG [IO-/127.0.0.1:49435] (o.a.q.s.p.frame) - 
RECV[/127.0.0.1:49435|1] : 
Transfer{handle=0,deliveryId=2046,deliveryTag=72d,messageFormat=0}
2017-03-13 23:12:52,254 DEBUG [IO-/127.0.0.1:49435] (o.a.q.s.p.frame) - 
SEND[/127.0.0.1:49435|1] : 
Disposition{role=receiver,first=2046,last=2046,settled=true,state=Accepted{}}
2017-03-13 23:12:52,254 DEBUG [IO-/127.0.0.1:49435] (o.a.q.s.p.frame) - 
RECV[/127.0.0.1:49435|1] : 
Transfer{handle=0,deliveryId=2047,deliveryTag=72e,messageFormat=0}
2017-03-13 23:12:52,254 DEBUG [IO-/127.0.0.1:49435] (o.a.q.s.p.frame) - 
SEND[/127.0.0.1:49435|1] : 
Disposition{role=receiver,first=2047,last=2047,settled=true,state=Accepted{}}
2017-03-13 23:12:52,254 DEBUG [IO-/127.0.0.1:49435] (o.a.q.s.p.frame) - 
SEND[/127.0.0.1:49435|1] : 
Flow{nextIncomingId=2049,incomingWindow=2048,nextOutgoingId=0,outgoingWindow=2048}
2017-03-13 23:12:52,254 DEBUG [IO-/127.0.0.1:49435] (o.a.q.s.p.frame) - 
RECV[/127.0.0.1:49435|0] : Close{}
2017-03-13 23:12:52,267 INFO  [IO-/127.0.0.1:49435] (q.m.c.close) - 
[con:14(admin@/127.0.0.1:49435/default)/ch:0] 
[con:14(admin@/127.0.0.1:49435/default)/ch:0] CHN-1003 : Close
{noformat}

So we see that the broker initially gives 2048 of session credit, then when it 
has received 1024 messages, it opens the window up again (incoming_window = 
2048, so it can send *another* 2048 frames on top of the 1024 it sent 
already)... then after it has received 2048 messages it opens up the window 
again...  However at that point the client simply closes the connection.

If, prior to doing the connection.close() you explicitly close the message 
producer, then the broker receives all the messages.

I'm going to move this JIRA over to the JMS client JIRA system so they can 
decide whether this is a bug, or working as designed :-).


> Unable to send more than 2048 messages (async + 

[jira] [Commented] (PROTON-1434) filter long-running python tests when running under tox

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on PROTON-1434:


GitHub user kgiusti opened a pull request:

https://github.com/apache/qpid-proton/pull/98

PROTON-1434: add test blacklist to tox tests

Helps speed up the time spent running the tox tests

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

$ git pull https://github.com/kgiusti/qpid-proton PROTON-1434

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

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


commit 8b7a565aa21f5b628a12eb725e95f5bf67536000
Author: Kenneth Giusti 
Date:   2017-03-08T16:44:23Z

PROTON-1434: add test blacklist to tox tests




> filter long-running python tests when running under tox
> ---
>
> Key: PROTON-1434
> URL: https://issues.apache.org/jira/browse/PROTON-1434
> Project: Qpid Proton
>  Issue Type: Test
>  Components: python-binding
>Affects Versions: 0.17.0
>Reporter: Ken Giusti
>Assignee: Ken Giusti
>Priority: Trivial
> Fix For: 0.18.0
>
>
> Running the entire python test suite under tox is largely redundant - these 
> tests have already been run as the python-test suite.
> The tox tests should really just exercise the binding layer - not the full 
> functionality of proton.
> Let's pare down the number of tox tests executed by filtering the 
> longer-running system tests.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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

[GitHub] qpid-proton pull request #98: PROTON-1434: add test blacklist to tox tests

[kgiusti]

GitHub user kgiusti opened a pull request:

https://github.com/apache/qpid-proton/pull/98

PROTON-1434: add test blacklist to tox tests

Helps speed up the time spent running the tox tests

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

$ git pull https://github.com/kgiusti/qpid-proton PROTON-1434

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

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


commit 8b7a565aa21f5b628a12eb725e95f5bf67536000
Author: Kenneth Giusti 
Date:   2017-03-08T16:44:23Z

PROTON-1434: add test blacklist to tox tests




---
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] [Resolved] (PROTON-1345) [python] Avoid hardcoding the list of C files to be compiled in setup.py

[Ken Giusti (JIRA)]

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

Ken Giusti resolved PROTON-1345.

Resolution: Fixed

> [python] Avoid hardcoding the list of C files to be compiled in setup.py
> 
>
> Key: PROTON-1345
> URL: https://issues.apache.org/jira/browse/PROTON-1345
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: python-binding
>Affects Versions: 0.15.0
>Reporter: Ken Giusti
>Assignee: Ken Giusti
> Fix For: 0.18.0
>
>
> Remove the hardcoded list of C source files in the setup.py file.  It's easy 
> to forget to update this list, and debugging the resulting tox build failure 
> is tricky.
> Instead have the setup.py discover all the necessary C source files using an 
> regex.  Add an explicit blacklist for those C source files that shouldn't be 
> built by the setup.py process (if there actually is any).



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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

[jira] [Commented] (PROTON-1345) [python] Avoid hardcoding the list of C files to be compiled in setup.py

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on PROTON-1345:


Github user asfgit closed the pull request at:

https://github.com/apache/qpid-proton/pull/97


> [python] Avoid hardcoding the list of C files to be compiled in setup.py
> 
>
> Key: PROTON-1345
> URL: https://issues.apache.org/jira/browse/PROTON-1345
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: python-binding
>Affects Versions: 0.15.0
>Reporter: Ken Giusti
>Assignee: Ken Giusti
> Fix For: 0.18.0
>
>
> Remove the hardcoded list of C source files in the setup.py file.  It's easy 
> to forget to update this list, and debugging the resulting tox build failure 
> is tricky.
> Instead have the setup.py discover all the necessary C source files using an 
> regex.  Add an explicit blacklist for those C source files that shouldn't be 
> built by the setup.py process (if there actually is any).



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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

[jira] [Commented] (PROTON-1345) [python] Avoid hardcoding the list of C files to be compiled in setup.py

[ASF subversion and git services (JIRA)]

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

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

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

PROTON-1345: update setup.py.in with libuv and cmake source list

This closes #97


> [python] Avoid hardcoding the list of C files to be compiled in setup.py
> 
>
> Key: PROTON-1345
> URL: https://issues.apache.org/jira/browse/PROTON-1345
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: python-binding
>Affects Versions: 0.15.0
>Reporter: Ken Giusti
>Assignee: Ken Giusti
> Fix For: 0.18.0
>
>
> Remove the hardcoded list of C source files in the setup.py file.  It's easy 
> to forget to update this list, and debugging the resulting tox build failure 
> is tricky.
> Instead have the setup.py discover all the necessary C source files using an 
> regex.  Add an explicit blacklist for those C source files that shouldn't be 
> built by the setup.py process (if there actually is any).



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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

[GitHub] qpid-proton pull request #97: PROTON-1345: update setup.py.in with libuv and...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/qpid-proton/pull/97


---
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] [Resolved] (DISPATCH-622) use "-lpthread" instead of "-pthread" as compiler error to avoid undefined symbol on Solaris

[Ganesh Murthy (JIRA)]

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

Ganesh Murthy resolved DISPATCH-622.

   Resolution: Fixed
Fix Version/s: 0.8.0

> use "-lpthread" instead of "-pthread" as compiler error to avoid undefined 
> symbol on Solaris
> 
>
> Key: DISPATCH-622
> URL: https://issues.apache.org/jira/browse/DISPATCH-622
> Project: Qpid Dispatch
>  Issue Type: Bug
>Affects Versions: 0.7.0
>Reporter: Adel Boutros
>Assignee: Ganesh Murthy
> Fix For: 0.8.0
>
> Attachments: 
> 0012-use-lpthread-instead-of-pthread-as-compiler-error-to.patch
>
>
> Undefined symbol _mcount : CMakeFiles/qpid-dispatch.dir/bitmask.c.o



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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

[jira] [Assigned] (DISPATCH-622) use "-lpthread" instead of "-pthread" as compiler error to avoid undefined symbol on Solaris

[Ganesh Murthy (JIRA)]

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

Ganesh Murthy reassigned DISPATCH-622:
--

Assignee: Ganesh Murthy

> use "-lpthread" instead of "-pthread" as compiler error to avoid undefined 
> symbol on Solaris
> 
>
> Key: DISPATCH-622
> URL: https://issues.apache.org/jira/browse/DISPATCH-622
> Project: Qpid Dispatch
>  Issue Type: Bug
>Affects Versions: 0.7.0
>Reporter: Adel Boutros
>Assignee: Ganesh Murthy
> Fix For: 0.8.0
>
> Attachments: 
> 0012-use-lpthread-instead-of-pthread-as-compiler-error-to.patch
>
>
> Undefined symbol _mcount : CMakeFiles/qpid-dispatch.dir/bitmask.c.o



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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

[jira] [Commented] (DISPATCH-622) use "-lpthread" instead of "-pthread" as compiler error to avoid undefined symbol on Solaris

[ASF subversion and git services (JIRA)]

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

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

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

DISPATCH-622 - Use -lpthread compile option for Solaris


> use "-lpthread" instead of "-pthread" as compiler error to avoid undefined 
> symbol on Solaris
> 
>
> Key: DISPATCH-622
> URL: https://issues.apache.org/jira/browse/DISPATCH-622
> Project: Qpid Dispatch
>  Issue Type: Bug
>Affects Versions: 0.7.0
>Reporter: Adel Boutros
> Attachments: 
> 0012-use-lpthread-instead-of-pthread-as-compiler-error-to.patch
>
>
> Undefined symbol _mcount : CMakeFiles/qpid-dispatch.dir/bitmask.c.o



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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

[GitHub] qpid-cpp pull request #3: QPID-7702: use SWIG_fail instead of returning on e...

[kgiusti]

GitHub user kgiusti opened a pull request:

https://github.com/apache/qpid-cpp/pull/3

QPID-7702: use SWIG_fail instead of returning on error

This change should prevent many of the wrapper-related resource leaks found 
by Coverity.

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

$ git pull https://github.com/kgiusti/qpid-cpp QPID-7702

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

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


commit 5fa92f8515fd63b7e0eecfb43b26b21dd62a401d
Author: Kenneth Giusti 
Date:   2017-03-13T19:07:25Z

QPID-7702: use SWIG_fail instead of returning on error




---
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] (QPID-7702) Use of 'return NULL' in swig binding leaks memory

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on QPID-7702:
--

GitHub user kgiusti opened a pull request:

https://github.com/apache/qpid-cpp/pull/3

QPID-7702: use SWIG_fail instead of returning on error

This change should prevent many of the wrapper-related resource leaks found 
by Coverity.

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

$ git pull https://github.com/kgiusti/qpid-cpp QPID-7702

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

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


commit 5fa92f8515fd63b7e0eecfb43b26b21dd62a401d
Author: Kenneth Giusti 
Date:   2017-03-13T19:07:25Z

QPID-7702: use SWIG_fail instead of returning on error




> Use of 'return NULL' in swig binding leaks memory
> -
>
> Key: QPID-7702
> URL: https://issues.apache.org/jira/browse/QPID-7702
> Project: Qpid
>  Issue Type: Bug
>  Components: C++ Client
>Affects Versions: qpid-cpp-1.36.0
>Reporter: Ken Giusti
>Assignee: Ken Giusti
>Priority: Minor
> Fix For: qpid-cpp-1.37.0
>
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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

[jira] [Resolved] (DISPATCH-612) Add support for GCC equivalent compiler options

[Ganesh Murthy (JIRA)]

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

Ganesh Murthy resolved DISPATCH-612.

   Resolution: Fixed
Fix Version/s: 0.8.0

> Add support for GCC equivalent compiler options
> ---
>
> Key: DISPATCH-612
> URL: https://issues.apache.org/jira/browse/DISPATCH-612
> Project: Qpid Dispatch
>  Issue Type: Bug
>Affects Versions: 0.7.0
>Reporter: Adel Boutros
>Assignee: Ganesh Murthy
> Fix For: 0.8.0
>
> Attachments: 
> 0002-Add-support-for-GCC-equivalent-compiler-options.patch
>
>
> Some compiler flags used are only for GCC



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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

[jira] [Commented] (DISPATCH-612) Add support for GCC equivalent compiler options

[ASF subversion and git services (JIRA)]

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

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

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

DISPATCH-612 - Add support for GCC equivalent compiler options


> Add support for GCC equivalent compiler options
> ---
>
> Key: DISPATCH-612
> URL: https://issues.apache.org/jira/browse/DISPATCH-612
> Project: Qpid Dispatch
>  Issue Type: Bug
>Affects Versions: 0.7.0
>Reporter: Adel Boutros
>Assignee: Ganesh Murthy
> Fix For: 0.8.0
>
> Attachments: 
> 0002-Add-support-for-GCC-equivalent-compiler-options.patch
>
>
> Some compiler flags used are only for GCC



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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

[jira] [Assigned] (DISPATCH-612) Add support for GCC equivalent compiler options

[Ganesh Murthy (JIRA)]

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

Ganesh Murthy reassigned DISPATCH-612:
--

Assignee: Ganesh Murthy

> Add support for GCC equivalent compiler options
> ---
>
> Key: DISPATCH-612
> URL: https://issues.apache.org/jira/browse/DISPATCH-612
> Project: Qpid Dispatch
>  Issue Type: Bug
>Affects Versions: 0.7.0
>Reporter: Adel Boutros
>Assignee: Ganesh Murthy
> Attachments: 
> 0002-Add-support-for-GCC-equivalent-compiler-options.patch
>
>
> Some compiler flags used are only for GCC



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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

[jira] [Created] (QPID-7704) Unable to send more than 2048 messages (async + persistent)

[Antonin Vyborny (JIRA)]

Antonin Vyborny created QPID-7704:
-

 Summary: Unable to send more than 2048 messages (async + 
persistent)
 Key: QPID-7704
 URL: https://issues.apache.org/jira/browse/QPID-7704
 Project: Qpid
  Issue Type: Bug
  Components: Java Broker
Affects Versions: qpid-java-6.1.1
Reporter: Antonin Vyborny
Priority: Minor


When I use jms.forceAsyncSend=True flag along with DeliveryMode.PERSISTENT I am 
unable to receive more than 2048 messages in the queue. I am not receiving any 
warning/error so from client it looks like all messages are sent, but only 2048 
messages are actually found in the queue.
There is unfortunately nothing in the log either.

Steps to reproduce: 
1) Use the Sender example (org.apache.qpid.jms.example.Sender)
2) Set the following in Sender class:
private static final int DEFAULT_COUNT = 3000;
private static final int DELIVERY_MODE = DeliveryMode.PERSISTENT;
3) Set async sending in jndi.properties:
amqp://localhost:5672?jms.forceAsyncSend=True
4) run the example...





--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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

[jira] [Created] (QPID-7703) [Java Broker] 'Unbind' privilege is not checked for removal of queue bindings on queue deletion

[Alex Rudyy (JIRA)]

Alex Rudyy created QPID-7703:


 Summary: [Java Broker] 'Unbind' privilege is not checked  for 
removal of queue bindings on queue deletion
 Key: QPID-7703
 URL: https://issues.apache.org/jira/browse/QPID-7703
 Project: Qpid
  Issue Type: Bug
  Components: Java Broker
Affects Versions: qpid-java-broker-7.0.0
Reporter: Alex Rudyy


As part of  changes in QPID-6028 the queue binding implementation was changed 
and responsibilities to create and remove bindings were moved into Exchange 
operations 'bind' and 'unbind' accordingly.  The exchanges are now responsible 
for performing authorization checks for  'bind' and 'unbind' operations. 
However, on queue deletion, the queue bindings are removed without performing 
'unbind' authorization checks which is a change in behaviour comparing with 
previous 6.x releases. We need to decide whether we  need to restore previous 
behaviour and enforce 'unbind' ACL check on queue deletion or keep existing 
functionality.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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

[jira] [Commented] (DISPATCH-614) strerror_r on Solaris does not return char*

[Ganesh Murthy (JIRA)]

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

Ganesh Murthy commented on DISPATCH-614:


Commit 610739ff529adc295892390294b6cfdb87f84602 got rid of the line

static inline void ignore_result(char* ignored) {}

On an unrelated note, src/posix/driver.c does have an int as a parameter to  
ignore_result

static inline void ignore_result(int unused_result) {
(void) unused_result;
}

> strerror_r on Solaris does not return char*
> ---
>
> Key: DISPATCH-614
> URL: https://issues.apache.org/jira/browse/DISPATCH-614
> Project: Qpid Dispatch
>  Issue Type: Bug
>Affects Versions: 0.7.0
>Reporter: Adel Boutros
>Assignee: Ganesh Murthy
> Fix For: 0.8.0
>
> Attachments: 0004-strerror_r-on-Solaris-does-not-return-char.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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

[jira] [Resolved] (DISPATCH-614) strerror_r on Solaris does not return char*

[Ganesh Murthy (JIRA)]

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

Ganesh Murthy resolved DISPATCH-614.

   Resolution: Fixed
Fix Version/s: 0.8.0

> strerror_r on Solaris does not return char*
> ---
>
> Key: DISPATCH-614
> URL: https://issues.apache.org/jira/browse/DISPATCH-614
> Project: Qpid Dispatch
>  Issue Type: Bug
>Affects Versions: 0.7.0
>Reporter: Adel Boutros
>Assignee: Ganesh Murthy
> Fix For: 0.8.0
>
> Attachments: 0004-strerror_r-on-Solaris-does-not-return-char.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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

[jira] [Commented] (QPID-7696) [Java Broker] Deletion of a temporary queue can crash the broker with certain ACLs

[ASF subversion and git services (JIRA)]

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

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

Commit 1786743 from oru...@apache.org in branch 'java/branches/6.1.x'
[ https://svn.apache.org/r1786743 ]

QPID-7696: Check whether actor invoking  queue delete operation has 'unbind' 
privilege for queue bindings before proceeding with queue deletion

> [Java Broker] Deletion of a temporary queue can crash the broker with certain 
> ACLs
> --
>
> Key: QPID-7696
> URL: https://issues.apache.org/jira/browse/QPID-7696
> Project: Qpid
>  Issue Type: Bug
>  Components: Java Broker
>Affects Versions: qpid-java-6.1.1
>Reporter: Lorenz Quack
> Fix For: qpid-java-6.1.2
>
>
> ACL:
> {noformat}
> ACL ALLOW-LOG testUser CREATE QUEUE temporary="true"
> ACL ALLOW-LOG testUser DELETE QUEUE temporary="true"
> ACL ALLOW-LOG testUser ACCESS ALL
> ACL ALLOW-LOG admin ALL ALL
> ACL DENY-LOG ALL ALL
> {noformat}
> client code:
> {code}
> /* create connection */
> Session session = connection.createSession(true, 
> Session.SESSION_TRANSACTED);
> TemporaryQueue temporaryQueue = session.createTemporaryQueue();
> temporaryQueue.delete();
>/* cleanup */
> {code}
> This crashes the broker v6.1.1
> {noformat}
> 
> #
> # Unhandled Exception java.security.AccessControlException: Permission DELETE 
> is denied for : Binding 'TempQueuec64ba00d-9b7c-44f2-9217-80c954234ce4' on 
> Queue 'TempQueuec64ba00d-9b7c-44f2-9217-80c954234ce4' Exchange 'amq.direct' 
> in Thread IO-/127.0.0.1:53477
> #
> # Exiting
> #
> 
> java.security.AccessControlException: Permission DELETE is denied for : 
> Binding 'TempQueuec64ba00d-9b7c-44f2-9217-80c954234ce4' on Queue 
> 'TempQueuec64ba00d-9b7c-44f2-9217-80c954234ce4' Exchange 'amq.direct'
>   at 
> org.apache.qpid.server.model.AbstractConfiguredObject.authorise(AbstractConfiguredObject.java:2959)
>   at 
> org.apache.qpid.server.model.AbstractConfiguredObject.authorise(AbstractConfiguredObject.java:2891)
>   at 
> org.apache.qpid.server.model.AbstractConfiguredObject.authoriseSetAttributes(AbstractConfiguredObject.java:2970)
>   at 
> org.apache.qpid.server.model.AbstractConfiguredObject$15.execute(AbstractConfiguredObject.java:1659)
>   at 
> org.apache.qpid.server.model.AbstractConfiguredObject$15.execute(AbstractConfiguredObject.java:1629)
>   at 
> org.apache.qpid.server.model.AbstractConfiguredObject$2.execute(AbstractConfiguredObject.java:632)
>   at 
> org.apache.qpid.server.model.AbstractConfiguredObject$2.execute(AbstractConfiguredObject.java:625)
>   at 
> org.apache.qpid.server.configuration.updater.TaskExecutorImpl$TaskLoggingWrapper.execute(TaskExecutorImpl.java:240)
>   at 
> org.apache.qpid.server.configuration.updater.TaskExecutorImpl$CallableWrapper$1.run(TaskExecutorImpl.java:312)
>   at java.security.AccessController.doPrivileged(Native Method)
>   at javax.security.auth.Subject.doAs(Subject.java:360)
>   at 
> org.apache.qpid.server.configuration.updater.TaskExecutorImpl$CallableWrapper.call(TaskExecutorImpl.java:305)
>   at java.util.concurrent.FutureTask.run(FutureTask.java:266)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>   at java.lang.Thread.run(Thread.java:745)
> Process finished with exit code 1
> {noformat}
> I have not tested with other versions of the broker, yet.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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

[jira] [Resolved] (QPIDIT-56) Rhea installs to /usr/lib regardless of cmake install dir

[Kim van der Riet (JIRA)]

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

Kim van der Riet resolved QPIDIT-56.

Resolution: Fixed

> Rhea installs to /usr/lib regardless of cmake install dir
> -
>
> Key: QPIDIT-56
> URL: https://issues.apache.org/jira/browse/QPIDIT-56
> Project: Apache QPID IT
>  Issue Type: Bug
>  Components: Rhea JavaScript Shim
> Environment: Fedora 23 x64, bash
>Reporter: Chuck Rolke
>Assignee: Kim van der Riet
>
> {noformat}
> export INSTALLPREFIX=/opt/local
> cd ${QPID_INTEROP_TEST_HOME}/build
> cmake -DCMAKE_BUILD_TYPE=Debug \
>   -DCMAKE_INSTALL_PREFIX=${INSTALLPREFIX} \
>   -DPROTON_INSTALL_DIR=${INSTALLPREFIX} \
>   ..
> {noformat}
> Fails when npm can't create a directory in /usr/lib
> {noformat}
> npm ERR! Error: EACCES, mkdir '/usr/lib/node_modules/rhea'
> npm ERR!  { [Error: EACCES, mkdir '/usr/lib/node_modules/rhea']
> npm ERR!   errno: 3,
> npm ERR!   code: 'EACCES',
> npm ERR!   path: '/usr/lib/node_modules/rhea',
> npm ERR!   fstream_type: 'Directory',
> npm ERR!   fstream_path: '/usr/lib/node_modules/rhea',
> npm ERR!   fstream_class: 'DirWriter',
> npm ERR!   fstream_stack: 
> npm ERR![ '/usr/lib/node_modules/fstream/lib/dir-writer.js:36:23',
> npm ERR!  '/usr/lib/node_modules/mkdirp/index.js:37:53',
> npm ERR!  'Object.oncomplete (fs.js:108:15)' ] }
> npm ERR! 
> npm ERR! Please try running this command again as root/Administrator.
> {noformat}
> My policy is to never run local builds as root. I have /opt/local set up as 
> the target workspace for my local installs. Typically I build/install
> * qpid-proton
> * qpid-python
> * qpid-cpp
> * qpid-dispatch
> * qpid-interop-test



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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

[jira] [Created] (QPID-7702) Use of 'return NULL' in swig binding leaks memory

[Ken Giusti (JIRA)]

Ken Giusti created QPID-7702:


 Summary: Use of 'return NULL' in swig binding leaks memory
 Key: QPID-7702
 URL: https://issues.apache.org/jira/browse/QPID-7702
 Project: Qpid
  Issue Type: Bug
  Components: C++ Client
Affects Versions: qpid-cpp-1.36.0
Reporter: Ken Giusti
Assignee: Ken Giusti
Priority: Minor
 Fix For: qpid-cpp-1.37.0






--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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

[jira] [Commented] (QPIDIT-56) Rhea installs to /usr/lib regardless of cmake install dir

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on QPIDIT-56:
---

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

QPIDIT-56: Additional improvements for handling local folder containing Rhea


> Rhea installs to /usr/lib regardless of cmake install dir
> -
>
> Key: QPIDIT-56
> URL: https://issues.apache.org/jira/browse/QPIDIT-56
> Project: Apache QPID IT
>  Issue Type: Bug
>  Components: Rhea JavaScript Shim
> Environment: Fedora 23 x64, bash
>Reporter: Chuck Rolke
>Assignee: Kim van der Riet
>
> {noformat}
> export INSTALLPREFIX=/opt/local
> cd ${QPID_INTEROP_TEST_HOME}/build
> cmake -DCMAKE_BUILD_TYPE=Debug \
>   -DCMAKE_INSTALL_PREFIX=${INSTALLPREFIX} \
>   -DPROTON_INSTALL_DIR=${INSTALLPREFIX} \
>   ..
> {noformat}
> Fails when npm can't create a directory in /usr/lib
> {noformat}
> npm ERR! Error: EACCES, mkdir '/usr/lib/node_modules/rhea'
> npm ERR!  { [Error: EACCES, mkdir '/usr/lib/node_modules/rhea']
> npm ERR!   errno: 3,
> npm ERR!   code: 'EACCES',
> npm ERR!   path: '/usr/lib/node_modules/rhea',
> npm ERR!   fstream_type: 'Directory',
> npm ERR!   fstream_path: '/usr/lib/node_modules/rhea',
> npm ERR!   fstream_class: 'DirWriter',
> npm ERR!   fstream_stack: 
> npm ERR![ '/usr/lib/node_modules/fstream/lib/dir-writer.js:36:23',
> npm ERR!  '/usr/lib/node_modules/mkdirp/index.js:37:53',
> npm ERR!  'Object.oncomplete (fs.js:108:15)' ] }
> npm ERR! 
> npm ERR! Please try running this command again as root/Administrator.
> {noformat}
> My policy is to never run local builds as root. I have /opt/local set up as 
> the target workspace for my local installs. Typically I build/install
> * qpid-proton
> * qpid-python
> * qpid-cpp
> * qpid-dispatch
> * qpid-interop-test



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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

[jira] [Assigned] (DISPATCH-614) strerror_r on Solaris does not return char*

[Ganesh Murthy (JIRA)]

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

Ganesh Murthy reassigned DISPATCH-614:
--

Assignee: Ganesh Murthy

> strerror_r on Solaris does not return char*
> ---
>
> Key: DISPATCH-614
> URL: https://issues.apache.org/jira/browse/DISPATCH-614
> Project: Qpid Dispatch
>  Issue Type: Bug
>Affects Versions: 0.7.0
>Reporter: Adel Boutros
>Assignee: Ganesh Murthy
> Attachments: 0004-strerror_r-on-Solaris-does-not-return-char.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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

[jira] [Created] (DISPATCH-726) Connection Property for Failover Servers

[Ted Ross (JIRA)]

Ted Ross created DISPATCH-726:
-

 Summary: Connection Property for Failover Servers
 Key: DISPATCH-726
 URL: https://issues.apache.org/jira/browse/DISPATCH-726
 Project: Qpid Dispatch
  Issue Type: New Feature
  Components: Container
Reporter: Ted Ross
Assignee: Ted Ross
 Fix For: 0.8.0


Qpid Dispatch Router should be configurable to supply a failover list in the 
connection properties such that clients (like the Qpid JMS client) can have a 
list of alternate hosts and ports to connect to should the router connection 
fail.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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

[jira] [Comment Edited] (QPID-7696) [Java Broker] Deletion of a temporary queue can crash the broker with certain ACLs

[Alex Rudyy (JIRA)]

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

Alex Rudyy edited comment on QPID-7696 at 3/13/17 5:16 PM:
---

The absence of ACL UNBIND permission causes queue deletion to fail with 
AccessControlException. The deleted flag of queue is set into true and deleted 
future is set to  AccessControlException. When connection is closed an attempt 
is made to delete the queue from connection post close task using system 
principal, but because both deleted flag and deleted future are set already, 
the previous deleted future is returned with AccessControlException, and the 
exception is re-thrown from connection post close task. Because exception is 
not handled, it crushes the broker


was (Author: alex.rufous):
The absence of ACL UNBIND permission causes queue deletion to fail with 
AccessControlException. The deleted flag of queue is set into true and deleted 
future is set to  AccessControlException. When connection is closed an attempt 
is made to delete the queue from connection post close task using system 
principal, but because both deleted flag and deleted future are set already, 
the previous deleted future is returned with AccessControlException, and the 
exception is re-thrown from connection post close task. Because exception is 
not handled, it crashes the broker

> [Java Broker] Deletion of a temporary queue can crash the broker with certain 
> ACLs
> --
>
> Key: QPID-7696
> URL: https://issues.apache.org/jira/browse/QPID-7696
> Project: Qpid
>  Issue Type: Bug
>  Components: Java Broker
>Affects Versions: qpid-java-6.1.1
>Reporter: Lorenz Quack
> Fix For: qpid-java-6.1.2
>
>
> ACL:
> {noformat}
> ACL ALLOW-LOG testUser CREATE QUEUE temporary="true"
> ACL ALLOW-LOG testUser DELETE QUEUE temporary="true"
> ACL ALLOW-LOG testUser ACCESS ALL
> ACL ALLOW-LOG admin ALL ALL
> ACL DENY-LOG ALL ALL
> {noformat}
> client code:
> {code}
> /* create connection */
> Session session = connection.createSession(true, 
> Session.SESSION_TRANSACTED);
> TemporaryQueue temporaryQueue = session.createTemporaryQueue();
> temporaryQueue.delete();
>/* cleanup */
> {code}
> This crashes the broker v6.1.1
> {noformat}
> 
> #
> # Unhandled Exception java.security.AccessControlException: Permission DELETE 
> is denied for : Binding 'TempQueuec64ba00d-9b7c-44f2-9217-80c954234ce4' on 
> Queue 'TempQueuec64ba00d-9b7c-44f2-9217-80c954234ce4' Exchange 'amq.direct' 
> in Thread IO-/127.0.0.1:53477
> #
> # Exiting
> #
> 
> java.security.AccessControlException: Permission DELETE is denied for : 
> Binding 'TempQueuec64ba00d-9b7c-44f2-9217-80c954234ce4' on Queue 
> 'TempQueuec64ba00d-9b7c-44f2-9217-80c954234ce4' Exchange 'amq.direct'
>   at 
> org.apache.qpid.server.model.AbstractConfiguredObject.authorise(AbstractConfiguredObject.java:2959)
>   at 
> org.apache.qpid.server.model.AbstractConfiguredObject.authorise(AbstractConfiguredObject.java:2891)
>   at 
> org.apache.qpid.server.model.AbstractConfiguredObject.authoriseSetAttributes(AbstractConfiguredObject.java:2970)
>   at 
> org.apache.qpid.server.model.AbstractConfiguredObject$15.execute(AbstractConfiguredObject.java:1659)
>   at 
> org.apache.qpid.server.model.AbstractConfiguredObject$15.execute(AbstractConfiguredObject.java:1629)
>   at 
> org.apache.qpid.server.model.AbstractConfiguredObject$2.execute(AbstractConfiguredObject.java:632)
>   at 
> org.apache.qpid.server.model.AbstractConfiguredObject$2.execute(AbstractConfiguredObject.java:625)
>   at 
> org.apache.qpid.server.configuration.updater.TaskExecutorImpl$TaskLoggingWrapper.execute(TaskExecutorImpl.java:240)
>   at 
> org.apache.qpid.server.configuration.updater.TaskExecutorImpl$CallableWrapper$1.run(TaskExecutorImpl.java:312)
>   at java.security.AccessController.doPrivileged(Native Method)
>   at javax.security.auth.Subject.doAs(Subject.java:360)
>   at 
> org.apache.qpid.server.configuration.updater.TaskExecutorImpl$CallableWrapper.call(TaskExecutorImpl.java:305)
>   at java.util.concurrent.FutureTask.run(FutureTask.java:266)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>   at java.lang.Thread.run(Thread.java:745)
> Process finished with exit code 1
> {noformat}
> I have not tested with other versions of the broker, yet.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (QPID-7696) [Java Broker] Deletion of a temporary queue can crash the broker with certain ACLs

[Alex Rudyy (JIRA)]

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

Alex Rudyy commented on QPID-7696:
--

The absence of ACL UNBIND permission causes queue deletion to fail with 
AccessControlException. The deleted flag of queue is set into true and deleted 
future is set to  AccessControlException. When connection is closed an attempt 
is made to delete the queue from connection post close task using system 
principal, but because both deleted flag and deleted future are set already, 
the previous deleted future is returned with AccessControlException, and the 
exception is re-thrown from connection post close task. Because exception is 
not handled, it crashes the broker

> [Java Broker] Deletion of a temporary queue can crash the broker with certain 
> ACLs
> --
>
> Key: QPID-7696
> URL: https://issues.apache.org/jira/browse/QPID-7696
> Project: Qpid
>  Issue Type: Bug
>  Components: Java Broker
>Affects Versions: qpid-java-6.1.1
>Reporter: Lorenz Quack
> Fix For: qpid-java-6.1.2
>
>
> ACL:
> {noformat}
> ACL ALLOW-LOG testUser CREATE QUEUE temporary="true"
> ACL ALLOW-LOG testUser DELETE QUEUE temporary="true"
> ACL ALLOW-LOG testUser ACCESS ALL
> ACL ALLOW-LOG admin ALL ALL
> ACL DENY-LOG ALL ALL
> {noformat}
> client code:
> {code}
> /* create connection */
> Session session = connection.createSession(true, 
> Session.SESSION_TRANSACTED);
> TemporaryQueue temporaryQueue = session.createTemporaryQueue();
> temporaryQueue.delete();
>/* cleanup */
> {code}
> This crashes the broker v6.1.1
> {noformat}
> 
> #
> # Unhandled Exception java.security.AccessControlException: Permission DELETE 
> is denied for : Binding 'TempQueuec64ba00d-9b7c-44f2-9217-80c954234ce4' on 
> Queue 'TempQueuec64ba00d-9b7c-44f2-9217-80c954234ce4' Exchange 'amq.direct' 
> in Thread IO-/127.0.0.1:53477
> #
> # Exiting
> #
> 
> java.security.AccessControlException: Permission DELETE is denied for : 
> Binding 'TempQueuec64ba00d-9b7c-44f2-9217-80c954234ce4' on Queue 
> 'TempQueuec64ba00d-9b7c-44f2-9217-80c954234ce4' Exchange 'amq.direct'
>   at 
> org.apache.qpid.server.model.AbstractConfiguredObject.authorise(AbstractConfiguredObject.java:2959)
>   at 
> org.apache.qpid.server.model.AbstractConfiguredObject.authorise(AbstractConfiguredObject.java:2891)
>   at 
> org.apache.qpid.server.model.AbstractConfiguredObject.authoriseSetAttributes(AbstractConfiguredObject.java:2970)
>   at 
> org.apache.qpid.server.model.AbstractConfiguredObject$15.execute(AbstractConfiguredObject.java:1659)
>   at 
> org.apache.qpid.server.model.AbstractConfiguredObject$15.execute(AbstractConfiguredObject.java:1629)
>   at 
> org.apache.qpid.server.model.AbstractConfiguredObject$2.execute(AbstractConfiguredObject.java:632)
>   at 
> org.apache.qpid.server.model.AbstractConfiguredObject$2.execute(AbstractConfiguredObject.java:625)
>   at 
> org.apache.qpid.server.configuration.updater.TaskExecutorImpl$TaskLoggingWrapper.execute(TaskExecutorImpl.java:240)
>   at 
> org.apache.qpid.server.configuration.updater.TaskExecutorImpl$CallableWrapper$1.run(TaskExecutorImpl.java:312)
>   at java.security.AccessController.doPrivileged(Native Method)
>   at javax.security.auth.Subject.doAs(Subject.java:360)
>   at 
> org.apache.qpid.server.configuration.updater.TaskExecutorImpl$CallableWrapper.call(TaskExecutorImpl.java:305)
>   at java.util.concurrent.FutureTask.run(FutureTask.java:266)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>   at java.lang.Thread.run(Thread.java:745)
> Process finished with exit code 1
> {noformat}
> I have not tested with other versions of the broker, yet.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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

[jira] [Resolved] (DISPATCH-352) Crash with empty configuration file

[Ted Ross (JIRA)]

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

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

> Crash with empty configuration file
> ---
>
> Key: DISPATCH-352
> URL: https://issues.apache.org/jira/browse/DISPATCH-352
> Project: Qpid Dispatch
>  Issue Type: Bug
>  Components: Router Node
>Affects Versions: 0.6.0
> Environment: RHEL 6.8x
> Git tip at commit 87d0a406c6 "DISPATCH-339 - [From Ganesh Murthy] Properly 
> handle default values for host/addr."
>Reporter: Jiri Danek
> Fix For: 0.8.0
>
> Attachments: core.7166.backtrace, core.7166.bz2
>
>
> {noformat}
> $ touch empty.conf
> $ local/sbin/qdrouterd -c empty.conf 
> Thu May 26 13:34:19 2016 SERVER (info) Container Name: (null)
> Segmentation fault (core dumped)
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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

[jira] [Commented] (QPID-7690) [Java Broker] Cannot create VirtualHostLogger with certain ACLs in place

[ASF subversion and git services (JIRA)]

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

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

Commit 1786731 from [~lorenz.quack] in branch 'java/branches/6.1.x'
[ https://svn.apache.org/r1786731 ]

QPID-7690: [Java Broker] Fix ACLs for VirtualHost-type objects

merged from trunk with:
$ svn merge -c1786690 ^/qpid/java/trunk

> [Java Broker] Cannot create VirtualHostLogger with certain ACLs in place
> 
>
> Key: QPID-7690
> URL: https://issues.apache.org/jira/browse/QPID-7690
> Project: Qpid
>  Issue Type: Bug
>  Components: Java Broker
>Reporter: Lorenz Quack
> Fix For: qpid-java-6.1.2, qpid-java-broker-7.0.0
>
> Attachments: 
> 0001-QPID-7690-Java-Broker-Fix-ACLs-for-VirtualHost-type-.patch
>
>
> If the following ACL is in place
> {noformat}
> ACL ALLOW foo ALL ALL virtualhost_name="test"
> ACL DENY-LOG ALL ALL
> {noformat}
> the first rule should allow the user {{foo}} to create VirtualHostLoggers on 
> the virtual host called {{test}}.
> However this currently fails with a 403 Access Denied error.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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

[jira] [Created] (QPID-7701) [BDB HA] Cursor#getNext misuse

[Keith Wall (JIRA)]

Keith Wall created QPID-7701:


 Summary: [BDB HA] Cursor#getNext misuse
 Key: QPID-7701
 URL: https://issues.apache.org/jira/browse/QPID-7701
 Project: Qpid
  Issue Type: Bug
  Components: Java Broker
Reporter: Keith Wall
 Fix For: qpid-java-6.1, qpid-java-6.0, 0.32, 0.30


The documentation for methods {{com.sleepycat.je.Cursor#getNext}} and 
{{com.sleepycat.je.Cursor#getSearchKeyRange}} notes the following:

{quote}
In a replicated environment, an explicit transaction must have been
specified when opening the cursor, unless read-uncommitted isolation is
specified via the {{CursorConfig}} or {{LockMode}}
parameter.
{quote}

Currently methods such as 
{{org.apache.qpid.server.store.berkeleydb.AbstractBDBMessageStore.BDBMessageStoreReader#visitDistributedTransactions}}
 do not do this.

The documentation does not state the implications of not following this advice.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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

New Defects reported by Coverity Scan for Apache-Qpid

[scan-admin]

Hi,

Please find the latest report on new defect(s) introduced to Apache-Qpid found 
with Coverity Scan.

238 new defect(s) introduced to Apache-Qpid found with Coverity Scan.
34 defect(s), reported by Coverity Scan earlier, were marked fixed in the 
recent build analyzed by Coverity Scan.

New defect(s) Reported-by: Coverity Scan
Showing 20 of 238 defect(s)


** CID 1063262:  Resource leaks  (RESOURCE_LEAK)
/bindings/qpid/python/qpid_messagingPYTHON_wrap.cxx: 8946 in 
_wrap_new_Message__SWIG_0(_object *, _object *)()



*** CID 1063262:  Resource leaks  (RESOURCE_LEAK)
/bindings/qpid/python/qpid_messagingPYTHON_wrap.cxx: 8946 in 
_wrap_new_Message__SWIG_0(_object *, _object *)()
8940   error = ex.what();
8941 }
8942 /*@SWIG@*/
8943 Py_END_ALLOW_THREADS;
8944 if (!error.empty()) {
8945   PyErr_SetString(pExceptionType, error.c_str());
>>> CID 1063262:  Resource leaks  (RESOURCE_LEAK)
>>> Variable "arg1" going out of scope leaks the storage it points to.
8946   return NULL;
8947 }
8948   }
8949   resultobj = SWIG_NewPointerObj(SWIG_as_voidptr(result), 
SWIGTYPE_p_qpid__messaging__Message, SWIG_POINTER_NEW |  0 );
8950   {
8951 delete arg1;

** CID 1062932:  Performance inefficiencies  (PASS_BY_VALUE)
/usr/include/boost/function/function_template.hpp: 1124 in 
boost::function::operator 
=, std::allocator>> &, const 
std::__cxx11::basic_string 
&, const std::map, qpid::types::Variant, 
std::less>, std::allocator, 
qpid::types::Variant>>> &, const std::__cxx11::basic_string &), 
boost::_bi::list4, 
std::allocator>, 
boost::_bi::value, qpid::types::Variant, 
std::less>, std::allocator, 
qpid::types::Variant, boost::_bi::value(T1)()



*** CID 1062932:  Performance inefficiencies  (PASS_BY_VALUE)
/usr/include/boost/function/function_template.hpp: 1124 in 
boost::function::operator 
=, std::allocator>> &, const 
std::__cxx11::basic_string 
&, const std::map, qpid::types::Variant, 
std::less>, std::allocator, 
qpid::types::Variant>>> &, const std::__cxx11::basic_string &), 
boost::_bi::list4, 
std::allocator>, 
boost::_bi::value, qpid::types::Variant, 
std::less>, std::allocator, 
qpid::types::Variant, boost::_bi::value(T1)()
1118   typename boost::enable_if_c<
1119  !(is_integral::value),
1120   self_type&>::type
1121 #else
1122   self_type&
1123 #endif
>>> CID 1062932:  Performance inefficiencies  (PASS_BY_VALUE)
>>> Passing parameter f of type 
>>> "boost::_bi::bind_t>> qpid::messaging::ConnectionImpl 
>>> *(*)(std::vector>> std::allocator >, std::allocator>> std::char_traits, std::allocator > > > const &, 
>>> std::__cxx11::basic_string>> std::allocator > const &, std::map>> std::char_traits, std::allocator >, qpid::types::Variant, 
>>> std::less>> std::allocator > >, 
>>> std::allocator>> std::char_traits, 

[jira] [Assigned] (QPID-7685) [Java Broker, BDB] AsyncRecovery and Queue#enqueue can contend for a BDB Lock potentially bringing down the broker

[Keith Wall (JIRA)]

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

Keith Wall reassigned QPID-7685:


Assignee: Keith Wall

> [Java Broker, BDB] AsyncRecovery and Queue#enqueue can contend for a BDB Lock 
> potentially bringing down the broker
> --
>
> Key: QPID-7685
> URL: https://issues.apache.org/jira/browse/QPID-7685
> Project: Qpid
>  Issue Type: Bug
>  Components: Java Broker
>Affects Versions: 0.32, qpid-java-6.0.6, qpid-java-6.1.1, 
> qpid-java-broker-7.0.0
>Reporter: Lorenz Quack
>Assignee: Keith Wall
>Priority: Critical
>
> This is the scenario:
> BDB message store.
> AsyncRecovery completes recovery of queue Q1. Queue Q2 is still being 
> recovered.
> An transacted application sends a message to Q1 but does not commit the 
> transaction. This ends up creating an entry in the {{DeliveryDb}} through the 
> following call chain:
> > AMQChannel#deliverCurrentMessageIfComplete
> --> AbstractExchange#send
> > LocalTransaction#enqueue(List, EnqueueableMessage, 
> ServerTransaction.Action)
> --> AbstractBDBMessageStore.BDBTransaction#enqueueMessage
> > AbstractBDBMessageStore#enqueueMessage
> --> getDeliveryDb().put
> The transaction will hold a write lock on this new DB entry until the 
> transaction is committed.
> If it now happens that this entry appears immediately after the last entry of 
> Q2 in the database the recovery code will try to read that entry in 
> {{AbstractBDBMessageStore#visitMessageInstances(TransactionLogResource, 
> MessageInstanceHandler)}}:
> {{cursor.getNext(key, value, LockMode.DEFAULT)}}
> Acquisition of the read lock will timeout after {{je.lock.timeout}} (default: 
> 500ms) and after exhaustion of the retries (hard coded to 5) a 
> {{StoreException}} will be thrown bringing down the broker with the following 
> stack trace (from a broker derived from 0.32):
> {noformat}
> 
> #
> # Unhandled Exception 
> com.google.common.util.concurrent.UncheckedExecutionException: 
> org.apache.qpid.server.store.StoreException: Cannot visit messages in Thread 
> pool-2-thread-1
> #
> # Exiting
> #
> 
> com.google.common.util.concurrent.UncheckedExecutionException: 
> org.apache.qpid.server.store.StoreException: Cannot visit messages
>   at 
> com.google.common.util.concurrent.Futures.wrapAndThrowUnchecked(Futures.java:1358)
>   at 
> com.google.common.util.concurrent.Futures.getUnchecked(Futures.java:1344)
>   at 
> org.apache.qpid.server.virtualhost.AbstractVirtualHost$4.run(AbstractVirtualHost.java:1619)
>   at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
>   at java.util.concurrent.FutureTask.run(FutureTask.java:262)
>   at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178)
>   at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
>   at java.lang.Thread.run(Thread.java:745)
> Caused by: org.apache.qpid.server.store.StoreException: Cannot visit messages
>   at 
> org.apache.qpid.server.store.berkeleydb.StandardEnvironmentFacade.handleDatabaseException(StandardEnvironmentFacade.java:369)
>   at 
> org.apache.qpid.server.store.berkeleydb.AbstractBDBMessageStore.sleepOrThrowOnLockConflict(AbstractBDBMessageStore.java:665)
>   at 
> org.apache.qpid.server.store.berkeleydb.AbstractBDBMessageStore.visitMessageInstances(AbstractBDBMessageStore.java:233)
>   at 
> org.apache.qpid.server.virtualhost.AsynchronousMessageStoreRecoverer$AsynchronousRecoverer.recoverQueue(AsynchronousMessageStoreRecoverer.java:163)
>   at 
> org.apache.qpid.server.virtualhost.AsynchronousMessageStoreRecoverer$AsynchronousRecoverer.access$900(AsynchronousMessageStoreRecoverer.java:86)
>   at 
> org.apache.qpid.server.virtualhost.AsynchronousMessageStoreRecoverer$AsynchronousRecoverer$QueueRecoveringTask.run(AsynchronousMessageStoreRecoverer.java:436)
>   at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
>   at java.util.concurrent.FutureTask.run(FutureTask.java:262)
>   ... 3 more
> Caused by: com.sleepycat.je.LockTimeoutException: (JE 5.0.104) Lock expired. 
> Locker 2109822146 -1_Queue Recoverer : Q2 (vh: default)_ThreadLocker: waited 
> for lock on database=QUEUE_ENTRIES LockAddr:530828558 LSN=0x0/0xa45c 
> 

[jira] [Updated] (QPID-7684) [Java Broker, BDB] Close Cursor when LockConflictException is thrown

[Keith Wall (JIRA)]

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

Keith Wall updated QPID-7684:
-
Fix Version/s: qpid-java-broker-7.0.0
   qpid-java-6.1.2
   qpid-java-6.0.7

> [Java Broker, BDB] Close Cursor when LockConflictException is thrown
> 
>
> Key: QPID-7684
> URL: https://issues.apache.org/jira/browse/QPID-7684
> Project: Qpid
>  Issue Type: Bug
>  Components: Java Broker
>Affects Versions: 0.32, qpid-java-6.0.6, qpid-java-6.1.1, 
> qpid-java-broker-7.0.0
>Reporter: Lorenz Quack
> Fix For: qpid-java-6.0.7, qpid-java-6.1.2, qpid-java-broker-7.0.0
>
>
> Currently, when a LockConflictException is thrown we retry the operation.
> However the retry logic does not adhere to the rules outlined in the BDB JE 
> documentation, specifically we do not close and recreate the Cursor.
> To quote the 
> [documentation|https://docs.oracle.com/cd/E17277_02/html/java/com/sleepycat/je/LockConflictException.html]:
> {quote}If a lock conflict occurs during a transaction, the transaction may be 
> retried by performing the following steps. \[...\]:
> # Close all cursors opened under the transaction.
> # Abort the transaction.
> # Begin a new transaction and repeat the operations.
> {quote}
> The impact of not doing this is unclear.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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

[jira] [Commented] (QPID-7684) [Java Broker, BDB] Close Cursor when LockConflictException is thrown

[ASF subversion and git services (JIRA)]

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

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

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

QPID-7684: [Java Broker, BDB] Adhere to recommended practice for retrying after 
a LockConflictException

Also used try-with-resources to simplify coding

> [Java Broker, BDB] Close Cursor when LockConflictException is thrown
> 
>
> Key: QPID-7684
> URL: https://issues.apache.org/jira/browse/QPID-7684
> Project: Qpid
>  Issue Type: Bug
>  Components: Java Broker
>Affects Versions: 0.32, qpid-java-6.0.6, qpid-java-6.1.1, 
> qpid-java-broker-7.0.0
>Reporter: Lorenz Quack
>
> Currently, when a LockConflictException is thrown we retry the operation.
> However the retry logic does not adhere to the rules outlined in the BDB JE 
> documentation, specifically we do not close and recreate the Cursor.
> To quote the 
> [documentation|https://docs.oracle.com/cd/E17277_02/html/java/com/sleepycat/je/LockConflictException.html]:
> {quote}If a lock conflict occurs during a transaction, the transaction may be 
> retried by performing the following steps. \[...\]:
> # Close all cursors opened under the transaction.
> # Abort the transaction.
> # Begin a new transaction and repeat the operations.
> {quote}
> The impact of not doing this is unclear.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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

[jira] [Closed] (QPID-2022) Bug in C# request-response example client program

[Chuck Rolke (JIRA)]

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

Chuck Rolke closed QPID-2022.
-
   Resolution: Cannot Reproduce
Fix Version/s: qpid-cpp-1.37.0

The client referenced in this issue does not exist any more.

> Bug in C# request-response example client program
> -
>
> Key: QPID-2022
> URL: https://issues.apache.org/jira/browse/QPID-2022
> Project: Qpid
>  Issue Type: Bug
>  Components: .NET Client
> Environment: VS 2008, Windows XP
>Reporter: Jan Matti
>Assignee: Chuck Rolke
>Priority: Minor
> Fix For: qpid-cpp-1.37.0
>
>   Original Estimate: 5m
>  Remaining Estimate: 5m
>
> instead
>  string response_queue = "client" + session.getName();
> you must write
> ASCIIEncoding enc = new ASCIIEncoding();
> string response_queue = "client" + enc.GetString(session.getName());



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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

[jira] [Commented] (DISPATCH-725) Use Patternfly styles for console

[ASF subversion and git services (JIRA)]

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

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

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

DISPATCH-725 Modified stand-alone console's include css and js files


> Use Patternfly styles for console
> -
>
> Key: DISPATCH-725
> URL: https://issues.apache.org/jira/browse/DISPATCH-725
> Project: Qpid Dispatch
>  Issue Type: Improvement
>  Components: Console
>Affects Versions: 0.7.0
>Reporter: Ernest Allen
>Assignee: Ernest Allen
>
> For the stand-alone console, use the patternfly.org styles.
> This does not include the hawtio console since hawtio has it's own styles 
> that are not consistant with patternfly.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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

[jira] [Commented] (DISPATCH-725) Use Patternfly styles for console

[ASF subversion and git services (JIRA)]

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

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

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

DISPATCH-725 Use patternfly styles for stand-alone console


> Use Patternfly styles for console
> -
>
> Key: DISPATCH-725
> URL: https://issues.apache.org/jira/browse/DISPATCH-725
> Project: Qpid Dispatch
>  Issue Type: Improvement
>  Components: Console
>Affects Versions: 0.7.0
>Reporter: Ernest Allen
>Assignee: Ernest Allen
>
> For the stand-alone console, use the patternfly.org styles.
> This does not include the hawtio console since hawtio has it's own styles 
> that are not consistant with patternfly.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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

[jira] [Commented] (DISPATCH-725) Use Patternfly styles for console

[ASF subversion and git services (JIRA)]

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

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

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

DISPATCH-725 Use patternfly styles for stand-alone console


> Use Patternfly styles for console
> -
>
> Key: DISPATCH-725
> URL: https://issues.apache.org/jira/browse/DISPATCH-725
> Project: Qpid Dispatch
>  Issue Type: Improvement
>  Components: Console
>Affects Versions: 0.7.0
>Reporter: Ernest Allen
>Assignee: Ernest Allen
>
> For the stand-alone console, use the patternfly.org styles.
> This does not include the hawtio console since hawtio has it's own styles 
> that are not consistant with patternfly.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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

[jira] [Assigned] (QPID-566) Need to document extension points

[Justin Ross (JIRA)]

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

Justin Ross reassigned QPID-566:


Assignee: Justin Ross

> Need to document extension points
> -
>
> Key: QPID-566
> URL: https://issues.apache.org/jira/browse/QPID-566
> Project: Qpid
>  Issue Type: Improvement
>  Components: Website
>Affects Versions: M3
>Reporter: Aidan Skinner
>Assignee: Justin Ross
>Priority: Minor
>
> The programming guide should contain information on extending qpid using 
> exchanges, method args etc.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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

[jira] [Assigned] (QPID-2311) Clarify and extend the "Getting Started" broker sections of the web site for Windows users

[Justin Ross (JIRA)]

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

Justin Ross reassigned QPID-2311:
-

Assignee: Justin Ross

> Clarify and extend the "Getting Started" broker sections of the web site for 
> Windows users
> --
>
> Key: QPID-2311
> URL: https://issues.apache.org/jira/browse/QPID-2311
> Project: Qpid
>  Issue Type: Bug
>  Components: Website
>Affects Versions: 0.6
>Reporter: Steve Huston
>Assignee: Justin Ross
>
> The getting started info currently explains primarily use of Qpid on Linux; 
> there is some Windows info but we can do a better job of helping users of one 
> or the other platform zero in on what they need quicker. Also need more info 
> for Windows users for options, how to use the store, etc.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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

[jira] [Assigned] (QPID-1083) Qpid Messaging Tutorial

[Justin Ross (JIRA)]

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

Justin Ross reassigned QPID-1083:
-

Assignee: Justin Ross

> Qpid Messaging Tutorial
> ---
>
> Key: QPID-1083
> URL: https://issues.apache.org/jira/browse/QPID-1083
> Project: Qpid
>  Issue Type: New Feature
>  Components: Website
>Reporter: Jonathan Robie
>Assignee: Justin Ross
> Attachments: Messaging_Tutorial.tar.gz
>
>
> This is the messaging tutorial currently shipped with the Red Hat Messaging 
> beta. Red Hat has agreed to contribute it to Qpid.
> I have not done any work to remove references to Red Hat or our products, 
> this is precisely what we sent out with our beta (except for one phrase which 
> I returned to its original vernacular).
> This is all in DocBook format.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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

[jira] [Assigned] (QPID-1596) Example of using TTL with Multiple consumer pattern

[Justin Ross (JIRA)]

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

Justin Ross reassigned QPID-1596:
-

Assignee: Justin Ross

> Example of using TTL with Multiple consumer pattern
> ---
>
> Key: QPID-1596
> URL: https://issues.apache.org/jira/browse/QPID-1596
> Project: Qpid
>  Issue Type: Improvement
>  Components: Website
>Affects Versions: M4
>Reporter: William Henry
>Assignee: Justin Ross
>
> I would like to add the following example description to the web page 
> documentation.  The code from QPID-1595 can be included at the bottom.
> Some formatting of headers, lists and source code is required:
> -
> Multi-consumer example with Time-To-Live.
> There are several client examples in the distribution that focus primarily on 
> the various types of exchanges. However, there are several different consumer 
> patterns that are worth looking at: 
> * Last Value Queues (LVQ) that allow messages with the latest value to 
> overwrite the previous messages with the same key in a header (think stock 
> values)
> * Time-To-Live (TTL) which provide a timeout mechanism for messages to expire
> * Ring queues for conserving space and insuring that queues don't grow to 
> unmanagable sizes that might impact performance (this is more of an 
> implementation detail rather than a consumer pattern). 
> In this example we examine how we might use TTL and some other features to 
> create a the following consumer pattern:
> Provide several topic based queues that will be shared among several 
> consumers (subscribers).
> Make sure that all consumers can see all messages published to the queue 
> within a certain timeframe.
> Provide a timeout on published messages to make sure that 'stale' messages 
> don't remain in the queue and so that late coming subscribers only get 
> 'recent', 'relevent' information.
> First we must declare the queues. There are three differences between this 
> example and the pub/sub example:
> 1. The queues are declared independent of the subscriber (listener) sessions 
> and willl therefore outlive the listeners. If the broker restarts the queues 
> will need to be declared again.  (This can be changed by making the queues 
> durable.)
> Each queue needs to be declared as follows:
>   session.queueDeclare(arg::queue="usa", arg::exclusive=false);
>   session.exchangeBind(arg::exchange="amq.topic", arg::queue="usa", 
> arg::bindingKey="usa.#");
> The important part here is that the queue is non-exclusive.  Also note that 
> the name of the queue name does not have any subscriber specific ID and 
> therefore is easily shared.
> 2. The topic listener program will subscribe to the queue(s).  
> subscriptions.subscribe(*this, queue);
> subscriptions.setAcquireMode(message::ACQUIRE_MODE_NOT_ACQUIRED);
> The important part here is that the subscriber will 'browse' messages and not 
> acquire (ACQUIRE_MODE_NOT_ACQUIRED), i.e. take ownership, of the message. 
> This allows other subscribers to see the message too.
> 3. The topic publisher program will send messages with a set Time-To-Live 
> (TTL). i.e. the message will time out and be purged after the TTL period. The 
> TTL period is in milliseconds.
> message_data << "My Message";  // the example put this in a loop
> message.setData(message_data.str());
> message.getDeliveryProperties().setTtl(ttl_time);  // ttl_time is an int, 
> say 3000
> // Asynchronous transfer sends messages as quickly as
> // possible without waiting for confirmation.
> async(session).messageTransfer(arg::content=message, 
> arg::destination="amq.topic");
> The important part here is that the setTtl() method is called so that 
> messages can timeout and be removed from the queue.
> Expected Behavior
> Run declare_queues to set up the non-exclusive queues.
> Run a topic_listener in one shell which will wiat for messages to be posted.
> Run the topic_publisher in another shell and give it a ttl paramater of 4000.
> Run another topic_listener in another shell.  
> Look at the output of both topic_listeners. The first one, started before the 
> publisher, will get all the messages.  The second listener may or may not get 
> all/any of the messages depending on how late it joined the queue and started 
> listening.  
> Another enhancement would be to have a delay built into the listner handler 
> which would slow the listener down and therefore it may miss some messages.  
> Again, in certain scenarios it is okay not to get older messages.
> 
> Code from QPID-1595 added here excluding the makefile.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

-
To unsubscribe, 

[jira] [Assigned] (QPID-568) [Document] How to use Qpid with 3rd party tools

[Justin Ross (JIRA)]

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

Justin Ross reassigned QPID-568:


Assignee: Justin Ross

> [Document] How to use Qpid with 3rd party tools
> ---
>
> Key: QPID-568
> URL: https://issues.apache.org/jira/browse/QPID-568
> Project: Qpid
>  Issue Type: Task
>  Components: Website
>Affects Versions: M2.1, M3
>Reporter: Martin Ritchie
>Assignee: Justin Ross
>  Labels: starter
>
> Document how to use qpid with 3rd party tools:
> Some potential tools where describing the configuration steps may help.
>  - JBoss
>  - Spring
>  - Mule 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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

[jira] [Assigned] (QPID-2823) HermesJMS QPID integration document refers to jar files no longer used in QPID 0.6

[Justin Ross (JIRA)]

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

Justin Ross reassigned QPID-2823:
-

Assignee: Justin Ross

> HermesJMS QPID integration document refers to jar files no longer used in 
> QPID 0.6
> --
>
> Key: QPID-2823
> URL: https://issues.apache.org/jira/browse/QPID-2823
> Project: Qpid
>  Issue Type: Improvement
>  Components: Website
>Affects Versions: 0.6
> Environment: Website, HermesJMS 1.13
>Reporter: Philip Schlesinger
>Assignee: Justin Ross
>
> This web page: https://cwiki.apache.org/qpid/hermesjms.html
> refers to configuring HermesJMS to add to its classpath several jars, many of 
> which no longer exist in the 0.6 distribution.  I cannot find in the 0.6 
> distribution:
> * client-launch.jar
> * slf4j-simple.jar (is this slf4j-api-1.4.0.jar?)
> * client.jar (is this qpid-client-0.6.jar?)
> * common.jar (is this qpid-common-0.6.jar?)
> I'm assuming the two mina jars can be just replaced with their newer 
> versions.  Please update the diagram to show the new filenames to use and 
> where they're located relative to the directory tree.
> I should note that adding the jars from the 
> qpid-0.6\java\client\release\qpid-client-0.6\lib\ directory seems to work.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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

[jira] [Assigned] (DISPATCH-638) [Test] If proton is built without Swig then twenty self tests fail

[Ganesh Murthy (JIRA)]

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

Ganesh Murthy reassigned DISPATCH-638:
--

Assignee: Ganesh Murthy

> [Test] If proton is built without Swig then twenty self tests fail
> --
>
> Key: DISPATCH-638
> URL: https://issues.apache.org/jira/browse/DISPATCH-638
> Project: Qpid Dispatch
>  Issue Type: Bug
>  Components: Tests
>Affects Versions: 0.7.0
> Environment: Fedora 25, dispatch master branch at commit 6ebae
>Reporter: Chuck Rolke
>Assignee: Ganesh Murthy
>
> The tests generally fail with
> {noformat}
> 10: Run python module 'unittest': ImportError: No module named proton
> {noformat}
> A better user experience would be a message: "Test skipped because Proton 
> Python is missing. (Was Proton python language binding built with Swig?)". 
> And then have the test be skipped and not failed.
> Proton C tests also have issues when Swig is absent: 
> https://issues.apache.org/jira/browse/PROTON-1411



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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

[jira] [Resolved] (DISPATCH-611) Router core dump with old config file

[Ganesh Murthy (JIRA)]

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

Ganesh Murthy resolved DISPATCH-611.

Resolution: Fixed

> Router core dump with old config file
> -
>
> Key: DISPATCH-611
> URL: https://issues.apache.org/jira/browse/DISPATCH-611
> Project: Qpid Dispatch
>  Issue Type: Bug
>Affects Versions: 0.7.0
> Environment: Linux hostname 4.8.13-100.fc23.x86_64 #1 SMP Fri Dec 9 
> 14:51:40 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
>Reporter: Chuck Rolke
>Assignee: Ganesh Murthy
> Fix For: 0.8.0
>
> Attachments: oops.conf
>
>
> Revving up an old config file causes a core dump.
> {noformat}
> > ./qdrouterd -c oops.conf  -I /home/user/git/qpid-dispatch/python
> qdrouterd: /home/user/git/qpid-dispatch/src/dispatch.c:162: 
> qd_dispatch_configure_router: Assertion `qd->router_id' failed.
> Aborted (core dumped)
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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

[jira] [Commented] (DISPATCH-611) Router core dump with old config file

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on DISPATCH-611:
-

Github user asfgit closed the pull request at:

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


> Router core dump with old config file
> -
>
> Key: DISPATCH-611
> URL: https://issues.apache.org/jira/browse/DISPATCH-611
> Project: Qpid Dispatch
>  Issue Type: Bug
>Affects Versions: 0.7.0
> Environment: Linux hostname 4.8.13-100.fc23.x86_64 #1 SMP Fri Dec 9 
> 14:51:40 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
>Reporter: Chuck Rolke
>Assignee: Ganesh Murthy
> Fix For: 0.8.0
>
> Attachments: oops.conf
>
>
> Revving up an old config file causes a core dump.
> {noformat}
> > ./qdrouterd -c oops.conf  -I /home/user/git/qpid-dispatch/python
> qdrouterd: /home/user/git/qpid-dispatch/src/dispatch.c:162: 
> qd_dispatch_configure_router: Assertion `qd->router_id' failed.
> Aborted (core dumped)
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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

[jira] [Commented] (DISPATCH-611) Router core dump with old config file

[ASF subversion and git services (JIRA)]

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

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

Commit 1a59f1fcab5a5e83cfb33eac9c8c273c9edd32c8 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=1a59f1f ]

DISPATCH-611 - Exit, don't crash, if there is no router id specified.
Patch from Ganesh Murthy
This closes #148


> Router core dump with old config file
> -
>
> Key: DISPATCH-611
> URL: https://issues.apache.org/jira/browse/DISPATCH-611
> Project: Qpid Dispatch
>  Issue Type: Bug
>Affects Versions: 0.7.0
> Environment: Linux hostname 4.8.13-100.fc23.x86_64 #1 SMP Fri Dec 9 
> 14:51:40 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
>Reporter: Chuck Rolke
>Assignee: Ganesh Murthy
> Fix For: 0.8.0
>
> Attachments: oops.conf
>
>
> Revving up an old config file causes a core dump.
> {noformat}
> > ./qdrouterd -c oops.conf  -I /home/user/git/qpid-dispatch/python
> qdrouterd: /home/user/git/qpid-dispatch/src/dispatch.c:162: 
> qd_dispatch_configure_router: Assertion `qd->router_id' failed.
> Aborted (core dumped)
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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

[GitHub] qpid-dispatch pull request #148: DISPATCH-611 - Exit if there is no router i...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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-631) Tests should be made conditional to skip tests for SASL features that are not available

[Ganesh Murthy (JIRA)]

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

Ganesh Murthy reassigned DISPATCH-631:
--

Assignee: Ganesh Murthy

> Tests should be made conditional to skip tests for SASL features that are not 
> available
> ---
>
> Key: DISPATCH-631
> URL: https://issues.apache.org/jira/browse/DISPATCH-631
> Project: Qpid Dispatch
>  Issue Type: Bug
>  Components: Tests
>Affects Versions: 0.7.0, 0.8.0
> Environment: linux, sunos
>Reporter: Rabih Mourad
>Assignee: Ganesh Murthy
> Fix For: 0.8.0
>
> Attachments: failedTests.txt
>
>
> > Hello,
> > 
> > I compiled qpid-proton 0.16.0 with "-DSASL_IMPL=none", but i have an
> > 3 of qpid-dispatch 0.7.0 unit tests that are failing:
> > 
> > system_tests_qdstat
> > system_tests_sasl_plain
> > system_tests_deprecated
> > 
> > I attached the tests output.
> > 
> > Do you have any idea, where should i look? Is Cyrus mandatory for the 
> > qpid-dispatch 0.7.0?
> Not mandatory, the tests should probably be made conditional to skip tests 
> for SASL features that are not available. Raise a JIRA for that.
> > Best regards,
> > Rabih



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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

[jira] [Resolved] (DISPATCH-631) Tests should be made conditional to skip tests for SASL features that are not available

[Ganesh Murthy (JIRA)]

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

Ganesh Murthy resolved DISPATCH-631.

   Resolution: Fixed
Fix Version/s: 0.8.0

> Tests should be made conditional to skip tests for SASL features that are not 
> available
> ---
>
> Key: DISPATCH-631
> URL: https://issues.apache.org/jira/browse/DISPATCH-631
> Project: Qpid Dispatch
>  Issue Type: Bug
>  Components: Tests
>Affects Versions: 0.7.0, 0.8.0
> Environment: linux, sunos
>Reporter: Rabih Mourad
>Assignee: Ganesh Murthy
> Fix For: 0.8.0
>
> Attachments: failedTests.txt
>
>
> > Hello,
> > 
> > I compiled qpid-proton 0.16.0 with "-DSASL_IMPL=none", but i have an
> > 3 of qpid-dispatch 0.7.0 unit tests that are failing:
> > 
> > system_tests_qdstat
> > system_tests_sasl_plain
> > system_tests_deprecated
> > 
> > I attached the tests output.
> > 
> > Do you have any idea, where should i look? Is Cyrus mandatory for the 
> > qpid-dispatch 0.7.0?
> Not mandatory, the tests should probably be made conditional to skip tests 
> for SASL features that are not available. Raise a JIRA for that.
> > Best regards,
> > Rabih



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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

[jira] [Commented] (DISPATCH-631) Tests should be made conditional to skip tests for SASL features that are not available

[ASF subversion and git services (JIRA)]

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

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

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

DISPATCH-631 - Tests made conditional to skip tests for SASL features that are 
not available


> Tests should be made conditional to skip tests for SASL features that are not 
> available
> ---
>
> Key: DISPATCH-631
> URL: https://issues.apache.org/jira/browse/DISPATCH-631
> Project: Qpid Dispatch
>  Issue Type: Bug
>  Components: Tests
>Affects Versions: 0.7.0, 0.8.0
> Environment: linux, sunos
>Reporter: Rabih Mourad
> Attachments: failedTests.txt
>
>
> > Hello,
> > 
> > I compiled qpid-proton 0.16.0 with "-DSASL_IMPL=none", but i have an
> > 3 of qpid-dispatch 0.7.0 unit tests that are failing:
> > 
> > system_tests_qdstat
> > system_tests_sasl_plain
> > system_tests_deprecated
> > 
> > I attached the tests output.
> > 
> > Do you have any idea, where should i look? Is Cyrus mandatory for the 
> > qpid-dispatch 0.7.0?
> Not mandatory, the tests should probably be made conditional to skip tests 
> for SASL features that are not available. Raise a JIRA for that.
> > Best regards,
> > Rabih



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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

[jira] [Commented] (QPID-7690) [Java Broker] Cannot create VirtualHostLogger with certain ACLs in place

[ASF subversion and git services (JIRA)]

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

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

Commit 1786690 from [~lorenz.quack] in branch 'java/trunk'
[ https://svn.apache.org/r1786690 ]

QPID-7690: [Java Broker] Fix ACLs for VirtualHost-type objects

Add the virtualhost name to the properties so the ACL rules can refer to 
virtualhost_name

> [Java Broker] Cannot create VirtualHostLogger with certain ACLs in place
> 
>
> Key: QPID-7690
> URL: https://issues.apache.org/jira/browse/QPID-7690
> Project: Qpid
>  Issue Type: Bug
>  Components: Java Broker
>Reporter: Lorenz Quack
> Fix For: qpid-java-6.1.2, qpid-java-broker-7.0.0
>
> Attachments: 
> 0001-QPID-7690-Java-Broker-Fix-ACLs-for-VirtualHost-type-.patch
>
>
> If the following ACL is in place
> {noformat}
> ACL ALLOW foo ALL ALL virtualhost_name="test"
> ACL DENY-LOG ALL ALL
> {noformat}
> the first rule should allow the user {{foo}} to create VirtualHostLoggers on 
> the virtual host called {{test}}.
> However this currently fails with a 403 Access Denied error.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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

[jira] [Updated] (QPID-7700) Jira clean up for C++ and related components

[Justin Ross (JIRA)]

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

Justin Ross updated QPID-7700:
--
Description: 
Updated query:

https://issues.apache.org/jira/issues/?filter=-4=project%20%3D%20QPID%20AND%20resolution%20%3D%20Unresolved%20AND%20fixVersion%20%3D%20EMPTY%20AND%20component%20in%20(%22C%2B%2B%20Broker%22%2C%20%22C%2B%2B%20Client%22%2C%20%22C%2B%2B%20Clustering%22%2C%20%22.NET%20Client%22%2C%20JCA%2C%20%22Perl%20Client%22%2C%20%22Python%20Client%22%2C%20%22Python%20Test%20Suite%22%2C%20%22C%2B%2B%20Tools%22%2C%20%22C%2B%2B%20Examples%22%2C%20%22QMF%22%2C%20%22Ruby%20Client%22%2C%20%22WCF%2FC%2B%2B%20Client%22)%20AND%20updated%20%3C%3D%202014-01-01%20ORDER%20BY%20priority%20DESC

---

Currently there are 300 unresolved and not scheduled to be resolved issues 
affecting these components. It will help the community to maintain focus if we 
can review and update them. If the issue is no longer relevant, was already 
resolved or unlikely to be resolved at all, the issue should be marked as 
resolved or closed, otherwise it should be updated with a note and/or scheduled 
for resolution (fix versions .21 or future).

There are 155 issues created before Jan. 1, 2012, and not updated after this 
date. I would like to ask all to review them by March 1, 2013 and update them 
as needed. I would like to propose closing any issues that do not get updated 
by this date. Corresponding query:

https://issues.apache.org/jira/issues/?filter=-4=project%20%3D%20QPID%20AND%20resolution%20%3D%20Unresolved%20AND%20fixVersion%20%3D%20EMPTY%20AND%20component%20in%20(%22C%2B%2B%20Broker%22%2C%20%22C%2B%2B%20Client%22%2C%20%22C%2B%2B%20Clustering%22%2C%20%22Dot%20Net%20Client%22%2C%20JCA%2C%20%22Perl%20Client%22%2C%20%22Python%20Client%22%2C%20%22Python%20Test%20Suite%22%2C%20%22Python%20Tools%22%2C%20%22Qpid%20Examples%22%2C%20%22Qpid%20Managment%20Framework%22%2C%20%22Ruby%20Client%22%2C%20%22WCF%2FC%2B%2B%20Client%22)%20AND%20updated%20%3C%3D%202012-01-01%20ORDER%20BY%20priority%20DESC

Please also take time to review any other open issues that are either assigned 
to you or were created by you, and take appropriate actions. Thank you for your 
contribution!

Regards, Irina.

  was:
Currently there are 300 unresolved and not scheduled to be resolved issues 
affecting these components. It will help the community to maintain focus if we 
can review and update them. If the issue is no longer relevant, was already 
resolved or unlikely to be resolved at all, the issue should be marked as 
resolved or closed, otherwise it should be updated with a note and/or scheduled 
for resolution (fix versions .21 or future).

There are 155 issues created before Jan. 1, 2012, and not updated after this 
date. I would like to ask all to review them by March 1, 2013 and update them 
as needed. I would like to propose closing any issues that do not get updated 
by this date. Corresponding query:

https://issues.apache.org/jira/issues/?filter=-4=project%20%3D%20QPID%20AND%20resolution%20%3D%20Unresolved%20AND%20fixVersion%20%3D%20EMPTY%20AND%20component%20in%20(%22C%2B%2B%20Broker%22%2C%20%22C%2B%2B%20Client%22%2C%20%22C%2B%2B%20Clustering%22%2C%20%22Dot%20Net%20Client%22%2C%20JCA%2C%20%22Perl%20Client%22%2C%20%22Python%20Client%22%2C%20%22Python%20Test%20Suite%22%2C%20%22Python%20Tools%22%2C%20%22Qpid%20Examples%22%2C%20%22Qpid%20Managment%20Framework%22%2C%20%22Ruby%20Client%22%2C%20%22WCF%2FC%2B%2B%20Client%22)%20AND%20updated%20%3C%3D%202012-01-01%20ORDER%20BY%20priority%20DESC

Please also take time to review any other open issues that are either assigned 
to you or were created by you, and take appropriate actions. Thank you for your 
contribution!

Regards, Irina.


> Jira clean up for C++ and related components
> 
>
> Key: QPID-7700
> URL: https://issues.apache.org/jira/browse/QPID-7700
> Project: Qpid
>  Issue Type: Task
>  Components: .NET Client, C++ Broker, C++ Client, C++ Clustering, C++ 
> Documentation, C++ Examples, C++ Tools, Perl Client, Python Client, Python 
> Test Suite, QMF, Ruby Client, WCF/C++ Client
>Affects Versions: JIRA Cleanup
>Reporter: Justin Ross
>  Labels: cleanup
>   Original Estimate: 336h
>  Remaining Estimate: 336h
>
> Updated query:
> 

[jira] [Updated] (QPID-7700) Jira clean up for C++ and related components

[Justin Ross (JIRA)]

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

Justin Ross updated QPID-7700:
--
Component/s: (was: JCA)
 C++ Documentation

> Jira clean up for C++ and related components
> 
>
> Key: QPID-7700
> URL: https://issues.apache.org/jira/browse/QPID-7700
> Project: Qpid
>  Issue Type: Task
>  Components: .NET Client, C++ Broker, C++ Client, C++ Clustering, C++ 
> Documentation, C++ Examples, C++ Tools, Perl Client, Python Client, Python 
> Test Suite, QMF, Ruby Client, WCF/C++ Client
>Affects Versions: JIRA Cleanup
>Reporter: Justin Ross
>  Labels: cleanup
>   Original Estimate: 336h
>  Remaining Estimate: 336h
>
> Currently there are 300 unresolved and not scheduled to be resolved issues 
> affecting these components. It will help the community to maintain focus if 
> we can review and update them. If the issue is no longer relevant, was 
> already resolved or unlikely to be resolved at all, the issue should be 
> marked as resolved or closed, otherwise it should be updated with a note 
> and/or scheduled for resolution (fix versions .21 or future).
> There are 155 issues created before Jan. 1, 2012, and not updated after this 
> date. I would like to ask all to review them by March 1, 2013 and update them 
> as needed. I would like to propose closing any issues that do not get updated 
> by this date. Corresponding query:
> https://issues.apache.org/jira/issues/?filter=-4=project%20%3D%20QPID%20AND%20resolution%20%3D%20Unresolved%20AND%20fixVersion%20%3D%20EMPTY%20AND%20component%20in%20(%22C%2B%2B%20Broker%22%2C%20%22C%2B%2B%20Client%22%2C%20%22C%2B%2B%20Clustering%22%2C%20%22Dot%20Net%20Client%22%2C%20JCA%2C%20%22Perl%20Client%22%2C%20%22Python%20Client%22%2C%20%22Python%20Test%20Suite%22%2C%20%22Python%20Tools%22%2C%20%22Qpid%20Examples%22%2C%20%22Qpid%20Managment%20Framework%22%2C%20%22Ruby%20Client%22%2C%20%22WCF%2FC%2B%2B%20Client%22)%20AND%20updated%20%3C%3D%202012-01-01%20ORDER%20BY%20priority%20DESC
> Please also take time to review any other open issues that are either 
> assigned to you or were created by you, and take appropriate actions. Thank 
> you for your contribution!
> Regards, Irina.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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

[jira] [Created] (QPID-7700) Jira clean up for C++ and related components

[Justin Ross (JIRA)]

Justin Ross created QPID-7700:
-

 Summary: Jira clean up for C++ and related components
 Key: QPID-7700
 URL: https://issues.apache.org/jira/browse/QPID-7700
 Project: Qpid
  Issue Type: Task
  Components: .NET Client, C++ Broker, C++ Client, C++ Clustering, C++ 
Examples, C++ Tools, JCA, Perl Client, Python Client, Python Test Suite, QMF, 
Ruby Client, WCF/C++ Client
Affects Versions: JIRA Cleanup
Reporter: Justin Ross


Currently there are 300 unresolved and not scheduled to be resolved issues 
affecting these components. It will help the community to maintain focus if we 
can review and update them. If the issue is no longer relevant, was already 
resolved or unlikely to be resolved at all, the issue should be marked as 
resolved or closed, otherwise it should be updated with a note and/or scheduled 
for resolution (fix versions .21 or future).

There are 155 issues created before Jan. 1, 2012, and not updated after this 
date. I would like to ask all to review them by March 1, 2013 and update them 
as needed. I would like to propose closing any issues that do not get updated 
by this date. Corresponding query:

https://issues.apache.org/jira/issues/?filter=-4=project%20%3D%20QPID%20AND%20resolution%20%3D%20Unresolved%20AND%20fixVersion%20%3D%20EMPTY%20AND%20component%20in%20(%22C%2B%2B%20Broker%22%2C%20%22C%2B%2B%20Client%22%2C%20%22C%2B%2B%20Clustering%22%2C%20%22Dot%20Net%20Client%22%2C%20JCA%2C%20%22Perl%20Client%22%2C%20%22Python%20Client%22%2C%20%22Python%20Test%20Suite%22%2C%20%22Python%20Tools%22%2C%20%22Qpid%20Examples%22%2C%20%22Qpid%20Managment%20Framework%22%2C%20%22Ruby%20Client%22%2C%20%22WCF%2FC%2B%2B%20Client%22)%20AND%20updated%20%3C%3D%202012-01-01%20ORDER%20BY%20priority%20DESC

Please also take time to review any other open issues that are either assigned 
to you or were created by you, and take appropriate actions. Thank you for your 
contribution!

Regards, Irina.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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

[jira] [Created] (DISPATCH-725) Use Patternfly styles for console

[Ernest Allen (JIRA)]

Ernest Allen created DISPATCH-725:
-

 Summary: Use Patternfly styles for console
 Key: DISPATCH-725
 URL: https://issues.apache.org/jira/browse/DISPATCH-725
 Project: Qpid Dispatch
  Issue Type: Improvement
  Components: Console
Affects Versions: 0.7.0
Reporter: Ernest Allen
Assignee: Ernest Allen


For the stand-alone console, use the patternfly.org styles.
This does not include the hawtio console since hawtio has it's own styles that 
are not consistant with patternfly.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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

[jira] [Updated] (QPID-7690) [Java Broker] Cannot create VirtualHostLogger with certain ACLs in place

[Lorenz Quack (JIRA)]

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

Lorenz Quack updated QPID-7690:
---
Attachment: 0001-QPID-7690-Java-Broker-Fix-ACLs-for-VirtualHost-type-.patch

> [Java Broker] Cannot create VirtualHostLogger with certain ACLs in place
> 
>
> Key: QPID-7690
> URL: https://issues.apache.org/jira/browse/QPID-7690
> Project: Qpid
>  Issue Type: Bug
>  Components: Java Broker
>Reporter: Lorenz Quack
> Fix For: qpid-java-6.1.2, qpid-java-broker-7.0.0
>
> Attachments: 
> 0001-QPID-7690-Java-Broker-Fix-ACLs-for-VirtualHost-type-.patch
>
>
> If the following ACL is in place
> {noformat}
> ACL ALLOW foo ALL ALL virtualhost_name="test"
> ACL DENY-LOG ALL ALL
> {noformat}
> the first rule should allow the user {{foo}} to create VirtualHostLoggers on 
> the virtual host called {{test}}.
> However this currently fails with a 403 Access Denied error.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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

[jira] [Updated] (DISPATCH-646) Link route tests which test the drain feature fail intermittently

[Ted Ross (JIRA)]

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

Ted Ross updated DISPATCH-646:
--
Fix Version/s: 0.8.0

> Link route tests which test the drain feature fail intermittently
> -
>
> Key: DISPATCH-646
> URL: https://issues.apache.org/jira/browse/DISPATCH-646
> Project: Qpid Dispatch
>  Issue Type: Bug
>  Components: Container
>Affects Versions: 0.7.0
>Reporter: Ganesh Murthy
>Assignee: Ted Ross
> Fix For: 0.8.0
>
>
> There is test called test_www_drain_support_all_messages in 
> system_tests_link_routes that fails intermittently. Here is the output of the 
> test
> {noformat}
> [gmurthy@localhost build]$  /usr/bin/python 
> "/home/gmurthy/opensource/dispatch/build/tests/run.py" "-m" "unittest" "-v" 
> "system_tests_link_routes.LinkRouteTest.test_www_drain_support_all_messages"
> test_www_drain_support_all_messages (system_tests_link_routes.LinkRouteTest) 
> ... 
> FAIL
> ==
> FAIL: test_www_drain_support_all_messages 
> (system_tests_link_routes.LinkRouteTest)
> --
> Traceback (most recent call last):
>   File "/home/gmurthy/opensource/dispatch/tests/system_tests_link_routes.py", 
> line 542, in test_www_drain_support_all_messages
> self.assertEqual(None, drain_support.error)
> AssertionError: None != 'Timeout Expired: sent: 10 rcvd: 7'
> --
> Ran 1 test in 9.421s
> FAILED (failures=1)
> {noformat}
> The test uses 3 routers (routers A, B and C) with router A acting as the 
> broker and the senders and receivers connected router C and they send/receive 
> on link routed addresses. The messages sent to router C are link-routed to 
> router B and go on to router A and are eventually link routed back to router 
> B and finally to a receiver attached to router C.
> The sender sends 10 messages and the receiver initially issues a flow of 4 
> followed by a drain of 20. This means that the remaining 6 messages must come 
> thru to the receiver. The problem in that in router B, the 6 transfers from 
> router A to router B are followed by a response flow frame (drain=true). In 
> router B, this flow frame sometimes  gets ahead of the transfers and shuts 
> down the remaining transfers.
> The following frame trace shows the flow frame coming in from router C and 
> being sent to router A which followed by 6 transfer frames and a response 
> flow frame arriving from router A. Note now that the router B forwards 3 of 
> the 6 transfers to router C and tries sending the response flow frame before 
> the remaining 3 transfers. Because of this the receiver is not seeing all 10 
> messages.
> {noformat}
> Fri Mar  3 13:49:11 2017 SERVER (trace) [3]:4 <- @flow(19) 
> [next-incoming-id=4, incoming-window=2147483647, next-outgoing-id=0, 
> outgoing-window=2147483647, handle=0, delivery-count=4, link-credit=20, 
> drain=true] (/home/gmurthy/opensource/dispatch/src/server.c:197)
> Fri Mar  3 13:49:11 2017 ROUTER_CORE (trace) Core action 'link_flow' 
> (/home/gmurthy/opensource/dispatch/src/router_core/router_core_thread.c:82)
> Fri Mar  3 13:49:11 2017 SERVER (trace) [2]:0 -> @flow(19) 
> [next-incoming-id=4, incoming-window=2147483647, next-outgoing-id=0, 
> outgoing-window=2147483647, handle=0, delivery-count=4, link-credit=20, 
> drain=true] (/home/gmurthy/opensource/dispatch/src/server.c:197)
> Fri Mar  3 13:49:11 2017 SERVER (trace) [2]:0 <- @transfer(20) [handle=0, 
> delivery-id=4, delivery-tag=b"\x04\x00\x00\x00\x00\x00\x00\x00", 
> message-format=0, settled=true, more=false] (96) 
> "\x00Sp\xd0\x00\x00\x00\x0b\x00\x00\x00\x05BP\x04@BR\x00\x00Ss\xd0\x00\x00\x00"\x00\x00\x00\x0d\x83\x00\x00\x00\x00\x00\x00\x00\x00\x83\x00\x00\x00\x00\x00\x00\x00\x00@R\x00@\x00St\xd1\x00\x00\x00\x0b\x00\x00\x00\x02\xa0\x03seqT\x04\x00Sw\xa0\x0bHello
>  World" (/home/gmurthy/opensource/dispatch/src/server.c:197)
> Fri Mar  3 13:49:11 2017 SERVER (trace) [2]:0 <- @transfer(20) [handle=0, 
> delivery-id=5, delivery-tag=b"\x05\x00\x00\x00\x00\x00\x00\x00", 
> message-format=0, settled=true, more=false] (96) 
> "\x00Sp\xd0\x00\x00\x00\x0b\x00\x00\x00\x05BP\x04@BR\x00\x00Ss\xd0\x00\x00\x00"\x00\x00\x00\x0d\x83\x00\x00\x00\x00\x00\x00\x00\x00\x83\x00\x00\x00\x00\x00\x00\x00\x00@R\x00@\x00St\xd1\x00\x00\x00\x0b\x00\x00\x00\x02\xa0\x03seqT\x05\x00Sw\xa0\x0bHello
>  World" (/home/gmurthy/opensource/dispatch/src/server.c:197)
> Fri Mar  3 13:49:11 2017 SERVER (trace) [2]:0 <- @transfer(20) [handle=0, 
> delivery-id=6, delivery-tag=b"\x06\x00\x00\x00\x00\x00\x00\x00", 
> message-format=0, settled=true, more=false] (96) 
> 

[jira] [Updated] (DISPATCH-646) Link route tests which test the drain feature fail intermittently

[Ted Ross (JIRA)]

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

Ted Ross updated DISPATCH-646:
--
Affects Version/s: (was: 0.8.0)
   0.7.0

> Link route tests which test the drain feature fail intermittently
> -
>
> Key: DISPATCH-646
> URL: https://issues.apache.org/jira/browse/DISPATCH-646
> Project: Qpid Dispatch
>  Issue Type: Bug
>  Components: Container
>Affects Versions: 0.7.0
>Reporter: Ganesh Murthy
>Assignee: Ted Ross
> Fix For: 0.8.0
>
>
> There is test called test_www_drain_support_all_messages in 
> system_tests_link_routes that fails intermittently. Here is the output of the 
> test
> {noformat}
> [gmurthy@localhost build]$  /usr/bin/python 
> "/home/gmurthy/opensource/dispatch/build/tests/run.py" "-m" "unittest" "-v" 
> "system_tests_link_routes.LinkRouteTest.test_www_drain_support_all_messages"
> test_www_drain_support_all_messages (system_tests_link_routes.LinkRouteTest) 
> ... 
> FAIL
> ==
> FAIL: test_www_drain_support_all_messages 
> (system_tests_link_routes.LinkRouteTest)
> --
> Traceback (most recent call last):
>   File "/home/gmurthy/opensource/dispatch/tests/system_tests_link_routes.py", 
> line 542, in test_www_drain_support_all_messages
> self.assertEqual(None, drain_support.error)
> AssertionError: None != 'Timeout Expired: sent: 10 rcvd: 7'
> --
> Ran 1 test in 9.421s
> FAILED (failures=1)
> {noformat}
> The test uses 3 routers (routers A, B and C) with router A acting as the 
> broker and the senders and receivers connected router C and they send/receive 
> on link routed addresses. The messages sent to router C are link-routed to 
> router B and go on to router A and are eventually link routed back to router 
> B and finally to a receiver attached to router C.
> The sender sends 10 messages and the receiver initially issues a flow of 4 
> followed by a drain of 20. This means that the remaining 6 messages must come 
> thru to the receiver. The problem in that in router B, the 6 transfers from 
> router A to router B are followed by a response flow frame (drain=true). In 
> router B, this flow frame sometimes  gets ahead of the transfers and shuts 
> down the remaining transfers.
> The following frame trace shows the flow frame coming in from router C and 
> being sent to router A which followed by 6 transfer frames and a response 
> flow frame arriving from router A. Note now that the router B forwards 3 of 
> the 6 transfers to router C and tries sending the response flow frame before 
> the remaining 3 transfers. Because of this the receiver is not seeing all 10 
> messages.
> {noformat}
> Fri Mar  3 13:49:11 2017 SERVER (trace) [3]:4 <- @flow(19) 
> [next-incoming-id=4, incoming-window=2147483647, next-outgoing-id=0, 
> outgoing-window=2147483647, handle=0, delivery-count=4, link-credit=20, 
> drain=true] (/home/gmurthy/opensource/dispatch/src/server.c:197)
> Fri Mar  3 13:49:11 2017 ROUTER_CORE (trace) Core action 'link_flow' 
> (/home/gmurthy/opensource/dispatch/src/router_core/router_core_thread.c:82)
> Fri Mar  3 13:49:11 2017 SERVER (trace) [2]:0 -> @flow(19) 
> [next-incoming-id=4, incoming-window=2147483647, next-outgoing-id=0, 
> outgoing-window=2147483647, handle=0, delivery-count=4, link-credit=20, 
> drain=true] (/home/gmurthy/opensource/dispatch/src/server.c:197)
> Fri Mar  3 13:49:11 2017 SERVER (trace) [2]:0 <- @transfer(20) [handle=0, 
> delivery-id=4, delivery-tag=b"\x04\x00\x00\x00\x00\x00\x00\x00", 
> message-format=0, settled=true, more=false] (96) 
> "\x00Sp\xd0\x00\x00\x00\x0b\x00\x00\x00\x05BP\x04@BR\x00\x00Ss\xd0\x00\x00\x00"\x00\x00\x00\x0d\x83\x00\x00\x00\x00\x00\x00\x00\x00\x83\x00\x00\x00\x00\x00\x00\x00\x00@R\x00@\x00St\xd1\x00\x00\x00\x0b\x00\x00\x00\x02\xa0\x03seqT\x04\x00Sw\xa0\x0bHello
>  World" (/home/gmurthy/opensource/dispatch/src/server.c:197)
> Fri Mar  3 13:49:11 2017 SERVER (trace) [2]:0 <- @transfer(20) [handle=0, 
> delivery-id=5, delivery-tag=b"\x05\x00\x00\x00\x00\x00\x00\x00", 
> message-format=0, settled=true, more=false] (96) 
> "\x00Sp\xd0\x00\x00\x00\x0b\x00\x00\x00\x05BP\x04@BR\x00\x00Ss\xd0\x00\x00\x00"\x00\x00\x00\x0d\x83\x00\x00\x00\x00\x00\x00\x00\x00\x83\x00\x00\x00\x00\x00\x00\x00\x00@R\x00@\x00St\xd1\x00\x00\x00\x0b\x00\x00\x00\x02\xa0\x03seqT\x05\x00Sw\xa0\x0bHello
>  World" (/home/gmurthy/opensource/dispatch/src/server.c:197)
> Fri Mar  3 13:49:11 2017 SERVER (trace) [2]:0 <- @transfer(20) [handle=0, 
> delivery-id=6, delivery-tag=b"\x06\x00\x00\x00\x00\x00\x00\x00", 
> message-format=0, settled=true, more=false] 

[jira] [Resolved] (DISPATCH-646) Link route tests which test the drain feature fail intermittently

[Ted Ross (JIRA)]

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

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

> Link route tests which test the drain feature fail intermittently
> -
>
> Key: DISPATCH-646
> URL: https://issues.apache.org/jira/browse/DISPATCH-646
> Project: Qpid Dispatch
>  Issue Type: Bug
>  Components: Container
>Affects Versions: 0.7.0
>Reporter: Ganesh Murthy
>Assignee: Ted Ross
> Fix For: 0.8.0
>
>
> There is test called test_www_drain_support_all_messages in 
> system_tests_link_routes that fails intermittently. Here is the output of the 
> test
> {noformat}
> [gmurthy@localhost build]$  /usr/bin/python 
> "/home/gmurthy/opensource/dispatch/build/tests/run.py" "-m" "unittest" "-v" 
> "system_tests_link_routes.LinkRouteTest.test_www_drain_support_all_messages"
> test_www_drain_support_all_messages (system_tests_link_routes.LinkRouteTest) 
> ... 
> FAIL
> ==
> FAIL: test_www_drain_support_all_messages 
> (system_tests_link_routes.LinkRouteTest)
> --
> Traceback (most recent call last):
>   File "/home/gmurthy/opensource/dispatch/tests/system_tests_link_routes.py", 
> line 542, in test_www_drain_support_all_messages
> self.assertEqual(None, drain_support.error)
> AssertionError: None != 'Timeout Expired: sent: 10 rcvd: 7'
> --
> Ran 1 test in 9.421s
> FAILED (failures=1)
> {noformat}
> The test uses 3 routers (routers A, B and C) with router A acting as the 
> broker and the senders and receivers connected router C and they send/receive 
> on link routed addresses. The messages sent to router C are link-routed to 
> router B and go on to router A and are eventually link routed back to router 
> B and finally to a receiver attached to router C.
> The sender sends 10 messages and the receiver initially issues a flow of 4 
> followed by a drain of 20. This means that the remaining 6 messages must come 
> thru to the receiver. The problem in that in router B, the 6 transfers from 
> router A to router B are followed by a response flow frame (drain=true). In 
> router B, this flow frame sometimes  gets ahead of the transfers and shuts 
> down the remaining transfers.
> The following frame trace shows the flow frame coming in from router C and 
> being sent to router A which followed by 6 transfer frames and a response 
> flow frame arriving from router A. Note now that the router B forwards 3 of 
> the 6 transfers to router C and tries sending the response flow frame before 
> the remaining 3 transfers. Because of this the receiver is not seeing all 10 
> messages.
> {noformat}
> Fri Mar  3 13:49:11 2017 SERVER (trace) [3]:4 <- @flow(19) 
> [next-incoming-id=4, incoming-window=2147483647, next-outgoing-id=0, 
> outgoing-window=2147483647, handle=0, delivery-count=4, link-credit=20, 
> drain=true] (/home/gmurthy/opensource/dispatch/src/server.c:197)
> Fri Mar  3 13:49:11 2017 ROUTER_CORE (trace) Core action 'link_flow' 
> (/home/gmurthy/opensource/dispatch/src/router_core/router_core_thread.c:82)
> Fri Mar  3 13:49:11 2017 SERVER (trace) [2]:0 -> @flow(19) 
> [next-incoming-id=4, incoming-window=2147483647, next-outgoing-id=0, 
> outgoing-window=2147483647, handle=0, delivery-count=4, link-credit=20, 
> drain=true] (/home/gmurthy/opensource/dispatch/src/server.c:197)
> Fri Mar  3 13:49:11 2017 SERVER (trace) [2]:0 <- @transfer(20) [handle=0, 
> delivery-id=4, delivery-tag=b"\x04\x00\x00\x00\x00\x00\x00\x00", 
> message-format=0, settled=true, more=false] (96) 
> "\x00Sp\xd0\x00\x00\x00\x0b\x00\x00\x00\x05BP\x04@BR\x00\x00Ss\xd0\x00\x00\x00"\x00\x00\x00\x0d\x83\x00\x00\x00\x00\x00\x00\x00\x00\x83\x00\x00\x00\x00\x00\x00\x00\x00@R\x00@\x00St\xd1\x00\x00\x00\x0b\x00\x00\x00\x02\xa0\x03seqT\x04\x00Sw\xa0\x0bHello
>  World" (/home/gmurthy/opensource/dispatch/src/server.c:197)
> Fri Mar  3 13:49:11 2017 SERVER (trace) [2]:0 <- @transfer(20) [handle=0, 
> delivery-id=5, delivery-tag=b"\x05\x00\x00\x00\x00\x00\x00\x00", 
> message-format=0, settled=true, more=false] (96) 
> "\x00Sp\xd0\x00\x00\x00\x0b\x00\x00\x00\x05BP\x04@BR\x00\x00Ss\xd0\x00\x00\x00"\x00\x00\x00\x0d\x83\x00\x00\x00\x00\x00\x00\x00\x00\x83\x00\x00\x00\x00\x00\x00\x00\x00@R\x00@\x00St\xd1\x00\x00\x00\x0b\x00\x00\x00\x02\xa0\x03seqT\x05\x00Sw\xa0\x0bHello
>  World" (/home/gmurthy/opensource/dispatch/src/server.c:197)
> Fri Mar  3 13:49:11 2017 SERVER (trace) [2]:0 <- @transfer(20) [handle=0, 
> delivery-id=6, delivery-tag=b"\x06\x00\x00\x00\x00\x00\x00\x00", 
> message-format=0, settled=true, more=false] (96) 
> 

[jira] [Commented] (DISPATCH-646) Link route tests which test the drain feature fail intermittently

[ASF subversion and git services (JIRA)]

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

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

Commit 40b52d9fe21d03230914fbc4576cec8f2130ded6 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=40b52d9 ]

DISPATCH-646 - Refactored the core->IO communication around link-specific work 
lists to preserve the order of flows and deliveries.


> Link route tests which test the drain feature fail intermittently
> -
>
> Key: DISPATCH-646
> URL: https://issues.apache.org/jira/browse/DISPATCH-646
> Project: Qpid Dispatch
>  Issue Type: Bug
>  Components: Container
>Affects Versions: 0.8.0
>Reporter: Ganesh Murthy
>Assignee: Ted Ross
>
> There is test called test_www_drain_support_all_messages in 
> system_tests_link_routes that fails intermittently. Here is the output of the 
> test
> {noformat}
> [gmurthy@localhost build]$  /usr/bin/python 
> "/home/gmurthy/opensource/dispatch/build/tests/run.py" "-m" "unittest" "-v" 
> "system_tests_link_routes.LinkRouteTest.test_www_drain_support_all_messages"
> test_www_drain_support_all_messages (system_tests_link_routes.LinkRouteTest) 
> ... 
> FAIL
> ==
> FAIL: test_www_drain_support_all_messages 
> (system_tests_link_routes.LinkRouteTest)
> --
> Traceback (most recent call last):
>   File "/home/gmurthy/opensource/dispatch/tests/system_tests_link_routes.py", 
> line 542, in test_www_drain_support_all_messages
> self.assertEqual(None, drain_support.error)
> AssertionError: None != 'Timeout Expired: sent: 10 rcvd: 7'
> --
> Ran 1 test in 9.421s
> FAILED (failures=1)
> {noformat}
> The test uses 3 routers (routers A, B and C) with router A acting as the 
> broker and the senders and receivers connected router C and they send/receive 
> on link routed addresses. The messages sent to router C are link-routed to 
> router B and go on to router A and are eventually link routed back to router 
> B and finally to a receiver attached to router C.
> The sender sends 10 messages and the receiver initially issues a flow of 4 
> followed by a drain of 20. This means that the remaining 6 messages must come 
> thru to the receiver. The problem in that in router B, the 6 transfers from 
> router A to router B are followed by a response flow frame (drain=true). In 
> router B, this flow frame sometimes  gets ahead of the transfers and shuts 
> down the remaining transfers.
> The following frame trace shows the flow frame coming in from router C and 
> being sent to router A which followed by 6 transfer frames and a response 
> flow frame arriving from router A. Note now that the router B forwards 3 of 
> the 6 transfers to router C and tries sending the response flow frame before 
> the remaining 3 transfers. Because of this the receiver is not seeing all 10 
> messages.
> {noformat}
> Fri Mar  3 13:49:11 2017 SERVER (trace) [3]:4 <- @flow(19) 
> [next-incoming-id=4, incoming-window=2147483647, next-outgoing-id=0, 
> outgoing-window=2147483647, handle=0, delivery-count=4, link-credit=20, 
> drain=true] (/home/gmurthy/opensource/dispatch/src/server.c:197)
> Fri Mar  3 13:49:11 2017 ROUTER_CORE (trace) Core action 'link_flow' 
> (/home/gmurthy/opensource/dispatch/src/router_core/router_core_thread.c:82)
> Fri Mar  3 13:49:11 2017 SERVER (trace) [2]:0 -> @flow(19) 
> [next-incoming-id=4, incoming-window=2147483647, next-outgoing-id=0, 
> outgoing-window=2147483647, handle=0, delivery-count=4, link-credit=20, 
> drain=true] (/home/gmurthy/opensource/dispatch/src/server.c:197)
> Fri Mar  3 13:49:11 2017 SERVER (trace) [2]:0 <- @transfer(20) [handle=0, 
> delivery-id=4, delivery-tag=b"\x04\x00\x00\x00\x00\x00\x00\x00", 
> message-format=0, settled=true, more=false] (96) 
> "\x00Sp\xd0\x00\x00\x00\x0b\x00\x00\x00\x05BP\x04@BR\x00\x00Ss\xd0\x00\x00\x00"\x00\x00\x00\x0d\x83\x00\x00\x00\x00\x00\x00\x00\x00\x83\x00\x00\x00\x00\x00\x00\x00\x00@R\x00@\x00St\xd1\x00\x00\x00\x0b\x00\x00\x00\x02\xa0\x03seqT\x04\x00Sw\xa0\x0bHello
>  World" (/home/gmurthy/opensource/dispatch/src/server.c:197)
> Fri Mar  3 13:49:11 2017 SERVER (trace) [2]:0 <- @transfer(20) [handle=0, 
> delivery-id=5, delivery-tag=b"\x05\x00\x00\x00\x00\x00\x00\x00", 
> message-format=0, settled=true, more=false] (96) 
> 

[jira] [Created] (PROTON-1437) c proactor address info and listen hints

[Alan Conway (JIRA)]

Alan Conway created PROTON-1437:
---

 Summary: c proactor address info and listen hints 
 Key: PROTON-1437
 URL: https://issues.apache.org/jira/browse/PROTON-1437
 Project: Qpid Proton
  Issue Type: Improvement
  Components: proton-c
Affects Versions: 0.17.0
Reporter: Alan Conway
Assignee: Alan Conway
 Fix For: 0.18.0


The C proactor should provide access to the remote network address for incoming 
connections and allow listener hints to be set to control protocols etc. The 
standard BSD `struct addrinfo` will be used to represent the address, this is 
portable to any platform that supports BSD sockets and is (in principle) 
extensible to cover new types of address by adding new values for ai_family



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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

[jira] [Resolved] (PROTON-1422) c libuv proactor should not require extras library

[Alan Conway (JIRA)]

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

Alan Conway resolved PROTON-1422.
-
Resolution: Fixed

> c libuv proactor should not require extras library
> --
>
> Key: PROTON-1422
> URL: https://issues.apache.org/jira/browse/PROTON-1422
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: proton-c
>Affects Versions: 0.17.0
>Reporter: Alan Conway
>Assignee: Alan Conway
> Fix For: 0.18.0
>
>
> The libuv proactor uses pn_url functions from the extras library. It should 
> only use functions from the core library. Provide minimal, private URL 
> functions in core sufficient for the needs of a proactor.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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

[jira] [Resolved] (QPID-7317) Deadlock on publish

[Alan Conway (JIRA)]

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

Alan Conway resolved QPID-7317.
---
Resolution: Fixed

So far this appears to resolve the problem. Will re-open if it any new evidence 
appears

> Deadlock on publish
> ---
>
> Key: QPID-7317
> URL: https://issues.apache.org/jira/browse/QPID-7317
> Project: Qpid
>  Issue Type: Bug
>  Components: Python Client
>Affects Versions: 0.32
> Environment: python-qpid-0.32-13.fc23.noarch
>Reporter: Brian Bouterse
>Assignee: Alan Conway
> Fix For: qpid-python-1.36.0
>
> Attachments: bad_child.py, bad_child.py, bt.txt, lsof.txt, 
> pystack.17806, spout-hang.py, spout-hang-trace.txt, taabt.txt, worker-stacks
>
>
> When publishing a task with qpid.messaging it deadlocks and our application 
> cannot continue. This has not been a problem for several releases, but within 
> a few days recently, another Satellite developer and I both experienced the 
> issue on separate machines, different distros. He is using a MRG built 
> pacakge (not sure of version). I am using python-qpid-0.32-13.fc23.
> Both deadlocked machines had core dumps taken on the deadlocked processes and 
> only show only 1 Qpid thread when I expect there to be 2. There are other 
> mongo threads, but those are idle as expected and not related. The traces 
> show our application calling into qpid.messaging to publish a message to the 
> message bus.
> This problem happens intermittently, and in cases where message publish is 
> successful I've verified by core dump that there are the expected 2 threads 
> for Qpid.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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

[jira] [Updated] (QPID-2520) Broken POM generation on Windows

[Justin Ross (JIRA)]

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

Justin Ross updated QPID-2520:
--
Component/s: (was: Build Tools)
 Java Build

> Broken POM generation on Windows
> 
>
> Key: QPID-2520
> URL: https://issues.apache.org/jira/browse/QPID-2520
> Project: Qpid
>  Issue Type: Bug
>  Components: C++ Tools, Java Build
>Affects Versions: 0.6
>Reporter: Emmanuel Bourg
>Assignee: Robbie Gemmell
> Fix For: 0.7
>
> Attachments: genpom.patch
>
>
> The genpom script doesn't work on Windows. Calling "ant pom" gives the 
> following stacktrace :
> {code}
> pom:
>  [java] Traceback (most recent call last):
>  [java]   File "C:\dev\apache\qpid\java/genpom", line 95, in 
>  [java] pom = search(expanded_path, "%s.pom" % base)
>  [java]   File "C:\dev\apache\qpid\java/genpom", line 83, in search
>  [java] return mllib.xml_parse(f)
>  [java]   File "C:\dev\apache\qpid\python\mllib\__init__.py", line 79, in 
> xml_parse
>  [java] p.parse(source)
>  [java]   File 
> "C:\dev\apache\qpid\java\lib\jython-2.5.0.jar\Lib\xml\sax\drivers2\drv_javasax.py",
>  line 141, in parse
>  [java] at java.io.FileInputStream.open(Native Method)
>  [java] at java.io.FileInputStream.(FileInputStream.java:106)
>  [java] at java.io.FileInputStream.(FileInputStream.java:66)
>  [java] at 
> sun.net.www.protocol.file.FileURLConnection.connect(FileURLConnection.java:70)
>  [java] at 
> sun.net.www.protocol.file.FileURLConnection.getInputStream(FileURLConnection.java:161)
>  [java] at 
> com.sun.org.apache.xerces.internal.impl.XMLEntityManager.setupCurrentEntity(XMLEntityManager.java:653)
>  [java] at 
> com.sun.org.apache.xerces.internal.impl.XMLVersionDetector.determineDocVersion(XMLVersionDetector.java:186)
>  [java] at 
> com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:772)
>  [java] at 
> com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:737)
>  [java] at 
> com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:119)
>  [java] at 
> com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1205)
>  [java] at 
> com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(SAXParserImpl.java:522)
>  [java] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>  [java] at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>  [java] at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>  [java] at java.lang.reflect.Method.invoke(Method.java:597)
>  [java]
>  [java] java.io.FileNotFoundException: java.io.FileNotFoundException: 
> C:\dev\apache\qpid\java\common\dev\apache\qpid\java\lib\poms\slf4j-api-1.4.0.pom
>  (Le chemin d'accès spécifié est introuvable)
> {code}
> It works fine on Linux



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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

[jira] [Updated] (QPID-5610) implement a Maven 3 build for the Java QMF tools and GUI

[Justin Ross (JIRA)]

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

Justin Ross updated QPID-5610:
--
Component/s: (was: Build Tools)
 Java Build

> implement a Maven 3 build for the Java QMF tools and GUI
> 
>
> Key: QPID-5610
> URL: https://issues.apache.org/jira/browse/QPID-5610
> Project: Qpid
>  Issue Type: Improvement
>  Components: Java Build
>Reporter: Robbie Gemmell
>Assignee: Robbie Gemmell
> Fix For: 0.29
>
>
> The work being done in QPID-5048 will add an initial Maven 3 build for the 
> components in the current main java tree, subsequent to which we will look to 
> split the tree apart to become more component oriented.
> As part of the overall process we will also look to implement a Maven 3 build 
> for the Java QMF tools, since these depend on e.g the Java client or the Java 
> broker and currently utilise the output of their existing Ant build. In 
> addition to adopting the new builds for the other components, this will 
> additionally allow deploying them to Maven Central and make it easier to keep 
> the QMF tools functioning.
> This will be a more involved process for the QMF tools than those in 
> QPID-5048, requiring layout changes to adopt a suitable structure in the 
> repository around which to create the new build.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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

[jira] [Updated] (QPID-7266) RAT check fails on release archive due to generated file

[Justin Ross (JIRA)]

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

Justin Ross updated QPID-7266:
--
Component/s: (was: Build Tools)
 Java Build

> RAT check fails on release archive due to generated file
> 
>
> Key: QPID-7266
> URL: https://issues.apache.org/jira/browse/QPID-7266
> Project: Qpid
>  Issue Type: Task
>  Components: Java Build
>Affects Versions: qpid-java-6.0.2
>Reporter: Robbie Gemmell
>Assignee: Robbie Gemmell
> Fix For: qpid-java-6.0.3
>
>
> Running "mvn apache-rat:check" on the source release fails because the 
> generated DEPENDENCIES file fails the check. The RAT config should be updated 
> to skip the file in the immediate term. Long term the file could perhaps be 
> excluded from the archive.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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

[jira] [Updated] (QPID-5046) Change release.sh to use cmake instead of autotools to build the cpp tree

[Justin Ross (JIRA)]

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

Justin Ross updated QPID-5046:
--
Component/s: (was: Build Tools)
 Packaging

> Change release.sh to use cmake instead of autotools to build the cpp tree
> -
>
> Key: QPID-5046
> URL: https://issues.apache.org/jira/browse/QPID-5046
> Project: Qpid
>  Issue Type: Task
>  Components: Packaging
>Affects Versions: 0.24
>Reporter: Justin Ross
>Assignee: Justin Ross
> Fix For: 0.25
>
>
> Autotools is deprecated in 0.24 and removed in 0.26.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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

[jira] [Updated] (QPID-1964) bin/release.sh --help does not work

[Justin Ross (JIRA)]

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

Justin Ross updated QPID-1964:
--
Component/s: (was: Build Tools)
 Packaging

> bin/release.sh --help does not work
> ---
>
> Key: QPID-1964
> URL: https://issues.apache.org/jira/browse/QPID-1964
> Project: Qpid
>  Issue Type: Bug
>  Components: Packaging
>Affects Versions: M4
>Reporter: Jan Sarenik
>Assignee: Aidan Skinner
>Priority: Trivial
> Fix For: 0.6
>
> Attachments: 0001-Make-release.sh-help-work.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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

[jira] [Updated] (QPID-3151) Remove dotnet and ruby from the --all release artifacts

[Justin Ross (JIRA)]

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

Justin Ross updated QPID-3151:
--
Component/s: (was: Build Tools)
 Packaging

> Remove dotnet and ruby from the --all release artifacts
> ---
>
> Key: QPID-3151
> URL: https://issues.apache.org/jira/browse/QPID-3151
> Project: Qpid
>  Issue Type: Improvement
>  Components: Packaging
>Affects Versions: 0.10, 0.11
>Reporter: Justin Ross
>Assignee: Robbie Gemmell
> Fix For: 0.10, 0.11
>
> Attachments: release.sh.patch
>
>
> Since these components are no longer supported, drop them from the release 
> artifacts.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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

[jira] [Updated] (QPID-1861) Update release.sh script to ensure tests are run and pass

[Justin Ross (JIRA)]

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

Justin Ross updated QPID-1861:
--
Component/s: (was: Build Tools)
 Packaging

> Update release.sh script to ensure tests are run and pass 
> --
>
> Key: QPID-1861
> URL: https://issues.apache.org/jira/browse/QPID-1861
> Project: Qpid
>  Issue Type: Task
>  Components: Packaging
>Reporter: Martin Ritchie
>Assignee: Martin Ritchie
> Fix For: 0.5
>
>
> Summary:
> The recent make check failures would have been picked up if we had enforced 
> running tests before we create our release artefacts.
> A quick update to the release.sh script will ensure that these tests are run 
> as part of the release process.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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

[jira] [Updated] (QPID-1429) buildCreator uses fixed location of binarires.

[Justin Ross (JIRA)]

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

Justin Ross updated QPID-1429:
--
Component/s: (was: Build Tools)
 Packaging

> buildCreator uses fixed location of binarires. 
> ---
>
> Key: QPID-1429
> URL: https://issues.apache.org/jira/browse/QPID-1429
> Project: Qpid
>  Issue Type: Bug
>  Components: Packaging
>Reporter: Martin Ritchie
>
> BuildCreator.py uses a fixed location for binaries such as cp , ls, patch etc.
> These fixed locations are validated ons startup. 
> At worst they should be configurable. The users should only have to configure 
> them if they are required.
> i.e. Forcing user to have WGET when there is not a HTTP source is 
> unreasonable.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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

[jira] [Updated] (QPID-1256) Provide build tool for combining source and patches from a variety of sources.

[Justin Ross (JIRA)]

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

Justin Ross updated QPID-1256:
--
Component/s: (was: Build Tools)
 Packaging

> Provide build tool for combining source and patches from a variety of sources.
> --
>
> Key: QPID-1256
> URL: https://issues.apache.org/jira/browse/QPID-1256
> Project: Qpid
>  Issue Type: New Feature
>  Components: Packaging
>Affects Versions: M3
>Reporter: Martin Ritchie
>Assignee: Martin Ritchie
> Fix For: M4
>
>
> Summary:
> This is a tool that I can provide back to the community that allows a variety 
> of sources to be downloaded, patched and built in to a release tar. Whilst 
> this may not have immediate use for this project it could be helpful for 
> users that wish to use the BerkeleyDB Store. 
> The python script currently has some documentation but I aim to document the 
> tool and provide example configurations for an Apache build, which will in 
> essence just use our current build system.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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

[jira] [Updated] (QPID-1354) buildCreator recurses directorys looking for patches.

[Justin Ross (JIRA)]

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

Justin Ross updated QPID-1354:
--
Component/s: (was: Build Tools)
 Packaging

> buildCreator recurses directorys looking for patches.
> -
>
> Key: QPID-1354
> URL: https://issues.apache.org/jira/browse/QPID-1354
> Project: Qpid
>  Issue Type: Bug
>  Components: Packaging
>Affects Versions: M4
>Reporter: Aidan Skinner
> Attachments: QPID-1354.patch
>
>
> The buildCreator script explores directorys and applys any files (ending in 
> *.patch?) that it finds. It should require that the user specify precisely 
> which patches are to be applied and no other.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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

[jira] [Updated] (QPID-1336) [buildCreator] Update to write a revision file in to each build that details the inputs to the build

[Justin Ross (JIRA)]

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

Justin Ross updated QPID-1336:
--
Component/s: (was: Build Tools)
 Packaging

> [buildCreator] Update to write a revision file in to each build that details 
> the inputs to the build
> 
>
> Key: QPID-1336
> URL: https://issues.apache.org/jira/browse/QPID-1336
> Project: Qpid
>  Issue Type: Bug
>  Components: Packaging
>Affects Versions: M3
>Reporter: Martin Ritchie
>Assignee: Rob Godfrey
> Fix For: M4
>
>
> Summary:
> Currently when a build is run there is no details to show what went in to the 
> build in terms of sources and patches.
> This update should allow the release script writer to decide where and when 
> to write this information.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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

[jira] [Updated] (QPID-2987) Implement a Maven 2 build process to replace Ant

[Justin Ross (JIRA)]

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

Justin Ross updated QPID-2987:
--
Component/s: (was: Build Tools)
 Java Build

> Implement a Maven 2 build process to replace Ant
> 
>
> Key: QPID-2987
> URL: https://issues.apache.org/jira/browse/QPID-2987
> Project: Qpid
>  Issue Type: New Feature
>  Components: Java Build
>Reporter: Andrew Kennedy
>Assignee: Andrew Kennedy
>Priority: Minor
> Fix For: Future
>
>
> The current Ant based build system, while adequate, does not lend itself to 
> simple dependency management or production of release artifacts suitable for 
> inclusion in public repositories. This issue is intended to add a parallel 
> build mechanism using Maven 2.2 that uses the existing Ant tasks for the more 
> complex parts of the build (code generation et al) while making the 
> specification of library dependencies much simpler. It is envisaged, that if 
> this system is approved, we could eventually move over to Maven completely 
> and ditch the Ant build files entirely.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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

[jira] [Updated] (QPID-1916) Maven artifacts for the client

[Justin Ross (JIRA)]

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

Justin Ross updated QPID-1916:
--
Component/s: (was: Build Tools)
 Java Build

> Maven artifacts for the client
> --
>
> Key: QPID-1916
> URL: https://issues.apache.org/jira/browse/QPID-1916
> Project: Qpid
>  Issue Type: New Feature
>  Components: Java Build, Java Client, Java Common, Java Tools, QMF
>Affects Versions: M3, M4, 0.5, 0.6, 0.7, 0.8
>Reporter: Bryan Kearney
>Assignee: Andrew Kennedy
>  Labels: ant_build_system
> Fix For: 0.9
>
> Attachments: genpom.patch, mavenize3.patch, maven.patch
>
>
> The attached patch files adds the maven ant tasks to the build system. It 
> allows, on a per-module basis, to support creating a pom file and exporting 
> the jars to a maven repository. This is not a very DRY solution, as it 
> requires copying the dependency information from the build.deps file. I have 
> only added the pom files for the client bits, since i believe these are the 
> most likely to be required by folks using QMF.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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

[jira] [Updated] (QPID-4037) make qpid jar OSGi friendly

[Justin Ross (JIRA)]

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

Justin Ross updated QPID-4037:
--
Component/s: (was: Build Tools)
 Java Build

> make qpid jar OSGi friendly
> ---
>
> Key: QPID-4037
> URL: https://issues.apache.org/jira/browse/QPID-4037
> Project: Qpid
>  Issue Type: Improvement
>  Components: Java Build
>Reporter: Freeman Fang
>
> qpid jar currently isn't OSGi friendly, so for those who wanna use it in OSGi 
> container, must wrap it with tool like bnd/maven-bundle-plugin. Apache 
> Servicemix always wrap 3rd party jars which isn't OSGi friendly, you can see 
> we've done it for lots of jars here[1], more specifically for several qpid 
> versions[2]. Though we may keep this way doing it, the problem is that we 
> need do it for every new released version for 3rd party jars, more 
> importantly we need ensure other Apache projects communities are aware of 
> we're doing it.
> In Servicemix we just wrap qpid 0.16, issues to track it in Servicemix is[3].
> We hope Apache QPID can offer OSGi friendly jars, in most cases, it's should 
> be straightforward, as it just need add OSGi metadata headers to MANIFEST.MF, 
> this could be done easily with maven-bundle-plugin if build with maven. 
> There's also some other practice should be followed like different modules 
> shouldn't share same package(avoid split pacakge).
> thanks
> [1]http://repo2.maven.org/maven2/org/apache/servicemix/bundles
> [2]http://repo2.maven.org/maven2/org/apache/servicemix/bundles/org.apache.servicemix.bundles.qpid/
> [3]https://issues.apache.org/jira/browse/SMX4-1148



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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

[jira] [Updated] (QPID-3124) Update release script for new build artifacts

[Justin Ross (JIRA)]

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

Justin Ross updated QPID-3124:
--
Component/s: (was: Build Tools)
 Packaging

> Update release script for new build artifacts
> -
>
> Key: QPID-3124
> URL: https://issues.apache.org/jira/browse/QPID-3124
> Project: Qpid
>  Issue Type: Improvement
>  Components: Packaging
>Affects Versions: 0.10, 0.11
>Reporter: Justin Ross
>Assignee: Robbie Gemmell
> Fix For: 0.10, 0.11
>
> Attachments: release.sh.patch
>
>
> This patch (1) fixes the scripting for maven artifacts and (2) adds scripting 
> for the qmf and tools components.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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

[jira] [Updated] (QPID-3149) Set up Hudson Continuous Integration

[Justin Ross (JIRA)]

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

Justin Ross updated QPID-3149:
--
Component/s: Java Build

> Set up Hudson Continuous Integration
> 
>
> Key: QPID-3149
> URL: https://issues.apache.org/jira/browse/QPID-3149
> Project: Qpid
>  Issue Type: Task
>  Components: Build Tools, Java Build
>Reporter: Andrew Kennedy
>Assignee: Andrew Kennedy
>Priority: Minor
>  Labels: build, hudson, qpid
>
> Set up a Continuous Integration build environment for Java and C++ with full 
> unit, system and integration test suites being run, as well as the Python 
> test kit. This will use the ASF Hudson infrastructure, and will build on both 
> Unix and Windows environments. See here for details:
> http://wiki.apache.org/general/Hudson



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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

[jira] [Updated] (QPID-4195) Add AMQP 1.0 JMS client to release script

[Justin Ross (JIRA)]

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

Justin Ross updated QPID-4195:
--
Component/s: (was: Build Tools)
 Packaging

> Add AMQP 1.0 JMS client to release script
> -
>
> Key: QPID-4195
> URL: https://issues.apache.org/jira/browse/QPID-4195
> Project: Qpid
>  Issue Type: Improvement
>  Components: Packaging
>Reporter: Rob Godfrey
>Assignee: Rob Godfrey
> Fix For: 0.19
>
>
> Add the AMQP 1.0 JMS client, and the java 1.0 AMQP 1.0 pom generation to the 
> release script



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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

[jira] [Updated] (QPID-4363) memory leak in Java message broker resulting in out of memory exception being thrown

[Justin Ross (JIRA)]

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

Justin Ross updated QPID-4363:
--
Component/s: (was: Build Tools)
 Java Broker

> memory leak in Java message broker resulting in out of memory exception being 
> thrown
> 
>
> Key: QPID-4363
> URL: https://issues.apache.org/jira/browse/QPID-4363
> Project: Qpid
>  Issue Type: Bug
>  Components: Java Broker
>Affects Versions: 0.18
>Reporter: Derrick
> Fix For: 0.18
>
>
> The message broker consumes memory when receiving messages. The memory is not 
> freed and the broker crashes and throws an out of Memory Exception.
> Using the jmx monitor shows that the queue depth is < 10 when the broker 
> crashes



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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

[jira] [Updated] (QPID-5048) [Java] Implement a Maven 3 build system

[Justin Ross (JIRA)]

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

Justin Ross updated QPID-5048:
--
Component/s: (was: Build Tools)
 Java Build

> [Java] Implement a Maven 3 build system 
> 
>
> Key: QPID-5048
> URL: https://issues.apache.org/jira/browse/QPID-5048
> Project: Qpid
>  Issue Type: Task
>  Components: Java Build
>Reporter: Rob Godfrey
>Assignee: Robbie Gemmell
> Fix For: 0.29
>
> Attachments: 
> 0001-NO-JIRA-fix-to-resolve-potential-parse-error-in-Abst.patch, 
> 0001-QPID-5048-added-basic-cpp-broker-test-profile.patch, 
> 0001-QPID-5048-changes-get-perf-tests-running-again.patch, 
> 0001-QPID-5048-dby-profiles-bdb-test-deps-and-config-for-.patch, 
> 0001-QPID-5048-Maven-enahancements-to-remove-child-versio.patch, 
> 0001-QPID-5048-Maven-enahancements-to-restructure-POM-hie.patch, 
> 0001-QPID-5048-maven-license-plugin-optimisation-enhanced.patch, 
> 0001-QPID-5048-Maven-POM-refactoring-names-descriptions-d.patch, 
> 0001-QPID-5048-modified-deployment-plugin-config-so-only-.patch, 
> 0001-QPID-5048-Moved-slf4j-deps-to-test-utils-to-workarou.patch, 
> 0001-QPID-5048-new-maven-enforcer-plugin-rule-for-checkin.patch, 
> 0001-QPID-5048-parent-pom-changes-for-release-license-and.patch, 
> 0001-QPID-5048-remove-enforcer-rule-that-requires-enable-.patch, 
> 0001-QPID-5048-split-out-systests-from-perftests-and-add-.patch, 
> 0001-QPID-5048-surefire-site-coverage-and-jxr-config.patch, 
> 0001-QPID-5048-update-qpid-parent-pom-to-inherit-from-lat.patch, 
> 0001-QPID-5048-update-qpid-parent-pom-to-remove-dependenc.patch, 
> 0002-QPID-5048-added-dependency-license-reference-checkin.patch, 
> 0002-QPID-5048-Logging-dependency-and-configuration-tidy-.patch, 
> 0002-QPID-5048-re-instate-dependency-versions-after-qpid-.patch, 
> 0003-QPID-5048-logging-and-build-output-cleanup.patch, 
> QPID-5048-maven-qpid-parent-changes.diff
>
>
> Implement a Maven build system which generates the same artefacts as the 
> current ant based build.  
> See: https://cwiki.apache.org/confluence/display/qpid/Java+Build+System
> TO DO
> - Fix what the systests/perftests do to copy the test-profiles dir to the 
> necessary location.
> - Test deploying the modules to a local Nexus instance (by overriding the 
> repo properties locally).
> - Ensure we dont deploy modules we aren't already doing so, it will make 
> changing them later less of a pain for everyone.
> - Align the XML in the pom files consistently, fix whitepsace errors.
> - improve the performance hit from using the license plugin
> - check that perf-tests actually needs the unpacked broker for running non 
> spawn profiles and remove if not
> - remove the child module version to let them inherit from java parent
> - check the bcel bundle dependancy exclusions are still required
> === Once the Ant build is removed ===
> - Move all the resources to be in the /src/foo/resources folders.
> - Make qpidversion.properties in common be a filtered resource instead of 
> generated.
> - Get rid of the antrun-plugin execution in common, directly invoke the 
> required java elements.
> - Do the above in the generate-sources-common profile instead of current 
> default config.
> - Get rid of the antrun-plugin execution in broker-core, directly invoke the 
> required java elements.
> - Fix the tests not to be dependant on the working dir being the java dir.
> - Fix the tests not to be dependant on the test config/output dirs being 
> children of qpid.home.
> - Remove the QBTC output file mechanics, rely on Surefire to do it?
> - JUnit test profiles instead of Exludes files?



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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

[jira] [Updated] (QPID-5996) [Java Build] Test coverage reports are not currently working

[Justin Ross (JIRA)]

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

Justin Ross updated QPID-5996:
--
Component/s: (was: Build Tools)
 Java Build

> [Java Build] Test coverage reports are not currently working
> 
>
> Key: QPID-5996
> URL: https://issues.apache.org/jira/browse/QPID-5996
> Project: Qpid
>  Issue Type: Bug
>  Components: Java Build
>Reporter: Rob Godfrey
>Assignee: Rob Godfrey
> Fix For: 0.30
>
> Attachments: QPID-5996.patch
>
>
> According to 
> https://cwiki.apache.org/confluence/display/qpid/Qpid+Java+Build+How+To
> mvn test jacoco:report
> should execute the unit tests and then produce the code coverage report.
> It does the former, but not the latter.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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

[jira] [Updated] (QPID-5047) Release.sh is written to bash, not sh, and has an incorrect shebang

[Justin Ross (JIRA)]

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

Justin Ross updated QPID-5047:
--
Component/s: (was: Build Tools)
 Packaging

> Release.sh is written to bash, not sh, and has an incorrect shebang
> ---
>
> Key: QPID-5047
> URL: https://issues.apache.org/jira/browse/QPID-5047
> Project: Qpid
>  Issue Type: Bug
>  Components: Packaging
>Affects Versions: 0.24
>Reporter: Justin Ross
>Assignee: Justin Ross
> Fix For: 0.31
>
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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

[jira] [Updated] (QPID-6010) [Java Tests] Use context value defaulting for setting the protocols in use, rather than a system property

[Justin Ross (JIRA)]

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

Justin Ross updated QPID-6010:
--
Component/s: Java Tests
 Java Broker

> [Java Tests] Use context value defaulting for setting the protocols in use, 
> rather than a system property 
> --
>
> Key: QPID-6010
> URL: https://issues.apache.org/jira/browse/QPID-6010
> Project: Qpid
>  Issue Type: Improvement
>  Components: Java Broker, Java Build, Java Tests
>Reporter: Rob Godfrey
>Assignee: Keith Wall
> Fix For: 0.30
>
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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

[jira] [Updated] (QPID-6010) [Java Tests] Use context value defaulting for setting the protocols in use, rather than a system property

[Justin Ross (JIRA)]

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

Justin Ross updated QPID-6010:
--
Component/s: (was: Build Tools)
 (was: Java Broker)
 Java Build

> [Java Tests] Use context value defaulting for setting the protocols in use, 
> rather than a system property 
> --
>
> Key: QPID-6010
> URL: https://issues.apache.org/jira/browse/QPID-6010
> Project: Qpid
>  Issue Type: Improvement
>  Components: Java Broker, Java Build, Java Tests
>Reporter: Rob Godfrey
>Assignee: Keith Wall
> Fix For: 0.30
>
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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

[jira] [Updated] (QPID-6777) [Java] Change parent pom for qpid-java-build to apache-parent

[Justin Ross (JIRA)]

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

Justin Ross updated QPID-6777:
--
Component/s: (was: Build Tools)
 Java Build

> [Java] Change parent pom for qpid-java-build to apache-parent
> -
>
> Key: QPID-6777
> URL: https://issues.apache.org/jira/browse/QPID-6777
> Project: Qpid
>  Issue Type: Improvement
>  Components: Java Broker, Java Build, Java Client, Java Common, Java 
> Performance Tests, Java Tests, Java Tools, JCA, Packaging
>Affects Versions: qpid-java-6.0
>Reporter: Alex Rudyy
> Fix For: qpid-java-6.0
>
>
> Currently java components have a parent pom set to qpid-parent. We agreed 
> \[1\] that qpid-parent should be replaced with apache-parent as apache-parent 
> is updated and released regularly whilst releasing of qpid-parent creates an 
> extra overhead into our release process.
> \[1\] 
> [http://mail-archives.apache.org/mod_mbox/qpid-dev/201510.mbox/%3CCAFitrpTjSOtukQCaDOHchcwS0POi56DQrwV9uL2ca3fqFDZ6rg%40mail.gmail.com%3E]



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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

[jira] [Updated] (QPID-5307) Change test scripts to cross-platform language

[Justin Ross (JIRA)]

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

Justin Ross updated QPID-5307:
--
Component/s: (was: C++ Client)
 (was: C++ Broker)
 C++ Tests

> Change test scripts to cross-platform language
> --
>
> Key: QPID-5307
> URL: https://issues.apache.org/jira/browse/QPID-5307
> Project: Qpid
>  Issue Type: Improvement
>  Components: C++ Tests
>Reporter: Steve Huston
>Assignee: Justin Ross
>  Labels: test
> Fix For: Future
>
> Attachments: review.diff
>
>
> The C++ tree's test suite drivers are primarily shell scripts. Many were 
> duplicated as Windows PowerShell scripts along the way. However, not all 
> scripts were PowerShell-ized, and the dual set of test scripts is not 
> maintained in sync. Someone (Cliff?) suggested a while back that the test 
> driver scripts be written in a common language across Linux and Windows, and 
> for other platforms as well.
> Python, Perl, Ruby are all possible choices - python and ruby need to be on 
> build systems anyway for code generation. What do people think about a) this 
> idea in general, b) language to use?



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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

[jira] [Updated] (QPID-5307) Change test scripts to cross-platform language

[Justin Ross (JIRA)]

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

Justin Ross updated QPID-5307:
--
Component/s: (was: C++ Clustering)

> Change test scripts to cross-platform language
> --
>
> Key: QPID-5307
> URL: https://issues.apache.org/jira/browse/QPID-5307
> Project: Qpid
>  Issue Type: Improvement
>  Components: C++ Broker, C++ Client
>Reporter: Steve Huston
>Assignee: Justin Ross
>  Labels: test
> Fix For: Future
>
> Attachments: review.diff
>
>
> The C++ tree's test suite drivers are primarily shell scripts. Many were 
> duplicated as Windows PowerShell scripts along the way. However, not all 
> scripts were PowerShell-ized, and the dual set of test scripts is not 
> maintained in sync. Someone (Cliff?) suggested a while back that the test 
> driver scripts be written in a common language across Linux and Windows, and 
> for other platforms as well.
> Python, Perl, Ruby are all possible choices - python and ruby need to be on 
> build systems anyway for code generation. What do people think about a) this 
> idea in general, b) language to use?



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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

[jira] [Assigned] (QPID-5307) Change test scripts to cross-platform language

[Justin Ross (JIRA)]

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

Justin Ross reassigned QPID-5307:
-

Assignee: Justin Ross  (was: Steve Huston)

> Change test scripts to cross-platform language
> --
>
> Key: QPID-5307
> URL: https://issues.apache.org/jira/browse/QPID-5307
> Project: Qpid
>  Issue Type: Improvement
>  Components: C++ Broker, C++ Client
>Reporter: Steve Huston
>Assignee: Justin Ross
>  Labels: test
> Fix For: Future
>
> Attachments: review.diff
>
>
> The C++ tree's test suite drivers are primarily shell scripts. Many were 
> duplicated as Windows PowerShell scripts along the way. However, not all 
> scripts were PowerShell-ized, and the dual set of test scripts is not 
> maintained in sync. Someone (Cliff?) suggested a while back that the test 
> driver scripts be written in a common language across Linux and Windows, and 
> for other platforms as well.
> Python, Perl, Ruby are all possible choices - python and ruby need to be on 
> build systems anyway for code generation. What do people think about a) this 
> idea in general, b) language to use?



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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

[jira] [Updated] (QPID-2963) doxygen-generated C++ docs lost CSS references

[Justin Ross (JIRA)]

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

Justin Ross updated QPID-2963:
--
Component/s: (was: Documentation)
 C++ Documentation

> doxygen-generated C++ docs lost CSS references
> --
>
> Key: QPID-2963
> URL: https://issues.apache.org/jira/browse/QPID-2963
> Project: Qpid
>  Issue Type: Bug
>  Components: C++ Documentation
>Affects Versions: 0.7
>Reporter: Steve Huston
>Assignee: Robbie Gemmell
>Priority: Minor
> Fix For: 0.9
>
> Attachments: header.html.patch
>
>
> The svn checkin at r95722 removed the CSS references from 
> qpid/cpp/docs/api/header.html - this caused the generated html to lose the 
> CSS references and the tab navigation, etc. The web content hasn't been 
> regenerated since before this change so it still looks ok.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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

[jira] [Updated] (QPID-2850) Context Free Grammar definition seems to be incomplete

[Justin Ross (JIRA)]

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

Justin Ross updated QPID-2850:
--
Component/s: (was: Documentation)
 C++ Documentation

> Context Free Grammar definition seems to be incomplete
> --
>
> Key: QPID-2850
> URL: https://issues.apache.org/jira/browse/QPID-2850
> Project: Qpid
>  Issue Type: Bug
>  Components: C++ Documentation
>Affects Versions: 0.7
>Reporter: William Henry
>
> In the document Programming With Apache Qpid.
> The BNF for the addressing does not define several nonterminals:
>  
> 
> 
> 
> 
> And it's not always clear what is a terminal and a nonterminal. Is the 
> grammar consistently using <> for nonterminals? And tokens are defined but 
> don't seem to be used e.g. in
> subject := ( part | quoted | "/" )*
> Should "/" be defined as SLASH?
> subject := ( part | quoted | SLASH )*
> subject := ( part | quoted | )*



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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

[jira] [Assigned] (QPID-2850) Context Free Grammar definition seems to be incomplete

[Justin Ross (JIRA)]

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

Justin Ross reassigned QPID-2850:
-

Assignee: Justin Ross

> Context Free Grammar definition seems to be incomplete
> --
>
> Key: QPID-2850
> URL: https://issues.apache.org/jira/browse/QPID-2850
> Project: Qpid
>  Issue Type: Bug
>  Components: C++ Documentation
>Affects Versions: 0.7
>Reporter: William Henry
>Assignee: Justin Ross
>
> In the document Programming With Apache Qpid.
> The BNF for the addressing does not define several nonterminals:
>  
> 
> 
> 
> 
> And it's not always clear what is a terminal and a nonterminal. Is the 
> grammar consistently using <> for nonterminals? And tokens are defined but 
> don't seem to be used e.g. in
> subject := ( part | quoted | "/" )*
> Should "/" be defined as SLASH?
> subject := ( part | quoted | SLASH )*
> subject := ( part | quoted | )*



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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