[jira] [Created] (QPID-4316) qpid aborts with FrameDecoder exception Assertion `b.available() == 0' failed
Andrea Barisani created QPID-4316:
-
Summary: qpid aborts with FrameDecoder exception Assertion
`b.available() == 0' failed
Key: QPID-4316
URL: https://issues.apache.org/jira/browse/QPID-4316
Project: Qpid
Issue Type: Bug
Components: C++ Broker
Affects Versions: 0.16
Environment: CentOS Linux 5.5 64bit
Reporter: Andrea Barisani
All stable qpid versions from 0.8 to 0.16 routinely crash with the following
exception on our setup:
2012-09-18 06:01:03 debug No messages to dispatch on queue '192.168.100.192.0'
2012-09-18 06:01:03 trace cluster(10.22.200.2:12586 READY) DLVR 2339671:
Frame[BEbe; channel=0; {ClusterConnectionDeliverDoOutputBody: limit=2048; }]
control 10.22.200.4:15196-3
2012-09-18 06:01:03 debug Sufficient credit for buffer-192.168.100.193.0 on
anonymous.session-4-350fa3c0-fea2-11e1-bd79-d4ae52bb0582, have bytes:
4294967295 msgs: 4294967295, need 13965 bytes
2012-09-18 06:01:03 debug Credit allocated for buffer-192.168.100.193.0 on
anonymous.session-4-350fa3c0-fea2-11e1-bd79-d4ae52bb0582, was bytes:
4294967295 msgs: 4294967295 now bytes: 4294967295 msgs: 4294967295
2012-09-18 06:01:03 trace
anonymous.session-4-350fa3c0-fea2-11e1-bd79-d4ae52bb0582: sent cmd 197949:
{MessageTransferBody: destination=buffer-192.168.100.193.0; accept-mode=0;
acquire-mode=0; }
2012-09-18 06:01:03 trace
anonymous.session-4-350fa3c0-fea2-11e1-bd79-d4ae52bb0582: sent cmd 197949:
header (46 bytes); properties={{MessageProperties: content-type=text/plain;
}{DeliveryProperties: exchange=replication-mx.0; routing-key=#; }}
2012-09-18 06:01:03 trace
anonymous.session-4-350fa3c0-fea2-11e1-bd79-d4ae52bb0582: sent cmd 197949:
content (13919 bytes) \x04\x08{\x08:
Document: data{\x1Dc...
2012-09-18 06:01:03 debug No messages to dispatch on queue '192.168.100.193.0'
2012-09-18 06:01:03 trace MCAST Event[10.22.200.2:12586-1 data 28 bytes]
2012-09-18 06:01:03 trace cluster(10.22.200.2:12586 READY) DLVR 2339672:
Frame[BEbe; channel=0; {MessageAcceptBody: transfers={ [186207,186207] }; }]
data 10.22.200.2:12586-1 read-credit=1
2012-09-18 06:01:03 trace
anonymous.session-2-d0d6be80-fe87-11e1-b474-0026b97689bc: recv cmd 412347:
{MessageAcceptBody: transfers={ [186207,186207] }; }
2012-09-18 06:01:03 debug DeliveryRecord::setEnded() id=186207
2012-09-18 06:01:03 debug Accepted 186207
2012-09-18 06:01:03 debug
anonymous.session-2-d0d6be80-fe87-11e1-b474-0026b97689bc: receiver marked
completed: 412347 incomplete: { } unknown-completed: { [393216,412347] }
2012-09-18 06:01:03 trace SENT [127.0.0.1:5672-127.0.0.1:59842]: Frame[BEbe;
channel=0; {SessionCompletedBody: commands={ [393216,412347] }; }]
2012-09-18 06:01:03 trace cluster(10.22.200.2:12586 READY) DLVR 2339673:
null-frame data 10.22.200.3:21966-2 read-credit=1
2012-09-18 06:01:03 trace MCAST Event[10.22.200.2:12586-0 Frame[BEbe;
channel=0; {ClusterClockBody: time=1347940863856643000; }]]
qpidd: qpid/framing/FrameDecoder.cpp:63: bool
qpid::framing::FrameDecoder::decode(qpid::framing::Buffer): Assertion
`b.available() == 0' failed.
We cannot confirm if the issue is present in version 0.18 because a different
exception for a possibly different problem is triggered before we get a chance
to witness this one (I'll file a separate report for that).
We are using corosync for virtual synchrony, qpid is compiled from the C++
broker with default configure flags + --with-cpg. The cluster has auth=no in
the configuration and no further tuning.
Cheers
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Assigned] (QPID-4317) make browse-only x-arg similar to others.
[ https://issues.apache.org/jira/browse/QPID-4317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] michael j. goulish reassigned QPID-4317: Assignee: michael j. goulish make browse-only x-arg similar to others. - Key: QPID-4317 URL: https://issues.apache.org/jira/browse/QPID-4317 Project: Qpid Issue Type: Improvement Components: C++ Broker Reporter: michael j. goulish Assignee: michael j. goulish Priority: Minor Make the x-arg string for the new browse-only queue feature qpid.browse-only to be similar to (almost all of) the others. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (QPID-4317) make browse-only x-arg similar to others.
michael j. goulish created QPID-4317: Summary: make browse-only x-arg similar to others. Key: QPID-4317 URL: https://issues.apache.org/jira/browse/QPID-4317 Project: Qpid Issue Type: Improvement Components: C++ Broker Reporter: michael j. goulish Priority: Minor Make the x-arg string for the new browse-only queue feature qpid.browse-only to be similar to (almost all of) the others. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-4317) make browse-only x-arg similar to others.
[ https://issues.apache.org/jira/browse/QPID-4317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13457797#comment-13457797 ] michael j. goulish commented on QPID-4317: -- done in rev 1387135. make browse-only x-arg similar to others. - Key: QPID-4317 URL: https://issues.apache.org/jira/browse/QPID-4317 Project: Qpid Issue Type: Improvement Components: C++ Broker Reporter: michael j. goulish Assignee: michael j. goulish Priority: Minor Fix For: 0.19 Make the x-arg string for the new browse-only queue feature qpid.browse-only to be similar to (almost all of) the others. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (QPID-4317) make browse-only x-arg similar to others.
[ https://issues.apache.org/jira/browse/QPID-4317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] michael j. goulish resolved QPID-4317. -- Resolution: Fixed Fix Version/s: 0.19 done in rev 1387135. make browse-only x-arg similar to others. - Key: QPID-4317 URL: https://issues.apache.org/jira/browse/QPID-4317 Project: Qpid Issue Type: Improvement Components: C++ Broker Reporter: michael j. goulish Assignee: michael j. goulish Priority: Minor Fix For: 0.19 Make the x-arg string for the new browse-only queue feature qpid.browse-only to be similar to (almost all of) the others. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (QPID-4318) QpidConnectionFactoryProxy should implement Queue/Topic Connection factory API's to support older clients
Weston M. Price created QPID-4318: - Summary: QpidConnectionFactoryProxy should implement Queue/Topic Connection factory API's to support older clients Key: QPID-4318 URL: https://issues.apache.org/jira/browse/QPID-4318 Project: Qpid Issue Type: Improvement Components: JCA Affects Versions: 0.18 Environment: All supported OS platforms, all supported JEE platforms. Reporter: Weston M. Price Assignee: Weston M. Price Priority: Minor Fix For: 0.19 Currently the QpidConnectionFactoryProxy only implements the javax.jms.ConnectionFactory API. We are seeing issues in varying JEE environments where certain containers depend on the ConnectionFactory implementing either Queue or Topic connection factory. In order to address this, the ConnectioFactoryProxy should implement the messaging domain specific API. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (QPID-4319) Perf test VaryingNumberOfParticipants produced broker exception Metadata not found for message with id nnnnn [error code 541: internal error]
Keith Wall created QPID-4319:
Summary: Perf test VaryingNumberOfParticipants produced broker
exception Metadata not found for message with id n [error code 541:
internal error]
Key: QPID-4319
URL: https://issues.apache.org/jira/browse/QPID-4319
Project: Qpid
Issue Type: Bug
Components: Java Broker
Affects Versions: 0.18
Reporter: Keith Wall
Running the complete perf testsuite (perftest/etc/testdef), I ran into the
following failure. The test had reached VaryingNumberOfParticipants - 1
consumer - 10 producers - PERSISTENT and the Broker was struggling for memory
(1gb heap).
The client stack was:
{code}
2012-09-18 14:57:56,197 ERROR [IoSender - localhost/127.0.0.1:5672] [IoSender]
error in write thread
java.net.SocketException: Broken pipe
at java.net.SocketOutputStream.socketWrite0(Native Method)
at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92)
at java.net.SocketOutputStream.write(SocketOutputStream.java:136)
at org.apache.qpid.transport.network.io.IoSender.run(IoSender.java:313)
at java.lang.Thread.run(Thread.java:662)
{code}
whilst the Broker stack was:
{code}
2012-09-18 14:57:56,094 ERROR [IoReceiver - /127.0.0.1:49348]
(AMQProtocolEngine.java:258) - Unexpected exception when processing datablock
java.lang.RuntimeException: org.apache.qpid.AMQStoreException: Metadata not
found for message with id 22902968 [error code 541: internal error]
at
org.apache.qpid.server.store.berkeleydb.AbstractBDBMessageStore$StoredBDBMessage.getMetaData(AbstractBDBMessageStore.java:1615)
at
org.apache.qpid.server.message.AMQMessage.getMessageMetaData(AMQMessage.java:93)
at
org.apache.qpid.server.message.AMQMessage.getArrivalTime(AMQMessage.java:160)
at
org.apache.qpid.server.queue.SimpleAMQQueue.getOldestMessageArrivalTime(SimpleAMQQueue.java:1057)
at
org.apache.qpid.server.queue.NotificationCheck$4.notifyIfNecessary(NotificationCheck.java:104)
at
org.apache.qpid.server.queue.SimpleAMQQueue.checkForNotification(SimpleAMQQueue.java:2327)
at
org.apache.qpid.server.queue.SimpleAMQQueue.enqueue(SimpleAMQQueue.java:766)
at
org.apache.qpid.server.AMQChannel$MessageDeliveryAction.postCommit(AMQChannel.java:1207)
at
org.apache.qpid.server.AMQChannel$AsyncCommand.complete(AMQChannel.java:1674)
at org.apache.qpid.server.AMQChannel.sync(AMQChannel.java:1644)
at
org.apache.qpid.server.AMQChannel.receivedComplete(AMQChannel.java:221)
at
org.apache.qpid.server.protocol.AMQProtocolEngine.receiveComplete(AMQProtocolEngine.java:271)
at
org.apache.qpid.server.protocol.AMQProtocolEngine.received(AMQProtocolEngine.java:254)
at
org.apache.qpid.server.protocol.AMQProtocolEngine.received(AMQProtocolEngine.java:85)
at
org.apache.qpid.server.protocol.MultiVersionProtocolEngine.received(MultiVersionProtocolEngine.java:118)
at
org.apache.qpid.server.protocol.MultiVersionProtocolEngine.received(MultiVersionProtocolEngine.java:37)
at
org.apache.qpid.transport.network.io.IoReceiver.run(IoReceiver.java:152)
at java.lang.Thread.run(Thread.java:662)
Caused by: org.apache.qpid.AMQStoreException: Metadata not found for message
with id 22902968 [error code 541: internal error]
at
org.apache.qpid.server.store.berkeleydb.AbstractBDBMessageStore.getMessageMetaData(AbstractBDBMessageStore.java:1417)
at
org.apache.qpid.server.store.berkeleydb.AbstractBDBMessageStore$StoredBDBMessage.getMetaData(AbstractBDBMessageStore.java:1611)
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-4319) Perf test VaryingNumberOfParticipants produced broker exception Metadata not found for message with id nnnnn [error code 541: internal error]
[
https://issues.apache.org/jira/browse/QPID-4319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Keith Wall updated QPID-4319:
-
Attachment: Screenshot-Java Monitoring Management Console.png
Perf test VaryingNumberOfParticipants produced broker exception Metadata not
found for message with id n [error code 541: internal error]
-
Key: QPID-4319
URL: https://issues.apache.org/jira/browse/QPID-4319
Project: Qpid
Issue Type: Bug
Components: Java Broker
Affects Versions: 0.18
Reporter: Keith Wall
Attachments: Screenshot-Java Monitoring Management Console.png
Running the complete perf testsuite (perftest/etc/testdef), I ran into the
following failure. The test had reached VaryingNumberOfParticipants - 1
consumer - 10 producers - PERSISTENT and the Broker was struggling for memory
(1gb heap).
The client stack was:
{code}
2012-09-18 14:57:56,197 ERROR [IoSender - localhost/127.0.0.1:5672]
[IoSender] error in write thread
java.net.SocketException: Broken pipe
at java.net.SocketOutputStream.socketWrite0(Native Method)
at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92)
at java.net.SocketOutputStream.write(SocketOutputStream.java:136)
at
org.apache.qpid.transport.network.io.IoSender.run(IoSender.java:313)
at java.lang.Thread.run(Thread.java:662)
{code}
whilst the Broker stack was:
{code}
2012-09-18 14:57:56,094 ERROR [IoReceiver - /127.0.0.1:49348]
(AMQProtocolEngine.java:258) - Unexpected exception when processing datablock
java.lang.RuntimeException: org.apache.qpid.AMQStoreException: Metadata not
found for message with id 22902968 [error code 541: internal error]
at
org.apache.qpid.server.store.berkeleydb.AbstractBDBMessageStore$StoredBDBMessage.getMetaData(AbstractBDBMessageStore.java:1615)
at
org.apache.qpid.server.message.AMQMessage.getMessageMetaData(AMQMessage.java:93)
at
org.apache.qpid.server.message.AMQMessage.getArrivalTime(AMQMessage.java:160)
at
org.apache.qpid.server.queue.SimpleAMQQueue.getOldestMessageArrivalTime(SimpleAMQQueue.java:1057)
at
org.apache.qpid.server.queue.NotificationCheck$4.notifyIfNecessary(NotificationCheck.java:104)
at
org.apache.qpid.server.queue.SimpleAMQQueue.checkForNotification(SimpleAMQQueue.java:2327)
at
org.apache.qpid.server.queue.SimpleAMQQueue.enqueue(SimpleAMQQueue.java:766)
at
org.apache.qpid.server.AMQChannel$MessageDeliveryAction.postCommit(AMQChannel.java:1207)
at
org.apache.qpid.server.AMQChannel$AsyncCommand.complete(AMQChannel.java:1674)
at org.apache.qpid.server.AMQChannel.sync(AMQChannel.java:1644)
at
org.apache.qpid.server.AMQChannel.receivedComplete(AMQChannel.java:221)
at
org.apache.qpid.server.protocol.AMQProtocolEngine.receiveComplete(AMQProtocolEngine.java:271)
at
org.apache.qpid.server.protocol.AMQProtocolEngine.received(AMQProtocolEngine.java:254)
at
org.apache.qpid.server.protocol.AMQProtocolEngine.received(AMQProtocolEngine.java:85)
at
org.apache.qpid.server.protocol.MultiVersionProtocolEngine.received(MultiVersionProtocolEngine.java:118)
at
org.apache.qpid.server.protocol.MultiVersionProtocolEngine.received(MultiVersionProtocolEngine.java:37)
at
org.apache.qpid.transport.network.io.IoReceiver.run(IoReceiver.java:152)
at java.lang.Thread.run(Thread.java:662)
Caused by: org.apache.qpid.AMQStoreException: Metadata not found for message
with id 22902968 [error code 541: internal error]
at
org.apache.qpid.server.store.berkeleydb.AbstractBDBMessageStore.getMessageMetaData(AbstractBDBMessageStore.java:1417)
at
org.apache.qpid.server.store.berkeleydb.AbstractBDBMessageStore$StoredBDBMessage.getMetaData(AbstractBDBMessageStore.java:1611)
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (QPID-4320) Python client causes Windows firewall denial
Balázs Miklós created QPID-4320:
---
Summary: Python client causes Windows firewall denial
Key: QPID-4320
URL: https://issues.apache.org/jira/browse/QPID-4320
Project: Qpid
Issue Type: Bug
Components: Python Client
Affects Versions: 0.18
Environment: Python 2.7 on Windows XP, Vista, or 7
Client running as regular user.
Reporter: Balázs Miklós
Priority: Minor
When running a simple message producer program that sends messages to a remote
QPID broker from a Windows client, a Windows Firewall dialog comes up saying
that it prohibited the program from accepting remote connections.
Afterwards, the QPID client seems to work even with the firewall prohibition
rule in place.
I have traced the problem down to the listener.bind call in the method
SockWaiter.selectable_waiter() defined in compat.py.
Originally, it was:
listener.bind(('', 0))
I changed it to:
listener.bind(('127.0.0.1', 0))
And the firewall denial dialog no longer came up.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
Re: Announcing new committers
Well done! William - Original Message - On Fri, Sep 14, 2012 at 01:13:26PM -0400, Carl Trieloff wrote: I'm Glad to announce that Darryl Pierce and Oleksandr Rudyy where nominated and have accepted committership for the qpid project. Please join me in welcoming them as committers to Qpid. Darryl and Oleksandr, if you have any issues in being able to commit, please let me know. Note that you need to re-checkout using the https URL. Thank you, Carl. :) -- Darryl L. Pierce, Sr. Software Engineer @ Red Hat, Inc. Delivering value year after year. Red Hat ranks #1 in value among software vendors. http://www.redhat.com/promo/vendor/ - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-4291) Renamed the Ruby gemfile to qpid_messaging
[ https://issues.apache.org/jira/browse/QPID-4291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated QPID-4291: - Fix Version/s: (was: 0.18) 0.19 Renamed the Ruby gemfile to qpid_messaging Key: QPID-4291 URL: https://issues.apache.org/jira/browse/QPID-4291 Project: Qpid Issue Type: Improvement Components: Ruby Client Affects Versions: 0.18 Reporter: Darryl L. Pierce Assignee: Darryl L. Pierce Fix For: 0.19 Attachments: 0001-Some-cleanup-on-the-rdoc-generation-and-markups.patch, 0002-Renamed-the-gemfile-to-qpid_messaging.patch Since the name qpid is already claimed on Rubygems.org, we've had to change the name of our gem to qpid_messaging. This patch set includes changes needed in the internals for the Qpid Ruby bindings to use this new naming. Users will need to change: require qpid to: require qpid_messaging to avoid any potential name collisions. Otherwise, no other changes are required to their code. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-4291) Renamed the Ruby gemfile to qpid_messaging
[ https://issues.apache.org/jira/browse/QPID-4291?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13458237#comment-13458237 ] Robbie Gemmell commented on QPID-4291: -- Bumped fix-for to 0.19 since 0.18 already went out before the JIRA was opened. Renamed the Ruby gemfile to qpid_messaging Key: QPID-4291 URL: https://issues.apache.org/jira/browse/QPID-4291 Project: Qpid Issue Type: Improvement Components: Ruby Client Affects Versions: 0.18 Reporter: Darryl L. Pierce Assignee: Darryl L. Pierce Fix For: 0.19 Attachments: 0001-Some-cleanup-on-the-rdoc-generation-and-markups.patch, 0002-Renamed-the-gemfile-to-qpid_messaging.patch Since the name qpid is already claimed on Rubygems.org, we've had to change the name of our gem to qpid_messaging. This patch set includes changes needed in the internals for the Qpid Ruby bindings to use this new naming. Users will need to change: require qpid to: require qpid_messaging to avoid any potential name collisions. Otherwise, no other changes are required to their code. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
Re: Outstanding open JIRAs
There now remains 5 JIRAs open against released versions. Can the following please have their status updated, either by the assignee or just someone who actually knows their status: Ken: https://issues.apache.org/jira/browse/QPID-3690 Ted: https://issues.apache.org/jira/browse/QPID-3653 Mick: https://issues.apache.org/jira/browse/QPID-3398 Kim: https://issues.apache.org/jira/browse/QPID-3619 Cliff: https://issues.apache.org/jira/browse/QPID-4071 On 12 September 2012 22:55, Robbie Gemmell robbie.gemm...@gmail.com wrote: Thanks to those who updated their JIRAs. Given there were still around 30 sitting open against released versions I have just gone through them all myself and either updated the fix-for or resolved them based on any apparent work done after checking the commit logs (which obviously works best when commits reference the JIRA). There are still a bunch for which the status wasnt clear to me, so can the assignees please look at them and update them accordingly: Ken: https://issues.apache.org/jira/browse/QPID-3690 Ted: https://issues.apache.org/jira/browse/QPID-3653 Mick: https://issues.apache.org/jira/browse/QPID-3398 Kim: https://issues.apache.org/jira/browse/QPID-3619 Andrew: https://issues.apache.org/jira/browse/QPID-3618 Rajith: https://issues.apache.org/jira/browse/QPID-3602 https://issues.apache.org/jira/browse/QPID-3612 https://issues.apache.org/jira/browse/QPID-3613 https://issues.apache.org/jira/browse/QPID-3462 Weston: https://issues.apache.org/jira/browse/QPID-3991 Cliff: https://issues.apache.org/jira/browse/QPID-4071 On 2 September 2012 21:10, Robbie Gemmell robbie.gemm...@gmail.comwrote: So, 6 months and a couple of releases later, we now have 45 open JIRAs assigned to released versions. Can everyone please take a look at JIRAs they have in 0.15 and 0.17 and either resolve them or update the fix-for to remove them from the old versions? Thanks, Robbie On 19 February 2012 23:59, Robbie Gemmell robbie.gemm...@gmail.comwrote: Hi everyone, As you may or may not have noticed from the hundreds of emails I have no doubt generated (I kept some of the traffic off the dev list with bulk changes, but you cant fix some things in bulk without losing data), I have been on some JIRA cleanup sprees both recently and in spots over the last several months. This included resolving completed and/or redundant JIRAs as well as moving obviously incomplete ones to different fix-for versions, archiving some of our ancient versions, and removing a few Components that were either duplicates, obviously-defunct, or the contents of which seemed far better served by identification though use of Labels. One of the things I was aiming to do was clear the released versions of outstanding JIRAs so they dont show up on the front pages as being incomplete, as it was a little ridiculous that we still had things open for released versions going back to 2008. I have now got that number down to a grand total of 2 which I'm not too sure whether to resolve or bump forward, so can their respective owners noted below (or anyone else with a clue) please do so: https://issues.apache.org/jira/browse/QPID-3369 (Alan) https://issues.apache.org/jira/browse/QPID-3079 (Ken) I am sure there is still a vast amount of cruft in JIRA that we can tidy up, there are still almost 500 open issues which seems more a bit much. I dont have anywhere near enough knowledge about many of the non-Java components to judge whether a lot of issues can be closed or not (short of them basically saying 'we will never do this' or 'this is done' and having commits..which, surprisingly, several actually did), so it would be good id those who do could take a look. This sort of thing would be *so* much easier to do if we could get things into a managable state and then keep it there with mere minutes of attention now and then. I'm not done looking at the Java stuff, I'm sure there are still duplicates and invalid things that can be closed and I know there are still several open JIRAs for the Java client that have work done on them that it should be possible to close (Rajith, I'm looking at you sitting with the most assigned open issues in the project :P). Robbie
[jira] [Resolved] (QPID-1354) buildCreator recurses directorys looking for patches.
[ https://issues.apache.org/jira/browse/QPID-1354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell resolved QPID-1354. -- Resolution: Won't Fix buildCreator recurses directorys looking for patches. - Key: QPID-1354 URL: https://issues.apache.org/jira/browse/QPID-1354 Project: Qpid Issue Type: Bug Components: Build Tools 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (QPID-1429) buildCreator uses fixed location of binarires.
[ https://issues.apache.org/jira/browse/QPID-1429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell resolved QPID-1429. -- Resolution: Won't Fix buildCreator uses fixed location of binarires. --- Key: QPID-1429 URL: https://issues.apache.org/jira/browse/QPID-1429 Project: Qpid Issue Type: Bug Components: Build Tools 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
