Re: Cannot initialize queue:Resource temporarily unavailable

2019-11-22 Thread Justin Bertram
One more thing you can try... The default value for is 4096 so you could specify something smaller than that, e.g. 2048. This value is used in the call to io_queue_init. Justin On Fri, Nov 22, 2019 at 11:06 AM Justin Bertram wrote: > You could also work-around this issue by specifying > NIO

Re: Cannot initialize queue:Resource temporarily unavailable

2019-11-22 Thread Justin Bertram
You could also work-around this issue by specifying NIO in your broker.xml. The defaults to ASYNCIO which will use the native libaio for best performance. Justin On Fri, Nov 22, 2019 at 11:04 AM Justin Bertram wrote: > The last bit of Java code before entering the JNI code is here [1]. The >

Re: Cannot initialize queue:Resource temporarily unavailable

2019-11-22 Thread Justin Bertram
The last bit of Java code before entering the JNI code is here [1]. The JNI code [2] attempts to invoke io_queue_init [3] from libaio which results in the "Resource temporarily unavailable" error. So it appears there's something environmental which is preventing libaio from doing its work. My sear

Re: LDAP authorization with multiple LDAP servers

2019-11-22 Thread Justin Bertram
Under the covers the cachedLDAPAuthorizationMap uses com.sun.jndi.ldap.LdapCtxFactory for connectivity with LDAP [1]. The Oracle documentation states [2], "Instead of just one URL, you can also supply a space-separated list of URLs. In this case, the LDAP provider will attempt to use each URL in t

Re: Not running on Jetty, JSR-356 support unavailable

2019-11-22 Thread Naveen Kumar
Hi JB, I am starting it from code using brokerservice. Thanks Naveen -- Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html

LDAP authorization with multiple LDAP servers

2019-11-22 Thread Weil, Janus
Dear ActiveMQ people, we have a neatly working setup of several ActiveMQ 5 brokers which rely on an LDAP server for authorization. The configuration in activemq.xml looks roughly like this (some parts omitted): ldap://my

Re: Disk I/O requirement for persistent messages

2019-11-22 Thread Peter Hicks
Hi Tim, Jean-Baptiste, I've worked out what the issue is/was: I have a Camel route which splits groups of 32 elements in a JSON array in to 32 individual messages. These are small and persistent and so written to disk when there's a durable subscription in place, causing the high I/O load. Even

Cannot initialize queue:Resource temporarily unavailable

2019-11-22 Thread Ehsan Zaery Moghaddam
Hi We're using WildFly 18 which is using ActiveMQ 2.10.1. Since a few days ago, we're getting the following exception whenever we try to start the WildFly on some of our servers. It seems to be on some random servers, but those that have this issue, continuously throw the same exception. It's from

Re: Not running on Jetty, JSR-356 support unavailable

2019-11-22 Thread Jean-Baptiste Onofré
Hi Naveen Are you integrated in Tomcat with RAR or you just start ActiveMQ by "code" (BrokerService) ? Regards JB On 22/11/2019 11:52, Naveen Kumar wrote: > I am trying to upgrade ActiveMQ jar to its latest version. It requires me > to upgrade Jetty to 9.4 version. > I have current setup as Tomc

Not running on Jetty, JSR-356 support unavailable

2019-11-22 Thread Naveen Kumar
I am trying to upgrade ActiveMQ jar to its latest version. It requires me to upgrade Jetty to 9.4 version. I have current setup as Tomcat 9 + ActiveMQ 5.12 + jetty-all-8.1. I want to upgrade it as Tomcat 9 + ActiveMQ 5.15 + jetty-all-9.4. After doing the changes when I try to start tomcat, it give