You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@qpid.apache.org by Rob Godfrey <ro...@gmail.com> on 2014/08/28 15:49:01 UTC

Request For Inclusion into 0.30 (QPID-6050)

Hi Justin,

Cory Adams [1] discovered a bug in the JMS AMQP 1.0 client handling of a
System Property which prevents JVM wide setting of the synchronous publish
behaviour.  While there is a workaround (to set it on the connection URL
for each connection), the fix [2] is isolated to this client and low impact
and low risk.  If possible I'd like to get this into 0.30


-- Rob

[1]
http://qpid.2158936.n2.nabble.com/Experiences-with-Qpid-AMQP-1-0-JMS-client-in-production-tp7611393p7612664.html
[2] JIRA:  https://issues.apache.org/jira/browse/QPID-6050

Re: Request For Inclusion into 0.30 (QPID-6050)

Posted by Rob Godfrey <ro...@gmail.com>.
Hi Justin

FYI... On a plane right now - just about to take off... So won't be able to
merge this until tmr morning Germany time

-- Rob
On 28 Aug 2014 19:44, "Justin Ross" <jr...@apache.org> wrote:

> Thanks, Cory, for testing.  It's now approved so you should see it in the
> final 0.30 release.
>
>
> On Thu, Aug 28, 2014 at 11:58 AM, Adams, Cory <co...@paypal.com> wrote:
>
> > I verified that the system property of -Dqpid.sync_publish=false did work
> > in 0.32-SNAPSHOT by building from trunk today and testing.
> >
> > Thank you,
> >
> > Cory
> >
> > -----Original Message-----
> > From: Rob Godfrey [mailto:rob.j.godfrey@gmail.com]
> > Sent: Thursday, August 28, 2014 8:49 AM
> > To: users@qpid.apache.org; jross@apache.org
> > Subject: Request For Inclusion into 0.30 (QPID-6050)
> >
> > Hi Justin,
> >
> > Cory Adams [1] discovered a bug in the JMS AMQP 1.0 client handling of a
> > System Property which prevents JVM wide setting of the synchronous
> publish
> > behaviour.  While there is a workaround (to set it on the connection URL
> > for each connection), the fix [2] is isolated to this client and low
> impact
> > and low risk.  If possible I'd like to get this into 0.30
> >
> >
> > -- Rob
> >
> > [1]
> >
> >
> http://qpid.2158936.n2.nabble.com/Experiences-with-Qpid-AMQP-1-0-JMS-client-in-production-tp7611393p7612664.html
> > [2] JIRA:  https://issues.apache.org/jira/browse/QPID-6050
> >
>

Re: Request For Inclusion into 0.30 (QPID-6050)

Posted by Justin Ross <jr...@apache.org>.
Thanks, Cory, for testing.  It's now approved so you should see it in the
final 0.30 release.


On Thu, Aug 28, 2014 at 11:58 AM, Adams, Cory <co...@paypal.com> wrote:

> I verified that the system property of -Dqpid.sync_publish=false did work
> in 0.32-SNAPSHOT by building from trunk today and testing.
>
> Thank you,
>
> Cory
>
> -----Original Message-----
> From: Rob Godfrey [mailto:rob.j.godfrey@gmail.com]
> Sent: Thursday, August 28, 2014 8:49 AM
> To: users@qpid.apache.org; jross@apache.org
> Subject: Request For Inclusion into 0.30 (QPID-6050)
>
> Hi Justin,
>
> Cory Adams [1] discovered a bug in the JMS AMQP 1.0 client handling of a
> System Property which prevents JVM wide setting of the synchronous publish
> behaviour.  While there is a workaround (to set it on the connection URL
> for each connection), the fix [2] is isolated to this client and low impact
> and low risk.  If possible I'd like to get this into 0.30
>
>
> -- Rob
>
> [1]
>
> http://qpid.2158936.n2.nabble.com/Experiences-with-Qpid-AMQP-1-0-JMS-client-in-production-tp7611393p7612664.html
> [2] JIRA:  https://issues.apache.org/jira/browse/QPID-6050
>

RE: Request For Inclusion into 0.30 (QPID-6050)

Posted by "Adams, Cory" <co...@paypal.com.INVALID>.
I verified that the system property of -Dqpid.sync_publish=false did work in 0.32-SNAPSHOT by building from trunk today and testing.

Thank you,

Cory

-----Original Message-----
From: Rob Godfrey [mailto:rob.j.godfrey@gmail.com] 
Sent: Thursday, August 28, 2014 8:49 AM
To: users@qpid.apache.org; jross@apache.org
Subject: Request For Inclusion into 0.30 (QPID-6050)

Hi Justin,

Cory Adams [1] discovered a bug in the JMS AMQP 1.0 client handling of a System Property which prevents JVM wide setting of the synchronous publish behaviour.  While there is a workaround (to set it on the connection URL for each connection), the fix [2] is isolated to this client and low impact and low risk.  If possible I'd like to get this into 0.30


-- Rob

[1]
http://qpid.2158936.n2.nabble.com/Experiences-with-Qpid-AMQP-1-0-JMS-client-in-production-tp7611393p7612664.html
[2] JIRA:  https://issues.apache.org/jira/browse/QPID-6050