date:20090317


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

Robert Gemmell closed QPID-1570.


   Resolution: Won't Fix
Fix Version/s: (was: Eclipse MC M5)

The mentioned code was tidied up a little, but as per the comments above the 
functionality cant/wont be changed and is now only used for backwards 
compatibility..

 JMXConnectionFactory exception handling code is fragile
 ---

 Key: QPID-1570
 URL: https://issues.apache.org/jira/browse/QPID-1570
 Project: Qpid
  Issue Type: Bug
  Components: Java Management : CLI Tool, Java Management : JMX Console
Reporter: Aidan Skinner

 Split off from QPID-1522:
 Rob Godfrey:
 JMXConnectionFactory:
 The code which looks at the exception text seems remarkable fragile to me... 
 At the very least I would expect some constants which could be shared with 
 the code that throws the exception.
 Robbie Gemmell:
 Hi Rob,
 I wrote that bit originally. It is somewhat fragile, but unfortunately having 
 looked at the code that generates the exceptions i didnt think there was much 
 else i could do. The exception is generated by code within the optional JMXMP 
 addon (jmxremote_optional.jar) and just directly throws an IOException like 
 so:
 throw new IOException(The server supported profiles  +
 serverProfilesList +  do not  +
 match the client required profiles  +
 clientProfilesList + .);
 so there are no constants to match against (though granted i should possibly 
 still have used constants for my own bit).
 I have a secure RMI based JMX setup ready to go, so we can remove the 
 user-unfriendly/slightly-proprietary JMXMP stuff in future if desired (I know 
 Aidan wants to :P), and if so then that section of code should only really 
 ever be getting used for connecting to older brokers if they have used the 
 JMXMP based solution, which it seems that at the moment many dont, given how 
 guff the console was in that area.

-- 
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-1742) improve splash screen description

improve splash screen description
-

 Key: QPID-1742
 URL: https://issues.apache.org/jira/browse/QPID-1742
 Project: Qpid
  Issue Type: Improvement
  Components: Java Management : JMX Console
Affects Versions: M4, M3, M2.1
Reporter: Robert Gemmell
Assignee: Robert Gemmell
Priority: Trivial
 Fix For: Eclipse MC M5


The JMX management console's splash screen could be more descriptive, saying 
that it uses JMX to distinguish it from any future QMF efforts, and signalling 
that it is only for the 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] Updated: (QPID-1653) add ability to dump queue/message content to a file via JMX


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

Robert Gemmell updated QPID-1653:
-

Fix Version/s: (was: Eclipse MC M5)

 add ability to dump queue/message content to a file via JMX
 ---

 Key: QPID-1653
 URL: https://issues.apache.org/jira/browse/QPID-1653
 Project: Qpid
  Issue Type: New Feature
  Components: Java Broker, Java Management : JMX Console
Reporter: Robert Gemmell
Priority: Minor

 It would be useful to be able to dump queue/message content to a file using 
 the mangement console.
 Some initial discussion on the topic from partychat:
 (4:41:20 PM) Robbie: just considering the message/queue dump to file feature
 (4:41:53 PM) Robbie: i was wondering...any thoughts on the best approach for 
 tackling binary content ?
 (4:42:30 PM) Robbie: since it may or may not be mixed in with plain text 
 messages
 (4:43:22 PM) Robbie: i think thinking maybe go with hex output..?
 (4:43:32 PM) Robbie: *was thinking
 (4:43:40 PM) partych...@gmail.com: [Martin] binary file?
 (4:44:05 PM) Robbie: what about the text messages then ?:)
 (4:44:06 PM) partych...@gmail.com: [Martin] The Messae/queue dump feature  
 was it to be readable?
 (4:44:23 PM) Robbie: hmm, good point...i just asumed so
 snip
 (4:45:45 PM) partych...@gmail.com: [Martin] Is it couple with a 
 message/queue load?
 (4:45:52 PM) partych...@gmail.com: [Martin] s/couple/coupled/
 (4:45:52 PM) partych...@gmail.com: Martin meant Is it coupled with a 
 message/queue load?
 (4:46:02 PM) Robbie: nope
 (4:46:20 PM) partych...@gmail.com: [aidan] i would say leave the contents 
 alone and dump the bit stream. I might have a zip or something i want to get 
 out of the message that I don't want to de-hexify
 (4:46:24 PM) Robbie: i dot eall have any mroe background on it than what i 
 just said above hehe
 (4:46:44 PM) Robbie: *dont really
 (4:47:06 PM) partych...@gmail.com: [Martin] I'd say dump like the MC viewer 
 :  | ASCII | HEX |
 (4:47:42 PM) Robbie: my original thoughts were to be putting out some of the 
 header info, then the contents.lather, rinse and repeat
 (4:47:58 PM) partych...@gmail.com: [aidan] the viewer is a somewhat 
 different use case IMO
 (4:48:13 PM) partych...@gmail.com: [Martin] Take a look at the 
 MessasgeStore Tool ... it does some thing similar.. but only dumps to the 
 screen
 (4:48:37 PM) Robbie: k
 (4:48:59 PM) partych...@gmail.com: [aidan] yeah, see, in the case of the 
 message store tool I think the intention is to get something human-readable
 (4:49:08 PM) partych...@gmail.com: [aidan] same as with view-message in the 
 console
 (4:49:26 PM) partych...@gmail.com: [aidan] but with dump to disk you might 
 want to do a number of things with the message
 (4:49:36 PM) partych...@gmail.com: [aidan] that require the origional 
 message contents
 (4:49:49 PM) partych...@gmail.com: [Martin] but without a load it seems a 
 bit odd
 (4:50:03 PM) partych...@gmail.com: [Martin] I'd expect dump , fix issue, 
 load
 (4:50:09 PM) Robbie: i think maybe we need a marnie:ping to decide futher :)
 (4:50:24 PM) Robbie: well, load isnt out of the question, it was jsut never 
 mentioned is all :)
 (4:50:24 PM) partych...@gmail.com: [aidan] file a jira and attach this 
 conversation to it?
 (4:50:36 PM) partych...@gmail.com: [rob] i'd not worry about load just yet
 (4:50:40 PM) Robbie: k
 (4:50:48 PM) partych...@gmail.com: [aidan] load gets rather more messy
 (4:50:52 PM) partych...@gmail.com: [rob] indeed
 snip
 (4:51:01 PM) partych...@gmail.com: [rob] it breaks lots of important 
 properties of the model as well
 snip
 (4:51:30 PM) partych...@gmail.com: [aidan] but I can see a use case of 
 something like i need this humongous archive out of my queue so I can put it 
 on an ftp server
 snip
 (4:51:43 PM) partych...@gmail.com: [aidan] and having to de-MIME it first 
 would irritate me
 (4:52:00 PM) Robbie: ;)
 (4:52:09 PM) partych...@gmail.com: [rob] The most likely thing is going to 
 be this message keeps breaking my application what's in the message I 
 don't know - whenever I try to get it it breaks my application
 snip
 (4:52:52 PM) partych...@gmail.com: [aidan] rob: indeed, and if the message 
 is a bitstream it should probably stay a bitstream
 snip
 (4:53:03 PM) partych...@gmail.com: [rob] yes - you want to have the option
 (4:53:22 PM) partych...@gmail.com: [rob] ideally we'd like to have a way to 
 deserialize the different java message types
 (4:53:32 PM) partych...@gmail.com: [rob] you also want to get the headers - 
 separate from the file content
 (4:55:07 PM) Robbie: k

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


-
Apache

[jira] Assigned: (QPID-1742) improve splash screen description


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

Robert Gemmell reassigned QPID-1742:


Assignee: Martin Ritchie  (was: Robert Gemmell)

Hi Martin, can you review this change please, thanks.

 improve splash screen description
 -

 Key: QPID-1742
 URL: https://issues.apache.org/jira/browse/QPID-1742
 Project: Qpid
  Issue Type: Improvement
  Components: Java Management : JMX Console
Affects Versions: M2.1, M3, M4
Reporter: Robert Gemmell
Assignee: Martin Ritchie
Priority: Trivial
 Fix For: Eclipse MC M5


 The JMX management console's splash screen could be more descriptive, saying 
 that it uses JMX to distinguish it from any future QMF efforts, and 
 signalling that it is only for the 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] Updated: (QPID-1742) improve splash screen description


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

Robert Gemmell updated QPID-1742:
-

Status: Ready To Review  (was: In Progress)

 improve splash screen description
 -

 Key: QPID-1742
 URL: https://issues.apache.org/jira/browse/QPID-1742
 Project: Qpid
  Issue Type: Improvement
  Components: Java Management : JMX Console
Affects Versions: M2.1, M3, M4
Reporter: Robert Gemmell
Assignee: Robert Gemmell
Priority: Trivial
 Fix For: Eclipse MC M5


 The JMX management console's splash screen could be more descriptive, saying 
 that it uses JMX to distinguish it from any future QMF efforts, and 
 signalling that it is only for the 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

Re: Java broker clustering (was: RE: want to contribute ;) )

2009-03-17 Thread Etienne Antoniutti Di Muro

Hi Marnie,

you've got everything, perfectly!

I was just trying to sum up, previous discussions:

The idea of borrowing some existing components, i.e. the virtual
sync implementation,
from the C++ clustering has been suggested, in order to keep a compact
codebase and
minimize maintenance.
However we are fully in sync that having a mixed java and C++ implementation
might be a big PRO from an architectural point of view,
but is a big CON for a working approach
Plus you are right, cluster set up is a mayhem that exponentially
grows with the cluster dimension,
so this would raise deployment issues to the N power.

I see your point about HA,
but from a theoretical point of view HA without RELIABILITY is quite pointless,
moreover you can have BOTH with not much extra spending.
Depending on the proper configuration of the cluster,
scalability and throughput can be maximized, with respect to the
available cluster nodes,
at the same time ensuring reliability inherited from the virtual
synchrony paradigm.
The trade off is the need to setup a number of configuration parameters that can
become a cumbersome activity, unless some adaptation policy is defined to
help with static initialization and dynamic run time system adjustments.

I'm quite new to this list, how can we set up an open discussion ?
Just the list ? Jira ? What else ?

Regards,
Etienne


On Tue, Mar 17, 2009 at 11:14 AM, Marnie McCormack
marnie.mccorm...@googlemail.com wrote:
 Hi Etienne,

 I'm not sure I entirely understand what you're proposing, so apologies if I
 have misunderstood 

 On Tue, Mar 17, 2009 at 9:19 AM, Etienne Antoniutti Di Muro 
 etienne.antoniu...@adaptivebytes.com wrote:

 Hello,

 having a mixed java - C++ implementation leads to the following
 (abridged version):


 So, you do really mean an implementation using both languages that could be
 used for clustering Java Brokers ?


 pros:
 - ease of maintenance;
 - compactness and organic architecture of the project,

 cons:
 - less portability;
 - building complexity and distribution

 This would be an important 'con' for our user community. Portability is
 pretty key, and some of the Java Broker deployments go out on a host of
 platforms at the moment (across 10s of machines). The need to produce a
 build for each would be a significant stumbling block for uptake imho.



 However these choices can be postponed to the design stage as for now we
 need to define basic clustering requirements.

 As food for thought, I'd suggest:

 - clustering for dependability: pretty obvious;
 - clustering and performance:  which trade-offs ?
 - clustering adaptability: at which level ?
 - adaptability policies: none /  some / mid - smart / zero policy
 (a.k.a ad hoc control theory) / autonomic ?

 Most of the traffic I get about clustering is really for HA, avoiding the
 need to start up a secondary broker and point it at the original persistent
 store. Our users want to avoid downtime. The Java Broker is pretty amenable
 to having several instances running to help with scalability, and throughput
 for transient mesasging is pretty good.


 Can we start a whiteboard discussion on this ?

 Definitely a good idea.


 Cheers,
 Etienne

 Regards,
 Marnie


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

[jira] Created: (QPID-1743) get/set maxMessageSize incorrectlydescribed as being in KB in ManagedQueue

get/set maxMessageSize incorrectlydescribed as being in KB in ManagedQueue
--

 Key: QPID-1743
 URL: https://issues.apache.org/jira/browse/QPID-1743
 Project: Qpid
  Issue Type: Bug
  Components: Java Broker
Affects Versions: M4, M3, M2.1
Reporter: Robert Gemmell
Assignee: Robert Gemmell
 Fix For: Eclipse MC M5


The get/set maxMessageSize methods are incorrectly described as operating in KB 
within ManagedQueue

-- 
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: [Action Required] [0.5] JIRA Review

2009-03-17 Thread Martin Ritchie

2009/3/16 Rajith Attapattu rajit...@gmail.com:
 The following JIRA's could be closed for M5.
 https://issues.apache.org/jira/browse/QPID-1645
 https://issues.apache.org/jira/browse/QPID-1720
 https://issues.apache.org/jira/browse/QPID-1713
 https://issues.apache.org/jira/browse/QPID-1692
 https://issues.apache.org/jira/browse/QPID-1609
 https://issues.apache.org/jira/browse/QPID-1677
 https://issues.apache.org/jira/browse/QPID-1106

 I am waiting for Rafi to comment on them.

 https://issues.apache.org/jira/browse/QPID-1544 should have been fixed
 by one of Rafi's commits.
 I will verify it and let resolve the JIRA.

 For https://issues.apache.org/jira/browse/QPID-1608 let me try to add
 in a test case by tomorrow and we could close this as well.

 Regards,

 Rajith

Thanks for the update Rajith. There are a lot of JIRAs there that do
not have 'Fix For' set to M5. Can you update this field and where the
work has been completed but awaiting feedback change the status to
'Ready for Review'.

Thanks
Martin

 On Mon, Mar 16, 2009 at 11:17 AM, Aidan Skinner ai...@apache.org wrote:
 On Mon, Mar 16, 2009 at 1:55 PM, Martin Ritchie ritch...@apache.org wrote:

 Could Aidan, Rafi, Rajith, Ted and myself please take a look at the
 issues and decide if they should be blocking 0.5 release or moved to
 the next release.

 I've descoped a few, of the remaining ones that are assigned to me and
 fix-for 0.5:

 QPID-1736 i'm testing a fix for just now
 QPID-1670 has been a problem for a while and while nice to get fixed
 probably doesn't block the release, if I don't get to it today it
 should just be bumped
 QPID-1652 I'll review today
 QPID-1626 I need to address your remarks

 - Aidan
 --
 Apache Qpid - World Domination through Advanced Message Queueing
 http://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





-- 
Martin Ritchie

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

[0.5] [Branch] [Code Freeze] Trunk now branched, code freeze lifted.

2009-03-17 Thread Martin Ritchie

Hi all,

I have just branched trunk to our 0.5-release branch.

If everyone can ensure that their JIRAs are in the correct state that
will ensure we can track how close we are to a final release state.
It will also make our release notes more complete.

For reference, work completed as part of 0.5 should be labelled 'Fix'
0.5, if the work was not completed and so is still outstanding then
'Affects' should be set to 0.5.

The process that I would like to follow for merging the remaining bug
fixes to 0.5-release is that the code is first committed to the new
0.5-release branch and then merged to trunk. If anyone is concerned
about a patch being included in 0.5 then we can discuss that as it
happens.

Finally the branching means that trunk is now free again for all development.

Cheers

Martin
-- 
Martin Ritchie

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

[jira] Updated: (QPID-1670) Errors thrown from onMessage can kill the dispatcher

2009-03-17 Thread Aidan Skinner (JIRA)

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

Aidan Skinner updated QPID-1670:

Description:
BasicMessageConsumer.notifyMessage catches Exception and handles it, but
unchecked throwables will cause the Dispatcher thread in the Session to
terminate after logging. It does not kill the session.

The JMS spec has this to say:
4.5.2 Asynchronous Delivery
A client can register an object that implements the JMS MessageListener
interface with a MessageConsumer. As messages arrive for the consumer, the
provider delivers them by calling the listener's onMessage method.
It is possible for a listener to throw a RuntimeException; however, this is
considered a client programming error. Well-behaved listeners should catch
such exceptions and attempt to divert messages causing them to some form of
application-specific 'unprocessable message' destination.
The result of a listener throwing a RuntimeException depends on the session's
acknowledgment mode.
• AUTO_ACKNOWLEDGE or DUPS_OK_ACKNOWLEDGE - the message
will be immediately redelivered. The number of times a JMS provider will
redeliver the same message before giving up is provider-dependent. The
JMSRedelivered message header field will be set for a message redelivered
under these circumstances.
• CLIENT_ACKNOWLEDGE - the next message for the listener is delivered.
If a client wishes to have the previous unacknowledged message
redelivered, it must manually recover the session.
• Transacted Session - the next message for the listener is delivered. The
client
can either commit or roll back the session (in other words, a
RuntimeException does not automatically rollback the session).
JMS providers should flag clients with message listeners that are throwing
RuntimeExceptions as possibly malfunctioning.

was:
BasicMessageConsumer.notifyMessage catches Exception and handles it, but
unchecked exceptions (eg. RuntimeException) will cause the Dispatcher thread in
the Session to terminate after logging. It does not kill the session.

Affects Version/s: 0.6
Fix Version/s: (was: 0.5)
Summary: Errors thrown from onMessage can kill the dispatcher
(was: runtime exceptions from onMessage can kill the dispatcher)

I was about to fix this, but we do actually handle RuntimeException properly.
What we don't handle are things that don't extend Exception, such as Error. I'm
not sure that we want to handle those this way though, death may be a more
appropriate response.

Errors thrown from onMessage can kill the dispatcher

Key: QPID-1670
URL: https://issues.apache.org/jira/browse/QPID-1670
Project: Qpid
Issue Type: Bug
Components: Java Client
Affects Versions: 0.5, 0.6
Reporter: Aidan Skinner
Assignee: Aidan Skinner
Priority: Blocker

BasicMessageConsumer.notifyMessage catches Exception and handles it, but
unchecked throwables will cause the Dispatcher thread in the Session to
terminate after logging. It does not kill the session.
The JMS spec has this to say:
4.5.2 Asynchronous Delivery
A client can register an object that implements the JMS MessageListener
interface with a MessageConsumer. As messages arrive for the consumer, the
provider delivers them by calling the listener's onMessage method.
It is

[jira] Created: (QPID-1744) Adding a new node to a cluster node that has recovered messages from disk fails.

2009-03-17 Thread Gordon Sim (JIRA)

Adding a new node to a cluster node that has recovered messages from disk fails.


 Key: QPID-1744
 URL: https://issues.apache.org/jira/browse/QPID-1744
 Project: Qpid
  Issue Type: Bug
  Components: C++ Broker
Affects Versions: M4
Reporter: Gordon Sim
Assignee: Gordon Sim
 Fix For: 0.5


Instead you get something like:

2009-mar-16 14:28:41 error Connection exception: framing-error: Unexpected
command start frame. (qpid/SessionState.cpp:57)

-- 
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-1744) Adding a new node to a cluster node that has recovered messages from disk fails.

2009-03-17 Thread Gordon Sim (JIRA)


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

Gordon Sim resolved QPID-1744.
--

Resolution: Fixed

Fixed on 0.5 branch as r755315 and on trunk as r755316.

 Adding a new node to a cluster node that has recovered messages from disk 
 fails.
 

 Key: QPID-1744
 URL: https://issues.apache.org/jira/browse/QPID-1744
 Project: Qpid
  Issue Type: Bug
  Components: C++ Broker
Affects Versions: M4
Reporter: Gordon Sim
Assignee: Gordon Sim
 Fix For: 0.5


 Instead you get something like:
 2009-mar-16 14:28:41 error Connection exception: framing-error: Unexpected
 command start frame. (qpid/SessionState.cpp:57)

-- 
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: svn commit: r755324 - /qpid/trunk/qpid/java/systests/src/main/java/org/apache/qpid/test/unit/client/connection/ConnectionCloseTest.java

2009-03-17 Thread Aidan Skinner

On Tue, Mar 17, 2009 at 5:09 PM,  r...@apache.org wrote:

 Author: rhs
 Date: Tue Mar 17 17:09:12 2009
 New Revision: 755324

 URL: http://svn.apache.org/viewvc?rev=755324view=rev
 Log:
 increased timeout for ConnectionCloseTest

 -            this.wait(1000);
 +            this.wait(1);

That's a long time. Are you seeing this fail often?

- Aidan

-- 
Apache Qpid - World Domination through Advanced Message Queueing
http://qpid.apache.org

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

[jira] Updated: (QPID-1550) C++ broker crashes periodically when handling connection closure


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

Steve Huston updated QPID-1550:
---

Attachment: AsynchIO.2.diff

The AsynchIO.diff I posted previously doesn't crash, but does leak memory. The 
new AsynchIO.2.diff appears to work correctly and not leak. I'm planning to 
commit this when I finish testing - please review/test and let me know of any 
issues.


 C++ broker crashes periodically when handling connection closure
 

 Key: QPID-1550
 URL: https://issues.apache.org/jira/browse/QPID-1550
 Project: Qpid
  Issue Type: Bug
  Components: C++ Broker
Affects Versions: M4
 Environment: Windows XP SP2, Visual Studio 2008 SP 1. .NET WCF client 
 (trunk)
Reporter: Robert Greig
Assignee: Steve Huston
 Fix For: 0.5

 Attachments: AsynchIO.2.diff, AsynchIO.diff, patch.1550, 
 qpid-broker-log.txt


 Periodically when running the .NET WCF client against the C++ broker running 
 on windows, the broker crashes.
 This occurs every 10 runs or thereabouts.
 Logs and stacks attached.

-- 
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-1625) C++ tests need Linux-isms changed to build on Windows

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

Steve Huston resolved QPID-1625.

Resolution: Fixed
Fix Version/s: 0.5

This was fixed and on trunk prior to the 0.5-release branch (it came in with
qpid-1673 DLL changes), so is good to go for 0.5.

C++ tests need Linux-isms changed to build on Windows
-

Key: QPID-1625
URL: https://issues.apache.org/jira/browse/QPID-1625
Project: Qpid
Issue Type: Improvement
Components: C++ Broker, C++ Client
Affects Versions: M4
Environment: Windows
Reporter: Steve Huston
Assignee: Steve Huston
Priority: Minor
Fix For: 0.5

A number of the qpid/cpp/src/tests sources contain #includes that don't work
on Windows. For example, alloca.h. In many cases, the referenced facilities
exist on Windows but are accessed slightly differently. For example, this
works on Windows where alloca.h is included:
#ifdef _WIN32
# include malloc.h
# define alloc _alloc
#else
# include alloca.h
#endif
I was thinking that, rather than add things to qpid/cpp/src/qpid/sys
(platform-specific code for broker and client) that a sys directory be added
to qpid/cpp/src/tests where things used just for the testing are placed. For
example, there could be a tests/sys/alloca.h which contains, essentially, the
ifdef block above.
Thoughts?

--
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

client::Connection::registerFailureCallback

2009-03-17 Thread Ted Ross

I want to use Connection::registerFailureCallback (in the client) to 
receive notification that my connection has been dropped.  I can find no 
use of this feature anywhere in the qpid c++ code.


My concern is that only one callback can be registered per connection.  
Subsequent registrations overwrite earlier ones.  Is this feature 
intended for a particular purpose or is it available for general use?  I 
don't want some future implementation to step on my callback (or vice 
versa).


Thanks,

-Ted


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

[jira] Assigned: (QPID-1537) Version the MBeans so we can maintain backward compatibility with new features


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

Robert Gemmell reassigned QPID-1537:


Assignee: Robert Gemmell

 Version the MBeans so we can maintain backward compatibility with new features
 --

 Key: QPID-1537
 URL: https://issues.apache.org/jira/browse/QPID-1537
 Project: Qpid
  Issue Type: Improvement
  Components: Java Broker
Affects Versions: M2, M2.1, M3, M4
Reporter: Martin Ritchie
Assignee: Robert Gemmell
 Attachments: QPID-1537_19feb2009.patch


 Summary:
 With the change to the UserManagementMBean to change the ensure that the 
 input is always plain text for the password we need to ensure we can still 
 send the hashed version with the older versions of the broker.
 Setting a version flag on the MBean will allow us to tell when to send what 
 value. It will also allow us to handle future changes.

-- 
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-1537) Version the MBeans so we can maintain backward compatibility with new features


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

Robert Gemmell updated QPID-1537:
-

Status: Ready To Review  (was: In Progress)

 Version the MBeans so we can maintain backward compatibility with new features
 --

 Key: QPID-1537
 URL: https://issues.apache.org/jira/browse/QPID-1537
 Project: Qpid
  Issue Type: Improvement
  Components: Java Broker
Affects Versions: M2, M2.1, M3, M4
Reporter: Martin Ritchie
Assignee: Robert Gemmell
 Fix For: 0.5

 Attachments: QPID-1537_19feb2009.patch


 Summary:
 With the change to the UserManagementMBean to change the ensure that the 
 input is always plain text for the password we need to ensure we can still 
 send the hashed version with the older versions of the broker.
 Setting a version flag on the MBean will allow us to tell when to send what 
 value. It will also allow us to handle future changes.

-- 
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-1568) JConsole/VisualVM unable to connect to broker when JMX RMI authentication and access control is used


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

Robert Gemmell updated QPID-1568:
-

Fix Version/s: 0.5
Affects Version/s: 0.5

 JConsole/VisualVM unable to connect to broker when JMX RMI authentication and 
 access control is used
 

 Key: QPID-1568
 URL: https://issues.apache.org/jira/browse/QPID-1568
 Project: Qpid
  Issue Type: Bug
  Components: Java Broker
Affects Versions: 0.5
Reporter: Robert Gemmell
Assignee: Robert Gemmell
 Fix For: 0.5

 Attachments: QPID-1568_11jan2009.patch


 When authentication and access control is added to the RMI based JMX 
 connector server used by the Java broker, management tools such as JConsole 
 and VisualVM are unable to remotely connect to the console. Logging output 
 from JConsole indicated that a connection is successfully established and 
 then immediatley closed.

-- 
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-1568) JConsole/VisualVM unable to connect to broker when JMX RMI authentication and access control is used


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

Robert Gemmell updated QPID-1568:
-

Status: Ready To Review  (was: In Progress)

 JConsole/VisualVM unable to connect to broker when JMX RMI authentication and 
 access control is used
 

 Key: QPID-1568
 URL: https://issues.apache.org/jira/browse/QPID-1568
 Project: Qpid
  Issue Type: Bug
  Components: Java Broker
Affects Versions: 0.5
Reporter: Robert Gemmell
Assignee: Robert Gemmell
 Fix For: 0.5

 Attachments: QPID-1568_11jan2009.patch


 When authentication and access control is added to the RMI based JMX 
 connector server used by the Java broker, management tools such as JConsole 
 and VisualVM are unable to remotely connect to the console. Logging output 
 from JConsole indicated that a connection is successfully established and 
 then immediatley closed.

-- 
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-1568) JConsole/VisualVM unable to connect to broker when JMX RMI authentication and access control is used


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

Robert Gemmell reassigned QPID-1568:


Assignee: Martin Ritchie  (was: Robert Gemmell)

Hi Martin, can you review this change please, thanks.

 JConsole/VisualVM unable to connect to broker when JMX RMI authentication and 
 access control is used
 

 Key: QPID-1568
 URL: https://issues.apache.org/jira/browse/QPID-1568
 Project: Qpid
  Issue Type: Bug
  Components: Java Broker
Affects Versions: 0.5
Reporter: Robert Gemmell
Assignee: Martin Ritchie
 Fix For: 0.5

 Attachments: QPID-1568_11jan2009.patch


 When authentication and access control is added to the RMI based JMX 
 connector server used by the Java broker, management tools such as JConsole 
 and VisualVM are unable to remotely connect to the console. Logging output 
 from JConsole indicated that a connection is successfully established and 
 then immediatley closed.

-- 
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-1550) C++ broker crashes periodically when handling connection closure


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

Steve Huston resolved QPID-1550.


Resolution: Fixed

The AsynchIO.2.diff fix is working and has been committed to:

0.5-release: r755440
trunk: r755441


 C++ broker crashes periodically when handling connection closure
 

 Key: QPID-1550
 URL: https://issues.apache.org/jira/browse/QPID-1550
 Project: Qpid
  Issue Type: Bug
  Components: C++ Broker
Affects Versions: M4
 Environment: Windows XP SP2, Visual Studio 2008 SP 1. .NET WCF client 
 (trunk)
Reporter: Robert Greig
Assignee: Steve Huston
 Fix For: 0.5

 Attachments: AsynchIO.2.diff, AsynchIO.diff, patch.1550, 
 qpid-broker-log.txt


 Periodically when running the .NET WCF client against the C++ broker running 
 on windows, the broker crashes.
 This occurs every 10 runs or thereabouts.
 Logs and stacks attached.

-- 
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-1745) C++ Windows; IntegerTypes.h need not define size_t

C++ Windows; IntegerTypes.h need not define size_t
--

 Key: QPID-1745
 URL: https://issues.apache.org/jira/browse/QPID-1745
 Project: Qpid
  Issue Type: Bug
  Components: C++ Broker, C++ Client
Affects Versions: M4
 Environment: Windows, Visual Studio 2008 (VC9)
Reporter: Steve Huston
Assignee: Steve Huston
Priority: Minor
 Fix For: 0.5


The qpid/cpp/src/qpid/sys/windows/IntegerTypes.h file typedefs size_t. This is 
not necessary for VC9, and the definition conflicts with the proper def for 
64-bit builds. Removing the typedef for size_t works for both 32- and 64-bit 
builds.

-- 
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-1745) C++ Windows; IntegerTypes.h need not define size_t


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

Steve Huston resolved QPID-1745.


Resolution: Fixed

Fixed; 0.5-release r755442, trunk r755443

 C++ Windows; IntegerTypes.h need not define size_t
 --

 Key: QPID-1745
 URL: https://issues.apache.org/jira/browse/QPID-1745
 Project: Qpid
  Issue Type: Bug
  Components: C++ Broker, C++ Client
Affects Versions: M4
 Environment: Windows, Visual Studio 2008 (VC9)
Reporter: Steve Huston
Assignee: Steve Huston
Priority: Minor
 Fix For: 0.5


 The qpid/cpp/src/qpid/sys/windows/IntegerTypes.h file typedefs size_t. This 
 is not necessary for VC9, and the definition conflicts with the proper def 
 for 64-bit builds. Removing the typedef for size_t works for both 32- and 
 64-bit builds.

-- 
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: Problem running tests/client_test

2009-03-17 Thread Steve Huston

Hi James,

I tested it using one of the examples in cpp/examples - I did notice
that test_client didn't work, but had bigger fish to fry before
getting back to that.

You raise great points that I'd like to discuss more. I don't have
time at the moment, but wanted to ack your note. I'll reply further
another day.

-Steve

 -Original Message-
 From: James Mansion [mailto:ja...@mansionfamily.plus.com] 
 Sent: Tuesday, March 17, 2009 3:48 PM
 To: dev@qpid.apache.org
 Subject: Re: Problem running tests/client_test
 
 
 Steve Huston wrote:
  Fix is on svn trunk...
  -Steve

 How did you test it?  It didn't work for me using the rather minimal
 debug settings in the test_client solution.
 
 My analysis of the failure is:
 
 In WindowsSasl, if we have PLAIN on offer, then we choose it 
 - even if we
 do not have a configured username and password.  Also, we 
 seem to take no
 notice of settings.mechanism.
 
 This will fix it so that the client can connect in the absence of a 
 username,
 though it still ignores the mechanism.  Arguably, more 
 information is needed
 in the case where we have a username but the password is 
 empty - perhaps we
 infer the username from the current login session but have not been 
 given the
 password - should we use PLAIN and hope that an empty 
 password is valid, or
 still use ANONYMOUS in that case because we don't know 
 whether 'empty' means
 'password not provided' ie incomplete information.  I think 
 we would need a
 flag in the settings structure to handle this (or, we should 
 never infer the
 user name and require that user name and password are both 
 provided - I find
 user name inference handy though).
 
 C:\src\qpid\trunk\qpid\cpp\srcsvn diff qpid\client
 Index: qpid/client/windows/SaslFactory.cpp
 ===
 --- qpid/client/windows/SaslFactory.cpp (revision 755031)
 +++ qpid/client/windows/SaslFactory.cpp (working copy)
 @@ -110,7 +110,7 @@
  throw InternalErrorException(QPID_MSG(Sasl error: no
common 
 mechanism
 ));
 
  std::string resp = ;
 -if (havePlain) {
 +if (havePlain  !settings.username.empty()) {
  mechanism = PLAIN;
  resp = ((char)0) + settings.username + ((char)0) + 
 settings.password;
  }
 
 
 Also ...
 
 The WindowsSasl implementation doesn't do anything 
 Windows-ish.  Why isn't
 this basic implementation the default if CyrusSasl is not 
 available?  Is it
 intended that a Windows security token could be passed?  This 
 makes sense
 for Windows deployments, but might also be workable for 
 non-Windows brokers
 that have access to a domain controller.  If you can support 
 single signon
 for Windows client applications, there will be general rejoicing.
 
 James
 
 

-
 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] Created: (QPID-1746) 0.5 Package generation

0.5 Package generation
--

 Key: QPID-1746
 URL: https://issues.apache.org/jira/browse/QPID-1746
 Project: Qpid
  Issue Type: Task
  Components: Build Tools
Reporter: Martin Ritchie
Priority: Blocker
 Fix For: 0.5


Package list discussed on Qpid Dev.

- Single Source package
- C++ Source package
- Binary Packages for
 + Brokers
  + C++
- Windows only from Qpid, simply link to other downstream binary
builds for other platforms
  + Java
 + Client and Example Package
  + C++
- Windows only from Qpid, simply link to other downstream binary
builds for other platforms
  + C# (0-8,0-10)
  + Java
  + Python
  + Ruby
+ Management
 - Eclipse JMX Console
   + Win
   + Linux
   + OS X
 - JMX Command Line Tool
 - QMan / WsDmAdapter
 - QMF Command line tools


-- 
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-1747) Update release script to gather new packages

Update release script to gather new packages


 Key: QPID-1747
 URL: https://issues.apache.org/jira/browse/QPID-1747
 Project: Qpid
  Issue Type: Sub-task
  Components: Build Tools
Reporter: Martin Ritchie
Assignee: Martin Ritchie
 Fix For: 0.5


Update the bin/release.sh script to include the required tools.

-- 
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-1748) Create Java Client Example packge

Create Java Client Example packge
-

 Key: QPID-1748
 URL: https://issues.apache.org/jira/browse/QPID-1748
 Project: Qpid
  Issue Type: Sub-task
Reporter: Martin Ritchie




-- 
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-1749) Create c++ client example package

Create c++ client example package
-

 Key: QPID-1749
 URL: https://issues.apache.org/jira/browse/QPID-1749
 Project: Qpid
  Issue Type: Sub-task
Reporter: Martin Ritchie




-- 
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-1750) Create Single c# client package

Create Single c# client package
---

 Key: QPID-1750
 URL: https://issues.apache.org/jira/browse/QPID-1750
 Project: Qpid
  Issue Type: Sub-task
Reporter: Martin Ritchie




-- 
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-1751) Create c# example package

Create c# example package
-

 Key: QPID-1751
 URL: https://issues.apache.org/jira/browse/QPID-1751
 Project: Qpid
  Issue Type: Sub-task
Reporter: Martin Ritchie




-- 
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-1752) Create JMX Command line tool package

Create JMX Command line tool package


 Key: QPID-1752
 URL: https://issues.apache.org/jira/browse/QPID-1752
 Project: Qpid
  Issue Type: Sub-task
Reporter: Martin Ritchie




-- 
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-1755) Create QMF Command line tools package

Create QMF Command line tools package
-

 Key: QPID-1755
 URL: https://issues.apache.org/jira/browse/QPID-1755
 Project: Qpid
  Issue Type: Sub-task
Reporter: Martin Ritchie




-- 
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-1754) Create QMF Command line tools package

Create QMF Command line tools package
-

 Key: QPID-1754
 URL: https://issues.apache.org/jira/browse/QPID-1754
 Project: Qpid
  Issue Type: Sub-task
Reporter: Martin Ritchie




-- 
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-1757) Create Python example package

Create Python example package
-

 Key: QPID-1757
 URL: https://issues.apache.org/jira/browse/QPID-1757
 Project: Qpid
  Issue Type: Sub-task
Reporter: Martin Ritchie




-- 
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-1756) Create Ruby Example package