issues
search
amqphub
/
quarkus-qpid-jms
Quarkus extension for using the Qpid JMS AMQP 1.0 client.
Apache License 2.0
12
stars
11
forks
source link
issues
Newest
Newest
Most commented
Recently updated
Oldest
Least commented
Least recently updated
Feature request: Support for XA transactions
#24
jochenr
opened
1 month ago
0
Fix #22 to add pooling support
#23
zhfeng
closed
1 year ago
6
Add pooling support
#22
zhfeng
closed
1 year ago
0
Mark the QPID JMS extension as stable.
#21
cescoffier
closed
2 years ago
1
Azure Managed ID
#20
RJJdeVries
closed
2 years ago
1
Upgrade quarkus-test-artemis to 1.0.5
#19
gsmet
closed
2 years ago
2
Added health check
#18
mikethecalamity
opened
2 years ago
2
Quarkus JMS tutorial contains test that always fails
#17
maxkahan
closed
3 years ago
1
JMS Tutorial building native executive with Docker
#16
aslihanilgin
closed
3 years ago
1
Implement an AMQP dev service
#15
vkasala
opened
3 years ago
4
make URL config prop optional by giving it a default
#14
gemmellr
closed
3 years ago
0
Support for Named Multiple ConnectionFactories
#13
vkasala
opened
3 years ago
5
Upgrade to Quarkus 2.0.0.CR3
#12
ppalaga
closed
3 years ago
9
Consider making `quarkus.qpid-jms.url` optional
#11
jamesnetherton
closed
3 years ago
9
setObject on ObjectMessage hangs when running in GraalVM
#10
chughts
opened
3 years ago
6
Feature request : support SSL certificate
#9
zhang-hongjie
closed
4 years ago
5
Feature request : health check
#8
bligny
opened
4 years ago
1
Consuming messages from RabbitMQ using AMQP-1.0
#7
mthmulders
opened
4 years ago
1
Client is not consuming message
#6
15I
closed
4 years ago
3
issue 4 - improve extension description and metadata
#5
emmanuelbernard
closed
4 years ago
3
Improve description for code.quarkus.io
#4
emmanuelbernard
closed
4 years ago
2
multiple URL connections
#3
15I
closed
4 years ago
3
The client's failover provider did not fire the connection ExceptionListener
#2
15I
closed
4 years ago
1
opentracing WARN with jms.tracing=opentracing
#1
15I
closed
4 years ago
3