The ECCN classification of ActiveMQ is given as 5D002, see
http://www.apache.org/licenses/exports/
I believe this is a self-classification.
To answer your question, this bit is relevant (my bolding):
"Products classified as ECCN 5D002 , are exported by the ASF under the TSU
exception in EAR 740.
Hi: Does ActiveMQ contain encryption algorithms that preclude it from being
shipped to other countries? I see on the ActiveMQ website that password
encryption can be done using encrypt and decrypt options of the activemq
command, for example. Is other encryption or decryption done by ActiveMQ or
is
Without looking at your specific exception, you say everything was working
until you changed 2 things.
Can you come back here when you have isolated whether the behaviour changes
when you go from tcp to nio or when you make the change for kahaDB?
If it's for kahaDB, you need to tell us the range
Multicast... not broadcast...
While I'm at it, you have to be aware of a race where one broker is starting
but has not yet advertised its transports.
-
Michael Hayes B.Sc. (NUI), M.Sc. (DCU), SCSA SCNA
--
View this message in context:
http://activemq.2283324.n4.nabble.com/How-to-check-i
One way is using the feature of multicast broker discovery
http://activemq.apache.org/discovery-transport-reference.html
Then, every >500ms, a broadcast datagram is sent for each transport on each
broker.
239.255.2.3 UDP D=6155 S=6155
The message indicates the transport that is running.
Looks interesting... you might get a response if you comment on his blog
entry directly.
However, I think http://activemq.apache.org/jdbc-master-slave.html is worth
a look anyway:
"Clients should be using the Failover Transport to connect to the available
brokers. e.g. using a URL something like
Hhm, SMX 4.4.1 deploys ActiveMQ 5.5.1 just nicely into its OSGi container.
On May 30, 2012, at 11:44 AM, Jeremias Maerki wrote:
> Hi Torsten,
>
> thanks. Yes, I've made experiments with 5.5.1 on the server side but had
> trouble getting it up reliably in my OSGi environment so I'm hesitant to
>
Hi Torsten,
thanks. Yes, I've made experiments with 5.5.1 on the server side but had
trouble getting it up reliably in my OSGi environment so I'm hesitant to
upgrade on the server side. However, the problem resides mainly in the
client AFAICS, and that one uses 5.5.1 already. I guess I'll take a p
Hello,
ActiveMQ 5.3.0 is really old. Have you thought of upgrading to the latest
broker release 5.5.1?
Chances aren't too bad that your problem has been resolved.
Torsten Mielke
tors...@fusesource.com
tmie...@blogspot.com
On May 30, 2012, at 11:25 AM, Jeremias Maerki wrote:
> No ideas? As
For temp space it is set using the dataDirectory property on the bean:
http://activemq.apache.org/schema/core"; brokerName="localhost"
dataDirectory="${activemq.base}/data">
For the store, it is typically your KahaDB configuration
or similar config if you're using a different persistence
No ideas? As a work-around I'm now thinking about running a scheduled
task that restarts the MessageListener every hour. That's a work-around
that shouldn't really be necessary, right? A colleague told me yesterday
that he did exactly that in a personal project of his. So, I'm probably
not the only
11 matches
Mail list logo
