XML Parsing error in web console XML Queue View

Hi, we've recently upgraded from amq 5.9.0 to 5.14.5, and now I get the following, instead of the xml queue info I previously got when using the XML Queue View from the web console: XML Parsing Error: prefix not bound to a namespace Location: http://amq-admin.domain/admin/xml/queues.jsp Line

Re: PooledConnectionFactory: createConnection results in log entry "Successfully connected to ..."

Hi Jochen, Excellent news, glad you have found and resolved your issue. Cheers, Mike Sent from my iPhone > On 7 Jul 2017, at 16:00, jochenw wrote: > > Hi, > > sorry, but the issue was a different one. It was my misunderstanding of the > idleTimeout property.

Re: Increasing Duplicate ID Cache size

www 122 Original message From: Clebert Suconic Date: 7/7/17 7:56 PM (GMT+01:00) To: users@activemq.apache.org Subject: Re: Increasing Duplicate ID Cache size WwwI believe you are talking about ActiveMQ Artemis. the duplicate detection is

Re: Increasing Duplicate ID Cache size

Original message From: Clebert Suconic Date: 7/7/17 7:56 PM (GMT+01:00) To: users@activemq.apache.org Subject: Re: Increasing Duplicate ID Cache size I believe you are talking about ActiveMQ Artemis. the duplicate detection is intended for in

Is there a way to load group name in SecurityContext during ldap authentication?

Currently when AcitveMQ logs in to LDAP, it is creating SecurityContext with UserPrincipal object. Is there a way we can also get the GroupPrincipal corresponding to user from LDAP? -- View this message in context:

Re: Increasing Duplicate ID Cache size

I believe you are talking about ActiveMQ Artemis. the duplicate detection is intended for in transit messages.. that means.. in case you retry a send (say because of an error), the duplicate would be ignored.. and you would then achieve Exactly Once semantic without using transactions. You could

Re: PooledConnectionFactory: createConnection results in log entry "Successfully connected to ..."

Hi, sorry, but the issue was a different one. It was my misunderstanding of the idleTimeout property. Is doesn't timeout a connection which is used from the pool, but the connection which the pool opens to the broker. My settings were such that the timeout was too short for the connection pool to

Re: PooledConnectionFactory: createConnection results in log entry "Successfully connected to ..."

Hi Mike, good idea. I still have to do some testing, but on a first glance, I saw that in the JUnit test, they never close a created connection. I thought that after getting a connection from the PooledConnectionFactory with connection = pooledConnectionFactory.createConnection() and having

Re: Network of brokers: problem with duplex="false" for static bridges

Hi Tim, thanks for clarifying this. I may have expressed it not precisely in my answer: the problem exactly was that for the broker1_broker2_simplex bridge, when sending messages to a queue which is initially only known by broker 2 (because only there a consumer exists for this queue), sometimes

[ANNOUNCE] Apache ActiveMQ 5.15.0 Released

Hi everyone, The ActiveMQ team is pleased to announce that Apache ActiveMQ 5.15.0 has been released and includes many fixes and improvements. Also note that this release bumps the minimum required Java version to Java 8. A list of issues resolved in this release is available here:

Re: AMQ service stops on network disconnection

Thanks for explaining what you did. Tim On Jul 7, 2017 2:23 AM, "sgtech" wrote: > At first we only use the default jdbcPersistenceAdapter (without the lease > lock) -> not surviving a network disconnection > > Then we tried to change the wrapper.conf to

Increasing Duplicate ID Cache size

Hi, Due to the requirement of being able to store a large number of messages in the queue without duplicates, I am considering increasing the duplicate id cache size (parameter: id-cache-size) from its default value of 2000 to a million. While I know that this would require additional

Re: AcativeMQ becomes slow suddenly in 60 minutes after starting a performance test

Dear Tim Thanks for helping me a lot. Let me answer your questions. > Were your IoT processes publishing to queues or topics? Topics > To a single one or to one per client? To a single ActiveMQ broker. > Was anything consuming the messages? Yes, our subscriber consume the topics. > Were

Re: AMQ service stops on network disconnection

At first we only use the default jdbcPersistenceAdapter (without the lease lock) -> not surviving a network disconnection Then we tried to change the wrapper.conf to restart the AMQ service -> not working also wrapper.filter.trigger.1=Failed to start Apache ActiveMQ