date:20110224


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

Gordon Sim resolved QPID-2714.
--

Resolution: Fixed

 Programming in Apache Qpid doesn't discuss capacity/credit
 

 Key: QPID-2714
 URL: https://issues.apache.org/jira/browse/QPID-2714
 Project: Qpid
  Issue Type: Bug
  Components: Documentation
Affects Versions: 0.7
Reporter: Steve Huston
Priority: Minor
 Attachments: QPID-2714.patch


 My comments grew out of looking at the C++ messaging API, though this 
 probably applies to Python and .NET as well.
 During a discussion on users@qpid I initiated recently I learned that 
 creating a number of Receivers and calling session.nextReceiver() to wait for 
 a message on any of the Receivers doesn't work unless some capacity is 
 granted to the Receivers first. This is different from simply calling fetch() 
 on a Receiver with no capacity - in that case the client code issues credit 
 behind the scenes.
 The code example shown in section 6 won't work (I used something very similar 
 in a program I wrote, and it didn't for the reason above). I'll attach a 
 patch that fixes the C++ code example, but there should be an 
 introduction/discussion of the whole topic of capacity, credit, acks, etc.

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira



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

[jira] Assigned: (QPID-2326) exchange.declare should throw a 404 - not found exception if the exchange type is unknown


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

Gordon Sim reassigned QPID-2326:


Assignee: Gordon Sim

 exchange.declare should throw a 404 - not found exception if the exchange 
 type is unknown
 -

 Key: QPID-2326
 URL: https://issues.apache.org/jira/browse/QPID-2326
 Project: Qpid
  Issue Type: Bug
  Components: C++ Broker, Python Test Suite
Affects Versions: 0.6
Reporter: Rob Godfrey
Assignee: Gordon Sim

 The C++ Broker returns a 503 error when an exchange is declared as being of a 
 type which the broker does not recognize, and the python test 
 testTypeNotKnown in exchange.py tests for this behaviour
 However the AMQP0-10 spec (pg 217 of the PDF) says
 Exception: exchange-type-not-found
  Error:not-found
 If the client attempts to create an exchange which the server does not 
 recognize, an exception MUST be sent.
 not-found is error code 404

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira



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

Re: Enterprise Messaging Solutions

2011-02-24 Thread Gordon Sim


On 02/24/2011 10:49 AM, Massimo Paladin wrote:

Someone filled it for Qpid C++, can you confirm?


Yes, I did!

('Composite Destinations' is not a term we explicitly use, but I believe 
you can achieve that using the exchange/queue/binding model)



Could someone fill the form for Qpid Java?
Here again: http://goo.gl/ENpfc

Regards,
---
Massimo Paladin

email: massimo.pala...@gmail.com
website: http://www.mpaladin.com
flickr's page: http://flickr.com/photos/massimop


On Wed, Feb 23, 2011 at 3:27 PM, Massimo Paladinmassimo.pala...@cern.chwrote:


Hello,

I am currently doing a survey on available enterprise messaging solutions.

Would you be so kind to spend some minutes and fill in this form for Qpid
(Java and C++)?
http://goo.gl/ENpfc

Kind regards,
---
Massimo Paladin

email: massimo.pala...@gmail.com
website: http://www.mpaladin.com
flickr's page: http://flickr.com/photos/massimop






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

[jira] Resolved: (QPID-2362) No clear way to read an AbsTime from a Variant...


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

Gordon Sim resolved QPID-2362.
--

Resolution: Not A Problem

The (latest) doxygen for qpid/sys/Time.h recommends :

int64_t nanosec_since_epoch = Duration(EPOCH, now());

which you could then get back to an AbsTime by:

AbsTime myTime(EPOCH, nanosec_since_epoch);

(If this doesn't address the issue, feel free to reopen with details).

 No clear way to read an AbsTime from a Variant...
 -

 Key: QPID-2362
 URL: https://issues.apache.org/jira/browse/QPID-2362
 Project: Qpid
  Issue Type: Bug
  Components: C++ Client
Affects Versions: 0.5
 Environment: C++
Reporter: Kerry Bonin

 I'm working on sending and receiving a timestamp of type qpid::sys::AbsTime 
 via qpid::messaging::MapContent.
 The instructions in qpid\sys\Time.h recommend use of the Duration class for 
 access to the ns value, leading to this example:
   Message msgOut;
   MapContent contentOut( msgOut );
   contentOut[ timestamp ] = Variant( Duration( AbsTime::now() ) );
 This works fine (other than the epoch bug [QPID-1904] on Windows I just 
 submitted a patch for.)
 The problem is, how do I get the AbsTime back out of the map?  I can extract 
 the int64_t value just fine, but there are no appropriate AbsTime 
 constructors.  The only exposed methods are now() and the (const AbsTime  t, 
 const Duration  d) constructor, but since the default constructor for 
 AbsTime initializes to a 'not-a-date-time' state, there does not appear to be 
 a valid way to initialize AbsTime from a specific value.
 One suggestion would be to add an AbsTime constructor that takes an int64_t 
 ns parameter in the Jan 1, 1970 epoch.

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira



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

[jira] Closed: (QPID-2713) persiste last node no use in cluster


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

Gordon Sim closed QPID-2713.


Resolution: Incomplete

 persiste last node no use in cluster
 

 Key: QPID-2713
 URL: https://issues.apache.org/jira/browse/QPID-2713
 Project: Qpid
  Issue Type: Bug
  Components: C++ Broker
Affects Versions: 0.6
 Environment: on Linux,using openais for cluster.
Reporter: creator wang
   Original Estimate: 240h
  Remaining Estimate: 240h

 on Linux,using openais for cluster.Testing QueueOptions setPersistLastNode(), 
 found it not worked.

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira



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

[jira] Resolved: (QPID-3021) the Session and Connector actors should be set for events occurring on 0-10 connections


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

Andrew Kennedy resolved QPID-3021.
--

Resolution: Fixed

Review OK

 the Session and Connector actors should be set for events occurring on 0-10 
 connections
 ---

 Key: QPID-3021
 URL: https://issues.apache.org/jira/browse/QPID-3021
 Project: Qpid
  Issue Type: Bug
  Components: Java Broker
Affects Versions: 0.8, 0.9
Reporter: Robbie Gemmell
Assignee: Andrew Kennedy
 Fix For: 0.9


 When addressing QPID-3014 it was noticed that the Session and Connector 
 actors were not being set appropriately when processing events arriving on 
 0-10 connections. As a result, logging such as session close and connection 
 close do not properly convey the associated LogActor, and instead reported 
 either the actor for the wrong connection that was previously left on the 
 CurrentAActor stack, or jsut the default Broker actor supplied when the stack 
 is empty.

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira



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

[jira] Resolved: (QPID-2977) Updated pom files for slf4j


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

Andrew Kennedy resolved QPID-2977.
--

Resolution: Fixed

Review OK

 Updated pom files for slf4j
 ---

 Key: QPID-2977
 URL: https://issues.apache.org/jira/browse/QPID-2977
 Project: Qpid
  Issue Type: Bug
  Components: Java Common
Affects Versions: 0.8
Reporter: Emmanuel Bourg
Assignee: Andrew Kennedy
Priority: Trivial
 Fix For: 0.9


 slf4j has been updated to the version 1.6.1 recently, but the corresponding 
 pom files were not updated in qpid/java/lib/poms. The 1.4.0 poms should be 
 removed and replaced by these:
 http://repo1.maven.org/maven2/org/slf4j/slf4j-api/1.6.1/slf4j-api-1.6.1.pom
 http://repo1.maven.org/maven2/org/slf4j/slf4j-log4j12/1.6.1/slf4j-log4j12-1.6.1.pom

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira



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

[jira] Updated: (QPID-3065) Send header and frame data as single buffer


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

Andrew Kennedy updated QPID-3065:
-

Status: Ready To Review  (was: In Progress)

 Send header and frame data as single buffer
 ---

 Key: QPID-3065
 URL: https://issues.apache.org/jira/browse/QPID-3065
 Project: Qpid
  Issue Type: Bug
  Components: Java Broker
Affects Versions: 0.9
Reporter: Andrew Kennedy
Assignee: Andrew Kennedy
 Fix For: 0.9


 The Disassembler class for the AMQP 0-10 protocol version sends the 12 byte 
 frame header to the network layer in a separate call from the rest of the 
 frame data. This can cause frame header data to be received out-of-order or 
 corrupted frame bodies, particularly with VM transports. The entire frame, 
 including the header, should be written into a single ByteBuffer which should 
 be sent using a single call to the network layer, eliminating this issue.

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira



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

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


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

Andrew Kennedy resolved QPID-1916.
--

Resolution: Fixed

Review OK

 Maven artifacts for the client
 --

 Key: QPID-1916
 URL: https://issues.apache.org/jira/browse/QPID-1916
 Project: Qpid
  Issue Type: New Feature
  Components: Ant Build System, Build Tools, Java Client, Java Common, 
 Java Tools, Maven build system, Qpid Managment Framework
Affects Versions: M3, M4, 0.5, 0.6, 0.7, 0.8
Reporter: Bryan Kearney
Assignee: Andrew Kennedy
 Fix For: 0.9

 Attachments: genpom.patch, maven.patch, mavenize3.patch


 The attached patch files adds the maven ant tasks to the build system. It 
 allows, on a per-module basis, to support creating a pom file and exporting 
 the jars to a maven repository. This is not a very DRY solution, as it 
 requires copying the dependency information from the build.deps file. I have 
 only added the pom files for the client bits, since i believe these are the 
 most likely to be required by folks using QMF.

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira



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

[jira] Assigned: (QPID-3065) Send header and frame data as single buffer


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

Andrew Kennedy reassigned QPID-3065:


Assignee: Robbie Gemmell  (was: Andrew Kennedy)

Robbie, please review

 Send header and frame data as single buffer
 ---

 Key: QPID-3065
 URL: https://issues.apache.org/jira/browse/QPID-3065
 Project: Qpid
  Issue Type: Bug
  Components: Java Broker
Affects Versions: 0.9
Reporter: Andrew Kennedy
Assignee: Robbie Gemmell
 Fix For: 0.9


 The Disassembler class for the AMQP 0-10 protocol version sends the 12 byte 
 frame header to the network layer in a separate call from the rest of the 
 frame data. This can cause frame header data to be received out-of-order or 
 corrupted frame bodies, particularly with VM transports. The entire frame, 
 including the header, should be written into a single ByteBuffer which should 
 be sent using a single call to the network layer, eliminating this issue.

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira



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

[jira] Closed: (QPID-2377) ssl errors are not signalled correctly in nss based impl


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

Gordon Sim closed QPID-2377.


Resolution: Duplicate

Duplicate of QPID-2083

 ssl errors are not signalled correctly in nss based impl
 

 Key: QPID-2377
 URL: https://issues.apache.org/jira/browse/QPID-2377
 Project: Qpid
  Issue Type: Bug
  Components: C++ Broker
Affects Versions: 0.6
Reporter: Gordon Sim

 this is due to making the handshake non-blocking: 
 http://svn.apache.org/viewvc?view=revisionrevision=790291

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira



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

[jira] Resolved: (QPID-2518) Qpid C++ broker can easily be blocked by client trying to connect over SSL port


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

Gordon Sim resolved QPID-2518.
--

Resolution: Fixed

 Qpid C++ broker can easily be blocked by client trying to connect over SSL 
 port
 ---

 Key: QPID-2518
 URL: https://issues.apache.org/jira/browse/QPID-2518
 Project: Qpid
  Issue Type: Bug
  Components: C++ Broker
 Environment: Red Hat Enterprise MRG 1.2
Reporter: Armin Noll

 We are running a C++ broker as deamon with the following configuration:
  
 log-enable=info+
 log-to-file=/var/lib/qpidd/op_prod09/data/0097/qpidd.log
 log-to-syslog=no
 auth=yes
 acl-file=qpidd.acl
 realm=QPID0097
 data-dir=/var/lib/qpidd/op_prod09/data/0097
 pid-dir=/var/lib/qpidd/op_prod09/data/0097
 port=20097
 wait=30
 num-jfiles=4
 jfile-size-pgs=1
 wcache-page-size=128
 tpl-num-jfiles=4
 tpl-jfile-size-pgs=1
 tpl-wcache-page-size=128
 ssl-cert-db=/var/lib/qpidd/op_prod09/data/0097
 ssl-port=10097
 ssl-cert-name=RGC001
 ssl-cert-password-file=/var/lib/qpidd/op_prod09/data/0097/amq_cert_db.pwd
 ssl-require-client-authentication=yes
 cluster-name=QPID0097
 cluster-url=amqp:tcp:172.16.45.198:20097
 cluster-username=x
 cluster-password=x
  
 We tried to connect an application to the SSL port which does not talk the 
 correct protocol. We simply used telnet:
 $ telnet 172.16.45.198 10097
  
 The result was (we waited at least 30 min, then killed the process running 
 telnet):
 The broker doesn't react anymore, no more new client connections can be 
 established, the broker even cannot be stopped with qpidd -p 20097 -q.
  
 This way anybody in the world could easily block our service provided over a 
 Qpid broker.
 Is there a way to get around this? 
 This issue has also been reported as Red Hat service request no. 2014266.

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira



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

Re: qpid.pc installing into /usr/lib/pkgconfig on x86_64

2011-02-24 Thread Alan Conway


On 02/23/2011 10:05 AM, Andrew Stitcher wrote:

On Wed, 2011-02-23 at 11:06 +1100, Angus Salkeld wrote:

On Tue, Feb 22, 2011 at 10:17:42AM -0500, Alan Conway wrote:

On 02/20/2011 07:01 PM, Angus Salkeld wrote:

Hi

I ran ./configure --prefix=/usr and qpid.pc got installed into
/usr/lib/pkgconfig/. All the other .pc files on my system are in
/usr/lib64/pkgconfig/.

Now my PKG_CHECK_MODULES(QPID) doesn't work.

Any ideas? Any other preferred way of finding the libs?

I am on Fedora14, using latest qpid code.



You can get it to do the right thing with:
  ./configure --prefix=/usr --libdir=/usr/lib64

I'm not sure how to get automake to do it right automatically.


OK, no worries I have worked around it.

you could do something like this in the configure.ac:

   if test $libdir = \${exec_prefix}/lib; then
 if test -e /usr/lib64; then
   libdir=${exec_prefix}/lib64
 fi
   fi



I don't think this works as a test.

Remember that in many 64 bit systems (certainly true for x86_64) you can
run and compile both 32 and 64 bit binaries, so the presence of the 64
bit libs doesn't show what you want to build one way or the other.

Also it's very important to note that the lib/lib64 distinction is not
at all general and pretty much distribution specific. For example this
isn't how it's done on FreeBSD (lib/lib32).

So I don't think that the upstream source should try to vary from the
gnu defaults and distribution packaging should deal with it themselves
(which is indeed what the Fedora packages do).

This also isn't at all specific to qpid.


Right, and from a quick read-around the standard solution is
 ./configure --prefix=/usr --libdir=/usr/lib64
If someone knows of autoconf project(s) that have a better solution we could 
copy it but I'm not keen on trying to figure it out by trial and error.


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

[jira] Commented: (QPID-2979) The following SASL mechanisms [PLAIN] specified by the client are not supported by the broker


[ 
https://issues.apache.org/jira/browse/QPID-2979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12998878#comment-12998878
 ] 

Gordon Sim commented on QPID-2979:
--

I don't think either of those is a good solution.

(1) The broker can't send nothing in the mechanism array as that means no 
mechanisms are supported and the sasl handshake that is required part of the 
AMQP connection handshake could not complete.

(2) I'm not sure what you mean by having Java 'skip SASL negotiation'. It has 
to send a connection-start-ok anyway; all it needs to do is state ANONYMOUS in 
the mechanism the response can actually be empty if desired. The neatest way to 
do this is a simple SASL plugin. 


 The following SASL mechanisms [PLAIN] specified by the client are not 
 supported by the broker
 -

 Key: QPID-2979
 URL: https://issues.apache.org/jira/browse/QPID-2979
 Project: Qpid
  Issue Type: Bug
  Components: C++ Broker, Java Client
Affects Versions: 0.8
 Environment: Windows XP
Reporter: Ibisek
 Fix For: Future


 An exception is thrown when connecting from a Java client (v 0.8) to qpidd (v 
 0.8) run with --auth no.
 javax.jms.JMSException: Error creating connection: The following SASL 
 mechanisms [PLAIN] specified by the client are not supported by the broker
   at 
 org.apache.qpid.client.AMQConnectionFactory.createConnection(AMQConnectionFactory.java:286)
 Used JNDI/JMS configuration:
 java.naming.factory.initial = 
 org.apache.qpid.jndi.PropertiesFileInitialContextFactory
 connectionfactory.qpidConnectionfactory = 
 amqp://guest:guest@clientid/abcd?brokerlist='tcp://localhost:5672'
 destination.mainSend = direct://amq.direct//step.01
 It worked just fine in 0.6 but no success now in 0.8. 
 The broker is from Contributed C++ Packages - Windows Installer 
 (http://www.riverace.com/qpid/qpidc-0.8-x86.msi)
 Logs from qpidd:
 C:Program Filesapache-qpidc-0.8binqpidd --auth no --log-enable info+ 
 --log-enable trace+:amqp_0_10
 2010-12-15 11:42:48 info Management enabled
 2010-12-15 11:42:48 notice SASL disabled: No Authentication Performed
 2010-12-15 11:42:48 info Policy file not specified. ACL Disabled, no ACL 
 checking being done!
 2010-12-15 11:42:48 error Failed to initialise SSL listener: The credentials 
 supplied to the package were not recognized (cpps
 rcqpidbrokerwindowsSslProtocolFactory.cpp:177)
 2010-12-15 11:42:48 notice Listening on TCP port 5672
 5672
 2010-12-15 11:42:48 notice Broker running
 2010-12-15 11:42:53 trace SENT 127.0.0.1:1786 INIT(0-10)
 2010-12-15 11:42:53 trace SENT [127.0.0.1:1786]: Frame[BEbe; channel=0; 
 {ConnectionStartBody: server-properties={qpid.federation_tag:V2:36:s
 tr16(96790865-dc5c-427a-affe-70d021653737)}; 
 mechanisms=str16{V2:9:str16(ANONYMOUS)}; locales=str16{V2:5:str16(en_US)}; }]
 Run it with the -t option:
 2010-12-15 11:45:56 trace SEND raiseEvent (v1) 
 class=org.apache.qpid.broker.clientDisconnect
 2010-12-15 11:46:01 debug RECV [127.0.0.1:1794] INIT(0-10)
 2010-12-15 11:46:01 trace SENT 127.0.0.1:1794 INIT(0-10)
 2010-12-15 11:46:01 trace SENT [127.0.0.1:1794]: Frame[BEbe; channel=0; 
 {ConnectionStartBody: server-properties={qpid.federation_tag:V2:36:s
 tr16(96790865-dc5c-427a-affe-70d021653737)}; 
 mechanisms=str16{V2:9:str16(ANONYMOUS)}; locales=str16{V2:5:str16(en_US)}; }]
 2010-12-15 11:46:01 debug DISCONNECTED [127.0.0.1:1794]
 2010-12-15 11:46:01 trace SEND raiseEvent (v1) 
 class=org.apache.qpid.broker.clientDisconnect 

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira



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

[jira] Updated: (QPID-2979) The following SASL mechanisms [PLAIN] specified by the client are not supported by the broker


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

Gordon Sim updated QPID-2979:
-

Attachment: sasl-anonymous-java-client.patch

This patch provides an ANONYMOUS SaslClient implementation (the broker already 
seems to have a SaslServer).

It also adds the factory to the dynamic list properties and registers all 
factories from AMQConnectionDelegate_0_10 as the registration only seems to 
happen for 0-8/0-9 paths at present.

 The following SASL mechanisms [PLAIN] specified by the client are not 
 supported by the broker
 -

 Key: QPID-2979
 URL: https://issues.apache.org/jira/browse/QPID-2979
 Project: Qpid
  Issue Type: Bug
  Components: C++ Broker, Java Client
Affects Versions: 0.8
 Environment: Windows XP
Reporter: Ibisek
 Fix For: Future

 Attachments: sasl-anonymous-java-client.patch


 An exception is thrown when connecting from a Java client (v 0.8) to qpidd (v 
 0.8) run with --auth no.
 javax.jms.JMSException: Error creating connection: The following SASL 
 mechanisms [PLAIN] specified by the client are not supported by the broker
   at 
 org.apache.qpid.client.AMQConnectionFactory.createConnection(AMQConnectionFactory.java:286)
 Used JNDI/JMS configuration:
 java.naming.factory.initial = 
 org.apache.qpid.jndi.PropertiesFileInitialContextFactory
 connectionfactory.qpidConnectionfactory = 
 amqp://guest:guest@clientid/abcd?brokerlist='tcp://localhost:5672'
 destination.mainSend = direct://amq.direct//step.01
 It worked just fine in 0.6 but no success now in 0.8. 
 The broker is from Contributed C++ Packages - Windows Installer 
 (http://www.riverace.com/qpid/qpidc-0.8-x86.msi)
 Logs from qpidd:
 C:Program Filesapache-qpidc-0.8binqpidd --auth no --log-enable info+ 
 --log-enable trace+:amqp_0_10
 2010-12-15 11:42:48 info Management enabled
 2010-12-15 11:42:48 notice SASL disabled: No Authentication Performed
 2010-12-15 11:42:48 info Policy file not specified. ACL Disabled, no ACL 
 checking being done!
 2010-12-15 11:42:48 error Failed to initialise SSL listener: The credentials 
 supplied to the package were not recognized (cpps
 rcqpidbrokerwindowsSslProtocolFactory.cpp:177)
 2010-12-15 11:42:48 notice Listening on TCP port 5672
 5672
 2010-12-15 11:42:48 notice Broker running
 2010-12-15 11:42:53 trace SENT 127.0.0.1:1786 INIT(0-10)
 2010-12-15 11:42:53 trace SENT [127.0.0.1:1786]: Frame[BEbe; channel=0; 
 {ConnectionStartBody: server-properties={qpid.federation_tag:V2:36:s
 tr16(96790865-dc5c-427a-affe-70d021653737)}; 
 mechanisms=str16{V2:9:str16(ANONYMOUS)}; locales=str16{V2:5:str16(en_US)}; }]
 Run it with the -t option:
 2010-12-15 11:45:56 trace SEND raiseEvent (v1) 
 class=org.apache.qpid.broker.clientDisconnect
 2010-12-15 11:46:01 debug RECV [127.0.0.1:1794] INIT(0-10)
 2010-12-15 11:46:01 trace SENT 127.0.0.1:1794 INIT(0-10)
 2010-12-15 11:46:01 trace SENT [127.0.0.1:1794]: Frame[BEbe; channel=0; 
 {ConnectionStartBody: server-properties={qpid.federation_tag:V2:36:s
 tr16(96790865-dc5c-427a-affe-70d021653737)}; 
 mechanisms=str16{V2:9:str16(ANONYMOUS)}; locales=str16{V2:5:str16(en_US)}; }]
 2010-12-15 11:46:01 debug DISCONNECTED [127.0.0.1:1794]
 2010-12-15 11:46:01 trace SEND raiseEvent (v1) 
 class=org.apache.qpid.broker.clientDisconnect 

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira



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

[jira] Commented: (QPID-2979) The following SASL mechanisms [PLAIN] specified by the client are not supported by the broker


[ 
https://issues.apache.org/jira/browse/QPID-2979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12998883#comment-12998883
 ] 

Gordon Sim commented on QPID-2979:
--

A further question is why the 0-10 codepath defaults to only accepting PLAIN 
rather than allowing the underlying Sasl implementation to determine what is 
available (when no user defined preferences or restrictions are specified)?

 The following SASL mechanisms [PLAIN] specified by the client are not 
 supported by the broker
 -

 Key: QPID-2979
 URL: https://issues.apache.org/jira/browse/QPID-2979
 Project: Qpid
  Issue Type: Bug
  Components: C++ Broker, Java Client
Affects Versions: 0.8
 Environment: Windows XP
Reporter: Ibisek
 Fix For: Future

 Attachments: sasl-anonymous-java-client.patch


 An exception is thrown when connecting from a Java client (v 0.8) to qpidd (v 
 0.8) run with --auth no.
 javax.jms.JMSException: Error creating connection: The following SASL 
 mechanisms [PLAIN] specified by the client are not supported by the broker
   at 
 org.apache.qpid.client.AMQConnectionFactory.createConnection(AMQConnectionFactory.java:286)
 Used JNDI/JMS configuration:
 java.naming.factory.initial = 
 org.apache.qpid.jndi.PropertiesFileInitialContextFactory
 connectionfactory.qpidConnectionfactory = 
 amqp://guest:guest@clientid/abcd?brokerlist='tcp://localhost:5672'
 destination.mainSend = direct://amq.direct//step.01
 It worked just fine in 0.6 but no success now in 0.8. 
 The broker is from Contributed C++ Packages - Windows Installer 
 (http://www.riverace.com/qpid/qpidc-0.8-x86.msi)
 Logs from qpidd:
 C:Program Filesapache-qpidc-0.8binqpidd --auth no --log-enable info+ 
 --log-enable trace+:amqp_0_10
 2010-12-15 11:42:48 info Management enabled
 2010-12-15 11:42:48 notice SASL disabled: No Authentication Performed
 2010-12-15 11:42:48 info Policy file not specified. ACL Disabled, no ACL 
 checking being done!
 2010-12-15 11:42:48 error Failed to initialise SSL listener: The credentials 
 supplied to the package were not recognized (cpps
 rcqpidbrokerwindowsSslProtocolFactory.cpp:177)
 2010-12-15 11:42:48 notice Listening on TCP port 5672
 5672
 2010-12-15 11:42:48 notice Broker running
 2010-12-15 11:42:53 trace SENT 127.0.0.1:1786 INIT(0-10)
 2010-12-15 11:42:53 trace SENT [127.0.0.1:1786]: Frame[BEbe; channel=0; 
 {ConnectionStartBody: server-properties={qpid.federation_tag:V2:36:s
 tr16(96790865-dc5c-427a-affe-70d021653737)}; 
 mechanisms=str16{V2:9:str16(ANONYMOUS)}; locales=str16{V2:5:str16(en_US)}; }]
 Run it with the -t option:
 2010-12-15 11:45:56 trace SEND raiseEvent (v1) 
 class=org.apache.qpid.broker.clientDisconnect
 2010-12-15 11:46:01 debug RECV [127.0.0.1:1794] INIT(0-10)
 2010-12-15 11:46:01 trace SENT 127.0.0.1:1794 INIT(0-10)
 2010-12-15 11:46:01 trace SENT [127.0.0.1:1794]: Frame[BEbe; channel=0; 
 {ConnectionStartBody: server-properties={qpid.federation_tag:V2:36:s
 tr16(96790865-dc5c-427a-affe-70d021653737)}; 
 mechanisms=str16{V2:9:str16(ANONYMOUS)}; locales=str16{V2:5:str16(en_US)}; }]
 2010-12-15 11:46:01 debug DISCONNECTED [127.0.0.1:1794]
 2010-12-15 11:46:01 trace SEND raiseEvent (v1) 
 class=org.apache.qpid.broker.clientDisconnect 

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira



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

[jira] Assigned: (QPID-2385) Qpid C++ broker: delivery property


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

Gordon Sim reassigned QPID-2385:


Assignee: Gordon Sim

 Qpid C++ broker: delivery property 
 ---

 Key: QPID-2385
 URL: https://issues.apache.org/jira/browse/QPID-2385
 Project: Qpid
  Issue Type: Bug
  Components: C++ Broker
 Environment: Red Hat Enterprise MRG 1.2
Reporter: Armin Noll
Assignee: Gordon Sim
Priority: Minor

 Consider the following scenario:
 - start two clustered brokers (B1 and B2) with durable queue Q and durable 
 topic exchange E (the configuration of queues, exchanges and bindings must be 
 persistent)
 - create binding between Q and E for all messages
 - start a consumer application C, connect it to B2, waiting for messages in 
 queue Q
 - start a publisher application P, connect it to B1, start continuous message 
 transfer to exchange E
 - stop broker B2
 - P is still connected to B1 and is publishing messages
 - start broker B2
 - reconnect C to B2
 The first N messages received by C after the reconnect are missing the 
 delivery property exchange.
 This problem has also been reported as Red Hat service request #1991690.

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira



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

[jira] Assigned: (QPID-3003) By inspection looks like there is an error in qpid/python/messaging/message.py


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

Gordon Sim reassigned QPID-3003:


Assignee: Rafael H. Schloming

 By inspection looks like there is an error in qpid/python/messaging/message.py
 --

 Key: QPID-3003
 URL: https://issues.apache.org/jira/browse/QPID-3003
 Project: Qpid
  Issue Type: Bug
  Components: Python Client
Reporter: Andrew Stitcher
Assignee: Rafael H. Schloming

 On trunk version r1059846:
 There appears to be an error in this map initialisation (line 40):
 TYPE_MAPPINGS={
   dict: amqp/map,
   list: amqp/list,
 HERE:
   unicode: text/plain; charset=utf8,
   unicode: text/plain,
 ^^^
 [Seems to be a duplicate entry for unicode]
   buffer: None,
   str: None,
   None.__class__: None
   }

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira



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

[jira] Assigned: (QPID-2643) trunk build failed under VS10 x64.


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

Gordon Sim reassigned QPID-2643:


Assignee: Chuck Rolke

 trunk build failed  under VS10 x64.
 ---

 Key: QPID-2643
 URL: https://issues.apache.org/jira/browse/QPID-2643
 Project: Qpid
  Issue Type: Bug
  Components: C++ Broker
Affects Versions: 0.7
 Environment: visual studio 2010 c++ express
Reporter: Jinius
Assignee: Chuck Rolke
Priority: Minor
  Labels: vs10, win64
 Fix For: 0.9


 nmake compile failed at 
 C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\INCLUDE\iterator(142) 
 : error C2039: 'value_type' : is not a memb
 er of 'qpid::framing::List'
 C:\A.svn_qpid\cpp\include\qpid/framing/List.h(40) : see declaration 
 of 'qpid::framing::List'
 C:\A.svn_qpid\cpp\src\qpid\amqp_0_10\Codecs.cpp(51) : see reference 
 to class template instantiation 'std::insert
 _iterator_Container' being compiled
 with
 [
 _Container=qpid::framing::List
 ]
 C:\svn_qpid\cpp\src\qpid\amqp_0_10\Codecs.cpp(83) : see reference to 
 function template instantiation 'void qpi
 d::amqp_0_10::convertqpid::types::Variant::List,qpid::framing::List,boost::shared_ptrT(__cdecl
  *)(const qpid::types::
 Variant )(const std::list_Ty ,U ,F)' being compiled
 with
 [
 T=qpid::framing::FieldValue,
 _Ty=qpid::types::Variant,
 U=qpid::framing::List,
 F=boost::shared_ptrqpid::framing::FieldValue (__cdecl *)(const 
 qpid::types::Variant )
 ]
 C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\INCLUDE\iterator(149) 
 : error C2182: '_Val' : illegal use of type
  'void'
 C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\INCLUDE\iterator(156) 
 : error C2182: '_Val' : illegal use of type
  'void'
 NMAKE : fatal error U1077: 'C:\PROGRA~2\MICROS~1.0\VC\bin\cl.exe' : return 
 code '0x2'
 Stop.
 NMAKE : fatal error U1077: 'C:\Program Files (x86)\Microsoft Visual Studio 
 10.0\VC\BIN\nmake.exe' : return code '0x2'
 Stop.
 NMAKE : fatal error U1077: 'C:\Program Files (x86)\Microsoft Visual Studio 
 10.0\VC\BIN\nmake.exe' : return code '0x2'

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira



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

[jira] Assigned: (QPID-2368) Exception Thrown at qpid/sys/epoll/EpollPoller.cpp:254 Leaves Orphan File Descriptor


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

Gordon Sim reassigned QPID-2368:


Assignee: Andrew Stitcher

 Exception Thrown at qpid/sys/epoll/EpollPoller.cpp:254 Leaves Orphan File 
 Descriptor
 

 Key: QPID-2368
 URL: https://issues.apache.org/jira/browse/QPID-2368
 Project: Qpid
  Issue Type: Bug
  Components: C++ Client
Affects Versions: 0.5
 Environment: c++ client
Reporter: Jason Schlauch
Assignee: Andrew Stitcher
Priority: Minor

 While researching JIRA QPID-2367 I noticed a pileup of file descriptors in 
 /proc/PID/fd.  I traced the creation of these descriptors back to this chunk 
 of code in qpid/sys/epoll/EpollPoller.cpp:
 244 PollerPrivate() :
 245 epollFd(::epoll_create(DefaultFds)),
 246 isShutdown(false) {
 247 QPID_POSIX_CHECK(epollFd);
 248 ::sigemptyset(sigMask);
 249 // Add always readable fd into our set (but not listening to it 
 yet)
 250 ::epoll_event epe;
 251 epe.events = 0;
 252 epe.data.u64 = 0;
 253 QPID_POSIX_CHECK(::epoll_ctl(epollFd, EPOLL_CTL_ADD, 
 alwaysReadableFd, epe));
 254 }
 The problem is with the second QPID_POSIX_CHECK -- a macro that throws an 
 exception.  If an exception is thrown then the file descriptor allocated by 
 epollFd(::epoll_create(DefaultFds)) is left dangling.  A ::close(epollFd) 
 would be needed in the catch() block to free it.  
 There are a number of functions with a similar design in EpollPoller.cpp that 
 might be similarly affected.

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira



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

Default assignees by component

2011-02-24 Thread Justin Ross

Hi, everyone.  Is it possible to configure our jira instance to assign 
jiras to component owners when no explicit assignee is given?


I ask because I've recently been looking at ways to clean up our jira 
database.  One big problem stands out: many open issues are unassigned, 
and they often remain that way for more than a year.


It's my hope that having a single default assignee for each component, 
someone who can then reassign the issue as needed, will help these jiras 
get the attention they deserve.


Justin


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

[jira] Assigned: (QPID-2367) Early Initialization of File Descriptors Conflicts With Daemon Best Practices

2011-02-24 Thread Andrew Stitcher (JIRA)


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

Andrew Stitcher reassigned QPID-2367:
-

Assignee: Andrew Stitcher

 Early Initialization of File Descriptors Conflicts With Daemon Best Practices
 -

 Key: QPID-2367
 URL: https://issues.apache.org/jira/browse/QPID-2367
 Project: Qpid
  Issue Type: Improvement
  Components: C++ Client
Affects Versions: 0.5
 Environment: Linux (possibly all UNIX), c++, g++
Reporter: Jason Schlauch
Assignee: Andrew Stitcher

 At least one file descriptor (in qpid/sys/epoll/EpollPoller.*) in the c++ 
 client is global and declared as static.  In programs linked against the c++ 
 qpid libs g++ generates code for allocation and, more importantly, 
 initialization of these descriptors that occurs before main().  You can 
 confirm this with gdb by breakpointing both the initialization and main() 
 (the initialization break is hit first).
 On the other hand, the canonical recipe for creating a UNIX daemon calls for 
 the closing of all open file descriptors after fork()ing (where the fork() 
 certainly occurs after main()).  While not an absolute requirement, closing 
 all open file descriptors is considered a best practice.  A loop to close all 
 descriptors is also common in boilerplate daemon creation code and has 
 undoubtedly been cut-and-pasted into numerous daemons.
 The net effect is that the typical daemon will close the file descriptor 
 opened before main() in the c++ client library.  In the case of the epoll 
 code this manifests as an inability to connect to the broker.
 A fix for this would be to defer the initialization of the file descriptor 
 (perhaps via the Singleton pattern or a move of the variables into a class 
 member).

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira



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

[jira] Created: (QPID-3083) C++ Windows Build is looking for 'qpid/framing/constants.h', but that file is not in the distribution at that location

C++ Windows Build is looking for 'qpid/framing/constants.h', but that file is 
not in the distribution at that location
--

 Key: QPID-3083
 URL: https://issues.apache.org/jira/browse/QPID-3083
 Project: Qpid
  Issue Type: Bug
  Components: Build Tools, C++ Broker, C++ Client, C++ Clustering
Affects Versions: 0.8
 Environment: Windows 7 OS, MS Visual Studio 2008, CMake, Ruby, Python
Reporter: David Hickerson


qpid/Exception.h:  #include qpid/framing/constants.h 
in the cpp portion of the Full Source Distribution of the 0.8 source, 
constants.h does not exist at that location. One was found at 
qpid-0.8\cpp\src\qpid\replication , but it is not clear as to if that was the 
intended file.

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira



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

[jira] Created: (QPID-3084) Cluster may hang during update if asynchronous completion is pending.

2011-02-24 Thread Ken Giusti (JIRA)

Cluster may hang during update if asynchronous completion is pending.
-

 Key: QPID-3084
 URL: https://issues.apache.org/jira/browse/QPID-3084
 Project: Qpid
  Issue Type: Bug
  Components: C++ Clustering
Affects Versions: 0.9
Reporter: Ken Giusti
Assignee: Ken Giusti
 Fix For: 0.9


During an update of a newly joined broker, io processing requests are held off. 
 Asynchronous command completion requires io processing in order to complete 
asynchronous operations.  If any async commands are pending completion during 
the update, they may not complete and cause the cluster to hang.  This may be 
cause by store or during queue flow control. 

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira



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

[jira] Created: (QPID-3085) C++ Windows Build is looking for 'qpid/framing/MessageProperties.h', but that file is not in the distribution at that location

C++ Windows Build is looking for 'qpid/framing/MessageProperties.h', but that 
file is not in the distribution at that location
--

 Key: QPID-3085
 URL: https://issues.apache.org/jira/browse/QPID-3085
 Project: Qpid
  Issue Type: Bug
  Components: Build Tools, C++ Broker, C++ Client, C++ Clustering
Affects Versions: 0.8
 Environment: Windows 7 OS, MS Visual Studio 2008, CMake, Ruby, Python
Reporter: David Hickerson


qpid/Exception.h:  #include qpid/framing/constants.h 
in the cpp portion of the Full Source Distribution of the 0.8 source, 
constants.h does not exist at that location. One was found at 
qpid-0.8\cpp\src\qpid\replication , but it is not clear as to if that was the 
intended file.

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira



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

[jira] Resolved: (QPID-3084) Cluster may hang during update if asynchronous completion is pending.

2011-02-24 Thread Ken Giusti (JIRA)


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

Ken Giusti resolved QPID-3084.
--

Resolution: Fixed

Alan Conway has provided the fix for this bug.

 Cluster may hang during update if asynchronous completion is pending.
 -

 Key: QPID-3084
 URL: https://issues.apache.org/jira/browse/QPID-3084
 Project: Qpid
  Issue Type: Bug
  Components: C++ Clustering
Affects Versions: 0.9
Reporter: Ken Giusti
Assignee: Ken Giusti
 Fix For: 0.9


 During an update of a newly joined broker, io processing requests are held 
 off.  Asynchronous command completion requires io processing in order to 
 complete asynchronous operations.  If any async commands are pending 
 completion during the update, they may not complete and cause the cluster to 
 hang.  This may be cause by store or during queue flow control. 

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira



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

[jira] Updated: (QPID-3085) C++ Windows Build is looking for 'qpid/framing/MessageProperties.h', but that file is not in the distribution at that location


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

David Hickerson updated QPID-3085:
--

Description: 
qpid/client/Message.h:  #include qpid/framing/MessageProperties.h 
in the cpp portion of the Full Source Distribution of the 0.8 source, 
MessageProperties.h does not exist at that location. 

  was:
qpid/Exception.h:  #include qpid/framing/constants.h 
in the cpp portion of the Full Source Distribution of the 0.8 source, 
constants.h does not exist at that location. One was found at 
qpid-0.8\cpp\src\qpid\replication , but it is not clear as to if that was the 
intended file.


 C++ Windows Build is looking for 'qpid/framing/MessageProperties.h', but that 
 file is not in the distribution at that location
 --

 Key: QPID-3085
 URL: https://issues.apache.org/jira/browse/QPID-3085
 Project: Qpid
  Issue Type: Bug
  Components: Build Tools, C++ Broker, C++ Client, C++ Clustering
Affects Versions: 0.8
 Environment: Windows 7 OS, MS Visual Studio 2008, CMake, Ruby, Python
Reporter: David Hickerson
  Labels: build
   Original Estimate: 24h
  Remaining Estimate: 24h

 qpid/client/Message.h:  #include qpid/framing/MessageProperties.h 
 in the cpp portion of the Full Source Distribution of the 0.8 source, 
 MessageProperties.h does not exist at that location. 

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira



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

[jira] Commented: (QPID-3083) C++ Windows Build is looking for 'qpid/framing/constants.h', but that file is not in the distribution at that location

2011-02-24 Thread Chuck Rolke (JIRA)

[
https://issues.apache.org/jira/browse/QPID-3083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12999105#comment-12999105
]

Chuck Rolke commented on QPID-3083:
---

The file is not part of the source kit. It is generated when you run CMake.

When you run CMake from a given directory, say dir, it will produce file
dir\qpid-cpp.sln.
Then from there CMake will produce dir\include\qpid\framing\constants.h.

When I first started on this project I was running CMake in the qpid\cpp
directory. This works
for just one platform, say x86, but fails if you try to build a second platform
like x64. Lately
I run CMake from a directory under qpid\ to be a peer directory of qpid\cpp.
Usually I create
qpid\b32 and qpid\b64 to build 32-bit and 64-bit variants.

So if you can get CMake to work your constants.h file will be generated in a
directory relative
to where CMake ran.

C++ Windows Build is looking for 'qpid/framing/constants.h', but that file is
not in the distribution at that location
--

Key: QPID-3083
URL: https://issues.apache.org/jira/browse/QPID-3083
Project: Qpid
Issue Type: Bug
Components: Build Tools, C++ Broker, C++ Client, C++ Clustering
Affects Versions: 0.8
Environment: Windows 7 OS, MS Visual Studio 2008, CMake, Ruby, Python
Reporter: David Hickerson
Labels: build
Original Estimate: 24h
Remaining Estimate: 24h

qpid/Exception.h: #include qpid/framing/constants.h
in the cpp portion of the Full Source Distribution of the 0.8 source,
constants.h does not exist at that location. One was found at
qpid-0.8\cpp\src\qpid\replication , but it is not clear as to if that was the
intended file.

--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

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

[jira] Commented: (QPID-3085) C++ Windows Build is looking for 'qpid/framing/MessageProperties.h', but that file is not in the distribution at that location

2011-02-24 Thread Chuck Rolke (JIRA)


[ 
https://issues.apache.org/jira/browse/QPID-3085?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12999109#comment-12999109
 ] 

Chuck Rolke commented on QPID-3085:
---

Please see QPID-3083 for description of where the file comes from.

Also, please see file qpid\cpp\bindings\qpid\dotnet\configure-windows.ps1 for a 
script designed for Windows to get 32-bit and 64-bit out-of-source build trees 
started. Even if you don't run the script to create out-of-source built trees 
you can read the commentary to understand the build environment a little more 
or to see example CMake command lines.

 C++ Windows Build is looking for 'qpid/framing/MessageProperties.h', but that 
 file is not in the distribution at that location
 --

 Key: QPID-3085
 URL: https://issues.apache.org/jira/browse/QPID-3085
 Project: Qpid
  Issue Type: Bug
  Components: Build Tools, C++ Broker, C++ Client, C++ Clustering
Affects Versions: 0.8
 Environment: Windows 7 OS, MS Visual Studio 2008, CMake, Ruby, Python
Reporter: David Hickerson
  Labels: build
   Original Estimate: 24h
  Remaining Estimate: 24h

 qpid/client/Message.h:  #include qpid/framing/MessageProperties.h 
 in the cpp portion of the Full Source Distribution of the 0.8 source, 
 MessageProperties.h does not exist at that location. 

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira



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

[jira] Commented: (QPID-3083) C++ Windows Build is looking for 'qpid/framing/constants.h', but that file is not in the distribution at that location


[ 
https://issues.apache.org/jira/browse/QPID-3083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12999155#comment-12999155
 ] 

David Hickerson commented on QPID-3083:
---

I ran cmake -i under the quip\cpp like what was stated in the INSTALL-WINDOWS 
file, but did get this cmake error:
CMake Error at src/CMakeLists.txt:224 (include):
  include could not find load file:

C:/dev/tools/Qpid/qpid-0.8/cpp/src/rubygen.cmake

I had read the wiki stating that the cmake build method was not finished and 
had got project files out of the cmake -i, so I assumed that was an in work 
issue that did not affect the current build. 

rubygen.cmake is no where in the distro, so I assume that is the real issue 
here.

 C++ Windows Build is looking for 'qpid/framing/constants.h', but that file is 
 not in the distribution at that location
 --

 Key: QPID-3083
 URL: https://issues.apache.org/jira/browse/QPID-3083
 Project: Qpid
  Issue Type: Bug
  Components: Build Tools, C++ Broker, C++ Client, C++ Clustering
Affects Versions: 0.8
 Environment: Windows 7 OS, MS Visual Studio 2008, CMake, Ruby, Python
Reporter: David Hickerson
  Labels: build
   Original Estimate: 24h
  Remaining Estimate: 24h

 qpid/Exception.h:  #include qpid/framing/constants.h 
 in the cpp portion of the Full Source Distribution of the 0.8 source, 
 constants.h does not exist at that location. One was found at 
 qpid-0.8\cpp\src\qpid\replication , but it is not clear as to if that was the 
 intended file.

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira



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

[jira] Commented: (QPID-3085) C++ Windows Build is looking for 'qpid/framing/MessageProperties.h', but that file is not in the distribution at that location