Krzysztof Sobkowiak created KARAF-3639:
------------------------------------------
Summary: jms:queues doesn't show queues when used with pooled xa
connection factory
Key: KARAF-3639
URL: https://issues.apache.org/jira/browse/KARAF-3639
Project: Karaf
Issue Type: Bug
Affects Versions: 2.3.10, 2.4.1, 3.0.3
Environment: Karaf 2.4.1, ActiveMQ 5.11.1
Reporter: Krzysztof Sobkowiak
I have installed ActveMQ on Karaf and copied the attached blueprint file into
{{deploy}} directory. This is a blueprint from ServiceMix which defines defaul
connection factories
* {{activemqConnectionFactory}} -- non-xa connection factory
* {{pooledConnectionFactory}} -- non-xa pooled connection factory
* {{jmsXaConnectionFactory}} -- xa connection factory
* {{jmsXaPoolConnectionFactory}} -- xa pooled connection factory
Next the {{pooledConnectionFactory}} and {{jmsXaPoolConnectionFactory}} are
exported as OSGi services. The both are detected with
{{jms:connectionfactories}}
{code}
karaf@root> jms:connectionfactories
JMS Connection Factory
jms/default-cf-xa
jms/default-cf
{code}
The both can be used to send or browse messages
{code}
karaf@root> jms:send jms/default-cf-xa test-queue 11
karaf@root> jms:send jms/default-cf-xa test-queue 22
karaf@root> jms:send jms/default-cf-xa test-queue 33
karaf@root> jms:browse jms/default-cf test-queue
ID % Content Charset Type Correlation Delivery
Destination Expiration Priority Redelivered ReplyTo
ID:lenovo-42443-1427742093201-3:1:1:1:1 % 11 UTF-8 null
null Persistent queue://test-queue Never 4 false null
ID:lenovo-42443-1427742093201-3:2:1:1:1 % 22 UTF-8 null
null Persistent queue://test-queue Never 4 false null
ID:lenovo-42443-1427742093201-3:3:1:1:1 % 33 UTF-8 null
null Persistent queue://test-queue Never 4 false null
{code}
But {{jms:queues}} shows available queues only if used with the non-xa pooled
factory
{code}
karaf@root> jms:queues jms/default-cf-xa
JMS Queues
karaf@root> jms:queues jms/default-cf
JMS Queues
test-queue
karaf@root>
{code}
It doesn't work with xa pooled connection factory. But if I export the xa
connection factory {{jmsXaConnectionFactory}} instead of
{{jmsXaPoolConnectionFactory}} it works correctly
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
