Some observation :
I saw this exception in ActiveMQ setup again. This time I restarted broker
with "AllowLinkStealing" and issue got resolved.
Again I restarted broker with normal configuration (without
"AllowLinkStealing"), I didn't see the issue.
Can I use "AllowLinkStealing" for workaround
Sorry to hear your frustration. Please keep in mind this is an open-source
project and only volunteers spend their time helping here. I wish I were
paid to reply to your questions so I could do so all day long!
With that said, based on the error message, I believe the error means there
is an att
My work is stuck here and no one is responding. We expect ActiveMQ vendors to
help us to resolve such issues. It's been 10 days since I posted and no
response after that. Really disappointing.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/javax-jms-InvalidClientIDE
Hi,
I also have a similar requirement where I want to have multiple durable
subscribers and publishers in the same client application connecting to the
broker.(broker version 5.10)
What should be the correct way to configure the above mentioned case?
As Anuj mentioned in last update:
1) I use
> When using the pool the calls to createConnection will create up to max
connections before returning > already existing connections, so if
you want a durable subscription on a pooled connection type setup you > must
limit it to one connection
When I try with maxCOnneciton to "1" and by u
Hey Tim,
Did you get a chance to look at this ?
--
View this message in context:
http://activemq.2283324.n4.nabble.com/javax-jms-InvalidClientIDException-for-durable-subscription-on-broker-restart-tp4684381p4684429.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Please respond
--
View this message in context:
http://activemq.2283324.n4.nabble.com/javax-jms-InvalidClientIDException-for-durable-subscription-on-broker-restart-tp4684381p4684406.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Hi,
In my case I am creating 6 listeners in my application using different
spring DMLC.
So In this case should
1) I use 1 pooledConnectionFactory with "maxConnection" = 6
OR
2) different pooledCOnnectionFactory for each listener.
Thanks,
Anuj
--
View this message in context:
http://ac
On 08/11/2014 09:57 AM, khandelwalanuj wrote:
Hi,
No only one application is running on the host.
Yes I am using pooled connection factory. This is how my connection factory
looks liks:
jmsFactory*"
class="org.apache.activemq.pool.PooledConnectionFactory"
destroy-method
Hi,
No only one application is running on the host.
Yes I am using pooled connection factory. This is how my connection factory
looks liks:
jmsFactory*"
class="org.apache.activemq.pool.PooledConnectionFactory"
destroy-method="stop">
On 08/11/2014 06:24 AM, khandelwalanuj wrote:
Hi,
I am seeing a weird issue:
when I restart the ActiveMQ broker a *durable subscriber client* is not able
to connect to the broker showing "InvalidClientIDException".
*Exception:
*Failed to add Connection ID:gbo5.nyc.xyz.com-36751-1407746385464-11
Can someone please check. It is affecting my production setup.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/javax-jms-InvalidClientIDException-for-durable-subscription-on-broker-restart-tp4684381p4684382.html
Sent from the ActiveMQ - User mailing list archive at Nabb
Hi,
I am seeing a weird issue:
when I restart the ActiveMQ broker a *durable subscriber client* is not able
to connect to the broker showing "InvalidClientIDException".
*Exception:
*Failed to add Connection ID:gbo5.nyc.xyz.com-36751-1407746385464-11:6
javax.jms.InvalidClientIDException: Broker:
13 matches
Mail list logo
