You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@qpid.apache.org by bryand <bd...@simon.com> on 2018/01/11 16:55:08 UTC

qpid-jms-0.11.1 with qpid-broker-j-7.0.0

I am just getting started with qpid broker-j and have installed the latest
release (7.0.0).  I'm hoping that qpid broker-j can replace our ActiveMQ
broker.   We have some older JMS consumers that are using JMS 1.1 and JDK
1.7 and can't be upgraded near term so I need to use a qpid jms client at
those older levels.  I have successfully prototyped with qpid-jms-0.11.1
with qpid-broker-j-7.0.0 but wanted to double check using an older qpid jms
release is something that will be ok ('supported' if you will).   For our
newer JMS (and AMPQ) consumers I'll plan on using the most current qpid jms
client of Qpid JMS 0.28.0,



--
Sent from: http://qpid.2158936.n2.nabble.com/Apache-Qpid-users-f2158936.html

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org


Re: qpid-jms-0.11.1 with qpid-broker-j-7.0.0

Posted by Robbie Gemmell <ro...@gmail.com>.
That is the current release of the older AMQP 0-x JMS client, yes, and
still uses Java 7 since any newer releases of it are primarily going
to aim at fixes for existing older deployments. For new deployments we
would recommend looking toward the newer AMQP 1.0 JMS client, of which
0.28.0 is the current version.

FYI, your posts to the users mailing list (which backs the Nabble
site) are being spam-filtered by Gmail because "This message has a
from address in simon.com but has failed simon.com's required tests
for authentication" so its likely some folks arent seeing them.

Robbie

On 17 January 2018 at 12:50, bryand <bd...@simon.com> wrote:
> I was a little confused on the versioning and found that
> apache-qpid-jms-0-x-6.3.0 was a current release and it is working for us
> with JDK 1.7.
>
>
>
> --
> Sent from: http://qpid.2158936.n2.nabble.com/Apache-Qpid-users-f2158936.html
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
> For additional commands, e-mail: users-help@qpid.apache.org
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org


Re: qpid-jms-0.11.1 with qpid-broker-j-7.0.0

Posted by bryand <bd...@simon.com>.
I was a little confused on the versioning and found that
apache-qpid-jms-0-x-6.3.0 was a current release and it is working for us
with JDK 1.7.



--
Sent from: http://qpid.2158936.n2.nabble.com/Apache-Qpid-users-f2158936.html

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org


Re: qpid-jms-0.11.1 with qpid-broker-j-7.0.0

Posted by Robbie Gemmell <ro...@gmail.com>.
I'm not aware of any specific issues in using the two together,
however it is not a combination I have tried mysel. The 7.0.0 broker
was a major update with various work on its AMQP 1.0 support, plus the
0.11.1 client is now pretty old. We dont plan any more releases in the
0.11.x client stream.

Obviously the JVM version is the governing issue either way, but I'll
still note that you can use the JMS 2.0 client with things only built
against the 1.1 API, the 2.0 jar just also has to be on the classpath
as well at runtime.

On 11 January 2018 at 16:55, bryand <bd...@simon.com> wrote:
> I am just getting started with qpid broker-j and have installed the latest
> release (7.0.0).  I'm hoping that qpid broker-j can replace our ActiveMQ
> broker.   We have some older JMS consumers that are using JMS 1.1 and JDK
> 1.7 and can't be upgraded near term so I need to use a qpid jms client at
> those older levels.  I have successfully prototyped with qpid-jms-0.11.1
> with qpid-broker-j-7.0.0 but wanted to double check using an older qpid jms
> release is something that will be ok ('supported' if you will).   For our
> newer JMS (and AMPQ) consumers I'll plan on using the most current qpid jms
> client of Qpid JMS 0.28.0,
>
>
>
> --
> Sent from: http://qpid.2158936.n2.nabble.com/Apache-Qpid-users-f2158936.html
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
> For additional commands, e-mail: users-help@qpid.apache.org
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org