Re: certificate authentication

[Eric Li]

Thanks.  I just gave a trial with the following command on ubuntu.  

sudo ./src/qpidd --auth no --load-module /usr/lib/libssl3.so --ssl-cert-db 
/home/amqp/server_db --ssl-cert-password-file /home/amqp/ok.pwd --ssl-cert-name 
localhost.domain
2010-04-20 05:44:12 critical Unexpected error: Error in command line options: 
unknown option ssl-cert-db
Use --help to see valid options

I built the qpid from the source distribution and do not see the ssl.so module 
under the .src/.lib/ folder.  Do I miss anything here?

Thanks,
li




From: Gordon Sim 
To: dev@qpid.apache.org
Sent: Fri, April 23, 2010 4:30:24 AM
Subject: Re: certificate authentication

On 04/23/2010 01:14 AM, Steve Huston wrote:
>> Can you tell me where I can specify the crl location that
>> contains the list of revoked certificates info?
> 
> I believe that's part of the certificate database you're already passing
> to qpidd, but I'm not 100% clear on that.

For the nss based ssl implementation (on linux) I believe you use the crlutil 
tool: http://www.mozilla.org/projects/security/pki/nss/tools/crlutil.html

-
Apache Qpid - AMQP Messaging Implementation
Project:  http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org


  

RE: [Java] PluginTest failure.

[Robbie Gemmell]

Looks like a required patch wasn't put up with the rest, I've applied a fix
so it should be ok now.

Robbie

> -Original Message-
> From: Rajith Attapattu [mailto:rajit...@gmail.com]
> Sent: 23 April 2010 22:47
> To: dev@qpid.apache.org
> Cc: Martin Ritchie
> Subject: [Java] PluginTest failure.
> 
> The PluginTest is failing at the moment with the following errors.
> Since it does not extend QpidTestCase it cannot be excluded.
> Therefore I will temporarily comment on the test case.
> 
> Can somebody who knows the code have a look at it and fix this test
> case?
> 
> 
> Regards,
> 
> Rajith Attapattu
> Red Hat
> http://rajith.2rlabs.com/
> 
>   Testsuite: org.apache.qpid.server.plugins.PluginTest
>   Tests run: 2, Failures: 1, Errors: 0, Time elapsed: 0.151 sec
>   - Standard Output ---
>   main 2010-04-23 13:36:57,215 INFO
> [qpid.server.registry.ApplicationRegistry] Creating
> DEFAULT_APPLICATION_REGISTRY:
> org.apache.qpid.server.util.NullApplicationRegistry : Instance:1
>   main 2010-04-23 13:36:57,215 INFO
> [qpid.server.registry.ApplicationRegistry] Initialising Application
> Registry:1
>   main 2010-04-23 13:36:57,217 INFO
> [qpid.server.registry.ApplicationRegistry] Initialising
> NullApplicationRegistry
>   main 2010-04-23 13:36:57,217 INFO
> [security.auth.manager.PrincipalDatabaseAuthenticationManager]
> Initialising Default PrincipleDatabase authentication manager.
>   main 2010-04-23 13:36:57,217 WARN
> [security.auth.sasl.UsernamePasswordInitialiser] we need a server that
> will correctly convert the incomming plain text for comparison to
> file.
>   main 2010-04-23 13:36:57,217 INFO
> [security.auth.manager.PrincipalDatabaseAuthenticationManager]
> Initialised PLAIN SASL provider successfully
>   main 2010-04-23 13:36:57,217 INFO
> [security.auth.manager.PrincipalDatabaseAuthenticationManager]
> Initialised CRAM-MD5 SASL provider successfully
>   main 2010-04-23 13:36:57,217 INFO
> [security.auth.manager.PrincipalDatabaseAuthenticationManager]
> Additional SASL providers successfully registered.
>   main 2010-04-23 13:36:57,217 INFO
> [qpid.server.management.NoopManagedObjectRegistry] Management is
> disabled
>   main 2010-04-23 13:36:57,218 INFO [qpid.message] MESSAGE [Test
> Actor] VHT-1001 : Created : test
>   main 2010-04-23 13:36:57,218 INFO [qpid.message] MESSAGE [Test
> Actor] EXH-1001 : Create : Durable Type: headers Name: amq.match
>   main 2010-04-23 13:36:57,219 INFO [qpid.message] MESSAGE [Test
> Actor] EXH-1001 : Create : Durable Type: topic Name: amq.topic
>   main 2010-04-23 13:36:57,219 INFO [qpid.message] MESSAGE [Test
> Actor] EXH-1001 : Create : Durable Type: direct Name: amq.direct
>   main 2010-04-23 13:36:57,219 INFO [qpid.message] MESSAGE [Test
> Actor] EXH-1001 : Create : Durable Type: fanout Name: amq.fanout
>   main 2010-04-23 13:36:57,220 INFO [qpid.message] MESSAGE [Test
> Actor] EXH-1001 : Create : Durable Type: direct Name: <>
>   main 2010-04-23 13:36:57,220 DEBUG
> [qpid.server.virtualhost.VirtualHostImpl] Loading configuration for
> virtualhost: test
>   main 2010-04-23 13:36:57,220 INFO [qpid.message] MESSAGE [Test
> Actor] [vh(/test)/ms(MemoryMessageStore)] CFG-1001 : Created :
> org.apache.qpid.server.store.MemoryMessageStore
>   main 2010-04-23 13:36:57,220 INFO
> [qpid.server.store.MemoryMessageStore] Using capacity 5 for hash
> tables
>   main 2010-04-23 13:36:57,220 INFO [qpid.message] MESSAGE [Test
> Actor] [vh(/test)/ms(MemoryMessageStore)] MST-1001 : Created :
> org.apache.qpid.server.store.MemoryMessageStore
>   main 2010-04-23 13:36:57,220 INFO
> [security.auth.manager.PrincipalDatabaseAuthenticationManager]
> Initialising 'test' PrincipleDatabase authentication manager.
>   main 2010-04-23 13:36:57,221 INFO
> [qpid.server.registry.ApplicationRegistry] Initialised Application
> Registry:1
>   ERROR: Error starting
> file:/var/lib/ptolemy/sources/qpid/java/build/lib/plugins/qpid-broker-
> plugins-extras-0.7.jar
> (org.osgi.framework.BundleException: Unresolved package in bundle 1:
> package; (package=org.apache.qpid.protocol))
>   -  ---
>   - Standard Error -
>   org.osgi.framework.BundleException: Unresolved package in bundle 1:
> package; (package=org.apache.qpid.protocol)
> at
> org.apache.felix.framework.Felix._resolveBundle(Felix.java:1649)
> at
> org.apache.felix.framework.Felix._startBundle(Felix.java:1516)
> at
> org.apache.felix.framework.Felix.startBundle(Felix.java:1469)
> at
> org.apache.felix.framework.Felix.setFrameworkStartLevel(Felix.java:1064
> )
> at
> org.apache.felix.framework.StartLevelImpl.run(StartLevelImpl.java:258)
> at java.lang.Thread.run(Thread.java:619)
>   -  ---
> 
> -
> Apache Qpid - AMQP Messaging Implementation
> Project:  http://qpid.apache.org
> Use/Int

[jira] Commented: (QPID-2534) Add org.apache.qpid.protocol and org.apache.junit.extensions.util to the packages exported by the PluginManager

[Robbie Gemmell (JIRA)]

[ 
https://issues.apache.org/jira/browse/QPID-2534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12860448#action_12860448
 ] 

Robbie Gemmell commented on QPID-2534:
--

The required changes have been made.

> Add org.apache.qpid.protocol and org.apache.junit.extensions.util  to the 
> packages exported by the PluginManager 
> -
>
> Key: QPID-2534
> URL: https://issues.apache.org/jira/browse/QPID-2534
> Project: Qpid
>  Issue Type: Improvement
>  Components: Java Broker
>Affects Versions: 0.7
>Reporter: Sorin Suciu
>Assignee: Robbie Gemmell
>Priority: Minor
> Fix For: 0.7
>
>
> org.apache.qpid.protocol and org.apache.junit.extensions.util  are needed by 
> the "extras" plugin so it should be exported by the PluginManager. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
Apache Qpid - AMQP Messaging Implementation
Project:  http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org

[jira] Updated: (QPID-2534) Add org.apache.qpid.protocol and org.apache.junit.extensions.util to the packages exported by the PluginManager

[Robbie Gemmell (JIRA)]

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

Robbie Gemmell updated QPID-2534:
-

Status: Ready To Review  (was: In Progress)

> Add org.apache.qpid.protocol and org.apache.junit.extensions.util  to the 
> packages exported by the PluginManager 
> -
>
> Key: QPID-2534
> URL: https://issues.apache.org/jira/browse/QPID-2534
> Project: Qpid
>  Issue Type: Improvement
>  Components: Java Broker
>Affects Versions: 0.7
>Reporter: Sorin Suciu
>Assignee: Robbie Gemmell
>Priority: Minor
> Fix For: 0.7
>
>
> org.apache.qpid.protocol and org.apache.junit.extensions.util  are needed by 
> the "extras" plugin so it should be exported by the PluginManager. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
Apache Qpid - AMQP Messaging Implementation
Project:  http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org

[jira] Commented: (QPID-2531) Improve the qpid broker build system to automatically build OSGI modules on broker-plugins directory

[Robbie Gemmell (JIRA)]

[ 
https://issues.apache.org/jira/browse/QPID-2531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12860447#action_12860447
 ] 

Robbie Gemmell commented on QPID-2531:
--

The java/broker-plugins/src/main/java directory is still required until the 
build system is updated to fully accomodate the recent changes made to the 
broker-plugins module. Once that is done it the src/ dir can be removed.

> Improve the qpid broker build system to automatically build OSGI modules on 
> broker-plugins directory
> 
>
> Key: QPID-2531
> URL: https://issues.apache.org/jira/browse/QPID-2531
> Project: Qpid
>  Issue Type: Improvement
>Reporter: Sorin Suciu
>Assignee: Martin Ritchie
> Attachments: qpid-2531.patch
>
>
> The qpid broker ant build system could be improved to automatically build the 
> OSGI modules in the broker-plugins directory given we might have multiple 
> modules. For this, we could modify the current build.xml file from 
> broker-plugins to delegate the tasks to each individual module via a subant 
> task. Each module would have its own build.xml file (which would be pretty 
> much generic). 
> So the task of adding a new OSGI module would involve: 
> - creating a new directory (eg myplugin) having a generic build.xml and the 
> code in src subdir
> - adding the new directory to the subant task so it will be build
> - updating the build.deps file

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
Apache Qpid - AMQP Messaging Implementation
Project:  http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org

[jira] Assigned: (QPID-2534) Add org.apache.qpid.protocol and org.apache.junit.extensions.util to the packages exported by the PluginManager

[Robbie Gemmell (JIRA)]

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

Robbie Gemmell reassigned QPID-2534:


Assignee: Robbie Gemmell

> Add org.apache.qpid.protocol and org.apache.junit.extensions.util  to the 
> packages exported by the PluginManager 
> -
>
> Key: QPID-2534
> URL: https://issues.apache.org/jira/browse/QPID-2534
> Project: Qpid
>  Issue Type: Improvement
>  Components: Java Broker
>Affects Versions: 0.7
>Reporter: Sorin Suciu
>Assignee: Robbie Gemmell
>Priority: Minor
> Fix For: 0.7
>
>
> org.apache.qpid.protocol and org.apache.junit.extensions.util  are needed by 
> the "extras" plugin so it should be exported by the PluginManager. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
Apache Qpid - AMQP Messaging Implementation
Project:  http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org

[Java] PluginTest failure.

[Rajith Attapattu]

The PluginTest is failing at the moment with the following errors.
Since it does not extend QpidTestCase it cannot be excluded.
Therefore I will temporarily comment on the test case.

Can somebody who knows the code have a look at it and fix this test case?


Regards,

Rajith Attapattu
Red Hat
http://rajith.2rlabs.com/

  Testsuite: org.apache.qpid.server.plugins.PluginTest
  Tests run: 2, Failures: 1, Errors: 0, Time elapsed: 0.151 sec
  - Standard Output ---
  main 2010-04-23 13:36:57,215 INFO
[qpid.server.registry.ApplicationRegistry] Creating
DEFAULT_APPLICATION_REGISTRY:
org.apache.qpid.server.util.NullApplicationRegistry : Instance:1
  main 2010-04-23 13:36:57,215 INFO
[qpid.server.registry.ApplicationRegistry] Initialising Application
Registry:1
  main 2010-04-23 13:36:57,217 INFO
[qpid.server.registry.ApplicationRegistry] Initialising
NullApplicationRegistry
  main 2010-04-23 13:36:57,217 INFO
[security.auth.manager.PrincipalDatabaseAuthenticationManager]
Initialising Default PrincipleDatabase authentication manager.
  main 2010-04-23 13:36:57,217 WARN
[security.auth.sasl.UsernamePasswordInitialiser] we need a server that
will correctly convert the incomming plain text for comparison to
file.
  main 2010-04-23 13:36:57,217 INFO
[security.auth.manager.PrincipalDatabaseAuthenticationManager]
Initialised PLAIN SASL provider successfully
  main 2010-04-23 13:36:57,217 INFO
[security.auth.manager.PrincipalDatabaseAuthenticationManager]
Initialised CRAM-MD5 SASL provider successfully
  main 2010-04-23 13:36:57,217 INFO
[security.auth.manager.PrincipalDatabaseAuthenticationManager]
Additional SASL providers successfully registered.
  main 2010-04-23 13:36:57,217 INFO
[qpid.server.management.NoopManagedObjectRegistry] Management is
disabled
  main 2010-04-23 13:36:57,218 INFO [qpid.message] MESSAGE [Test
Actor] VHT-1001 : Created : test
  main 2010-04-23 13:36:57,218 INFO [qpid.message] MESSAGE [Test
Actor] EXH-1001 : Create : Durable Type: headers Name: amq.match
  main 2010-04-23 13:36:57,219 INFO [qpid.message] MESSAGE [Test
Actor] EXH-1001 : Create : Durable Type: topic Name: amq.topic
  main 2010-04-23 13:36:57,219 INFO [qpid.message] MESSAGE [Test
Actor] EXH-1001 : Create : Durable Type: direct Name: amq.direct
  main 2010-04-23 13:36:57,219 INFO [qpid.message] MESSAGE [Test
Actor] EXH-1001 : Create : Durable Type: fanout Name: amq.fanout
  main 2010-04-23 13:36:57,220 INFO [qpid.message] MESSAGE [Test
Actor] EXH-1001 : Create : Durable Type: direct Name: <>
  main 2010-04-23 13:36:57,220 DEBUG
[qpid.server.virtualhost.VirtualHostImpl] Loading configuration for
virtualhost: test
  main 2010-04-23 13:36:57,220 INFO [qpid.message] MESSAGE [Test
Actor] [vh(/test)/ms(MemoryMessageStore)] CFG-1001 : Created :
org.apache.qpid.server.store.MemoryMessageStore
  main 2010-04-23 13:36:57,220 INFO
[qpid.server.store.MemoryMessageStore] Using capacity 5 for hash
tables
  main 2010-04-23 13:36:57,220 INFO [qpid.message] MESSAGE [Test
Actor] [vh(/test)/ms(MemoryMessageStore)] MST-1001 : Created :
org.apache.qpid.server.store.MemoryMessageStore
  main 2010-04-23 13:36:57,220 INFO
[security.auth.manager.PrincipalDatabaseAuthenticationManager]
Initialising 'test' PrincipleDatabase authentication manager.
  main 2010-04-23 13:36:57,221 INFO
[qpid.server.registry.ApplicationRegistry] Initialised Application
Registry:1
  ERROR: Error starting
file:/var/lib/ptolemy/sources/qpid/java/build/lib/plugins/qpid-broker-plugins-extras-0.7.jar
(org.osgi.framework.BundleException: Unresolved package in bundle 1:
package; (package=org.apache.qpid.protocol))
  -  ---
  - Standard Error -
  org.osgi.framework.BundleException: Unresolved package in bundle 1:
package; (package=org.apache.qpid.protocol)
at org.apache.felix.framework.Felix._resolveBundle(Felix.java:1649)
at org.apache.felix.framework.Felix._startBundle(Felix.java:1516)
at org.apache.felix.framework.Felix.startBundle(Felix.java:1469)
at 
org.apache.felix.framework.Felix.setFrameworkStartLevel(Felix.java:1064)
at 
org.apache.felix.framework.StartLevelImpl.run(StartLevelImpl.java:258)
at java.lang.Thread.run(Thread.java:619)
  -  ---

-
Apache Qpid - AMQP Messaging Implementation
Project:  http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org

[jira] Commented: (QPID-2531) Improve the qpid broker build system to automatically build OSGI modules on broker-plugins directory

[Emmanuel Bourg (JIRA)]

[ 
https://issues.apache.org/jira/browse/QPID-2531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12860381#action_12860381
 ] 

Emmanuel Bourg commented on QPID-2531:
--

The directory java/broker-plugins/src is empty after this change, I could be 
removed.

> Improve the qpid broker build system to automatically build OSGI modules on 
> broker-plugins directory
> 
>
> Key: QPID-2531
> URL: https://issues.apache.org/jira/browse/QPID-2531
> Project: Qpid
>  Issue Type: Improvement
>Reporter: Sorin Suciu
>Assignee: Martin Ritchie
> Attachments: qpid-2531.patch
>
>
> The qpid broker ant build system could be improved to automatically build the 
> OSGI modules in the broker-plugins directory given we might have multiple 
> modules. For this, we could modify the current build.xml file from 
> broker-plugins to delegate the tasks to each individual module via a subant 
> task. Each module would have its own build.xml file (which would be pretty 
> much generic). 
> So the task of adding a new OSGI module would involve: 
> - creating a new directory (eg myplugin) having a generic build.xml and the 
> code in src subdir
> - adding the new directory to the subant task so it will be build
> - updating the build.deps file

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
Apache Qpid - AMQP Messaging Implementation
Project:  http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org

[jira] Updated: (QPID-2543) Change uint to standard type

[Bruno Matos (JIRA)]

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

Bruno Matos updated QPID-2543:
--

Attachment: (was: CPP_uint_to_unsigned_int.patch)

> Change uint to standard type
> 
>
> Key: QPID-2543
> URL: https://issues.apache.org/jira/browse/QPID-2543
> Project: Qpid
>  Issue Type: Improvement
>  Components: C++ Client
>Affects Versions: 0.7
>Reporter: Bruno Matos
> Fix For: 0.6
>
> Attachments: CPP_uint_to_unsigned_int.patch
>
>   Original Estimate: 0.25h
>  Remaining Estimate: 0.25h
>
> I can't find uint as a standard type and it is breaking Mac OS X client 
> compilation.
> The references I found:
> broker/Broker.h:109:uint queueLimit;
> broker/Link.cpp:338:uint Link::nextChannel()
> broker/Link.h:71:uint channelCounter;
> broker/Link.h:111:uint nextChannel();
> broker/SaslAuthenticator.cpp:432:uint ssf = *(reinterpret_cast unsigned*>(value));
> client/MessageReplayTracker.cpp:27:MessageReplayTracker::MessageReplayTracker(uint
>  f) : flushInterval(f), count(0) {}
> client/MessageReplayTracker.cpp:51:void 
> MessageReplayTracker::setFlushInterval(uint f)
> client/MessageReplayTracker.cpp:56:uint 
> MessageReplayTracker::getFlushInterval()
> client/SaslFactory.cpp:331:uint ssf = *(reinterpret_cast unsigned*>(value));
> framing/SendContent.cpp:24:qpid::framing::SendContent::SendContent(FrameHandler&
>  h, uint16_t mfs, uint efc) : handler(h), 
> framing/SendContent.h:42:uint expectedFrameCount;
> framing/SendContent.h:43:uint frameCount;
> framing/SendContent.h:48:QPID_COMMON_EXTERN SendContent(FrameHandler& 
> _handler, uint16_t _maxFrameSize, uint frameCount);
> sys/Semaphore.h:30:Semaphore(uint c = 1) : count(c) {}
> sys/Semaphore.h:54:void release(uint n)
> sys/Semaphore.h:74:uint count;

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
Apache Qpid - AMQP Messaging Implementation
Project:  http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org

[jira] Updated: (QPID-2543) Change uint to standard type

[Bruno Matos (JIRA)]

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

Bruno Matos updated QPID-2543:
--

Attachment: CPP_uint_to_unsigned_int.patch

Indentation problem solved

> Change uint to standard type
> 
>
> Key: QPID-2543
> URL: https://issues.apache.org/jira/browse/QPID-2543
> Project: Qpid
>  Issue Type: Improvement
>  Components: C++ Client
>Affects Versions: 0.7
>Reporter: Bruno Matos
> Fix For: 0.6
>
> Attachments: CPP_uint_to_unsigned_int.patch
>
>   Original Estimate: 0.25h
>  Remaining Estimate: 0.25h
>
> I can't find uint as a standard type and it is breaking Mac OS X client 
> compilation.
> The references I found:
> broker/Broker.h:109:uint queueLimit;
> broker/Link.cpp:338:uint Link::nextChannel()
> broker/Link.h:71:uint channelCounter;
> broker/Link.h:111:uint nextChannel();
> broker/SaslAuthenticator.cpp:432:uint ssf = *(reinterpret_cast unsigned*>(value));
> client/MessageReplayTracker.cpp:27:MessageReplayTracker::MessageReplayTracker(uint
>  f) : flushInterval(f), count(0) {}
> client/MessageReplayTracker.cpp:51:void 
> MessageReplayTracker::setFlushInterval(uint f)
> client/MessageReplayTracker.cpp:56:uint 
> MessageReplayTracker::getFlushInterval()
> client/SaslFactory.cpp:331:uint ssf = *(reinterpret_cast unsigned*>(value));
> framing/SendContent.cpp:24:qpid::framing::SendContent::SendContent(FrameHandler&
>  h, uint16_t mfs, uint efc) : handler(h), 
> framing/SendContent.h:42:uint expectedFrameCount;
> framing/SendContent.h:43:uint frameCount;
> framing/SendContent.h:48:QPID_COMMON_EXTERN SendContent(FrameHandler& 
> _handler, uint16_t _maxFrameSize, uint frameCount);
> sys/Semaphore.h:30:Semaphore(uint c = 1) : count(c) {}
> sys/Semaphore.h:54:void release(uint n)
> sys/Semaphore.h:74:uint count;

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
Apache Qpid - AMQP Messaging Implementation
Project:  http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org

[jira] Updated: (QPID-2237) UUID are not decoded properly by the .Net 0-10 api

[Bruno Matos (JIRA)]

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

Bruno Matos updated QPID-2237:
--

Attachment: CPP_uint_to_unsigned_int.patch

Indentation problem solved

> UUID are not decoded properly by the .Net 0-10 api
> --
>
> Key: QPID-2237
> URL: https://issues.apache.org/jira/browse/QPID-2237
> Project: Qpid
>  Issue Type: Improvement
>  Components: Dot Net Client
>Affects Versions: 0.5
>Reporter: Julien Lavigne du Cadet
> Fix For: 0.6
>
> Attachments: UUID decoding.patch
>
>
> See patch below

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
Apache Qpid - AMQP Messaging Implementation
Project:  http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org

[jira] Updated: (QPID-2237) UUID are not decoded properly by the .Net 0-10 api

[Bruno Matos (JIRA)]

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

Bruno Matos updated QPID-2237:
--

Attachment: (was: CPP_uint_to_unsigned_int.patch)

> UUID are not decoded properly by the .Net 0-10 api
> --
>
> Key: QPID-2237
> URL: https://issues.apache.org/jira/browse/QPID-2237
> Project: Qpid
>  Issue Type: Improvement
>  Components: Dot Net Client
>Affects Versions: 0.5
>Reporter: Julien Lavigne du Cadet
> Fix For: 0.6
>
> Attachments: UUID decoding.patch
>
>
> See patch below

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
Apache Qpid - AMQP Messaging Implementation
Project:  http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org

[jira] Updated: (QPID-2543) Change uint to standard type

[Bruno Matos (JIRA)]

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

Bruno Matos updated QPID-2543:
--

Attachment: CPP_uint_to_unsigned_int.patch

The right one.

> Change uint to standard type
> 
>
> Key: QPID-2543
> URL: https://issues.apache.org/jira/browse/QPID-2543
> Project: Qpid
>  Issue Type: Improvement
>  Components: C++ Client
>Affects Versions: 0.7
>Reporter: Bruno Matos
> Fix For: 0.6
>
> Attachments: CPP_uint_to_unsigned_int.patch
>
>   Original Estimate: 0.25h
>  Remaining Estimate: 0.25h
>
> I can't find uint as a standard type and it is breaking Mac OS X client 
> compilation.
> The references I found:
> broker/Broker.h:109:uint queueLimit;
> broker/Link.cpp:338:uint Link::nextChannel()
> broker/Link.h:71:uint channelCounter;
> broker/Link.h:111:uint nextChannel();
> broker/SaslAuthenticator.cpp:432:uint ssf = *(reinterpret_cast unsigned*>(value));
> client/MessageReplayTracker.cpp:27:MessageReplayTracker::MessageReplayTracker(uint
>  f) : flushInterval(f), count(0) {}
> client/MessageReplayTracker.cpp:51:void 
> MessageReplayTracker::setFlushInterval(uint f)
> client/MessageReplayTracker.cpp:56:uint 
> MessageReplayTracker::getFlushInterval()
> client/SaslFactory.cpp:331:uint ssf = *(reinterpret_cast unsigned*>(value));
> framing/SendContent.cpp:24:qpid::framing::SendContent::SendContent(FrameHandler&
>  h, uint16_t mfs, uint efc) : handler(h), 
> framing/SendContent.h:42:uint expectedFrameCount;
> framing/SendContent.h:43:uint frameCount;
> framing/SendContent.h:48:QPID_COMMON_EXTERN SendContent(FrameHandler& 
> _handler, uint16_t _maxFrameSize, uint frameCount);
> sys/Semaphore.h:30:Semaphore(uint c = 1) : count(c) {}
> sys/Semaphore.h:54:void release(uint n)
> sys/Semaphore.h:74:uint count;

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
Apache Qpid - AMQP Messaging Implementation
Project:  http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org

[jira] Updated: (QPID-2543) Change uint to standard type

[Bruno Matos (JIRA)]

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

Bruno Matos updated QPID-2543:
--

Attachment: (was: CPP_uint_to_unsigned_int.patch)

> Change uint to standard type
> 
>
> Key: QPID-2543
> URL: https://issues.apache.org/jira/browse/QPID-2543
> Project: Qpid
>  Issue Type: Improvement
>  Components: C++ Client
>Affects Versions: 0.7
>Reporter: Bruno Matos
> Fix For: 0.6
>
> Attachments: CPP_uint_to_unsigned_int.patch
>
>   Original Estimate: 0.25h
>  Remaining Estimate: 0.25h
>
> I can't find uint as a standard type and it is breaking Mac OS X client 
> compilation.
> The references I found:
> broker/Broker.h:109:uint queueLimit;
> broker/Link.cpp:338:uint Link::nextChannel()
> broker/Link.h:71:uint channelCounter;
> broker/Link.h:111:uint nextChannel();
> broker/SaslAuthenticator.cpp:432:uint ssf = *(reinterpret_cast unsigned*>(value));
> client/MessageReplayTracker.cpp:27:MessageReplayTracker::MessageReplayTracker(uint
>  f) : flushInterval(f), count(0) {}
> client/MessageReplayTracker.cpp:51:void 
> MessageReplayTracker::setFlushInterval(uint f)
> client/MessageReplayTracker.cpp:56:uint 
> MessageReplayTracker::getFlushInterval()
> client/SaslFactory.cpp:331:uint ssf = *(reinterpret_cast unsigned*>(value));
> framing/SendContent.cpp:24:qpid::framing::SendContent::SendContent(FrameHandler&
>  h, uint16_t mfs, uint efc) : handler(h), 
> framing/SendContent.h:42:uint expectedFrameCount;
> framing/SendContent.h:43:uint frameCount;
> framing/SendContent.h:48:QPID_COMMON_EXTERN SendContent(FrameHandler& 
> _handler, uint16_t _maxFrameSize, uint frameCount);
> sys/Semaphore.h:30:Semaphore(uint c = 1) : count(c) {}
> sys/Semaphore.h:54:void release(uint n)
> sys/Semaphore.h:74:uint count;

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
Apache Qpid - AMQP Messaging Implementation
Project:  http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org

[jira] Commented: (QPID-2543) Change uint to standard type

[Bruno Matos (JIRA)]

[ 
https://issues.apache.org/jira/browse/QPID-2543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12860361#action_12860361
 ] 

Bruno Matos commented on QPID-2543:
---

If there is a better way to do it, just say.

Thank you!

> Change uint to standard type
> 
>
> Key: QPID-2543
> URL: https://issues.apache.org/jira/browse/QPID-2543
> Project: Qpid
>  Issue Type: Improvement
>  Components: C++ Client
>Affects Versions: 0.7
>Reporter: Bruno Matos
> Fix For: 0.6
>
> Attachments: CPP_uint_to_unsigned_int.patch
>
>   Original Estimate: 0.25h
>  Remaining Estimate: 0.25h
>
> I can't find uint as a standard type and it is breaking Mac OS X client 
> compilation.
> The references I found:
> broker/Broker.h:109:uint queueLimit;
> broker/Link.cpp:338:uint Link::nextChannel()
> broker/Link.h:71:uint channelCounter;
> broker/Link.h:111:uint nextChannel();
> broker/SaslAuthenticator.cpp:432:uint ssf = *(reinterpret_cast unsigned*>(value));
> client/MessageReplayTracker.cpp:27:MessageReplayTracker::MessageReplayTracker(uint
>  f) : flushInterval(f), count(0) {}
> client/MessageReplayTracker.cpp:51:void 
> MessageReplayTracker::setFlushInterval(uint f)
> client/MessageReplayTracker.cpp:56:uint 
> MessageReplayTracker::getFlushInterval()
> client/SaslFactory.cpp:331:uint ssf = *(reinterpret_cast unsigned*>(value));
> framing/SendContent.cpp:24:qpid::framing::SendContent::SendContent(FrameHandler&
>  h, uint16_t mfs, uint efc) : handler(h), 
> framing/SendContent.h:42:uint expectedFrameCount;
> framing/SendContent.h:43:uint frameCount;
> framing/SendContent.h:48:QPID_COMMON_EXTERN SendContent(FrameHandler& 
> _handler, uint16_t _maxFrameSize, uint frameCount);
> sys/Semaphore.h:30:Semaphore(uint c = 1) : count(c) {}
> sys/Semaphore.h:54:void release(uint n)
> sys/Semaphore.h:74:uint count;

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
Apache Qpid - AMQP Messaging Implementation
Project:  http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org

[jira] Updated: (QPID-2543) Change uint to standard type

[Bruno Matos (JIRA)]

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

Bruno Matos updated QPID-2543:
--

Attachment: CPP_uint_to_unsigned_int.patch

Patch to convert all uint references to unsigned int

> Change uint to standard type
> 
>
> Key: QPID-2543
> URL: https://issues.apache.org/jira/browse/QPID-2543
> Project: Qpid
>  Issue Type: Improvement
>  Components: C++ Client
>Affects Versions: 0.7
>Reporter: Bruno Matos
> Fix For: 0.6
>
> Attachments: CPP_uint_to_unsigned_int.patch
>
>   Original Estimate: 0.25h
>  Remaining Estimate: 0.25h
>
> I can't find uint as a standard type and it is breaking Mac OS X client 
> compilation.
> The references I found:
> broker/Broker.h:109:uint queueLimit;
> broker/Link.cpp:338:uint Link::nextChannel()
> broker/Link.h:71:uint channelCounter;
> broker/Link.h:111:uint nextChannel();
> broker/SaslAuthenticator.cpp:432:uint ssf = *(reinterpret_cast unsigned*>(value));
> client/MessageReplayTracker.cpp:27:MessageReplayTracker::MessageReplayTracker(uint
>  f) : flushInterval(f), count(0) {}
> client/MessageReplayTracker.cpp:51:void 
> MessageReplayTracker::setFlushInterval(uint f)
> client/MessageReplayTracker.cpp:56:uint 
> MessageReplayTracker::getFlushInterval()
> client/SaslFactory.cpp:331:uint ssf = *(reinterpret_cast unsigned*>(value));
> framing/SendContent.cpp:24:qpid::framing::SendContent::SendContent(FrameHandler&
>  h, uint16_t mfs, uint efc) : handler(h), 
> framing/SendContent.h:42:uint expectedFrameCount;
> framing/SendContent.h:43:uint frameCount;
> framing/SendContent.h:48:QPID_COMMON_EXTERN SendContent(FrameHandler& 
> _handler, uint16_t _maxFrameSize, uint frameCount);
> sys/Semaphore.h:30:Semaphore(uint c = 1) : count(c) {}
> sys/Semaphore.h:54:void release(uint n)
> sys/Semaphore.h:74:uint count;

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
Apache Qpid - AMQP Messaging Implementation
Project:  http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org

RE: Contributer Patches - Committers Requested

[Steve Huston]

I assigned the WCF and Windows SSL ones to me.

-Steve

> -Original Message-
> From: Marnie McCormack [mailto:marnie.mccorm...@googlemail.com] 
> Sent: Thursday, April 22, 2010 7:06 AM
> To: dev@qpid.apache.org
> Subject: Contributer Patches - Committers Requested
> 
> 
> Hi All,
> 
> I think there may be a few JIRAs out there with patches 
> looking for a committer to pick up.
> 
> We've got quite a few contributers who are new/just getting 
> established just now so I'd like to propose we volunteer to 
> pair up with the new submitters to pick up patches. Perhaps 
> the ad hoc system is working just now, but I'm not sure how 
> else we avoid items dropping into gaps ? Be good to have 
> thoughts on this subject.
> 
> I've spotted a few patches (below) in need of a committer, 
> just from recent activity on JIRA and I think Emmanuel might 
> have a couple of older ones about too. (There's a couple I 
> wasn't sure if the patch had been applied/issue resolved or not.)
> 
> Contributers - please shout if I've missed anything else 
> you're waiting for us to pick up ? Thank you.
> 
>  *Key*
>  *Summary*
>  *Assignee*
>  *Reporter*
>  QPID-2498 
>  Upgrade Mina to 1.1.7
>  Martin Ritchie
>  Emmanuel Bourg
>  QPID-2531 
>  Improve the qpid broker build system to automatically build 
> OSGI modules on broker-plugins directory  Unassigned  Sorin 
> Suciu  QPID-2530 
>  Refactor the broker-plugins directory setup to allow adding 
> new modules  Unassigned  Sorin Suciu  QPID-2529 
> 
>  Update the Felix OSGI framework to a recent release
>  Unassigned
>  Sorin Suciu
>  QPID-2528 
>  qpid-config's add exchange option "--durable" doesn't work  
> Unassigned  Tim Powers  QPID-1811 
> 
>  Unable to compile qpid on FreeBSD
>  ? Andrew Stitcher
>  Attila Nagy
>  QPID-2526 
>  Ant build fails if the path contains a space character  
> Unassigned  Emmanuel Bourg  QPID-2513 
> 
>  Expose the ServerConfiguration as an OSGI service for use in 
> plugins  Unassigned  Sorin Suciu  QPID-2519 
> 
>  Allow Windows Broker to run as a Service
>  Unassigned
>  Kerry Bonin
>  QPID-2520 
>  Broken POM generation on Windows
>  Unassigned
>  Emmanuel Bourg
>  QPID-2516 
>  New sample to show how to specify WCF bindings in config 
> files  Unassigned  Cliff Jansen  QPID-2501 
> 
>  WCF Binding Configuration parameters
>  Unassigned
>  Cliff Jansen
>  QPID-2500 
>  Transport security for the WCF channel
>  Unassigned
>  Cliff Jansen
>  QPID-2502 
>  securityTracker open() call is made on exchangeTracker 
> instance instead  Unassigned  Sorin Suciu Regards, Marnie
> 


-
Apache Qpid - AMQP Messaging Implementation
Project:  http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org

[jira] Commented: (QPID-2517) Proposed change to QMF schema for the broker

[Rafael H. Schloming (JIRA)]

[ 
https://issues.apache.org/jira/browse/QPID-2517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12860335#action_12860335
 ] 

Rafael H. Schloming commented on QPID-2517:
---

I'd go ahead and commit this as an interim fix, but leave the JIRA open so Rob 
can comment when he gets back.

> Proposed change to QMF schema for the broker
> 
>
> Key: QPID-2517
> URL: https://issues.apache.org/jira/browse/QPID-2517
> Project: Qpid
>  Issue Type: Improvement
>  Components: C++ Broker, Java Broker
>Reporter: Ted Ross
>Assignee: Ted Ross
>Priority: Minor
> Attachments: broker-idx.diff, java.diff
>
>
> I would like to make a change to the management schema for the broker.  A 
> patch will be attached.
> The current schema causes the "broker" object to be indexed by the TCP port.  
> This is a problem in clusters where each node in the cluster may have a 
> different port.  Since the port is part of the index, and the index is used 
> as the QMFv2 object identifier, method calls addressed to the broker may not 
> be handled uniformly by each node in a cluster.
> The change removes the "index" status from the "port" attribute and adds a 
> new index attribute called "name".  This name is fixed as "amqp-broker".  
> This is a safe thing to do as there is only one broker associated with the 
> broker-resident agent.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
Apache Qpid - AMQP Messaging Implementation
Project:  http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org

Re: Contributer Patches - Committers Requested

[Martin Ritchie]

On 22 April 2010 12:08, Martin Ritchie  wrote:
> On 22 April 2010 12:05, Marnie McCormack
>  wrote:
>> Hi All,
>>
>> I think there may be a few JIRAs out there with patches looking for a
>> committer to pick up.
>>
>> We've got quite a few contributers who are new/just getting established just
>> now so I'd like to propose we volunteer to pair up with the new submitters
>> to pick up patches. Perhaps the ad hoc system is working just now, but I'm
>> not sure how else we avoid items dropping into gaps ? Be good to have
>> thoughts on this subject.
>>
>> I've spotted a few patches (below) in need of a committer, just from recent
>> activity on JIRA and I think Emmanuel might have a couple of older ones
>> about too. (There's a couple I wasn't sure if the patch had been
>> applied/issue resolved or not.)
>>
>> Contributers - please shout if I've missed anything else you're waiting for
>> us to pick up ? Thank you.
>>
>> *Key*
>>  *Summary*
>>  *Assignee*
>>  *Reporter*
>>  QPID-2498 
>>  Upgrade Mina to 1.1.7
>>  Martin Ritchie
>>  Emmanuel Bourg
>>  QPID-2531 
>>  Improve the qpid broker build system to automatically build OSGI modules on
>> broker-plugins directory
>>  Unassigned
>>  Sorin Suciu
>>  QPID-2530 
>>  Refactor the broker-plugins directory setup to allow adding new modules
>>  Unassigned
>>  Sorin Suciu
>>  QPID-2529 
>>  Update the Felix OSGI framework to a recent release
>>  Unassigned
>>  Sorin Suciu
>>  QPID-2528 
>>  qpid-config's add exchange option "--durable" doesn't work
>>  Unassigned
>>  Tim Powers
>>  QPID-1811 
>>  Unable to compile qpid on FreeBSD
>>  ? Andrew Stitcher
>>  Attila Nagy
>>  QPID-2526 
>>  Ant build fails if the path contains a space character
>>  Unassigned
>>  Emmanuel Bourg
>>  QPID-2513 
>>  Expose the ServerConfiguration as an OSGI service for use in plugins
>>  Unassigned
>>  Sorin Suciu
>>  QPID-2519 
>>  Allow Windows Broker to run as a Service
>>  Unassigned
>>  Kerry Bonin
>>  QPID-2520 
>>  Broken POM generation on Windows
>>  Unassigned
>>  Emmanuel Bourg
>>  QPID-2516 
>>  New sample to show how to specify WCF bindings in config files
>>  Unassigned
>>  Cliff Jansen
>>  QPID-2501 
>>  WCF Binding Configuration parameters
>>  Unassigned
>>  Cliff Jansen
>>  QPID-2500 
>>  Transport security for the WCF channel
>>  Unassigned
>>  Cliff Jansen
>>  QPID-2502 
>>  securityTracker open() call is made on exchangeTracker instance instead
>>  Unassigned
>>  Sorin Suciu
>> Regards,
>> Marnie
>
> I'll take a look at the following:
> QPID-2498
> QPID-2502
> QPID-2513
> QPID-2529
> QPID-2530
> QPID-2531
>
> I'll assign them over to me now.
>
> Martin
>
>
> --
> Martin Ritchie
>

I've reviewed and applied Sorin's patches. Thanks for those Sorin,
OSGi is the new hotness for the broker.

Will look at QPID-2529 again when you've got a patch on it.

Thanks again for those.

Emmanuel will look at the mina one next.

Cheers
-- 
Martin Ritchie

-
Apache Qpid - AMQP Messaging Implementation
Project:  http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org

[jira] Commented: (QPID-2199) Federation connections initiated from windows brokers stuck in "connecting" state

[Steve Huston (JIRA)]

[ 
https://issues.apache.org/jira/browse/QPID-2199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12860313#action_12860313
 ] 

Steve Huston commented on QPID-2199:


Kerry, there's another jira around somewhere that suggests ways to replace the 
compiler-directed tss with a run-time directed mechanism. That would alleviate 
the DLL-loading problems. Driving it from that angle may be more efficient. For 
now, you could try using the compiler-directed TSS on Windows (there's a 
QPID_TSS or some such macro that does this) to see if that's going to solve the 
problem.

> Federation connections initiated from windows brokers stuck in "connecting" 
> state
> -
>
> Key: QPID-2199
> URL: https://issues.apache.org/jira/browse/QPID-2199
> Project: Qpid
>  Issue Type: Bug
>  Components: C++ Broker
>Affects Versions: 0.5
> Environment: Windows XP, qpid 0.5 from .msi installer, hosts scengsrv 
> and jlaughlin, qpidbroker.exe running under cmd.exe, other tools running 
> under cygwin
> Ubuntu Hardy, qpid 0.5 compiled from source with unused return value patches, 
> host santa-anna
>Reporter: Jeff Laughlin
> Attachments: linux.cap, linux.out, windows.cap, windows.out
>
>
> My Windows broker can't establish federation link to other brokers running on 
> windows or linux; links remain in "connecting" state forever. Packet sniffer 
> reveals strange and inconsistent things. Linux broker can successfully 
> establish links to windows brokers, however. Python client tools seems to 
> work fine with both windows and linux brokers, from both cygwin python and 
> linux python.
> Here's a terminal session transcript that illustrates this behavior. I'm 
> starting with two fresh instances of qpid on two different windows hosts, 
> jlaughlin and scengsrv. Both have been configured with a durable alarms 
> exchange and durable alarmd queue that have been bound together.
> First I try to create the link in push mode, so qpid-route is commanding 
> jlaughlin (the localhost) to establish a link to scengsrv
> jlaugh...@jlaughlin ~/Downloads/qpid-0.5/python/commands
> $ python2.5 qpid-route queue add scengsrv jlaughlin alarms alarmd --ack 1 
> --src-local
> After a  moment I check my links
> jlaugh...@jlaughlin ~/Downloads/qpid-0.5/python/commands
> $ python2.5 qpid-route link list
> HostPortTransport Durable  State Last Error
> =
> scengsrv5672tcp  N Connecting
> Hm it's still connecting. Wait a few moments.
> jlaugh...@jlaughlin ~/Downloads/qpid-0.5/python/commands
> $ python2.5 qpid-route link list
> HostPortTransport Durable  State Last Error
> =
> scengsrv5672tcp  N Connecting
> Still connecting. Darn. Lets try going the other way, commanding scengsrv to 
> link to jlaughlin.
> jlaugh...@jlaughlin ~/Downloads/qpid-0.5/python/commands
> $ python2.5 qpid-route queue add scengsrv jlaughlin alarms alarmd --ack 1 
>
> jlaugh...@jlaughlin ~/Downloads/qpid-0.5/python/commands
> $ python2.5 qpid-route link list scengsrv
> HostPortTransport Durable  State Last Error
> =
> jlaughlin   5672tcp  N Connecting
> Still no good.
> Now lets try commanding jlaughlin to connect to my linux box, santa-anna
> jlaugh...@jlaughlin ~/Downloads/qpid-0.5/python/commands
> $ python2.5 qpid-route queue add santa-anna jlaughlin alarms alarmd --ack 1 
> --src-local
> jlaugh...@jlaughlin ~/Downloads/qpid-0.5/python/commands
> $ python2.5 qpid-route link list 
> HostPortTransport Durable  State Last Error
> =
> santa-anna  5672tcp  N Connecting
> jlaugh...@jlaughlin ~/Downloads/qpid-0.5/python/commands
> $ python2.5 qpid-route link list 
> HostPortTransport Durable  State Last Error
> =
> santa-anna  5672tcp  N Connecting
> Negative, ghost rider, the pattern is full.
> Enough of this, lets command the linux host, santa-anna, to connect to my 
> jlaughlin windows host:
> jlaugh...@jlaughlin ~/Downloads/qpid-0.5/python/commands
> $ python2.5 qpid-route queue add santa-anna jlaughlin alarms alarmd --ack 1   
>  
> jlaugh...@jlaughlin ~/Downloads/qpid-0.5/python/commands
> $ python2.5 qpid-route link list santa-anna
> HostPo

[jira] Commented: (QPID-2543) Change uint to standard type

[Steve Huston (JIRA)]

[ 
https://issues.apache.org/jira/browse/QPID-2543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12860314#action_12860314
 ] 

Steve Huston commented on QPID-2543:


I suppose you could, yes. It's more work, but it'll do.

> Change uint to standard type
> 
>
> Key: QPID-2543
> URL: https://issues.apache.org/jira/browse/QPID-2543
> Project: Qpid
>  Issue Type: Improvement
>  Components: C++ Client
>Affects Versions: 0.7
>Reporter: Bruno Matos
> Fix For: 0.6
>
>   Original Estimate: 0.25h
>  Remaining Estimate: 0.25h
>
> I can't find uint as a standard type and it is breaking Mac OS X client 
> compilation.
> The references I found:
> broker/Broker.h:109:uint queueLimit;
> broker/Link.cpp:338:uint Link::nextChannel()
> broker/Link.h:71:uint channelCounter;
> broker/Link.h:111:uint nextChannel();
> broker/SaslAuthenticator.cpp:432:uint ssf = *(reinterpret_cast unsigned*>(value));
> client/MessageReplayTracker.cpp:27:MessageReplayTracker::MessageReplayTracker(uint
>  f) : flushInterval(f), count(0) {}
> client/MessageReplayTracker.cpp:51:void 
> MessageReplayTracker::setFlushInterval(uint f)
> client/MessageReplayTracker.cpp:56:uint 
> MessageReplayTracker::getFlushInterval()
> client/SaslFactory.cpp:331:uint ssf = *(reinterpret_cast unsigned*>(value));
> framing/SendContent.cpp:24:qpid::framing::SendContent::SendContent(FrameHandler&
>  h, uint16_t mfs, uint efc) : handler(h), 
> framing/SendContent.h:42:uint expectedFrameCount;
> framing/SendContent.h:43:uint frameCount;
> framing/SendContent.h:48:QPID_COMMON_EXTERN SendContent(FrameHandler& 
> _handler, uint16_t _maxFrameSize, uint frameCount);
> sys/Semaphore.h:30:Semaphore(uint c = 1) : count(c) {}
> sys/Semaphore.h:54:void release(uint n)
> sys/Semaphore.h:74:uint count;

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
Apache Qpid - AMQP Messaging Implementation
Project:  http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org

[jira] Assigned: (QPID-2359) Need functional tests for the transactional AMQP WCF channel

[Steve Huston (JIRA)]

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

Steve Huston reassigned QPID-2359:
--

Assignee: Steve Huston

> Need functional tests for the transactional AMQP WCF channel
> 
>
> Key: QPID-2359
> URL: https://issues.apache.org/jira/browse/QPID-2359
> Project: Qpid
>  Issue Type: Test
>  Components: WCF/C++ Client
>Affects Versions: 0.6
>Reporter: Devang Gandhi
>Assignee: Steve Huston
> Attachments: QPID-2359.patch
>
>


-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
Apache Qpid - AMQP Messaging Implementation
Project:  http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org

[jira] Assigned: (QPID-2415) Update doc for new SSL support in Windows broker and client

[Steve Huston (JIRA)]

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

Steve Huston reassigned QPID-2415:
--

Assignee: Steve Huston

> Update doc for new SSL support in Windows broker and client
> ---
>
> Key: QPID-2415
> URL: https://issues.apache.org/jira/browse/QPID-2415
> Project: Qpid
>  Issue Type: Improvement
>  Components: C++ Broker
>Affects Versions: 0.7
> Environment: Windows
>Reporter: Cliff Jansen
>Assignee: Steve Huston
> Fix For: 0.7
>
> Attachments: ssldoc.patch
>
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> SSL support has been added to Windows.  The SSL related documentation should 
> be updated to reflect that.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
Apache Qpid - AMQP Messaging Implementation
Project:  http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org

[jira] Assigned: (QPID-2516) New sample to show how to specify WCF bindings in config files

[Steve Huston (JIRA)]

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

Steve Huston reassigned QPID-2516:
--

Assignee: Steve Huston

> New sample to show how to specify WCF bindings in config files
> --
>
> Key: QPID-2516
> URL: https://issues.apache.org/jira/browse/QPID-2516
> Project: Qpid
>  Issue Type: Improvement
>  Components: WCF/C++ Client
>Affects Versions: 0.7
> Environment: Windows
>Reporter: Cliff Jansen
>Assignee: Steve Huston
> Fix For: 0.7
>
> Attachments: QPID-2516.patch
>
>   Original Estimate: 2h
>  Remaining Estimate: 2h
>


-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
Apache Qpid - AMQP Messaging Implementation
Project:  http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org

[jira] Assigned: (QPID-2500) Transport security for the WCF channel

[Steve Huston (JIRA)]

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

Steve Huston reassigned QPID-2500:
--

Assignee: Steve Huston

> Transport security for the WCF channel
> --
>
> Key: QPID-2500
> URL: https://issues.apache.org/jira/browse/QPID-2500
> Project: Qpid
>  Issue Type: New Feature
>  Components: WCF/C++ Client
>Affects Versions: 0.7
> Environment: Windows
>Reporter: Cliff Jansen
>Assignee: Steve Huston
> Fix For: 0.7
>
> Attachments: QPID-2500-1.patch, QPID-2500-2.patch, QPID-2500-3.patch
>
>
> SSL and Sasl PLAIN capabilities have been recently ported to the C++ client 
> on Windows.  The WCF client can now be enhanced to use these features and to 
> provide the expected transport level security classes and binding parameters 
> for specifying encryption and authentication on the transport channel.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
Apache Qpid - AMQP Messaging Implementation
Project:  http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org

[jira] Assigned: (QPID-2501) WCF Binding Configuration parameters

[Steve Huston (JIRA)]

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

Steve Huston reassigned QPID-2501:
--

Assignee: Steve Huston

> WCF Binding Configuration parameters
> 
>
> Key: QPID-2501
> URL: https://issues.apache.org/jira/browse/QPID-2501
> Project: Qpid
>  Issue Type: Improvement
>  Components: WCF/C++ Client
>Affects Versions: 0.7
> Environment: Windows
>Reporter: Cliff Jansen
>Assignee: Steve Huston
> Fix For: 0.7
>
> Attachments: QPID-2501.patch
>
>   Original Estimate: 48h
>  Remaining Estimate: 48h
>
> The existing configuration capabilities of the WCF channel should be fleshed 
> out to handle transport level security.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
Apache Qpid - AMQP Messaging Implementation
Project:  http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org

[jira] Created: (QPID-2547) Improve PluginTest.java in order to test new OSGI plugins

[Sorin Suciu (JIRA)]

Improve PluginTest.java in order to test new OSGI plugins
-

 Key: QPID-2547
 URL: https://issues.apache.org/jira/browse/QPID-2547
 Project: Qpid
  Issue Type: Improvement
  Components: Java Broker
Affects Versions: 0.7
Reporter: Sorin Suciu
 Fix For: 0.7


The current PluginTest.java is testing only the TestExchangePlugin, this can be 
improved so:
- it can easily test other plugins
- tests the correct loading/unloading of the plugins

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
Apache Qpid - AMQP Messaging Implementation
Project:  http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org

Re: Versioning DocBook and API docs on the Qpid Web Site

[Rajith Attapattu]

On Fri, Apr 23, 2010 at 11:50 AM, Jonathan Robie
 wrote:
> If we want to post our current docs as work-in-progress, but still have the
> flexibility to be able to keep multiple versions on the site, we could put
> all docs in ./devel for now. Would you be OK with that?

For now we can post all docs under /devel or /trunk  (I think that
gives the users the impression that it's work-in-progress)
(Also going forward we can continue to maintain the /devel for people
who use trunk)
Then for each release we put them under the release number.
In our website we could have links for the last 3 releases and the
rest under "Archive".
(I described this in the prototype for the website. But I can't seem
to access my apache space now)

> I like the idea of putting a header on the Wiki page. I think it should
> mention that we are "in the process of" replacing the Wiki, and link to the
> new DocBook docs.
>
> I also like the idea of not deleting the old Wiki info.
>
> Make sense?
agreed.

> Jonathan
>
> On 04/23/2010 11:34 AM, Rajith Attapattu wrote:
>>
>> I would keep it simple for now.
>>
>> We should post the current docs as work-in-progress.
>> Then when we release 0.7 we can then have our first set of version
>> controlled docs.
>> For all previous releases we should ask them to refer to the wiki docs.
>>
>> We shouldn't delete the old wiki docs.
>> Rather in bold letters we should put at the top saying that these docs
>> are deprecated and *may* only be relevant for versions<  0.7 or
>> something to that extent :)
>>
>> How does that sound?
>>
>> Rajith
>>
>> On Fri, Apr 23, 2010 at 11:20 AM, Jonathan Robie
>>   wrote:
>>
>>>
>>> I'm getting ready to post the DocBook docs on the Qpid web site along
>>> with
>>> API docs (looks like early next week at this point).
>>>
>>> I want to make sure we have a good plan to handle versions and links
>>> among
>>> documents. I think a file structure like this might work well:
>>>
>>> Versions
>>>
>>> http://qpid.apache.org/doc/
>>> contains all docs
>>>
>>> http://qpid.apache.org/devel/
>>> symlink to the devel version of the documentation
>>>
>>> http://qpid.apache.org/stable/
>>> symlink to the docs for the latest release
>>>
>>> http://qpid.apache.org/doc/ 0.6/
>>> docs for a specific version
>>>
>>> Subdirectories
>>>
>>> http://qpid.apache.org/doc/stable/book/
>>> Current Wiki, converted to book. We may eventually subdivide this into
>>> different guides, e.g.
>>> http://qpid.apache.org/doc/stable/book/programming,
>>> or http://qpid.apache.org/doc/stable/book/broker-java.
>>>
>>> http://qpid.apache.org/doc/stable/api/cpp
>>> C++ API reference, generated by Doxygen
>>>
>>> http://qpid.apache.org/doc/stable/api/cpp
>>> Python API reference, generated by ePydoc
>>>
>>> Links among Documents
>>>
>>> Links should be absolute links to the current version of the
>>> documentation.
>>> For instance, a link from
>>> http://qpid.apache.org/doc/0.6/book/qpid-book.html to the C++ API docs
>>> should point to http://qpid.apache.org/doc/0.6/api/cpp
>>>
>>> Tracking changes in the text
>>>
>>> We should endeaver to use phrases like "since 0.6" to identify new
>>> features
>>> and changes, so the latest documentation shows what has changed.
>>>
>>>
>>> Does this makes sense? Once we start using a given structure, it becomes
>>> harder to change, so I want to get agreement on this up front.
>>>
>>> Jonathan
>>>
>>> -
>>> Apache Qpid - AMQP Messaging Implementation
>>> Project:      http://qpid.apache.org
>>> Use/Interact: mailto:dev-subscr...@qpid.apache.org
>>>
>>>
>>>
>>
>>
>>
>
>
> -
> Apache Qpid - AMQP Messaging Implementation
> Project:      http://qpid.apache.org
> Use/Interact: mailto:dev-subscr...@qpid.apache.org
>
>



-- 
Regards,

Rajith Attapattu
Red Hat
http://rajith.2rlabs.com/

-
Apache Qpid - AMQP Messaging Implementation
Project:  http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org

[jira] Commented: (QPID-2537) Add QMF/JMX administration of ACLs

[Rajith Attapattu (JIRA)]

[ 
https://issues.apache.org/jira/browse/QPID-2537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12860296#action_12860296
 ] 

Rajith Attapattu commented on QPID-2537:


Just to clarify "1. Add/Remove/Modify users and groups " further.

We are not adding new users here. Users are managed via authentication.
What I meant was adding/removing and modifying the groups.
Sorry if my initial comment was not clear.

> Add QMF/JMX administration of ACLs
> --
>
> Key: QPID-2537
> URL: https://issues.apache.org/jira/browse/QPID-2537
> Project: Qpid
>  Issue Type: Sub-task
>  Components: Java Broker, Java Management : JMX Interface, Java 
> Management : QMF
>Reporter: Andrew Kennedy
> Fix For: 0.7
>
>


-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
Apache Qpid - AMQP Messaging Implementation
Project:  http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org

[jira] Commented: (QPID-2531) Improve the qpid broker build system to automatically build OSGI modules on broker-plugins directory

[Martin Ritchie (JIRA)]

[ 
https://issues.apache.org/jira/browse/QPID-2531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12860294#action_12860294
 ] 

Martin Ritchie commented on QPID-2531:
--

We should update the plugin integration to build a release artefact with 
installations instructions.

> Improve the qpid broker build system to automatically build OSGI modules on 
> broker-plugins directory
> 
>
> Key: QPID-2531
> URL: https://issues.apache.org/jira/browse/QPID-2531
> Project: Qpid
>  Issue Type: Improvement
>Reporter: Sorin Suciu
>Assignee: Martin Ritchie
> Attachments: qpid-2531.patch
>
>
> The qpid broker ant build system could be improved to automatically build the 
> OSGI modules in the broker-plugins directory given we might have multiple 
> modules. For this, we could modify the current build.xml file from 
> broker-plugins to delegate the tasks to each individual module via a subant 
> task. Each module would have its own build.xml file (which would be pretty 
> much generic). 
> So the task of adding a new OSGI module would involve: 
> - creating a new directory (eg myplugin) having a generic build.xml and the 
> code in src subdir
> - adding the new directory to the subant task so it will be build
> - updating the build.deps file

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
Apache Qpid - AMQP Messaging Implementation
Project:  http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org

[jira] Resolved: (QPID-2513) Expose the ServerConfiguration as an OSGI service for use in plugins

[Martin Ritchie (JIRA)]

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

Martin Ritchie resolved QPID-2513.
--

Resolution: Fixed

> Expose the ServerConfiguration as an OSGI service for use in plugins
> 
>
> Key: QPID-2513
> URL: https://issues.apache.org/jira/browse/QPID-2513
> Project: Qpid
>  Issue Type: Improvement
>Affects Versions: 0.5, 0.6, 0.7
>Reporter: Sorin Suciu
>Assignee: Martin Ritchie
> Fix For: 0.7
>
> Attachments: qpid-2513.patch
>
>
> The ServerConfiguration could be used by OSGI plugins to query configuration 
> parameters. For this, a service has to be registered with the current OSGI 
> framework (currently Apache Felix). 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
Apache Qpid - AMQP Messaging Implementation
Project:  http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org

[jira] Resolved: (QPID-2530) Refactor the broker-plugins directory setup to allow adding new modules

[Martin Ritchie (JIRA)]

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

Martin Ritchie resolved QPID-2530.
--

Resolution: Fixed

> Refactor the broker-plugins directory setup to allow adding new modules 
> 
>
> Key: QPID-2530
> URL: https://issues.apache.org/jira/browse/QPID-2530
> Project: Qpid
>  Issue Type: Improvement
>Reporter: Sorin Suciu
>Assignee: Martin Ritchie
> Fix For: 0.7
>
> Attachments: build.xml, extras.tgz
>
>
> The broker-plugins is currently having only one module (DiagnosticExchange 
> and TestExchange). We should have a directory for each module building as  a 
> separate jar. This would allow adding a new module to be just a matter of 
> creating a new directory and adding it to the build system, We should move 
> the content of the src directory to its own plugin directory and adjust the 
> build system accordingly. Suggested layout: 
> broker-plugins
> ---> build.xml
> ---> extras  (OSGI-Plugin) 
> ---> my_plugin1 (OSGI-Plugin)
> ---> my_plugin2 (OSGI-Plugin)
>  etc
> Please perform the following: on java/broker-plugins folder: 
> - delete the src folder and untar the tarball attached
> - remove the build.xml and add the attached build.xml
> - apply QPID-2502 to fix the PluginManager.java issue with security tracker
> - apply QPID-2513 
> - apply QPID-2531 to update the build.deps and main build.xml

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
Apache Qpid - AMQP Messaging Implementation
Project:  http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org

[jira] Closed: (QPID-2502) securityTracker open() call is made on exchangeTracker instance instead

[Martin Ritchie (JIRA)]

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

Martin Ritchie closed QPID-2502.


Resolution: Fixed

Covered by QPID-2513

> securityTracker open() call  is made  on exchangeTracker instance instead
> -
>
> Key: QPID-2502
> URL: https://issues.apache.org/jira/browse/QPID-2502
> Project: Qpid
>  Issue Type: Bug
>  Components: Java Broker
>Affects Versions: 0.5
>Reporter: Sorin Suciu
>Assignee: Martin Ritchie
>Priority: Minor
> Fix For: 0.7
>
> Attachments: qpid-2502.patch
>
>
> In this snippet:
> _exchangeTracker = new ServiceTracker(_activator.getContext(), 
> ExchangeType.class.getName(), null);
> _exchangeTracker.open();
> 
> _securityTracker = new ServiceTracker(_activator.getContext(), 
> ACLPlugin.class.getName(), null);
> _exchangeTracker.open();
> the open method is called on _exchangeTracker instead of  _securityTracker. 
> This leads to a NPE if plugin-directory is used in the config file. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
Apache Qpid - AMQP Messaging Implementation
Project:  http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org

[jira] Resolved: (QPID-2002) [Logging] Migrate existing logging to new framework

[Marnie McCormack (JIRA)]

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

Marnie McCormack resolved QPID-2002.


Resolution: Fixed

Accepted, too many commits on the JIRA for review in this lifetime!

> [Logging] Migrate existing logging to new framework
> ---
>
> Key: QPID-2002
> URL: https://issues.apache.org/jira/browse/QPID-2002
> Project: Qpid
>  Issue Type: Improvement
>  Components: Java Broker
>Reporter: Martin Ritchie
>Assignee: Marnie McCormack
>
> As described in the Technical specifcation there are some existing messages 
> that overlap with the new logging framework messages:
> http://cwiki.apache.org/confluence/display/qpid/Operational+Logging+-+Status+Update+-+Technical+Specification
> These old messages need migrated and any new messages need added and then 
> tested according to the test specfication:
> http://cwiki.apache.org/confluence/display/qpid/Operational+Logging+-+Status+Update+-+Test+Specification

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
Apache Qpid - AMQP Messaging Implementation
Project:  http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org

[jira] Commented: (QPID-2541) Separate Group an ACL configuration and make group sources pluggable

[Rajith Attapattu (JIRA)]

[ 
https://issues.apache.org/jira/browse/QPID-2541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12860293#action_12860293
 ] 

Rajith Attapattu commented on QPID-2541:


Users are under the purview of the authentication mechanism.
We use SASL for that.  

Groups in ACL is a convenience mechanism in ACL to allow a bunch of users (or 
groups) to be identified together.

As mentioned in the email thread, specifying the groups in the ACL file is just 
a convenience method.
By all means we need to allow them to be configured via other sources.
(However having a separate file for specifying groups doesn't really make 
sense.)


My preferred option of allowing dynamic provisioning of groups is via QMF as 
explained in QPID-2537
What other sources do you have in mind?

> Separate Group an ACL configuration and make group sources pluggable
> 
>
> Key: QPID-2541
> URL: https://issues.apache.org/jira/browse/QPID-2541
> Project: Qpid
>  Issue Type: Sub-task
>  Components: Java Broker
>Reporter: Andrew Kennedy
> Fix For: 0.7
>
>


-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
Apache Qpid - AMQP Messaging Implementation
Project:  http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org

Re: Versioning DocBook and API docs on the Qpid Web Site

[Marnie McCormack]

Hi, sounds like a plan to me !

Thanks,
Marnie

On Fri, Apr 23, 2010 at 4:50 PM, Jonathan Robie
wrote:

> If we want to post our current docs as work-in-progress, but still have the
> flexibility to be able to keep multiple versions on the site, we could put
> all docs in ./devel for now. Would you be OK with that?
>
> I like the idea of putting a header on the Wiki page. I think it should
> mention that we are "in the process of" replacing the Wiki, and link to the
> new DocBook docs.
>
> I also like the idea of not deleting the old Wiki info.
>
> Make sense?
>
> Jonathan
>
>
> On 04/23/2010 11:34 AM, Rajith Attapattu wrote:
>
>> I would keep it simple for now.
>>
>> We should post the current docs as work-in-progress.
>> Then when we release 0.7 we can then have our first set of version
>> controlled docs.
>> For all previous releases we should ask them to refer to the wiki docs.
>>
>> We shouldn't delete the old wiki docs.
>> Rather in bold letters we should put at the top saying that these docs
>> are deprecated and *may* only be relevant for versions<  0.7 or
>> something to that extent :)
>>
>> How does that sound?
>>
>> Rajith
>>
>> On Fri, Apr 23, 2010 at 11:20 AM, Jonathan Robie
>>   wrote:
>>
>>
>>> I'm getting ready to post the DocBook docs on the Qpid web site along
>>> with
>>> API docs (looks like early next week at this point).
>>>
>>> I want to make sure we have a good plan to handle versions and links
>>> among
>>> documents. I think a file structure like this might work well:
>>>
>>> Versions
>>>
>>> http://qpid.apache.org/doc/
>>> contains all docs
>>>
>>> http://qpid.apache.org/devel/
>>> symlink to the devel version of the documentation
>>>
>>> http://qpid.apache.org/stable/
>>> symlink to the docs for the latest release
>>>
>>> http://qpid.apache.org/doc/ 0.6/
>>> docs for a specific version
>>>
>>> Subdirectories
>>>
>>> http://qpid.apache.org/doc/stable/book/
>>> Current Wiki, converted to book. We may eventually subdivide this into
>>> different guides, e.g.
>>> http://qpid.apache.org/doc/stable/book/programming,
>>> or http://qpid.apache.org/doc/stable/book/broker-java.
>>>
>>> http://qpid.apache.org/doc/stable/api/cpp
>>> C++ API reference, generated by Doxygen
>>>
>>> http://qpid.apache.org/doc/stable/api/cpp
>>> Python API reference, generated by ePydoc
>>>
>>> Links among Documents
>>>
>>> Links should be absolute links to the current version of the
>>> documentation.
>>> For instance, a link from
>>> http://qpid.apache.org/doc/0.6/book/qpid-book.html to the C++ API docs
>>> should point to http://qpid.apache.org/doc/0.6/api/cpp
>>>
>>> Tracking changes in the text
>>>
>>> We should endeaver to use phrases like "since 0.6" to identify new
>>> features
>>> and changes, so the latest documentation shows what has changed.
>>>
>>>
>>> Does this makes sense? Once we start using a given structure, it becomes
>>> harder to change, so I want to get agreement on this up front.
>>>
>>> Jonathan
>>>
>>> -
>>> Apache Qpid - AMQP Messaging Implementation
>>> Project:  http://qpid.apache.org
>>> Use/Interact: mailto:dev-subscr...@qpid.apache.org
>>>
>>>
>>>
>>>
>>
>>
>>
>>
>
>
> -
> Apache Qpid - AMQP Messaging Implementation
> Project:  http://qpid.apache.org
> Use/Interact: mailto:dev-subscr...@qpid.apache.org
>
>

[jira] Commented: (QPID-1992) [Logging] Create Operational logging framework

[Marnie McCormack (JIRA)]

[ 
https://issues.apache.org/jira/browse/QPID-1992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12860288#action_12860288
 ] 

Marnie McCormack commented on QPID-1992:


Requires more work on trunk to make the logging model robust.

> [Logging] Create Operational logging framework
> --
>
> Key: QPID-1992
> URL: https://issues.apache.org/jira/browse/QPID-1992
> Project: Qpid
>  Issue Type: New Feature
>  Components: Java Broker
>Reporter: Martin Ritchie
>Assignee: Martin Ritchie
> Fix For: 0.6
>
> Attachments: qpid-1992-response.txt, QPID-1992-review.txt
>
>
> Summary:
> As a first step in improving the Java broker's logging operation this work 
> will provide a new abstraction layer for logging.
> Full Design and Technical Details can be found on confluence:
> http://cwiki.apache.org/confluence/display/qpid/Status+Update+Design
> http://cwiki.apache.org/confluence/display/qpid/Operational+Logging+-+Status+Update+-+Technical+Specification

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
Apache Qpid - AMQP Messaging Implementation
Project:  http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org

[jira] Resolved: (QPID-2001) [Logging] Provide mechanism to provide fixed log messages

[Marnie McCormack (JIRA)]

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

Marnie McCormack resolved QPID-2001.


Resolution: Fixed

> [Logging] Provide mechanism to provide fixed log messages
> -
>
> Key: QPID-2001
> URL: https://issues.apache.org/jira/browse/QPID-2001
> Project: Qpid
>  Issue Type: Improvement
>  Components: Java Broker
>Reporter: Martin Ritchie
>Assignee: Martin Ritchie
> Fix For: 0.6
>
> Attachments: qpid-2001-response.txt, QPID-2001-review.txt
>
>
> Summary:
> As highlighted in the Technical specification:
> http://cwiki.apache.org/confluence/display/qpid/Operational+Logging+-+Status+Update+-+Technical+Specification#OperationalLogging-StatusUpdate-TechnicalSpecification-Howtoprovidefixedlogmessages
> The logging design calls for the ablity to peform something similar to:
> String message = BrokerLogMessages.BRK-1001(version, build); 
> Producing:
> BRK-1001 : Startup : Version: 0.6 Build: 794277
> Where the actual LogMessage is parameterized :
> BRK-1001 = Startup : Version {0} Build: {1} 
> This has many benefits:
> - it easy to locate where a particular log messasge is sued
> - it makes updating the log messages straight forward.
> - it makes localisation easy

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
Apache Qpid - AMQP Messaging Implementation
Project:  http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org

Re: Versioning DocBook and API docs on the Qpid Web Site

[Jonathan Robie]

If we want to post our current docs as work-in-progress, but still have 
the flexibility to be able to keep multiple versions on the site, we 
could put all docs in ./devel for now. Would you be OK with that?


I like the idea of putting a header on the Wiki page. I think it should 
mention that we are "in the process of" replacing the Wiki, and link to 
the new DocBook docs.


I also like the idea of not deleting the old Wiki info.

Make sense?

Jonathan

On 04/23/2010 11:34 AM, Rajith Attapattu wrote:

I would keep it simple for now.

We should post the current docs as work-in-progress.
Then when we release 0.7 we can then have our first set of version
controlled docs.
For all previous releases we should ask them to refer to the wiki docs.

We shouldn't delete the old wiki docs.
Rather in bold letters we should put at the top saying that these docs
are deprecated and *may* only be relevant for versions<  0.7 or
something to that extent :)

How does that sound?

Rajith

On Fri, Apr 23, 2010 at 11:20 AM, Jonathan Robie
  wrote:
   

I'm getting ready to post the DocBook docs on the Qpid web site along with
API docs (looks like early next week at this point).

I want to make sure we have a good plan to handle versions and links among
documents. I think a file structure like this might work well:

Versions

http://qpid.apache.org/doc/
contains all docs

http://qpid.apache.org/devel/
symlink to the devel version of the documentation

http://qpid.apache.org/stable/
symlink to the docs for the latest release

http://qpid.apache.org/doc/ 0.6/
docs for a specific version

Subdirectories

http://qpid.apache.org/doc/stable/book/
Current Wiki, converted to book. We may eventually subdivide this into
different guides, e.g. http://qpid.apache.org/doc/stable/book/programming,
or http://qpid.apache.org/doc/stable/book/broker-java.

http://qpid.apache.org/doc/stable/api/cpp
C++ API reference, generated by Doxygen

http://qpid.apache.org/doc/stable/api/cpp
Python API reference, generated by ePydoc

Links among Documents

Links should be absolute links to the current version of the documentation.
For instance, a link from
http://qpid.apache.org/doc/0.6/book/qpid-book.html to the C++ API docs
should point to http://qpid.apache.org/doc/0.6/api/cpp

Tracking changes in the text

We should endeaver to use phrases like "since 0.6" to identify new features
and changes, so the latest documentation shows what has changed.


Does this makes sense? Once we start using a given structure, it becomes
harder to change, so I want to get agreement on this up front.

Jonathan

-
Apache Qpid - AMQP Messaging Implementation
Project:  http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org


 



   



-
Apache Qpid - AMQP Messaging Implementation
Project:  http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org

[jira] Updated: (QPID-1992) [Logging] Create Operational logging framework

[Marnie McCormack (JIRA)]

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

Marnie McCormack updated QPID-1992:
---

Status: Open  (was: Ready To Review)

Keeping log messages apart from log subjects enforces an unwritten contract 
between broekr events and the log messages generated. Will be fragile and will 
get broken, as discussed in detail.

> [Logging] Create Operational logging framework
> --
>
> Key: QPID-1992
> URL: https://issues.apache.org/jira/browse/QPID-1992
> Project: Qpid
>  Issue Type: New Feature
>  Components: Java Broker
>Reporter: Martin Ritchie
>Assignee: Martin Ritchie
> Fix For: 0.6
>
> Attachments: qpid-1992-response.txt, QPID-1992-review.txt
>
>
> Summary:
> As a first step in improving the Java broker's logging operation this work 
> will provide a new abstraction layer for logging.
> Full Design and Technical Details can be found on confluence:
> http://cwiki.apache.org/confluence/display/qpid/Status+Update+Design
> http://cwiki.apache.org/confluence/display/qpid/Operational+Logging+-+Status+Update+-+Technical+Specification

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
Apache Qpid - AMQP Messaging Implementation
Project:  http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org

[jira] Updated: (QPID-2531) Improve the qpid broker build system to automatically build OSGI modules on broker-plugins directory

[Martin Ritchie (JIRA)]

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

Martin Ritchie updated QPID-2531:
-

Status: Ready To Review  (was: In Progress)

> Improve the qpid broker build system to automatically build OSGI modules on 
> broker-plugins directory
> 
>
> Key: QPID-2531
> URL: https://issues.apache.org/jira/browse/QPID-2531
> Project: Qpid
>  Issue Type: Improvement
>Reporter: Sorin Suciu
>Assignee: Martin Ritchie
> Attachments: qpid-2531.patch
>
>
> The qpid broker ant build system could be improved to automatically build the 
> OSGI modules in the broker-plugins directory given we might have multiple 
> modules. For this, we could modify the current build.xml file from 
> broker-plugins to delegate the tasks to each individual module via a subant 
> task. Each module would have its own build.xml file (which would be pretty 
> much generic). 
> So the task of adding a new OSGI module would involve: 
> - creating a new directory (eg myplugin) having a generic build.xml and the 
> code in src subdir
> - adding the new directory to the subant task so it will be build
> - updating the build.deps file

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
Apache Qpid - AMQP Messaging Implementation
Project:  http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org

[jira] Resolved: (QPID-2531) Improve the qpid broker build system to automatically build OSGI modules on broker-plugins directory

[Martin Ritchie (JIRA)]

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

Martin Ritchie resolved QPID-2531.
--

Resolution: Fixed

> Improve the qpid broker build system to automatically build OSGI modules on 
> broker-plugins directory
> 
>
> Key: QPID-2531
> URL: https://issues.apache.org/jira/browse/QPID-2531
> Project: Qpid
>  Issue Type: Improvement
>Reporter: Sorin Suciu
>Assignee: Martin Ritchie
> Attachments: qpid-2531.patch
>
>
> The qpid broker ant build system could be improved to automatically build the 
> OSGI modules in the broker-plugins directory given we might have multiple 
> modules. For this, we could modify the current build.xml file from 
> broker-plugins to delegate the tasks to each individual module via a subant 
> task. Each module would have its own build.xml file (which would be pretty 
> much generic). 
> So the task of adding a new OSGI module would involve: 
> - creating a new directory (eg myplugin) having a generic build.xml and the 
> code in src subdir
> - adding the new directory to the subant task so it will be build
> - updating the build.deps file

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
Apache Qpid - AMQP Messaging Implementation
Project:  http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org

[jira] Updated: (QPID-2530) Refactor the broker-plugins directory setup to allow adding new modules

[Martin Ritchie (JIRA)]

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

Martin Ritchie updated QPID-2530:
-

Status: Ready To Review  (was: In Progress)

> Refactor the broker-plugins directory setup to allow adding new modules 
> 
>
> Key: QPID-2530
> URL: https://issues.apache.org/jira/browse/QPID-2530
> Project: Qpid
>  Issue Type: Improvement
>Reporter: Sorin Suciu
>Assignee: Martin Ritchie
> Fix For: 0.7
>
> Attachments: build.xml, extras.tgz
>
>
> The broker-plugins is currently having only one module (DiagnosticExchange 
> and TestExchange). We should have a directory for each module building as  a 
> separate jar. This would allow adding a new module to be just a matter of 
> creating a new directory and adding it to the build system, We should move 
> the content of the src directory to its own plugin directory and adjust the 
> build system accordingly. Suggested layout: 
> broker-plugins
> ---> build.xml
> ---> extras  (OSGI-Plugin) 
> ---> my_plugin1 (OSGI-Plugin)
> ---> my_plugin2 (OSGI-Plugin)
>  etc
> Please perform the following: on java/broker-plugins folder: 
> - delete the src folder and untar the tarball attached
> - remove the build.xml and add the attached build.xml
> - apply QPID-2502 to fix the PluginManager.java issue with security tracker
> - apply QPID-2513 
> - apply QPID-2531 to update the build.deps and main build.xml

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
Apache Qpid - AMQP Messaging Implementation
Project:  http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org

Re: Versioning DocBook and API docs on the Qpid Web Site

[Jonathan Robie]

Hi Marnie,

I think ./devel always refers to whatever matches what the most recent 
docs in svn, ./stable always refers to the latest released docs (which 
will have even numbers), and we only create ./0.6, ./0.8, etc. when we 
do a release. So you're right, we won't see odd version numbers here.


Does that make sense?

Jonathan

On 04/23/2010 11:28 AM, Marnie McCormack wrote:

Hi Jonathan,

I missed the debate about versions, but we'll only ref 0.6 then 0.8 in doc
is that right ? So if we're working on something with a 0.7 version on trunk
when its released the docs should ref 0.8 but the devel links will go to 0.7
docs ?

Sorry if I have the stick by the wrong end (not that the numbers are
confusing :-)

I think whats you're proposing makes sense, though I'm not sure how best to
ref back and forward as we make changes but using absolute refs avoids
confusion or inadvertant links to non-relevant pages.

Thanks,
Marnie

On Fri, Apr 23, 2010 at 4:20 PM, Jonathan Robie
wrote:

   

I'm getting ready to post the DocBook docs on the Qpid web site along with
API docs (looks like early next week at this point).

I want to make sure we have a good plan to handle versions and links among
documents. I think a file structure like this might work well:

Versions

http://qpid.apache.org/doc/
contains all docs

http://qpid.apache.org/devel/
symlink to the devel version of the documentation

http://qpid.apache.org/stable/
symlink to the docs for the latest release

http://qpid.apache.org/doc/ 0.6/
docs for a specific version

Subdirectories

http://qpid.apache.org/doc/stable/book/
Current Wiki, converted to book. We may eventually subdivide this into
different guides, e.g. http://qpid.apache.org/doc/stable/book/programming,
or http://qpid.apache.org/doc/stable/book/broker-java.

http://qpid.apache.org/doc/stable/api/cpp
C++ API reference, generated by Doxygen

http://qpid.apache.org/doc/stable/api/cpp
Python API reference, generated by ePydoc

Links among Documents

Links should be absolute links to the current version of the documentation.
For instance, a link from
http://qpid.apache.org/doc/0.6/book/qpid-book.html to the C++ API docs
should point to http://qpid.apache.org/doc/0.6/api/cpp

Tracking changes in the text

We should endeaver to use phrases like "since 0.6" to identify new features
and changes, so the latest documentation shows what has changed.


Does this makes sense? Once we start using a given structure, it becomes
harder to change, so I want to get agreement on this up front.

Jonathan

-
Apache Qpid - AMQP Messaging Implementation
Project:  http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org


 
   



-
Apache Qpid - AMQP Messaging Implementation
Project:  http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org

[jira] Commented: (QPID-2537) Add QMF/JMX administration of ACLs

[Rajith Attapattu (JIRA)]

[ 
https://issues.apache.org/jira/browse/QPID-2537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12860285#action_12860285
 ] 

Rajith Attapattu commented on QPID-2537:


Here is a very brief of summary of what Ted Ross (QMF guy) and I had discussed 
in the past.
Ted please correct/add anything if needed.

1.  The broker is bootstraped with a file based ACL. 
 This will control who can and cannot use QMF to manage/control ACL. 

2.  The ACL module will contain a QMF agent which will handle the requests.

3.  The QMF Agent will support (not an exhaustive list) the following

 1.  Add/Remove/Modify users and groups
 2.  Add/Remove/Modify permissions
 3.  Generate alerts for illegal accessing 

As for JMX we could probably leverage the QMF <==> JMX bridge written by Andrea.

> Add QMF/JMX administration of ACLs
> --
>
> Key: QPID-2537
> URL: https://issues.apache.org/jira/browse/QPID-2537
> Project: Qpid
>  Issue Type: Sub-task
>  Components: Java Broker, Java Management : JMX Interface, Java 
> Management : QMF
>Reporter: Andrew Kennedy
> Fix For: 0.7
>
>


-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
Apache Qpid - AMQP Messaging Implementation
Project:  http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org

[jira] Resolved: (QPID-1878) JMX CLI throws NumberFormatException while attempting to undertake various queue commands

[Marnie McCormack (JIRA)]

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

Marnie McCormack resolved QPID-1878.


Resolution: Fixed

Change to use Number and attr name looks fine thx

> JMX CLI throws NumberFormatException while attempting to undertake various 
> queue commands
> -
>
> Key: QPID-1878
> URL: https://issues.apache.org/jira/browse/QPID-1878
> Project: Qpid
>  Issue Type: Bug
>  Components: Java Management : CLI Tool
>Affects Versions: 0.5
> Environment: trunk broker (r778914), 0.5 JMX CLI
>Reporter: Robbie Gemmell
>Assignee: Robbie Gemmell
> Fix For: 0.6
>
>
> While attempting to view messages on a queue, the CLi is unable to determine 
> the message count for the queue following 2 NumberFormatExceptions and then 
> incorrectly states the given argument is invalid. This appears to be because 
> instead of the message count, it is retrieving one of the boolean attributes 
> (durability i believe based on output of list -o queues and comparison 
> between the source code).
> This also affects other commands, such as viewing the content of a message, 
> although this actually completes following the exception as it only related 
> to a check for the queue being empty. The delete command looks like it will 
> be similarly affected, although should the user not specify a number of 
> messages to delete from the top of the queue then they should successfully be 
> given the option to delete all messages. 
> qpid-admin-$ queue view -n message_queue -t 5
> java.lang.NumberFormatException: For input string: "false"
>   at 
> java.lang.NumberFormatException.forInputString(NumberFormatException.java:48)
>   at java.lang.Integer.parseInt(Integer.java:447)
>   at java.lang.Integer.(Integer.java:620)
>   at 
> org.apache.qpid.commands.objects.QueueObject.getmessagecount(QueueObject.java:71)
>   at 
> org.apache.qpid.commands.Commandview.viewmessages(Commandview.java:73)
>   at org.apache.qpid.commands.Commandview.execute(Commandview.java:216)
>   at 
> org.apache.qpid.CommandExecutionEngine.runcommand(CommandExecutionEngine.java:69)
>   at 
> org.apache.qpid.CommandLineInterpreter.main(CommandLineInterpreter.java:170)
> java.lang.NumberFormatException: For input string: "false"
>   at 
> java.lang.NumberFormatException.forInputString(NumberFormatException.java:48)
>   at java.lang.Integer.parseInt(Integer.java:447)
>   at java.lang.Integer.(Integer.java:620)
>   at 
> org.apache.qpid.commands.objects.QueueObject.getmessagecount(QueueObject.java:71)
>   at 
> org.apache.qpid.commands.Commandview.viewmessages(Commandview.java:81)
>   at org.apache.qpid.commands.Commandview.execute(Commandview.java:216)
>   at 
> org.apache.qpid.CommandExecutionEngine.runcommand(CommandExecutionEngine.java:69)
>   at 
> org.apache.qpid.CommandLineInterpreter.main(CommandLineInterpreter.java:170)
> Given number is Greater than the Queue Depth
> qpid-admin-$ queue viewcontent -n message_queue -id 120
> java.lang.NumberFormatException: For input string: "false"
>   at 
> java.lang.NumberFormatException.forInputString(NumberFormatException.java:48)
>   at java.lang.Integer.parseInt(Integer.java:447)
>   at java.lang.Integer.(Integer.java:620)
>   at 
> org.apache.qpid.commands.objects.QueueObject.getmessagecount(QueueObject.java:71)
>   at 
> org.apache.qpid.commands.Commandviewcontent.viewcontent(Commandviewcontent.java:74)
>   at 
> org.apache.qpid.commands.Commandviewcontent.execute(Commandviewcontent.java:212)
>   at 
> org.apache.qpid.CommandExecutionEngine.runcommand(CommandExecutionEngine.java:69)
>   at 
> org.apache.qpid.CommandLineInterpreter.main(CommandLineInterpreter.java:170)
>   AMQ MessageId|Content|   Encoding|   MimeType|
> 120| Message 19|  UTF-8| text/plain|

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
Apache Qpid - AMQP Messaging Implementation
Project:  http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org

[jira] Created: (QPID-2546) QMF: ruby and python bindings need event support

[Ken Giusti (JIRA)]

QMF: ruby and python bindings need event support


 Key: QPID-2546
 URL: https://issues.apache.org/jira/browse/QPID-2546
 Project: Qpid
  Issue Type: Bug
  Components: Qpid Managment Framework
Reporter: Ken Giusti


Missing functionality.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
Apache Qpid - AMQP Messaging Implementation
Project:  http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org

[jira] Assigned: (QPID-2546) QMF: ruby and python bindings need event support

[Ken Giusti (JIRA)]

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

Ken Giusti reassigned QPID-2546:


Assignee: Ken Giusti

> QMF: ruby and python bindings need event support
> 
>
> Key: QPID-2546
> URL: https://issues.apache.org/jira/browse/QPID-2546
> Project: Qpid
>  Issue Type: Bug
>  Components: Qpid Managment Framework
>Reporter: Ken Giusti
>Assignee: Ken Giusti
>
> Missing functionality.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
Apache Qpid - AMQP Messaging Implementation
Project:  http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org

Re: Versioning DocBook and API docs on the Qpid Web Site

[Rajith Attapattu]

I would keep it simple for now.

We should post the current docs as work-in-progress.
Then when we release 0.7 we can then have our first set of version
controlled docs.
For all previous releases we should ask them to refer to the wiki docs.

We shouldn't delete the old wiki docs.
Rather in bold letters we should put at the top saying that these docs
are deprecated and *may* only be relevant for versions < 0.7 or
something to that extent :)

How does that sound?

Rajith

On Fri, Apr 23, 2010 at 11:20 AM, Jonathan Robie
 wrote:
> I'm getting ready to post the DocBook docs on the Qpid web site along with
> API docs (looks like early next week at this point).
>
> I want to make sure we have a good plan to handle versions and links among
> documents. I think a file structure like this might work well:
>
> Versions
>
> http://qpid.apache.org/doc/
> contains all docs
>
> http://qpid.apache.org/devel/
> symlink to the devel version of the documentation
>
> http://qpid.apache.org/stable/
> symlink to the docs for the latest release
>
> http://qpid.apache.org/doc/ 0.6/
> docs for a specific version
>
> Subdirectories
>
> http://qpid.apache.org/doc/stable/book/
> Current Wiki, converted to book. We may eventually subdivide this into
> different guides, e.g. http://qpid.apache.org/doc/stable/book/programming,
> or http://qpid.apache.org/doc/stable/book/broker-java.
>
> http://qpid.apache.org/doc/stable/api/cpp
> C++ API reference, generated by Doxygen
>
> http://qpid.apache.org/doc/stable/api/cpp
> Python API reference, generated by ePydoc
>
> Links among Documents
>
> Links should be absolute links to the current version of the documentation.
> For instance, a link from
> http://qpid.apache.org/doc/0.6/book/qpid-book.html to the C++ API docs
> should point to http://qpid.apache.org/doc/0.6/api/cpp
>
> Tracking changes in the text
>
> We should endeaver to use phrases like "since 0.6" to identify new features
> and changes, so the latest documentation shows what has changed.
>
>
> Does this makes sense? Once we start using a given structure, it becomes
> harder to change, so I want to get agreement on this up front.
>
> Jonathan
>
> -
> Apache Qpid - AMQP Messaging Implementation
> Project:      http://qpid.apache.org
> Use/Interact: mailto:dev-subscr...@qpid.apache.org
>
>



-- 
Regards,

Rajith Attapattu
Red Hat
http://rajith.2rlabs.com/

-
Apache Qpid - AMQP Messaging Implementation
Project:  http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org

[jira] Resolved: (QPID-2268) the reported attributes for queue objects change between brokers

[Marnie McCormack (JIRA)]

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

Marnie McCormack resolved QPID-2268.


Resolution: Fixed

Change to use attr names ok

> the reported attributes for queue objects change between brokers
> 
>
> Key: QPID-2268
> URL: https://issues.apache.org/jira/browse/QPID-2268
> Project: Qpid
>  Issue Type: Bug
>  Components: Java Management : CLI Tool
>Affects Versions: 0.5
>Reporter: Robbie Gemmell
>Assignee: Robbie Gemmell
> Fix For: 0.6
>
>
> The CLI reports a selection of the attributes for the Queue objects. 
> Originally this was Name, Durable,ActiveConsumerCount,MessageCount, and 
> RecievedMesageCount. However, the reported attributes differ on newer brokers 
> due to identification taking place using position within the returned data, 
> which has subsequently changed.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
Apache Qpid - AMQP Messaging Implementation
Project:  http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org

[jira] Commented: (QPID-2539) Update ACL file syntax to be clearer and add extra operations

[Rajith Attapattu (JIRA)]

[ 
https://issues.apache.org/jira/browse/QPID-2539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12860279#action_12860279
 ] 

Rajith Attapattu commented on QPID-2539:


Andrew, have you had a chance to  look at http://qpid.apache.org/acl.html ?
If you have, could you please explain what improvements you would like to make ?


> Update ACL file syntax to be clearer and add extra operations
> -
>
> Key: QPID-2539
> URL: https://issues.apache.org/jira/browse/QPID-2539
> Project: Qpid
>  Issue Type: Sub-task
>  Components: Java Broker
>Reporter: Andrew Kennedy
> Fix For: 0.7
>
>


-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
Apache Qpid - AMQP Messaging Implementation
Project:  http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org

[jira] Commented: (QPID-2538) Add XML configuration syntax for ACLs in Java broker

[Rajith Attapattu (JIRA)]

[ 
https://issues.apache.org/jira/browse/QPID-2538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12860277#action_12860277
 ] 

Rajith Attapattu commented on QPID-2538:


I'd question the value of having an XML based format.
Is there a specific reason for this?

> Add XML configuration syntax for ACLs in Java broker
> 
>
> Key: QPID-2538
> URL: https://issues.apache.org/jira/browse/QPID-2538
> Project: Qpid
>  Issue Type: Sub-task
>  Components: Java Broker
>Reporter: Andrew Kennedy
> Fix For: 0.7
>
>


-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
Apache Qpid - AMQP Messaging Implementation
Project:  http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org

Re: Versioning DocBook and API docs on the Qpid Web Site

[Marnie McCormack]

Hi Jonathan,

I missed the debate about versions, but we'll only ref 0.6 then 0.8 in doc
is that right ? So if we're working on something with a 0.7 version on trunk
when its released the docs should ref 0.8 but the devel links will go to 0.7
docs ?

Sorry if I have the stick by the wrong end (not that the numbers are
confusing :-)

I think whats you're proposing makes sense, though I'm not sure how best to
ref back and forward as we make changes but using absolute refs avoids
confusion or inadvertant links to non-relevant pages.

Thanks,
Marnie

On Fri, Apr 23, 2010 at 4:20 PM, Jonathan Robie
wrote:

> I'm getting ready to post the DocBook docs on the Qpid web site along with
> API docs (looks like early next week at this point).
>
> I want to make sure we have a good plan to handle versions and links among
> documents. I think a file structure like this might work well:
>
> Versions
>
> http://qpid.apache.org/doc/
> contains all docs
>
> http://qpid.apache.org/devel/
> symlink to the devel version of the documentation
>
> http://qpid.apache.org/stable/
> symlink to the docs for the latest release
>
> http://qpid.apache.org/doc/ 0.6/
> docs for a specific version
>
> Subdirectories
>
> http://qpid.apache.org/doc/stable/book/
> Current Wiki, converted to book. We may eventually subdivide this into
> different guides, e.g. http://qpid.apache.org/doc/stable/book/programming,
> or http://qpid.apache.org/doc/stable/book/broker-java.
>
> http://qpid.apache.org/doc/stable/api/cpp
> C++ API reference, generated by Doxygen
>
> http://qpid.apache.org/doc/stable/api/cpp
> Python API reference, generated by ePydoc
>
> Links among Documents
>
> Links should be absolute links to the current version of the documentation.
> For instance, a link from
> http://qpid.apache.org/doc/0.6/book/qpid-book.html to the C++ API docs
> should point to http://qpid.apache.org/doc/0.6/api/cpp
>
> Tracking changes in the text
>
> We should endeaver to use phrases like "since 0.6" to identify new features
> and changes, so the latest documentation shows what has changed.
>
>
> Does this makes sense? Once we start using a given structure, it becomes
> harder to change, so I want to get agreement on this up front.
>
> Jonathan
>
> -
> Apache Qpid - AMQP Messaging Implementation
> Project:  http://qpid.apache.org
> Use/Interact: mailto:dev-subscr...@qpid.apache.org
>
>

[jira] Resolved: (QPID-2269) the specified queue is not used when trying to view message content

[Marnie McCormack (JIRA)]

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

Marnie McCormack resolved QPID-2269.


Resolution: Fixed

Removal of private instance vars looks good to me

> the specified queue is not used when trying to view message content
> ---
>
> Key: QPID-2269
> URL: https://issues.apache.org/jira/browse/QPID-2269
> Project: Qpid
>  Issue Type: Bug
>  Components: Java Management : CLI Tool
>Affects Versions: 0.5
>Reporter: Robbie Gemmell
>Assignee: Robbie Gemmell
> Fix For: 0.6
>
>
> When attemtping to view message content, the CLI throws an exception 
> indicating the message did no exist. Closer inspection shows this is because 
> of an invocation exception because the wrong queue MBean was operated upon.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
Apache Qpid - AMQP Messaging Implementation
Project:  http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org

Re: JavaBroker v2 ACLs (QPID-2476)

[Rajith Attapattu]

Andrew,

Sorry about the late reply. I've been a bit swamped the past 2 weeks.

On Fri, Apr 16, 2010 at 5:29 AM, Andrew Kennedy
 wrote:
> hi.
>
> i am going to be implementing QPID-2476, version 2 access control
> lists for the Java broker. these are my current thoughts and i would
> appreciate any ideas or caveats, but please bear in mind that i am new
> to the Qpid code-base, and may be going over material that has already
> been discussed or conclusions already reached, although i couldn't
> find much in the list archives...

Excellent and welcome aboard!
Going forward we need to ensure that both brokers support a similar feature set.
There are people who are already attempting to use both C++ and Java
brokers in a single federated set up. So having similar behaviour and
features are crucial for operational folks for maintaining and
administering the brokers.

> at the moment i am going to simply port the C++ file format to Java,
> and access it from the existing XML configuration via a link to a
> separate file, but i think the ACLs should also be expressible as a
> pure XML configuration, to be documented later.

I think for all intents and purposes we should only have a single file format.
I think we debated this point and agreed on the current file format.
It's not just the c++ file format, but the acl file format for Qpid as well.

Also I'd question the value of having an XML based format.
Is there a specific reason for this?

> additionally, the C++
> file format could be improved, by being stricter with the processing
> of continuations and comment lines,

In general I'd be keen to hear any thoughts on how we could improve.
Could you explain the above point a bit more?

> and i see no reason for the tokens
> to be case sensitive. quoting of identifiers would be a useful
> addition, allowing syntax such as:
>
>    ACL "a...@iterator.co.uk" ALLOW \
>        create queue name="adk.*" routingKey="adk" selector="*"
>
By token you mean the keywords like action, object and property names?
If so I am fine with it.

> perhaps also splitting group configuration and ACL configuration into
> separate files, since these are obviously quite different things, and
> it is foreseeable that groups would be desirable to load via an
> external authentication or directory service.
>

This is one of the key things I want to tackle on the C++ side as well.
There have been requests for this from several users.
Specifying the groups in the ACL file is more a convenience than anything else.
And we should allow to plug in a 3rd party mechanism in which the ACL
file will not contain any group information.

Also ACL file is just one way of expressing rules.
User should be able to provision acl rules dynamically via QMF.
Ted and I have had some discussions about this in the past and I will
comment in detail on the JIRA you opened.
There is another person who tried to integrate the ACL module with SELinux.

> a proper description of the meaning of ACL rules is also required,
> since it is not always clear what the intent of rules and ordering
> might be. the only documentation i could find is here:
>
>    http://qpid.apache.org/acl.html#ACL-userguide
>
Check this out
http://qpid.apache.org/acl.html

Also jonathan and I are working on ACL documentation.
I am sure he will contribute that soon.

> i will try and use the same error text as the C++ parser, but these
> should probably be standardised somewhere (again, i may just not have
> been able to find this). also, error recovery is not very well defined
> - i would be interested to know what people's position is on broker
> behavior with invalid or badly-formed ACL configurations. there are a
> few possibilities:
>
>    1. exit the broker immediately with an exception.
This is what we do if you try to start up a broker with an invalid ACL file.

We also allow to reload an ACL file using QMF.
Now in this case if the new ACL file is invalid,
   1. The management method will return the error text.
   2. the old ACL data will continue to work

>    2. record the error and start the broker with a best effort at
> parsing the file, ignoring the rule (and possibly even all following
> rules).
>    3. record the error and start the broker with an empty ACL
> configuration that ALLOWS all access.
>    4. record the error and start the broker with an empty ACL
> configuration that DENIES all access.
>
> i believe 2 is desirable, but 1 is easiest. depending on requirements,
> 3 or 4 could be configurable behaviours after errors.
>
> as regards the mechanics of the implementation, i will use the
> existing plugin architecture, and eventually a proper OSGi plugin
> would be desirable, particularly when interacting with other plugins
> for SSO, kerberos et al.
The c++ broker also uses it's own pluggin mechanism.

>  i will also change the actual access checking
> from inside the protocol frame handlers to inside the broker entities
> themselves.
This what the c++ side do as well.

> this wi

[jira] Assigned: (QPID-2529) Update the Felix OSGI framework to a recent release

[Martin Ritchie (JIRA)]

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

Martin Ritchie reassigned QPID-2529:


Assignee: (was: Martin Ritchie)

> Update the Felix OSGI framework to a recent release
> ---
>
> Key: QPID-2529
> URL: https://issues.apache.org/jira/browse/QPID-2529
> Project: Qpid
>  Issue Type: Improvement
>  Components: Java Broker
>Affects Versions: 0.6
>Reporter: Sorin Suciu
>Priority: Minor
> Fix For: 0.7
>
>
> The felix framework currently used in qpid is version 1.0.0, an update to a 
> later version would provide new features as well as bugfixes. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
Apache Qpid - AMQP Messaging Implementation
Project:  http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org

[jira] Created: (QPID-2545) Improve PluginTest.java in order to test new OSGI plugins

[Sorin Suciu (JIRA)]

Improve PluginTest.java in order to test new OSGI plugins
-

 Key: QPID-2545
 URL: https://issues.apache.org/jira/browse/QPID-2545
 Project: Qpid
  Issue Type: Improvement
Reporter: Sorin Suciu


The current PluginTest.java is testing only the TestExchangePlugin, this can be 
improved so:
- it can easily test other plugins
- tests the correct loading/unloading of the plugins

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
Apache Qpid - AMQP Messaging Implementation
Project:  http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org

[jira] Commented: (QPID-2199) Federation connections initiated from windows brokers stuck in "connecting" state

[Kerry Bonin (JIRA)]

[ 
https://issues.apache.org/jira/browse/QPID-2199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12860270#action_12860270
 ] 

Kerry Bonin commented on QPID-2199:
---

I'm looking at ways to fix this...

The cleanest fix would appear to be to generalize the Posix version so it runs 
on Windows.  The main problem I've seen so far with that approach is the Posix 
code uses thread local storage, which is unusable on Windows (if the code could 
run in a DLL loaded with LoadLibrary on OS's before Vista or Server 2008, see 
http://msdn2.microsoft.com/en-us/library/2s9wt68x.aspx for details.)  Simplest 
way to address that would seem to add these variables to the AsynchIO class and 
lock before use.  For now I'll copy the Posix version over the Windows version 
and see about making the changes there.  Comments appreciated!

Kerry

> Federation connections initiated from windows brokers stuck in "connecting" 
> state
> -
>
> Key: QPID-2199
> URL: https://issues.apache.org/jira/browse/QPID-2199
> Project: Qpid
>  Issue Type: Bug
>  Components: C++ Broker
>Affects Versions: 0.5
> Environment: Windows XP, qpid 0.5 from .msi installer, hosts scengsrv 
> and jlaughlin, qpidbroker.exe running under cmd.exe, other tools running 
> under cygwin
> Ubuntu Hardy, qpid 0.5 compiled from source with unused return value patches, 
> host santa-anna
>Reporter: Jeff Laughlin
> Attachments: linux.cap, linux.out, windows.cap, windows.out
>
>
> My Windows broker can't establish federation link to other brokers running on 
> windows or linux; links remain in "connecting" state forever. Packet sniffer 
> reveals strange and inconsistent things. Linux broker can successfully 
> establish links to windows brokers, however. Python client tools seems to 
> work fine with both windows and linux brokers, from both cygwin python and 
> linux python.
> Here's a terminal session transcript that illustrates this behavior. I'm 
> starting with two fresh instances of qpid on two different windows hosts, 
> jlaughlin and scengsrv. Both have been configured with a durable alarms 
> exchange and durable alarmd queue that have been bound together.
> First I try to create the link in push mode, so qpid-route is commanding 
> jlaughlin (the localhost) to establish a link to scengsrv
> jlaugh...@jlaughlin ~/Downloads/qpid-0.5/python/commands
> $ python2.5 qpid-route queue add scengsrv jlaughlin alarms alarmd --ack 1 
> --src-local
> After a  moment I check my links
> jlaugh...@jlaughlin ~/Downloads/qpid-0.5/python/commands
> $ python2.5 qpid-route link list
> HostPortTransport Durable  State Last Error
> =
> scengsrv5672tcp  N Connecting
> Hm it's still connecting. Wait a few moments.
> jlaugh...@jlaughlin ~/Downloads/qpid-0.5/python/commands
> $ python2.5 qpid-route link list
> HostPortTransport Durable  State Last Error
> =
> scengsrv5672tcp  N Connecting
> Still connecting. Darn. Lets try going the other way, commanding scengsrv to 
> link to jlaughlin.
> jlaugh...@jlaughlin ~/Downloads/qpid-0.5/python/commands
> $ python2.5 qpid-route queue add scengsrv jlaughlin alarms alarmd --ack 1 
>
> jlaugh...@jlaughlin ~/Downloads/qpid-0.5/python/commands
> $ python2.5 qpid-route link list scengsrv
> HostPortTransport Durable  State Last Error
> =
> jlaughlin   5672tcp  N Connecting
> Still no good.
> Now lets try commanding jlaughlin to connect to my linux box, santa-anna
> jlaugh...@jlaughlin ~/Downloads/qpid-0.5/python/commands
> $ python2.5 qpid-route queue add santa-anna jlaughlin alarms alarmd --ack 1 
> --src-local
> jlaugh...@jlaughlin ~/Downloads/qpid-0.5/python/commands
> $ python2.5 qpid-route link list 
> HostPortTransport Durable  State Last Error
> =
> santa-anna  5672tcp  N Connecting
> jlaugh...@jlaughlin ~/Downloads/qpid-0.5/python/commands
> $ python2.5 qpid-route link list 
> HostPortTransport Durable  State Last Error
> =
> santa-anna  5672tcp  N Connecting
> Negative, ghost rider, the pattern is full.
> Enough of this, lets command the linux host, santa-anna, to connect to my 
> jlaughlin windows host:
> jlaugh...@jlaug

[jira] Resolved: (QPID-2233) provide meaningful error messages when failing to complete the JMX connection

[Marnie McCormack (JIRA)]

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

Marnie McCormack resolved QPID-2233.


Resolution: Fixed

Using exception details looks better to me

> provide meaningful error messages when failing to complete the JMX connection
> -
>
> Key: QPID-2233
> URL: https://issues.apache.org/jira/browse/QPID-2233
> Project: Qpid
>  Issue Type: Improvement
>  Components: Java Management : JMX Console
>Affects Versions: 0.5
>Reporter: Robbie Gemmell
>Assignee: Robbie Gemmell
> Fix For: 0.6
>
>
> Provide meaningful error messages when failing to complete the JMX 
> connection. Currently the console uses a couple of generic error messages 
> during connection failure. Instead, the exceptions raised should be used to 
> provide more useful error messages to the user to help diagnose connection 
> issues, eg when a connection times out, or fails due to there being no route 
> to the host, etc.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
Apache Qpid - AMQP Messaging Implementation
Project:  http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org

Versioning DocBook and API docs on the Qpid Web Site

[Jonathan Robie]

I'm getting ready to post the DocBook docs on the Qpid web site along 
with API docs (looks like early next week at this point).


I want to make sure we have a good plan to handle versions and links 
among documents. I think a file structure like this might work well:


Versions

http://qpid.apache.org/doc/
contains all docs

http://qpid.apache.org/devel/
symlink to the devel version of the documentation

http://qpid.apache.org/stable/
symlink to the docs for the latest release

http://qpid.apache.org/doc/ 0.6/
docs for a specific version

Subdirectories

http://qpid.apache.org/doc/stable/book/
Current Wiki, converted to book. We may eventually subdivide this into 
different guides, e.g. 
http://qpid.apache.org/doc/stable/book/programming, or 
http://qpid.apache.org/doc/stable/book/broker-java.


http://qpid.apache.org/doc/stable/api/cpp
C++ API reference, generated by Doxygen

http://qpid.apache.org/doc/stable/api/cpp
Python API reference, generated by ePydoc

Links among Documents

Links should be absolute links to the current version of the 
documentation. For instance, a link from
http://qpid.apache.org/doc/0.6/book/qpid-book.html to the C++ API docs 
should point to http://qpid.apache.org/doc/0.6/api/cpp


Tracking changes in the text

We should endeaver to use phrases like "since 0.6" to identify new 
features and changes, so the latest documentation shows what has changed.



Does this makes sense? Once we start using a given structure, it becomes 
harder to change, so I want to get agreement on this up front.


Jonathan

-
Apache Qpid - AMQP Messaging Implementation
Project:  http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org

[jira] Resolved: (QPID-2137) StringIndexOutOfBounds when formating Connection Message during failed systest run.

[Marnie McCormack (JIRA)]

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

Marnie McCormack resolved QPID-2137.


Resolution: Fixed

> StringIndexOutOfBounds when formating Connection Message during failed 
> systest run.
> ---
>
> Key: QPID-2137
> URL: https://issues.apache.org/jira/browse/QPID-2137
> Project: Qpid
>  Issue Type: Bug
>  Components: Java Tests
>Reporter: Martin Ritchie
>Assignee: Martin Ritchie
>Priority: Blocker
> Fix For: 0.7, 0.6
>
> Attachments: QPID-2137-LogMessages.vm.Update.patch, 
> TEST-org.apache.qpid.test.unit.ack.AcknowledgeAfterFailoverOnMessageTest.testDupsOk.out
>
>
> This problem occured during a run of systests in the 
> AcknowledgeAfterFailoverOnmessageTest. The test failed with a concurrent 
> modification exception. However prior to that a StringIndexOutOfBounds during 
> client connection establishment occured
> Then shortly afterwards a NullPointerException occured and repeated a number 
> of times. 
> Most likely what occured is the failed connection open was not correclty 
> closed by mina and so the attempts to send on the socket resulted in the NPEs.
> Then the ConcurrentModException occured potentially as a result of a new 
> getConnection() being called asynchronously via the onMessage when the 
> close() was being called.
> Dispatcher-Channel-1 2009-10-12 16:25:36,694 ERROR 
> [qpid.server.protocol.AMQPFastProtocolHandler] Exception caught 
> inanonymous(17670761)(?, closing session explictly: 
> java.lang.StringIndexOutOfBoundsException: String index out of range: 37
> java.lang.StringIndexOutOfBoundsException: String index out of range: 37
>   at java.lang.String.substring(String.java:1934)
>   at java.text.MessageFormat.subformat(MessageFormat.java:1208)
>   at java.text.MessageFormat.format(MessageFormat.java:836)
>   at java.text.Format.format(Format.java:140)
>   at 
> org.apache.qpid.server.logging.messages.ConnectionMessages.CON_1001(ConnectionMessages.java:141)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
Apache Qpid - AMQP Messaging Implementation
Project:  http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org

[jira] Commented: (QPID-2137) StringIndexOutOfBounds when formating Connection Message during failed systest run.

[Marnie McCormack (JIRA)]

[ 
https://issues.apache.org/jira/browse/QPID-2137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12860266#action_12860266
 ] 

Marnie McCormack commented on QPID-2137:


LogMesssageTest.testSimultaneousLogging has a superfluous int LOG_COUNT. Aside 
from that commits look ok afaics thx.


> StringIndexOutOfBounds when formating Connection Message during failed 
> systest run.
> ---
>
> Key: QPID-2137
> URL: https://issues.apache.org/jira/browse/QPID-2137
> Project: Qpid
>  Issue Type: Bug
>  Components: Java Tests
>Reporter: Martin Ritchie
>Assignee: Martin Ritchie
>Priority: Blocker
> Fix For: 0.6, 0.7
>
> Attachments: QPID-2137-LogMessages.vm.Update.patch, 
> TEST-org.apache.qpid.test.unit.ack.AcknowledgeAfterFailoverOnMessageTest.testDupsOk.out
>
>
> This problem occured during a run of systests in the 
> AcknowledgeAfterFailoverOnmessageTest. The test failed with a concurrent 
> modification exception. However prior to that a StringIndexOutOfBounds during 
> client connection establishment occured
> Then shortly afterwards a NullPointerException occured and repeated a number 
> of times. 
> Most likely what occured is the failed connection open was not correclty 
> closed by mina and so the attempts to send on the socket resulted in the NPEs.
> Then the ConcurrentModException occured potentially as a result of a new 
> getConnection() being called asynchronously via the onMessage when the 
> close() was being called.
> Dispatcher-Channel-1 2009-10-12 16:25:36,694 ERROR 
> [qpid.server.protocol.AMQPFastProtocolHandler] Exception caught 
> inanonymous(17670761)(?, closing session explictly: 
> java.lang.StringIndexOutOfBoundsException: String index out of range: 37
> java.lang.StringIndexOutOfBoundsException: String index out of range: 37
>   at java.lang.String.substring(String.java:1934)
>   at java.text.MessageFormat.subformat(MessageFormat.java:1208)
>   at java.text.MessageFormat.format(MessageFormat.java:836)
>   at java.text.Format.format(Format.java:140)
>   at 
> org.apache.qpid.server.logging.messages.ConnectionMessages.CON_1001(ConnectionMessages.java:141)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
Apache Qpid - AMQP Messaging Implementation
Project:  http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org

[jira] Updated: (QPID-2513) Expose the ServerConfiguration as an OSGI service for use in plugins

[Martin Ritchie (JIRA)]

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

Martin Ritchie updated QPID-2513:
-

Status: Ready To Review  (was: In Progress)

> Expose the ServerConfiguration as an OSGI service for use in plugins
> 
>
> Key: QPID-2513
> URL: https://issues.apache.org/jira/browse/QPID-2513
> Project: Qpid
>  Issue Type: Improvement
>Affects Versions: 0.5, 0.6, 0.7
>Reporter: Sorin Suciu
>Assignee: Martin Ritchie
> Fix For: 0.7
>
> Attachments: qpid-2513.patch
>
>
> The ServerConfiguration could be used by OSGI plugins to query configuration 
> parameters. For this, a service has to be registered with the current OSGI 
> framework (currently Apache Felix). 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
Apache Qpid - AMQP Messaging Implementation
Project:  http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org

Re: JavaBroker v2 ACLs (QPID-2476)

[Marnie McCormack]

On Fri, Apr 16, 2010 at 10:29 AM, Andrew Kennedy <
andrewinternatio...@gmail.com> wrote:

> hi.
>
> i am going to be implementing QPID-2476, version 2 access control
> lists for the Java broker. these are my current thoughts and i would
> appreciate any ideas or caveats, but please bear in mind that i am new
> to the Qpid code-base, and may be going over material that has already
> been discussed or conclusions already reached, although i couldn't
> find much in the list archives...
>
> at the moment i am going to simply port the C++ file format to Java,
> and access it from the existing XML configuration via a link to a
> separate file, but i think the ACLs should also be expressible as a
> pure XML configuration, to be documented later. additionally, the C++
> file format could be improved, by being stricter with the processing
> of continuations and comment lines, and i see no reason for the tokens
> to be case sensitive. quoting of identifiers would be a useful
> addition, allowing syntax such as:
>
>ACL "a...@iterator.co.uk" ALLOW \
>create queue name="adk.*" routingKey="adk" selector="*"
>
> perhaps also splitting group configuration and ACL configuration into
> separate files, since these are obviously quite different things, and
> it is foreseeable that groups would be desirable to load via an
> external authentication or directory service.
>
> I think splitting out groups and ACL from the one file would be a good
thing, I don't see why we'd maintain them in the same place. I don't know
how the groups are used (aside from ACLs) in the C++ broker though ? Groups
would often be anticipated to come from another source, ideally, to negate
the need to maintain multiple user credentials.


> a proper description of the meaning of ACL rules is also required,
> since it is not always clear what the intent of rules and ordering
> might be. the only documentation i could find is here:
>
>http://qpid.apache.org/acl.html#ACL-userguide
>
Be good know what the set of use cases we support is - I couldn't spot that
?


> i will try and use the same error text as the C++ parser, but these
> should probably be standardised somewhere (again, i may just not have
> been able to find this).


Can you doc the error codes to be used on the JIRA pls and I'll take a look
? Thx.


> also, error recovery is not very well defined
> - i would be interested to know what people's position is on broker
> behavior with invalid or badly-formed ACL configurations. there are a
> few possibilities:
>
>1. exit the broker immediately with an exception.
>

1. definitely best - they can after all opt to have no ACLs if they like,
but invalid ACLs are probably always a hard fail case.


>2. record the error and start the broker with a best effort at
> parsing the file, ignoring the rule (and possibly even all following
> rules).
>3. record the error and start the broker with an empty ACL
> configuration that ALLOWS all access.
>4. record the error and start the broker with an empty ACL
> configuration that DENIES all access.
>
> i believe 2 is desirable, but 1 is easiest. depending on requirements,
> 3 or 4 could be configurable behaviours after errors.
>
> as regards the mechanics of the implementation, i will use the
> existing plugin architecture, and eventually a proper OSGi plugin
> would be desirable, particularly when interacting with other plugins
> for SSO, kerberos et al. i will also change the actual access checking
> from inside the protocol frame handlers to inside the broker entities
> themselves. this will allow a single set of ACLs to control the broker
> no matter how it is accessed - by AMQP client, JMS, JMX or QMF. i will
> also be adding extra objects that can have ACLs, such as the
> administration of users and logs, and will need to determine how much
> of a performance impact ACL processing incurs, particularly for
> publishing and consuming messages, and whether some form of cache
> strategy will be necessary.
>
> What access routes to the C++ broker are currently controlled from the ACLs
?


> i will be updating the QPID-2476 issue with some sub-tasks to reflect
> the text above and also adding some design documentation in due
> course, but would still appreciate any comments so far.
>
> Thanks, will take a look at the JIRA too.

Regards,
Marnie

> cheers,
> adk.
> --
> -- andrew d kennedy ? edinburgh : +44 7941 197 134 ;
>
> -
> Apache Qpid - AMQP Messaging Implementation
> Project:  http://qpid.apache.org
> Use/Interact: mailto:dev-subscr...@qpid.apache.org
>
>

[jira] Commented: (QPID-2543) Change uint to standard type

[Bruno Matos (JIRA)]

[ 
https://issues.apache.org/jira/browse/QPID-2543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12860263#action_12860263
 ] 

Bruno Matos commented on QPID-2543:
---

Can't I just replace all occurrences with 'unsigned int'? 

> Change uint to standard type
> 
>
> Key: QPID-2543
> URL: https://issues.apache.org/jira/browse/QPID-2543
> Project: Qpid
>  Issue Type: Improvement
>  Components: C++ Client
>Affects Versions: 0.7
>Reporter: Bruno Matos
> Fix For: 0.6
>
>   Original Estimate: 0.25h
>  Remaining Estimate: 0.25h
>
> I can't find uint as a standard type and it is breaking Mac OS X client 
> compilation.
> The references I found:
> broker/Broker.h:109:uint queueLimit;
> broker/Link.cpp:338:uint Link::nextChannel()
> broker/Link.h:71:uint channelCounter;
> broker/Link.h:111:uint nextChannel();
> broker/SaslAuthenticator.cpp:432:uint ssf = *(reinterpret_cast unsigned*>(value));
> client/MessageReplayTracker.cpp:27:MessageReplayTracker::MessageReplayTracker(uint
>  f) : flushInterval(f), count(0) {}
> client/MessageReplayTracker.cpp:51:void 
> MessageReplayTracker::setFlushInterval(uint f)
> client/MessageReplayTracker.cpp:56:uint 
> MessageReplayTracker::getFlushInterval()
> client/SaslFactory.cpp:331:uint ssf = *(reinterpret_cast unsigned*>(value));
> framing/SendContent.cpp:24:qpid::framing::SendContent::SendContent(FrameHandler&
>  h, uint16_t mfs, uint efc) : handler(h), 
> framing/SendContent.h:42:uint expectedFrameCount;
> framing/SendContent.h:43:uint frameCount;
> framing/SendContent.h:48:QPID_COMMON_EXTERN SendContent(FrameHandler& 
> _handler, uint16_t _maxFrameSize, uint frameCount);
> sys/Semaphore.h:30:Semaphore(uint c = 1) : count(c) {}
> sys/Semaphore.h:54:void release(uint n)
> sys/Semaphore.h:74:uint count;

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
Apache Qpid - AMQP Messaging Implementation
Project:  http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org

[jira] Resolved: (QPID-2308) durable exchange bindings are not recovered from the store following broker restart

[Marnie McCormack (JIRA)]

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

Marnie McCormack resolved QPID-2308.


Resolution: Fixed

Reviewed changes ok and confirmed with Robbie that r894443 already resolved on 
trunk so no merge required.

> durable exchange bindings are not recovered from the store following broker 
> restart
> ---
>
> Key: QPID-2308
> URL: https://issues.apache.org/jira/browse/QPID-2308
> Project: Qpid
>  Issue Type: Bug
>  Components: Java Broker
>Affects Versions: 0.5, 0.6
>Reporter: Robbie Gemmell
>Assignee: Robbie Gemmell
>Priority: Blocker
> Fix For: 0.6
>
> Attachments: QPID-2308_trunk.patch
>
>
> Durable exchange bindings are not recovered from the store following broker 
> restart. This appears to be due to workarounds put in place for QPID-2096 to 
> prevent duplicate createExchange calls being made to the store, which results 
> in exchanges not being added to the store at all and leads to failure on 
> restart to attempt recovering the bindings, which are actually in the store.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
Apache Qpid - AMQP Messaging Implementation
Project:  http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org

[jira] Commented: (QPID-2543) Change uint to standard type

[Steve Huston (JIRA)]

[ 
https://issues.apache.org/jira/browse/QPID-2543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12860256#action_12860256
 ] 

Steve Huston commented on QPID-2543:


One way to resolve this is to add an applicable branch in 
qpid/cpp/include/qpid/sys/IntegerTypes.h

> Change uint to standard type
> 
>
> Key: QPID-2543
> URL: https://issues.apache.org/jira/browse/QPID-2543
> Project: Qpid
>  Issue Type: Improvement
>  Components: C++ Client
>Affects Versions: 0.7
>Reporter: Bruno Matos
> Fix For: 0.6
>
>   Original Estimate: 0.25h
>  Remaining Estimate: 0.25h
>
> I can't find uint as a standard type and it is breaking Mac OS X client 
> compilation.
> The references I found:
> broker/Broker.h:109:uint queueLimit;
> broker/Link.cpp:338:uint Link::nextChannel()
> broker/Link.h:71:uint channelCounter;
> broker/Link.h:111:uint nextChannel();
> broker/SaslAuthenticator.cpp:432:uint ssf = *(reinterpret_cast unsigned*>(value));
> client/MessageReplayTracker.cpp:27:MessageReplayTracker::MessageReplayTracker(uint
>  f) : flushInterval(f), count(0) {}
> client/MessageReplayTracker.cpp:51:void 
> MessageReplayTracker::setFlushInterval(uint f)
> client/MessageReplayTracker.cpp:56:uint 
> MessageReplayTracker::getFlushInterval()
> client/SaslFactory.cpp:331:uint ssf = *(reinterpret_cast unsigned*>(value));
> framing/SendContent.cpp:24:qpid::framing::SendContent::SendContent(FrameHandler&
>  h, uint16_t mfs, uint efc) : handler(h), 
> framing/SendContent.h:42:uint expectedFrameCount;
> framing/SendContent.h:43:uint frameCount;
> framing/SendContent.h:48:QPID_COMMON_EXTERN SendContent(FrameHandler& 
> _handler, uint16_t _maxFrameSize, uint frameCount);
> sys/Semaphore.h:30:Semaphore(uint c = 1) : count(c) {}
> sys/Semaphore.h:54:void release(uint n)
> sys/Semaphore.h:74:uint count;

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
Apache Qpid - AMQP Messaging Implementation
Project:  http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org

Re: qpid client 0.6 connection

[Andrew Stitcher]

On Fri, 2010-04-23 at 00:40 -0800, andrei4002 wrote:
> hello
> 
> i'm trying to handle a connection to a broker, using the new 0.6 release (in
> 0.5 i have no problems) and i get an unhandled exception using
> connection.open to a computer which has it's broker stopped (when it's on is
> ok)
> 
> the connection.open method does not seem to throw any exceptions when this
> happens

More information would be useful here:

Sample code which demonstrates the problem would be really useful -
perhaps you could create a Jira to track the bug with reproducer code
attached.

I'm assuming you're using a 0.6 c++ client, being explicit would help. I
suppose the version of broker probably doesn't matter as it's stopped.

What do you mean by stopped? Do you mean not running at all: as in the
service is stopped; or do you mean ^z as in sent the SIGSTOP signal
meaning the process is suspended?

Your 2 paragraphs seems to be contradictory - Do you get an exception or
not?

Thanks

Andrew



-
Apache Qpid - AMQP Messaging Implementation
Project:  http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org

[jira] Created: (QPID-2544) Enhance the config.xml and virtualhost.xml to be validated and provide an XSD schema to do so

[Sorin Suciu (JIRA)]

Enhance the config.xml and virtualhost.xml to be validated and provide an XSD 
schema to do so
-

 Key: QPID-2544
 URL: https://issues.apache.org/jira/browse/QPID-2544
 Project: Qpid
  Issue Type: Improvement
  Components: Java Broker
Affects Versions: 0.7
Reporter: Sorin Suciu
 Fix For: 0.7


The current broker XML files are not validated at the moment due to various 
reasons. I propose we enhance the configuration and validate the XML's for 
corectness using an XSD schema.
 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
Apache Qpid - AMQP Messaging Implementation
Project:  http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org

[jira] Updated: (QPID-2543) Change uint to standard type

[Bruno Matos (JIRA)]

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

Bruno Matos updated QPID-2543:
--

 Original Estimate: 0.25h  (was: 0.03h)
Remaining Estimate: 0.25h  (was: 0.03h)
   Description: 
I can't find uint as a standard type and it is breaking Mac OS X client 
compilation.

The references I found:

broker/Broker.h:109:uint queueLimit;
broker/Link.cpp:338:uint Link::nextChannel()
broker/Link.h:71:uint channelCounter;
broker/Link.h:111:uint nextChannel();
broker/SaslAuthenticator.cpp:432:uint ssf = *(reinterpret_cast(value));
client/MessageReplayTracker.cpp:27:MessageReplayTracker::MessageReplayTracker(uint
 f) : flushInterval(f), count(0) {}
client/MessageReplayTracker.cpp:51:void 
MessageReplayTracker::setFlushInterval(uint f)
client/MessageReplayTracker.cpp:56:uint MessageReplayTracker::getFlushInterval()
client/SaslFactory.cpp:331:uint ssf = *(reinterpret_cast(value));
framing/SendContent.cpp:24:qpid::framing::SendContent::SendContent(FrameHandler&
 h, uint16_t mfs, uint efc) : handler(h), 
framing/SendContent.h:42:uint expectedFrameCount;
framing/SendContent.h:43:uint frameCount;
framing/SendContent.h:48:QPID_COMMON_EXTERN SendContent(FrameHandler& 
_handler, uint16_t _maxFrameSize, uint frameCount);
sys/Semaphore.h:30:Semaphore(uint c = 1) : count(c) {}
sys/Semaphore.h:54:void release(uint n)
sys/Semaphore.h:74:uint count;


  was:
I can't find uint as a standard type and it is breaking Mac OS X client 
compilation in file frame_functors.h.
Can be changed to unsigned int or is more appropriated size_t in this context?


> Change uint to standard type
> 
>
> Key: QPID-2543
> URL: https://issues.apache.org/jira/browse/QPID-2543
> Project: Qpid
>  Issue Type: Improvement
>  Components: C++ Client
>Affects Versions: 0.7
>Reporter: Bruno Matos
> Fix For: 0.6
>
>   Original Estimate: 0.25h
>  Remaining Estimate: 0.25h
>
> I can't find uint as a standard type and it is breaking Mac OS X client 
> compilation.
> The references I found:
> broker/Broker.h:109:uint queueLimit;
> broker/Link.cpp:338:uint Link::nextChannel()
> broker/Link.h:71:uint channelCounter;
> broker/Link.h:111:uint nextChannel();
> broker/SaslAuthenticator.cpp:432:uint ssf = *(reinterpret_cast unsigned*>(value));
> client/MessageReplayTracker.cpp:27:MessageReplayTracker::MessageReplayTracker(uint
>  f) : flushInterval(f), count(0) {}
> client/MessageReplayTracker.cpp:51:void 
> MessageReplayTracker::setFlushInterval(uint f)
> client/MessageReplayTracker.cpp:56:uint 
> MessageReplayTracker::getFlushInterval()
> client/SaslFactory.cpp:331:uint ssf = *(reinterpret_cast unsigned*>(value));
> framing/SendContent.cpp:24:qpid::framing::SendContent::SendContent(FrameHandler&
>  h, uint16_t mfs, uint efc) : handler(h), 
> framing/SendContent.h:42:uint expectedFrameCount;
> framing/SendContent.h:43:uint frameCount;
> framing/SendContent.h:48:QPID_COMMON_EXTERN SendContent(FrameHandler& 
> _handler, uint16_t _maxFrameSize, uint frameCount);
> sys/Semaphore.h:30:Semaphore(uint c = 1) : count(c) {}
> sys/Semaphore.h:54:void release(uint n)
> sys/Semaphore.h:74:uint count;

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
Apache Qpid - AMQP Messaging Implementation
Project:  http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org

[jira] Updated: (QPID-2543) Change uint to standard type

[Bruno Matos (JIRA)]

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

Bruno Matos updated QPID-2543:
--

Summary: Change uint to standard type  (was: Change uint to standar type)

> Change uint to standard type
> 
>
> Key: QPID-2543
> URL: https://issues.apache.org/jira/browse/QPID-2543
> Project: Qpid
>  Issue Type: Improvement
>  Components: C++ Client
>Affects Versions: 0.7
>Reporter: Bruno Matos
> Fix For: 0.6
>
>   Original Estimate: 0.03h
>  Remaining Estimate: 0.03h
>
> I can't find uint as a standard type and it is breaking Mac OS X client 
> compilation in file frame_functors.h.
> Can be changed to unsigned int or is more appropriated size_t in this context?

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
Apache Qpid - AMQP Messaging Implementation
Project:  http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org

[jira] Created: (QPID-2543) Change uint to standar type

[Bruno Matos (JIRA)]

Change uint to standar type
---

 Key: QPID-2543
 URL: https://issues.apache.org/jira/browse/QPID-2543
 Project: Qpid
  Issue Type: Improvement
  Components: C++ Client
Affects Versions: 0.7
Reporter: Bruno Matos
 Fix For: 0.6


I can't find uint as a standard type and it is breaking Mac OS X client 
compilation in file frame_functors.h.
Can be changed to unsigned int or is more appropriated size_t in this context?

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
Apache Qpid - AMQP Messaging Implementation
Project:  http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org

[jira] Resolved: (QPID-1807) Backout Flow to Disk from 0.5 to allow more time for testing

[Martin Ritchie (JIRA)]

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

Martin Ritchie resolved QPID-1807.
--

Resolution: Fixed

> Backout Flow to Disk from 0.5 to allow more time for testing 
> -
>
> Key: QPID-1807
> URL: https://issues.apache.org/jira/browse/QPID-1807
> Project: Qpid
>  Issue Type: Task
>  Components: Java Broker
>Affects Versions: M4, 0.5
>Reporter: Martin Ritchie
>Assignee: Martin Ritchie
> Fix For: 0.5
>
>
> From Aidan's Email the plan is to:
> 1. copy trunk at a known good revision from before this work started
> onto a "newtip"[1] branch
> 2. use the new 1.5 svn merge tooling to take the good patches from
> trunk to newtip
> 2.5 test newtip to ensure that the resulting broker is sound, safe and sane.
> 3. move trunk/qpid/java/broker to a holding branch so that the work
> isn't lost and can be easily retrieved later
> 4. move newtip/qpid/java/broker to trunk/qpid/java/broker and copy it
> to 0.5-release/qpid/java/broker

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
Apache Qpid - AMQP Messaging Implementation
Project:  http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org

[jira] Commented: (QPID-2517) Proposed change to QMF schema for the broker

[Ted Ross (JIRA)]

[ 
https://issues.apache.org/jira/browse/QPID-2517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12860245#action_12860245
 ] 

Ted Ross commented on QPID-2517:


Rob,

I like your suggestion about transports/endpoints.  This is a better model for 
the C++ broker as well since it supports TCP, SSL, and rdma transports 
simultaneously.

Would you object if I commit the attached Java patch as an interim step toward 
making the more involved changes?

-Ted


> Proposed change to QMF schema for the broker
> 
>
> Key: QPID-2517
> URL: https://issues.apache.org/jira/browse/QPID-2517
> Project: Qpid
>  Issue Type: Improvement
>  Components: C++ Broker, Java Broker
>Reporter: Ted Ross
>Assignee: Ted Ross
>Priority: Minor
> Attachments: broker-idx.diff, java.diff
>
>
> I would like to make a change to the management schema for the broker.  A 
> patch will be attached.
> The current schema causes the "broker" object to be indexed by the TCP port.  
> This is a problem in clusters where each node in the cluster may have a 
> different port.  Since the port is part of the index, and the index is used 
> as the QMFv2 object identifier, method calls addressed to the broker may not 
> be handled uniformly by each node in a cluster.
> The change removes the "index" status from the "port" attribute and adds a 
> new index attribute called "name".  This name is fixed as "amqp-broker".  
> This is a safe thing to do as there is only one broker associated with the 
> broker-resident agent.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
Apache Qpid - AMQP Messaging Implementation
Project:  http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org

[jira] Updated: (QPID-2517) Proposed change to QMF schema for the broker

[Ted Ross (JIRA)]

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

Ted Ross updated QPID-2517:
---

Attachment: java.diff

Patch to the Java broker to adapt to this change.

> Proposed change to QMF schema for the broker
> 
>
> Key: QPID-2517
> URL: https://issues.apache.org/jira/browse/QPID-2517
> Project: Qpid
>  Issue Type: Improvement
>  Components: C++ Broker, Java Broker
>Reporter: Ted Ross
>Assignee: Ted Ross
>Priority: Minor
> Attachments: broker-idx.diff, java.diff
>
>
> I would like to make a change to the management schema for the broker.  A 
> patch will be attached.
> The current schema causes the "broker" object to be indexed by the TCP port.  
> This is a problem in clusters where each node in the cluster may have a 
> different port.  Since the port is part of the index, and the index is used 
> as the QMFv2 object identifier, method calls addressed to the broker may not 
> be handled uniformly by each node in a cluster.
> The change removes the "index" status from the "port" attribute and adds a 
> new index attribute called "name".  This name is fixed as "amqp-broker".  
> This is a safe thing to do as there is only one broker associated with the 
> broker-resident agent.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
Apache Qpid - AMQP Messaging Implementation
Project:  http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org

[jira] Updated: (QPID-2536) Implement posix clock_gettime

[Bruno Matos (JIRA)]

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

Bruno Matos updated QPID-2536:
--

Summary: Implement  posix clock_gettime  (was: Implement  posix get_time)

> Implement  posix clock_gettime
> --
>
> Key: QPID-2536
> URL: https://issues.apache.org/jira/browse/QPID-2536
> Project: Qpid
>  Issue Type: Task
>  Components: C++ Client
>Affects Versions: 0.7
> Environment: mac os x
>Reporter: Bruno Matos
>
> In mac os x there is no implementation for the POSIX clock_gettime function.
> We can try this workaround:
> http://www.wand.net.nz/~smr26/wordpress/2009/01/19/monotonic-time-in-mac-os-x/

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
Apache Qpid - AMQP Messaging Implementation
Project:  http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org

[jira] Updated: (QPID-2536) Implement posix get_time

[Bruno Matos (JIRA)]

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

Bruno Matos updated QPID-2536:
--

Description: 
In mac os x there is no implementation for the POSIX clock_gettime function.
We can try this workaround:

http://www.wand.net.nz/~smr26/wordpress/2009/01/19/monotonic-time-in-mac-os-x/

  was:
In mac os x there is no implementation for the POSIX get_time function.
We can try this workaround:

http://www.wand.net.nz/~smr26/wordpress/2009/01/19/monotonic-time-in-mac-os-x/


> Implement  posix get_time
> -
>
> Key: QPID-2536
> URL: https://issues.apache.org/jira/browse/QPID-2536
> Project: Qpid
>  Issue Type: Task
>  Components: C++ Client
>Affects Versions: 0.7
> Environment: mac os x
>Reporter: Bruno Matos
>
> In mac os x there is no implementation for the POSIX clock_gettime function.
> We can try this workaround:
> http://www.wand.net.nz/~smr26/wordpress/2009/01/19/monotonic-time-in-mac-os-x/

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
Apache Qpid - AMQP Messaging Implementation
Project:  http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org

qpid client 0.6 connection

[andrei4002]

hello

i'm trying to handle a connection to a broker, using the new 0.6 release (in
0.5 i have no problems) and i get an unhandled exception using
connection.open to a computer which has it's broker stopped (when it's on is
ok)

the connection.open method does not seem to throw any exceptions when this
happens

any ideas where to start looking?

thanks
-- 
View this message in context: 
http://apache-qpid-developers.2158895.n2.nabble.com/qpid-client-0-6-connection-tp4949387p4949387.html
Sent from the Apache Qpid developers mailing list archive at Nabble.com.

-
Apache Qpid - AMQP Messaging Implementation
Project:  http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org

[jira] Created: (QPID-2541) Separate Group an ACL configuration and make group sources pluggable

[Andrew Kennedy (JIRA)]

Separate Group an ACL configuration and make group sources pluggable


 Key: QPID-2541
 URL: https://issues.apache.org/jira/browse/QPID-2541
 Project: Qpid
  Issue Type: Sub-task
  Components: Java Broker
Reporter: Andrew Kennedy
 Fix For: 0.7




-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
Apache Qpid - AMQP Messaging Implementation
Project:  http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org

[jira] Created: (QPID-2542) Implement ACL checking as OSGi plugin

[Andrew Kennedy (JIRA)]

Implement ACL checking as OSGi plugin
-

 Key: QPID-2542
 URL: https://issues.apache.org/jira/browse/QPID-2542
 Project: Qpid
  Issue Type: Sub-task
Reporter: Andrew Kennedy




-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
Apache Qpid - AMQP Messaging Implementation
Project:  http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org

[jira] Updated: (QPID-2537) Add QMF/JMX administration of ACLs

[Andrew Kennedy (JIRA)]

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

Andrew Kennedy updated QPID-2537:
-

Parent: QPID-2476
Issue Type: Sub-task  (was: Task)

> Add QMF/JMX administration of ACLs
> --
>
> Key: QPID-2537
> URL: https://issues.apache.org/jira/browse/QPID-2537
> Project: Qpid
>  Issue Type: Sub-task
>  Components: Java Broker, Java Management : JMX Interface, Java 
> Management : QMF
>Reporter: Andrew Kennedy
> Fix For: 0.7
>
>


-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
Apache Qpid - AMQP Messaging Implementation
Project:  http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org

[jira] Updated: (QPID-2539) Update ACL file syntax to be clearer and add extra operations

[Andrew Kennedy (JIRA)]

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

Andrew Kennedy updated QPID-2539:
-

Parent: QPID-2476
Issue Type: Sub-task  (was: Task)

> Update ACL file syntax to be clearer and add extra operations
> -
>
> Key: QPID-2539
> URL: https://issues.apache.org/jira/browse/QPID-2539
> Project: Qpid
>  Issue Type: Sub-task
>  Components: Java Broker
>Reporter: Andrew Kennedy
> Fix For: 0.7
>
>


-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
Apache Qpid - AMQP Messaging Implementation
Project:  http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org

[jira] Updated: (QPID-2538) Add XML configuration syntax for ACLs in Java broker

[Andrew Kennedy (JIRA)]

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

Andrew Kennedy updated QPID-2538:
-

Parent: QPID-2476
Issue Type: Sub-task  (was: Task)

> Add XML configuration syntax for ACLs in Java broker
> 
>
> Key: QPID-2538
> URL: https://issues.apache.org/jira/browse/QPID-2538
> Project: Qpid
>  Issue Type: Sub-task
>  Components: Java Broker
>Reporter: Andrew Kennedy
> Fix For: 0.7
>
>


-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
Apache Qpid - AMQP Messaging Implementation
Project:  http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org

[jira] Updated: (QPID-2540) Create parser and implementation of C++ style ACL files for Java broker

[Andrew Kennedy (JIRA)]

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

Andrew Kennedy updated QPID-2540:
-

Parent: QPID-2476
Issue Type: Sub-task  (was: Task)

> Create parser and implementation of C++ style ACL files for Java broker
> ---
>
> Key: QPID-2540
> URL: https://issues.apache.org/jira/browse/QPID-2540
> Project: Qpid
>  Issue Type: Sub-task
>  Components: Java Management : CLI Tool
>Reporter: Andrew Kennedy
>Priority: Minor
> Fix For: 0.7
>
>


-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
Apache Qpid - AMQP Messaging Implementation
Project:  http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org

[jira] Created: (QPID-2540) Create parser and implementation of C++ style ACL files for Java broker

[Andrew Kennedy (JIRA)]

Create parser and implementation of C++ style ACL files for Java broker
---

 Key: QPID-2540
 URL: https://issues.apache.org/jira/browse/QPID-2540
 Project: Qpid
  Issue Type: Task
  Components: Java Management : CLI Tool
Reporter: Andrew Kennedy
Priority: Minor
 Fix For: 0.7




-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
Apache Qpid - AMQP Messaging Implementation
Project:  http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org

[jira] Created: (QPID-2539) Update ACL file syntax to be clearer and add extra operations

[Andrew Kennedy (JIRA)]

Update ACL file syntax to be clearer and add extra operations
-

 Key: QPID-2539
 URL: https://issues.apache.org/jira/browse/QPID-2539
 Project: Qpid
  Issue Type: Task
  Components: Java Broker
Reporter: Andrew Kennedy
 Fix For: 0.7




-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
Apache Qpid - AMQP Messaging Implementation
Project:  http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org

[jira] Created: (QPID-2537) Add QMF/JMX administration of ACLs

[Andrew Kennedy (JIRA)]

Add QMF/JMX administration of ACLs
--

 Key: QPID-2537
 URL: https://issues.apache.org/jira/browse/QPID-2537
 Project: Qpid
  Issue Type: Task
  Components: Java Broker, Java Management : JMX Interface, Java 
Management : QMF
Reporter: Andrew Kennedy
 Fix For: 0.7




-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
Apache Qpid - AMQP Messaging Implementation
Project:  http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org

[jira] Created: (QPID-2538) Add XML configuration syntax for ACLs in Java broker

[Andrew Kennedy (JIRA)]

Add XML configuration syntax for ACLs in Java broker


 Key: QPID-2538
 URL: https://issues.apache.org/jira/browse/QPID-2538
 Project: Qpid
  Issue Type: Task
  Components: Java Broker
Reporter: Andrew Kennedy
 Fix For: 0.7




-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
Apache Qpid - AMQP Messaging Implementation
Project:  http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org

Re: Contributer Patches - Committers Requested

[Marnie McCormack]

I'll try to pick up a few more later today, on the Java side.

Regards,
Marnie

On Fri, Apr 23, 2010 at 10:39 AM, Marnie McCormack <
marnie.mccorm...@googlemail.com> wrote:

> QPID-2433 done, after careful consideration ;-)
>
> Regards,
> Marnie
>
>  On Thu, Apr 22, 2010 at 2:27 PM, Emmanuel Bourg wrote:
>
>> Rajith Attapattu a écrit :
>>
>> I have taken care of QPID-2508 and QPID-2522 from Emmanuel.
>>> I left the MINA patch to Martin as he is more familiar with that side.
>>>
>>
>> Thanks all for taking care of the patches. There is also an involved patch
>> waiting for a thorough review in QPID-2433.
>>
>>https://issues.apache.org/jira/browse/QPID-2433
>>
>> Emmanuel Bourg
>>
>>
>> -
>> Apache Qpid - AMQP Messaging Implementation
>> Project:  http://qpid.apache.org
>> Use/Interact: mailto:dev-subscr...@qpid.apache.org
>>
>>
>

[jira] Resolved: (QPID-2433) qpid-server.bat fails if the path contains a space character

[Marnie McCormack (JIRA)]

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

Marnie McCormack resolved QPID-2433.


Fix Version/s: 0.7
   Resolution: Fixed

Applied patch from Emmanuel

> qpid-server.bat fails if the path contains a space character
> 
>
> Key: QPID-2433
> URL: https://issues.apache.org/jira/browse/QPID-2433
> Project: Qpid
>  Issue Type: Bug
>  Components: Java Broker
>Affects Versions: 0.5
>Reporter: Emmanuel Bourg
>Priority: Trivial
> Fix For: 0.7
>
> Attachments: qpid-bat.patch
>
>
> The qpid-server.bat file doesn't work if Qpid is installed on a path 
> containing space characters. Extra quotes must be added to the command line 
> to make it work properly.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
Apache Qpid - AMQP Messaging Implementation
Project:  http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org

Re: Contributer Patches - Committers Requested

[Marnie McCormack]

QPID-2433 done, after careful consideration ;-)

Regards,
Marnie

On Thu, Apr 22, 2010 at 2:27 PM, Emmanuel Bourg  wrote:

> Rajith Attapattu a écrit :
>
> I have taken care of QPID-2508 and QPID-2522 from Emmanuel.
>> I left the MINA patch to Martin as he is more familiar with that side.
>>
>
> Thanks all for taking care of the patches. There is also an involved patch
> waiting for a thorough review in QPID-2433.
>
>https://issues.apache.org/jira/browse/QPID-2433
>
> Emmanuel Bourg
>
>
> -
> Apache Qpid - AMQP Messaging Implementation
> Project:  http://qpid.apache.org
> Use/Interact: mailto:dev-subscr...@qpid.apache.org
>
>

[jira] Created: (QPID-2536) Implement posix get_time

[Bruno Matos (JIRA)]

Implement  posix get_time
-

 Key: QPID-2536
 URL: https://issues.apache.org/jira/browse/QPID-2536
 Project: Qpid
  Issue Type: Task
  Components: C++ Client
Affects Versions: 0.7
 Environment: mac os x
Reporter: Bruno Matos


In mac os x there is no implementation for the POSIX get_time function.
We can try this workaround:

http://www.wand.net.nz/~smr26/wordpress/2009/01/19/monotonic-time-in-mac-os-x/

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
Apache Qpid - AMQP Messaging Implementation
Project:  http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org

Re: certificate authentication

[Gordon Sim]

On 04/23/2010 01:14 AM, Steve Huston wrote:

Can you tell me where I can specify the crl location that
contains the list of revoked certificates info?


I believe that's part of the certificate database you're already passing
to qpidd, but I'm not 100% clear on that.


For the nss based ssl implementation (on linux) I believe you use the 
crlutil tool: 
http://www.mozilla.org/projects/security/pki/nss/tools/crlutil.html


-
Apache Qpid - AMQP Messaging Implementation
Project:  http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org