[ http://issues.apache.org/jira/browse/QPID-135?page=all ]
Steven Shaw resolved QPID-135.
--
Resolution: Fixed
> implement transactional channel
> ---
>
> Key: QPID-135
> URL: http://issues.apache.or
+1 from me.
Regards
Tejeswar
-Original Message-
From: Carl Trieloff [mailto:[EMAIL PROTECTED]
Sent: Tuesday, November 28, 2006 12:51 PM
To: qpid-dev@incubator.apache.org
Subject: [VOTE] Relaese Qpid Milestone 1 - (Java, Python, Ruby)
Please vote to publish the Milestone 1 release. Plea
Seems to work correctly on OS X as far as I can tell, so here's my +1. Nice
job, Rajith!
[X] +1 Release the source and binaries as Qpid Milestone 1 (M1)
[ ] -1 Veto the release (provide specific comments)
--steve
[ http://issues.apache.org/jira/browse/QPID-134?page=all ]
Steven Shaw resolved QPID-134.
--
Resolution: Fixed
Except for perhaps the closing of sessions and consumers. If there's a problem
there, we'll find it in the Java client too.
> Revisit fail over
>
Sorry about the mix up.
I have the RC build from scratch again at the same location
Rajith
On 11/28/06, Gordon Sim <[EMAIL PROTECTED]> wrote:
> Please cast your votes:
> [X] +1 Release the source and binaries as Qpid Milestone 1 (M1)
> [ ] -1 Veto the release (provide specific comments)
Apart
Please cast your votes:
[X] +1 Release the source and binaries as Qpid Milestone 1 (M1)
[ ] -1 Veto the release (provide specific comments)
Apart from the source issue already mentioned it looks good (I only saw
java related packages though). The broker starts fine and seems to work
with some
Also if were the Python and Ruby code is also in the zip we need to
ensure that the zip is correctly labeled.
qpid-python
qpid-ruby
or
qpid-java-python-ruby
Yeah, I don't know why I included Python, Ruby in the header as they are
not in the zip that we are
voting on or any of the
Martin Ritchie wrote:
The source zip contains release3.tar.gz which is the RC3 release
builds hence the extra 30Meg
yes I just found that.
Other than that it looks ok.. I can't test at home as I don't have the
right java. Will do so tomorow.
On 28/11/06, Martin Ritchie <[EMAIL PROTECTED]> wr
The source zip contains release3.tar.gz which is the RC3 release
builds hence the extra 30Meg
Other than that it looks ok.. I can't test at home as I don't have the
right java. Will do so tomorow.
On 28/11/06, Martin Ritchie <[EMAIL PROTECTED]> wrote:
Also if were the Python and Ruby code is al
Also if were the Python and Ruby code is also in the zip we need to
ensure that the zip is correctly labeled.
qpid-python
qpid-ruby
or
qpid-java-python-ruby
On 28/11/06, Martin Ritchie <[EMAIL PROTECTED]> wrote:
The source build doesn't seem right. At 37Meg it is going take me 20
mi
The source build doesn't seem right. At 37Meg it is going take me 20
minutes from now to download and check. My guess is that release
wasn't done from a fresh checkout.
The RC3 src zip was only 7.1Meg.
On 28/11/06, Rajith Attapattu <[EMAIL PROTECTED]> wrote:
+1 from me.
Rajith
On 11/28/06, Car
[X] +1 Release the source and binaries as Qpid Milestone 1 (M1)
[ ] -1 Veto the release (provide specific comments)
+1 from me.
Rajith
On 11/28/06, Carl Trieloff <[EMAIL PROTECTED]> wrote:
Please vote to publish the Milestone 1 release. Please take some time
to download the distributions, review them and test them in your
environment
if you have not done so already before voting.
The vote is open for at l
Please vote to publish the Milestone 1 release. Please take some time
to download the distributions, review them and test them in your environment
if you have not done so already before voting.
The vote is open for at least the next 72 hours.
At least three +1 votes are required, and only t
implement acknowledgement modes
---
Key: QPID-137
URL: http://issues.apache.org/jira/browse/QPID-137
Project: Qpid
Issue Type: New Feature
Components: Dot Net Client
Reporter: Steven Shaw
*
implement prefetch
--
Key: QPID-136
URL: http://issues.apache.org/jira/browse/QPID-136
Project: Qpid
Issue Type: New Feature
Components: Dot Net Client
Reporter: Steven Shaw
The .NET client started lif
[ http://issues.apache.org/jira/browse/QPID-134?page=all ]
Steven Shaw updated QPID-134:
-
Component/s: Dot Net Client
> Revisit fail over
> -
>
> Key: QPID-134
> URL: http://issues.apache.org/jira/browse/QPID-1
[ http://issues.apache.org/jira/browse/QPID-135?page=all ]
Steven Shaw reassigned QPID-135:
Assignee: Steven Shaw
> implement transactional channel
> ---
>
> Key: QPID-135
> URL: http://issues.a
Revisit fail over
-
Key: QPID-134
URL: http://issues.apache.org/jira/browse/QPID-134
Project: Qpid
Issue Type: Bug
Reporter: Steven Shaw
In reorganising the .NET Qpid.Messaging API the issue of fail over was
ne
implement transactional channel
---
Key: QPID-135
URL: http://issues.apache.org/jira/browse/QPID-135
Project: Qpid
Issue Type: New Feature
Components: Dot Net Client
Reporter: Steven Shaw
I
[ http://issues.apache.org/jira/browse/QPID-134?page=all ]
Steven Shaw reassigned QPID-134:
Assignee: Steven Shaw
> Revisit fail over
> -
>
> Key: QPID-134
> URL: http://issues.apache.org/jira/browse/QPID-1
[ http://issues.apache.org/jira/browse/QPID-54?page=all ]
Martin Ritchie resolved QPID-54.
Resolution: Later
Awaiting changes in MINA (DIRMINA-302) to discount that as a problem.
> When the broker is receiving high load client received rate falls.
> -
[ http://issues.apache.org/jira/browse/QPID-54?page=all ]
Martin Ritchie reassigned QPID-54:
--
Assignee: Martin Ritchie
> When the broker is receiving high load client received rate falls.
> ---
[ http://issues.apache.org/jira/browse/QPID-126?page=all ]
Martin Ritchie closed QPID-126.
---
Resolution: Invalid
This is related to the revertion of QPID-92 changes and the non removal of the
libs directories QPID-132.
The wrong mina jar was being picked
[ http://issues.apache.org/jira/browse/QPID-122?page=all ]
Martin Ritchie resolved QPID-122.
-
Resolution: Fixed
r480119 changes made to all relevant classes. Updated AbstractJMSMessage to
handle most of the tests.
> JMS*Message do not throw MessageNotW
On 28/11/06, Carl Trieloff <[EMAIL PROTECTED]> wrote:
The Java code gen is already there, it just needs to be integrated and
tested, so there
should be enough to go from to do the cs. Thanks for creating the JIRA.
Once the new Java codgen is integrated, I'll look at doing the same for the C#.
[ http://issues.apache.org/jira/browse/QPID-42?page=all ]
Gordon Sim updated QPID-42:
---
Component/s: (was: C++ Broker)
Fixed for c++ broker during related refactoring.
> Refragment messages when delivering to client with max frame size less than
> publish
Very belatedly I've put up the Qpid style guide:
http://cwiki.apache.org/confluence/display/qpid/CppStyleGuide
This guide reflects things that were agreed on the list some time ago,
and things that are de facto standard in the existing codebase. The page
includes guidelines for making further sty
[ http://issues.apache.org/jira/browse/QPID-133?page=all ]
Robert Greig reassigned QPID-133:
-
Assignee: Steven Shaw
Carl indicates that the Java stuff is done, just requires integrating so would
be great if you could take a look at how easy it will be t
Update .NET client to use new code generation technique
---
Key: QPID-133
URL: http://issues.apache.org/jira/browse/QPID-133
Project: Qpid
Issue Type: Improvement
Components: Dot
Paul,
I have added this disclaimer to the notices file.
Carl.
Paul Fremantle wrote:
I've looked at the issue of you guys shipping with JMS. In general it
is not good to ship Java Platform Interface (java.* javax.*)
interfaces without passing the relevant TCK. However, as long as you
label th
Robert Greig wrote:
On 28/11/06, Carl Trieloff <[EMAIL PROTECTED]> wrote:
If we did that the java tool lib would be needed to build the cs client,
I would
think that we would want to add the classes to the tool for cs also and
have a
single generation tool.
As we will be removing the xslt fro
On 28/11/06, Carl Trieloff <[EMAIL PROTECTED]> wrote:
If we did that the java tool lib would be needed to build the cs client,
I would
think that we would want to add the classes to the tool for cs also and
have a
single generation tool.
As we will be removing the xslt from C++ (done) and Java
C# clients look great,
Looking through it, it uses the multi pass XSLT, I guess that we could
also
convert it at some point to support multi version generation and the new
generator (that tool is in Java supporting both C++ and Java generation.)
If we did that the java tool lib would be need
I've looked at the issue of you guys shipping with JMS. In general it
is not good to ship Java Platform Interface (java.* javax.*)
interfaces without passing the relevant TCK. However, as long as you
label this release correctly, we should be ok.
So please include clear documentation that this re
[ http://issues.apache.org/jira/browse/QPID-132?page=all ]
Martin Ritchie updated QPID-132:
Summary: Remove the lib directories that were used for the ant build system
(was: The lib directories were used for the ant build system)
> Remove the lib direc
The lib directories were used for the ant build system
---
Key: QPID-132
URL: http://issues.apache.org/jira/browse/QPID-132
Project: Qpid
Issue Type: Sub-task
Reporter: Martin
[ http://issues.apache.org/jira/browse/QPID-71?page=all ]
Martin Ritchie resolved QPID-71.
Resolution: Fixed
r480032
Updated AMQBrokerDetails to handle port error.
Created BrokerDetailsTest to test issues and moved test from ConnectionURLTest
that wer
[ http://issues.apache.org/jira/browse/QPID-71?page=all ]
Martin Ritchie reassigned QPID-71:
--
Assignee: Martin Ritchie
> ConnectionURL Not parsed correctly under Java 1.6
> -
>
> Key: QPID-
I'll have a look.
Previous discussion has settled on two approaches:
a) Clustering; where several servers look/behave as one.
b) Bridging; to link geographically separate servers, or servers under
control of a different organisation. Bridging is also useful to link to
different middlewares.
It
I guess we should just finally check that we've been able to get the broker
running successfully (and connect to it with a client) on every platfrom:
Windows
Linux
Unix
I'll start checking now (have had it up wth previous RCs but will recheck) -
please post if you've been able to do this ok alre
41 matches
Mail list logo
