You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Giridharan Jayaseelan (Jira)" <ji...@apache.org> on 2020/11/30 09:39:00 UTC
[jira] [Updated] (AMQ-8092) Unable to retrieve JMS message; Caused
by: Setting clientID on a used Connection is not allowed.
[ https://issues.apache.org/jira/browse/AMQ-8092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Giridharan Jayaseelan updated AMQ-8092:
---------------------------------------
Description:
In Dell Boomi we are using JMS connector with GET action for Active MQ to subscribe data from Topic using Durable Subscription Name. In connector we enabled Connection pool with Maximum idle time as 0 sec.
And we tried to schedule process for every 1 min/2min/5min interval but we see below error more frequently for every 3 execution we have this error for 2nd execution.
Error Message :
*Unable to retrieve JMS message; Caused by: Setting clientID on a used Connection is not allowed.*
We also noticed all times process executing happening on specific node for both success and failure.
We tired of few Active MQ properties to close connection like jms.closeTimeout but it doesn’t worked for us. So could you please help us on this issue .
Also, we have tested with disabling pooling and it worked fine .But for better performance we are needed pooling enable.
And also idle time we have changed to 10000ms , 5000ms and tested but we see same issue in pooling enable mode.
Please let me know in case if you need any other details.
was:
In Dell Boomi we are using JMS connector with GET action for Active MQ to subscribe data from Topic using Durable Subscription Name. In connector we enabled Connection pool with Maximum idle time as 0 sec.
And we tried to schedule process for every 1 min/2min/5min interval but we see below error more frequently for every 3 execution we have this error for 2nd execution.
Error Message :
Unable to retrieve JMS message; Caused by: Setting clientID on a used Connection is not allowed.
We also noticed all times process executing happening on specific node for both success and failure.
We tired of few Active MQ properties to close connection like jms.closeTimeout but it doesn’t worked for us. So could you please help us on this issue .
Also, we have tested with disabling pooling and it worked fine .But for better performance we are needed pooling enable.
And also idle time we have changed to 10000ms , 5000ms and tested but we see same issue in pooling enable mode.
Please let me know in case if you need any other details.
> Unable to retrieve JMS message; Caused by: Setting clientID on a used Connection is not allowed.
> ------------------------------------------------------------------------------------------------
>
> Key: AMQ-8092
> URL: https://issues.apache.org/jira/browse/AMQ-8092
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker, JMS client
> Affects Versions: 5.15.13
> Reporter: Giridharan Jayaseelan
> Priority: Major
>
> In Dell Boomi we are using JMS connector with GET action for Active MQ to subscribe data from Topic using Durable Subscription Name. In connector we enabled Connection pool with Maximum idle time as 0 sec.
> And we tried to schedule process for every 1 min/2min/5min interval but we see below error more frequently for every 3 execution we have this error for 2nd execution.
>
> Error Message :
> *Unable to retrieve JMS message; Caused by: Setting clientID on a used Connection is not allowed.*
>
> We also noticed all times process executing happening on specific node for both success and failure.
>
> We tired of few Active MQ properties to close connection like jms.closeTimeout but it doesn’t worked for us. So could you please help us on this issue .
>
> Also, we have tested with disabling pooling and it worked fine .But for better performance we are needed pooling enable.
> And also idle time we have changed to 10000ms , 5000ms and tested but we see same issue in pooling enable mode.
> Please let me know in case if you need any other details.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)