Re: Message going in topic with the use of "session.createQueue(name)"

[Timothy Bish]

On 07/30/2018 01:00 PM, akabhishek1 wrote:

HI Robbie And Tim,

It's quite old topic, but still i want to provide update on this issue.

I raised this issue with Microsoft and they accepted this issue and released
fixes in “azure-servicebus-1.2.7”.

I have done testing with “azure-servicebus-1.2.7”  and getting expected
error now. They are using "proton-j-0.22.0" internally. I don't know, what
they have done changes to fix this issue but we are getting expected error.

I want to request you, if possible please take a look on this issue again.
It will be great if we can get same feature in Qpid JMS.


What feature are you requesting for Qpid JMS?  From the previous 
discussion on the list on this thread I don't see anything that wasn't 
already working as it should in the client.



Regards,
Abhishek Kumar





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

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

[Timothy Bish]

On 07/31/2018 11:00 AM, Robbie Gemmell wrote:

Hi folks,

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

The files can be grabbed from:
https://dist.apache.org/repos/dist/dev/qpid/proton-j/0.27.3-rc1/

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

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

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

The dependency for proton-j would then be:

   
 org.apache.qpid
 proton-j
 0.27.3
   

-
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 binary for licensee and notice files.
* Checked for license headers with 'mvn apache-rat:check'
* Built source and ran the unit tests
* Built Qpid JMS master branch using the staged artifact and ran the tests
* Built ActiveMQ 5.x master branch using the staged artifact and ran the 
tests
* Built ActiveMQ Artemis master branch using the staged artifact 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.28.1

[Timothy Bish]

On 07/31/2018 12:18 PM, Robbie Gemmell wrote:

Hi folks,

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

The files can be grabbed from:
https://dist.apache.org/repos/dist/dev/qpid/proton-j/0.28.1-rc1/

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

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

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

The dependency for proton-j would then be:

   
 org.apache.qpid
 proton-j
 0.28.1
   

-
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 binary for licensee and notice files.
* Checked for license headers with 'mvn apache-rat:check'
* Built source and ran the unit tests
* Built Qpid JMS master branch using the staged artifact and ran the tests
* Built ActiveMQ 5.x master branch using the staged artifact and ran the 
tests
* Built ActiveMQ Artemis master branch using the staged artifact 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: [DISCUSS] Ending support for Java 7 in Proton-J

[Timothy Bish]

+1

I'd be happy if we moved up to 8 and allow for usage of some of the APIs 
not available in 7


On 08/08/2018 02:04 PM, Robbie Gemmell wrote:

I think this is probably as much a notice as a discussion, however...

In a previous mail thread [1] some 20 months ago, I proposed requiring
Java 8 support for some components, particularly the JMS client ahead
of its 0.20.0 release, for which the change [2] was made days later
given the support voiced.

At the time I said I didnt mind proton-j sticking on Java 7 a bit
longer, even though most uses of it I was aware of would/did already
require 8 at the time. It has now been 'a bit' longer and the switch
has never been made, and I'd say its time it was. I'm no longer
familiar with any usage of proton-j that doesn't itself require Java 8
already. 8 is getting on in years itself now and 11 is almost upon us
as the next long lasting version.

Thoughts? I'll proceed with the change soon unless there are
compelling arguments otherwise.

Robbie

[1] 
https://lists.apache.org/thread.html/00b8f739bd5a653ebb1ce096566fdaf35b0c8cfe749b2ba81bf7c38c@%3Cusers.qpid.apache.org%3E
[2] https://issues.apache.org/jira/browse/QPIDJMS-248

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

[Timothy Bish]

On 08/10/2018 04:12 PM, Robbie Gemmell wrote:

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

The files can be grabbed from:
https://dist.apache.org/repos/dist/dev/qpid/proton-j/0.29.0-rc1/

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

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

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

The dependency for proton-j would then be:

   
 org.apache.qpid
 proton-j
 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 in the archives
* Built the source and ran the tests
* Validated license headers on the source with 'mvn apache-rat:check'
* Built ActiveMQ 5.x master using the staged artifacts and ran the AMQP 
tests
* Built ActiveMQ Artemis master using the staged artifacts and ran the 
AMQP tests

* Built Qpid JMS master using the staged artifacts 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 JMS 0.36.0

[Timothy Bish]

On 08/15/2018 02:18 PM, Robbie Gemmell wrote:

I have put together a spin for a 0.36.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.36.0-rc1/

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

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

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

The dependency for the client itself would then be:

   
 org.apache.qpid
 qpid-jms-client
 0.36.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 archives for license and notice files
* Ran the rat check maven goal to check for missing license headers
* Built from source and ran the tests
* Built ActiveMQ 5.x using staged artifacts and ran the AMQP tests
* Built ActiveMQ Artemis using staged artifacts 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-interop-test 0.2.0 (RC4)

[Timothy Bish]

On 08/24/2018 01:39 PM, Gordon Sim wrote:

On 14/08/18 14:52, Kim van der Riet wrote:

Hi,

I have assembled a proposed release for Apache Qpid Interop Test 
0.2.0 (RC4). The Python path issue found in RC3 was fixed. Please try 
it out and test it, then vote accordingly on this thread.


+1 (managed to build it from source - build needs to be under source 
dir, and ran tests with c++ broker, c++ client, rhea and python2).


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



+1

Built and ran against ActiveMQ 5.x master

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

[Timothy Bish]

On 07/20/2018 06:10 AM, Robbie Gemmell wrote:

I have put together a spin for a 0.35.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.35.0-rc1/

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

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

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

The dependency for the client itself would then be:

   
 org.apache.qpid
 qpid-jms-client
 0.35.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 archives
* Validated source license headers with mvn apache-rat:check
* Built from source and ran the tests on a couple different platforms
* Built ActiveMQ 5.x using staged artifacts and ran the AMQP tests
* Bult ActiveMQ Artemis using the staged artifacts 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.27.2

[Timothy Bish]

On 07/13/2018 03:39 PM, Robbie Gemmell wrote:

Hi folks,

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

The files can be grabbed from:
https://dist.apache.org/repos/dist/dev/qpid/proton-j/0.27.2-rc1/

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

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

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

The dependency for proton-j would then be:

   
 org.apache.qpid
 proton-j
 0.27.2
   

-
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 license and notice files
* Built from source and ran the tests
* Built Qpid JMS using staged artifacts and ran the tests
* Built ActiveMQ 5.x using staged artifacts and ran the AMQP tests
* Built ActiveMQ Artemis using the staged artifacts and ran the AMQP 
integration 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.28.0

[Timothy Bish]

On 07/13/2018 04:33 PM, Robbie Gemmell wrote:

Hi folks,

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

The files can be grabbed from:
https://dist.apache.org/repos/dist/dev/qpid/proton-j/0.28.0-rc1/

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

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

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

The dependency for proton-j would then be:

   
 org.apache.qpid
 proton-j
 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
* Checked license and notice files
* Built from source and ran the tests
* Built Qpid JMS using staged artifacts and ran the tests
* Built ActiveMQ 5.x using staged artifacts and ran the AMQP tests
* Built ActiveMQ Artemis using the staged artifacts and ran the AMQP 
integration 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] Severe performance issue after upgrading from 0.33.0 to 0.34.0

[Timothy Bish]

On 07/11/2018 04:44 PM, jo.stenb...@offilive.com wrote:

When upgrading from qpid-jms client 0.33.0 to 0.34. we can see a massive 
performance degradation when sending messages. With 0.33.0 we can send 
9000msg/s to our Artemis broker via a single JMS Connection/JMS Producer. 
Switching to v0.34.0 we can only send 100msg/s with the same client.

Interestingly the CPU usage is at 2% so I guess there may be some resource 
synchronization/locking related problem in the latest version.

Is this a known issue? Can anyone else confirm this?

Thanks,
Jo



This would be surprising given most testing on the client shows 
significant performance gains over the previous release.  Without 
additional information on you setup and configuration and perhaps some 
frame tracing to see what is going on at the protocol level it would be 
quite difficult to guess what might be going on.



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

[Timothy Bish]

On 02/28/2018 02:33 PM, Robbie Gemmell wrote:

Hi folks,

I have put together a spin for a Qpid Proton 0.21.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.21.0-rc1/

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

It is tagged as 0.21.0-rc1.

Regards,
Robbie

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



+1

* Verified signatures and checksums
* Checked for License and NOTICE files
* Built from source and ran the tests
* Ran some examples against an Artemis broker install


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

[Timothy Bish]

On 04/13/2018 03:03 PM, Robbie Gemmell wrote:

Hi folks,

I have put together a spin for a Qpid Proton-J 0.27.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.27.0-rc1/

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

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

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

The dependency for proton-j would then be:

   
 org.apache.qpid
 proton-j
 0.27.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
* checked for license and notice files in the archives
* Built from source and ran the tests
* Built Qpid JMS using staged bits and ran the tests
* Dropped proton jar into Artemis build and ran some tests against 
running instance
* Dropped proton jar into ActiveMQ 5 build and ran some tests against 
running instance



--
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.27.0 (RC2)

[Timothy Bish]

On 04/18/2018 04:01 PM, Robbie Gemmell wrote:

Hi folks,

I have put together a second spin for a Qpid Proton-J 0.27.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.27.0-rc2/

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

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

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

The dependency for proton-j would then be:

   
 org.apache.qpid
 proton-j
 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 license and notice files in the archives
* Built from source and ran the tests, also ran tests with PN_TRACE_FRM 
manually enabled

* Ran the mvn apache-rat:check command to check for missing license headers
* Built Qpid JMS branch with changes to use this version's new APIs and 
ran tests
* Built Artemis branch with changes to use this version's new APIs and 
ran tests

* Dropped the 0.27.0 jar into an Artemis build and ran tests against it
* Dropped the 0.27.0 jar into an ActiveMQ 5.x build and ran tests against it

--
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 --> 0.31.0, Azure Service Bus - Cannot allocate more handles to the current session or connection. The maximum number of handles allowed is 4999.

[Timothy Bish]

On 04/23/2018 05:45 PM, Abhishek Kumar wrote:

HI Team,

I am using "qpid-jms-client --> 0.31.0" for sending message to Azure 
Service Bus. I am sending 10K msgs. While sending 10k messages only 5k 
messages successfully sent. After sending 5k messages, i am 
continuously getting error" Cannot allocate more handles to the 
current session or connection.The maximum number of handles allowed is 
4999. Please free up resources and try again. [condition = 
amqp:resource-limit-exceeded] (javax.jms.ResourceAllocationException) "


I opened "jvisualvm" and found that lot of "JmsSession Completion 
Dispatcher" thread are open. Please find attached screen shot.  I did 
a lot R but i could not find any solution to solve this issue.




This would suggest that you are creating a number of JMS Sessions in 
your application and those are not being closed.  The completion thread 
is generally not created unless you are doing JMS 2.0 style asynchronous 
sends so you could start by reviewing that area of your code to see if 
you have a resource leak which would be my first suspicion given the 
error that you are receiving.


Could you please suggest any solution to solve this issue. Please find 
below code snippet and error details



*_Error Stack Trace_*
*_
_*

Message               : Cannot allocate more handles to the current 
session or connection. The maximum number of handles allowed is 4999. 
Please free up resources and try again. [condition = 
amqp:resource-limit-exceeded] (javax.jms.ResourceAllocationException)

JMS Code              : null
Element               : /servicebusConnector @ app:test-mule-jms.xml:19

Root Exception stack trace:
javax.jms.ResourceAllocationException: Cannot allocate more handles to 
the current session or connection. The maximum number of handles 
allowed is 4999. Please free up resources and try again. [condition = 
amqp:resource-limit-exceeded]
at 
org.apache.qpid.jms.provider.amqp.AmqpSupport.convertToException(AmqpSupport.java:145)
at 
org.apache.qpid.jms.provider.amqp.AmqpSupport.convertToException(AmqpSupport.java:117)
at 
org.apache.qpid.jms.provider.amqp.AmqpAbstractResource.processRemoteClose(AmqpAbstractResource.java:262)
at 
org.apache.qpid.jms.provider.amqp.AmqpProvider.processUpdates(AmqpProvider.java:973)
at 
org.apache.qpid.jms.provider.amqp.AmqpProvider.access$1900(AmqpProvider.java:104)
at 
org.apache.qpid.jms.provider.amqp.AmqpProvider$17.run(AmqpProvider.java:831)

at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)

at java.lang.Thread.run(Thread.java:748)



*_Connection CODE_*
Hashtable hashtable = new Hashtable<>();
hashtable.put("connectionfactory.SBCF","failover:(amqps://" + host + 
")?failover.reconnectDelay=2000=20=true=3=10");

hashtable.put("queue.QUEUE", "iptest2");

hashtable.put(Context.INITIAL_CONTEXT_FACTORY, 
QPID_CONNECTION_FACTORY_CLASS);


Context context = new InitialContext(hashtable);

ConnectionFactory connectionFactory = (ConnectionFactory) 
context.lookup("SBCF");


destination = (Destination) context.lookup("QUEUE");

// Create Connection
Connection connection = connectionFactory.createConnection(username, 
password);


connection.setExceptionListener(this);
connection.start();

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

MessageProducer producer = session.createProducer(destination);

this.setJmsSession(session);
this.setMessageProducer(producer);
this.setDestination(destination);
this.setConnection(connection);


*_Sender - Parallel 16 threads are running to send_*
/               producer.send(jmsMessage);/

Regards,
Abhishek Kumar




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

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

[Timothy Bish]

I've added a fix in ea46607e776062c8555ef24a74c48a9b12bf2ca9 that I 
think sound resolve this.  Sadly we need to -1 this release candidate 
and spin a new one.


changing vote to -1

On 04/17/2018 06:49 PM, Keith W wrote:

With the 0.27.0 RC (and the Qpid JMS Client 0.31.0) I am noticing a
java.lang.ArrayIndexOutOfBoundsException when PN_TRACE_FRM=true, which
did not occur with 0.26.0.

My JMS code fragment (based on HelloWorld).

Context context = new InitialContext();
ConnectionFactory factory = (ConnectionFactory)
context.lookup("myFactoryLookup");
Destination queue = (Destination) context.lookup("myQueueLookup");
Connection connection =
factory.createConnection(System.getProperty("USER"),
System.getProperty("PASSWORD"));
Session session = connection.createSession(false, Session.AUTO_ACKNOWLEDGE);
MessageProducer messageProducer = session.createProducer(queue);
BytesMessage message = session.createBytesMessage();
message.writeBytes(new byte[261955 /*261954 wont produce the AIOOBE*/]);
messageProducer.send(message);

and the protocol trace/stack trace:

/Library/Java/JavaVirtualMachines/jdk1.8.0_162.jdk/Contents/Home/bin/java
-DUSER=admin -DPASSWORD=admin "-javaagent:/Applications/IntelliJ
IDEA.app/Contents/lib/idea_rt.jar=53139:/Applications/IntelliJ
IDEA.app/Contents/bin" -Dfile.encoding=UTF-8 -classpath

Re: [VOTE] Release Apache Qpid JMS 0.31.0

[Timothy Bish]

On 03/22/2018 02:44 PM, Robbie Gemmell wrote:

Hi folks,

I have put together a spin for a 0.31.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.31.0-rc1/

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

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

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

The dependency for the client itself would then be:

   
 org.apache.qpid
 qpid-jms-client
 0.31.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 included License and Notice files.
* Checked source licenses using mvn apache-rat:check
* Built from source and ran the tests
* Built ActiveMQ 5.x against staged artifacts and ran the AMQP test suite
* Built ActiveMQ Artemis against staged artifacts and ran the AMQP test 
suite
* Built the example and ran the Hello World sample against an ActiveMQ 
5.x broker


--
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 C++ 1.38.0

[Timothy Bish]

+1

* Validated signatures and checksums
* Built from source and ran the tests

On 03/23/2018 08:45 AM, Robbie Gemmell wrote:

On 22 March 2018 at 12:33, Justin Ross  wrote:

Hi, all.  Please test this release candidate and indicate your vote on this
thread.

Source archive and signatures:
https://dist.apache.org/repos/dist/dev/qpid/cpp/1.38.0-rc1/

Issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310520=12340228

Tag:
1.38.0-rc1

+1

Checked thigns out as follows:
- Verified signature and checksum files.
- Checked for LICENCE+NOTICE files.
- Ran the source build against proton-0.21.0, ran the tests, all passed.
- Ran the qpid-jms 0.31.0 (RC1) HelloWorld example against the built broker.

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 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=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.27.1

[Timothy Bish]

On 04/25/2018 04:50 PM, Robbie Gemmell wrote:

I have put together a spin for a Qpid Proton-J 0.27.1 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.27.1-rc1/

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

The only change is https://issues.apache.org/jira/browse/PROTON-1836, which
affects use of some new functionality added in 0.27.0.

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

The dependency for proton-j would then be:

   
 org.apache.qpid
 proton-j
 0.27.1
   

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



+1

* Verified signatures and checksums
* Built from source and ran tests
* Built ActiveMQ 5.x using staged binaries and ran the AMQP tests
* Built ActiveMQ Artemis using staged binaries and ran the AMQP tests
* Built Qpid JMS using staged artifacts 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 C++ 1.39.0

[Timothy Bish]

On 10/22/18 8:47 AM, Justin Ross wrote:

Hi, everyone.  Please test this release candidate and vote based on what
you find.

Source archive and signatures:
https://dist.apache.org/repos/dist/dev/qpid/cpp/1.39.0-rc1/

Issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310520=12342978

Tag:
1.39.0-rc1


+1

* Verified signatures and checksums
* Checked for license and notice files
* Built from source and ran the tests
* Ran some examples applications against an external ActiveMQ broker.




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

[Timothy Bish]

On 10/01/2018 09:58 AM, Robbie Gemmell wrote:

Hi folks,

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

The files can be grabbed from:
https://dist.apache.org/repos/dist/dev/qpid/proton/0.26.0-rc1/

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

It is tagged as 0.26.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
* Reviewed license and notice files
* built from source and ran the tests.
* Ran a couple of the examples against an Artemis broker build.

I did run into some issues building the library on a recent ubuntu based 
distro due to the new json-cpp dependency and the fact that on ubuntu 
the json/value.h header is located under /usr/include/json-cpp/json as 
opposed to older variants that seem to have it under /usr/include/json.  
I removed the libjsoncpp-dev package and that allowed me to build and 
run the tests as on previous releases.


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

[Timothy Bish]

On 09/28/2018 01:32 PM, Robbie Gemmell wrote:

Hi folks,

I have put together a spin for a 0.37.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.37.0-rc1/

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

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

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

The dependency for the client itself would then be:

   
 org.apache.qpid
 qpid-jms-client
 0.37.0
   

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



+1

* Checked for license and notice files in archives
* Validated signatures and checksums
* Built from source and ran the tests
* Built ActiveMQ 5.x master using staged artifacts and ran the AMQP tests
* Built ActiveMQ Artemis 2.6.3 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.26.0 (RC2)

[Timothy Bish]

On 10/04/2018 08:27 AM, Robbie Gemmell wrote:

Hi folks,

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

The files can be grabbed from:
https://dist.apache.org/repos/dist/dev/qpid/proton/0.26.0-rc2/

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

The changes since RC1 were made via PROTON-1946 and PROTON-1947 (fixup
sub tasks for PROTON-1935).

It is tagged as 0.26.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
* Checked for license and notice files
* Built from source and ran the tests
* Previous compilation failure now resolved
* Confirmed that the previously failing test is now passing
* Ran samples against an ActiveMQ Artemis broker instance


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

[Timothy Bish]

On 12/17/18 6:46 AM, Robbie Gemmell wrote:

Hi folks,

I have put together a spin for a 0.40.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.40.0-rc1/

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

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

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

The dependency for the client itself would then be:

   
 org.apache.qpid
 qpid-jms-client
 0.40.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
* Checked for license and notice files in the archives
* Built from source and ran the test suite
* Verified license headers using 'mvn apache-rat:check'
* Built ActiveMQ 5.x using the staged artifacts and ran the AMQP tests
* Built ActiveMQ Artemis master using the staged artifacts and ran the 
AMQP integration 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.31.0

[Timothy Bish]

On 11/23/18 11:01 AM, Robbie Gemmell wrote:

Hi folks,

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

The files can be grabbed from:
https://dist.apache.org/repos/dist/dev/qpid/proton-j/0.31.0-rc1/

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

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

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

The dependency for proton-j would then be:

   
 org.apache.qpid
 proton-j
 0.31.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 archive files for License and Notice files
* Built from source and ran the test suite
* Built ActiveMQ 5.x using the staged artifacts and ran the AMQP tests
* Built ActiveMQ Artemis using the staged artifacts and ran the AMQP tests
* Built Qpid JMS using the staged artifacts and ran the tests
* Checked the license headers using apache rat from maven


--
Tim Bish


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

Re: Welcome Roddie Kieley as an Apache Qpid committer

[Timothy Bish]

On 11/27/18 9:27 AM, Robbie Gemmell wrote:

The Qpid PMC have voted to grant commit rights to Roddie Kieley in
recognition of continued contributions to the project.

Welcome, Roddie!

Robbie

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



Congratulations Roddie, welcome aboard!

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

[Timothy Bish]

On 11/28/18 8:36 AM, Robbie Gemmell wrote:

Hi folks,

I have put together a spin for a 0.39.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.39.0-rc1/

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

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

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

The dependency for the client itself would then be:

   
 org.apache.qpid
 qpid-jms-client
 0.39.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 archives for License and Notice files
* Built from source and ran the tests
* Validated license headers in source via 'mvn apache-rat:check'
* Built ActiveMQ 5.x with staged artifact and ran the test suite
* Built Artemis with staged artifact and ran the test suite


--
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 0.35.0 problem reading message after some message redeliveries

[Timothy Bish]

This has been identified as an issue in the Artemis broker's AMQP 
implementation and fixed for the next release:

https://issues.apache.org/jira/browse/ARTEMIS-2082


On 08/10/2018 06:53 PM, Dan Langford wrote:

TLDR messages redelivered from artemis broker get into state where qpid jms
client api will not show me the properties or body. trying to determine if
its the broker sending down bad data or if its the client not supporting
some frame structure

I have a message on my broker right now (Artemis 2.6.2) its on a Queue
waiting to be delivered. I am connecting with Qpid Jms Client 0.35.0 and
the client is not revealing to me the properties or payload of the message.
below is my code. its using the simplified api we got in 2.0 (JmsContext)
to create a Consumer and the set a MessageListener. Then i do this on each
javax.jms.Message


for(Object name: Collections.list(message.getPropertyNames())) {
 System.out.printf("property name=%s value=%s%n", name,
message.getObjectProperty((String) name));
}
System.out.printf("message payload=%s%n", message.getBody(String.class));
System.out.println("done");


and here are the frames i am seeing due to env variable PN_TRACE_FRM=true
(with some data scrubbed like hostnames)


[199721506:0] -> Open{
containerId='ID:12eea5d0-97f3-47d4-8d5a-e59c37452c10:1', hostname='
stage.myhost.org', maxFrameSize=1048576, channelMax=32767,
idleTimeOut=3, outgoingLocales=null, incomingLocales=null,
offeredCapabilities=null,
desiredCapabilities=[sole-connection-for-container, DELAYED_DELIVERY,
ANONYMOUS-RELAY, SHARED-SUBS], properties={product=QpidJMS, version=0.35.0,
platform=JVM: 1.8.0_181, 25.181-b13, Oracle Corporation, OS: Mac OS X,
10.13.6, x86_64}}
[199721506:0] <- Open{ containerId='node1', hostname='null',
maxFrameSize=131072, channelMax=65535, idleTimeOut=3,
outgoingLocales=null, incomingLocales=null,
offeredCapabilities=[sole-connection-for-container, DELAYED_DELIVERY,
SHARED-SUBS, ANONYMOUS-RELAY], desiredCapabilities=null,
properties={product=apache-activemq-artemis,
failover-server-list=[{hostname=node1, scheme=amqp, port=61616,
network-host=node2}], version=2.6.2}}
[199721506:0] -> Begin{remoteChannel=null, nextOutgoingId=1,
incomingWindow=2047, outgoingWindow=2147483647, handleMax=65535,
offeredCapabilities=null, desiredCapabilities=null, properties=null}
[199721506:0] <- Begin{remoteChannel=0, nextOutgoingId=1,
incomingWindow=2147483647, outgoingWindow=2147483647, handleMax=65535,
offeredCapabilities=null, desiredCapabilities=null, properties=null}
[199721506:1] -> Begin{remoteChannel=null, nextOutgoingId=1,
incomingWindow=2047, outgoingWindow=2147483647, handleMax=65535,
offeredCapabilities=null, desiredCapabilities=null, properties=null}
[199721506:1] <- Begin{remoteChannel=1, nextOutgoingId=1,
incomingWindow=2147483647, outgoingWindow=2147483647, handleMax=65535,
offeredCapabilities=null, desiredCapabilities=null, properties=null}
[199721506:1] ->
Attach{name='qpid-jms:receiver:ID:36414498-1cef-45b7-9829-65adf6b870b4:1:1:1:QUE-134b55356db040f68dd2f51413c1895c',
handle=0, role=RECEIVER, sndSettleMode=UNSETTLED, rcvSettleMode=FIRST,
source=Source{address='QUE-134b55356db040f68dd2f51413c1895c', durable=NONE,
expiryPolicy=LINK_DETACH, timeout=0, dynamic=false,
dynamicNodeProperties=null, distributionMode=null, filter=null,
defaultOutcome=Modified{deliveryFailed=true, undeliverableHere=null,
messageAnnotations=null}, outcomes=[amqp:accepted:list, amqp:rejected:list,
amqp:released:list, amqp:modified:list], capabilities=[queue]},
target=Target{address='null', durable=NONE, expiryPolicy=SESSION_END,
timeout=0, dynamic=false, dynamicNodeProperties=null, capabilities=null},
unsettled=null, incompleteUnsettled=false, initialDeliveryCount=null,
maxMessageSize=null, offeredCapabilities=null, desiredCapabilities=null,
properties=null}
[199721506:1] <-
Attach{name='qpid-jms:receiver:ID:36414498-1cef-45b7-9829-65adf6b870b4:1:1:1:QUE-134b55356db040f68dd2f51413c1895c',
handle=0, role=SENDER, sndSettleMode=UNSETTLED, rcvSettleMode=FIRST,
source=Source{address='QUE-134b55356db040f68dd2f51413c1895c', durable=NONE,
expiryPolicy=LINK_DETACH, timeout=0, dynamic=false,
dynamicNodeProperties=null, distributionMode=null, filter=null,
defaultOutcome=Modified{deliveryFailed=true, undeliverableHere=null,
messageAnnotations=null}, outcomes=[amqp:accepted:list, amqp:rejected:list,
amqp:released:list, amqp:modified:list], capabilities=[queue]},
target=Target{address='null', durable=NONE, expiryPolicy=SESSION_END,
timeout=0, dynamic=false, dynamicNodeProperties=null, capabilities=null},
unsettled=null, incompleteUnsettled=false, initialDeliveryCount=0,
maxMessageSize=null, offeredCapabilities=null, desiredCapabilities=null,
properties=null}
[199721506:1] -> Flow{nextIncomingId=1, incomingWindow=2047,
nextOutgoingId=1, outgoingWindow=2147483647, handle=0, deliveryCount=0,
linkCredit=1, available=null, drain=false, echo=false, properties=null}
[199721506:1] <- Transfer{handle=0, 

Re: [VOTE] Release Apache Qpid JMS 0.41.0

[Timothy Bish]

On 4/3/19 1:17 PM, Robbie Gemmell wrote:

Hi folks,

I have put together a spin for a 0.41.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.41.0-rc1/

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

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

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

The dependency for the client itself would then be:

   
 org.apache.qpid
 qpid-jms-client
 0.41.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
* Verified archives contained license and notice files
* Checked source files for license headers using 'mvn apache-rat:check'
* Built from source and ran all tests.
* Built ActiveMQ 5 master using staged bits and ran all AMQP tests
* Built ActiveMQ Artemis master using staged bits and ran the AMQP 
integration 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.32.0

[Timothy Bish]

On 3/27/19 10:28 AM, Robbie Gemmell wrote:

Hi folks,

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

The files can be grabbed from:
https://dist.apache.org/repos/dist/dev/qpid/proton-j/0.32.0-rc1/

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

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

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

The dependency for proton-j would then be:

   
 org.apache.qpid
 proton-j
 0.32.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 archives
* Checked source for license headers using 'mvn apache-rat:check'
* Built from source and ran the test suite
* Built Qpid JMS using the staged artifacts and ran the tests
* Built ActiveMQ master using the staged artifacts and run the tests
* Built ActiveMQ Artemis master using the staged artifacts and run the 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.27.0

[Timothy Bish]

On 2/6/19 9:01 AM, Robbie Gemmell wrote:

Hi folks,

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

The files can be grabbed from:
https://dist.apache.org/repos/dist/dev/qpid/proton/0.27.0-rc1/

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

It is tagged as 0.27.0-rc1.

Regards,
Robbie

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



+1

* Verified the signature and checksum files.
* Checked for LICENCE and NOTICE files in the archive.
* Built the library on Mint 19 and ran the test suite.
* Ran some of the examples against an Artemis broker.

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

[Timothy Bish]

On 4/15/19 1:42 PM, Robbie Gemmell wrote:

Hi folks,

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

The files can be grabbed from:
https://dist.apache.org/repos/dist/dev/qpid/proton/0.27.1-rc1/

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

It is tagged as 0.27.1-rc1.

Regards,
Robbie

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



+1
* Built from source and ran the tests
* Verified signature and checksums
* Ran some C++ examples against a running Artemis broker


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

[Timothy Bish]

On 6/4/19 8:08 AM, Robbie Gemmell wrote:

Hi folks,

I have put together a spin for a 0.43.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.43.0-rc1/

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

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

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

The dependency for the client itself would then be:

   
 org.apache.qpid
 qpid-jms-client
 0.43.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
* Built from source and ran all tests
* Checked for source licenses using 'mvn apache-rat:check'
* Built ActiveMQ 5.x master using staged files and ran the AMQP tests
* Built ActiveMQ Artemis master using staged files and ran the AMQP tests
* Built the example application and ran it against an Artemis build that 
used the older proton-j library as well as the new one.


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

[Timothy Bish]

On 5/30/19 2:02 PM, Robbie Gemmell wrote:

Hi folks,

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

The files can be grabbed from:
https://dist.apache.org/repos/dist/dev/qpid/proton-j/0.33.1-rc1/

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

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

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

The dependency for proton-j would then be:

   
 org.apache.qpid
 proton-j
 0.33.1
   

-
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 test suite
* Checked source for license headers using 'mvn apache-rat:check'
* Built Qpid JMS master using staged artifacts and ran the tests
* Built ActiveMQ 5.x master using staged artifacts and ran the AMQP tests
* Built ActiveMQ Artemis master 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: Better way to handle 'MessageNotWriteableException: Message is currently read-only'

[Timothy Bish]

On 5/13/19 8:32 AM, akabhishek1 wrote:

Hi Team,

ServiceBus forcefully disconnect producer for 10m idle timeout. We are
handling this situation with below code snippet ("//***Code At Time Of
Error***"), but we are getting strange error
"javax.jms.MessageNotWriteableException: Message is currently read-only".
This is a very rare error, and we haven't received this error from one year.


There is a bug in the client that is causing this to happen when sending 
to a connection that has already dropped before you get round to 
sending, it is fixed now in QPIDJMS-457 and will be in the next release.


https://issues.apache.org/jira/browse/QPIDJMS-457



We are not not able to reproduce this issue as well. However, we came to
conclusion that copy of message to origionalJmsMessage "final Message
origionalJmsMessage = message", that could be issue. Because i am copying
"message" via reference instead of value.

So i changed the logic to copy value by "Message origionalJmsMessage =
(org.apache.qpid.jms.message.JmsMessage)message).copy();"

I am not sure, this approach is bullet proof or not.

Could you please suggest your opinion to preserve JMS message in a better
way and send again for handling idle timeout of the producer.

//Artifact Version
qpid-jms-client - 0.40.0
Broker - Azure ServiceBus
Java - JBK8
OS - Linux

//***Code At Time Of Error***
final Message origionalJmsMessage = message; // message = javax.jms.Message
try {
sendMessage(message);
} catch (IllegalStateException illegalStateException) {
// Reset Producer due to Idle TimeOut after 10m
resetProducer();
sendMessage(origionalJmsMessage);
}   


//**Code After Correction***
Message origionalJmsMessage;
try {
sendMessage(message); // message = javax.jms.Message
} catch (IllegalStateException illegalStateException) {
// Reset Producer due to Idle TimeOut after 10m
resetProducer();
origionalJmsMessage =
((org.apache.qpid.jms.message.JmsMessage)message).copy();
sendMessage(origionalJmsMessage);
}   

//***Exception Stack Trace***
Caused by: javax.jms.MessageNotWriteableException: Message is currently
read-only
org.apache.qpid.jms.message.JmsMessage.checkReadOnly(JmsMessage.java:509)
org.apache.qpid.jms.message.JmsMessage.setJMSDeliveryMode(JmsMessage.java:242)
org.apache.qpid.jms.JmsSession.send(JmsSession.java:817)
org.apache.qpid.jms.JmsSession.send(JmsSession.java:811)
org.apache.qpid.jms.JmsMessageProducer.sendMessage(JmsMessageProducer.java:252)
org.apache.qpid.jms.JmsMessageProducer.send(JmsMessageProducer.java:182)


Regards,
Abhishek Kumar



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

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




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

[Timothy Bish]

On 5/1/19 2:36 PM, Robbie Gemmell wrote:

Hi folks,

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

The files can be grabbed from:
https://dist.apache.org/repos/dist/dev/qpid/proton-j/0.33.0-rc1/

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

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

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

The dependency for proton-j would then be:

   
 org.apache.qpid
 proton-j
 0.33.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
* Checked source license headers using 'mvn apache-rat:check'
* Built from source and ran the tests
* Built Qpid-JMS master using the staged artifact and ran the tests
* Built ActiveMQ master using the staged artifact and ran the AMQP tests
* Built ActiveMQ Artemis master using the staged artifact 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 JMS 0.42.0

[Timothy Bish]

On 5/7/19 1:38 PM, Robbie Gemmell wrote:

Hi folks,

I have put together a spin for a 0.42.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.42.0-rc1/

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

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

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

The dependency for the client itself would then be:

   
 org.apache.qpid
 qpid-jms-client
 0.42.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
* Checked source licenses with 'mvn apache-rat:check'
* Built from source and ran all tests
* Built ActiveMQ 5.x master and ran the AMQP tests using staged artifacts
* Built ActiveMQ Artemis master and ran the AMQP tests using staged 
artifacts



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

[Timothy Bish]

On 5/7/19 11:54 AM, Robbie Gemmell wrote:

Hi folks,

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

The files can be grabbed from:
https://dist.apache.org/repos/dist/dev/qpid/proton/0.28.0-rc1/

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

It is tagged as 0.28.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
* Build from source and ran the test suite
* Ran some examples against an ActiveMQ Artemis master broker build.


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

[Timothy Bish]

On 6/28/19 2:01 PM, Robbie Gemmell wrote:

Hi folks,

I have put together a spin for a 0.44.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.44.0-rc1/

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

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

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

The dependency for the client itself would then be:

   
 org.apache.qpid
 qpid-jms-client
 0.44.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 archives
* Checked source for license headers with 'mvn apache-rat:check'
* Built from source and ran all tests
* Built ActiveMQ 5 with staged artifacts and ran all AMQP tests.
* Built ActiveMQ Artemis with staged artifacts and ran the AMQP test suite
* Ran the example from the client against a running Artemis broker install.


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

[Timothy Bish]

On 8/13/19 11:14 AM, Robbie Gemmell wrote:

Hi folks,

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

The files can be grabbed from:
https://dist.apache.org/repos/dist/dev/qpid/proton/0.29.0-rc1/

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

It is tagged as 0.29.0-rc1.

Regards,
Robbie

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



+1

* Verified license and notice files
* Verified signatures and checksums
* Built from source and ran the tests
* Ran some of the examples against an Artemis broker instance.

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

[Timothy Bish]

On 8/21/19 12:16 PM, Robbie Gemmell wrote:

On Wed, 21 Aug 2019 at 16:28, Robbie Gemmell  wrote:

Hi folks,

I have put together a spin for a 0.45.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.45.0-rc1/

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

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

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

The dependency for the client itself would then be:

   
 org.apache.qpid
 qpid-jms-client
 0.45.0
   

+1

I checked things out as follows:
- Verified the signature and checksum files.
- Checked for LICENCE and NOTICE files in the archives.
- Ran "mvn apache-rat:check" to check source archive licence headers.
- Ran the source build and tests on JDK8 + JDK11 (plus 12+13EA in CI).
- Built Qpid Broker-J 7.1.x using the staged bits and ran the systests.
- Built ActiveMQ 5.15.x and Artemis master using staged bits, ran AMQP tests.
- Built the HelloWorld example from the binary archive using staged bits.
- Ran it against Qpid Dispatch 1.8.0, Broker-J 7.1.4, and C++ 1.39.0 broker.

Robbie

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




+1


* Verified signatures and checksums
* Verified Licensee and Notice files in archives
* Used rat check to verify license headers in source files
* Built ActiveMQ 5 master and ran tests using staged artifacts
* Built ActiveMQ Artemis master and ran tests using staged artifacts
* Built from source archive and ran all tests.



--
Tim Bish


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

Re: Need help to fix "javax.jms.MessageNotReadableException: Message body is write-only"

[Timothy Bish]

On 8/29/19 5:04 AM, A K wrote:


Hi Timothy And Team,

I posted below details through web ui 
http://qpid.2158936.n2.nabble.com/Apache-Qpid-users-f2158936.html  but 
latest comment and new topic is not reflecting on UI. I think, there 
is some issue on UI.


###


We are having one issue, so need your to help to fix this issue.

As per your suggestion on issue - 
http://qpid.2158936.n2.nabble.com/Better-way-to-handle-MessageNotWriteableException-Message-is-currently-read-only-td7684002.html,


i am creating JMSMessage again whenever producer failed to send message.

For achieving this scenario, i need to extract(read) message content 
from original JMS message. While extracting message content for 
JmsBytesMessage/JmsStreamMessage,  i am getting error 
"javax.jms.MessageNotReadableException: Message body is write-only".


The information provided isn't enough to come to any conclusion on what 
may be going on with the state of the message.  I'd suggest gathering 
some logging and AMQP frame traces when you reproduce this to aid in 
seeing what the client is doing and what the conditions are that cause 
the message to not be in a readable state.  See the logging docs: 
http://qpid.apache.org/releases/qpid-jms-0.45.0/docs/index.html#logging


You could also try and create a simple reproducer using the existing 
client unit tests as a model.  There was a test case added for 
QPIDJMS-457 that covered the scenario in that issue where the message 
was not restored to readable.


https://github.com/apache/qpid-jms/blob/master/qpid-jms-client/src/test/java/org/apache/qpid/jms/integration/ProducerIntegrationTest.java#L3124


I also did similar testing for JmsTextMessage, JmsMapMessage, 
JmsObjectMessage but there is no issue in these type of messages. We 
are having issue only for JmsStreamMessage and JmsBytesMessage.


I did testing with "qpid-jms-client-0.40.0", "qpid-jms-client-0.43.0" 
and "qpid-jms-client-0.45.0". Having same issue in all three of jars.


Please find attached error stack trace “JmsBytesMessage_Error.txt” and 
“JmsStreamMessage_Error.txt”.


How To reproduce this issue ? – I did testing with ServiceBus.
1. First send message to Queue
2. Disable Queue/topic
3. Enable Queue/topic
4. Send message again which will throw error 
“javax.jms.MessageNotReadableException: Message body is write-only”


Please find below code snippet for JmsBytesMessage

try {
sendMessage(message);
} catch (IllegalStateException illegalStateException) {
      // Reset Producer due to Idle TimeOut after 10m
resetProducer();

      Message recreatedMessage = reCreateMessage(message);
sendMessage(recreatedMessage);
}

Public Message reCreateMessage(Message message){
      byte[] content = getMessageContent(message);

      BytesMessage bMsg = session.createBytesMessage();
bMsg.writeBytes(content);

      return bMsg;
}

Public byte[] getMessageContent(Message message){
      BytesMessage message = (JmsBytesMessage)message;
      byte[] bytes = new byte[(int) message.getBodyLength()];
message.readBytes(bytes);
      return bytes;
}

Please let me know if you need any details.

Regards,
Abhishek Kumar


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



--
Tim Bish

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

[Timothy Bish]

On 8/9/19 12:04 PM, Robbie Gemmell wrote:

Hi folks,

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

The files can be grabbed from:
https://dist.apache.org/repos/dist/dev/qpid/proton-j/0.33.2-rc1/

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

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

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

The dependency for proton-j would then be:

   
 org.apache.qpid
 proton-j
 0.33.2
   

-
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
* Checked source for license headers using 'mvn apache-rat:check'
* Built from source and ran the tests
* Built Qpid JMS using staged artifacts and ran the test suites
* Built ActiveMQ 5.x master using staged artifacts and ran the AMQP test 
suites
* Built ActiveMQ Artemis master using staged artifacts and ran the AMQP 
integration tests



--
Tim Bish


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

Re: Log Level for client authentication errors

[Timothy Bish]

On 7/18/19 11:22 AM, Igor Natanzon wrote:

I noticed today that when Qpid client session fails to log in (due to an
invalid password), the log entry that's generated is at DEBUG level:

2019-07-18 11:00:32,262|DEBUG|FailoverProvider: async work
thread|o.a.q.j.JmsConnection|Async exception with no exception listener: {}
java.io.IOException: Client failed to authenticate using SASL: SCRAM-SHA-256
 at
org.apache.qpid.jms.util.IOExceptionSupport.create(IOExceptionSupport.java:45)
 at
org.apache.qpid.jms.provider.ProviderFuture.failOnError(ProviderFuture.java:118)

The only entry showing up at ERROR level is the following:
2019-07-18 10:45:33,649|ERROR|FailoverProvider: async work
thread|o.a.q.j.p.f.FailoverProvider|Failed to connect after: 1 attempt(s)

So if log level is set to WARN or ERROR, the reason for connectivity
failure is not recorded.

Can that be changed, or is there a reason for it to be in Debug level?

Thanks!

Given this is a security exception I'd assume your client failed at 
Connection.start() or if you had more than one host configured for 
failover the Connection would have signaled you with a onException would 
you have had an ExceptionListener registered which would give you 
suitable information for your application to log the stoppage reason.


When using the Failover mechanism it is assumed that failures will 
happen and folks tend to complain in the opposite when the full details 
of each reconnect attempt get logged as the expectation is that the 
client is going to recover on its own. While we could possibly add more 
logging for a full stoppage, you should have had all the details 
contained in the JMSSecurityException that the JMS layer would have 
provided you.




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

[Timothy Bish]

On 12/6/19 12:39 PM, Robbie Gemmell wrote:

Hi folks,

I have put together a spin for a 0.48.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.48.0-rc1/

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

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

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

The dependency for the client itself would then be:

   
 org.apache.qpid
 qpid-jms-client
 0.48.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
* Checked source for license headers with 'mvn apache-rat:check'
* Built from source and ran all tests
* Built ActiveMQ 5.x and ran the AMQP tests
* Built ActiveMQ Artemis and ran the AMQP integration 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.33.3

[Timothy Bish]

On 12/3/19 1:23 PM, Robbie Gemmell wrote:

Hi folks,

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

The files can be grabbed from:
https://dist.apache.org/repos/dist/dev/qpid/proton-j/0.33.3-rc1/

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

The only JIRA assigned is:
https://issues.apache.org/jira/browse/PROTON-2142

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

The dependency for proton-j would then be:

   
 org.apache.qpid
 proton-j
 0.33.3
   

-
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
* Checked source for license headers using 'mvn apache-rat:check'
* Built from source and ran all tests
* Built Qpid JMS using staged artifacts and ran tests.
* Built ActiveMQ 5.x using staged artifacts and ran tests.
* Built ActiveMQ Artemis using staged artifacts and ran integration 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.30.0

[Timothy Bish]

On 12/9/19 10:59 AM, Robbie Gemmell wrote:

Hi folks,

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

The files can be grabbed from:
https://dist.apache.org/repos/dist/dev/qpid/proton/0.30.0-rc1/

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

It is tagged as 0.30.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 test suite.

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

[Timothy Bish]

On 11/1/19 8:37 AM, Robbie Gemmell wrote:

Hi folks,

I have put together a spin for a 0.47.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.47.0-rc1/

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

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

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

The dependency for the client itself would then be:

   
 org.apache.qpid
 qpid-jms-client
 0.47.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
* Verified License and Notice files in archives
* Checked source license headers using 'mvn apache-rat:check'
* Built from source and ran tests
* Built ActiveMQ 5 master using staged artifacts and ran AMQP tests
* Built ActiveMQ Artemis master using staged artifacts and ran 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 JMS 0.46.0

[Timothy Bish]

On 9/24/19 1:47 PM, Robbie Gemmell wrote:

Hi folks,

I have put together a spin for a 0.46.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.46.0-rc1/

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

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

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

The dependency for the client itself would then be:

   
 org.apache.qpid
 qpid-jms-client
 0.46.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 archives
* Checked source for license headers using Apache rat maven plugin
* Built from source and ran all tests
* Built ActiveMQ 5.x master using staged artifacts and ran the AMQP tests
* Built ActiveMQ Artemis master 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 JMS 0.49.0

[Timothy Bish]

On 2/24/20 6:35 AM, Robbie Gemmell wrote:

Hi folks,

I have put together a spin for a 0.49.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.49.0-rc1/

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

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

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

The dependency for the client itself would then be:

   
 org.apache.qpid
 qpid-jms-client
 0.49.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
* Verified presence of License and NOTICE files
* Built from source and ran the test suite
* Checked source license headers using 'mvn apache-rat:check'
* Built ActiveMQ 5.x master with staged artifacts and ran the AMQP tests
* Built ActiveMQ Artemis master with 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: Out Of Memory error - Qpid not releasing memory in failed to acknowledge scenario

[Timothy Bish]

On 2/7/20 7:16 AM, akabhishek1 wrote:

Hi Team,

We were doing testing of Qpid JMS client for failed scenario. We are
receiving message as client acknowledgment mode.

Scenario - Receive message but do not acknowledge the message.

Issue - Memory is not getting released by Qpid on failed Scenario


In client acknowledge mode it is your responsibility to acknowledge 
messages when they have been processed.  The mechanics of the JMS 
consumer and session in client ack mode require that messages be 
retained such that a call to session recover can replay the delivered 
but unacknowledged messages so we cannot just release them on delivery.


Your sample is just receiving forever without any error conditions being 
simulated or handled so the client will accumulate messages.  This is 
really just a misuse of the client, you can resolve it in the test by 
periodically calling acknowledge on an incoming message and all previous 
messages will be acknowledged and releases and you'd see heap usage 
decrease as a result.


You mention that you are trying to test failed scenarios but the code 
given doesn't seem to be expressing any sort of handling of same so you 
might want to evaluate what you are trying to accomplish a bit more and 
maybe ask for help here on that end.





We could have this scenario in prodcution. We received the message, but
failed to process that message, so there will no aknowledgment. As we are
acknowledging only one success scenario.

Please find attached sample TestQpidRcvOnly.java, Total_Memory.PNG,
Sampler_Per_Thread_Allocation.PNG, Out_Of_Memory_Error.log .

Steps to reproduce this issue -->

1. Provide Correct details of QUEUE_NAME, SBUS_NAME, USERNAME, USERNAME in
TestQpidRcvOnly class
2. Publish 20 message on QUEUE_NAME, from any utility
3. Start the TestQpidRcvOnly class and keep it running
4. Open JVisualVM and have a look on Heap memory
5. Wait for 20m, you can see memory consumption continously increasing
6. You can see Out Of Memory Error on exhaustion of defined Max heap Memory.
Could be 1hr depends on Max Size
7. You can have a look on Sampler--> Memory -->Per Thread Allocation, you
can observe that Qpid thread is consuming more that 98% memory.

Consumption is OK but it is not releasing the memory, which is the cause for
Out of Memory Error.

Using -- Java 8, Azure ServiceBus, Qpid-jms-client-0.48


Could you please take a look on this issue.

Regards,
Abhishek Kumar

Out_Of_Memory_Error.log

Sampler_Per_Thread_Allocation.PNG

TestQpidRcvOnly.txt

Total_Memory.PNG




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

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



--
Tim Bish


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

Re: Out Of Memory error - Qpid not releasing memory in failed to acknowledge scenario

[Timothy Bish]

On 2/7/20 11:57 AM, akabhishek1 wrote:

Hi Tim,

Thanks a lot for quick reply. Please find attached updated code. I am
intentionally throwing exception after receiving the message. We could face
this issue in production.

We have implemented reliability pattern, message should be acknowledge only
after successful transformation. Bussiness transformation/process could be
fail continously due to unavailability of service.

We are using *connection.createSession(false, 101)* , so only one message
will be acknowledged at a time not prior messages.


Client individual ack mode operates in fundamentally the same manner as 
Client Ack mode where failures due to exceptions in the asynchronous 
path must be handled by a call to session recover to replay the message 
and reprocess it, or close the session if you can't handle reprocessing 
of failed messages.  You can't just throw an exception in the async 
MessageListener onMessage handler and hope for the best here.





The given example is just to replicate Out of Memory error based on
bussiness scenario.

Please suggest, if i can do anything to avoid this error.

Don't throw exceptions from onMessage as the specification labels this a 
client programming error.




   TestQpidRcvOnly.txt




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

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



--
Tim Bish


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

Re: An imperative AMQP client API

[Timothy Bish]

As a follow on to the prototyping work Justin has done for python I wanted
to also point to the work Robbie and myself have been doing around an
imperative API based Java client.  This client follows the basic API
guidelines for a futures based client as outlined in the API specification :

http://www.ssorj.net/pumpjack/client/index.html

The Java based client is currently somewhat functional but has some gaps
yet to be worked out around credit handling and drain etc.  Some basic
examples are in place to show off the API implementation are in the Git
repository.  The current implementation is pretty up to date with the most
recent imperative API documentation changes.

The repository for the client is here:

   https://github.com/tabish121/AMQPerative

And a compressed set of samples for various API interaction is located here:


https://github.com/tabish121/AMQPerative/blob/master/amqperative-examples/src/main/java/org/messaginghub/amqperative/example/Samples.java

It is also important to note that the Java client uses an experimental
proton-j engine implementation that we've also been working on which is
built around a more reactive model using modern Java language features and
offers easier coupling to the I/O layer of choice.  The imperative client
is using Netty similar to the Qpid JMS client for its I/O.  If you want to
run the examples from the imperative API client you'd need to also build
and install the new proton-j engine library into you local maven
repository, the code can be checked out from Github here:

   https://github.com/tabish121/proton4j

The project names are not meant to be the final names just quick
placeholders to get something going, hopefully future discussion can work
out some more suitable naming for these should they gain traction.

On Mon, Jan 13, 2020 at 7:40 AM Justin Ross  wrote:

> Hi, everyone.  For a while now, some members of the Qpid community have
> been working on a new style of messaging API.  It now has a reasonable
> shape, and we want to share it and get your feedback.
>
> We currently offer either JMS or Proton's reactive API.  These certainly
> aren't going anywhere - they're important - but for some use cases, the
> absence of a high-level command-oriented API for AMQP messaging is a source
> of inconvenience.
>
> This inconvenience comes in two forms.  First, JMS is helpfully imperative
> (in part - it contains multitudes), but it doesn't expose some of the
> things you can do with AMQP.  And it can't reasonably expose those things,
> because that would break the contract of the JMS API.  Second, the Proton
> APIs, since they are reactive, make it harder to handle cases where you
> need to sequence the processing of events.
>
> The imperative client API we are talking about here uses modern language
> support for futures or coroutines.  Most of the API's operation is
> asynchronous, but you can easily introduce blocking where you need to.
>
> It's a client API only.  We think a comparably high-level server API would
> be its own dedicated thing, functioning more like Python Flask or JAX-RS.
> In any case, the Proton reactive API is already a good fit for writing
> servers.
>
> We have the outline of the API and some proof-of-concept implementations,
> but much remains to be done.  We anticipate that this work will ultimately
> become a sub-module of Proton, such as proton/client.
>
> The API spec:
> http://www.ssorj.net/pumpjack/client/index.html
>
> I've worked on the Python prototypes, so I'll share them here.  I did these
> some time ago, so they need updating for the latest API spec changes, but
> they serve to show how the API can use futures or coroutines.  (For Python,
> coroutines are the preferred approach.)
>
> Python prototype (future-based):
> https://github.com/ssorj/gambit/blob/futures/python/demo.py
> https://github.com/ssorj/gambit/blob/futures/python/gambit.py
>
> Python prototype (coroutine-based):
> https://github.com/ssorj/gambit/blob/asyncio2/python/demo.py
> https://github.com/ssorj/gambit/blob/asyncio2/python/gambit.py
>
> Some of the other folks who have done exploratory work will follow up on
> this thread to show what they've done.
>
> Some caveats: this is in early stages, and the API will change as we
> discuss it more.  There are also big outstanding pieces to look at, such as
> reconnect and failover, to name just one.
>
> Thanks for your time, and please let us know what you think.
>


-- 
--
Tim Bish

Re: [VOTE] Release Apache Qpid JMS 0.50.0

[Timothy Bish]

On 3/11/20 12:35 PM, Robbie Gemmell wrote:

Hi folks,

I have put together a spin for a 0.50.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.50.0-rc1/

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

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

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

The dependency for the client itself would then be:

   
 org.apache.qpid
 qpid-jms-client
 0.50.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
* Verified License and Notice files present
* Check source license header using 'mvn apache-rat:check'
* Built from source and ran all tests
* Built ActiveMQ 5.x master and ran AMQP tests
* Built ActiveMQ Artemis master and ran AMQP integration 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.51.0

[Timothy Bish]

On 4/21/20 11:01 AM, Robbie Gemmell wrote:

Hi folks,

I have put together a spin for a 0.51.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.51.0-rc1/

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

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

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

The dependency for the client itself would then be:

   
 org.apache.qpid
 qpid-jms-client
 0.51.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 archives for license and notice files
* Checked source using 'mvn apache-rat:check'
* Built from source and ran the tests
* Built ActiveMQ 5 master using staged artifacts and ran AMQP tests.
* Built ActiveMQ Artemis master using staged artifacts and ran AMQP 
integration 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.33.4

[Timothy Bish]

On 4/2/20 12:53 PM, Robbie Gemmell wrote:

Hi folks,

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

The files can be grabbed from:
https://dist.apache.org/repos/dist/dev/qpid/proton-j/0.33.4-rc1/

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

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

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

The dependency for proton-j would then be:

   
 org.apache.qpid
 proton-j
 0.33.4
   

-
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 archives
* Checked source for license headers with apache-rat
* Built from source and ran tests
* Built Qpid JMS using staged artifacts and ran all tests
* Built ActiveMQ 5 master using staged artifacts and ran the AMQP tests
* Built ActiveMQ Artemis master using staged artifacts and ran the AMQP 
tests

* Checked that new automatic module name was present in the jar


--
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.31.0 (RC2)

[Timothy Bish]

On 5/1/20 12:41 PM, Robbie Gemmell wrote:

Hi folks,

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

The files can be grabbed from:
https://dist.apache.org/repos/dist/dev/qpid/proton/0.31.0-rc2/

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

It is tagged as 0.31.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
* Verified license and notice files
* Built from source and ran the test suite


--
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.31.0 (RC3)

[Timothy Bish]

On 5/7/20 12:06 PM, Robbie Gemmell wrote:

Hi folks,

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

The files can be grabbed from:
https://dist.apache.org/repos/dist/dev/qpid/proton/0.31.0-rc3/

There is only one additional change in RC3:
https://issues.apache.org/jira/browse/PROTON-2211

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

It is tagged as 0.31.0-rc3.

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
* Verified license and notice files
* Built from source and ran the test suite

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

[Timothy Bish]

On 5/29/20 11:59 AM, Robbie Gemmell wrote:

Hi folks,

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

The files can be grabbed from:
https://dist.apache.org/repos/dist/dev/qpid/proton-j/0.33.5-rc1/

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

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

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

The dependency for proton-j would then be:

   
 org.apache.qpid
 proton-j
 0.33.5
   

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


+1

* Validated signatures and checksums
* Verified license and notice files in archives
* Checked source for license headers using Apache Rat Plugin
* Built Qpid JMS with staged library and ran the tests
* Built ActiveMQ 5 master with staged library and ran the tests
* Built ActiveMQ Artemis master with staged library and ran the 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.33.6

[Timothy Bish]

On 7/21/20 12:27 PM, Robbie Gemmell wrote:

Hi folks,

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

The files can be grabbed from:
https://dist.apache.org/repos/dist/dev/qpid/proton-j/0.33.6-rc1/

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

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

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

The dependency for proton-j would then be:

   
 org.apache.qpid
 proton-j
 0.33.6
   

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


+1

* Validated signatures and checksums
* Verified license and notice files present in archives
* Checked source licenses with Apache Rat maven plugin
* Built from source and ran test suite
* Built ActiveMQ 5.x and Artemis master with staged artifacts and ran 
AMQP tests

* Built Qpid JMS master with staged artifacts and ran the 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] AmqpTransferTagGenerator is causing duplicate delivery-tag errors

[Timothy Bish]

On 8/10/20 5:05 PM, Timo Naroska wrote:

Hi,

we're seeing sporadic cases in our JMS application where the 
AmqpTransferTagGenerator used inside JMS MessageProducer is sending duplicate 
delivery-tags. This leads to the producer being closed and unusable for any 
further operations.

Setup:
QPID-J 7.16 broker cluster of 3 using BDB HA replication
qpid jms client 0.53.0
org.messaginghub/pooled-jms connection pool 1.1.1

Our JMS clients are using the messaginghub JMS pool for connection management. 
We're also setting a 5 second timeout for send operations 
(org.apache.qpid.jms.JmsConnectionFactory#setSendTimeout). In case of send 
timeout we consider the broker temporarily offline and will retry the send 
later in our client code.

Having the JMS pool manage the connections, a send operation in the client is 
as follows:
- get a JMS connection from the pool
- create session and producer (these are cached by the pool implementation)
- send message
- close producer/session/connection (this close operation does *not* really 
close anything. the resources are simply released into the messaginghub JMS 
pool)

The promise of the JMS pool is to completely take care of the connection 
lifecycle and to provide some simple load balancing between connections.


Problem:
We're seeing sporadic cases where our client goes into an unrecoverable state 
after a send timeout. The observed symptoms are:
1. a message send fails due to timeout
2. subsequent send operation fails with the broker reporting:
 Delivery-tag '\x00' is used by another unsettled delivery. The 
delivery-tag MUST be unique amongst all deliveries that could be considered 
unsettled by either end of the link. [condition = amqp:illegal-state]
3. *all* subsequent send operations fail with:
 javax.jms.IllegalStateException: The MessageProducer is closed


It is not completely clear what causes the initial send timeout. We suppose some kind of 
network blip in either client<->broker communication or broker<->broker 
replication traffic. Having some send operations fail for such temporary blips is OK. Our 
system can handle that.
However, the worse issue is that the client (specifically the JMS 
MessageProducer) sends a duplicate delivery-tag to the broker and then gets 
shut down by the resulting amqp:illegat-state response.

Basically we would need to create a fresh MessageProducer. The problem is that 
we can't. The producer is managed by the JMS pool. Our code has no direct 
access to it and no way to create a new one. The JMS pool on the other hand has 
no way to know that the producer has gone bad. The JMS API provides no way to 
check validity of JMS objects. Therefore the pool also can't recycle the 
MessageProducer. Our client is then stuck with the closed producer, requiring 
an application restart.



I was able to reproduce and debug the behavior locally using a short send 
timeout and a TCP proxy (toxiproxy) to simulate erratic network latency. The 
problem can be tracked down to the AmqpTransferTagGenerator in the JMS client. 
This class generates the (supposedly unique) delivery-tags for each send 
operation.
By default it is using a pool of tags that get re-used. i.e when a message gets 
sent to the broker, the next free tag is retrieved from the pool and used as 
delivery-tag. Once the broker acknowledges the operation, that tag is put back 
in the pool. This seems to be an optimization to reduce memory allocations??

Problem: the tag is also returned to the pool when a send timeout occurs(!) 
even though there is no telling what caused the timeout.
In our case the broker is just slower than usual, but it is still processing 
the message.

Simplified steps:
1. client is about to send a message to the broker; AmqpTransferTagGenerator 
returns tag x00 from its pool
2. broker receives message with tag x00 and starts processing
3. network wonkiness causes the broker to take longer than usual
4. client runs into send timeout without an ACK from the broker; tag 0x00 is 
returned to AmqpTransferTagGenerator
5. subsequent message is about to be sent to the broker; 
AmqpTransferTagGenerator again returns tag x00 which was just returned to its 
pool
6. broker receives second message with tag x00 while *still* operating on the 
original message; returns amqp:illegal-state
7. client receives broker error. closes the JMS producer
8. messaginghub JMS pool has no way to tell the producer has gone bad and holds 
on to it forever...


Proposed change:

AmqpTransferTagGenerator has an option to disable the internal tag pool. In 
that mode a new tag is allocated for each operation and that seems to solve 
this issue. Currently there is no way to configure this externally though. To 
test this change, I had to modify the JMS client code locally and built a 
custom jar of it. It is a single line change when creating the 
AmqpTransferTagGenerator here:

Re: [VOTE] Release Apache Qpid JMS 0.54.0

[Timothy Bish]

On 8/13/20 9:42 AM, Robbie Gemmell wrote:

Hi folks,

I have put together a spin for a 0.54.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.54.0-rc1/

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

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

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

The dependency for the client itself would then be:

   
 org.apache.qpid
 qpid-jms-client
 0.54.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 archives for License and notice files
* Checked source using Apache rat check plugin
* Built from source and ran the test suite
* Built ActiveMQ 5 and Artemis master using staged artifacts and ran 
AMQP tests.




--
Tim Bish


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

Re: Feature request - increase visibility of JmsSession.checkClosed() method

[Timothy Bish]

On 7/2/20 11:37 AM, akabhishek1 wrote:

Hi Team,

We are using qpid library to publish/receive messages from ServiceBus.
Microsoft ServiceBus forcefully detach the connected session if session is
idle, same behavior for JMS connection as well.

Microsoft ServiceBus also has limitation that we can not create too much JMS
sessions and producers as well.

Due to this limitation, we have to use some sessions and producer to perform
all activities.

I looked on QPid class org.apache.qpid.jms.JmsSession, checkClosed()
internally used to check session status but this method is protected, so it
will be used in internal classes only.

I would like to request you - Can you please increase visibility(protected
to public) of checkClosed() method, so we can check session status as well
before performing any action.


The JMS resources all throw exceptions from the API methods if the 
resource is closed or the underlying connection is closed, your code 
should always be ready to handle such errors and react accordingly.  As 
well the JMS Connection provides the ExceptionListener to inform you of 
connection drops should the remote close the connection or the 
underlying connection be dropped for some reason so you can react to 
that as well.


There isn't any reason you need to be able to poll the session directly 
as you still need to react to errors thrown from the JMS API methods 
either at the Session level or at the MessageProducer or MessageConsumer 
level since they could fail at any time due to interruption.




This will be a great facility for ServiceBus use case. Please suggest your
opinion.

Regards,
Abhishek Kumar



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

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



--
Tim Bish


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

Re: Error while creating message - The Session was closed due to an unrecoverable error

[Timothy Bish]

On 7/2/20 12:39 PM, akabhishek1 wrote:

HI Team,

We are using qpid-jms-client-0.45.0 to publish/receive messages from
ServiceBus.

We are getting "The Session was closed due to an unrecoverable error" in our
several environments while creating JMS message with the help of Session.

We haven't received this type of error while creating JMS message from more
than 2 years. We are trying to find out the root cause of this issue.

We haven't got any clue for this issue. Please find below exception
stacktrace. Could you please take a look on stacktrace and suggest - what
could be the root cause for this issue?

Any suggestion will be great help. I tried to reproduce this issue but i
haven't got anyway to reproduce this issue. Please suggest if you have any
idea to reproduce this type of issue.

From the stack trace it looks like the remote closed the connection for 
some reason but didn't provide an AMQP Error Condition that the client 
could turn into a meaningful error message.  It would be helpful to 
capture an AMQP protocol trace and inspect the remote Close frame to see 
if any additional error information is provided within.




Exception StackTrace -

The Session was closed due to an unrecoverable error.
(javax.jms.IllegalStateException)
(org.mule.api.transformer.TransformerException)

org.apache.qpid.jms.provider.amqp.AmqpSupport.convertToNonFatalException(AmqpSupport.java:184)

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

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

org.apache.qpid.jms.provider.amqp.AmqpProvider.onData(AmqpProvider.java:850)

org.apache.qpid.jms.transports.netty.NettyTcpTransport$NettyTcpTransportHandler.channelRead0(NettyTcpTransport.java:542)

org.apache.qpid.jms.transports.netty.NettyTcpTransport$NettyTcpTransportHandler.channelRead0(NettyTcpTransport.java:535)

io.netty.channel.SimpleChannelInboundHandler.channelRead(SimpleChannelInboundHandler.java:105)

io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:374)

io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:360)

io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:352)
  io.netty.handler.ssl.SslHandler.unwrap(SslHandler.java:1475)
  io.netty.handler.ssl.SslHandler.decodeJdkCompatible(SslHandler.java:1224)
  io.netty.handler.ssl.SslHandler.decode(SslHandler.java:1271)

io.netty.handler.codec.ByteToMessageDecoder.decodeRemovalReentryProtection(ByteToMessageDecoder.java:505)

io.netty.handler.codec.ByteToMessageDecoder.callDecode(ByteToMessageDecoder.java:444)

io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:283)

io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:374)

io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:360)

io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:352)

io.netty.channel.DefaultChannelPipeline$HeadContext.channelRead(DefaultChannelPipeline.java:1421)

io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:374)

io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:360)

io.netty.channel.DefaultChannelPipeline.fireChannelRead(DefaultChannelPipeline.java:930)

io.netty.channel.epoll.AbstractEpollStreamChannel$EpollStreamUnsafe.epollInReady(AbstractEpollStreamChannel.java:794)
  io.netty.channel.epoll.EpollEventLoop.processReady(EpollEventLoop.java:424)
  io.netty.channel.epoll.EpollEventLoop.run(EpollEventLoop.java:326)

io.netty.util.concurrent.SingleThreadEventExecutor$5.run(SingleThreadEventExecutor.java:918)
  io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74)
  java.lang.Thread.run(Thread.java:745)
  


Regards,
Abhishek Kumar




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

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



--
Tim Bish


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

Re: Error while creating message - The Session was closed due to an unrecoverable error

[Timothy Bish]

On 7/9/20 8:41 AM, akabhishek1 wrote:

Hi Robbie,

Thanks a lot for your reply. In our application there are multiple
ServiceBus connection which serves for different endpoints. However we
didn't oberserve this issue for other endpoints but we observed this issue
for two endpoints. Yes you are are right multiple threads are envolved.

However i did testing with 0.52.0 (single thread) and i can see same
behaviour. Session.createTextMessage not throwing exception in the absence
of connection. I think, it should throw exception in the absence of
connection


As Robbie stated the create message methods will throw exceptions once 
the session state reflects the loss of connection (eventual consistency) 
and the follow on message send will throw if the create does not so 
there is no client issue here.  Your code needs to be ready to handle 
error for all of these cases as they can and do happen when connections 
drop.




Could you please check for this issue?
I am not sure this issue is related with our issue or not, but it could be
related, because session is not able to idetinfy correct connection status.

Please find below steps to reproduce
this issue and attached "TestQpidSendSessionRecoverableError.java".

Actual Behavior - Session successfully created text message in absence of
connection
Expected Behavior -  session.createTextMessage("Hello World") - should throw
exception in the absence of connection.

Steps to reproduce this issue -
1. Provide correct ServiceBus endpoint details
2. Add debug point at Line no 55  (before creating text message)
3. Start class in debug mode
5. Application should stop at debug point, and disable network
6. Click on resume button

We can see that, class successfully created text message instead of
connection exception. Please let us know your opinon.

TestQpidSendSessionRecoverableError.java


Regards,
Abhi



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

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



--
Tim Bish


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

Re: Apache Qpid Client with proxy setting

[Timothy Bish]

On 7/12/20 2:28 PM, vishnu pk wrote:

Hi Team,

Im using Qpid lib jars to establish a connection from a third party
application to AMQP Azure Service Bus. I'm looking for a property variable
for *PROXY *host settings but couldn't find one. May i know if there is a
way to use a proxy within Qpid Client property.

QPID JMS CLient Version :  Version: 0.52.0

Below are the current properties used for connection establishment.

connectionfactory.myFactoryLookup = amqps://<>.
servicebus.windows.net?jms.username=<>=<>
queue.QUEUE = <>

Appreciate your help!

Regards
Vishnu

You can use a proxy by supplying the client connection factory a Netty 
ProxyHandler that is configured for the type of proxy you intend to 
use.  Some sames are available in the tests for this feature here:


https://github.com/apache/qpid-jms/blob/master/qpid-jms-client/src/test/java/org/apache/qpid/jms/integration/ProxyIntegrationTest.java

You can also review the JIRA issue where this feature was added for more 
context:


https://issues.apache.org/jira/browse/QPIDJMS-441


--
Tim Bish

Re: Set Custom MessageID for duplicate message detection

[Timothy Bish]

On 6/26/20 1:19 PM, akabhishek1 wrote:

HI Team,

We are using ServiceBus Broker, and using qpid-jms-client-0.45.0 to publish
message. ServiceBus provides facility to 'ignore duplicate messages' with
the help of MessageID.

For achieving this requirement - We need to set JMS message ID while
publishing the message. At this moment, i have not found any way to set
custom messageID via qpid JMS client. I tried with below options but that
doesn't help.

JmsMessageProducer messageProducer = (JmsMessageProducer)
session.createProducer(destination);
messageProducer.setDisableMessageID(true);
TextMessage textMessage = session.createTextMessage("Hello World");
((AmqpJmsMessageFacade) ((JmsMessage)
textMessage).getFacade()).setMessageId("AKQWS:9d678sdfsdsds");


The JMSMessageID is set by the JMS provider. It cannot be set by the 
client as per the JMS specification. The JMS spec /does/ guarantee the 
uniqueness of the JMSMessageID. Section 3.4.3 of both the JMS 1.1 & 2 
specifications says the following in regards to this uniqueness quality.


"A |JMSMessageID| is a |String| value which should function as a unique 
key for identifying messages in a historical repository. The exact scope 
of uniqueness is provider defined. It should at least cover all messages 
for a specific installation of a provider where an installation is some 
connected set of message routers."


The specification also calls out that calling setJMSMessageID is 
reserved for provider use and that any user set value on an outgoing 
message will be lost as read from the JMS Message API documentation:


"This method is for use by JMS providers only to set this field when a 
message is sent. This message cannot be used by clients to configure the 
message ID. This method is public to allow a JMS provider to set this 
field when sending a message whose implementation is not its own."


Attempting to work around this quality is prevented by the normal 
functioning of the JMS MessageProducer implementation in the client 
which will manage the state of this field as per specification guidelines.


Qpid JMS does provide a means of providing your own Message ID via a 
policy object (JmsMessageIDPolicy) that can be set on the 
JmsConnectionFactory.


    CustomJmsMessageIDPolicy custom = new CustomJmsMessageIDPolicy();
    JmsConnectionFactory factory = new JmsConnectionFactory(uri);
    factory.setMessageIDPolicy(custom);

This is an advanced feature that requires care in its use and requires 
that you take ownership of any side effects caused by doing so.





I did testing with Microsoft JAVA SDK
(com.microsoft.azure:azure-servicebus:1.2.11), and i am able to achieve this
requirement via setting MessageID.

Could you please provide any way to set MessageID.

Regards,
Abhishek Kumar



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

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



--
Tim Bish

Re: [VOTE] Release Apache Qpid JMS 0.52.0

[Timothy Bish]

On 6/3/20 12:21 PM, Robbie Gemmell wrote:

Hi folks,

I have put together a spin for a 0.52.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.52.0-rc1/

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

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

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

The dependency for the client itself would then be:

   
 org.apache.qpid
 qpid-jms-client
 0.52.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
* Verified license and notice files present
* Built from source and ran the tests
* Built ActiveMQ 5 master with staged artifacts and ran the AMQP tests
* Built ActiveMQ Artemis master with 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 JMS 0.53.0

[Timothy Bish]

On 7/24/20 12:37 PM, Robbie Gemmell wrote:

Hi folks,

I have put together a spin for a 0.53.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.53.0-rc1/

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

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

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

The dependency for the client itself would then be:

   
 org.apache.qpid
 qpid-jms-client
 0.53.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
* Verified license and notice files in artifacts
* Checked source for license headers using Apache Rat plugin
* Built from source and ran the tests
* Built ActiveMQ 5.x and Artemis master branches with staged artifacts 
and ran all AMQP tests.



--
Tim Bish


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

Re: Customize message id

[Timothy Bish]

On 1/11/21 2:36 PM, jxz024000 wrote:

Hello,

I want to log the message id after sending each message. The message id will
be used to report ticket to Azure team for them to troubleshooting. My
project currently use Spring JmsTemplate as sender client. I first thought I
may be able to set it in the Message object used by JmsTemplate
(message.setJMSMessageID(some string here)). But when I debugged into the
qpid client. I found it always set it own produced message id in
JmsSession.send() method. Is there a good way I can override this behavior?


The JMS Specification defines how the MessageProducer is the responsible 
party in assigning the message id to the message when it is sent.  The 
Qpid JMS client does offer some minor customization of the type of 
message Id values it will send but does not provide a means of allowing 
a user defined message Id value in order to preserve JMS specification 
compliant behavior and AMQP compliant message ID types.


You should instead look to using a message property to carry and 
business application specific values as you have control of the property 
names and values (within the allowed JMS defined types).




Thanks,


 long messageSequence = producer.getNextMessageSequence();
 Object messageId = null;
 if (!disableMsgId) {
 messageId =
producer.getMessageIDBuilder().createMessageID(producer.getProducerId().toString(),
messageSequence);
 }




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

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



--
Tim Bish


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

Re: Disable prefetch and local message cache

[Timothy Bish]

On 1/6/21 3:37 PM, jxz024000 wrote:

Hello,

We are using qpid-jms-client 0.46.0 with Azure Service Bus. We use a poll
loop to receive and process messages. In Service Bus we have message lock
timeout default to 30 seconds. The message processing logic can vary in
time. Sometimes it can take more than much longer than 30 seconds to
complete. If prefetch is enabled (by default), it is possible the prefetched
message is unlocked on Service Bus side before the message is actually being
picked up by consumer. We would like to only receive one message when call
session.receive and no prefetch. In this case, we also don't need local
message buffer to hold the prefetched messages. Can we disable prefetch and
local message buffer? I checked the document here
https://qpid.apache.org/releases/qpid-jms-0.41.0/docs/index.html.
Should we just need to add the following to connection string?

jms.prefetchPolicy.all = 0
jms.receiveLocalOnly = false
jms.receiveNoWaitLocalOnly = false

amqps://xxx.servicebus.windows.net?amqp.idleTimeout=24000=0=false
= false=TLSv1.2


Setting a zero prefetch means that the client will request a message on 
each call to receive or if setting a MessageListener the client will 
request one at a time as it calls the onMessage and that method returns.







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

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



--
Tim Bish


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

An Imperative API AMQP client written in Java

[Timothy Bish]

Hi everyone, some time ago Justin Ross introduced the idea of an 
imperative messaging API that could be implemented in various languages 
and live alongside our existing AMQP clients like Qpid JMS and the 
various Proton-based reactive style clients that we offer.


The goals of the imperative API are to allow for development of clients 
that utilize modern language features to offer a mixture of asynchronous 
programming with options for blocking as needed within the application.  
These new clients would be client only implementations no server 
functionality is offered.


The Imperative API spec as previously introduced resides here:
http://www.ssorj.net/pumpjack/client/index.html

The previous mailing list thread introducing the imperative API can be 
found here:

http://mail-archives.apache.org/mod_mbox/qpid-users/202001.mbox/%3CCANVjZ_R31Hw4r9tWq6rDWNR6i-bJeyM9jKNbkRcWWOkbw%3DwBeA%40mail.gmail.com%3E

Here I am introducing an initial Java-based implementation of the 
proposal imperative API that uses Java Futures to back the asynchronous 
APIs allowing for blocking if needed but also for pipelined operation 
when desired.


Within this implementation I’ve provided support for things like the 
asynchronous sends and disposition tracking defined in the imperative 
API presently as well as support for transactions and large message 
streamed send and receive.  Future work remains around client 
reconnection and other possible API extensions.


As a reminder, the imperative API and this Java implementation remain 
subject to change.  We want to gather feedback from the community and 
make any important API changes that are called for.


The Java client code is located here for review:
https://github.com/tabish121/protonj2

A set of examples has been provided which should help in reviewing the 
basics of the new imperative API client, these are all located here:

https://github.com/tabish121/protonj2/tree/master/protonj2-client-examples/src/main/java/org/apache/qpid/protonj2/client/examples

The client is implemented atop a new AMQP protocol engine that is 
implemented as a more reactive or event based model than the existing 
proton-j engine which can hide some important details due to the 
temporal squashing that occurs in its state machine, that means some 
state changes can’t be discerned.  This new engine exists within a new 
set of Maven coordinates and Java packages which allows us to preserve 
and support the existing Java-based engine for the foreseeable future.  
The new engine is similarly subject to change.


--
Tim Bish

Re: [VOTE] Release Apache Qpid JMS 0.55.0

[Timothy Bish]

On Fri, Nov 20, 2020 at 12:34 PM Robbie Gemmell 
wrote:

> Hi folks,
>
> I have put together a spin for a 0.55.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.55.0-rc1/
>
> The maven artifacts are also staged for now at:
> https://repository.apache.org/content/repositories/orgapacheqpid-1210
>
> The JIRAs assigned are:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314524=12348681
>
> 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-1210
> 
> 
>   
>
> The dependency for the client itself would then be:
>
>   
> org.apache.qpid
> qpid-jms-client
> 0.55.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 archives for License and notice files
* Checked source using Apache rat check plugin
* Built from source and ran the test suite
* Built ActiveMQ 5 and Artemis master using staged artifacts and ran AMQP
tests.
* Ran Hello World example against Artemis broker
* Tested transaction fix using external reproducer and could not reproduce
any longer.

-- 
--
Tim Bish

Re: I'm using Qpid JMS 0.55.0 AMQP Java client and I'd like to compress the messages I'm sending

[Timothy Bish]

On 12/1/20 2:37 PM, KOELMAN Herbert wrote:

Hello,

I want to compress the messages I'm sending to ARTEMIS 2.15.0. The messages are 
roughly speaking 9MB big and are sent using a JMS TextMessage instance.

To do so I have created an instance of org.apache.qpid.jms.JmsConnectionFactory 
using this URL 
amqp://localhost:5672?messageCompressionThresholdSize=5000=true

JmsConnectionFactory qpidFactory = new 
JmsConnectionFactory("amqp://localhost:5672?messageCompressionThresholdSize=5000=true");
...

When I'm producing messages using this factory, the messages are not compressed.

Where did I go wrong ?

Cordialement

Herbert

Design and programming are human activities; forget that and all is lost.

Bjarne Stroustrup


The Qpid JMS client does not support any sort of message compression so 
I'm guessing you got those URI options from some Artemis Core (JMS) 
client documentation which explains why they don't produce any 
compressed output by the client.


Performing message compression from within a client is often bound to 
cause issues due to the need for every intermediary within the 
transmission chain that might need to touch the message to understand 
what kind of compression is used if any and how to decompress and then 
compress again depending on transformations etc.  Issues can arise for 
instance when crossing between the various protocol clients that might 
be consuming messages from the Artemis broker.


The best strategy here might be for you to use a BytesMessage as your 
means of sending they bytes that you compress yourself so that you can 
control the decompression on the receiving ends as needed.



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

[Timothy Bish]

On 12/14/20 12:11 PM, Robbie Gemmell wrote:

Hi folks,

I have put together a spin for a 0.56.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.56.0-rc1/

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

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

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

The dependency for the client itself would then be:

   
 org.apache.qpid
 qpid-jms-client
 0.56.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 archives
* Used 'mvn apache-rat:check' to verify source file license headers
* Built from source and ran all the client tests
* Built ActiveMQ 5 master using staged artifacts and ran the AMQP tests
* Built ActiveMQ Artemis master 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-J 0.33.8

[Timothy Bish]

On 11/13/20 1:30 PM, Robbie Gemmell wrote:

Hi folks,

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

The files can be grabbed from:
https://dist.apache.org/repos/dist/dev/qpid/proton-j/0.33.8-rc1/

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

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

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

The dependency for proton-j would then be:

   
 org.apache.qpid
 proton-j
 0.33.8
   

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


+1

* Validated signatures and checksums
* Verified license and notice files present in archives
* Checked source license using 'mvn apache-rat:check'
* Built from source and ran all tests
* Built Qpid JMS using staged artifacts and ran the tests
* Built ActiveMQ 5 master using staged artifacts and ran the tests
* Built ActiveMQ Artemis master using staged artifacts and ran the 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.33.7

[Timothy Bish]

On 10/26/20 2:49 PM, Robbie Gemmell wrote:

Hi folks,

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

The files can be grabbed from:
https://dist.apache.org/repos/dist/dev/qpid/proton-j/0.33.7-rc1/

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

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

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

The dependency for proton-j would then be:

   
 org.apache.qpid
 proton-j
 0.33.7
   

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


+1

* Validated signatures and checksums
* Verified license and notice files in archives
* Verified source license via 'mvn apache-rat:check'
* Built from source and ran the tests
* Built Qpid JMS using staged artifacts and ran the tests
* Built ActiveMQ 5.x using staged artifiacts and ran the tests.
* Built ActiveMQ Artemis using staged artifacts and ran the tests.


--
Tim Bish


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

Re: What can cause to forcefully close the JMS Session?

[Timothy Bish]

There isn't enough information here to really make a guess as to the 
root cause but likely ServiceBus is closing the resources for some 
reason such as exceeding some capacity restriction or idle period etc.  
This is something you'd need to investigate yourself via client and 
server logs as well as perhaps contacting the ServiceBus folks as we 
here aren't able to give you insights into that bit.


As usual collecting AMQP frame traces can help to determine when the 
session was closed and what the remote indicated in its error condition 
supplied at the time of closing (if any was offered).


On 1/27/21 6:57 AM, akabhishek1 wrote:

Hi Team,

We are using Qpid-JMS-Client-56.0 to publish/consume from ServiceBus.

We are getting "javax.jms.IllegalStateException - The MessageProducer is
closed"  error.

We reset the Producer whenever we got  "The MessageProducer is closed"
error. At this time, Producer and Session, both was closed. I am trying to
find out the reason for closed JMS Session.

Can you please guide us, What are the criteria can trigger to close the JMS
Session? So I can replicate with real enironment.

Regards,
Abhishek Kumar



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

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



--
Tim Bish


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

Re: [VOTE] Release Qpid Broker-J 8.0.5

[Timothy Bish]

+1

* Validated signatures and checksums
* Verified source licenses with maven rat plugin
* Built from source and ran tests
* Ram binary broker and did some quick tests

On Tue, Jun 15, 2021 at 8:00 AM Alex Rudyy  wrote:
>
> Hi folks,
>
> I built release artefacts for Qpid Broker-J version 8.0.5 RC1.
> Please, give them a test out and vote accordingly.
>
> The source and binary archives can be found at:
> https://dist.apache.org/repos/dist/dev/qpid/broker-j/8.0.5-rc1/
>
> The maven artifacts are also staged at:
> https://repository.apache.org/content/repositories/orgapacheqpid-1222/
>
> The new version brings a number of improvements and bug fixes.
> You can find the full list of JIRAs included into the release here:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310520=1234
>
> Kind Regards,
> Alex
>
> P.S. For testing of maven broker staging repo artefacts, please add
> into to your project pom the staging repo as below:
>
> 
> 
>   staging
>   
> https://repository.apache.org/content/repositories/orgapacheqpid-1222/
> 
> 
>
> -
> 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

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

Re: [VOTE] Release Qpid Dispatch Router 1.16.0 (RC1)

[Timothy Bish]

+1

* Validated signatures and checksums
* Verified license and notice files
* Built from source and ran tests
* Ran ProtonJ2 examples against the built router.

On 5/13/21 8:07 AM, Michael Goulish wrote:

+1

I ran 5 tests each of {1-router, 2-router} x {1 sender, 10 senders} -- i.e.
20 tests total -- sending 'hey' HTTP traffic through the router TCP adapter.

Performance was significantly better than code from 05 May 1.16.x branch,
and Nothing Blew Up.

Shippit.


On Wed, May 12, 2021 at 1:21 PM Robbie Gemmell 
wrote:


+1

I verified the new signature using your key from the KEYS file.
Testing of code as described before.

Robbie

On Wed, 12 May 2021 at 17:53, Ken Giusti  wrote:

Thanks for catching that Robbie.

Folks,

I've updated the qpid-dispatch-1.16.0.tar.gz.asc file with my new key on
the download link:
https://dist.apache.org/repos/dist/dev/qpid/dispatch/1.16.0-rc1/

To validate the signature please follow the instructions on the Downloads
page from the qpid.apache.org website:

https://qpid.apache.org/download.html#verify-what-you-download

The actual tar file (and associated sha512 integrity check) remains the
same.  No need to re-run tests on the code - it's unchanged.

Sorry for botching the signature,

On Wed, May 12, 2021 at 5:14 AM Robbie Gemmell 
Your GPG public key isnt in the KEYS file [1], or the generated group
[2] or individual [3] sig files files created based on the fingerprint
entries from id.apache.org.

It must be added to the KEYS file so people can use the sig file to
verify the release download.

For the other cases, it looks from
https://people.apache.org/keys/committer/ like you do have the key
fingerprint entered, but the process generating the page can't find it
yet. Could be that it isnt on the keyserver(s) it's looking at (where
have you added it?), or the server may not have been reachable when
tried, or maybe the fingerprint isnt entered quite as it wants (seems
ok), etc.

[1] https://downloads.apache.org/qpid/KEYS (source file at root of our
dist release area)
[2] https://people.apache.org/keys/group/qpid.asc
[3] https://people.apache.org/keys/committer/kgiusti.asc

On Mon, 10 May 2021 at 17:54, Ken Giusti  wrote:

Hello All,


Please cast your vote on this thread to release RC1 as the official

Qpid

Dispatch Router version  1.16.0.



RC1 of Qpid Dispatch Router version 1.16.0 can be found here:



https://dist.apache.org/repos/dist/dev/qpid/dispatch/1.16.0-rc1/



The JIRAs assigned are:




https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315321=12348780



It is tagged as 1.16.0-rc1.



Thanks

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



--
-K

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




--
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 ProtonJ2 1.0.0-M1 (RC1)

[Timothy Bish]

On Wed, May 5, 2021 at 1:48 PM Timothy Bish  wrote:

> Hi folks,
>
> I have put together a release candidate for a 1.0.0-M1 Qpid ProtonJ2
> 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/protonj2/1.0.0-M1-rc1/
>
> The maven artifacts are also staged for now at:
> https://repository.apache.org/content/repositories/orgapacheqpid-1218
>
> Regards
>
> 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-1218
> 
>  
>
>
> The dependency for the client or the engine itself would then be:
>
>
>  org.apache.qpid
>  protonj2
>  1.0.0-M1
>
>
>  org.apache.qpid
>  protonj2-client
>  1.0.0-M1
>
>
>
> --
> Tim Bish
>
>

-- 
--
Tim Bish

Re: [VOTE] Release Apache Qpid ProtonJ2 1.0.0-M1 (RC1)

[Timothy Bish]

On 5/5/21 1:48 PM, Timothy Bish wrote:

Hi folks,

I have put together a release candidate for a 1.0.0-M1 Qpid ProtonJ2 
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/protonj2/1.0.0-M1-rc1/

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

Regards

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


    
  

The dependency for the client or the engine itself would then be:

  
    org.apache.qpid
    protonj2
    1.0.0-M1
  
  
    org.apache.qpid
    protonj2-client
    1.0.0-M1
  




+1

* Validated signatures and checksums
* Verified license and notice files in archives
* Checked for source license headers using 'mvn apache-rat:check'
* Built from source and ran the full test suite
* Built the client examples and ran against ActiveMQ 5, ActiveMQ Artemis 
and Dispatch




--
Tim Bish


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

[RESULT][VOTE] Release Apache Qpid ProtonJ2 1.0.0-M1

[Timothy Bish]

There were 3 binding +1 votes, and no other votes received. The vote has 
passed.


I will add the files to the dist release repo and release the maven
staging repo shortly. The website will be updated after the release
has had time to sync to the mirrors and maven central.

--
Tim Bish


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

[ANNOUNCE] Apache Qpid ProtonJ2 1.0.0-M1 released

[Timothy Bish]

The Apache Qpid (http://qpid.apache.org) community is pleased to
announce the immediate availability of Apache ProtonJ2 1.0.0-M1.

This is the first milestone release of our AMQP Java client supporting the
Advanced Message Queuing Protocol 1.0 (AMQP 1.0, ISO/IEC 19464,
http://www.amqp.org), based around the Apache Qpid ProtonJ2 protocol
engine also contained in this release.

The release is available now from our website:
http://qpid.apache.org/download.html

Binaries are also available via Maven Central:
http://qpid.apache.org/maven.html

Thanks to all involved,

--
Tim Bish


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

[RESULT][VOTE] Release Apache Qpid ProtonJ2 1.0.0-M2

[Timothy Bish]

There were 3 binding +1 votes, and no other votes received. The vote has 
passed.


I will add the files to the dist release repo and release the maven
staging repo shortly. The website will be updated after the release
has had time to sync to the mirrors and maven central.

--
Tim Bish


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

[ANNOUNCE] Apache Qpid ProtonJ2 1.0.0-M2 released

[Timothy Bish]

The Apache Qpid (http://qpid.apache.org) community is pleased to
announce the immediate availability of Apache ProtonJ2 1.0.0-M2.

This is the latest release of our AMQP Java client supporting the
Advanced Message Queuing Protocol 1.0 (AMQP 1.0, ISO/IEC 19464,
http://www.amqp.org), based around the Apache Qpid ProtonJ2 protocol
engine also contained in this release.

The release is available now from our website:
    http://qpid.apache.org/download.html

Binaries are also available via Maven Central:
    http://qpid.apache.org/maven.html

Release notes can be found at:
http://qpid.apache.org/releases/qpid-protonj2-1.0.0-M2/release-notes.html

Thanks to all involved,

--
Tim Bish


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

[VOTE] Release Apache Qpid ProtonJ2 1.0.0-M2

[Timothy Bish]

Hi folks,

I have put together a release candidate for a 1.0.0-M2 Qpid ProtonJ2 
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/protonj2/1.0.0-M2-rc1/

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

The JIRAs assigned are:
https://issues.apache.org/jira/projects/PROTON/versions/12350154

Regards

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

The dependency for the protocol engine or the client itself would then be:

  
    org.apache.qpid
    protonj2
    1.0.0-M2
  
  
    org.apache.qpid
    protonj2-client
    1.0.0-M2
  

--
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 ProtonJ2 1.0.0-M2

[Timothy Bish]

Bump

On 5/25/21 3:27 PM, Timothy Bish wrote:

Hi folks,

I have put together a release candidate for a 1.0.0-M2 Qpid ProtonJ2 
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/protonj2/1.0.0-M2-rc1/

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

The JIRAs assigned are:
https://issues.apache.org/jira/projects/PROTON/versions/12350154

Regards

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


    
  

The dependency for the protocol engine or the client itself would then 
be:


  
    org.apache.qpid
    protonj2
    1.0.0-M2
  
  
    org.apache.qpid
    protonj2-client
    1.0.0-M2
  



--
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 ProtonJ2 1.0.0-M2

[Timothy Bish]

On 5/25/21 3:27 PM, Timothy Bish wrote:

Hi folks,

I have put together a release candidate for a 1.0.0-M2 Qpid ProtonJ2 
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/protonj2/1.0.0-M2-rc1/

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

The JIRAs assigned are:
https://issues.apache.org/jira/projects/PROTON/versions/12350154

Regards

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


    
  

The dependency for the protocol engine or the client itself would then 
be:


  
    org.apache.qpid
    protonj2
    1.0.0-M2
  
  
    org.apache.qpid
    protonj2-client
    1.0.0-M2
  


+1

* Validated signatures and checksums
* Verified license and notice files in archives
* Checked source license headers using 'mvn apache-rat:check'
* Built from source and ran the tests
* Built upstream Quiver ProtonJ2 arrow using staged artifacts and ran 
tests against Dispatch and ActiveMQ Artemis
* Built examples and ran them against Dispatch 1.16.0, ActiveMQ 5 and 
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 JMS 1.1.0

[Timothy Bish]

On 7/5/21 12:18 PM, Robbie Gemmell wrote:

Hi folks,

I have put together a spin for a 1.1.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/1.1.0-rc1/

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

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

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

The dependency for the client itself would then be:

   
 org.apache.qpid
 qpid-jms-client
 1.1.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
* Verified license and notice files
* Checked source headers with 'mvn apche-rat:check'
* Built from source and ran the test suite
* Built ActiveMQ Artemis master 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 0.35.0

[Timothy Bish]

On 6/28/21 4:44 AM, Robbie Gemmell wrote:

On Fri, 25 Jun 2021 at 15:55, Robbie Gemmell  wrote:

Hi folks,

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

The files can be grabbed from:
https://dist.apache.org/repos/dist/dev/qpid/proton/0.35.0-rc1/

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

It is tagged as 0.35.0-rc1.

Regards,
Robbie

+1

I checked things over as follows:
- Verified the signature and checksum files.
- Checked for LICENCE and NOTICE files present in the archive.
- Ran the build and tests and installed.
- Built Qpid Dispatch main and 1.16.x branches against it and ran the tests.
- Ran Qpid JMS 1.0.0 HelloWorld example against the built router.

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
* Verified license and notice files in archive
* Built from source and ran the test suite.



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

[Timothy Bish]

On 5/19/21 12:44 PM, Robbie Gemmell wrote:

Hi folks,

I have put together a spin for a 0.59.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.59.0-rc1/


This path is invalid and looking around in dist I don't see the upload 
any place else.





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

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

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

The dependency for the client itself would then be:

   
 org.apache.qpid
 qpid-jms-client
 0.59.0
   

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



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

[Timothy Bish]

On 5/19/21 11:41 AM, Robbie Gemmell wrote:

Hi folks,

I have put together a spin for a 1.0.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/1.0.0-rc1/

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

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

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

The dependency for the client itself would then be:

   
 org.apache.qpid
 qpid-jms-client
 1.0.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
* Verified license and notice files
* Checked source license headers with 'mvn apache-rat:check'
* Built from source and ran the test suite on JDK 11 and 16
* Built ActiveMQ Artemis main with 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 JMS 0.59.0

[Timothy Bish]

On 5/19/21 12:44 PM, Robbie Gemmell wrote:

Hi folks,

I have put together a spin for a 0.59.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.59.0-rc1/

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

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

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

The dependency for the client itself would then be:

   
 org.apache.qpid
 qpid-jms-client
 0.59.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 license and notice files
* Verified source license headers with 'mvn apache-rat:check'
* Built from source and ran the tests
* Built ActiveMQ 5 using staged artifacts and ran the AMQP tests
* Built 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

Update on the Java based Imperative API AMQP client

[Timothy Bish]

Hi Everyone, after a fair bit more development and testing the Java 
based Imperative API AMQP client has reached a point where I'd like to 
start driving towards an initial tech preview release to hopefully get 
it into the hands of some users for some feedback and give us a chance 
to iron out issues not yet spotted in the current test suite.


To that end I've requested a new Git repository and merged the work 
there.  The Github mirror can be found at the link below:


   https://github.com/apache/qpid-protonj2

The new client and the accompanying new protocol engine have been placed 
under the org.apache.qpid.protonj2 namespace and the maven GAV would be 
as follows:


    
  org.apache.qpid
  protonj2
    
    
  org.apache.qpid
  protonj2-client
    

My current plan would be to continue with some final cleanup and testing 
of the release artifacts and polish up the documentation a bit and then 
propose an initial release with a version of 1.0.0-M1 indicating this is 
not a full fledged release yet and then drive towards a 1.0.0 after 
we've gotten some feedback.


I'd hope to start the release process the coming weeks if not sooner 
depending on feedback.


--
Tim Bish


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

[VOTE] Release Apache Qpid ProtonJ2 1.0.0-M1 (RC1)

[Timothy Bish]

Hi folks,

I have put together a release candidate for a 1.0.0-M1 Qpid ProtonJ2 
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/protonj2/1.0.0-M1-rc1/

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

Regards

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

The dependency for the client or the engine itself would then be:

  
    org.apache.qpid
    protonj2
    1.0.0-M1
  
  
    org.apache.qpid
    protonj2-client
    1.0.0-M1
  


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

[Timothy Bish]

On 4/6/21 12:48 PM, Robbie Gemmell wrote:

Hi folks,

I have put together a spin for a 0.58.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.58.0-rc1/

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

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

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

The dependency for the client itself would then be:

   
 org.apache.qpid
 qpid-jms-client
 0.58.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
* Verified archives contained license and notice files
* Checked source for license headers with maven rat plugin
* Built from source and ran the test suite
* Built ActiveMQ Artemis master using staged artifacts and ran the AMQP 
tests

* Built ActiveMQ 5.x master 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: [DISCUSS/NOTICE] Renaming default git repo branches to "main"

[Timothy Bish]

+1

On 3/11/21 7:21 AM, Robbie Gemmell wrote:

Hi folks,

I would like to propose renaming our git repository default branches
from "master" to "main" in keeping with general efforts to remove
offensive language, and also aligning with it being the default naming
approach on new repositories in various places for some time now.

Having looked into doing this my understanding is that we simply
create the new branches ourselves, start using them, and then ask
infra to reconfigure the repository default branch both here and at
GitHub. After that is done, we can then remove the old branches at our
own discretion.

Various updates could be needed as part of the process. Some CI jobs
and scripts etc could need to be updated, maybe some READMES etc,
there could be links that need updated, etc. I would take care of
creating the branches, requesting INFRA update the repo defaults, and
ensuring the CI builds and website are in order during/after the
change. Committers would need to update their checkouts accordingly.
Folks with their own CI jobs etc elsewhere may also need to make any
updates as appropriate.

Barring discussion otherwise, I would look to begin the process next
week on Wednesday 17th.

I would create branches in all our repositories and send a notice mail
that it had been done, such that committers then make the swap over
for pushing new work. I would then ask infra to make the repository
changes, and proceed with updates to CI jobs etc. Perhaps adjusting
the READMEs on master to make things more obvious for anyone looking
at the repositories while it is still the default and/or both branches
exist. After all is done, we can consider when/whether to remove the
old branches.

Robbie

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

.



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

[Timothy Bish]

On 3/15/21 1:29 PM, Robbie Gemmell wrote:

Hi folks,

I have put together a spin for a 0.57.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.57.0-rc1/

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

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

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

The dependency for the client itself would then be:

   
 org.apache.qpid
 qpid-jms-client
 0.57.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 all tests
* Built ActiveMQ 5 master using staged artifacts and ran the AMQP tests
* Built ActiveMQ Artemis master using staged artifacts and run the AMQP 
integration test suite



--
Tim Bish


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