Re: [VOTE] Release Apache Qpid JMS 0.30.0

[Timothy Bish]

On 02/26/2018 07:18 AM, Robbie Gemmell wrote:

Hi folks,

I have put together a spin for a 0.30.0 Qpid JMS client release,
please give it a test out and vote accordingly.

The source and binary archives can be grabbed from:
https://dist.apache.org/repos/dist/dev/qpid/jms/0.30.0-rc1/

The maven artifacts are also staged for now at:
https://repository.apache.org/content/repositories/orgapacheqpid-1131

The JIRAs assigned are:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314524&version=12342544

Regards,
Robbie

P.S. If you want to test it out using maven (e.g with the examples
src, or your own things), you can temporarily add this to your poms to
access the staging repo:

   
 
   staging
   
https://repository.apache.org/content/repositories/orgapacheqpid-1131
 
   

The dependency for the client itself would then be:

   
 org.apache.qpid
 qpid-jms-client
 0.30.0
   

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




+1

* Verified the signatures and checksums
* Checked license and NOTICE files present
* Used mvn apache-rat:check to validate license headers
* Built from source and ran tests
* Built ActiveMQ Artemis using the staged bits and ran the AMQP tests.


--
Tim Bish
twitter: @tabish121
blog: http://timbish.blogspot.com/


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

Re: [VOTE] Release Apache Qpid Proton-J 0.26.0

[Timothy Bish]

+1

* Validated signatures and checksums
* Checked for license and notice files in binary and source archives
* Ran mvn apache-rat:check to validate source files have licenses
* Built from source and ran the tests
* Build ActiveMQ, ActiveMQ Artemis and Qpid JMS using the staged bits 
and ran the AMQP tests


On 02/22/2018 01:39 PM, Robbie Gemmell wrote:

Hi folks,

I have put together a spin for a Qpid Proton-J 0.26.0 release, please
test it and vote accordingly.

The source and binary archives can be grabbed from:
https://dist.apache.org/repos/dist/dev/qpid/proton-j/0.26.0-rc1/

The maven artifacts are staged for now at:
https://repository.apache.org/content/repositories/orgapacheqpid-1130

The JIRAs assigned are:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12313720&version=12342429

Regards,
Robbie

P.S. If you want to test things out using maven with your own build
you can temporarily add this to your poms to access the staging repo:

   
 
   staging
   
https://repository.apache.org/content/repositories/orgapacheqpid-1130
 
   

The dependency for proton-j would then be:

   
 org.apache.qpid
 proton-j
 0.26.0
   

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




--
Tim Bish
twitter: @tabish121
blog: http://timbish.blogspot.com/


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

Re: [VOTE] Release Apache Qpid Proton 0.20.0

[Timothy Bish]

On 01/25/2018 07:46 AM, Robbie Gemmell wrote:

Hi folks,

I have put together a spin for a Qpid Proton 0.20.0 release, please
give it a test out and vote accordingly.

The source archive can be grabbed from:
https://dist.apache.org/repos/dist/dev/qpid/proton/0.20.0-rc1/

The JIRAs currently assigned are:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12313720&version=12342219

It is tagged as 0.20.0-rc1.

Regards,
Robbie

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



+1

* Validated signatures and checksums, checked for license and notice files
* Built from source and ran the tests
* Ran some of the examples against an Artemis broker


--
Tim Bish
twitter: @tabish121
blog: http://timbish.blogspot.com/


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

Re: [VOTE] Release Apache Qpid JMS 0.29.0

[Timothy Bish]

On 01/19/2018 07:30 AM, Robbie Gemmell wrote:

Hi folks,

I have put together a spin for a 0.29.0 Qpid JMS client release,
please give it a test out and vote accordingly.

The source and binary archives can be grabbed from:
https://dist.apache.org/repos/dist/dev/qpid/jms/0.29.0-rc1/

The maven artifacts are also staged for now at:
https://repository.apache.org/content/repositories/orgapacheqpid-1128

The JIRAs currently assigned are:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314524&version=12342310

Regards,
Robbie

P.S. If you want to test it out using maven (e.g with the examples
src, or your own things), you can temporarily add this to your poms to
access the staging repo:

   
 
   staging
   
https://repository.apache.org/content/repositories/orgapacheqpid-1128
 
   

The dependency for the client itself would then be:

   
 org.apache.qpid
 qpid-jms-client
 0.29.0
   

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



+1

* Validated signatures and checksums
* Checked for License and Notice files with updated year, ran mvn 
apache-rat:check

* Built from source and ran the tests
* Built Artemis and ActiveMQ 5.x with staged bits and ran the AMQP tests
* Ran the included example against existing Artemis and ActiveMQ 5.x 
installs



--
Tim Bish
twitter: @tabish121
blog: http://timbish.blogspot.com/


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

Re: [VOTE] Release Apache Qpid Proton-J 0.25.0

[Timothy Bish]

On 01/11/2018 01:34 PM, Robbie Gemmell wrote:

Hi folks,

I have put together a first spin for a Qpid Proton-J 0.25.0 release,
please test it and vote accordingly.

The source and binary archives can be grabbed from:
https://dist.apache.org/repos/dist/dev/qpid/proton-j/0.25.0-rc1/

The maven artifacts are staged for now at:
https://repository.apache.org/content/repositories/orgapacheqpid-1127

The JIRAs assigned are:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12313720&version=12342290

Regards,
Robbie

P.S. If you want to test things out using maven with your own build
you can temporarily add this to your poms to access the staging repo:

   
 
   staging
   
https://repository.apache.org/content/repositories/orgapacheqpid-1127
 
   

The dependency for proton-j would then be:

   
 org.apache.qpid
 proton-j
 0.25.0
   

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




+1

* Validated signature and checksums
* Checked for license headers with 'mvn apache-rat:check'
* Built from source and ran tests
* Built Qpid JMS using staged artifacts and ran the tests
* Built ActiveMQ and ActiveMQ Artemis using staged artifacts and ran the 
AMQP tests


--
Tim Bish


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

Re: [VOTE] Release Apache Qpid Proton 0.19.0 (RC2)

[Timothy Bish]

On 12/20/2017 01:30 PM, Robbie Gemmell wrote:
Hi folks, I have put together a second spin for a Qpid Proton 0.19.0 
release, please give it a test out and vote accordingly. The source 
archive can be grabbed from: 
https://dist.apache.org/repos/dist/dev/qpid/proton/0.19.0-rc2/ The 
JIRAs currently assigned are: 
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12313720&version=12341125 
The only changes since RC1 are in the Ruby binding, reverting a prior 
change and making an example fixup: 
http://git-wip-us.apache.org/repos/asf/qpid-proton/commit/cd06716a 
http://git-wip-us.apache.org/repos/asf/qpid-proton/commit/45bd5733 It 
is tagged as 0.19.0-rc2. Regards, Robbie 
- 
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For 
additional commands, e-mail: users-h...@qpid.apache.org


+1
* Validated signatures and checksums
* Built from source and ran the test suite
* Installed and built Quiver drivers using those libs, ran tests against 
ActiveMQ Artemis



--
Tim Bish


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

Re: [VOTE] Release Apache Qpid Proton 0.19.0

[Timothy Bish]

On 12/19/2017 04:17 PM, Robbie Gemmell wrote:

Hi folks,

I have put together a spin for a Qpid Proton 0.19.0 release, please
give it a test out and vote accordingly.

The source archive can be grabbed from:
https://dist.apache.org/repos/dist/dev/qpid/proton/0.19.0-rc1/

The JIRAs currently assigned are:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12313720&version=12341125

It is tagged as 0.19.0-rc1.

Regards,
Robbie

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




+1
* Checked staged bits for license and notice files
* Validate signatures and checksum
* Built from source and ran tests
* Built the Quiver test suite using the install build and ran tests 
against ActiveMQ Artemis.



--
Tim Bish
twitter: @tabish121
blog: http://timbish.blogspot.com/


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

Re: [VOTE] Release Apache Qpid JMS 0.28.0

[Timothy Bish]

On 12/13/2017 08:39 AM, Jiri Danek wrote:

On Wed, Dec 13, 2017 at 1:29 PM, Jiri Danek  wrote:


3. Execute the following

java -jar cli-qpid-jms-1.2.2-SNAPSHOT-0.27.0.jar sender...


I meant 0.28.0.jar, sorry.

The problem seems to be in
org.apache.qpid.proton.codec.DecoderImpl#readConstructor in Artemis, it
tries to lookup code == 71 in _constructors. That one is null, and so it
throws.

Apparently this reads something weird, because there should be no such
thing, I looked both for 71 and 0x47 and this is not in AMQP... I did not
have much luck debugging this, so I'll try for self-contained reproducer
now.


There have been a few race conditions that were fixed in the Artemis 
AMQP protocol handler since 2.4.0 so I'd be testing only on a build off 
master first to rule any of those out.


--
Tim Bish
twitter: @tabish121
blog: http://timbish.blogspot.com/


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

Re: [VOTE] Release Apache Qpid JMS 0.28.0

[Timothy Bish]

On 12/11/2017 01:21 PM, Robbie Gemmell wrote:

Hi folks,

I have put together a spin for a 0.28.0 Qpid JMS client release, please
give it a test out and vote accordingly.

The source and binary archives can be grabbed from:
https://dist.apache.org/repos/dist/dev/qpid/jms/0.28.0-rc1/

The maven artifacts are also staged for now at:
https://repository.apache.org/content/repositories/orgapacheqpid-1126

The JIRAs currently assigned are:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314524&version=12342125

Regards,
Robbie

P.S. If you want to test it out using maven (e.g with the examples src, or
your own things), you can temporarily add this to your poms to access the
staging repo:

   
 
   staging
   
https://repository.apache.org/content/repositories/orgapacheqpid-1126
 
   

The dependency for the client itself would then be:

   
 org.apache.qpid
 qpid-jms-client
 0.28.0
   

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



+1

* Validated signatures and checksums, check for license and notice files
* Built from source and ran the test suite
* Used mvn apache-rat:check to validate the source contains license headers.
* Ran the example against an ActiveMQ Artemis broker install
* Built ActiveMQ Artemis and ActiveMQ 5.x using the staged artifacts and 
ran the AMQP tests



--
Tim Bish


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

Re: [VOTE] Release Apache Qpid Proton-J 0.24.0

[Timothy Bish]

On 12/08/2017 12:36 PM, Robbie Gemmell wrote:

Hi folks,

I have put together a first spin for a Qpid Proton-J 0.24.0 release,
please test it and vote accordingly.

The source and binary archives can be grabbed from:
https://dist.apache.org/repos/dist/dev/qpid/proton-j/0.24.0-rc1/

The maven artifacts are staged for now at:
https://repository.apache.org/content/repositories/orgapacheqpid-1125

The JIRAs assigned are:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12313720&version=12341942

Regards,
Robbie

P.S. If you want to test things out using maven with your own build
you can temporarily add this to your poms to access the staging repo:

   
 
   staging
   
https://repository.apache.org/content/repositories/orgapacheqpid-1125
 
   

The dependency for proton-j would then be:

   
 org.apache.qpid
 proton-j
 0.24.0
   

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



+1
* Validated signatures and checksums
* Checked for license and notice files in the archives
* Built from source and ran the tests
* Checked for source licenses using mvn apache-rat:check
* Built Qpid JMS using the staged artifacts and ran the tests
* Built ActiveMQ Artemis using the staged artifacts and ran the AMQP tests.
* Using the Quiver benchmark suite ran several tests using combinations 
of broker and client builds with the staged artifacts and the previous 
releases.



--
Tim Bish


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

Re: Connection problem with Azure Service Bus Queue

[Timothy Bish]

On 12/01/2017 12:38 PM, Gordon Sim wrote:

On 01/12/17 14:37, Шелест Ігор wrote:

hello_world called
on_container_start called[00CB1200]:  -> SASL
[00CB1200]:  <- SASL
[00CB1200]:0 <- @sasl-mechanisms(64)
[sasl-server-mechanisms=@PN_SYMBOL[:MSSBCBS, :PLAIN, :ANONYMOUS,
:EXTERNAL]]
[00CB1200]:0 -> @sasl-init(65) [mechanism=:EXTERNAL,
initial-response=b"IgorShelestNotPartitionedQueuePolicyName"]
[00CB1200]:0 <- @sasl-outcome(68) [code=0, additional-data=b"Welcome!"]
[00CB1200]:  -> AMQP
[00CB1200]:0 -> @open(16)
[container-id="41155a12-3703-475c-8063-d61b8f3de514",
hostname="igorshelestnamespacename.servicebus.windows.net",
max-frame-size=1, channel-max=32767, idle-time-out=500]
[00CB1200]:0 -> @close(24) [error=@error(29) [condition=:"proton:io",
description="An existing connection was forcibly closed by the remote
host.  - on read from
igorshelestnamespacename.servicebus.windows.net:5672 (AMQP header
mismatch: Insufficient data to determine protocol [''] (connection
aborted))"]]
[00CB1200]:  <- EOS

Exception: 
>


Unsuccessful exit
== 



I tried to google what the problem, didn't really find any solution.
As far as I understand some connection options are probably wrong.
Do you have any idea how to fix this issue?


Is there any error or log message available on the service bus side? 
It sounds like servicebus is just dropping the connection. It has 
successfully authenticated, so you could be right it may be that it 
doesn't like some of the values you send in the open frame, e.g. 500 
millisecs may be considered too low for the idle timeout. (The 
max-frame-size and channel-max don't really impose any particular 
burden on the peer). 


I recall there being a lower limit on the idle timeout of something like 
2 minutes so that could be causing it to reject the connection.


--
Tim Bish


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

Re: [VOTE] Release Apache Qpid CPP 1.37.0

[Timothy Bish]

On 11/21/2017 01:20 PM, Robbie Gemmell wrote:

Hi folks,

I have put together a spin for a Qpid CPP 1.37.0 release, please give
it a test out and vote accordingly.

The source archive can be grabbed from:
https://dist.apache.org/repos/dist/dev/qpid/cpp/1.37.0-rc1/

The JIRAs currently assigned are:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310520&version=12338808

It is tagged as 1.37.0-rc1.

Regards,
Robbie

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




+1
* Validated signatures and checksums
* Checked for valid license and notice files
* Built from source and installed the result
* Ran the broker and executed some of the samples as well as some other 
client tests against it

* Ran some of the client examples against an ActiveMQ Artemis broker


--
Tim Bish
twitter: @tabish121
blog: http://timbish.blogspot.com/


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

Re: [VOTE] Release Apache Qpid JMS 0.27.0

[Timothy Bish]

On 11/01/2017 12:37 PM, Robbie Gemmell wrote:

Hi folks,

I have put together a spin for a 0.27.0 Qpid JMS client release, please
give it a test out and vote accordingly.

The source and binary archives can be grabbed from:
https://dist.apache.org/repos/dist/dev/qpid/jms/0.27.0-rc1/

The maven artifacts are also staged for now at:
https://repository.apache.org/content/repositories/orgapacheqpid-1118

The JIRAs currently assigned are:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314524&version=12341712

Regards,
Robbie

P.S. If you want to test it out using maven (e.g with the examples src, or
your own things), you can temporarily add this to your poms to access the
staging repo:

   
 
   staging
   
https://repository.apache.org/content/repositories/orgapacheqpid-1118
 
   

The dependency for the client itself would then be:

   
 org.apache.qpid
 qpid-jms-client
 0.27.0
   

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



+1
* Validated signatures and checksums
* Checked for presence of license and notice files
* Ran mvn apache-rat:check to scan for missing license headers, none found.
* Built from source and ran tests
* Built ActiveMQ 5.x and ActiveMQ Artemis using staged bits and ran tests
* Inspected binary release for expected libraries and documentation.

--
Tim Bish
twitter: @tabish121
blog: http://timbish.blogspot.com/


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

Re: [VOTE] Release Apache Qpid Proton 0.18.1

[Timothy Bish]

On 10/31/2017 09:49 AM, Robbie Gemmell wrote:

Hi folks,

I have put together a spin for a Qpid Proton 0.18.1 release, please
give it a test out and vote accordingly.

The source archive can be grabbed from:
https://dist.apache.org/repos/dist/dev/qpid/proton/0.18.1-rc1/

The JIRAs currently assigned are:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12313720&version=12342056

It is tagged as 0.18.1-rc1.

Regards,
Robbie

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



+1
* Validated the signature and checksums
* Ensured that license file and notice file were present
* Built from source and ran the tests with bindings enabled

--
Tim Bish
twitter: @tabish121
blog: http://timbish.blogspot.com/


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

Re: Proposed update to minimum tool requirements for proton-c

[Timothy Bish]

On 10/20/2017 03:47 PM, Andrew Stitcher wrote:

In the course of the 0.18 release process I've been looking at the
minimum build tool versions supported - specifically CMake and C/C++
compilers. I've reached the following conclusions:

We should move to a minimum supported cmake of 2.8.12.2, gcc 4.4.7 &
Visual Studio 2010.

  - The oldest Linux distributions in large scale use here seem to be
RHEL 6/CentOS 6, Ubuntu 1404, Debian 8.
These all support either this or newer versions of cmake/gcc.

Visual Studio 2010 is already fairly old and comparable in age to gcc
4.4.7.

The benefit of this would be to simplify the CMake build system:

- Removing some early gcc specific build code
- Allowing us to use some simplifying CMake Modules
- Allow us to rely on some better cmake functions

For Visual Studio it will simplify the compilers we need to test, I'd
suggest we build/test using VS 2010, VS 2013 & VS 2017.

[VS 2010 because it's the oldest we support; VS 2013 because it
supports a pretty good subset of C99 and C++11 & VS 2017 because it is
the newest VS (with excellent C++11).]

Unless anyone objects I will do the substantive part of this next week,
before the suggested 0.18.1 release, that is:

- Update cmake_minimum() statements in the build files.
- Remove the special case code for gcc earlier than 4.4

There's nothing specific to do for VS except document that 2010 is the
earliest version that we will keep on making work.

So, thoughts, suggestions, and more particularly objections.

Andrew


While I have no objections to the change in general, it'd be a bit 
surprising to me as a user to have these sorts of changes go into an 
0.18.1 release where I'd really be expecting only minor tweaks / bug fix 
type changes.  Changing the supported tooling versions seems like 
something that really calls for a 0.19.0 release (that being the closest 
equivalent of a major version, given the 0.x designation).


--
Tim Bish


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

Re: [VOTE] Release Apache Qpid Proton 0.18.0

[Timothy Bish]

+1

* Validated signature and checksum
* Verified License and Notice files present
* Built from source and ran self tests.

On 10/18/2017 01:29 PM, Robbie Gemmell wrote:

Hi folks,

I have put together a first spin for a Qpid Proton 0.18.0 release,
please test it and vote accordingly.

The source archive can be grabbed from:
https://dist.apache.org/repos/dist/dev/qpid/proton/0.18.0-rc1/

The JIRAs currently assigned are:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12313720&version=12338903

It is tagged as 0.18.0-rc1.

Regards,
Robbie

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




--
Tim Bish
twitter: @tabish121
blog: http://timbish.blogspot.com/


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

Re: [VOTE] Release Apache Qpid Proton-J 0.23.0

[Timothy Bish]

On 10/12/2017 12:39 PM, Robbie Gemmell wrote:

Hi folks,

I have put together a first spin for a Qpid Proton-J 0.23.0 release,
please test it and vote accordingly.

The source and binary archives can be grabbed from:
https://dist.apache.org/repos/dist/dev/qpid/proton-j/0.23.0-rc1/

The maven artifacts are staged for now at:
https://repository.apache.org/content/repositories/orgapacheqpid-1117

The JIRAs assigned are:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12313720&version=12341631

Regards,
Robbie

P.S. If you want to test things out using maven with your own build
you can temporarily add this to your poms to access the staging repo:

   
 
   staging
   
https://repository.apache.org/content/repositories/orgapacheqpid-1117
 
   

The dependency for proton-j would then be:

   
 org.apache.qpid
 proton-j
 0.23.0
   

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



+1
* Validated signatures and checksums
* Checked for presence of license and notice files in the artifacts
* Built from source and ran the tests
* Checked for license headers using mvn apache-rat:check
* Built ActiveMQ 5.x using the staged bits and ran all AMQP tests
* Built Qpid JMS using the staged bits and ran the full test suite


--
Tim Bish
twitter: @tabish121
blog: http://timbish.blogspot.com/


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

Re: [VOTE] Release Apache Qpid JMS 0.26.0

[Timothy Bish]

On 10/04/2017 07:35 AM, Robbie Gemmell wrote:

Hi folks,

I have put together a spin for a 0.26.0 Qpid JMS client release, please
give it a test out and vote accordingly.

The source and binary archives can be grabbed from:
https://dist.apache.org/repos/dist/dev/qpid/jms/0.26.0-rc1/

The maven artifacts are also staged for now at:
https://repository.apache.org/content/repositories/orgapacheqpid-1116

The JIRAs currently assigned are:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314524&version=12341637

Regards,
Robbie

P.S. If you want to test it out using maven (e.g with the examples src, or
your own things), you can temporarily add this to your poms to access the
staging repo:

   
 
   staging
   
https://repository.apache.org/content/repositories/orgapacheqpid-1116
 
   

The dependency for the client itself would then be:

   
 org.apache.qpid
 qpid-jms-client
 0.26.0
   

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



+1

* Validated signatures and checksums
* Checked the binary and source archives for license and notice files.
* Built from source and ran the tests
* Built ActiveMQ 5 upstream with the staged bits and ran the AMQP tests
* Built Artemis upstream with the staged bits and ran the AMQP tests
* Ran the included example app against a running 5.x broker.


--
Tim Bish
twitter: @tabish121
blog: http://timbish.blogspot.com/


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

Re: [VOTE] Release Apache Qpid JMS 0.25.0

[Timothy Bish]

On 09/18/2017 12:45 PM, Robbie Gemmell wrote:

Hi folks,

I have put together a spin for a 0.25.0 Qpid JMS client release, please
give it a test out and vote accordingly.

The source and binary archives can be grabbed from:
https://dist.apache.org/repos/dist/dev/qpid/jms/0.25.0-rc1/

The maven artifacts are also staged for now at:
https://repository.apache.org/content/repositories/orgapacheqpid-1115

The JIRAs currently assigned are:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314524&version=12341292

Regards,
Robbie

P.S. If you want to test it out using maven (e.g with the examples src, or
your own things), you can temporarily add this to your poms to access the
staging repo:

   
 
   staging
   
https://repository.apache.org/content/repositories/orgapacheqpid-1115
 
   

The dependency for the client itself would then be:

   
 org.apache.qpid
 qpid-jms-client
 0.25.0
   

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



+1

* Validated signatures and checksums
* Checked bin and src archives for proper license and notice files
* Built from source and ran the tests
* Checked for license issues using 'mvn apache-rat:check'
* Used the staged artifacts in ActiveMQ 5.x to build and run all AMQP tests
* Used the staged artifacts in Artemis to build and run all AMQP tests
* Ran the example from the src archive against a running 5.x broker.


--
Tim Bish
twitter: @tabish121
blog: http://timbish.blogspot.com/


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

Re: [VOTE] Release Apache Qpid Proton-J 0.22.0

[Timothy Bish]

On 09/13/2017 10:35 AM, Robbie Gemmell wrote:

Hi folks,

I have put together a first spin for a Qpid Proton-J 0.22.0 release,
please test it and vote accordingly.

The source and binary archives can be grabbed from:
https://dist.apache.org/repos/dist/dev/qpid/proton-j/0.22.0-rc1/

The maven artifacts are staged for now at:
https://repository.apache.org/content/repositories/orgapacheqpid-1114

The JIRAs assigned are:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12313720&version=12341448

Regards,
Robbie

P.S. If you want to test things out using maven with your own build
you can temporarily add this to your poms to access the staging repo:

   
 
   staging
   
https://repository.apache.org/content/repositories/orgapacheqpid-1114
 
   

The dependency for proton-j would then be:

   
 org.apache.qpid
 proton-j
 0.22.0
   

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



+1
* Validated signatures and checksums
* Inspected license and notice files in the src and binary archives
* built from source and ran the tests
* validated licenses on files using mvn apache-rat:check
* built ActiveMQ 5.x using staged bits and ran AMQP tests
* built ActiveMQ Artemis using staged bits and ran AMQP tests
* built Qpid JMS using staged bits and ran the tests


--
Tim Bish
twitter: @tabish121
blog: http://timbish.blogspot.com/


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

Re: [VOTE] Release Apache Qpid Proton-J 0.21.0

[Timothy Bish]

On 08/31/2017 10:15 AM, Robbie Gemmell wrote:


Hi folks, I have put together a first spin for a Qpid Proton-J 0.21.0 
release, please test it and vote accordingly. The source and binary 
archives can be grabbed from: 
https://dist.apache.org/repos/dist/dev/qpid/proton-j/0.21.0-rc1/ The 
maven artifacts are staged for now at: 
https://repository.apache.org/content/repositories/orgapacheqpid-1113 
The JIRAs assigned are: 
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12313720&version=12341281 
Regards, Robbie P.S. If you want to test things out using maven with 
your own build you can temporarily add this to your poms to access the 
staging repo:   staging 
https://repository.apache.org/content/repositories/orgapacheqpid-1113 
  The dependency for proton-j would then 
be:  org.apache.qpid 
proton-j 0.21.0 
 
- 
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For 
additional commands, e-mail: users-h...@qpid.apache.org




+1
* checked signature and checksums on the archives
* checked that license and notice files are included
* built from source and ran tests on JDK 8 and 9
* built Qpid JMS using staged artifacts and ran tests
* built ActiveMQ 5.x using staged artifacts and ran tests
* built ActiveMQ Artemis master using staged artifacts and ran tests


--
Tim Bish


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

Re: [VOTE] Release Apache Qpid JMS 0.24.0

[Timothy Bish]

On 08/04/2017 05:42 PM, Robbie Gemmell wrote:

Hi folks,

I have put together a spin for a 0.24.0 Qpid JMS client release, please
give it a test out and vote accordingly.

The source and binary archives can be grabbed from:
https://dist.apache.org/repos/dist/dev/qpid/jms/0.24.0-rc1/

The maven artifacts are also staged for now at:
https://repository.apache.org/content/repositories/orgapacheqpid-1112

The JIRAs currently assigned are:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314524&version=12340587

Regards,
Robbie

P.S. If you want to test it out using maven (e.g with the examples src, or
your own things), you can temporarily add this to your poms to access the
staging repo:

   
 
   staging
   
https://repository.apache.org/content/repositories/orgapacheqpid-1112
 
   

The dependency for the client itself would then be:

   
 org.apache.qpid
 qpid-jms-client
 0.24.0
   

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



+1

* Verified signatures and checksums
* Reviewed the release archives for license and notice files
* Built from source and ran tests
* Built ActiveMQ 5.x and ActiveMQ Artemis using the staged bits and ran 
the AMQP tests

* Ran the binary example against ActiveMQ 5.x
* Verified license headers using 'mvn apache-rat:check'

--
Tim Bish


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

Re: Create durable subscription to Azure Service Bus

[Timothy Bish]

On 08/07/2017 09:26 AM, 4 Integration wrote:

Hi,

Testing QPid JMS (AMQP v1.0) with Azure Service Bus (SB).

Trying to get durable subscriptions to work.
I have created a topic in SB

When starting my test app I get:

javax.jms.JMSException: The messaging entity
'mynamespace:topic:test.topic~15|test1' could not be found.
TrackingId:12ecc2a3-f8f3-42a3-8bd5-ad5d9823c367_B20,
SystemTracker:jjarkebo:topic:test.topic~15|test1, Timestamp:8/7/2017
1:23:34 PM TrackingId:b1af76b2b7a44b95ad2bd0e01f406507_G20,
SystemTracker:gateway6, Timestamp:8/7/2017 1:23:34 PM
at
org.apache.qpid.amqp_1_0.jms.impl.TopicSubscriberImpl.createClientReceiver(TopicSubscriberImpl.java:111)
at
org.apache.qpid.amqp_1_0.jms.impl.MessageConsumerImpl.(MessageConsumerImpl.java:129)
at
org.apache.qpid.amqp_1_0.jms.impl.TopicSubscriberImpl.(TopicSubscriberImpl.java:46)
at
org.apache.qpid.amqp_1_0.jms.impl.SessionImpl.createDurableSubscriber(SessionImpl.java:544)
at
org.apache.qpid.amqp_1_0.jms.impl.SessionImpl.createDurableSubscriber(SessionImpl.java:512)
at
org.apache.qpid.amqp_1_0.jms.impl.SessionImpl.createDurableSubscriber(SessionImpl.java:59)
at com.vcrs.test.AmqpJmsSubscriberApp.(AmqpJmsSubscriberApp.java:39)
at com.vcrs.test.AmqpJmsSubscriberApp.main(AmqpJmsSubscriberApp.java:67)

Any ideas why this happen?
Do you have a working example?

My test app code below

import javax.jms.*;
import javax.naming.Context;
import javax.naming.InitialContext;

import org.apache.qpid.amqp_1_0.jms.Connection;
import org.apache.qpid.amqp_1_0.jms.ConnectionFactory;
import org.apache.qpid.amqp_1_0.jms.Destination;
import org.apache.qpid.amqp_1_0.jms.MessageConsumer;
import org.apache.qpid.amqp_1_0.jms.MessageProducer;
import org.apache.qpid.amqp_1_0.jms.Session;

import java.io.BufferedReader;
import java.io.InputStreamReader;
import java.util.Hashtable;
import java.util.Random;

public class AmqpJmsSubscriberApp {
 private Connection connection;
 private Session subscriberSession;
 private MessageConsumer subscriber;

 public AmqpJmsSubscriberApp() throws Exception {
 Hashtable env = new Hashtable();
 env.put(Context.INITIAL_CONTEXT_FACTORY,
"org.apache.qpid.amqp_1_0.jms.jndi.PropertiesFileInitialContextFactory");

 env.put("connectionfactory.SBCF", "amqps://
MyUser:mysecret...@mynamespace.servicebus.windows.net:5671");
 env.put("topic.TOPIC", "test.topic");

 Context context = new InitialContext(env);

 ConnectionFactory cf = (ConnectionFactory) context.lookup("SBCF");
 Topic topic = (Topic) context.lookup("TOPIC");

 connection = cf.createConnection();

 subscriberSession = connection.createSession(false,
Session.CLIENT_ACKNOWLEDGE);
 subscriber = subscriberSession.createDurableSubscriber(topic,
"test1");

 MessageListener messagelistener = new MessageListener()
 {
public void onMessage(Message message)
{
try {
   BytesMessage byteMsg = (BytesMessage)message;

   byte[] byteArr = new byte[(int)byteMsg.getBodyLength()];
   byteMsg.readBytes(byteArr);
   String msg = new String(byteArr);

System.out.println("Received message with JMSMessageID =
" + message.getJMSMessageID());
System.out.println("You said " + msg);
message.acknowledge();
} catch (Exception e) {
e.printStackTrace();
}
}
 };

 subscriber.setMessageListener( messagelistener );
 connection.start();
 }

 public static void main(String[] args) {
 try {
 AmqpJmsSubscriberApp simpleSubscriber = new AmqpJmsSubscriberApp();
 System.out.println("Press [enter] to send a message. Type
'exit' + [enter] to quit.");
 BufferedReader commandLine = new java.io.BufferedReader(new
InputStreamReader(System.in));

 while (true) {
 String s = commandLine.readLine();
 if (s.equalsIgnoreCase("exit")) {
 simpleSubscriber.close();
 System.exit(0);
 }
 }
 } catch (Exception e) {
 e.printStackTrace();
 }
 }

 public void close() throws JMSException {
 connection.close();
 }
}

From the packages you're importing you are not using Qpid JMS but are 
using the legacy AMQP 1.0 JMS client which has not been supported in 
quite some time.  You need to use the Qpid JMS client as documented 
here: http://qpid.apache.org/components/jms/index.html


--
Tim Bish
twitter: @tabish121
blog: http://timbish.blogspot.com/


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

Re: [VOTE] Release Apache Qpid Proton-J 0.20.0

[Timothy Bish]

On 08/02/2017 10:33 AM, Robbie Gemmell wrote:

Hi folks,

I have put together a first spin for a Qpid Proton-J 0.20.0 release,
please test it and vote accordingly.

The source and binary archives can be grabbed from:
https://dist.apache.org/repos/dist/dev/qpid/proton-j/0.20.0-rc1/

(Note: the .sha checksum files are generated using SHA512)

The maven artifacts are staged for now at:
https://repository.apache.org/content/repositories/orgapacheqpid-

The JIRAs currently assigned are:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12313720&version=12341280

Regards,
Robbie

P.S. If you want to test things out using maven with your own build
you can temporarily add this to your poms to access the staging repo:

   
 
   staging
   
https://repository.apache.org/content/repositories/orgapacheqpid-
 
   

The dependency for proton-j would then be:

   
 org.apache.qpid
 proton-j
 0.20.0
   

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



+1

* Reviewed bin and src archives for proper license and notice files
* Validated signatures and checksums
* Built from source and ran the tests.
* Built Qpid JMS using staged binary and ran the tests
* Built Artemis using staged binary and ran test broker AMQP tests.



--
Tim Bish


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

Re: [Qpid JMS client] Asynchronous send JMS 2.0

[Timothy Bish]

On 07/14/2017 09:34 AM, Vavricka wrote:

Hi,

   qpid jms client version - 0.23.0
   qpid c++ broker version - 0.34

   I am unable to send messages asynchronously using the JMS 2.0 API.

   Connection string is same for JMS 1.1 and JMS 2.0 -
"amqp://host:20405?jms.username=admin&jms.password=admin&amqp.traceFrames=true&jms.forceAsyncSend=true&jms.forceAsyncAcks=true"

   When I use JMS 1.1 API, it works ok.

*Code for JMS 1.1 below.*

try
{
 Topic queue = (Topic) initialContext.lookup("node");
 Connection connection = ((ConnectionFactory)
initialContext.lookup("connection")).createConnection();
 Session session = connection.createSession(false,
Session.CLIENT_ACKNOWLEDGE);
 MessageProducer producer = session.createProducer(queue);
 connection.start();
 for (int i = 0; i < 500; i++)
 {
 producer.send(session.createTextMessage("test"));
 }
}
catch
...

  However when I use JMS 2.0 API, sending is extremely slow (1 message per
second).

*Code for JMS 2.0 API below.*

try (JMSContext context =
connectionFactory.createContext(JMSContext.CLIENT_ACKNOWLEDGE))
{
 JMSProducer producer = context.createProducer();
 producer.setAsync(new SendCompletitionListener());
 for (int i = 0; i < senderOptionParser.getMessageCountValue(); i++)
 {
 producer.send(queue, context.createTextMessage("test"));
 }
}
catch
...

*Part of trace output of JMS 1.1 during one message sent:*

{Output before producer.send(session.createTextMessage("test"));}
...
[AmqpProvider:(1):[amqp://host:20405]] TRACE
org.apache.qpid.jms.provider.amqp.AmqpFixedProducer - Producer sending
message: JmsOutboundMessageDispatch {dispatchId =
ID:dfbce852-0cdc-4669-99df-e9d59569b0f6:1:1:1-1, MessageID =
ID:dfbce852-0cdc-4669-99df-e9d59569b0f6:1:1:1-1 }
[AmqpProvider:(1):[amqp://host:20405]] TRACE
org.apache.qpid.jms.provider.amqp.FRAMES - SENT: Transfer{handle=0,
deliveryId=0, deliveryTag=0, messageFormat=0, settled=null, more=false,
rcvSettleMode=null, state=null, resume=false, aborted=false,
batchable=false}
[AmqpProvider:(1):[amqp://host:20405]] TRACE
org.apache.qpid.jms.transports.netty.NettyTcpTransport - Attempted write of:
2283 bytes
...
{Output after producer.send(session.createTextMessage("test"));}

*Part of trace output of JMS 2.0 during one message sent:*

{Output before producer.send(queue, context.createTextMessage("test"));}
...
[AmqpProvider:(1):[amqp://host:20405]] TRACE
org.apache.qpid.jms.provider.amqp.FRAMES - SENT:
Attach{name='qpid-jms:sender:ID:8261d327-2100-47a1-8860-69bc1d0fd6ae:1:-1:1:broadcast',
handle=0, role=SENDER, sndSettleMode=UNSETTLED, rcvSettleMode=FIRST,
source=Source{address='ID:8261d327-2100-47a1-8860-69bc1d0fd6ae:1:-1:1',
durable=NONE, expiryPolicy=SESSION_END, timeout=0, dynamic=false,
dynamicNodeProperties=null, distributionMode=null, filter=null,
defaultOutcome=null, outcomes=[amqp:accepted:list, amqp:rejected:list,
amqp:released:list, amqp:modified:list], capabilities=null},
target=Target{address='broadcast', durable=NONE, expiryPolicy=SESSION_END,
timeout=0, dynamic=false, dynamicNodeProperties=null, capabilities=[topic]},
unsettled=null, incompleteUnsettled=false, initialDeliveryCount=0,
maxMessageSize=null, offeredCapabilities=null,
desiredCapabilities=[DELAYED_DELIVERY], properties=null}
[AmqpProvider:(1):[amqp://host:20405]] TRACE
org.apache.qpid.jms.transports.netty.NettyTcpTransport - Attempted write of:
324 bytes
[epollEventLoopGroup-2-1] TRACE
org.apache.qpid.jms.transports.netty.NettyTcpTransport - New data read: 212
bytes incoming: PooledUnsafeDirectByteBuf(ridx: 0, widx: 212, cap: 65536)
[AmqpProvider:(1):[amqp://host:20405]] TRACE
org.apache.qpid.jms.provider.amqp.FRAMES - RECV:
Attach{name='qpid-jms:sender:ID:8261d327-2100-47a1-8860-69bc1d0fd6ae:1:-1:1:broadcast',
handle=0, role=RECEIVER, sndSettleMode=MIXED, rcvSettleMode=FIRST,
source=Source{address='null', durable=NONE, expiryPolicy=SESSION_END,
timeout=0, dynamic=false, dynamicNodeProperties=null, distributionMode=null,
filter=null, defaultOutcome=null, outcomes=null, capabilities=null},
target=Target{address='broadcast', durable=NONE, expiryPolicy=SESSION_END,
timeout=0, dynamic=false, dynamicNodeProperties=null, capabilities=[topic]},
unsettled=null, incompleteUnsettled=false, initialDeliveryCount=0,
maxMessageSize=null, offeredCapabilities=null, desiredCapabilities=null,
properties=null}
[AmqpProvider:(1):[amqp://host:20405]] TRACE
org.apache.qpid.jms.provider.amqp.FRAMES - RECV: Flow{nextIncomingId=2,
incomingWindow=2147483647, nextOutgoingId=0, outgoingWindow=2147483647,
handle=0, deliveryCount=0, linkCredit=500, available=null, drain=false,
echo=false, properties=null}
[AmqpProvider:(1):[amqp://host:20405]] TRACE
org.apache.qpid.jms.provider.amqp.AmqpProvider - New Proton Event: LINK_INIT
[AmqpProvider:(1):[amqp://host:20405]] TRACE
org.apache.qpid.jms.provider.amqp.AmqpProvider - New Proton Event:
LINK_LOCAL_OPEN
[AmqpProvider:(1):[amqp://host:20405]] TRACE
org.apache.qpid.jms

Re: [VOTE] Release Apache Qpid JMS 0.23.0

[Timothy Bish]

+1

* Verified signatures and checksums
* Built from source archive and ran all tests
* Used apache-rat:check to look for missing license files
* Validated that LICENSE and NOTICE files are in place
* Ran the example included in the binary against ActiveMQ and ActiveMQ 
Artemis

* Built ActiveMQ 5.x using the staged artifacts and ran the unit tests
* Built ActiveMQ Artemis 2.x using the staged artifacts and ran the 
integration tests


On 05/12/2017 12:41 PM, Robbie Gemmell wrote:

Hi folks,

I have put together a spin for a 0.23.0 Qpid JMS client release, please
give it a test out and vote accordingly.

The source and binary archives can be grabbed from:
https://dist.apache.org/repos/dist/dev/qpid/jms/0.23.0-rc1/

The maven artifacts are also staged for now at:
https://repository.apache.org/content/repositories/orgapacheqpid-1106

The JIRAs currently assigned are:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314524&version=12340367

Regards,
Robbie

P.S. If you want to test it out using maven (e.g with the examples src, or
your own things), you can temporarily add this to your poms to access the
staging repo:

   
 
   staging
   
https://repository.apache.org/content/repositories/orgapacheqpid-1106
 
   

The dependency for the client itself would then be:

   
 org.apache.qpid
 qpid-jms-client
 0.23.0
   

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





--
Tim Bish
twitter: @tabish121
blog: http://timbish.blogspot.com/


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

Re: 2017-05-09 22:20:29,796 | ERROR | mix-7.0.0/deploy | BlueprintDeploymentListener | 105 - org.apache.karaf.deployer.blueprint - 4.0.8 | Unable to parse deployed file /tmp/apache-servicemix-7.0.0/de

[Timothy Bish]

It's XML so an & is expressed as "&"

"amqps://esesslx0827.ss.sw.ericsson.se:9443?transport.keyStoreLocation=etc/qpid.jks&transport.keyStorePassword=test123"



On 05/09/2017 06:26 PM, jeunii wrote:

I am trying to setup a connection using SSL.

My config initially was ::

  
 

  

 
   

In order to secure my connection, now Im using ::



As per documentation, I can add a number of parameter by seperating them
using '&'.

But I am getting the ERROR ::

Unable to parse deployed file
/tmp/apache-servicemix-7.0.0/deploy/qpid-routes-iv.xml
org.xml.sax.SAXParseException: The reference to entity
"transport.keyStorePassword" must end with the ';' delimiter.
at
org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(Unknown
Source)[:]


I tried doing the following ::



But Im getting the same ERROR. Ive tried looking at multiple forums but I do
not see the use of ";" as a separator. Im confused as to what is the issue ?
Do I need to update my libraries ?





--
View this message in context: 
http://qpid.2158936.n2.nabble.com/2017-05-09-22-20-29-796-ERROR-mix-7-0-0-deploy-BlueprintDeploymentListener-105-org-apache-karaf-deplR-tp7663005.html
Sent from the Apache Qpid users mailing list archive at Nabble.com.

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





--
Tim Bish
twitter: @tabish121
blog: http://timbish.blogspot.com/


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

Re: AmqpProvider - Transport connection remotely closed

[Timothy Bish]

The error alone without any other context simply indicates that the 
remote end suddenly broke the connection to the client, as to why you'd 
want to try and do some more digging.  One thing to do in these cases is 
to try and capture an AMQP protocol trace to see what's happening on the 
wire, there's some good information in the configuration documentation 
on how to enable such logging on the client: 
http://qpid.apache.org/releases/qpid-jms-0.22.0/docs/index.html




On 05/09/2017 04:47 PM, jeunii wrote:

I am using ServiceMix alongside Apache camel and Qpid libraries to connect to
a remote node to fetch JMS queues.

My Bean config is ::

   
 

   

 
   

  http://camel.apache.org/schema/blueprint";>
 
 

   
   
   
 


Using this bean I start my application and see some positive response ::


| DEBUG | mix-7.0.0/deploy | JmsProducer  | 43 -
org.apache.camel.camel-core - 2.16.4 | Starting producer:
Producer[amqp://queue:///CSDP_input]
| DEBUG | mix-7.0.0/deploy | JmsConsumer  | 43 -
org.apache.camel.camel-core - 2.16.4 | Starting consumer:
Consumer[amqp://queue:///CSDP_output]
| DEBUG | mix-7.0.0/deploy | BlueprintCamelContext| 43 -
org.apache.camel.camel-core - 2.16.4 | Route: route1 >>>
EventDrivenConsumerRoute[Endpoint[amqp://queue:///CS_output] ->
Pipeline[[Channel[Log(route1)[Copying o the output directory]],
Channel[sendTo(Endpoint[amqp://queue:///CS_input])
| DEBUG | mix-7.0.0/deploy | faultJmsMessageListenerContainer | 154 -
org.apache.servicemix.bundles.spring-jms - 3.2.17.RELEASE_1 | Established
shared JMS Connection


But then I get the below ERROR ::


| DEBUG | esesslxjks.se:9443] | AmqpProvider | 226 -
qpid-jms-client.jar - 0.0.0 | Transport connection remotely closed
| DEBUG | esesslxjks.se:9443] | JmsConnection| 226 -
qpid-jms-client.jar - 0.0.0 | Async exception with no exception listener:
java.io.IOException: Connection remotely closed.
java.io.IOException: Connection remotely closed.
  at
org.apache.qpid.jms.provider.amqp.AmqpProvider$18.run(AmqpProvider.java:727)[226:qpid-jms-client.jar:0.0.0]
  at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)[:1.8.0_121]
  at java.util.concurrent.FutureTask.run(FutureTask.java:266)[:1.8.0_121]
  at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)[:1.8.0_121]
  at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)[:1.8.0_121]
  at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)[:1.8.0_121]
  at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)[:1.8.0_121]
  at java.lang.Thread.run(Thread.java:745)[:1.8.0_121]


I am currently clueless as to why this would happen ? What other possible
debugging can I do ? Any pointers would be highly recommended.



--
View this message in context: 
http://qpid.2158936.n2.nabble.com/AmqpProvider-Transport-connection-remotely-closed-tp7663002.html
Sent from the Apache Qpid users mailing list archive at Nabble.com.

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





--
Tim Bish
twitter: @tabish121
blog: http://timbish.blogspot.com/


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

Re: [VOTE] Release Apache Qpid Proton-J 0.19.0

[Timothy Bish]

+1

* Checked signatures and checksums
* Built from source and ran tests
* used mvn apache-rat:check to look for missing license headers
* Checked for license and notice files in the archives
* Used staged version with Qpid JMS to run all tests
* Used staged version with ActiveMQ 5.x to run the AMQP tests
* Used staged version with Artemis master to run all its AMQP tests

On 05/02/2017 01:14 PM, Robbie Gemmell wrote:

Hi folks,

I have put together a first spin for a Qpid Proton-J 0.19.0 release,
please test it and vote accordingly.

The source and binary archives can be grabbed from:
https://dist.apache.org/repos/dist/dev/qpid/proton-j/0.19.0-rc1/

(Note: the .sha checksum files are generated using SHA512)

The maven artifacts are staged for now at:
https://repository.apache.org/content/repositories/orgapacheqpid-1105

The JIRAs currently assigned are:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12313720&version=12340043

Regards,
Robbie

P.S. If you want to test things out using maven with your own build
you can temporarily add this to your poms to access the staging repo:

   
 
   staging
   
https://repository.apache.org/content/repositories/orgapacheqpid-1105
 
   

The dependency for proton-j would then be:

   
 org.apache.qpid
 proton-j
 0.19.0
   

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





--
Tim Bish
twitter: @tabish121
blog: http://timbish.blogspot.com/


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

Re: [VOTE] Release Apache Qpid JMS 0.22.0

[Timothy Bish]

On 04/17/2017 01:34 PM, Robbie Gemmell wrote:

Hi folks,

I have put together a spin for a 0.22.0 Qpid JMS client release, please
give it a test out and vote accordingly.

The source and binary archives can be grabbed from:
https://dist.apache.org/repos/dist/dev/qpid/jms/0.22.0-rc1/

The maven artifacts are also staged for now at:
https://repository.apache.org/content/repositories/orgapacheqpid-1104

The JIRAs currently assigned are:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314524&version=12340042

Regards,
Robbie

P.S. If you want to test it out using maven (e.g with the examples src, or
your own things), you can temporarily add this to your poms to access the
staging repo:

   
 
   staging
   
https://repository.apache.org/content/repositories/orgapacheqpid-1104
 
   

The dependency for the client itself would then be:

   
 org.apache.qpid
 qpid-jms-client
 0.22.0
   

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




+1

* validated signatures and checksums
* checked for license and notice files present in src and bin
* built from the source archive and ran tests
* ran the HelloWorld example against ActiveMQ 5.14.5 and Artemis 2.0.0
* built an ActiveMQ 5.x snapshot and ran the Qpid JMS based tests
* ran mvn apache-rat:check to ensure no missing license files.


--
Tim Bish
twitter: @tabish121
blog: http://timbish.blogspot.com/


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

Re: One subscription, multiple consumers.

[Timothy Bish]

On 04/11/2017 12:42 PM, Robbie Gemmell wrote:

For the most part topic subscriptions only ever had a single
subscriber asociated with them, until at some point someone thought it
would be useful to support more. Some systems can do that, others
cant, others still have specific mechanisms to achieve the same
effect.

This is all completely independent of the concepts of sessions and
connections. You could have a single session with lots of subscribers
on it, or lots of sessions with a single subscriber, but that doesnt
particularly influence whether they can share a single subscription or
not, the messaging system itself does. Various messaging systems now
support doing that in their own way, hence my original question what
you were using. In ActiveMQ 5.x its abilities are closely related to
JMS 1.1, and I beleive its only method of achieving the shared
subscribers effect is Virtual Destinations, effectively turning each
subscriber for a given subscription into a specific queue consumer as
you note.

We recently mapped out a mechanism to support shared subscriptions
over AMQP 1.0 such that the JMS 2.0 shared subscriptions functionlity
could be supported for the Qpid JMS client. I'm only aware of 2
brokers that already implement support for the precise mechanism it
uses, ActiveMQ Artemis (I think 2.x is needed) and the upcoming Qpid
Broker-J 7.0.0. The Qpid C++ broker also supports a variant of shared
susbcriptions over AMQP 1.0, but does not currently support the
precise mechanism required by the JMS 2.0 client. You could similarly
use those mechanisms from other AMQP 1.0 clients, or alternatively
there may be other broker-specific mechanisms for achieving the same
effect, but as far as ActiveMQ 5.x is concerned, I beleive your only
option is Virtual Topics.


That is correct, you'd need to use Virtual Topic subscriptions for this 
scenario.




Robbie

On 11 April 2017 at 16:57, Jeremy Gooch  wrote:

If I understand this correctly, the limitation with regard to only a single 
consumer on one topic is in order to maintain compliance with the JMS 
specification.  ActiveMQ's Virtual Destinations give a workaround for this 
where a producer will publish to a topic as normal whilst allowing a consumer 
to connect as if to a queue, thereby enabling the consumer to operate multiple 
connections to increase its message consumption rate.

The AMQP model has the concept of sessions within a connection.  Is it possible 
therefore to have multiple sessions within a connection against a single 
subscription without using Virtual Destinations?  We could then use a client 
with some sort of concurrency feature to operate multiple sessions and increase 
message consumption.
J.

Jeremy Gooch http://goochgooch.co.uk

   From: Robbie Gemmell 
  To: "users@qpid.apache.org" 
  Sent: Tuesday, 11 April 2017, 14:49
  Subject: Re: One subscription, multiple consumers.

With ActiveMQ 5 I think your only option would be Virtual Topics,
http://activemq.apache.org/virtual-destinations.html

On 11 April 2017 at 13:17, Jeremy Gooch  wrote:

It's...
- ActiveMQ 5.14- Python 3 (running in Docker)- Latest version of Qpid Proton 
(installed via pip3)
J.
Jeremy Gooch http://goochgooch.co.uk

  From: Robbie Gemmell 
  To: "users@qpid.apache.org" 
  Sent: Monday, 10 April 2017, 15:55
  Subject: Re: One subscription, multiple consumers.

Answers here are likely to be quite dependent on which server, and
which version of it, that you are actually using.

On 10 April 2017 at 10:06, Jeremy Gooch  wrote:

Hello,
Using Qpid Proton (mainly Python), I know you can have multiple consumers 
against one queue and they operate in a race condition.
But can the same happen with a subscription?  In other words, how do I 
configure multiple consumers against one subscription so that messages are 
distributed amongst them?  This has come up as a requirement to support an 
auto-scaling client, who wants to make multiple connections to a durable 
subscription but not receive duplicate messages.
Thanks,
J.

Jeremy Gooch http://goochgooch.co.uk

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




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




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





--
Tim Bish
twitter: @tabish121
blog: http://timbish.blogspot.com/


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

Re: [VOTE] Migrate Qpid Broker J and Qpid JMS AMQP 0-x Client from SVN to GIT

[Timothy Bish]

+1

On 04/04/2017 08:44 AM, Keith W wrote:

As already proposed and discussed in the following thread:

http://qpid.2158936.n2.nabble.com/DISCUSS-Migrate-Qpid-Broker-for-Java-and-Qpid-JMS-AMQP-0-x-Client-from-SVN-to-GIT-tt7661505.html#none

In summary, the proposal is:

Qpid Broker J:

Current SVN location: https://svn.apache.org/repos/asf/qpid/java/
Proposed GIT repo: https://git-wip-us.apache.org/repos/asf/qpid-broker-j.git

The existing GIT svn mirror at git://git.apache.org/qpid-java.git would cease.

Qpid JMS AMQP 0-x Client:

Current SVN location: https://svn.apache.org/repos/asf/qpid/qpid-jms-amqp-0-x/
Proposed GIT repo: https://git-wip-us.apache.org/repos/asf/qpid-jms-amqp-0-x.git

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

.




--
Tim Bish
twitter: @tabish121
blog: http://timbish.blogspot.com/


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

Re: [VOTE] Release Apache Qpid JMS 0.21.0

[Timothy Bish]

+1

* Validated the signatures and checksums
* Checked for license and notice files in the source and binary archives
* Built from source and ran the tests.
* Checked the binary archive for the proper files
* Built an ActiveMQ 5.x broker against the staged bits and ran the AMQP 
tests.


On 03/10/2017 12:13 PM, Robbie Gemmell wrote:

Hi folks,

I have put together a spin for a 0.21.0 Qpid JMS client release,
please test it and vote accordingly.

The source and binary archives can be grabbed from:
https://dist.apache.org/repos/dist/dev/qpid/jms/0.21.0-rc1/

(Note: the .sha files contain SHA512 checksums)

The maven artifacts are also staged for now at:
https://repository.apache.org/content/repositories/orgapacheqpid-1102

Regards,
Robbie


P.S. If you want to test it out using maven (e.g with the examples
src, or your own things), you can temporarily add this to your poms to
access the staging repo:

   
 
   staging
   
https://repository.apache.org/content/repositories/orgapacheqpid-1102
 
   

The dependency for the client itself would then be:

   
 org.apache.qpid
 qpid-jms-client
 0.21.0
   

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





--
Tim Bish
twitter: @tabish121
blog: http://timbish.blogspot.com/


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

Re: [VOTE] Release Apache Qpid Proton-J 0.18.0

[Timothy Bish]

+1

* validated signatures and sums
* built from source and ran the tests,
* built ActiveMQ using the staged artifacts and ran the tests
* built Qpid JMS using the staged artifacts and ran the tests.
* Checked the License and NOTICE files

Issue with downloading the sha file from the site as it came out as 
binary, did an svn checkout and those were fine, Robbie seems to have 
chased down the root cause of that.


On 03/07/2017 01:13 PM, Robbie Gemmell wrote:

Hi folks,

I have put together a first spin for a Qpid Proton-J 0.18.0 release,
please test it and vote accordingly.

The source and binary archives can be grabbed from:
https://dist.apache.org/repos/dist/dev/qpid/proton-j/0.18.0-rc1/

(Note: the .sha checksum files are generated using SHA512)

The maven artifacts are staged for now at:
https://repository.apache.org/content/repositories/orgapacheqpid-1101

The JIRAs currently assigned are:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12313720&version=12339143

Regards,
Robbie

P.S. If you want to test things out using maven with your own build
you can temporarily add this to your poms to access the staging repo:

   
 
   staging
   
https://repository.apache.org/content/repositories/orgapacheqpid-1101
 
   

The dependency for proton-j would then be:

   
 org.apache.qpid
 proton-j
 0.18.0
   

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





--
Tim Bish
twitter: @tabish121
blog: http://timbish.blogspot.com/


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

Re: [DISCUSS] release checksum filename extension

[Timothy Bish]

On 03/07/2017 12:23 PM, Robbie Gemmell wrote:

According to http://www.apache.org/dev/release-distribution.html#sigs-and-sums
.sha is actually required:

"An SHA checksum SHOULD also be created and MUST be suffixed .sha. The
checksum SHOULD be generated using SHA512."

I find the extension a little unhelpful personally, but ok.. :)


I would have voted for .sha256 for clarity



Robbie

On 7 March 2017 at 17:11, Robbie Gemmell  wrote:

Hi folks,

I noted in the qpid-python-1.36.0 vote thread that the .sha file
contained a sha256 checksum, this being in place of the historic .sha1
checksum file.

I'm curious what people think about the name relative to the contents?
I think .sha256 might be friendlier so that people know how to try and
verify it implicitly from its name?

I mainly ask as I think I'll include one for the proton-j-0.18.0
release im about to cut, and am trying to settle on a name for it.

Robbie

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





--
Tim Bish
twitter: @tabish121
blog: http://timbish.blogspot.com/


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

Re: synchronous sending - using javax.jms.MessageProducer::send

[Timothy Bish]

On 03/07/2017 09:21 AM, Vince Cole wrote:

I have a requirement to for my JMS client to block, and only return once
the message has been accepted onto the specified queue or topic. If the
message is not accepted, then an exception should be thrown. We don't care
whether anything actually consumes the message.

However, my client can only seem to produce messages in asynchronous mode!
So if there's an exception, all we can do is log it. That's not enough, I
need the client application to keep the message (so it can retry later) and
only drop it once the broker has accepted it into the specified
queue/topic.

I am using:
* javax.jms : javax.jms-api : 2.0.1
* org.apache.qpid : qpid-jms-client : 0.11.1


The client offers documentation of all the configuration options some of 
which control when messages are sent sync or async, give that a look.


http://qpid.apache.org/releases/qpid-jms-0.11.1/docs/index.html


* org.apache.qpid : qpid-amqp-1-0-client-jms : 0.32
* The broker is ActiveMQ 5.14.0, if that makes any difference.

Please could you advise if the Qpid Java client library supports synchronous
  production and if so what settings to use, to acheive that, in the
following (where relevant):
* Options in the transport URI (in activemq.xml)
* Options in the connection URI (used by the client)
* Whether messages need to be 'persistent' or not?
* Whether the producer's JMS session should be transacted or not?
* What 'acknowledge mode' to set?
* Whether having a 'ConnectionListener' set on the connection will force it
to be asynchronous, regardless?

Thanks in advance.




--
Tim Bish
twitter: @tabish121
blog: http://timbish.blogspot.com/


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

Re: Performance degradation with Qpid JMS Client 0.20.0

[Timothy Bish]

This should be fixed now and will be part of the next release.
https://issues.apache.org/jira/browse/QPIDJMS-269

On 03/01/2017 12:29 PM, Oleksandr Rudyy wrote:

Hi Tim,

Please find attached a sample application testing transaction
throughput for one publishing and one consuming connections.
By running it on my machine I see a difference in performance of ~15%
between 0.11.0 and 0.20.0.

Our performance test suite uses 10 publishing and 10 consuming
connections. The difference in performance is a bit bigger with it.

Btw, you can run the suite from qpid-java project using

mvn integration-test -f ./perftests/pom.xml -DskipTests=true \
-Dperftests=qpid-jms-client  -Dqpid.disttest.duration=2   \
-Dperftests.hillclimb=true -Dperftests.hillclimb.minimum_delta=100
-Dperftests.hillclimb.max_runs=2 \
-Dperftests.test-config=./perftests/etc/testdefs \
-Dqpid-jms-client-version=0.11.0 \
  /// <--- parameters below are default values and can be skipped
-Dperftests.messaging-hostport-plain=localhost:5672 \
-Dperftests.messaging-hostport-tls=localhost:5671 \
-Dperftests.messaging-user=guest \
-Dperftests.messaging-password=guest \
-Dperftests.broker-virtualhostnode=default \
-Dperftests.broker-virtualhost=default \
-Dperftests.manangement-url=http://localhost:8080 \
-Dperftests.manangement-user=guest \
-Dperftests.manangement-password=guest \
-Dperftests.broker-virtualhostnode=default


The basic authentication needs to be enabled on http port in order to
run the suite. The suite contains 2 transaction and 2 auto ack tests.
Only transactions tests are affected. The difference in performance
for Auto ack is unnoticeable.
Potentially you can comment auto-ack tests in
./perftests/etc/testdefs/defaultTests.js and run only transaction
tests.

Kind Regards,
Alex

On 28 February 2017 at 17:04, Timothy Bish  wrote:

On 02/28/2017 08:10 AM, Oleksandr Rudyy wrote:

Hi all,

After upgrading Qpid JMS Client from version 0.11.0 to version 0.20.0
our performance test results  dropped approximately on 20-25% in the
performance tests testing transaction performance with trunk version
of Qpid Java Broker.

Changing client back to v0.11.0 and re-running the tests yields me the
same results as before the upgrade.

What changes on the client could be the reason for a performance drop?





--
Tim Bish
twitter: @tabish121
blog: http://timbish.blogspot.com/


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

Re: Performance degradation with Qpid JMS Client 0.20.0

[Timothy Bish]

On 02/28/2017 08:10 AM, Oleksandr Rudyy wrote:

Hi all,

After upgrading Qpid JMS Client from version 0.11.0 to version 0.20.0
our performance test results  dropped approximately on 20-25% in the
performance tests testing transaction performance with trunk version
of Qpid Java Broker.

Changing client back to v0.11.0 and re-running the tests yields me the
same results as before the upgrade.

What changes on the client could be the reason for a performance drop?


There was a great deal of change in the client to implement the extra 
bits needed to meet the JMS 2.0 specification requirements along with 
other changes to handle of the more interesting edge cases around JMS 
usages so it'd be hard to just pull out one change as the culprit 
without more research.  I'm not that surprised that there were some impacts.


What would be helpful would be to pull out one affected test case where 
you see this drop in performance into a standalone test so we could run 
it in the Qpid JMS test suite and do some digging.



The performance test creates 10 publishing connections and 10
consuming connections. They produce/consume every message in separate
transactions. The consumer is synchronous. Each pair of producer and
consumer uses its own queue.

Kind Regards,
Alex

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





--
Tim Bish
twitter: @tabish121
blog: http://timbish.blogspot.com/


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

Re: [JMS]How to verify the connection is ready for creating session

[Timothy Bish]

On 02/14/2017 02:32 PM, pqvchen1 wrote:

Just question further, is there a way that I can check whether the connection
or session is healthy? and ready to send/receive message before I doing so?
thanks again. Final question.


You can send a message, and if it throws an exception then it's not 
healthy.


If you use the failover option then it will attempt to reconnect if the 
connection goes down and your send will block until it gets a new 
connection or until your configured send timeout expires.





--
View this message in context: 
http://qpid.2158936.n2.nabble.com/JMS-How-to-verify-the-connection-is-ready-for-creating-session-tp7659153p7659167.html
Sent from the Apache Qpid users mailing list archive at Nabble.com.

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





--
Tim Bish
twitter: @tabish121
blog: http://timbish.blogspot.com/


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

Re: [JMS]How to verify the connection is ready for creating session

[Timothy Bish]

On 02/14/2017 02:12 PM, pqvchen1 wrote:

Thanks for reply. So can I just keep that connection open and not close even
after the session is done? and reuse the connection for next createSession?



Yes, the Connection can remain open an be used to create multiple 
sessions either at once or many over time.




--
View this message in context: 
http://qpid.2158936.n2.nabble.com/JMS-How-to-verify-the-connection-is-ready-for-creating-session-tp7659153p7659164.html
Sent from the Apache Qpid users mailing list archive at Nabble.com.

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





--
Tim Bish
twitter: @tabish121
blog: http://timbish.blogspot.com/


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

Re: [VOTE] Release Qpid Proton-J 0.17.0

[Timothy Bish]

+1

* Review the license and notice files
* Verified the signatures and checksums
* Checked using the rat check goal that all files are licensed properly
* Built from source and ran the tests
* Built Qpid JMS using the staged artifact and ran the tests
* Built ActiveMQ using the staged artifact and ran the tests


On 02/03/2017 12:03 PM, Robbie Gemmell wrote:

Hi folks,

I have put together a first spin for a 0.17.0 Qpid Proton-J release, please
test it and vote accordingly.

The source and binary archives can be grabbed from:
https://dist.apache.org/repos/dist/dev/qpid/proton-j/0.17.0-rc1/

The maven artifacts are staged for now at:
https://repository.apache.org/content/repositories/orgapacheqpid-1100

The JIRAs currently assigned are:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12313720&version=12338961

Regards,
Robbie

P.S. If you want to test things out using maven (e.g with your own build)
you can temporarily add this to your poms to access the staging repo:

   
 
   staging
   
https://repository.apache.org/content/repositories/orgapacheqpid-1100
 
   

The dependency for proton-j would then be:

   
 org.apache.qpid
 proton-j
 0.17.0
   

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





--
Tim Bish
twitter: @tabish121
blog: http://timbish.blogspot.com/


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

Re: [VOTE] Release Qpid JMS client 0.20.0

[Timothy Bish]

+1

* Validated the signatures and sums
* Reviewed the License and Notice files
* Reviewed the documentation file
* Built from source and ran the tests
* Used the staged artifacts in the ActiveMQ AMQP test suite
* Ran the provided examples against an ActiveMQ broker

On 01/16/2017 01:38 PM, Robbie Gemmell wrote:

Hi folks,

I have put together a spin for a 0.20.0 Qpid JMS client release,
please test it and vote accordingly.

The source and binary archives can be grabbed from:
https://dist.apache.org/repos/dist/dev/qpid/jms/0.20.0-rc1/

Those files and the other maven artifacts are also staged for now at:
https://repository.apache.org/content/repositories/orgapacheqpid-1097

Regards,
Robbie


P.S. If you want to test it out using maven (e.g with the examples
src, or your own things), you can temporarily add this to your poms to
access the staging repo:

   
 
   staging
   
https://repository.apache.org/content/repositories/orgapacheqpid-1097
 
   

The dependency for the client itself would then be:

   
 org.apache.qpid
 qpid-jms-client
 0.20.0
   

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





--
Tim Bish
twitter: @tabish121
blog: http://timbish.blogspot.com/


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

Re: [VOTE] Release Qpid JMS client 0.20.0

[Timothy Bish]

On 01/16/2017 02:29 PM, Adel Boutros wrote:

Hello Robbie,


Out of curiosity, can you please explain why the release is 0.20.0 and not 
0.12.0?

When will an official 1.0.0 be out?


The main reason for the bump is that this version now implements the JMS 
2.0 API and is therefore a larger shift in features and code changes 
that a version 0.12.0 would imply.


There are no plans for a 1.0.0 release at this time.



Regards,

Adel


From: Robbie Gemmell 
Sent: Monday, January 16, 2017 7:38:04 PM
To: users@qpid.apache.org
Subject: [VOTE] Release Qpid JMS client 0.20.0

Hi folks,

I have put together a spin for a 0.20.0 Qpid JMS client release,
please test it and vote accordingly.

The source and binary archives can be grabbed from:
https://dist.apache.org/repos/dist/dev/qpid/jms/0.20.0-rc1/

Those files and the other maven artifacts are also staged for now at:
https://repository.apache.org/content/repositories/orgapacheqpid-1097

Regards,
Robbie


P.S. If you want to test it out using maven (e.g with the examples
src, or your own things), you can temporarily add this to your poms to
access the staging repo:

   
 
   staging
   
https://repository.apache.org/content/repositories/orgapacheqpid-1097
 
   

The dependency for the client itself would then be:

   
 org.apache.qpid
 qpid-jms-client
 0.20.0
   

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





--
Tim Bish
twitter: @tabish121
blog: http://timbish.blogspot.com/


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

Re: [Qpid JMS 0.11.1] Nullpointer exception when providing an empty string to the ConnectionFactory

[Timothy Bish]

On 01/13/2017 10:08 AM, Adel Boutros wrote:

Hello Tim,


I took a look on the master brunch of the github repo and indeed it seems to be 
fixed.


Regards,

Adel


I made some additional changes to make the error reporting more consistent.




From: Timothy Bish 
Sent: Friday, January 13, 2017 3:30:59 PM
To: users@qpid.apache.org
Subject: Re: [Qpid JMS 0.11.1] Nullpointer exception when providing an empty 
string to the ConnectionFactory

On 01/13/2017 08:41 AM, Adel Boutros wrote:

Hello,


While playing around with the JMS API, we noticed that if an empty string is passed to 
the JmsConnectionFactory constructor, it will throw back a NullPointerException because 
it tries to access the ".toString" of a NULL URL (See createURI).


Do you agree that it would be better to throw an exception which clearly says 
an empty String URL is forbidden? If yes, I will add a jira issue for it.


public static void main(String[] args) {
  new JmsConnectionFactory("");
}


Output



Exception in thread "main" java.lang.NullPointerException
at 
org.apache.qpid.jms.JmsConnectionFactory.(JmsConnectionFactory.java:115)
at 
org.apache.qpid.jms.JmsConnectionFactory.(JmsConnectionFactory.java:111)


Regards,

Adel


I will take a look at the code again, some things were fixed recently in
QPIDJMS-245 but there's probably a few more defensive checks needed to
keep people from hitting this.


--
Tim Bish
twitter: @tabish121
blog: http://timbish.blogspot.com/


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





--
Tim Bish
twitter: @tabish121
blog: http://timbish.blogspot.com/


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

Re: [Qpid JMS 0.11.1] Nullpointer exception when providing an empty string to the ConnectionFactory

[Timothy Bish]

On 01/13/2017 08:41 AM, Adel Boutros wrote:

Hello,


While playing around with the JMS API, we noticed that if an empty string is passed to 
the JmsConnectionFactory constructor, it will throw back a NullPointerException because 
it tries to access the ".toString" of a NULL URL (See createURI).


Do you agree that it would be better to throw an exception which clearly says 
an empty String URL is forbidden? If yes, I will add a jira issue for it.


public static void main(String[] args) {
 new JmsConnectionFactory("");
}


Output



Exception in thread "main" java.lang.NullPointerException
at 
org.apache.qpid.jms.JmsConnectionFactory.(JmsConnectionFactory.java:115)
at 
org.apache.qpid.jms.JmsConnectionFactory.(JmsConnectionFactory.java:111)


Regards,

Adel



I will take a look at the code again, some things were fixed recently in 
QPIDJMS-245 but there's probably a few more defensive checks needed to 
keep people from hitting this.



--
Tim Bish
twitter: @tabish121
blog: http://timbish.blogspot.com/


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

Re: [VOTE] Release Qpid Proton 0.16.0

[Timothy Bish]

+1

* Checked signatures and checksums
* Built from source and ran tests using cmake
* Built proton-j using maven and ran the tests
* Reviewed License, Notice, and other documentation files
* Built ActiveMQ using the staged artifacts and ran the AMQP tests
* Built Qpid JMS using the staged artifacts and ran the tests.

On 12/08/2016 12:26 PM, Robbie Gemmell wrote:

Hi folks,

I have put together a first spin for a 0.16.0 Qpid Proton release, please
test it and vote accordingly.

The source archive can be grabbed from:
https://dist.apache.org/repos/dist/dev/qpid/proton/0.16.0-rc1/

The maven artifacts for proton-j are staged for now at:
https://repository.apache.org/content/repositories/orgapacheqpid-1094

The JIRAs currently assigned are:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12313720&version=12338399

It is tagged as 0.16.0-rc1 from the 0.16.x branch.

Regards,
Robbie


P.S. If you want to test things out using maven (e.g with your own build)
you can temporarily add this to your poms to access the staging repo:

   
 
   staging
   
https://repository.apache.org/content/repositories/orgapacheqpid-1094
 
   

The dependency for proton-j would then be:

   
 org.apache.qpid
 proton-j
 0.16.0
   

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





--
Tim Bish
twitter: @tabish121
blog: http://timbish.blogspot.com/


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

Re: Qpid JMS client JmsConnection.close() hangs

[Timothy Bish]

Close timeout handling has been fixed up a fair bit with issue:
https://issues.apache.org/jira/browse/QPIDJMS-228

On 11/25/2016 11:04 AM, Robbie Gemmell wrote:

"I also think I see an issue with the closeTimeout handling in that in
one place it seems likely to be using the requestTimeout value
instead. Need to investigate that further."

Though in my attemps that didnt actually matter and the close
completed fine if the network dropped and no response could be
received (or was ever sent). As I say, needs more investigation.

On 25 November 2016 at 15:49, DraCzech  wrote:

I'll try to find a way of preventing this problem from happening. (Though I'm
not sure how to do that properly at the moment.)

But how do you explain unlimited waiting for Close frame response as shown
in my previous post?


DraCzech wrote

2016-11-24 16:41:45.202589  [19105288:0] -> Close{error=null}

on network lost vs.

2016-11-24 16:51:31.027968  [18734493:0] -> Close{error=null}
2016-11-24 16:51:31.977722  [18734493:0] <- Close{error=null}

Shouldn't some timeout throw an exception or so?



--
View this message in context: 
http://qpid.2158936.n2.nabble.com/Qpid-JMS-client-JmsConnection-close-hangs-tp7654565p7654872.html
Sent from the Apache Qpid users mailing list archive at Nabble.com.

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


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





--
Tim Bish
twitter: @tabish121
blog: http://timbish.blogspot.com/


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

Re: [VOTE] Release Qpid Proton 0.15.0

[Timothy Bish]

+1

* Validated signatures and checksums
* Built from source using CMake and Maven (proton-j) and ran tests
* Tested ActiveMQ broker using the staged libraries

On 10/10/2016 01:20 PM, Robbie Gemmell wrote:

Hi folks,

I have put together a spin for a 0.15.0 Qpid Proton release as proposed,
please test it and vote accordingly.

The source archive can be grabbed from:
https://dist.apache.org/repos/dist/dev/qpid/proton/0.15.0-rc1/

The maven artifacts for proton-j are staged for now at:
https://repository.apache.org/content/repositories/orgapacheqpid-1088

The JIRAs still need tidied up a bit, but those currently assigned are:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12313720&version=12337973

Regards,
Robbie


P.S. If you want to test things out using maven (e.g with your own build)
you can temporarily add this to your poms to access the staging repo:

   
 
   staging
   
https://repository.apache.org/content/repositories/orgapacheqpid-1088
 
   

The dependency for proton-j would then be:

   
 org.apache.qpid
 proton-j
 0.15.0
   

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





--
Tim Bish
twitter: @tabish121
blog: http://timbish.blogspot.com/


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

Re: [VOTE] Release Qpid JMS client 0.11.1

[Timothy Bish]

+1

* Reviewed the bin and src for license and notice files
* Checked signatures and checksums
* Built from source and ran the tests
* Built ActiveMQ using staged bits and ran its tests
* Ran the included example against an ActiveMQ 5.14.1 broker

On 09/30/2016 11:24 AM, Robbie Gemmell wrote:

Hi folks,

I have put together a spin for a 0.11.1 Qpid JMS client release, please
test it and vote accordingly.

There are a few small changes included:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314524&version=12338292

The source and binary archives can be grabbed from:
https://dist.apache.org/repos/dist/dev/qpid/jms/0.11.1-rc1/

Those files and the other maven artifacts are also staged for now at:
https://repository.apache.org/content/repositories/orgapacheqpid-1086

Regards,
Robbie


P.S. If you want to test it out using maven (e.g with the examples src,
or your own things), you can temporarily add this to your poms to access
the staging repo:

   
 
   staging
   
https://repository.apache.org/content/repositories/orgapacheqpid-1086
 
   

The dependency for the client itself would then be:

   
 org.apache.qpid
 qpid-jms-client
 0.11.1
   

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





--
Tim Bish
twitter: @tabish121
blog: http://timbish.blogspot.com/


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

Re: [VOTE] Release Qpid JMS client 0.11.0

[Timothy Bish]

+1

* Reviewed the source and binary distribution files
* Checked license and notice files
* Validated Signatures and Checksums
* Built from the source distributions and ran the tests.
* Tested an ActiveMQ 5.x broker using the staged artifacts
* Ran the example against an existing ActiveMQ 5.x broker.

On 09/05/2016 11:47 AM, Robbie Gemmell wrote:

Hi folks,

I have put together a spin for a 0.11.0 Qpid JMS client release, please
test it and vote accordingly.

The source and binary archives can be grabbed from:
https://dist.apache.org/repos/dist/dev/qpid/jms/0.11.0-rc1/

Those files and the other maven artifacts are also staged for now at:
https://repository.apache.org/content/repositories/orgapacheqpid-1085

Regards,
Robbie


P.S. If you want to test it out using maven (e.g with the examples src,
or your own things), you can temporarily add this to your poms to access
the staging repo:

   
 
   staging
   
https://repository.apache.org/content/repositories/orgapacheqpid-1085
 
   

The dependency for the client itself would then be:

   
 org.apache.qpid
 qpid-jms-client
 0.11.0
   

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





--
Tim Bish
twitter: @tabish121
blog: http://timbish.blogspot.com/


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

Re: [VOTE] Release Qpid Proton 0.14.0

[Timothy Bish]

+1

* Built from source and ran all the tests
* Checked signature and sums
* Validated License and NOTICE files
* Ran Qpid JMS tests using the 0.14.0 maven dep
* Ran ActiveMQ 5.x tests using the 0.14.0 maven dep

On 08/17/2016 10:06 AM, Justin Ross wrote:

The artifacts proposed for release:

   https://dist.apache.org/repos/dist/dev/qpid/proton/0.14.0-rc/

Please indicate your vote below.  If you favor releasing the 0.14.0 RC bits
as 0.14.0 GA, vote +1.  If you have reason to think the RC is not ready for
release, vote -1.

Thanks,
Justin

---
Proton 0.14.0 release page:
https://cwiki.apache.org/confluence/display/qpid/Qpid+Proton+0.14.0




--
Tim Bish
twitter: @tabish121
blog: http://timbish.blogspot.com/


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

Re: Cannot conect while using ActiveMQ with Qpid JMS client

[Timothy Bish]

What is the connection URI that you are giving the client 
JmsConnectionFactory?


On 07/19/2016 08:28 AM, DraCzech wrote:

One thing I found out is that activemq-amqp artifact has proton-j compile
dependency:

+- org.apache.activemq:activemq-amqp:jar:5.13.3:compile
|  \- org.apache.qpid:proton-j:jar:0.12.1:compile

But that one was overridden by direct dependency when I used it (and the
issue had occurred even at that time). I now removed the activemq-amqp
dependency from the project so the tree now look like this:

--- maven-dependency-plugin:2.8:tree (default-cli) @ databroker ---
com.openmatics.box:databroker:bundle:3.6.0-SNAPSHOT
+- org.osgi:org.osgi.core:jar:4.2.0:compile
+- org.osgi:org.osgi.compendium:jar:4.2.0:compile
+- joda-time:joda-time:jar:1.6.2:compile
+- log4j:log4j:jar:1.2.14:compile
+- org.sonatype.tycho:org.eclipse.osgi:jar:3.5.1.R35x_v20090827:compile
 > Bunch of company bundles < 
+- org.glassfish.main.admin:javax.management.j2ee:jar:3.1.2:compile
|  \- org.glassfish.main.ejb:javax.ejb:jar:3.1.2:compile
| +- org.glassfish.main.transaction:javax.transaction:jar:3.1.2:compile
| \- org.glassfish.main.javaee-api:javax.annotation:jar:3.1.2:compile
+- org.jasypt:jasypt:jar:1.7:compile
+- org.slf4j:slf4j-api:jar:1.6.1:compile
+- org.slf4j:slf4j-log4j12:jar:1.6.1:compile
+- org.springframework:spring-context:jar:3.0.3.RELEASE:compile
+- org.springframework:spring-aop:jar:3.0.3.RELEASE:compile
|  \- aopalliance:aopalliance:jar:1.0:compile
+- org.springframework:spring-beans:jar:3.0.3.RELEASE:compile
+- org.springframework:spring-core:jar:3.0.3.RELEASE:compile
+- org.springframework:spring-expression:jar:3.0.3.RELEASE:compile
+- org.springframework:spring-asm:jar:3.0.3.RELEASE:compile
+- org.apache.activemq:activemq-broker:jar:5.13.3:compile
|  \- org.apache.activemq:activemq-openwire-legacy:jar:5.13.3:compile
+- org.apache.activemq:activemq-client:jar:5.13.3:compile
|  +- org.apache.geronimo.specs:geronimo-jms_1.1_spec:jar:1.1.1:compile
|  \-
org.apache.geronimo.specs:geronimo-j2ee-management_1.1_spec:jar:1.0.1:compile
+- org.apache.activemq:activemq-kahadb-store:jar:5.13.3:compile
|  +- org.apache.activemq.protobuf:activemq-protobuf:jar:1.1:compile
|  \- commons-net:commons-net:jar:2.2:compile
+- org.apache.activemq:activemq-spring:jar:5.13.3:compile
|  +- org.apache.activemq:activemq-pool:jar:5.13.3:compile
|  |  \- org.apache.activemq:activemq-jms-pool:jar:5.13.3:compile
|  +- org.apache.geronimo.specs:geronimo-jta_1.0.1B_spec:jar:1.0.1:compile
|  \- org.apache.commons:commons-pool2:jar:2.4.2:compile
+- org.apache.activemq:activemq-mqtt:jar:5.13.3:compile
+- org.apache.qpid:qpid-jms-client:jar:0.10.0:compile
|  +- org.apache.qpid:proton-j:jar:0.13.0:compile
|  +- io.netty:netty-buffer:jar:4.0.17.Final:compile
|  +- io.netty:netty-common:jar:4.0.17.Final:compile
|  +- io.netty:netty-handler:jar:4.0.17.Final:compile
|  |  \- io.netty:netty-codec:jar:4.0.17.Final:compile
|  \- io.netty:netty-transport:jar:4.0.17.Final:compile
+- io.netty:netty-all:jar:4.0.17.Final:compile
+- org.fusesource.mqtt-client:mqtt-client:jar:1.2:compile
+- org.fusesource.hawtdispatch:hawtdispatch-transport:jar:1.9:compile
|  \- org.fusesource.hawtdispatch:hawtdispatch:jar:1.9:compile
+- org.fusesource.hawtbuf:hawtbuf:jar:1.9:compile
+- junit:junit:jar:4.5:test
+- org.mockito:mockito-all:jar:1.8.5:test
+- org.apache.xbean:xbean-spring:jar:3.7:test
\- com.google.code.findbugs:annotations:jar:2.0.2:compile

I still haven't checked what the counterpart for calling *onSuccess()* or
*onFailure* methods on the affected *ProviderFuture* instance. But I guess
that will be my focus now.

And one more question: is there any possible issue with connecting to the
remote server on the netty side? I've noticed that different versions of the
library suffer from various issues of their own...



--
View this message in context: 
http://qpid.2158936.n2.nabble.com/Cannot-conect-while-using-ActiveMQ-with-Qpid-JMS-client-tp7647859p7647872.html
Sent from the Apache Qpid users mailing list archive at Nabble.com.

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





--
Tim Bish
twitter: @tabish121
blog: http://timbish.blogspot.com/


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

Re: [VOTE] Release Qpid JMS client 0.10.0

[Timothy Bish]

+1

* checked the license and notice files in the archives
* built from source and ran all tests.
* ran the example against an ActiveMQ broker
* ran the ActiveMQ broker tests using the artifacts from the staging repo
* gave the updated docs a once over.

On 06/27/2016 12:33 PM, Robbie Gemmell wrote:

Hi folks,

I have put together a spin for a 0.10.0 Qpid JMS client release, please
test it and vote accordingly.

The source and binary archives can be grabbed from here:
https://dist.apache.org/repos/dist/dev/qpid/jms/0.10.0-rc1/

Those files and the other maven artifacts are also staged for now at:
https://repository.apache.org/content/repositories/orgapacheqpid-1078

Regards,
Robbie


P.S. If you want to test it out using maven (e.g with the examples src,
or your own things), you can temporarily add this to your poms to access
the staging repo:

   
 
   staging
   
https://repository.apache.org/content/repositories/orgapacheqpid-1078
 
   

The dependency for the client itself would then be:

   
 org.apache.qpid
 qpid-jms-client
 0.10.0
   

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





--
Tim Bish
twitter: @tabish121
blog: http://timbish.blogspot.com/


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

Re: [VOTE] Release Qpid Proton 0.13.0

[Timothy Bish]

+1

* Checked the signature and the checksums
* Checked the license and notice files
* Built from source using the cmake build and ran tests
* Built from source for proton-j using the maven build and ran the tests
* Tested Qpid JMS using the 0.13.0 proton-j against ActiveMQ built 
against both 0.12.1 and 0.13.0
* Tested Qpid JMS using the 0.12.1 proton-j against an ActiveMQ broker 
built against 0.13.0

* Ran ActiveMQ unit tests with updated 0.13.0 dependency.

On 06/07/2016 10:31 AM, Justin Ross wrote:

The artifacts proposed for release:

 https://dist.apache.org/repos/dist/dev/qpid/proton/0.13.0-rc/

Please indicate your vote below.  If you favor releasing the 0.13.0 RC bits
as 0.13.0 GA, vote +1.  If you have reason to think the RC is not ready for
release, vote -1.

Thanks,
Justin

---
Proton 0.13.0 release page:
https://cwiki.apache.org/confluence/display/qpid/Qpid+Proton+0.13.0




--
Tim Bish
twitter: @tabish121
blog: http://timbish.blogspot.com/


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

Re: [DISCUSS] removing the 'proton/contrib/proton-hawtdispatch' module

[Timothy Bish]

Agreed, this seems like code that would be better off living in the 
hawtdispatch project if someone really wanted to pick up that torch.


On 04/26/2016 12:37 PM, Robbie Gemmell wrote:

As per the subject, I'd like to suggest removing
'proton/contrib/proton-hawtdispatch' module.

hawtdispatch itself doesn't appear to be seeing any development these
days, with only a handful of commits in the last couple years on
master, none in approaching a year, and the referenced website
appearing to be down. The proton-hawtdispatch module hasn't seen a
meaningful (non-version) commit in a couple years, and is itself using
an old release of hawtdispatch. The statistics repository.apache.org
gives for maven central usage suggest little use, with perhaps average
of 40 downloads a month from 10 IPs.

As the related project appears inactive, nobody is really maintaining
it, and few appear to be using it, I think it should be removed.

Thoughts?

Robbie

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





--
Tim Bish
twitter: @tabish121
blog: http://timbish.blogspot.com/


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

Re: [DISCUSS] removing the 'proton/contrib/proton-jms' module

[Timothy Bish]

On 04/26/2016 10:41 AM, Robbie Gemmell wrote:

As per the subject, I'd like to suggest removing
'proton/contrib/proton-jms' module.

It was written as part of adding AMQP 1.0 support to the ActiveMQ 5.x
broker and then contributed to Proton, and used across ActiveMQ
5.x/Artemis/Apollo. The code was since pulled back into ActiveMQ 5.x
to accommodate changes to better suit its needs and release schedules,
with Artemis now also using that variant, and Apollo is no longer
being worked on these days. As such, I don't know of anything in
particular using it going forward. The statistics
repository.apache.org gives for maven central usage suggest little to
nothing is, with use already dropping significantly some time ago,
probably coinciding with the change in ActiveMQ 5.x.

As nobody is really maintaining it, or appears to be using it, I think
it should be removed.

Thoughts?

Robbie

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


Makes sense to me.  The code in ActiveMQ 5 has already started to evolve 
to better integrate into the ActiveMQ inner workings would guess others 
would do the same for their broker implementations.


--
Tim Bish
twitter: @tabish121
blog: http://timbish.blogspot.com/


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

Re: [VOTE] Migrate Qpid C++ and Qpid Python to Git

[Timothy Bish]

+1

On 04/26/2016 10:40 AM, Justin Ross wrote:

As proposed and discussed at the following links:


http://qpid.2158936.n2.nabble.com/Qpid-source-code-reorg-update-tt7641526.html

http://qpid.2158936.n2.nabble.com/Qpid-Subversion-reorganization-proposal-tt7639094.html
   https://github.com/ssorj/qpid-svn-reorg
   https://issues.apache.org/jira/browse/QPID-7207

If you favor the migration of Qpid C++ and Qpid Python to Git, vote +1.  If
you oppose it, vote -1.




--
Tim Bish
twitter: @tabish121
blog: http://timbish.blogspot.com/


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

Re: [VOTE] move the website bits to a Git repo

[Timothy Bish]

+1

On 04/19/2016 08:03 PM, Robbie Gemmell wrote:

Hi folks,

Short version:
As per the title, I'd like to vote on moving the website bits to a Git
repo, specifically "qpid-site".

Further info:
The site is one of the single largest groups of stuff we have, both
with regard to its previous release content and for the additions of
various new releases as they occur. That's in terms of both overall
file size and especially the overall number of files. On the latter
point, this makes using Subversion particularly slow; for example it
took well over 30mins just to check in the website updates I made
yesterday. I literally had to leave and come back later because it
took so long.

Support for Git based sites have been offered by infra for some time
now [1]. Things work in essentially the same manner to our current
Subversion based site, whereby upon checkin the 'content' bits then
get published to the web servers. The only real difference is that the
site stuff must exist in the 'asf-site' branch of a particular git
repo, either the same one as general code or just a dedicated separate
repo. In our case a dedicated repo seems to makes the most sense, and
again it seems to be what various other projects do (even the
otherwise single-repo projects).

[1] https://blogs.apache.org/infra/entry/git_based_websites_available

Robbie

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

.




--
Tim Bish
twitter: @tabish121
blog: http://timbish.blogspot.com/


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

Re: [VOTE] Release Qpid Proton 0.12.2

[Timothy Bish]

On 04/14/2016 01:28 PM, Robbie Gemmell wrote:

Hi all,

I have put up an RC for 0.12.2, please test it and vote accordingly.

The source release archive and sig/checksums can be grabbed from:
https://dist.apache.org/repos/dist/dev/qpid/proton/0.12.2-rc1/

Maven artifacts for the Java bits can be found in a temporary staging repo at:
https://repository.apache.org/content/repositories/orgapacheqpid-1072

Other than version updates, there is only 1 changes since 0.12.1:
https://issues.apache.org/jira/browse/PROTON-1171

It was created from commit a9c41ef19664af2f928324024dab345c5958f85a
on the 0.12.x branch, and is tagged as 0.12.2-rc1.

Regards,
Robbie

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

.


+1

* Checked signatures and checksums
* Built using cmake and ran tests
* Built using maven and ran tests
* Built Qpid JMS using the staged bits and ran the tests
* Built ActiveMQ 5 using the staged bits and ran the AMQP tests.

--
Tim Bish
twitter: @tabish121
blog: http://timbish.blogspot.com/


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

Re: [VOTE] Release Qpid JMS client 0.9.0

[Timothy Bish]

+1

* Checked the signatures and sums
* Built the src and ran all tests
* Ran the example against an ActiveMQ 5 broker
* Ran the AMQP test suite in ActiveMQ 5 using the staged artifact
* Checked the LICENSE and NOTICE files
* Reviewed the Documentation file


On 04/07/2016 01:04 PM, Robbie Gemmell wrote:

Hi folks,

I have put together a spin for a 0.9.0 Qpid JMS client release, please
test it and vote accordingly.

The source and binary archives can be grabbed from here:
https://dist.apache.org/repos/dist/dev/qpid/jms/0.9.0-rc1/

Those files and the other maven artifacts are also staged for now at:
https://repository.apache.org/content/repositories/orgapacheqpid-1069

Regards,
Robbie


P.S. If you want to test it out using maven (e.g with the examples src,
or your own things), you can temporarily add this to your poms to access
the staging repo:

   
 
   staging
   
https://repository.apache.org/content/repositories/orgapacheqpid-1069
 
   

The dependency for the client itself would then be:

   
 org.apache.qpid
 qpid-jms-client
 0.9.0
   

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





--
Tim Bish
twitter: @tabish121
blog: http://timbish.blogspot.com/


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

Re: Anyone have an example of using message setProperty()?

[Timothy Bish]

On 04/07/2016 04:55 PM, Flores, Paul A. wrote:

At client site.

Need a clear example of the usage of setProperty()


Can you provide a bit more context on what code you are referring to and 
what you want to accomplish?



Thanks for your help it is appreciated!

Paul



This communication (including any attachments) may contain information that is 
proprietary, confidential or exempt from disclosure. If you are not the 
intended recipient, please note that further dissemination, distribution, use 
or copying of this communication is strictly prohibited. Anyone who received 
this message in error should notify the sender immediately by telephone or by 
return email and delete it from his or her computer.

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





--
Tim Bish
twitter: @tabish121
blog: http://timbish.blogspot.com/


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

Re: Questions about disabling sending of UserID with messages QPID-7159/QPIDJMS-163

[Timothy Bish]

On 03/30/2016 07:12 AM, Robbie Gemmell wrote:

On 30 March 2016 at 11:40, Oleksandr Rudyy  wrote:

Hi Robbie,

I would like to clarify the name of a connection parameter to disable
sending of UserID for both new and legacy JMS clients.
New JIRA QPIDJMS-163 requires to implement toggle to enable/disable it
but does not specify how toggle is implemented.

It would be a connection URI option, the new client does essentially
all its configuration that way at present:
http://qpid.apache.org/releases/qpid-jms-0.8.0/docs/index.html#connection-uri


In suggested changes for legacy JMS client implemented as part of
QPID-7159 connection parameter 'attachUserId' is used to disable
sending of UserID.
I am wondering whether the same name could be used in both old and new clients?


The name could be the same, but as per the above link the new client
prefixes properties into groups so unless the old client included the
same the two would still differ slightly.


I've implemented this feature in the Qpid JMS client code but I've gone 
with a different name which I hope is a bit more clear on what is 
happening when it is enabled.  The configuration for the client would be 
done on the URI using the following type of URI


   amqp://localhost:5672?jms.populateJMSXUserID=true




Another interesting question is whether enumeration returned by
ConnectionMetaData#getJMSXPropertyNames() should include JMSXUserID
when its sending is disabled?
It seems that connection will not support JMSXUserID in sent messages
but will support it in received messages.
JMS spec is very unclear about it.

Yes it is. It does describe that the existence of such 'JMS-defined'
properties for a particular message isnt a given, as providers may
choose to include them on some messages and not others based on the
ever-present 'administrative or other criteria' escape clause the spec
loves to use. As such I don't think having the name in the metadata
while not setting the value on send is actually against the spec,
though it certainly might not be what some people expect.


It looks like that JMSXUserID shall be included into
ConnectionMetaData#getJMSXPropertyNames() when sending of UserID is
disabled.
Any thoughts?

I think I'd tend towards removing it from the metadata if not setting
the value on send, but alternatively this all might even suggest a
second config option to control whether the metadata is exposed or
not, separate from whether outgoing messages actually have it
populated or not.I'd probably try to avoid that for now though.

Its probably worth me putting out there at this point that I actually
think including the value on sent messages should be disabled by
default. I tend to think of it as an optional opt-in, as the JMS spec
itself seems to, and not always particularly desirable. Obviously the
old client has been including it for some time, so I wouldnt change
that to avoid breaking existing stuff, but when implementing this on
the new client I'd tend toward changing the default behaviour (or
rather, also leaving it as it has effectively been all along for the
new client)


I've implemented this in an off by default manner as in most cases in 
the past I've seen more users request not to include this information 
than want it included.  I have not removed the advertisement of 
JMSXUserID from the metadata though as this value is used not only to 
indicate that the sender can apply it but also that the receive can ask 
for it and get a meaningful answer back if the remote happens to support 
populating it.  If it becomes an issue I'd suggest we would provide an 
additional configuration option to control what values are exposed in 
the metadata.



Robbie

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





--
Tim Bish
twitter: @tabish121
blog: http://timbish.blogspot.com/


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

Re: [VOTE] merge the proton mailing list into the users/dev lists

[Timothy Bish]

+1

On 03/30/2016 06:25 AM, Robbie Gemmell wrote:

Hello folks,

Many moons ago, a seperate mailing list was established for Proton,
back when it was purely a protocol engine other components would use.
Its scope has since expanded beyond that and the separate mailing list
has I feel been an increasing source of confusion and hassle of late
more than anything else. Collapsing it into the other larger existing
lists we have (that the traffic would otherwise have been on) seems to
me like it would be an improvement across the board, and as such I
have called this vote.

I would propose that discussion (such as this) would head to the
users@q.a.o list to join the similar/related/duplicate traffic already
present, with remaining things going to the dev@q.a.o list as
consistent with that list (e.g JIRA, GitHub integration mails,
ReviewBoard, though the latter was never actually directed to proton@
to begin with..).

Whilst redirecting JIRA etc emails should be easy enough (has been
done before), I dont know what the precise options are regarding
existing mail subscriptions to the list. There are significantly more
subscribers to users@ than proton@, and many are duplicates, but some
are not. I'd need to discuss options with infra, but first things
first, the vote.

I have gone straight to a vote on this because I feel this has already
been discussed enough previously over time that many people will have
already thought about it enough to quickly vote one way or the other,
and it is past time to act on it if things head that way. Obviously
things can be further discusssed at this point also if desired.

Note that both users@ and proton@ are in the recipients. I expect the
thread will splinter when someone forgets to reply-all, as almost all
cross-posted thread on the lists do, but at least it can start on both
for visibility to all.

Robbie
.




--
Tim Bish
twitter: @tabish121
blog: http://timbish.blogspot.com/


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

Re: AMQP 1.0 Qpid JMS and an Issue with Failover/Reconnect

[Timothy Bish]

On 03/23/2016 08:56 AM, Aleks Balaban wrote:

Tim,

Thx, good to know that the failover works! Obviously I've been doing 
something wrong. Well, as you requested here is my JMS/AMQP client 
source (I have removed the SSL initialization part used for amqps 
conncetion ):





Your code relies on there being at least one non-daemon thread in 
existence at all time to prevent the main app from shutting down which 
will not always be the case as the code is currently written. Because of 
this your shutdown hook is being triggered and the shutdown of the 
connection and its underlying resources is occurring leading to the logs 
that you are seeing.



Connection URI:
connectionfactory.nm = 
failover:(amqps://somedomain.com:5671)?failover.reconnectDelay=2000&failover.warnAfterReconnectAttempts=1



Source code:

public class TestClient implements Runnable {

private static final Logger logger = 
Logger.getLogger(TestClient.class.getName());

private static Connection connection;

public static void main(String[] args) {

org.apache.log4j.PropertyConfigurator.configure("./log4j.properties");

initSSL();

new Thread(new TestClient()).start();

Runtime.getRuntime().addShutdownHook(new Thread(() -> {

logger.info("Shutting down...");

try {
if (connection != null) {
connection.close();
}
} catch (JMSException e) {
logger.warning(e.getMessage());
}
}));
}

@Override
public void run() {

try {
Properties properties = new Properties();

if (System.getProperty("nmclient.configuration") == null) {
File jarPath = new 
File(TestClient.class.getProtectionDomain().getCodeSource().getLocation().getPath());

String propertiesPath = jarPath.getParent();
properties.load(new FileInputStream(propertiesPath + 
"/config.properties"));

} else {
properties.load(new 
FileInputStream(System.getProperty("nmclient.configuration")));

}

Context context = new InitialContext(properties);
ConnectionFactory connectionFactory = (ConnectionFactory) 
context.lookup("nm");


connection = connectionFactory.createConnection();

connection.setExceptionListener((final JMSException e) -> {
logger.log(Level.SEVERE, null, e);
});

Session consumerSession = connection.createSession(false, 
Session.CLIENT_ACKNOWLEDGE);

Queue queueEaup = (Queue) context.lookup("eaup");
MessageConsumer messageConsumer = 
consumerSession.createConsumer(queueEaup);


messageConsumer.setMessageListener((final Message message) 
-> {

try {
if (message instanceof TextMessage) {

TextMessage payload = (TextMessage) message;
logger.info(payload.getText());
}
message.acknowledge();
} catch (Exception e) {
logger.log(Level.SEVERE, null, e);
}
});

connection.start();

} catch (IOException | NamingException | JMSException e) {
logger.log(Level.SEVERE, null, e);
}
}

private static void initSSL() {
  // 
}
}

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





--
Tim Bish
twitter: @tabish121
blog: http://timbish.blogspot.com/


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

Re: AMQP 1.0 Qpid JMS and an Issue with Failover/Reconnect

[Timothy Bish]

On 03/22/2016 12:51 PM, Aleks Balaban wrote:
Thank you for writing back. My client quite minimalistic JMS client 
application with usual JMS stuff such as Connection, Session objects 
and "onMessage" listeners, which does nothing but connect to an AMQP 
server and waits to receive notifications/messages. It works just 
fine, only it isn't capable to re-establish the underlying SSL 
connection when something went wrong and that happens almost every 
day. I'm running it in a debug mode and the log I posted earlier is 
all I have. Obviously, the connection failure has been detected 
properly (for testing purposes I caused it by shooting down the 
internet connection) and the FailoverProvider makes two attempts to 
re-establish the connection. Both of them fails because the internet 
is off and suddenly some thread executor takes over and terminates 
everything. I'm just wondering is there any example in the web or 
anybody was trying to achieve the same. The documentation seems to be 
insufficient to find out what was wrong. What I've been thinking 
about, do I need to take care about configuration attributes at 
different communication levels? For example, do I have to take care 
manually that TCP, AMQP and JMS configuration parameters harmonize 
with each other?


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


I wrote a small test using your provided failover options and my test 
sits for as long as I let it trying to reconnect.  I would take a look 
at your code and see where you might be closing the connection as there 
should be no issue with these options.


--
Tim Bish
twitter: @tabish121
blog: http://timbish.blogspot.com/


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

Re: AMQP 1.0 Qpid JMS and an Issue with Failover/Reconnect

[Timothy Bish]

I'd recommend that you post some code to show what your client is 
doing.  The logs really don't provide enough information to diagnose 
what might be going on.


On 03/22/2016 11:07 AM, Aleks Balaban wrote:

Hi,

Im using Qpid JMS 0.8.0 library in order to implement a standalone 
Java AMQP client. Because the underlying transport connection tends to 
break every couple of hours I was trying to configure the reconnection 
attempts (like failover but to the same server) using following 
configuration:


failover:(amqps://someurl:5671)?failover.reconnectDelay=2000&failover.warnAfterReconnectAttempts=1 



In accordance with Qpid failover configuration explanation I expect my 
client to keep trying to reconnect increasing the attempt delays for 
factor 2 (starting with 2 seconds). Instead, according to the log 
file, only two attempts to reconnect have been performed when a 
connection failure was detected and at the end the whole client 
application has been terminated, what I definitively would like to 
avoid! Here is the log file:


2016-03-22 14:29:40 INFO AmqpProvider:1190 - IdleTimeoutCheck closed 
the transport due to the peer exceeding our requested idle-timeout. 
2016-03-22 14:29:40 DEBUG FailoverProvider:761 - Failover: the 
provider reports failure: Transport closed due to the peer exceeding 
our requested idle-timeout 2016-03-22 14:29:40 DEBUG 
FailoverProvider:519 - handling Provider failure: Transport closed due 
to the peer exceeding our requested idle-timeout 2016-03-22 14:29:40 
DEBUG FailoverProvider:653 - Connection attempt:[1] to: 
amqps://publish.preops.nm.eurocontrol.int:5671 in-progress 2016-03-22 
14:29:40 INFO FailoverProvider:659 - Connection attempt:[1] to: 
amqps://publish.preops.nm.eurocontrol.int:5671 failed 2016-03-22 
14:29:40 WARN FailoverProvider:686 - Failed to connect after: 1 
attempt(s) continuing to retry. 2016-03-22 14:29:42 DEBUG 
FailoverProvider:653 - Connection attempt:[2] to: 
amqps://publish.preops.nm.eurocontrol.int:5671 in-progress 2016-03-22 
14:29:42 INFO FailoverProvider:659 - Connection attempt:[2] to: 
amqps://publish.preops.nm.eurocontrol.int:5671 failed 2016-03-22 
14:29:42 WARN FailoverProvider:686 - Failed to connect after: 2 
attempt(s) continuing to retry. 2016-03-22 14:29:43 DEBUG 
ThreadPoolUtils:156 - Shutdown of ExecutorService: 
java.util.concurrent.ThreadPoolExecutor@778970af[Terminated, pool size 
= 0, active threads = 0, queued tasks = 0, completed tasks = 0] is 
shutdown: true and terminated: true took: 0.000 seconds. 2016-03-22 
14:29:45 DEBUG ThreadPoolUtils:192 - Waited 2.004 seconds for 
ExecutorService: 
java.util.concurrent.ScheduledThreadPoolExecutor@877a470[Shutting 
down, pool size = 1, active threads = 0, queued tasks = 1, completed 
tasks = 3] to terminate... 2016-03-22 14:29:46 DEBUG 
ThreadPoolUtils:156 - Shutdown of ExecutorService: 
java.util.concurrent.ScheduledThreadPoolExecutor@877a470[Terminated, 
pool size = 0, active threads = 0, queued tasks = 0, completed tasks = 
4] is shutdown: true and terminated: true took: 2.889 seconds.


Any idea, what I’m doing wrong here? Basically, what I'm looking for 
to achieve is a client which is capable to detect transport connection 
failure and try to reconnect every 5-10 seconds.


Many thanks!





--
Tim Bish
twitter: @tabish121
blog: http://timbish.blogspot.com/


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

Re: JMS client - send timeout

[Timothy Bish]

No, there is not currently a configurable send timeout implemented on 
the client.  I've opened QPIDJMS-157 to track the feature request.  You 
can configure the failover bits to give up after some number of attempts 
currently which would cause the sends to break.


On 03/16/2016 06:02 AM, Julien Charon wrote:

   Hi,


I'm currently doing some testing on a client that uses the JMS client 
internally to send messages to an AMQP queue.
Now I wanted to test what happens when the broker is not reachable and I try to 
send a message. I configured the connection with failover(...) so that the 
connection will be re-established automatically when the broker becomes 
available again, which works as expected.
But when the broker is down, the javax.jms.MessageProducer.send(Message) method 
does not return until the connection is re-established. I also tried to use 
javax.jms.MessageProducer.send(Message, int, int, long) and set a message 
lifetime, but the behaviour is the same.
Is there a way to configure a timeout for sending messages? Unfortunately, I 
didn't find anything in 
https://qpid.apache.org/releases/qpid-jms-0.8.0/docs/index.html


Best regards,
Julien

Avitech GmbH
Engineering AxL
Tel.: +49 (0)7541/282-177
Fax: +49 (0)7541/282-199
e-mail: julien.cha...@avitech.aero

Avitech GmbH
Principal Office: Bahnhofplatz 1 | 88045 Friedrichshafen | Germany
Court Registration: Amtsgericht Ulm | HRB 728293
Geschäftsführer/Managing Director: Jon Joseba Goyarzu Caño
http://avitech.aero

This message may contain confidential information and is intended only for the 
individual named. If you are not the named addressee you should not 
disseminate, distribute or copy this e-mail. Please notify the sender 
immediately by e-mail if you have received this e-mail by mistake and delete 
this e-mail from your system.





--
Tim Bish
twitter: @tabish121
blog: http://timbish.blogspot.com/


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

Re: Unhandled exception when using High Availabilty in Qpid Java Broker 6.0.0

[Timothy Bish]

On 03/10/2016 06:12 PM, Rob Godfrey wrote:

On 10 March 2016 at 23:44, Adel Boutros  wrote:


If I compile while skipping tests and deploy the jar then the broker no
longer crashes.
Nevertheless, the client doesn't try the 2nd URL, instead it fails with the
below stack. If I put back the MASTER URL before the Replicate URL, then
everything works fine.

It seems to me that the order in which the URLs are provided in the
failover shouldn't matter. Am I correct?


I'm not too familiar with the new AMQP 1.0 JMS client and how it handles
failure and failover...  Robbie and Tim can hopefully step in here and say
why it is not trying the second URL in the connection string you are
providing.  Ultimately in the broker we'll be implementing a redirect which
will tell the client where it should try to reconnect to (i.e. the
host/port of the current master) however currently it just responds that
the host name (virtual host) is not found at the location.  I don't know
whether the JMS client handles the redirect either to be fair.

-- Rob

I recall writing code and a test for redirect so I think it should in 
theory work if one is provided, but I don't have the code in front of me.






javax.jms.InvalidDestinationException: Received error from remote peer
without description [condition = amqp:not-found]
at

org.apache.qpid.jms.provider.amqp.AmqpSupport.convertToException(AmqpSupport.java:109)
at

org.apache.qpid.jms.provider.amqp.AmqpAbstractResource.remotelyClosed(AmqpAbstractResource.java:115)
at

org.apache.qpid.jms.provider.amqp.AmqpAbstractResource.processRemoteClose(AmqpAbstractResource.java:210)
at

org.apache.qpid.jms.provider.amqp.AmqpProvider.processUpdates(AmqpProvider.java:772)
at

org.apache.qpid.jms.provider.amqp.AmqpProvider.access$1900(AmqpProvider.java:92)
at

org.apache.qpid.jms.provider.amqp.AmqpProvider$17.run(AmqpProvider.java:701)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at

java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178)
at

java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292)
at

java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at

java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:744)

Regards,
Adel

On Thu, Mar 10, 2016 at 11:36 PM, Adel Boutros 
wrote:


Hello Rob,

I have 3 tests failing under *ProtocolEngine_1_0_0Test* when compiling

*broker-plugins

6.0.2-SNAPSHOT *in Intellij or maven

- ProtocolEngine_1_0_0Test.testProtocolEngineWithNoSaslNonTLSandAnon
- ProtocolEngine_1_0_0Test.testProtocolEngineWithNoSaslTLSandExternal
- ProtocolEngine_1_0_0Test.testProtocolEngineWithSaslNonTLSandAnon


All 3 tests are failing with the same issue:

Wanted but not invoked:
virtualHostImpl.registerConnection();
-> at


org.apache.qpid.server.protocol.v1_0.ProtocolEngine_1_0_0Test.testProtocolEngineWithNoSaslNonTLSandAnon(ProtocolEngine_1_0_0Test.java:176)

However, there were other interactions with this mock:
-> at


org.apache.qpid.server.protocol.v1_0.Connection_1_0.openReceived(Connection_1_0.java:182)

-> at


org.apache.qpid.server.protocol.v1_0.Connection_1_0.openReceived(Connection_1_0.java:191)

Wanted but not invoked:
virtualHostImpl.registerConnection();
-> at


org.apache.qpid.server.protocol.v1_0.ProtocolEngine_1_0_0Test.testProtocolEngineWithNoSaslNonTLSandAnon(ProtocolEngine_1_0_0Test.java:176)

However, there were other interactions with this mock:
-> at


org.apache.qpid.server.protocol.v1_0.Connection_1_0.openReceived(Connection_1_0.java:182)

-> at


org.apache.qpid.server.protocol.v1_0.Connection_1_0.openReceived(Connection_1_0.java:191)

Can you please advise?

Regards,
Adel Boutros

On Thu, Mar 10, 2016 at 9:20 PM, Rob Godfrey 
wrote:


Apologies for this - you have indeed run into bug :-(

I've raised a JIRA - https://issues.apache.org/jira/browse/QPID-7136 .

I've committed a fix both to trunk, and the 6.0.x branch which I hope

will

fix this issue...  If you want to test it out you can use the 6.0.x

branch

which can be found here:

https://svn.apache.org/repos/asf/qpid/java/branches/6.0.x


Hope this helps,
-- Rob

On 10 March 2016 at 20:10, Adel Boutros  wrote:


Hello,

When we provide a failover URL where the first URL is that of a

replicate

broker, the connection will trigger an IllegalStateException which is

not

caught anywhere. Thus making the broker crash and the session creation

fail

on the client-side.

Shouldn't the "close" method log the exception silently instead of

crashing

the broker?

*Code*

String brokerUrl =
"failover:(amqp://localhost:5672,amqp://localhost:10352)";
ConnectionFactory connectionFactory = new

JmsConnectionFactory(brokerUrl);

Connection connection = connectionFactory.createConnection();
Session session = c

Re: Unhandled exception when using High Availabilty in Qpid Java Broker 6.0.0

[Timothy Bish]

On 03/10/2016 05:44 PM, Adel Boutros wrote:

If I compile while skipping tests and deploy the jar then the broker no
longer crashes.
Nevertheless, the client doesn't try the 2nd URL, instead it fails with the
below stack. If I put back the MASTER URL before the Replicate URL, then
everything works fine.

It seems to me that the order in which the URLs are provided in the
failover shouldn't matter. Am I correct?
What is happening at the time this error is received?  The 
InvalidDestinationException error is treated differently as I recal 
because it indicates you have done something invalid not that the client 
has lost it's connection to the broker.  Since an invalid destination 
error is something that can be recovered from the client wouldn't try 
and reconnect because of it.  Now if you are losing your connection 
following this then I'd expect a failover but I don't see enough info 
here to infer that the connection dropped say I can't say.





javax.jms.InvalidDestinationException: Received error from remote peer
without description [condition = amqp:not-found]
at
org.apache.qpid.jms.provider.amqp.AmqpSupport.convertToException(AmqpSupport.java:109)
at
org.apache.qpid.jms.provider.amqp.AmqpAbstractResource.remotelyClosed(AmqpAbstractResource.java:115)
at
org.apache.qpid.jms.provider.amqp.AmqpAbstractResource.processRemoteClose(AmqpAbstractResource.java:210)
at
org.apache.qpid.jms.provider.amqp.AmqpProvider.processUpdates(AmqpProvider.java:772)
at
org.apache.qpid.jms.provider.amqp.AmqpProvider.access$1900(AmqpProvider.java:92)
at
org.apache.qpid.jms.provider.amqp.AmqpProvider$17.run(AmqpProvider.java:701)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:744)

Regards,
Adel

On Thu, Mar 10, 2016 at 11:36 PM, Adel Boutros  wrote:


Hello Rob,

I have 3 tests failing under *ProtocolEngine_1_0_0Test* when compiling 
*broker-plugins
6.0.2-SNAPSHOT *in Intellij or maven

- ProtocolEngine_1_0_0Test.testProtocolEngineWithNoSaslNonTLSandAnon
- ProtocolEngine_1_0_0Test.testProtocolEngineWithNoSaslTLSandExternal
- ProtocolEngine_1_0_0Test.testProtocolEngineWithSaslNonTLSandAnon


All 3 tests are failing with the same issue:

Wanted but not invoked:
virtualHostImpl.registerConnection();
-> at
org.apache.qpid.server.protocol.v1_0.ProtocolEngine_1_0_0Test.testProtocolEngineWithNoSaslNonTLSandAnon(ProtocolEngine_1_0_0Test.java:176)

However, there were other interactions with this mock:
-> at
org.apache.qpid.server.protocol.v1_0.Connection_1_0.openReceived(Connection_1_0.java:182)
-> at
org.apache.qpid.server.protocol.v1_0.Connection_1_0.openReceived(Connection_1_0.java:191)

Wanted but not invoked:
virtualHostImpl.registerConnection();
-> at
org.apache.qpid.server.protocol.v1_0.ProtocolEngine_1_0_0Test.testProtocolEngineWithNoSaslNonTLSandAnon(ProtocolEngine_1_0_0Test.java:176)

However, there were other interactions with this mock:
-> at
org.apache.qpid.server.protocol.v1_0.Connection_1_0.openReceived(Connection_1_0.java:182)
-> at
org.apache.qpid.server.protocol.v1_0.Connection_1_0.openReceived(Connection_1_0.java:191)

Can you please advise?

Regards,
Adel Boutros

On Thu, Mar 10, 2016 at 9:20 PM, Rob Godfrey 
wrote:


Apologies for this - you have indeed run into bug :-(

I've raised a JIRA - https://issues.apache.org/jira/browse/QPID-7136 .

I've committed a fix both to trunk, and the 6.0.x branch which I hope will
fix this issue...  If you want to test it out you can use the 6.0.x branch
which can be found here:

https://svn.apache.org/repos/asf/qpid/java/branches/6.0.x


Hope this helps,
-- Rob

On 10 March 2016 at 20:10, Adel Boutros  wrote:


Hello,

When we provide a failover URL where the first URL is that of a

replicate

broker, the connection will trigger an IllegalStateException which is

not

caught anywhere. Thus making the broker crash and the session creation

fail

on the client-side.

Shouldn't the "close" method log the exception silently instead of

crashing

the broker?

*Code*

String brokerUrl =
"failover:(amqp://localhost:5672,amqp://localhost:10352)";
ConnectionFactory connectionFactory = new

JmsConnectionFactory(brokerUrl);

Connection connection = connectionFactory.createConnection();
Session session = connection.createSession(false,
Session.AUTO_ACKNOWLEDGE);

*Test case*
Assuming that the broker on *localhost:5672 *is alive but as a

*REPLICATE*

and the one on* localhost:10352* as the *MASTER*

*Stack trace*
java.lang.IllegalStateException: The virtual hos

Re: Welcome Ganesh Murthy as an Apache Qpid committer

[Timothy Bish]

Nice job Ganesh! Welcome!


On 03/01/2016 12:30 PM, Robbie Gemmell wrote:

The Qpid PMC have voted to grant commit rights to Ganesh Murthy in
recognition of his contributions to the project.

Welcome, Ganesh!


Robbie

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




--
Tim Bish
twitter: @tabish121
blog: http://timbish.blogspot.com/


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

Re: [VOTE] Release Qpid JMS client 0.8.0

[Timothy Bish]

+1

* Checked signatures and checksums
* Built the source bundle and ran the tests
* Ran the included example against an ActiveMQ broker
* Tested the ActiveMQ broker AMQP module using the staged artifacts
* Reviewed the license and notice files in both the src and bin archives

On 02/16/2016 12:15 PM, Robbie Gemmell wrote:
> Hi folks,
>
> I have put together a spin for a 0.8.0 Qpid JMS client release, please
> test it and vote accordingly.
>
> The source and binary archives can be grabbed from here:
> https://dist.apache.org/repos/dist/dev/qpid/jms/0.8.0-rc1/
>
> Those files and the other maven artifacts are also staged for now at:
> https://repository.apache.org/content/repositories/orgapacheqpid-1064
>
> Regards,
> Robbie
>
>
> P.S. If you want to test it out using maven (e.g with the examples src,
> or your own things), you can temporarily add this to your poms to access
> the staging repo:
>
>   
> 
>   staging
>   
> https://repository.apache.org/content/repositories/orgapacheqpid-1064
> 
>   
>
> The dependency for the client itself would then be:
>
>   
> org.apache.qpid
> qpid-jms-client
> 0.8.0
>   
>
> -
> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
> For additional commands, e-mail: users-h...@qpid.apache.org
>
>


-- 
Tim Bish
twitter: @tabish121
blog: http://timbish.blogspot.com/


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

Re: AMQP Essentials refcard on resources page

[Timothy Bish]

On 01/18/2016 02:51 AM, Paolo Patierno wrote:
> Hi all,
> today my "AMQP Essentials" refcard was published on DZone web site :
> https://dzone.com/refcardz/amqp-essentials
> I was wondering if it could be useful to add its link inside the resources 
> page (https://qpid.apache.org/resources.html) of the Apache Qpid web site.
> Thanks,Paolo.
>
> Paolo PatiernoSenior Software Engineer
>  
>
> Windows Embedded & IoTMicrosoft Azure Advisor 
> Twitter : @ppatierno
> Linkedin : paolopatierno
> Blog : DevExperienceBlog : Embedded101
> 
Just read through some of the article, very nice work.  Did notice an
error in the section on the platforms and clients which states that
JBoss A-MQ is based on Apache Qpid, however it is actually based on
Apache ActiveMQ. 

-- 
Tim Bish
twitter: @tabish121
blog: http://timbish.blogspot.com/


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

Re: [VOTE] Release Qpid JMS client 0.7.0

[Timothy Bish]

+1

Checked the signatures and checksums
Checked that license and notice files were included.
Built the source archive and ran tests.
Used the staged artifacts to run the ActiveMQ AMQP JMS tests.
Ran the examples from the source build against ActiveMQ

On 12/18/2015 11:55 AM, Robbie Gemmell wrote:
> Hi folks,
>
> I have put together a first spin for a 0.7.0 Qpid JMS client release,
> please test it and vote accordingly.
>
> The source and binary archives can be grabbed from here:
> https://dist.apache.org/repos/dist/dev/qpid/jms/0.7.0-rc1/
>
> Those files and the other maven artifacts are also staged for now at:
> https://repository.apache.org/content/repositories/orgapacheqpid-1058
>
> Regards,
> Robbie
>
>
> P.S. If you want to test it out using maven (e.g with the examples src,
> or your own things), you can temporarily add this to your poms to access
> the staging repo:
>
>   
> 
>   staging
>   
> https://repository.apache.org/content/repositories/orgapacheqpid-1058
> 
>   
>
> The dependency for the client itself would then be:
>
>   
> org.apache.qpid
> qpid-jms-client
> 0.7.0
>   
>
> -
> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
> For additional commands, e-mail: users-h...@qpid.apache.org
>
>


-- 
Tim Bish
twitter: @tabish121
blog: http://timbish.blogspot.com/


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

Re: Qpid JMS client able to send but not receive

[Timothy Bish]

You need to call connection.start() in order to begin processing of
incoming messages when dealing with JMS connections.

On 12/17/2015 06:43 PM, Mark Soderquist wrote:
> I have implemented a simple client with the qpid-jms-client 0.6.0 client 
> against Qpid 6.0.0 Java Broker. I have successfully been able to send 
> messages but I am unable to consume messages. Everything works without error 
> and I know that I am connecting because I see the consumer create events on 
> the server, however, no messages arrive. I used the qpid-amqp-1-0-client-jms 
> 0.32 client and was able to receive messages so at this point I believe it is 
> either user error or a bug in qpid-jms-client. Here is my code to retrieve a 
> message in the event I'm missing something obvious.
>
> Connection connection = null;
> Session session = null;
> MessageConsumer consumer = null;
> EmxMessage emxMessage = null;
>
> String uri = "amqps://" + host + ":" + port + "?jms.username=" + 
> username + "&jms.password=" + password + "&amqp.vhost=default";
> ConnectionFactory factory = new JmsConnectionFactory( uri );
>
> try {
>   connection = factory.createConnection();
>   session = connection.createSession( false, 
> Session.AUTO_ACKNOWLEDGE );
>   consumer = session.createConsumer( new JmsQueue( queue ) );
>
>   Message message = consumer.receive( 2000 );
> }
> catch( Exception exception ) {
>   logger.error( "Error receiving message.", exception );
> }
>
> This is the client output:
>
> [AmqpProvider:(1):[amqps://emx-test.ldschurch.org:5671]] INFO 
> org.apache.qpid.jms.sasl.SaslMechanismFinder - Best match for SASL auth was: 
> SASL-PLAIN
> [AmqpProvider:(1):[amqps://emx-test.ldschurch.org:5671]] INFO 
> org.apache.qpid.jms.JmsConnection - Connection 
> ID:sandstone-53917-1450393363128-0:1 connected to remote Broker: 
> amqps://emx-test.ldschurch.org:5671
>
> Any ideas?
>
> ---
> Mark Soderquist
> Engineering Manager | Enterprise Integration
> The Church of Jesus Christ of Latter-Day Saints
> mark.soderqu...@ldschurch.org
> 801-240-9288
>
>


-- 
Tim Bish
twitter: @tabish121
blog: http://timbish.blogspot.com/


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

Re: [VOTE] Release Qpid Proton 0.11.1

[Timothy Bish]

On 12/15/2015 02:32 PM, Robbie Gemmell wrote:
> Hi all,
>
> I have put up an RC for 0.11.1, please test it and vote accordingly.
>
> The release archive and sig/checksums can be grabbed from:
> https://dist.apache.org/repos/dist/dev/qpid/proton/0.11.1-rc1/
>
> Maven artifacts for the Java bits can be found in a temporary staging repo at:
> https://repository.apache.org/content/repositories/orgapacheqpid-1057
>
> Other than version updates, there are only two changes since 0.11.0:
> https://issues.apache.org/jira/browse/PROTON-1059
> https://issues.apache.org/jira/browse/PROTON-1077
>
> It was created using commit 99ee72b897395b0abb72df001709095b498edbc5
> on the 0.11.x branch, and is tagged as 0.11.1-rc1.
>
> Regards,
> Robbie
>
> -
> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
> For additional commands, e-mail: users-h...@qpid.apache.org
>
>
+1

Tested with ActiveMQ5 AMQP tests
Tested with Qpid JMS test suite
Built from source and ran tests
Checked signatures and checksums

-- 
Tim Bish
Sr Software Engineer | RedHat Inc.
tim.b...@redhat.com | www.redhat.com 
twitter: @tabish121
blog: http://timbish.blogspot.com/


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

Re: [VOTE] Release Qpid JMS client 0.6.0

[Timothy Bish]

+1

* Validated signature and checksums
* Check license and notices in src and bin archives
* Built from source and ran all tests
* Ran examples against ActiveMQ broker
* Ran ActiveMQ internal AMQP tests using the deployed artifacts.

On 10/08/2015 02:09 PM, Robbie Gemmell wrote:
> Hi folks,
>
> I have put together a first spin for a 0.6.0 Qpid JMS client release,
> please test it and vote accordingly.
>
> The source and binary archives can be grabbed from here:
> https://dist.apache.org/repos/dist/dev/qpid/jms/0.6.0-rc1/
>
> Those files and the other maven artifacts are also staged for now at:
> https://repository.apache.org/content/repositories/orgapacheqpid-1046
>
> Regards,
> Robbie
>
>
> P.S. If you want to test it out using maven (e.g with the examples src,
> or your own things), you can temporarily add this to your poms to access
> the staging repo:
>
>   
> 
>   staging
>   
> https://repository.apache.org/content/repositories/orgapacheqpid-1046
> 
>   
>
> The dependency for the client itself would then be:
>
>   
> org.apache.qpid
> qpid-jms-client
> 0.6.0
>   
>
> -
> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
> For additional commands, e-mail: users-h...@qpid.apache.org
>
>


-- 
Tim Bish
Sr Software Engineer | RedHat Inc.
tim.b...@redhat.com | www.redhat.com 
twitter: @tabish121
blog: http://timbish.blogspot.com/


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

Re: [VOTE] Release Qpid JMS client 0.4.0

[Timothy Bish]

On 08/14/2015 08:47 AM, Robbie Gemmell wrote:
> Hi all,
>
> Its time for the 0.4.0 Qpid JMS client release, now that Proton 0.10
> is available. I have put together a first spin, please test it and
> vote accordingly.
>
> The source and binary archives can be grabbed from here:
> https://dist.apache.org/repos/dist/dev/qpid/jms/0.4.0-rc1/
>
> Those files and the other maven artifacts are also staged for now at:
> https://repository.apache.org/content/repositories/orgapacheqpid-1043
>
> Regards,
> Robbie
>
>
> P.S. If you want to test it out using maven (e.g with the examples src,
> or your own things), you can temporarily add this to your poms to access
> the staging repo:
>
>   
> 
>   staging
>   
> https://repository.apache.org/content/repositories/orgapacheqpid-1043
> 
>   
>
> The dependency for the client itself would then be:
>
>   
> org.apache.qpid
> qpid-jms-client
> 0.4.0
>   
>
> -
> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
> For additional commands, e-mail: users-h...@qpid.apache.org
>
>
+1

* Verified the signatures and sums.
* Reviewed the LICENSE and NOTICE files
* Built from the source archive and ran the tests.
* Checked for missing license headers.
* Used the repo to validate the release in ActiveMQ and run the tests.

-- 
Tim Bish
Sr Software Engineer | RedHat Inc.
tim.b...@redhat.com | www.redhat.com 
twitter: @tabish121
blog: http://timbish.blogspot.com/


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

Re: [VOTE] Release Qpid Proton 0.10 (RC2)

[Timothy Bish]

On 08/10/2015 02:34 PM, Robbie Gemmell wrote:
> Hi all,
>
> I have put up a second cut for 0.10, please test it and vote accordingly.
>
> This fixes a crash (PROTON-976) reported against the previous spin,
> and adds a known issue (PROTON-975) of possible failure using the
> DIGEST-MD5 mechanism against non-proton servers.
>
> The release archive and sig/checksums can be grabbed from:
> https://dist.apache.org/repos/dist/dev/qpid/proton/0.10-rc2/
>
> Maven artifacts for the Java bits can be found in a temporary staging repo at:
> https://repository.apache.org/content/repositories/orgapacheqpid-1041
>
> Regards,
> Robbie
>
> -
> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
> For additional commands, e-mail: users-h...@qpid.apache.org
>
>
+1

-- 
Tim Bish
Sr Software Engineer | RedHat Inc.
tim.b...@redhat.com | www.redhat.com 
twitter: @tabish121
blog: http://timbish.blogspot.com/


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

Re: [VOTE] Release Qpid JMS client 0.3.0

[Timothy Bish]

+1

Built from source, ran the tests.
Validated the sigs
Checked that the license and notices were present.
Ran the example
Tested ActiveMQ Unit Test suite using this 0.3.0 jars

On 06/11/2015 02:46 PM, Robbie Gemmell wrote:
> Hi all,
>
> We have made a bunch of fixes and improvements since the previous version
> so it is time to make them available via an updated release. I have put
> up an initial RC for folks to test and vote on accordingly.
>
> The source and binary archives can be grabbed from here:
> https://dist.apache.org/repos/dist/dev/qpid/jms/0.3.0-rc1/
>
> Those and the other individual maven artifacts are also staged for now at:
> https://repository.apache.org/content/repositories/orgapacheqpid-1035
>
> Regards,
> Robbie
>
>
> P.S. If you want to test it out using maven (e.g with the examples src,
> or your own things), you can temporarily add this to your poms to access
> the staging repo:
>
>   
> 
>   staging
>   
> https://repository.apache.org/content/repositories/orgapacheqpid-1035
> 
>   
>
>
> The dependency for the client itself would then be:
>
>   
> org.apache.qpid
> qpid-jms-client
> 0.3.0
>   
>
> -
> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
> For additional commands, e-mail: users-h...@qpid.apache.org
>
>


-- 
Tim Bish
Sr Software Engineer | RedHat Inc.
tim.b...@redhat.com | www.redhat.com 
twitter: @tabish121
blog: http://timbish.blogspot.com/



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

Re: Qpid JMS discorvery

[Timothy Bish]

On 06/08/2015 07:21 AM, Erik Aschenbrenner wrote:
> Dear Qpid users,
>
> the Qpid JMS 0.2.0 release contains the library
> "qpid-jms-discovery-0.2.0.jar". What is it good for? 
>
> Regards,
> Erik
>
>
>
> --
> View this message in context: 
> http://qpid.2158936.n2.nabble.com/Qpid-JMS-discorvery-tp7625966.html
> Sent from the Apache Qpid users mailing list archive at Nabble.com.
>
> -
> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
> For additional commands, e-mail: users-h...@qpid.apache.org
>
>
The discovery module provides the functionality necessary to implement
mechanisms for discovering and connecting to remote peers not known when
the client starts.  The implementation in 0.2.0 implements a multicast
listener that works with ActiveMQ brokers which can broadcast broker
addresses for listening clients.  The discovery bit acts as a layer on
top of failover collecting alternative remote peers to connect to.

-- 
Tim Bish
Sr Software Engineer | RedHat Inc.
tim.b...@redhat.com | www.redhat.com 
twitter: @tabish121
blog: http://timbish.blogspot.com/



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

Re: Changing from old Qpid JMS client to Qpid JMS 0.2.0

[Timothy Bish]

On 06/03/2015 09:45 AM, Erik Aschenbrenner wrote:
> Dear Qpid-Users,
>
> I just tried to use the new proton based Qpid JMS 0.2.0 client.
>
> I removed the jars of the old client (Qpid JMS 0.32) and added the jars of
> the new client to my project.
>
> When I try to start my application I'm getting this exception:
> javax.naming.NoInitialContextException: Cannot instantiate class:
> org.apache.qpid.amqp_1_0.jms.jndi.PropertiesFileInitialContextFactory [Root
> exception is java.lang.ClassNotFoundException:
> org.apache.qpid.amqp_1_0.jms.jndi.PropertiesFileInitialContextFactory]
>   at 
> javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:674)
>
> Is there something else that has to be changed in the code to get new Qpid
> JMS client working?
>
> Regards,
> Erik
>
>
>
> --
> View this message in context: 
> http://qpid.2158936.n2.nabble.com/Changing-from-old-Qpid-JMS-client-to-Qpid-JMS-0-2-0-tp7625652.html
> Sent from the Apache Qpid users mailing list archive at Nabble.com.
>
> -
> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
> For additional commands, e-mail: users-h...@qpid.apache.org
>
>
The JNDI configuration you are using will need to be updated to reflect
the new client code.  There is some documentation for this in the Git tree:

https://github.com/apache/qpid-jms/blob/master/qpid-jms-docs/Configuration.md

-- 
Tim Bish
Sr Software Engineer | RedHat Inc.
tim.b...@redhat.com | www.redhat.com 
twitter: @tabish121
blog: http://timbish.blogspot.com/


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

Re: Welcome Jakub Scholz as Qpid committer and PMC member

[Timothy Bish]

On 05/22/2015 02:24 PM, Robbie Gemmell wrote:
> The Qpid PMC has voted to grant commit rights and PMC membership to
> Jakub Scholz in recognition of his contributions to the project.
>
> Please join me in extending Jakub a warm welcome!
>
> Robbie
>
> -
> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
> For additional commands, e-mail: users-h...@qpid.apache.org
>
>
Welcome to the team Jakub!

-- 
Tim Bish
Sr Software Engineer | RedHat Inc.
tim.b...@redhat.com | www.redhat.com 
twitter: @tabish121
blog: http://timbish.blogspot.com/


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

Re: [VOTE] Ask infra to add git repo and JIRA for qpid-interop

[Timothy Bish]

+1

On Thu, May 21, 2015 at 5:35 AM, Robbie Gemmell 
wrote:

> On 19 May 2015 at 15:51, Kim van der Riet  wrote:
> > Thank you to all those who responded to my e-mail about the qpid-interop
> > project. I don't see any concern about this that precludes going ahead
> and
> > asking for infra to add a git repo and a JIRA for this project.
> >
> > In short, I am asking for a vote to:
> > Ask infra@ to add a git repo for qpid-interop;
> > Ask infra@ to add a JIRA for qpid-interop;
> > No additional mailing lists should be needed, as discussions should be
> > conducted on qpid-users@
> >
> > I will close the vote on Friday May 22.
> >
> > Kim van der Riet
> >
>
> +1
>
> -
> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
> For additional commands, e-mail: users-h...@qpid.apache.org
>
>


-- 
--
Tim Bish
---
RedHat Software
Email: tim.b...@fusesource.com
Web: http://fusesource.com
Twitter: tabish121
Blog: http://timbish.blogspot.com

Re: [VOTE] Release Qpid JMS client 0.2.0

[Timothy Bish]

+1

I performed the following checks

* Inspected the LICENSE and NOTICE files in both src and bin archives
* Validated the signatures for both archives.
* Built the project from the source archive and ran all tests (no failures).
* Reviewed the included documentation.
* Ran the example against an ActiveMQ broker.
* Used a build of ActiveMQ that pointed at the staging repo to run all
ActiveMQ JMS tests using 0.2.0 artefacts.

On 05/13/2015 12:10 PM, Robbie Gemmell wrote:
> Hi all,
>
> We have made a bunch of fixes and improvements since the previous
> client release, both in the client itself and also in Proton. It is
> time those were available via an updated client release, so I have put
> up an RC for folks to test and vote on.
>
> The source and binary archives can be grabbed from here:
> https://dist.apache.org/repos/dist/dev/qpid/jms/0.2.0-rc1/
>
> Those and the other individual maven artifacts are also staged for now at:
> https://repository.apache.org/content/repositories/orgapacheqpid-1034
>
> Regards,
> Robbie
>
>
> P.S. If you want to test it out from the staging repo using maven (e.g
> with the examples src, or your own things), add this to your poms:
>   
> 
>   staging
>   
> https://repository.apache.org/content/repositories/orgapacheqpid-1034
> 
>   
>
> The dependency for the client itself would then be:
>   
> org.apache.qpid
> qpid-jms-client
> 0.2.0
>   
>
> -
> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
> For additional commands, e-mail: users-h...@qpid.apache.org
>
>


-- 
Tim Bish
Sr Software Engineer | RedHat Inc.
tim.b...@redhat.com | www.redhat.com 
twitter: @tabish121
blog: http://timbish.blogspot.com/


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

Re: Qpid JMS 0.1.0 and SASL EXTERNAL

[Timothy Bish]

On 03/26/2015 08:19 AM, Jakub Scholz wrote:
> Hi Robbie, Tim,
>
> I was wondering ... does the new JMS client already support SASL EXTERNAL
> authentication? It looks like it selects the EXTERNAL mechanism when it is
> offered by the broker, but it looks like it never responds to the challenge
> sent by the broker (Qpid C++ 0.22 / MRG-M 3.0).
>
> Thanks & Regards
> Jakub
>
I know that Robbie did add some initial support for EXTERNAL but I'm not
sure to what extent it was tested or working, so we'd have to peek and
see.  My suggestion is that if you run into things like this you open a
JIRA at https://issues.apache.org/jira/browse/QPIDJMS/ to capture your
environment, broker config etc and we can try and get things sorted out. 

-- 
Tim Bish
Sr Software Engineer | RedHat Inc.
tim.b...@redhat.com | www.redhat.com 
skype: tabish121 | twitter: @tabish121
blog: http://timbish.blogspot.com/


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

Re: [VOTE] Release Qpid JMS 0.1.0

[Timothy Bish]

+1

* Verified the signatures matched
* Built source bundle and ran tests
* Tested ActiveMQ using staged jars
* Checked that all artefacts have proper license and notice files included.

On 03/16/2015 03:53 PM, Robbie Gemmell wrote:

Hi all,

We have reached a point that it would be useful to do an initial
release of the new Proton-based JMS client, so I have put up an RC for
folks to test and vote on.

The source and binary archives can be grabbed from here:
https://dist.apache.org/repos/dist/dev/qpid/jms/0.1.0-rc1/

Those and the other individual maven artifacts are also staged for now at:
https://repository.apache.org/content/repositories/orgapacheqpid-1030

I will close the vote some point towards the end of the week. I'll be
off on vacation by then so the exact timing is a little fuzzy but it
will be after 72hrs are up, i.e after 8pm GMT on Thursday 19th.

Regards,
Robbie


P.S. If you want to test it out from the staging repo (e.g using the
examples src, or your own things), add this to your poms:
   
 
   staging
   
https://repository.apache.org/content/repositories/orgapacheqpid-1030
 
   

The dependency for the client itself would then be:
   
 org.apache.qpid
 qpid-jms-client
 0.1.0
   

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





--
Tim Bish
Sr Software Engineer | RedHat Inc.
tim.b...@redhat.com | www.redhat.com
skype: tabish121 | twitter: @tabish121
blog: http://timbish.blogspot.com/


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

Re: [VOTE] Release Qpid 0.32

[Timothy Bish]

On 03/13/2015 11:45 AM, Justin Ross wrote:

Hi, folks.  As with 0.30, we are voting for each Qpid source component
individually, excluding Proton and Dispatch.

The artifacts proposed for release are here:

   https://dist.apache.org/repos/dist/dev/qpid/0.32-rc2/

They are signed.  If a given component is approved, the RC 2 bits will
become the GA bits.

Please indicate your vote for each component below.  If you favor
proceeding to GA, vote +1.  If you have reason to think a component is not
ready for release, vote -1.

* Checked for LICENSE and NOTICE files in all
* Built all from source on linux.
* Ran tests and a few of the examples.



  - Qpid C++ (qpid-cpp-0.32.tar.gz)

+1

  - Qpid Java (qpid-java-0.32.tar.gz)

+1


  - Qpid Java QMF tools (qpid-java-qmf-tools-0.32.tar.gz)

+1


  - Qpid Python (qpid-python-0.32.tar.gz)

+1


  - Qpid QMF (qpid-qmf-0.32.tar.gz)

+1


  - Qpid tests (qpid-tests-0.32.tar.gz)

+1


  - Qpid tools (qpid-tools-0.32.tar.gz)

+1


I will close the vote Wednesday evening US east coast time.

Thanks!
Justin

---
0.32 RC 2 thread:
http://qpid.2158936.n2.nabble.com/0-32-release-update-RC-2-is-available-td7621869.html
0.32 release page:
https://cwiki.apache.org/confluence/display/qpid/0.32+Release




--
Tim Bish
Sr Software Engineer | RedHat Inc.
tim.b...@redhat.com | www.redhat.com
skype: tabish121 | twitter: @tabish121
blog: http://timbish.blogspot.com/


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

Re: 0.32 release update - RC 2 is available

[Timothy Bish]

I wouldn't treat it as a blocker for the release, I'm pretty sure this 
has been popping up in our CI for some time now.


On 03/12/2015 12:36 PM, Rob Godfrey wrote:

>From looking at the code I don't think this is a new issue... I think
the same deadlock path would have been present in 0.30 and prior
versions (the two codepaths appear to me to be unchanged since Jan
2014).

I have made what I think is a fix on trunk, but given it's not a new
issue I'm not sure we can call it a blocker for release.  After 0.32
goes out I'm keen that we start doing more frequent releases of
individual components (as we have previously discussed), So I can
imagine we might put out a 0.32.1 version with a fix for this and
anything else that comes up.  Having said that, if there is a need for
a new RC to be spun for 0.32 for any other reason, it would be nice to
fix this :-)

-- Rob

On 12 March 2015 at 17:18, Robbie Gemmell  wrote:

Tim noticed an issue with the while working on some changes to ActiveMQ:
https://issues.apache.org/jira/browse/QPID-6447

On 12 March 2015 at 12:52, Justin Ross  wrote:

Hi, everyone.  Important defects were discovered soon after I published the
initial RC.  Here is RC 2 from revision 1666029.

   Release artifacts: https://dist.apache.org/repos/dist/dev/qpid/0.32-rc2/
   Maven staging repo:
https://repository.apache.org/content/repositories/orgapacheqpid-1028

This is pre-release code, for testing and nothing else!  Please try it in
your environment and report what you find.  A very big thanks is due to
those who have put in their time to evaluate the previous 0.32 artifacts.

These release artifacts are signed.  If approved by vote, the RC 2 bits
will be the final GA bits.  If no new blockers are discovered today, I will
open the vote tomorrow morning.

Thanks!
Justin

---
0.32 release page:
https://cwiki.apache.org/confluence/display/qpid/0.32+Release

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


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





--
Tim Bish
Sr Software Engineer | RedHat Inc.
tim.b...@redhat.com | www.redhat.com
skype: tabish121 | twitter: @tabish121
blog: http://timbish.blogspot.com/


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

Re: Qpid JMS 0.1.0-beta

[Timothy Bish]

On 03/11/2015 10:15 AM, Jakub Scholz wrote:

Hi Robbie,

I played with it a bit ... what I noticed is that it looks like it
completely ignores the truststore which I pass to the client using the
transport.trustStoreLocation option. Can it be that the
org.apache.qpid.jms.transports.TransportSupport has a bug in the
loadTrustManagers
method? I think it should do:
 String storeLocation = options.getTrustStoreLocation();
 String storePassword = options.getTrustStorePassword();
 String storeType = options.getStoreType();

 LOG.trace("Attempt to load TrustStore from location {} of type {}",
storeLocation, storeType);

instead of:
 String storeLocation = options.getKeyStoreLocation();
 String storePassword = options.getKeyStorePassword();
 String storeType = options.getStoreType();

 LOG.trace("Attempt to load KeyStore from location {} of type {}",
storeLocation, storeType);

Should I enter some JIRA or create a pull request on github?

Thanks & Regards
Jakub



Thanks for trying it out, I've pushed a fix for the problem so it should 
be fixed in the next spin.





On Mon, Mar 9, 2015 at 8:21 PM, Robbie Gemmell 
wrote:


Hi everyone,

I have posted a beta build for the new JMS client, in order to test
out the release process more and give people something fixed to test
around with before we release.

The source and binary archives for the beta can be grabbed from:
https://dist.apache.org/repos/dist/dev/qpid/jms/0.1.0-beta/

Those and the other maven artifacts are also staged for now at:
https://repository.apache.org/content/repositories/orgapacheqpid-1026

If you want to test it out from there (e.g using the examples src, or
your own things), add this to your poms:
   
 
   staging
   
https://repository.apache.org/content/repositories/orgapacheqpid-1026

 
   

The dependency for the client itself would then be:
   
 org.apache.qpid
 qpid-jms-client
 0.1.0-beta
   

Regards,
Robbie

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





--
Tim Bish
Sr Software Engineer | RedHat Inc.
tim.b...@redhat.com | www.redhat.com
skype: tabish121 | twitter: @tabish121
blog: http://timbish.blogspot.com/


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

Re: Qpid JMS 0.1.0-beta

[Timothy Bish]

On 03/09/2015 03:21 PM, Robbie Gemmell wrote:

Hi everyone,

I have posted a beta build for the new JMS client, in order to test
out the release process more and give people something fixed to test
around with before we release.

The source and binary archives for the beta can be grabbed from:
https://dist.apache.org/repos/dist/dev/qpid/jms/0.1.0-beta/

Those and the other maven artifacts are also staged for now at:
https://repository.apache.org/content/repositories/orgapacheqpid-1026

If you want to test it out from there (e.g using the examples src, or
your own things), add this to your poms:
   
 
   staging
   
https://repository.apache.org/content/repositories/orgapacheqpid-1026
 
   

The dependency for the client itself would then be:
   
 org.apache.qpid
 qpid-jms-client
 0.1.0-beta
   

Regards,
Robbie

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


I downloaded them both and checked things out.  The source archive 
builds and passes its tests and the examples in the binary distribution 
build and run fine for me.


--
Tim Bish
Sr Software Engineer | RedHat Inc.
tim.b...@redhat.com | www.redhat.com
skype: tabish121 | twitter: @tabish121
blog: http://timbish.blogspot.com/


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

Re: towards releasing the new AMQP 1.0 JMS client

[Timothy Bish]

On 02/19/2015 08:01 AM, Robbie Gemmell wrote:

Any more opinions out there on the name/version of the new client? If
not, I'll likely proceed to update the version to 0.1.0[-SNAPSHOT],
leave the module names as qpid-jms-foo, and begin working on setting
up a Jenkins job to publish snapshots to repository.apache.org later
today or tomorrow.

Robbie


I like the idea of just letting the new client supplant the old one 
using the QPid JMS name.  I'm pretty sure no matter what we called it 
there'd be confusion so I think its better to just try and do a good job 
of making things clear on the website and answer the question as they 
come up.  Over time this should all work itself out.




On 18 February 2015 at 22:39, Steve Huston  wrote:

-Original Message-
From: Robbie Gemmell [mailto:robbie.gemm...@gmail.com]
Sent: Wednesday, February 18, 2015 10:41 AM
To: users@qpid.apache.org
Subject: Re: towards releasing the new AMQP 1.0 JMS client

On 18 February 2015 at 14:59, Justin Ross  wrote:

On Wed, Feb 18, 2015 at 7:33 AM, Robbie Gemmell

wrote:


At the moment the version number is 0.1[-SNAPSHOT], to be followed by
0.2 etc until we think there is sufficient maturity to go 1.0
(sidenote: not years :P). The initial focus has been on implementing
the JMS 1.1 API for now so change will come once we begin
implementing the JMS 2.0 API, which could also be when we bump to 2.0
for the client itself if we hadn't already for other reasons. I
envisage us doing releases more frequently than our existing
components have tended to and expect we will do small point releases
eventually, so I think it probably makes sense to use 0.1.0 etc from
the start (or even
0.0.1 to underscore its the initial release). We could consider
adding alpha/beta etc status, however we would then have to contend
with the version ordering disparities between e.g Maven and OSGi by
crafting some horrible release versions (including the final
versions), and I'm not much of a fan of publishing those to central.


All of this seems fine to me, except perhaps 0.0.1.  That looks very
strange to me--like a patch update on a 0.0 release--and I think 0.1
gets the point across well enough.


Point taken. In that case 0.1.0 is what I would propose starting with.
Skipping back and forth between 2 and 3 digits isnt something I want to do,
but I do want to do point releases if appropriate.

+1 to that.


Next up is the name. The new client has thus far been called simply
'Qpid JMS', with module names qpid-jms-foo, and binary tar
apache-qpid-jms[-bin]. We already release two other JMS clients, the
original AMQP 0-x one, module named qpid-client, and the older AMQP
1.0 one, module named qpid-amqp-1-0-jms-client. Although the new
clients name describes what it is, and the version numbers will
differ from the previous clients, do people think this is enough

difference?

I think it is still going to be confusing for people no matter what
we do here, but should we perhaps give the new client a component
name to allow them more easily distinguished, i.e a name of the style
Qpid Foo or Qpid FooJMS? If so, any ideas (failing spectacularly over

here)?

I lean toward letting the new jms impl take the prime naming real estate:
qpid-jms, as you have it now.  I haven't thought of a good name ("Qpid
JamSession"? kidding), and since this is really where we want to
direct users going forward, it deserves the mantle of "Qpid JMS".


Thats why we went with that originally, I think it is an entirely appropriate
name for what it is/will be, and I certainly havent been able to think of
anything that fits as nice. Its just a question of whether its a bit overloaded.
I'm happy to leave it as it is if people think we can manage things going
forward though.

I agree with Justin to position the new AMQP 1.0 JMS client as Qpid JMS, even 
at the risk of some short term confusion.


Could we rename the qpid-amqp-1-0-jms-client artifact to include the
word "prototype"?

I think its a few years late for that hehe. If we were renaming, I'd possibly go
with 'legacy' or something to that effect, but I'd quite possibly leave it
unchanged.

I think that leaving it as is is fine, and make the distinction on the web 
site, aiming to have just the Qpid JMS after a small number of releases.


On the website, I see the previous AMQP 1.0 jms client as being
visible but not prominent, and perhaps only available through some extra

navigation.

The new AMQP 1.0 client, and the 0-10-0-8 client, should be the
featured offerings (especially the former).

+1

-Steve


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





--
Tim Bish
Sr Software Engineer | RedHat Inc.
tim.b...@redhat.com | www.redhat.com
skype: tabish121 | twitter: @tabish121
blog: http://timbish.blogspot.com/


-
To unsubscribe, e

Any ETA on a QPid 0.32 release

[Timothy Bish]

We've been working on improving the AMQP 1.0 support in ActiveMQ and 
I've found that the trunk code for QPid JMS client contains some fixes 
that would be nice to have in for testing the fixes that are in the 
pipeline for the broker.  Was wondering if there is any idea on when the 
0.32 release process might start rolling?


--
Tim Bish
Sr Software Engineer | RedHat Inc.
tim.b...@redhat.com | www.redhat.com
skype: tabish121 | twitter: @tabish121
blog: http://timbish.blogspot.com/


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

Re: Timeline to drop Java 6 support for Proton?

[Timothy Bish]

Just for information purposes the next release of ActiveMQ which hopes 
to use Proton 0.8 once it's released has now moved onto support for JDK 
7 and dropped official support for JDK 6.


On 09/24/2014 10:24 AM, Robbie Gemmell wrote:

The compilation issue I missed in the patch was test-only this time, but it
could have as easily been in non-test code. The other tests now failing
might actually point to some functionality under test not working under
Java 6 at runtime though, which is more of an issue. If the tests showing
it didnt exist, or the CI job had been using either the current or previous
major Java release, then that might not have been noticed prior to release.

Whether it compiles or not isnt the only reason to drop support. Releasing
new versions that people can continue deploying to EOL plaforms in years to
come isnt necessarily helping anyone if we aren't in fact properly ensuring
it really works there. If we dont tuly support it, we should probably cut
it.

Whether we do it now, or later, I just think it would be a good idea to
actually decide on a timeline.

Robbie

On 24 September 2014 14:11, Clebert Suconic  wrote:


This is just testing... can't you have a java7 tests folder? you would be
able to still have java7 specific tests.



On Sep 24, 2014, at 7:13 AM, Robbie Gemmell 
wrote:


Hi all,

With Qpid 0.30 we have made the move to requiring Java 7+. Currently,
proton still allows for use of Java 6, so I wonder what peoples thoughts
are on the timing of a similar move for Proton? I'd personally like to do
it soon since Java 6 is EOL, but if not then I think we should at least
decide when we will.

Robbie

Background:
I committed a patch yesterday which contained some Java 7 API usage in

its

tests, and subsequently broke the ASF Jenkins jobs that are still using
Java 6 (I'm using 8). Having now noticed this I updated the test to make

it

compile and run on Java 6, unfortunately having to disable use of some of
the input aimed at testing the defect in question. Everything now

compiles

and the test in question passes, but the overall test run is still

failing

because it turns out some other new changes in recent days mean there are
now a couple of URL tests which fail on Java 6 (but work on Java 8).





--
Tim Bish
Sr Software Engineer | RedHat Inc.
tim.b...@redhat.com | www.redhat.com
skype: tabish121 | twitter: @tabish121
blog: http://timbish.blogspot.com/


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

Re: [VOTE] Migrate the repo for the new JMS client work to use Git

[Timothy Bish]

On 09/16/2014 12:35 PM, Robbie Gemmell wrote:

Hello all,

I mentioned this briefly in a previous thread, and have decided just to
call a vote on the subject. I would like to migrate the repo for the new
JMS client work to use Git rather than Subversion.

This wont affect the rest of the Qpid codebase, though it could be viewed
as a test for any such move in future. Only the bits in the following
subtree are under consideration for migation at this time:
http://svn.apache.org/repos/asf/qpid/jms/

I believe it would make things easier for those of us currently working on
it, and ease future usage of things like the Github integration we
can/should have Apache infra enable. For anyone still wanting to use a
Subversion client to check things out, there will still be an option there
as e.g. Github repos can also be checked out with svn clients, and Apache
mirror things to Github.

Please cast your votes. Even if you don't intend to work on the code in
question, please vote or at least contribute your thoughts to any
discussion that pops up. I will tally the votes after this point on Friday,
i.e. 72hrs.

Robbie


+1 from me

--
Tim Bish
Sr Software Engineer | RedHat Inc.
tim.b...@redhat.com | www.redhat.com
skype: tabish121 | twitter: @tabish121
blog: http://timbish.blogspot.com/


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

Re: Welcome Tim Bish as a Qpid committer (was Re: Proton-based AMQP 1.0 JMS client collaboration)

[Timothy Bish]

On 09/15/2014 09:18 AM, Gordon Sim wrote:

On 09/08/2014 09:31 AM, Robbie Gemmell wrote:
As many of you know, there is work going on within Qpid towards 
creating a
new AMQP 1.0 JMS client based around Proton and implementing a JMS 
mapping

for AMQP as being documented by the OASIS AMQP Bindings & Mappings TC.
Timothy Bish, one of the committers/PMC members at the Apache ActiveMQ
project, is going to join me working on this effort going forward.

Tim has previously done a lot of work on an JMS 1.1 AMQP 1.0 client 
using

Proton for AMQP 1.0 support, with his existing code being available at
https://github.com/tabish121/NeutronJMS/tree/amqp-only. The code base is
markedly further along in terms of the wider client such as
Connection/Session/Producers/Consumers when compared to the existing 
work

here at Qpid, which has concentrated initially more on message
implementation and mapping.


The Qpid PMC voted to grant Tim, a long standing ActiveMQ contributor 
and PMC member, commit rights to Qpid to facilitate this valuable 
collaboration between the projects.


Welcome Tim, and thanks very much for your help on this!




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


Great, thanks for giving me a chance to contribute to the project, 
looking forward to working with you all.


--
Tim Bish
Sr Software Engineer | RedHat Inc.
tim.b...@redhat.com | www.redhat.com
skype: tabish121 | twitter: @tabish121
blog: http://timbish.blogspot.com/


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

Re: Serious Bug in AMQP 1.0 JMS Client with persistent messages

[Timothy Bish]

On 01/08/2014 05:34 PM, uromahn wrote:

With the patch added to my local sources, I ran a bunch of different tests
against an ActiveMQ 5.9.0 and 5.10-SNAPSHOT broker using the patched as well
as unpatched client library.

To summarize my findings:
1. running the patched client against ActiveMQ 5.9.0 without sync-publish
set at all does not seem to force sync-publish which could be proven by
message loss when killing the broker
2. running the patched or unpatched client against ActiveMQ 5.9.0 with
sync-publish=true set explicitly is publishing one single message and then
"hanging" on the send() call
3. running the patched client against ActiveMQ 5.10-SNAPSHOT without
sync-publish set at all seems to force sync-publish as demonstrated by *no*
message loss when killing the broker
4. running the unpatched client against ActiveMQ 5.10-SNAPSHOT also seems to
force sync-publish as demonstrated by *no* message loss when killing the
broker.
5. running the patched or unpatched client against ActiveMQ 5.10-SNAPSHOT
with sync-publish=true explicitly set is publishing one single message and
then "hanging" on the send() call

In addition to the "hanging" of the send() call with sync-publish=true set,
I also sense an issue within ActiveMQ as well.




--
View this message in context: 
http://qpid.2158936.n2.nabble.com/Serious-Bug-in-AMQP-1-0-JMS-Client-with-persistent-messages-tp7602408p7602448.html
Sent from the Apache Qpid users mailing list archive at Nabble.com.

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


You need to build ActiveMQ from source or wait for a new SNAPSHOT build 
as the sync send issue was resolved today with the fix for: 
https://issues.apache.org/jira/browse/AMQ-4741


--
Tim Bish
Sr Software Engineer | RedHat Inc.
tim.b...@redhat.com | www.fusesource.com | www.redhat.com
skype: tabish121 | twitter: @tabish121
blog: http://timbish.blogspot.com/


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

Re: Serious Bug in AMQP 1.0 JMS Client with persistent messages

[Timothy Bish]

On 01/08/2014 03:41 PM, Rob Godfrey wrote:

On 8 January 2014 21:27, Fraser Adams  wrote:


On 08/01/14 18:55, Rob Godfrey wrote:


Hi Uli,

To enable synchronous publishing you need to either set the Java system
property "qpid.sync_publish" to true, or have sync-publish=true as one of
the URL options in your connection URL.

I agree it should be the default, and we can look to change this in a
future release.


Hmm, I'd really rather you didn't do that. Async behaviour has been the
default behaviour with Qpid from year dot. so changing it is pretty likely
to bite someone nastily.

I'd agree that async behaviour technically means that by default Qpid
breaches JMS guarantees, but TBH I think it's a little late in the day now
to be going switching the default. It's also make the default behaviour
inconsistent with qpid::messaging which doesn't seem ideal.



Given this is a totally separate client, (and is vastly different in many
other ways - like different connection URLs, different address formats,
etc.) and it's probably being used more widely against non-qpid
brokers/services than it is against Qpid right now, then I'm not sure I'm
too worried about refleting the behaviour of the AMQP 0-8/9/9-1/10 client.
I think the bigger issue in switching the default right now is that it
would seem that it would break anyone trying to use it with ActiveMQ.



As we've discussed before not everyone has guaranteed delivery right up
there at the top end of things they give a damn about, in my case it's all
about performance and I can take the hit if I lose the odd message - plenty
more where they came from :-) I probably wouldn't be wildly amused to
upgrade to Qpid version "x" only to find a massive performance regression
that might force me to get a non-trivial number of clients to change some
bit of config. or other.



The "intelligent" change would be to only use syn publishing with
persistent but non-transactional messaging.  If you are using transient you
clearly aren't looking for guaranteed delivery anyway.  If you are using
transation, you get your guarantee at the commit.  This is the "expected"
behaviour for JMS (though most implementations offer a switch to turn it
off so people can get better performance... in which case you have to
wonder why they are using persistent messaging in the first place)

Anyway given the issues with ActiveMQ - I won't be changing it for the
moment anyways.

-- Rob



Frase




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



I submitted a patch for the issue that was opened for this thread:

https://issues.apache.org/jira/browse/QPID-5455

It enables sync sends either when the flag is set or the JMS 
DeliveryMode that was requested is PERSISTENT and there is no current TX 
in progress.  Testing against a 0.26-SNAPSHOT with the fix and an 
ActiveMQ 5.10-SNAPSHOT things seem to be working fine.


--
Tim Bish
Sr Software Engineer | RedHat Inc.
tim.b...@redhat.com | www.fusesource.com | www.redhat.com
skype: tabish121 | twitter: @tabish121
blog: http://timbish.blogspot.com/


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