Re: Failover

Hi all, Me and Robbie created the following draft of Failover Policy for Qpid Java Client. Could you please comment on it? Qpid Java Client Failover Policy 1. Qpid client failover basic principles. === When connection to broker is lost a Qpid

Re: Failover

Based on above, me and Robbie have chosen some of options of behaviour on failover and conducted a draft of Qpid Client Failover Behaviour Spec which is available from https://cwiki.apache.org/confluence/display/qpid/Client+Failover+Behaviour

Re: Failover

behaviour spec and tests before we get too far into implementation. Kind Regards, Alex On 23 September 2011 13:06, Oleksandr Rudyy oru...@gmail.com wrote: Based on above, me and Robbie have chosen some of options of behaviour on failover and conducted a draft of Qpid Client Failover Behaviour Spec

Re: Failover

Rajith, Thanks a lot for your feedback. Could you also have a look into the Failover Behaviour WIKI we created to summarize the failover behaviour? The discussion above gave us multiple options of failover behaviour. We selected the most appropriative behaviour options among many available and

Re: Review Request: QPID-3401 New class structure for address refactoring

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/2366/#review2589 --- There are a number of operations performed based on the Destination

Re: Address node type resolution issues

I completely agree with the suggested approach as it will completely remove the need to have a code which depends from the destination URL syntax. Kind Regards, Alex On 20 October 2011 11:05, Rob Godfrey rob.j.godf...@gmail.com wrote: Sorry for being a little late responding to this thread...

Review Request: QPID-3532 Fix the blocking of JMS operations when failover happens

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/2469/ --- Review request for qpid and rajith attapattu. Summary ---

ExecutionException is sent by cpp broker in response for queue.query command for a deleted queue

Hi, I would like to bring to your attention that java test org.apache.qpid.test.client.destination.AddressBasedDestinationTest.testDeleteOptions started to fail constantly against cpp broker. The test is written to test a queue deletion if a delete option is specified in address URL. It tests a

Re: ExecutionException is sent by cpp broker in response for queue.query command for a deleted queue

Thanks Gordon On 15 November 2011 09:54, Gordon Sim g...@redhat.com wrote: On 11/14/2011 08:25 PM, Oleksandr Rudyy wrote: Hi, I would like to bring to your attention that java test org.apache.qpid.test.client.destination.AddressBasedDestinationTest.testDeleteOptions started to fail

Re: [jira] [Commented] (QPID-3640) When releasing msgs, the JMS client should not mark msgs in the prefetch buffer as redelivered.

Hi Rajith, I assigned DLQ JIRA to Keith for review. Hopefully, he will commit it tomorrow in the morning (UK time). Kind Regards, Alex On 24 November 2011 19:16, Rajith Attapattu (Commented) (JIRA) j...@apache.org wrote:    [

Re: qpid Queue DLQ

Hi Rugene, With java broker you can create DLQ on creation your normal by specifying the following arguments: x-qpid-dlq-enabled = true x-qpid-maximum-delivery-count=max delivery count value Here is a java client example how to do it final MapString,Object arguments = new

Review Request: QPID-3911: Fix the deadlock occuring on concurrent invocation of MessageConsumer#close() and Session#rollback()

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/4546/ --- Review request for qpid, Robbie Gemmell, rajith attapattu, Keith Wall, and Rob

Re: 0.16 release update - proposed final RC is available

Hi Justin, I've run some tests against the Java Broker 0-16 RC3 and encountered no issues. Details of tests run: used java Drain/Spout examples to publish/receive messages to/from Java Broker. monitored queues using Java Broker Management Console. No issues found. Kind Regards, Alex

Re: Release artifacts (was: [VOTE] Release 0.16)

Justin, Robbie, I tested Java Broker, Java Client and Management Console artefacts. Everything worked fine for me. No issue is found. Details of the tests: Started Java Broker. Created test queue using Management Console and bound that queue to the direct exchange. Published test messages into

Re: Binding URL Options

Hi Rajith, Option reject_behaviour was introduced as part of work on implementing DLQ functionality in java broker. This is only 0-9-1 client setting and it is not needed for 0-10 client. By default, redelivered messages are not moved into DLQ after exceeding Maximum redelivery attempts (for

Re: Binding URL Options

assume this is passed as a queue-declare argument ? Regards, Rajith On Tue, May 15, 2012 at 4:30 AM, Oleksandr Rudyy oru...@gmail.com wrote: Hi Rajith, Option reject_behaviour was introduced as part of work on implementing DLQ  functionality in java broker. This is only 0-9-1 client setting

Re: Review Request: Fix for QPID-3575

(Session should be closed, (AMQSession?,?)session.isClosed()); Apart from adding the tests, I do not have any other commentaries about the suggested changes. - Oleksandr Rudyy On July 6, 2012, 12:39 a.m., rajith attapattu wrote

0.18 inclusion request

Hi Justin, Could you please consider inclusions of trunk commits http://svn.apache.org/viewvc?view=revisionrevision=1360120 and http://svn.apache.org/viewvc?view=revisionrevision=1360121 into 0.18 ? These 2 commits are low risk bug fixes and improvements for recently added into Java Broker REST

0.18 inclusion request

Hi Justin, Could you also consider inclusion of commit http://svn.apache.org/viewvc?rev=1361239view=rev which adds the support for HTTPS protocol into Java Broker REST interfaces and web management console? Kind Regards, Alex Rudyy

Re: Maven build?

Hi, I completely support Joseph's proposal to use maven as building system for j-poton module. Kind Regards, Alex - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail:

Re: 0.18 release update - RC1 is available

Hi Justin, I tested RC1 builds of Java Client, Java Broker, Management Console and could not find any issues with these builds. Test details: Using RC1 client successfully run Hello, Spout and Drains examples against Java and C++ Brokers (both RC1). Run RC1 build of Management Console against

Re: Maven build?

Hi, It looks for me that the structure of proton-j sub-project will be quite simple and will not require the creation of complicated building scripts similar to what we have in qpid java tree right now. I believe that we can have 2 building systems for proton-j at least on first stages of the

Re: Deadlock

Hi Eugene, What is the version of the client you are using? Is it 0.10 client? Kind Regards, Alex On 1 August 2012 11:47, eugene eugen.ra...@gmail.com wrote: Hello, We are having a DeadLock issue and it seems that this is the same bug as here:

Re: Deadlock

Hi Eugen, I am sorry for the late response. There is a good chance that the issue was fixed in QPID-3911 for 0.16 qpid client. However, I am afraid that you might run into other deadlocks by closing the consumer from MessageListener. I would avoid doing so. Do you have any test reproducing the

Re: Deadlock

Hi Eugene, I do apologize for making you waiting with the answer. I was quite busy with my current tasks and did not have time to look through the client in order to recollect the deadlock conditions. Regarding the deadlock scenario you have described, I believe that you are right. I cannot

Re: 0.18 release update - proposed final RC3

Hi Justin, I tested 0.18-rc3 builds of Java Broker, Java Client and JMX Management Console and could not find any issue with the builds. My tests included the following: - running spout, drain, hello examples with java client against the java broker - creating/deleting exchanges, bindings,

Re: Announcing new committers

Carl, Thank you very much. I am glad to join the team. Oleksandr (a.k.a. Alex) On 14 September 2012 18:13, Carl Trieloff cctriel...@redhat.com wrote: I'm Glad to announce that Darryl Pierce and Oleksandr Rudyy where nominated and have accepted committership for the qpid project. Please join

Re: Java broker proposal: move firewall rules into ACL file (QPID-4334)

Hi Phil, Existing firewall plugin denies/allows access to broker from network/host regardless virtual host. The suggested syntax implies that you can denies/allows access to the broker virtual hosts instead. Will it be possible to specify host name in the rule and restrict the access to the

Re: Please welcome Phil Harvey as committer

Welcome Phil! Alex - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org

Re: 0.20 release update - RC3 is out, C++ and proton problem

Hi Justin, I tested RC3 builds of java client and java broker by starting the broker and running hello, spout and drain examples. They ran successfully without any issue. Kind Regards, Alex On 18 December 2012 22:49, Justin Ross jr...@redhat.com wrote: Hi. Here's a new RC from revision

Re: [VOTE] Release 0.20

Hi, I successfully ran hello/drain/spout examples with 0.20 java client and broker. I did some smoke tests of java broker web and jmx management UI. No issue is found. +1 Kind Regards, Alex - To unsubscribe, e-mail:

Re: TransportConnection.createVMBroker(): what to use now in junit?

Hi, VM transport has been removed from the broker. In unit tests you can start broker like following: String qpidHome = System.getProperty(user.dir); String qpidWork = System.getProperty(java.io.tmpdir) + /qpid/work; String configPath = qpidHome + /qpid-config.xml; int port = getFreePort();

Re: [Java] Deadlock running Java tests

Hi Rob, I have not seen this issue. Also, I tried to reproduce the issue by running the BasicAuthRestTest in a cycle but could not reproduce it during 1 hour of running. I continue running the test. Could you please clarify what is the version of JVM you are using? Alex On 18 March 2013 12:19,

Re: [Java] Deadlock running Java tests

:24, Rob Godfrey rob.j.godf...@gmail.com wrote: Running jdk1.7.0_06. I've not seen it before either, and have not been able to reproduce. None of my local changes touch the areas being exercised, so I don't think it was down to them. Curious. -- Rob On 18 March 2013 18:09, Oleksandr Rudyy

Requests for inclusion into the 0.22

Hi Justin, I would like to request the inclusions into 0.22 release of the commits made for the following JIRAs: http://issues.apache.org/jira/browse/QPID-4671 https://issues.apache.org/jira/browse/QPID-4666 QPID-4671: commit: http://svn.apache.org/r1462162 It is a trivial fix adding a check

More requests for inclusion into 0.22 release

Hi Justin, Could you please approve the inclusion of the following into 0.22 release: JIRA: https://issues.apache.org/jira/browse/QPID-4696 Commit: http://svn.apache.org/r1464115 Description: Addresses the review comments for JIRA QPID-4661 commits (modifies broker attribute editing UI to group

Re: [C++] build failure on RHEL5

Hi, The cmake build fails with the same error: [ 22%] Building CXX object src/CMakeFiles/qpidcommon.dir/ qpid/sys/posix/Time.o cc1plus: warnings being treated as errors /home/f391718/workspace/qpid/qpid/cpp/src/qpid/sys/posix/Time.cpp: In function ‘std::istream qpid::sys::operator(std::istream,

Re: 0.22 release update - proposed final RC4

Hi Justin, I am wondering whether you have already cut RC5? If not, I would like to request the inclusion of changes made in revision http://svn.apache.org/r1485163 fixing QPID-4876. It is a one line change which does not effect core broker functionality but it could potentially save a lot of

Re: 0.22 release update - proposed final RC4

Justin, Thanks for approval. The fix (r1485163) was merged into 0.22 branch. Kind Regards, Alex On 22 May 2013 13:09, Oleksandr Rudyy oru...@gmail.com wrote: Hi Justin, I am wondering whether you have already cut RC5? If not, I would like to request the inclusion of changes made

Re: [VOTE] Release 0.22

Justin, I hope it is still not too late to request the inclusion into 0.22 of a minor fix for Windows batch script to start Java Broker ( http://svn.apache.org/r1485859 QPID-4881). We introduced new command line arguments requiring to pass an equal character as part of the argument but the

Re: [VOTE] Subversion to JIRA integration

QPID: Yes [X ] No [ ] PROTON: Yes [ X] No [ ] On 24 May 2013 12:03, Robbie Gemmell robbie.gemm...@gmail.com wrote: Hi all, As some of you will already know, a mail was sent to committers@a.oearlier outlining some of the newer services ASF infra offer that we may not know about. One in

Re: [VOTE] Release 0.22

script skills take a quick look at it? Justin On Thu, May 23, 2013 at 6:28 PM, Oleksandr Rudyy oru...@gmail.com wrote: Justin, I hope it is still not too late to request the inclusion into 0.22 of a minor fix for Windows batch script to start Java Broker ( http

Re: [VOTE] Create a QPIDJMS JIRA project

Yes [ X ] No [ ] On 28 May 2013 16:05, Robbie Gemmell robbie.gemm...@gmail.com wrote: Following recent discussions regarding a more component-focused structure, and beginning work on a Proton-based AMQP 1.0 JMS client, could everyone please vote on the following: Create a QPIDJMS JIRA

Re: [VOTE] Release 0.22 RC6 as 0.22 final

+1 On 26 May 2013 11:35, Justin Ross jr...@apache.org wrote: RC6 contains the proposed final bits for Qpid 0.22. If you favor making the RC6 bits into our official release, vote +1. If you have reason to believe RC6 is not ready for release, vote -1. Thanks! Justin

Re: [VOTE] Remove autotools build for C++ build

[X ] * When 0.25 opens after the 0.24 beta branch remove the C++ qpid autotools build infrastructure in favour of the cmake tools. * A heads up message to the user mailing list. * Add a release note to 0.24 to say it is the last release that will contain an autotools

Re: POLL: what to do with dev list

2. Keep the dev list but only for traffic not relevant to users of the code I am curious what that traffic might include? Developer polls, organization issues? What else? It looks like discussions about various aspects of implementation might be interesting for the end users. On 23 August 2013

Re: Welcome Pavel Moravec as a Qpid committer

Welcome Pavel! - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org

Re: Qpid java broker ACL

Hi Lalit, With Qpid Java Broker ACL you can restrict the access by IP/network to virtual hosts, for example ACL ALLOW guest ACCESS VIRTUALHOST name=default from_hostname=.*\.company1\.com,.*\.company1\.co\.uk ACL DENY messaging-users ACCESS VIRTUALHOST from_network=192.169.1.*,192.169.2.*

Re: connection refused error for a Java EE app with RabbitMQ broker, Qpid JMS client

Hi, Your specified a broker host as localhost in your connection URL. I suppose that your client application is not located on the same host as broker. Thus, the connection cannot be established and error is reported. You can replace the locahost with turtle.rmq.cloudamqp.com in your connection

Re: Trunk re-organisation

Keith, I agree it seems the good time to start changing project layout and introduce independent sub-projects. The proposed layout looks reasonable. Although, qpid-java sub-projects will be split later into more sub-projects. Apart from the ones you listed on wiki (java-broker and

Request for inclusion into 0.32

Justin, Could you please authorize an inclusion of the following into 0.32? QPID-6247: Updates to configuration files should maintain existing file permissions https://svn.apache.org/r1661162 https://svn.apache.org/r1661530 The commits above allow to preserve original configuration files

Re: Request for inclusion into 0.32

Justin, I would like to request an inclusion of QPID-6410( [Java Broker] Disambiguate the connection adapter name by adding a connection ID to the name) : https://svn.apache.org/r1661929 We ran into the issue this morning. If not fixed, there is a risk of a dead-lock on broker side caused by

Re: Trunk re-organisation

Hi, I am going to proceed with re-organizing of java source tree tomorrow. I created a page with possible steps to follow at [1]. Please, let me know if the sources move can impact anyone and it needs to be delayed. Kind Regards, Alex [1]

Re: Trunk re-organisation

Hi, I moved java source tree into top level [1] Additionally, I raised an infra request to create git mirror for java source tree [2]. Now, we need to decide how to change site generation scripts in order to publish java release artifacts like documentation, java related site pages, etc. Kind

Re: Trunk re-organisation

One thing that just occurred to me is that by moving the java dir its contents will no longer be available via the git mirrors as it currently is, so it would need to be requested for new mirrors at git.apache.org and GitHub. Hi Robbie, I am going to request a new git mirror for java source

Maven parent

Hi guys, We have a maven project in Qpid svn root [1]. At the moment it does not have much attention and care. Thus, it contains outdated information. Only Qpid java components depend on it at the moment. I am going to remove that dependency in qpid-java-6 and move some of useful parent pom

Question about PGP signing keys location for Qpid project

Hi all, Whilst performing release tasks for qpid java components of version 6.0.0 I realized that KEYS file [1] referred from Qpid download page [2] is actually not up to date. As far as I understood currently public PGP signing keys for qpid project are kept in [3]. I am not sure why download

Re: Question about PGP signing keys location for Qpid project

Robbie, Thanks for detailed explanation. I will append my key into KEYS file. Kind Regards, Alex On 2 December 2015 at 17:01, Robbie Gemmell <robbie.gemm...@gmail.com> wrote: > On 2 December 2015 at 16:20, Oleksandr Rudyy <oru...@gmail.com> wrote: >> Hi all, >> >>

[ANNOUNCE] Apache Qpid Java 6.0.3 released

The Apache Qpid community is pleased to announce the immediate availability of Apache Qpid Java 6.0.3. This release addresses CVE-2016-3094, CVE-2016-4432 vulnerabilities and incorporates a number of defect fixes and enhancements. The release is available now from our website:

Re: [Proposal] Roadmap for ending Java 7 support for the Java Broker and AMQP 0-x client

+1 to Robs suggestions On 11 February 2016 at 15:12, Rob Godfrey wrote: > All, > > about 2 years ago we discussed the roadmap for ending support for Java 6 > [1]. In April it will be one year since Oracle ceased public support for > Java 7. Towards the end of this year

[ANNOUNCE] Apache Qpid Java Broker and JMS Client for AMQP 0-8..0-10 version 6.0.1 is released

The Apache Qpid community is pleased to announce the immediate availability of version 6.0.1 for Apache Qpid Java Broker and JMS Client for AMQP 0-8...0-10. This release incorporates a number of defect fixes and enhancements. The release is available now from our website:

[ANNOUNCE] Apache Qpid Java 6.0.2 released

The Apache Qpid community is pleased to announce the immediate availability of Apache Qpid Java Components 6.0.2 This release incorporates a number of defect fixes and enhancement. The release is available now from our website: http://qpid.apache.org/download.html Binaries are also

Re: Apache Qpid Java naming concerns

Hi all, I believe I addressed the naming issue of Qpid java based components. In a number of commits under QPID-7341 [1] I changed the sources including documentation and Qpid site to use the following names when referring java based components: 'Apache Qpid for Java' or 'Qpid for Java' when

Re: [NOTICE] cpp and python subdirs of svn trunk have migrated to git repositories

Hi all, I updated configurations for jobs "Qpid-cpp-trunk-test" and "Qpid-Java-Cpp-Test" to get sources from new git repos. Lorenz did the same for job "Qpid-Python-Java-Test". The jobs are running and building. However, the failed tests on job "Qpid-cpp-trunk-test" do not mark the job as

Re: [NOTICE] cease commits to cpp and python subdirs of svn trunk, migrating to git

Hi, It looks like a number of commits is missed in git repo. I tried to compile cpp sources from https://git-wip-us.apache.org/repos/asf/qpid-cpp.git but compilation failed. The compilation errors are similar to the ones reported by Keith couple days ago. The fixes have been made as part of

Proton-c build failed with error: undefined reference to `proton::timestamp::now()'

Hi all, The proton-c build failed as part of jenkins job Qpid-Python-Java-Test [1] with the following error Linking CXX shared library libqpid-proton-cpp.so CMakeFiles/qpid-proton-cpp.dir/src/connector.cpp.o: In function `proton::connector::on_transport_closed(proton::proton_event&)':

Re: Proton-c build failed with error: undefined reference to `proton::timestamp::now()'

p-us.apache.org/repos/asf?p=qpid-proton.git;a=commit;h=44875208 > > Robbie > > On 16 September 2016 at 10:28, Oleksandr Rudyy <oru...@gmail.com> wrote: >> Hi all, >> The proton-c build failed as part of jenkins job Qpid-Python-Java-Test >> [1] with the following er

[VOTE] Release Qpid Java 6.0.5

Hi all, A release candidate for the next 6.0.5 release of the Qpid Java Components has been created. A number of important defect fixes and improvements have been made in this release. The list of changes can be found in Jira:

[ANNOUNCE] Apache Qpid for Java 6.1.0 released

The Apache Qpid community is pleased to announce the immediate availability of Apache Qpid for Java 6.1.0. The release brings with it the following headline changes: Management REST API is enhanced with new methods and features Query API is added allowing to search for attributes of Broker

[ANNOUNCE] Apache Qpid for Java 6.0.5 released

The Apache Qpid community is pleased to announce the immediate availability of Apache Qpid for Java 6.0.5. This release incorporates a number of defect fixes and enhancement. The release is available now from our website: http://qpid.apache.org/download.html Binaries are also available via

Re: Issue with prefetched messages not being released immediately on consumer close

Robbie, I raised JIRA https://issues.apache.org/jira/browse/QPIDJMS-231 for the issue Alex On 7 December 2016 at 17:50, Robbie Gemmell <robbie.gemm...@gmail.com> wrote: > On 7 December 2016 at 16:27, Oleksandr Rudyy <oru...@gmail.com> wrote: >> Hi , >> >> We

Closing connection whilst MessageListener in-flight delivery is in progress

Hi, Recently I noticed that new jms client can fail to acknowledge the message (with auto-ack delivery mode) which was in a process of delivery with MessageListener when Connection#close() is called from main application thread. The exception like the one below is delivered into

[ANNOUNCE] Apache Qpid for Java 6.1.1 released

The Apache Qpid community is pleased to announce the immediate availability of Apache Qpid for Java 6.1.1. This release addresses important defect fixes. The release is available now from our website: http://qpid.apache.org/download.html Binaries are also available via Maven Central:

[ANNOUNCE] Apache Qpid for Java 6.0.6 released

The Apache Qpid community is pleased to announce the immediate availability of Apache Qpid for Java 6.0.6. This release addresses important defect fixes. The release is available now from our website: http://qpid.apache.org/download.html Binaries are also available via Maven Central:

[CVE-2016-8741] Apache Qpid Broker for Java - Information Leakage

[CVE-2016-8741] Apache Qpid Broker for Java - Information Leakage Vendor: The Apache Software Foundation Versions Affected: Apache Qpid Broker for Java versions 6.0.1, 6.0.2, 6.0.3, 6.0.4, 6.0.5, and 6.1.0 Description: The Qpid Broker for Java can be configured to use

Issue with prefetched messages not being released immediately on consumer close

Hi , We were looking into failing system tests for AMQP 1.0 and discovered that transacted Consumer#close() does not release any prefetched messages immediately. It seems that transactions needs to be finished (committed/rolled back). As result, if another consumer is created before the

Support for Qpid cpp broker in java broker system tests

Hi everybody, The existing system tests for java broker can be run against cpp broker (with some exceptions for the tests relying on java broker REST API or java broker specific features). Is there an interest to continue support of cpp broker in java broker system tests? The reasons behind

[ANNOUNCE] Apache Qpid for Java 6.1.2 released

The Apache Qpid (http://qpid.apache.org) community is pleased to announce the immediate availability of Apache Qpid for Java 6.1.2. This release incorporates a number of defect fixes and enhancements in Qpid Broker for Java. The release is available now from our website:

Re: Support for Qpid cpp broker in java broker system tests

Regards, Alex On 20 March 2017 at 10:05, Oleksandr Rudyy <oru...@gmail.com> wrote: > Hi everybody, > > The existing system tests for java broker can be run against cpp > broker (with some exceptions for the tests relying on java broker REST > API or java bro

Re: Support for Qpid cpp broker in java broker system tests

ather than just the > broker? > > Robbie > > On 3 April 2017 at 12:28, Oleksandr Rudyy <oru...@gmail.com> wrote: > > Hi all, > > > > Since nobody sent any reply on my previous email I would like to re-ask > > again whether there is any interest in runn

[ANNOUNCE] Apache Qpid for Java 6.1.4 released

The Apache Qpid (https://qpid.apache.org) community is pleased to announce the immediate availability of Apache Qpid for Java 6.1.4. This release addresses defects and enhancements in Qpid Broker for Java (a.k.a. qpid-broker-j). The release is available now from our website:

[ANNOUNCE] Apache Qpid for Java 6.0.8 released

The Apache Qpid (https://qpid.apache.org) community is pleased to announce the immediate availability of Apache Qpid for Java 6.0.8. This release addresses defects and enhancements in Qpid Broker for Java (a.k.a. qpid-broker-j). The release is available now from our website:

Re: QPID 0.32 going out of memory

the jira but didnt got any resolution. > > Thanks > Akhil > > On Mon, Jun 19, 2017 at 1:47 PM, Oleksandr Rudyy <oru...@gmail.com> wrote: > > > Hi Akhil, > > > > The screenshots did not get through with your latest email. Could you > > please try

Re: QPID 0.32 going out of memory

we are using Log4j as appender and we have set the > > logging_level="info". Does changing it to only error will help? > > > > This is the present configuration : > > > > > > > > > > > > &g

Re: QPID 0.32 going out of memory

Hi Akhil, It seems attachments have been stripped off. Could you please resend them or raise a JIRA [1] and attach your screenshots to the JIRA? Kind Regards, Alex [1] https://issues.apache.org/jira/projects/QPID

Re: QPID 0.32 going out of memory

ached. > thanks > > Akhil > > On Sat, Jun 17, 2017 at 1:52 AM, Oleksandr Rudyy <oru...@gmail.com> wrote: > >> Hi Akhil, >> It seems attachments have been stripped off. Could you please resend them >> or raise a JIRA [1] and attach your screenshots

[ANNOUNCE] Apache Qpid Broker-J 7.0.0 released

The Apache Qpid (http://qpid.apache.org) community is pleased to announce the immediate availability of Apache Qpid Broker-J 7.0.0. Qpid Broker-J 7.0 brings the following major changes: * Improved AMQP 1.0 support * Support for AMQP JMS Mapping Version 1.0 WD09 * Support for JMS 2.0 shared

Re: InputStream in SSLUtil.java line 449

Hi Jesse, Thanks for letting us know about the defect. I fixed the defect as part of QPID-8213. Kind Regards, Alex [1] https://issues.apache.org/jira/browse/QPID-8213 On 27 June 2018 at 02:27, Jesse wrote: > Hello, > > I noticed that there may be an unclosed resource around line 449 of >

Re: [DISCUSS] Proposal to mark "Won't Fix" all open "JMS AMQP 0-x" JIRAs

Keith, Your suggestion looks reasonable to me. +1 from me. Kind Regards, Alex On 22 January 2018 at 22:27, Keith W wrote: > The JIRA component "JMS AMQP 0-x" corresponds to the old 0-8..0-10 > Qpid JMS Client. As development work on this component is ceased, I >

Re: [AMQP1.0] Intended use-case of transaction-error transaction-timeout

Hi Keith, I think that closing the connection is the simplest reasonable thing to do in order to fail early on transaction timeout. Though, I believe that the handling of transaction timeouts can be improved further by closing the link(s), where the timed out transactional work have been

Re: URGENT: missing links (was: [ANNOUNCE] Apache Qpid Broker-J versions 7.1.1 and 7.0.7 released)

Hi sebb, The Qpid download page only contains links to the highest versions of products developed as part of Qpid project. The highest released version for Qpid Broker-J is 7.1.1. Thus, the link to 7.1.1 is placed directly on the page. At the top of the page there is a link "current releases" [1]

Re: URGENT: missing links (was: [ANNOUNCE] Apache Qpid Broker-J versions 7.1.1 and 7.0.7 released)

20:23, Oleksandr Rudyy wrote: > > > > Hi sebb, > > > > The Qpid download page only contains links to the highest versions of > products developed as part of Qpid project. The highest released version > for Qpid Broker-J is 7.1.1. Thus, the link to 7.1.1 is placed direc

Re: Jakarta EE TCKs and compatibility logo

Hi Mark, I believe that Qpid Team members requested an access to TCK earlier in order to test compatibility of Qpid JMS clients with JMS specs. We added maven module [1] to run TCK tests against Qpid Broker-J. Though, TCK is not part of Qprid Broker-J project and it has to be provided

Re: o.a.q.s.m.p.ManagementException) - Unexpected Exception - Qpid 7.1.3

Hi Balanna, This warning is reported when someone is trying to save a dashboard under the same name as existing one. For example, you can clone the dashboard and try to save cloned one using the same name as original dashboard. It should not happen whilst browsing. Kind Regards, Alex On Mon, 15

[ANNOUNCE] Apache Qpid Broker-J 8.0.1 released

The Apache Qpid (http://qpid.apache.org) community is pleased to announce the immediate availability of Apache Qpid Broker-J 8.0.1. This is the latest release of pure java implementation of messaging broker supporting the Advanced Message Queuing Protocol 1.0 (AMQP 1.0, ISO/IEC 19464,

Re: [NOTICE] Jenkins CI server change, manual job migrations required

Hi Roobie, Thanks for the update. I will try to migrate Qpid Broker-J jobs over next week-end. Kind Regards, Alex On Fri, 24 Jul 2020 at 13:30, Robbie Gemmell wrote: > The Jenkins setup at https://builds.apache.org is being replaced, > including a server migration to a new Cloudbees hosted

Re: High Qpid Dequeue latency

Hi Ram, I think that achieving a low latency (<100ms) all time could be a tricky thing in a java broker. The full GC "stop the world" pauses can suspend message delivery for seconds if not more. Though, the JVM GC can be tuned to minimize a number of "stop the world" pauses and their duration

Feature 'publish is enabled in site .asf.yaml

Hi folks, As part of site changes for the Qpid Broker-J 8.0.5 release I added the section 'publish' into .asf.yaml in order to switch to new site publishing functionality. If required we can revert back to gitwcsub for publishing by removing the publish feature in .asf.yaml file. Kind Regards,

Re: Possibility of a Broker-J 8.0.6 release?

Hi Tom, I will try to build version 8.0.6 this week. You can track the release JIRA QPID-8561. Kind Regards, Alex On Tue, 17 Aug 2021 at 18:55, Tom Jordahl wrote: > > Hi Qpid folks, > > Would it be possible to release Broker-J 8.0.6 ? > > I need the resolution of