Unable to send to Solace JMS queue (Capability Mismatch: Router does not support durable endpoint management)
up vote
1
down vote
favorite
I am new to Solace. We have an app that looks up a Solace connection factory using JNDI and then sends/consumes messages from various queues.
In one of our environments, we get the following exception.
I assume this is because this Solace broker/router is configured differently. Any pointers on how to fix or troubleshoot the issue appreciated.
nested exception is com.solacesystems.jms.ConfigurationException: Error creating queue - operation not supported on router (Capability Mismatch: Router does not support durable endpoint management.)
at org.springframework.jms.support.JmsUtils.convertJmsAccessException(JmsUtils.java:316)
at org.springframework.jms.support.JmsAccessor.convertJmsAccessException(JmsAccessor.java:169)
at org.springframework.jms.core.JmsTemplate.execute(JmsTemplate.java:497)
at org.apache.camel.component.jms.JmsConfiguration$CamelJmsTemplate.send(JmsConfiguration.java:228)
at org.apache.camel.component.jms.JmsProducer.doSend(JmsProducer.java:431)
at org.apache.camel.component.jms.JmsProducer.processInOnly(JmsProducer.java:385)
jms jndi solace
add a comment |
up vote
1
down vote
favorite
I am new to Solace. We have an app that looks up a Solace connection factory using JNDI and then sends/consumes messages from various queues.
In one of our environments, we get the following exception.
I assume this is because this Solace broker/router is configured differently. Any pointers on how to fix or troubleshoot the issue appreciated.
nested exception is com.solacesystems.jms.ConfigurationException: Error creating queue - operation not supported on router (Capability Mismatch: Router does not support durable endpoint management.)
at org.springframework.jms.support.JmsUtils.convertJmsAccessException(JmsUtils.java:316)
at org.springframework.jms.support.JmsAccessor.convertJmsAccessException(JmsAccessor.java:169)
at org.springframework.jms.core.JmsTemplate.execute(JmsTemplate.java:497)
at org.apache.camel.component.jms.JmsConfiguration$CamelJmsTemplate.send(JmsConfiguration.java:228)
at org.apache.camel.component.jms.JmsProducer.doSend(JmsProducer.java:431)
at org.apache.camel.component.jms.JmsProducer.processInOnly(JmsProducer.java:385)
jms jndi solace
add a comment |
up vote
1
down vote
favorite
up vote
1
down vote
favorite
I am new to Solace. We have an app that looks up a Solace connection factory using JNDI and then sends/consumes messages from various queues.
In one of our environments, we get the following exception.
I assume this is because this Solace broker/router is configured differently. Any pointers on how to fix or troubleshoot the issue appreciated.
nested exception is com.solacesystems.jms.ConfigurationException: Error creating queue - operation not supported on router (Capability Mismatch: Router does not support durable endpoint management.)
at org.springframework.jms.support.JmsUtils.convertJmsAccessException(JmsUtils.java:316)
at org.springframework.jms.support.JmsAccessor.convertJmsAccessException(JmsAccessor.java:169)
at org.springframework.jms.core.JmsTemplate.execute(JmsTemplate.java:497)
at org.apache.camel.component.jms.JmsConfiguration$CamelJmsTemplate.send(JmsConfiguration.java:228)
at org.apache.camel.component.jms.JmsProducer.doSend(JmsProducer.java:431)
at org.apache.camel.component.jms.JmsProducer.processInOnly(JmsProducer.java:385)
jms jndi solace
I am new to Solace. We have an app that looks up a Solace connection factory using JNDI and then sends/consumes messages from various queues.
In one of our environments, we get the following exception.
I assume this is because this Solace broker/router is configured differently. Any pointers on how to fix or troubleshoot the issue appreciated.
nested exception is com.solacesystems.jms.ConfigurationException: Error creating queue - operation not supported on router (Capability Mismatch: Router does not support durable endpoint management.)
at org.springframework.jms.support.JmsUtils.convertJmsAccessException(JmsUtils.java:316)
at org.springframework.jms.support.JmsAccessor.convertJmsAccessException(JmsAccessor.java:169)
at org.springframework.jms.core.JmsTemplate.execute(JmsTemplate.java:497)
at org.apache.camel.component.jms.JmsConfiguration$CamelJmsTemplate.send(JmsConfiguration.java:228)
at org.apache.camel.component.jms.JmsProducer.doSend(JmsProducer.java:431)
at org.apache.camel.component.jms.JmsProducer.processInOnly(JmsProducer.java:385)
jms jndi solace
jms jndi solace
asked Nov 7 at 22:58
raylite3
185
185
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
up vote
0
down vote
accepted
In order to enable Guaranteed Messaging you basically have to configure this two steps:
- Modify the User Profile you're using to allow Guaranteed Send and/or Receive.
- Modify the VPN configuration to defin the size of the Message Spool to be used.
This can be done with the following sample commands on Solace CLI:
solace(configure)# client-profile default
solace(configure/client-profile)# allow-guaranteed-message-receive
solace(configure/client-profile)# allow-guaranteed-message-send
solace(configure/client-profile)# exit
solace(configure)# client-username default message-vpn default
solace(configure/client-username)# client-profile default
solace(configure/client-username)# no shutdown
solace(configure/client-username)# exit
solace(configure)# message-spool message-vpn default
solace(configure/message-spool)# max-spool-usage 60000
If you want more information about Guaranteed messaging and more detailed configuration, please refer to:
https://docs.solace.com/Configuring-and-Managing/Configuring-Guaranteed-Msging.htm
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
accepted
In order to enable Guaranteed Messaging you basically have to configure this two steps:
- Modify the User Profile you're using to allow Guaranteed Send and/or Receive.
- Modify the VPN configuration to defin the size of the Message Spool to be used.
This can be done with the following sample commands on Solace CLI:
solace(configure)# client-profile default
solace(configure/client-profile)# allow-guaranteed-message-receive
solace(configure/client-profile)# allow-guaranteed-message-send
solace(configure/client-profile)# exit
solace(configure)# client-username default message-vpn default
solace(configure/client-username)# client-profile default
solace(configure/client-username)# no shutdown
solace(configure/client-username)# exit
solace(configure)# message-spool message-vpn default
solace(configure/message-spool)# max-spool-usage 60000
If you want more information about Guaranteed messaging and more detailed configuration, please refer to:
https://docs.solace.com/Configuring-and-Managing/Configuring-Guaranteed-Msging.htm
add a comment |
up vote
0
down vote
accepted
In order to enable Guaranteed Messaging you basically have to configure this two steps:
- Modify the User Profile you're using to allow Guaranteed Send and/or Receive.
- Modify the VPN configuration to defin the size of the Message Spool to be used.
This can be done with the following sample commands on Solace CLI:
solace(configure)# client-profile default
solace(configure/client-profile)# allow-guaranteed-message-receive
solace(configure/client-profile)# allow-guaranteed-message-send
solace(configure/client-profile)# exit
solace(configure)# client-username default message-vpn default
solace(configure/client-username)# client-profile default
solace(configure/client-username)# no shutdown
solace(configure/client-username)# exit
solace(configure)# message-spool message-vpn default
solace(configure/message-spool)# max-spool-usage 60000
If you want more information about Guaranteed messaging and more detailed configuration, please refer to:
https://docs.solace.com/Configuring-and-Managing/Configuring-Guaranteed-Msging.htm
add a comment |
up vote
0
down vote
accepted
up vote
0
down vote
accepted
In order to enable Guaranteed Messaging you basically have to configure this two steps:
- Modify the User Profile you're using to allow Guaranteed Send and/or Receive.
- Modify the VPN configuration to defin the size of the Message Spool to be used.
This can be done with the following sample commands on Solace CLI:
solace(configure)# client-profile default
solace(configure/client-profile)# allow-guaranteed-message-receive
solace(configure/client-profile)# allow-guaranteed-message-send
solace(configure/client-profile)# exit
solace(configure)# client-username default message-vpn default
solace(configure/client-username)# client-profile default
solace(configure/client-username)# no shutdown
solace(configure/client-username)# exit
solace(configure)# message-spool message-vpn default
solace(configure/message-spool)# max-spool-usage 60000
If you want more information about Guaranteed messaging and more detailed configuration, please refer to:
https://docs.solace.com/Configuring-and-Managing/Configuring-Guaranteed-Msging.htm
In order to enable Guaranteed Messaging you basically have to configure this two steps:
- Modify the User Profile you're using to allow Guaranteed Send and/or Receive.
- Modify the VPN configuration to defin the size of the Message Spool to be used.
This can be done with the following sample commands on Solace CLI:
solace(configure)# client-profile default
solace(configure/client-profile)# allow-guaranteed-message-receive
solace(configure/client-profile)# allow-guaranteed-message-send
solace(configure/client-profile)# exit
solace(configure)# client-username default message-vpn default
solace(configure/client-username)# client-profile default
solace(configure/client-username)# no shutdown
solace(configure/client-username)# exit
solace(configure)# message-spool message-vpn default
solace(configure/message-spool)# max-spool-usage 60000
If you want more information about Guaranteed messaging and more detailed configuration, please refer to:
https://docs.solace.com/Configuring-and-Managing/Configuring-Guaranteed-Msging.htm
answered Nov 8 at 18:24
Mauricio Rodríguez
16
16
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53199189%2funable-to-send-to-solace-jms-queue-capability-mismatch-router-does-not-support%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown