Re: More than configured consumers count

2023-01-11 Thread Ekta Awasthi 
I have also created a qpid ticket on QPID JIRA Board.

https://issues.apache.org/jira/browse/DISPATCH-2353

Ekta Awasthi,
Engineer, EAI Operations & Support | Office Depot, Inc.
6600 North Military Trail | Boca Raton, FL 33496-2434
Office: 561-438-3552 | Mobile: 206-966-5577 | 
ekta.awas...@officedepot.com

-- Tips for EAI Support Engagement --
-EAI Pre-Prod Support: Create requests on the following JIRA board EAI 
Operations 
Support
-EAI Production Support: Create requests via IT Service 
Desk self-service 
portal, instructions click 
here:
 EAI Support queue --> ODP - Enterprise Apps Integration Support
-As a reminder, the Service Availability Managers should be engaged for any 
service impacting issues, with a ***Page*** to 
naitavailabilitym...@officedepot.com
 or by initiating a MIRT


From: Ekta Awasthi 
Sent: Wednesday, January 11, 2023 1:35 PM
To: Ted Ross 
Cc: users@qpid.apache.org ; Ajit Tathawade (CompuCom) 
; Nilesh Khokale (Contractor) 
; EAIOpsSupport 
Subject: Re: More than configured consumers count

Hello Ted,

I agree with you, we can certainly try upgrading but since this issue is 
happening directly in PROD and so frequently, we need a quick solution to solve 
these issues. Any help/suggestions will be greatly appreciated.


Ekta Awasthi,

Engineer, EAI Operations & Support | Office Depot, Inc.
6600 North Military Trail | Boca Raton, FL 33496-2434
Office: 561-438-3552 | Mobile: 206-966-5577 | 
ekta.awas...@officedepot.com



-- Tips for EAI Support Engagement --

-EAI Pre-Prod Support: Create requests on the following JIRA board EAI 
Operations 
Support

-EAI Production Support: Create requests via IT Service 
Desk self-service 
portal, instructions click 
here:
 EAI Support queue --> ODP - Enterprise Apps Integration Support

-As a reminder, the Service Availability Managers should be engaged for any 
service impacting issues, with a ***Page*** to 
naitavailabilitym...@officedepot.com
 or by initiating a MIRT


From: Ted Ross 
Sent: Friday, January 6, 2023 3:37 PM
To: Ekta Awasthi 
Cc: users@qpid.apache.org ; Ajit Tathawade (CompuCom) 
; Nilesh Khokale (Contractor) 
; EAIOpsSupport 
Subject: Re: More than configured consumers count

[CAUTION: EXTERNAL SENDER]

Ekta,

One thing you should consider is to bring your Qpid Dispatch Router code up to 
the latest version.  You are running 1.16.0 which is pretty old.  Many bugs 
have been fixed since 1.16.0.

-Ted


On Tue, Jan 3, 2023 at 5:03 PM Ekta Awasthi 
mailto:ekta.awas...@theodpcorp.com>> wrote:
Hello Ted,

Regarding Are the od-broker-1-[ms] connections configured via connectors or 
listeners? ---> They are configured via connectors only below is an example.

#od-broker-1-m connector
connector{
name: od-broker-1-m
host: 
activemq-test-1.odprivatecloud.com
port: 61618
role: route-container
linkCapacity: 40
sslProfile: od-router-2-test-ssl-profile
verifyHostName: no  #Since we have cert/hostname mismatches
#saslMechanisms: PLAIN
}


Ekta Awasthi,


From: Ted Ross mailto:tr...@redhat.com>>
Sent: Tuesday, January 3, 2023 10:43 AM
To: Ekta Awasthi 
mailto:ekta.awas...@theodpcorp.com>>
Cc: users@qpid.apache.org 
mailto:users@qpid.apache.org>>; Ajit Tathawade 
(CompuCom) 
mailto:ajit.tathaw...@officedepot.com>>; Nilesh 
Khokale (Contractor) 
mailto:nilesh.khok...@officedepot.com>>; 
EAIOpsSupport 
mailto:eaiopssupp...@officedepot.com>>
Subject: Re: More than configured consumers count

[CAUTION: EXTERNAL SENDER]

Another question...

Are the od-broker-1-[ms] connections configured via connectors or listeners?

-Ted


On Tue, Jan 3, 2023 at 10:14 AM Ted Ross 
mailto:tr...@redhat.com>> wrote:
Happy New Year Ekta,

Are your micro-services message producers or consumers?

When you see the more-than-expected consumers in Hawtio, get the link status 
from the routers using "qdstat -l".  There _should_ be one link for each 
auto-link as long as the targeted broker is reachable.  Thi

Re: More than configured consumers count

2023-01-11 Thread Ekta Awasthi 
Hello Ted,

I agree with you, we can certainly try upgrading but since this issue is 
happening directly in PROD and so frequently, we need a quick solution to solve 
these issues. Any help/suggestions will be greatly appreciated.

Ekta Awasthi,
Engineer, EAI Operations & Support | Office Depot, Inc.
6600 North Military Trail | Boca Raton, FL 33496-2434
Office: 561-438-3552 | Mobile: 206-966-5577 | 
ekta.awas...@officedepot.com

-- Tips for EAI Support Engagement --
-EAI Pre-Prod Support: Create requests on the following JIRA board EAI 
Operations 
Support
-EAI Production Support: Create requests via IT Service 
Desk self-service 
portal, instructions click 
here:
 EAI Support queue --> ODP - Enterprise Apps Integration Support
-As a reminder, the Service Availability Managers should be engaged for any 
service impacting issues, with a ***Page*** to 
naitavailabilitym...@officedepot.com
 or by initiating a MIRT


From: Ted Ross 
Sent: Friday, January 6, 2023 3:37 PM
To: Ekta Awasthi 
Cc: users@qpid.apache.org ; Ajit Tathawade (CompuCom) 
; Nilesh Khokale (Contractor) 
; EAIOpsSupport 
Subject: Re: More than configured consumers count

[CAUTION: EXTERNAL SENDER]

Ekta,

One thing you should consider is to bring your Qpid Dispatch Router code up to 
the latest version.  You are running 1.16.0 which is pretty old.  Many bugs 
have been fixed since 1.16.0.

-Ted


On Tue, Jan 3, 2023 at 5:03 PM Ekta Awasthi 
mailto:ekta.awas...@theodpcorp.com>> wrote:
Hello Ted,

Regarding Are the od-broker-1-[ms] connections configured via connectors or 
listeners? ---> They are configured via connectors only below is an example.

#od-broker-1-m connector
connector{
name: od-broker-1-m
host: 
activemq-test-1.odprivatecloud.com
port: 61618
role: route-container
linkCapacity: 40
sslProfile: od-router-2-test-ssl-profile
verifyHostName: no  #Since we have cert/hostname mismatches
#saslMechanisms: PLAIN
}


Ekta Awasthi,


From: Ted Ross mailto:tr...@redhat.com>>
Sent: Tuesday, January 3, 2023 10:43 AM
To: Ekta Awasthi 
mailto:ekta.awas...@theodpcorp.com>>
Cc: users@qpid.apache.org 
mailto:users@qpid.apache.org>>; Ajit Tathawade 
(CompuCom) 
mailto:ajit.tathaw...@officedepot.com>>; Nilesh 
Khokale (Contractor) 
mailto:nilesh.khok...@officedepot.com>>; 
EAIOpsSupport 
mailto:eaiopssupp...@officedepot.com>>
Subject: Re: More than configured consumers count

[CAUTION: EXTERNAL SENDER]

Another question...

Are the od-broker-1-[ms] connections configured via connectors or listeners?

-Ted


On Tue, Jan 3, 2023 at 10:14 AM Ted Ross 
mailto:tr...@redhat.com>> wrote:
Happy New Year Ekta,

Are your micro-services message producers or consumers?

When you see the more-than-expected consumers in Hawtio, get the link status 
from the routers using "qdstat -l".  There _should_ be one link for each 
auto-link as long as the targeted broker is reachable.  This should provide 
some clue as to what is happening.

-Ted


On Tue, Jan 3, 2023 at 10:01 AM Ekta Awasthi 
mailto:ekta.awas...@theodpcorp.com>> wrote:
Hello Ted,

Thank you for your response.

We are using AutoLinks for our addresses. Below is an example of a autolink 
queue in qdrouterd.conf for one activemq broker pair. Thanks

address {
  prefix: test-queue
  waypoint: yes
}

autoLink {
  connection: od-broker-1-m
  addr: test-queue
  dir: in
}

autoLink {
  connection: od-broker-1-m
  addr: test-queue
  dir: out
}

autoLink {
  connection: od-broker-1-s
  addr: test-queue
  dir: in
}

autoLink {
  connection: od-broker-1-s
  addr: test-queue
  dir: out
}


Ekta Awasthi,


From: Ted Ross mailto:tr...@redhat.com>>
Sent: Tuesday, January 3, 2023 8:47 AM
To: users@qpid.apache.org 
mailto:users@qpid.apache.org>>
Cc: Ajit Tathawade (CompuCom) 
mailto:ajit.tathaw...@officedepot.com>>; Nilesh 
Khokale (Contractor) 
mailto:nilesh.khok...@officedepot.com>>; 
EAIOpsSupport 
mailto:eaiopssupp...@officedepot.com>>
Subject: Re: More than configured consumers count

[CAUTION: EXTERNAL SENDER]

Hi Etka,

Can you tell us how you have configured the qdrouters to act as consumers?  Are 
you using auto-links or are you using link-routed addresses?

-Ted


On Wed, Dec 28, 2022 at 11:20 AM Ekta Awasthi 
 wrote:
Hello,

Is this the right mailing DL for QPID related queries.

Just wondering as I have not heard back but given it is a

Re: [VOTE] Release Apache Qpid ProtonJ2 1.0.0-M12

2023-01-11 Thread Gordon Sim 
+1, checked checksum and signature, built from source, ran example
against latest router release

On Tue, Jan 10, 2023 at 9:35 PM Timothy Bish  wrote:
>
> Hi folks,
>
> I have put together a release candidate for a 1.0.0-M12 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-M12-rc1/
>
> The maven artifacts are also staged for now at:
> https://repository.apache.org/content/repositories/orgapacheqpid-1254
>
> The JIRAs assigned are:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12313720&version=12352532
>
> 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-1254
>  
>
>
> The dependency for the protocol engine or the client itself would then be:
>
>
>  org.apache.qpid
>  protonj2
>  1.0.0-M12
>
>
>  org.apache.qpid
>  protonj2-client
>  1.0.0-M12
>
>
> {template}
>
> --
> Tim Bish
>
>
> -
> 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

Re: [VOTE] Release Apache Qpid JMS 2.2.0

2023-01-11 Thread Gordon Sim 
+1, checked checksum and signature, built from source, ran example
against latest router release

On Tue, Jan 10, 2023 at 6:04 PM Robbie Gemmell  wrote:
>
> Hi folks,
>
> I have put together a spin for a 2.2.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/2.2.0-rc1/
>
> The maven artifacts are also staged for now at:
> https://repository.apache.org/content/repositories/orgapacheqpid-1253
>
> The JIRAs assigned are:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314524&version=12352307
>
> 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-1253
> 
>   
>
> The dependency for the client itself would then be:
>
>   
> org.apache.qpid
> qpid-jms-client
> 2.2.0
>   
>
> -
> 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

Re: [VOTE] Release Apache Qpid JMS 1.8.0

2023-01-11 Thread Gordon Sim 
+1, checked checksum and signature, built from source, ran example
against latest router release

On Tue, Jan 10, 2023 at 5:11 PM Robbie Gemmell  wrote:
>
> Hi folks,
>
> I have put together a spin for a 1.8.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.8.0-rc1/
>
> The maven artifacts are also staged for now at:
> https://repository.apache.org/content/repositories/orgapacheqpid-1252
>
> The JIRAs assigned are:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314524&version=12352308
>
> 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-1252
> 
>   
>
> The dependency for the client itself would then be:
>
>   
> org.apache.qpid
> qpid-jms-client
> 1.8.0
>   
>
> -
> 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

Re: [VOTE] Release Apache Qpid ProtonJ2 1.0.0-M12

2023-01-11 Thread Robbie Gemmell 
On Tue, 10 Jan 2023 at 21:25, Timothy Bish  wrote:
>
> Hi folks,
>
> I have put together a release candidate for a 1.0.0-M12 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-M12-rc1/
>
> The maven artifacts are also staged for now at:
> https://repository.apache.org/content/repositories/orgapacheqpid-1254
>
> The JIRAs assigned are:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12313720&version=12352532
>
> 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-1254
>  
>
>
> The dependency for the protocol engine or the client itself would then be:
>
>
>  org.apache.qpid
>  protonj2
>  1.0.0-M12
>
>
>  org.apache.qpid
>  protonj2-client
>  1.0.0-M12
>
>
> {template}
>
> --
> Tim Bish
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
> For additional commands, e-mail: users-h...@qpid.apache.org
>

+1

I checked things out as follows:
- Verified the signature + checksum files.
- Checked for LICENCE + NOTICE files in the archives.
- Used "mvn apache-rat:check" to check headers in the source archive.
- Ran the source build and tests on JDK 11.
- Ran HelloWorld example against ActiveMQ Artemis main using the
staged client bits on JDK 11.

Robbie

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

2023-01-11 Thread Robbie Gemmell 
On Tue, 10 Jan 2023 at 17:55, Robbie Gemmell  wrote:
>
> Hi folks,
>
> I have put together a spin for a 2.2.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/2.2.0-rc1/
>
> The maven artifacts are also staged for now at:
> https://repository.apache.org/content/repositories/orgapacheqpid-1253
>
> The JIRAs assigned are:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314524&version=12352307
>
> 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-1253
> 
>   
>
> The dependency for the client itself would then be:
>
>   
> org.apache.qpid
> qpid-jms-client
> 2.2.0
>   

+1

I checked things over as follows:
- Verified the signature and checksum files.
- Checked for LICENCE and NOTICE files in the archives.
- Used "mvn apache-rat:check" to check headers in the source archive.
- Ran the build + tests from the source archive on JDK11.
- Built Quarkus extension for Qpid JMS using staged client and tested
on JDK11 and 17.
- Built Pooled JMS main and ran its tests against staged client on JDK11.
- Ran HelloWorld example against ActiveMQ Artemis main, on JDK11.

Robbie

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

2023-01-11 Thread Robbie Gemmell 
On Tue, 10 Jan 2023 at 17:02, Robbie Gemmell  wrote:
>
> Hi folks,
>
> I have put together a spin for a 1.8.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.8.0-rc1/
>
> The maven artifacts are also staged for now at:
> https://repository.apache.org/content/repositories/orgapacheqpid-1252
>
> The JIRAs assigned are:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314524&version=12352308
>
> 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-1252
> 
>   
>
> The dependency for the client itself would then be:
>
>   
> org.apache.qpid
> qpid-jms-client
> 1.8.0
>   

+1

I checked things over as follows:
- Verified the signature and checksum files.
- Checked for LICENCE and NOTICE files in the archives.
- Used "mvn apache-rat:check" to check headers in the source archive.
- Ran the build + tests from the source archive on JDK11.
- Built ActiveMQ Artemis main using staged client, ran AMQP tests, on JDK11.
- Built Quarkus extension for Qpid JMS using staged client and tested
on JDK11 and 17.
- Ran HelloWorld example against ActiveMQ Artemis main, on JDK11.

Robbie

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