[jira] [Created] (QPID-5338) The Dispatch top-level Python package should be renamed
Darryl L. Pierce created QPID-5338: -- Summary: The Dispatch top-level Python package should be renamed Key: QPID-5338 URL: https://issues.apache.org/jira/browse/QPID-5338 Project: Qpid Issue Type: Improvement Components: Qpid Dispatch Reporter: Darryl L. Pierce Assignee: Darryl L. Pierce Currently the package name is qpid, which conflicts with the public qpid Python package library. A better idea would be to rename it qpiddx. -- This message was sent by Atlassian JIRA (v6.1#6144) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Comment Edited] (QPID-5308) Make C++ test results reports output XML
[ https://issues.apache.org/jira/browse/QPID-5308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13821482#comment-13821482 ] Andrew Stitcher edited comment on QPID-5308 at 11/13/13 4:19 PM: - Thanks Robbie, I didn't realise the python tests already have a way to output JUnit XML (it's not a built in feature of the python testing framework as far as I could tell). So I'm really pleased you pointed me at the java testing scripts which tell me that all I need to do is pass -x filename into the python testing runs. was (Author: astitcher): Thanks Robbie, I didn't realise the python tests already have a way to output JUnit XML (it's not a built in feature of the python testing framework as far as I could tell). So I'm really pleased you pointed me at the java testins scripts which tell me that all I need to do is pass -x filename into the python testing runs. Make C++ test results reports output XML Key: QPID-5308 URL: https://issues.apache.org/jira/browse/QPID-5308 Project: Qpid Issue Type: Improvement Reporter: Andrew Stitcher Assignee: Andrew Stitcher Fix For: 0.25 The Jenkins CI system has good facilities for reporting in a friendly way test results that are prsntd in XML. So it would be nice to allow the C++ tests to output results in XML format. -- This message was sent by Atlassian JIRA (v6.1#6144) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-5308) Make C++ test results reports output XML
[ https://issues.apache.org/jira/browse/QPID-5308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13821482#comment-13821482 ] Andrew Stitcher commented on QPID-5308: --- Thanks Robbie, I didn't realise the python tests already have a way to output JUnit XML (it's not a built in feature of the python testing framework as far as I could tell). So I'm really pleased you pointed me at the java testins scripts which tell me that all I need to do is pass -x filename into the python testing runs. Make C++ test results reports output XML Key: QPID-5308 URL: https://issues.apache.org/jira/browse/QPID-5308 Project: Qpid Issue Type: Improvement Reporter: Andrew Stitcher Assignee: Andrew Stitcher Fix For: 0.25 The Jenkins CI system has good facilities for reporting in a friendly way test results that are prsntd in XML. So it would be nice to allow the C++ tests to output results in XML format. -- This message was sent by Atlassian JIRA (v6.1#6144) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-5338) The Dispatch top-level Python package should be renamed
[ https://issues.apache.org/jira/browse/QPID-5338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13821483#comment-13821483 ] ASF subversion and git services commented on QPID-5338: --- Commit 1541585 from [~mcpierce] in branch 'dispatch/trunk' [ https://svn.apache.org/r1541585 ] QPID-5338: Renamed the top Python package to qpiddx. This fixes the collision between the embedded library's name and the public Qpid Python libraries. The Dispatch top-level Python package should be renamed --- Key: QPID-5338 URL: https://issues.apache.org/jira/browse/QPID-5338 Project: Qpid Issue Type: Improvement Components: Qpid Dispatch Reporter: Darryl L. Pierce Assignee: Darryl L. Pierce Currently the package name is qpid, which conflicts with the public qpid Python package library. A better idea would be to rename it qpiddx. -- This message was sent by Atlassian JIRA (v6.1#6144) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-5338) The Dispatch top-level Python package should be renamed
[ https://issues.apache.org/jira/browse/QPID-5338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13821488#comment-13821488 ] ASF subversion and git services commented on QPID-5338: --- Commit 1541589 from [~mcpierce] in branch 'dispatch/trunk' [ https://svn.apache.org/r1541589 ] QPID-5338: Added ChangeLog entry The Dispatch top-level Python package should be renamed --- Key: QPID-5338 URL: https://issues.apache.org/jira/browse/QPID-5338 Project: Qpid Issue Type: Improvement Components: Qpid Dispatch Reporter: Darryl L. Pierce Assignee: Darryl L. Pierce Currently the package name is qpid, which conflicts with the public qpid Python package library. A better idea would be to rename it qpiddx. -- This message was sent by Atlassian JIRA (v6.1#6144) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-5335) Dispatch Python libraries need to install to a private directory.
[ https://issues.apache.org/jira/browse/QPID-5335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darryl L. Pierce updated QPID-5335: --- Summary: Dispatch Python libraries need to install to a private directory. (was: Dispatch Python libraries need to not install to a private directory.) Dispatch Python libraries need to install to a private directory. - Key: QPID-5335 URL: https://issues.apache.org/jira/browse/QPID-5335 Project: Qpid Issue Type: Improvement Components: Qpid Dispatch Reporter: Darryl L. Pierce Currently the embedded Python libraries are installed to the site-packages directory and are public, which is undesirable. Instead they should install to: /usr/lib/qpid-dispatch The binary should set this directory by default (or have it set as a compile time option) and also provide a way to override it as a command line option. -- This message was sent by Atlassian JIRA (v6.1#6144) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
Re: connection refused error for a Java EE app with RabbitMQ broker, Qpid JMS client
or prefix the values of your 'destination.lookup_name' entries with BURL
(i.e destination.lookupname=BURL.value
To correct myself, that should have been BURL: and then
destination.lookupname=BURL:value
Robbie
On 12 November 2013 22:56, Robbie Gemmell robbie.gemm...@gmail.com wrote:
As Alex has already beaten me to saying, the problem looks to be that the
connection url you are using is rather malformed and is instructing the
Qpid client to [attempt to] connect to your own machine.
You can find documentation of the actual connection url format used by the
client at:
http://qpid.apache.org/releases/qpid-0.24/programming/book/QpidJNDI.html#section-jms-connection-url
If you get that working, you will then likely discover a new issue in that
the destination syntax the client will use based on your properties file is
not actually supported when connecting to an AMQP 0-9-1 broker [such as
RabbitMQ]. The solution to this is either to set the system property
qpid.dest_syntax to BURL (i.e -Dqpid.dest_syntax=BURL) on your client
application, or prefix the values of your 'destination.lookup_name'
entries with BURL (i.e destination.lookupname=BURL.value), and then
ensure that the 'destination.' entry value uses the BindingURL format
outlined at
https://cwiki.apache.org/confluence/display/qpid/BindingURLFormat.
Alternatively, you can instead use the simpler 'queue.' and 'topic.'
entries:
# queue.[jndiName] = [physicalName]
queue.myQueue = myQueue
# topic.[jndiName] = [physicalName]
topic.myTopic= a.b.c
Next, if you are trying a recent Qpid release and a recent RabbitMQ
release together, you will likely then run into
https://issues.apache.org/jira/browse/QPID-5224 and
https://issues.apache.org/jira/browse/QPID-5184, plus potentially
https://issues.apache.org/jira/browse/QPID-5223. That is to say, you'll
iehter need to use older versions of Qpid and RabbitMQ, or will need to use
the current trunk version of the client (which was just branched 30mins ago
to form the basis of the 0.26 release due in a few weeks). You can get a
nightly build archive from:
https://builds.apache.org/view/M-R/view/Qpid/job/Qpid-Java-Artefact-Release/lastSuccessfulBuild/artifact/trunk/qpid/java/client/release/or
alternatively use the ASF snapshots repo:
https://repository.apache.org/content/repositories/snapshots/
Finally, you also almost certainly want to change the user details you
have posted to the mailing list.
Regards,
Robbie
On 11 November 2013 23:35, beon2013 ming.li.e...@gmail.com wrote:
In my Java EE application, I want send and receive a message using a
RabbitMQ
broker and a Qpid JMS client.
The information about RabbitMQ broker is as follow:
Server: turtle.rmq.cloudamqp.com
User: tsikywzh
Password: Z_1x359XUuKfkcK0PoohUVBWlqXtxVh
AMQP URL:
amqp://
tsikywzh:z_1x359xuukfkck0poohuvbwlqxt...@turtle.rmq.cloudamqp.com/tsikywzh
The code for send a message using the Qpid JMS client:
public void sendMessage(){
logger.log(Level.INFO, Sending message {0}, messageText);
Properties properties = new Properties();
properties.load(SenderBean.class.getResourceAsStream(/websimplemessage.properties));
Context context = new InitialContext(properties);
ConnectionFactory connectionFactory = (ConnectionFactory)
context.lookup(qpidConnectionfactory);
Connection connection = connectionFactory.createConnection();
connection.start();
Session session = connection.createSession(false,
Session.AUTO_ACKNOWLEDGE);
Destination destination = (Destination)
context.lookup(topicExchange);
MessageProducer messageProducer =
session.createProducer(destination);
String text = Message from producer: + messageText;
TextMessage message = session.createTextMessage(text);
messageProducer.send(message);
connection.close();
context.close();
}
Which uses this Apache Qpid JNDI Properties File
websimplemessage.properties
:
java.naming.factory.initial =
org.apache.qpid.jndi.PropertiesFileInitialContextFactory
connectionfactory.qpidConnectionfactory =
amqp://
tsikywzh:z_1x359xuukfkck0poohuvbwlqxt...@turtle.rmq.cloudamqp.com/tsikywzh?brokerlist='tcp://localhost:5672
'
destination.topicExchange = amq.topic
Unfortunately, when I run the application, I get connection errors:
SenderBean.sendMessage: Exception: javax.jms.JMSException: Error creating
connection: Connection refused
I am sure RabbitMQ broker is work. Maybe the Qpid JNDI properties File is
not correct.
How can I solve this error? Thanks
--
View this message in context:
http://apache-qpid-developers.2158895.n2.nabble.com/connection-refused-error-for-a-Java-EE-app-with-RabbitMQ-broker-Qpid-JMS-client-tp7590925.html
Sent from the Apache Qpid developers mailing list archive at Nabble.com.
-
To unsubscribe, e-mail:
[jira] [Commented] (QPID-5308) Make C++ test results reports output XML
[ https://issues.apache.org/jira/browse/QPID-5308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13821529#comment-13821529 ] Robbie Gemmell commented on QPID-5308: -- No problem, really the thanks go to Keith since he added that while setting up the Python test runs against the CPP and Java brokers on Jenkins. Make C++ test results reports output XML Key: QPID-5308 URL: https://issues.apache.org/jira/browse/QPID-5308 Project: Qpid Issue Type: Improvement Reporter: Andrew Stitcher Assignee: Andrew Stitcher Fix For: 0.25 The Jenkins CI system has good facilities for reporting in a friendly way test results that are prsntd in XML. So it would be nice to allow the C++ tests to output results in XML format. -- This message was sent by Atlassian JIRA (v6.1#6144) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-5319) Add ability to get list of connections through server management agent
[ https://issues.apache.org/jira/browse/QPID-5319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ernest Allen updated QPID-5319: --- Attachment: dispatch.connectors.diff4 The attached dispatch.connectors.diff4 addresses Ted's points. - Listener connections are now accumulated so incoming connections are now reported (from other routers as well as from qdstat) - Invoking qdstat repeatedly no longer removes outgoing connections Note: Repeatedly invoking qdstat -c shows that incoming (listener) connections are not always being freed. (https://issues.apache.org/jira/browse/QPID-4853) Add ability to get list of connections through server management agent -- Key: QPID-5319 URL: https://issues.apache.org/jira/browse/QPID-5319 Project: Qpid Issue Type: Improvement Components: Qpid Dispatch Affects Versions: Future Reporter: Ernest Allen Assignee: Ted Ross Attachments: dispatch.connectors.diff3, dispatch.connectors.diff4 Add a management agent handler that will return a list of connections. The following info should be returned: state - the state of the connection (Connecting, Opening, Operational, Failed, User) host - the host of the connection's container port - the post of the connection's container container - the name of the remote connection container sasl - the sasl mechanism list of the connection's container role - the role of the connection's container tools/src/py/qdstat should also be updated with a -c command line switch. ./qdstat -c -b localhost:20001 Connections statehost port container sasl-mechanisms role === Operational 0.0.0.0 20002 QDR.B ANONYMOUSinter-router Operational 0.0.0.0 20003 QDR.C ANONYMOUSinter-router Operational 0.0.0.0 20004 QDR.D ANONYMOUSinter-router -- This message was sent by Atlassian JIRA (v6.1#6144) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-5319) Add ability to get list of connections through server management agent
[ https://issues.apache.org/jira/browse/QPID-5319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ernest Allen updated QPID-5319: --- Attachment: (was: dispatch.connectors.diff3) Add ability to get list of connections through server management agent -- Key: QPID-5319 URL: https://issues.apache.org/jira/browse/QPID-5319 Project: Qpid Issue Type: Improvement Components: Qpid Dispatch Affects Versions: Future Reporter: Ernest Allen Assignee: Ted Ross Attachments: dispatch.connectors.diff4 Add a management agent handler that will return a list of connections. The following info should be returned: state - the state of the connection (Connecting, Opening, Operational, Failed, User) host - the host of the connection's container port - the post of the connection's container container - the name of the remote connection container sasl - the sasl mechanism list of the connection's container role - the role of the connection's container tools/src/py/qdstat should also be updated with a -c command line switch. ./qdstat -c -b localhost:20001 Connections statehost port container sasl-mechanisms role === Operational 0.0.0.0 20002 QDR.B ANONYMOUSinter-router Operational 0.0.0.0 20003 QDR.C ANONYMOUSinter-router Operational 0.0.0.0 20004 QDR.D ANONYMOUSinter-router -- This message was sent by Atlassian JIRA (v6.1#6144) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (QPID-5339) Dispatch - Intermittent crashes during scripted six-node tests
Ted Ross created QPID-5339: -- Summary: Dispatch - Intermittent crashes during scripted six-node tests Key: QPID-5339 URL: https://issues.apache.org/jira/browse/QPID-5339 Project: Qpid Issue Type: Bug Components: Qpid Dispatch Reporter: Ted Ross Assignee: Ted Ross Hat Tip: Mick Goulish Mick did some soak testing and discovered that a six-router topology, set up by a script, would occasionally leave core dumps. Analysis revealed that the crash would occur sometimes when two threads simultaneously attempted to allocate the first instance of the same type. There is a thread-safety issue in the initializer for the type-allocator. -- This message was sent by Atlassian JIRA (v6.1#6144) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-5339) Dispatch - Intermittent crashes during scripted six-node tests
[ https://issues.apache.org/jira/browse/QPID-5339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13821754#comment-13821754 ] ASF subversion and git services commented on QPID-5339: --- Commit 1541679 from [~tedross] in branch 'dispatch/trunk' [ https://svn.apache.org/r1541679 ] QPID-5339 - Fixed thread safety issue in the type allocator initialization - Added a memory test-mode to check for under/over-run of allocated space. Dispatch - Intermittent crashes during scripted six-node tests -- Key: QPID-5339 URL: https://issues.apache.org/jira/browse/QPID-5339 Project: Qpid Issue Type: Bug Components: Qpid Dispatch Reporter: Ted Ross Assignee: Ted Ross Hat Tip: Mick Goulish Mick did some soak testing and discovered that a six-router topology, set up by a script, would occasionally leave core dumps. Analysis revealed that the crash would occur sometimes when two threads simultaneously attempted to allocate the first instance of the same type. There is a thread-safety issue in the initializer for the type-allocator. -- This message was sent by Atlassian JIRA (v6.1#6144) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (QPID-5339) Dispatch - Intermittent crashes during scripted six-node tests
[ https://issues.apache.org/jira/browse/QPID-5339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross resolved QPID-5339. Resolution: Fixed Dispatch - Intermittent crashes during scripted six-node tests -- Key: QPID-5339 URL: https://issues.apache.org/jira/browse/QPID-5339 Project: Qpid Issue Type: Bug Components: Qpid Dispatch Reporter: Ted Ross Assignee: Ted Ross Hat Tip: Mick Goulish Mick did some soak testing and discovered that a six-router topology, set up by a script, would occasionally leave core dumps. Analysis revealed that the crash would occur sometimes when two threads simultaneously attempted to allocate the first instance of the same type. There is a thread-safety issue in the initializer for the type-allocator. -- This message was sent by Atlassian JIRA (v6.1#6144) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (QPID-5340) Consolidate qpid benchmark tests
Irina Boverman created QPID-5340: Summary: Consolidate qpid benchmark tests Key: QPID-5340 URL: https://issues.apache.org/jira/browse/QPID-5340 Project: Qpid Issue Type: Test Components: C++ Client, Java Performance Tests, Python Tools Affects Versions: 0.24 Environment: Linux, RHEL 6 Reporter: Irina Boverman Priority: Minor Existing tests (qpid/cpp/src/tests/qpid-cpp-benchmark and qpid/java/tools/bin/qpid-jms-benchmark) will be replaced by qpid/python/qpid-benchmark (using qpid-cpp-benchmark as a starting point). Options --qpid-send and --qpid-receive will default to qpid-send and qpid-receive and interpreted as path+binary. -- This message was sent by Atlassian JIRA (v6.1#6144) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-5340) Consolidate qpid benchmark tests
[ https://issues.apache.org/jira/browse/QPID-5340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13821765#comment-13821765 ] Irina Boverman commented on QPID-5340: -- First step is replace qpid-cpp-benchmark by qpid-benchmark and place it in python directory. Attached is a source for qpid-benchmark. Consolidate qpid benchmark tests Key: QPID-5340 URL: https://issues.apache.org/jira/browse/QPID-5340 Project: Qpid Issue Type: Test Components: C++ Client, Java Performance Tests, Python Tools Affects Versions: 0.24 Environment: Linux, RHEL 6 Reporter: Irina Boverman Priority: Minor Existing tests (qpid/cpp/src/tests/qpid-cpp-benchmark and qpid/java/tools/bin/qpid-jms-benchmark) will be replaced by qpid/python/qpid-benchmark (using qpid-cpp-benchmark as a starting point). Options --qpid-send and --qpid-receive will default to qpid-send and qpid-receive and interpreted as path+binary. -- This message was sent by Atlassian JIRA (v6.1#6144) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-5340) Consolidate qpid benchmark tests
[ https://issues.apache.org/jira/browse/QPID-5340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Irina Boverman updated QPID-5340: - Attachment: qpid-benchmark Test results comparing qpid-cpp-benchmark and qpid-benchmark using defaults: # ./qpid/cpp/src/tests/qpid-cpp-benchmark send-tp recv-tp l-min l-max l-avg total-tp 2600221822.48 8069.57 4729.28 2215 # ./qpid/python/qpid-benchmark send-tp recv-tp l-min l-max l-avg total-tp 2720230123.23 7711.96 4520.56 2297 Consolidate qpid benchmark tests Key: QPID-5340 URL: https://issues.apache.org/jira/browse/QPID-5340 Project: Qpid Issue Type: Test Components: C++ Client, Java Performance Tests, Python Tools Affects Versions: 0.24 Environment: Linux, RHEL 6 Reporter: Irina Boverman Priority: Minor Attachments: qpid-benchmark Existing tests (qpid/cpp/src/tests/qpid-cpp-benchmark and qpid/java/tools/bin/qpid-jms-benchmark) will be replaced by qpid/python/qpid-benchmark (using qpid-cpp-benchmark as a starting point). Options --qpid-send and --qpid-receive will default to qpid-send and qpid-receive and interpreted as path+binary. -- This message was sent by Atlassian JIRA (v6.1#6144) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-5319) Add ability to get list of connections through server management agent
[ https://issues.apache.org/jira/browse/QPID-5319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13821781#comment-13821781 ] ASF subversion and git services commented on QPID-5319: --- Commit 1541689 from [~tedross] in branch 'dispatch/trunk' [ https://svn.apache.org/r1541689 ] QPID-5319 - Added management access for connections. Applied patch from Ernie Allen Add ability to get list of connections through server management agent -- Key: QPID-5319 URL: https://issues.apache.org/jira/browse/QPID-5319 Project: Qpid Issue Type: Improvement Components: Qpid Dispatch Affects Versions: Future Reporter: Ernest Allen Assignee: Ted Ross Attachments: dispatch.connectors.diff4 Add a management agent handler that will return a list of connections. The following info should be returned: state - the state of the connection (Connecting, Opening, Operational, Failed, User) host - the host of the connection's container port - the post of the connection's container container - the name of the remote connection container sasl - the sasl mechanism list of the connection's container role - the role of the connection's container tools/src/py/qdstat should also be updated with a -c command line switch. ./qdstat -c -b localhost:20001 Connections statehost port container sasl-mechanisms role === Operational 0.0.0.0 20002 QDR.B ANONYMOUSinter-router Operational 0.0.0.0 20003 QDR.C ANONYMOUSinter-router Operational 0.0.0.0 20004 QDR.D ANONYMOUSinter-router -- This message was sent by Atlassian JIRA (v6.1#6144) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (QPID-5319) Add ability to get list of connections through server management agent
[ https://issues.apache.org/jira/browse/QPID-5319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross resolved QPID-5319. Resolution: Fixed Add ability to get list of connections through server management agent -- Key: QPID-5319 URL: https://issues.apache.org/jira/browse/QPID-5319 Project: Qpid Issue Type: Improvement Components: Qpid Dispatch Affects Versions: Future Reporter: Ernest Allen Assignee: Ted Ross Attachments: dispatch.connectors.diff4 Add a management agent handler that will return a list of connections. The following info should be returned: state - the state of the connection (Connecting, Opening, Operational, Failed, User) host - the host of the connection's container port - the post of the connection's container container - the name of the remote connection container sasl - the sasl mechanism list of the connection's container role - the role of the connection's container tools/src/py/qdstat should also be updated with a -c command line switch. ./qdstat -c -b localhost:20001 Connections statehost port container sasl-mechanisms role === Operational 0.0.0.0 20002 QDR.B ANONYMOUSinter-router Operational 0.0.0.0 20003 QDR.C ANONYMOUSinter-router Operational 0.0.0.0 20004 QDR.D ANONYMOUSinter-router -- This message was sent by Atlassian JIRA (v6.1#6144) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Assigned] (QPID-5325) [Java Broker] Add ability to save web management console open tabs in user preferences
[ https://issues.apache.org/jira/browse/QPID-5325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy reassigned QPID-5325: Assignee: Keith Wall (was: Alex Rudyy) Keith, I changed tooltip text as you had suggested. [Java Broker] Add ability to save web management console open tabs in user preferences -- Key: QPID-5325 URL: https://issues.apache.org/jira/browse/QPID-5325 Project: Qpid Issue Type: Improvement Components: Java Broker Reporter: Alex Rudyy Assignee: Keith Wall Fix For: 0.25 Add ability to save web management console open tabs in user preferences -- This message was sent by Atlassian JIRA (v6.1#6144) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-5330) Queue flow limit tests try to invoke a missing qpid-python-test
[ https://issues.apache.org/jira/browse/QPID-5330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13822011#comment-13822011 ] ASF subversion and git services commented on QPID-5330: --- Commit 1541765 from [~astitcher] in branch 'qpid/trunk' [ https://svn.apache.org/r1541765 ] QPID-5330: Typo in original checkin Queue flow limit tests try to invoke a missing qpid-python-test --- Key: QPID-5330 URL: https://issues.apache.org/jira/browse/QPID-5330 Project: Qpid Issue Type: Bug Components: C++ Broker Affects Versions: 0.25 Reporter: Justin Ross Assignee: Andrew Stitcher Fix For: 0.25 This is from testing a release tarball. I believe this test should avoid running if it can't find qpid-python-test. 25/54 Testing: queue_flow_limit_tests 25/54 Test: queue_flow_limit_tests Command: /tmp/tmp.qNIAEwMgJv/qpid-cpp-0.26/src/tests/run_test --build-dir=/tmp/tmp.qNIAEwMgJv/qpid-cpp-0.26/build --start-broker --broker-options=--default-flow-stop-threshold=80 --default-flow-resume-thre\ shold=70 -t --log-to-stderr=no --log-to-stdout=no /tmp/tmp.qNIAEwMgJv/qpid-cpp-0.26/src/tests/run_queue_flow_limit_tests Directory: /tmp/tmp.qNIAEwMgJv/qpid-cpp-0.26/build/src/tests queue_flow_limit_tests start time: Nov 09 19:51 EST Output: -- /tmp/tmp.qNIAEwMgJv/qpid-cpp-0.26/src/tests/run_queue_flow_limit_tests: line 24: /tmp/tmp.qNIAEwMgJv/qpid-cpp-0.26/build/src/tests/python/commands/qpid-python-test: No such file or directory end of output Test time = 3.96 sec -- Test Failed. queue_flow_limit_tests end time: Nov 09 19:51 EST queue_flow_limit_tests time elapsed: 00:00:03 -- -- This message was sent by Atlassian JIRA (v6.1#6144) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-5336) bash is not always found at /bin/bash
[ https://issues.apache.org/jira/browse/QPID-5336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13822009#comment-13822009 ] ASF subversion and git services commented on QPID-5336: --- Commit 1541763 from [~astitcher] in branch 'qpid/trunk' [ https://svn.apache.org/r1541763 ] QPID-5336: Don't hardcode location of bash in shell scripts As bash isn't specified by POSIX its location is variable. Specifically under BSDs it isn't found in /bin/bash. bash is not always found at /bin/bash - Key: QPID-5336 URL: https://issues.apache.org/jira/browse/QPID-5336 Project: Qpid Issue Type: Bug Affects Versions: 0.25 Environment: Freebsd Reporter: Andrew Stitcher Assignee: Andrew Stitcher The qpid test scripts will not run under FreeBSD because they have a hardcoded notion that bash is found at /bin/bash. However under FreeBSD it is actually found in /usr/local/bin/bash. We need to change the line which say #!/bin/bash to #!/usr/bin/env bash. -- This message was sent by Atlassian JIRA (v6.1#6144) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-5306) Improve cmake testing structure
[ https://issues.apache.org/jira/browse/QPID-5306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13822010#comment-13822010 ] ASF subversion and git services commented on QPID-5306: --- Commit 1541764 from [~astitcher] in branch 'qpid/trunk' [ https://svn.apache.org/r1541764 ] QPID-5306: Improve test wrapper to avoid using getopt for long options Using getopt with long options is a gnu extension and so best avoided for portability reasons. Improve cmake testing structure --- Key: QPID-5306 URL: https://issues.apache.org/jira/browse/QPID-5306 Project: Qpid Issue Type: Improvement Reporter: Andrew Stitcher Assignee: Andrew Stitcher Fix For: 0.25 Improve run_test test wrapper script so that it can run tests in various different ways. This is necessary to allow tests to run in a different directory from the build directory that corresponds to the source cmake file. It is also useful to allow consolidation of the various test scripts: So far some of the starting and stopping broker work in tests has been centralised into this script too. -- This message was sent by Atlassian JIRA (v6.1#6144) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
