Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Connection optimization for JBOSS Consumers. #77

Open
akhil1000 opened this issue Oct 3, 2022 · 3 comments
Open

Connection optimization for JBOSS Consumers. #77

akhil1000 opened this issue Oct 3, 2022 · 3 comments

Comments

@akhil1000
Copy link

Currently, we are seeing a high number of connections on the Broker so see if you can optimize.

We would like to have a way to control the number of connections or sessions using MaxSessions.

@eolivelli
Copy link
Collaborator

How any MDBs you have ?

for each MDS (endPoint) we try to re-use the same PulsarConnectionFactory.
The PulsarConnectionFactory holds an instance of the Java Pulsar Client, that maintains the pool of connections.

Are you configuring the MDBs with the same "Configuration" ?
if you have the same configuration and you simply change the destination I would expect that you have only one PulsarClient.

Each PulsarClient opens only 1 connection to each broker
se connectionsPerBroker configuration

@akhil1000
Copy link
Author

I do not see anything logged for below line
log.info( "Activate endpoint {} {} configuration {}",

Is there a way we can log - number of Connectionfactories/Sessions and other metrics in resource adapter to collect the meterics
?

@akhil1000
Copy link
Author

There are around 990 MDBs

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants