@Tim Bain: yes.. Artemis from what I see on the class Names (I also
spoke to him gnodet on the IRC channel earlier today).
@gnodet: I am not understanding why you would need to use reflection.
You can just simply use JMSManagementHelper directly. they are all
static methods...
This example
This is in Artemis?
On May 18, 2017 4:23 PM, "Guillaume Nodet" wrote:
> I'm trying do perform management operation with pure JMS api.
> To retrieve the list of queues, I'm currently using the following code:
>
> QueueSession session = ((QueueConnection)
>
I'm trying do perform management operation with pure JMS api.
To retrieve the list of queues, I'm currently using the following code:
QueueSession session = ((QueueConnection)
connection).createQueueSession(false, Session.AUTO_ACKNOWLEDGE);
Queue managementQueue =
For now, let's focus on the garbage collection behavior. CMS has a
well-documented failure mode where fragmentation of the Old Gen space can
result in the JVM being unable to allocate a new large object even though
the heap isn't full. That might be what's going on here, or it might not be
related
Is "Fresh KahaDB" equivalent to deleting the entire contents of KahaDB
folder? If yes, we do this every early morning to prevent the issue, but it
has never helped us!
--
View this message in context:
MartinEden do you have the Inactivity Monitor running on both client and
server for ActiveMq ?
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Connection-to-activemq-broker-is-lost-within-one-second-tp4726204p4726360.html
Sent from the ActiveMQ - User mailing list
We have experienced this twice before. A complete reinstall of ActiveMq
(fresh kahadb) resolved it. Never found the root cause.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/ActiveMQ-broker-becomes-unresponsive-after-sometime-tp4725278p4726359.html
Sent from the
We are experiencing an issue when we have queues that do not have a lot of
traffic, and the consumers of those queues are "slow".
With inactivityMonitor on, when there are no new messages on a queue for a
day or two, the connection will be closed even though we have
useKeepAlive=true. The problem
That property is relevant only when you're going to deserialize the object,
which typically happens only on the clients. Its possible to deserialize
the object on the server, in the case were you you the message via the web
console, but if you're not doing that then the only place you would need
Hi,
I am upgrading my ActiveMQ setup from v5.11.1 to v5.14.4. I came across this
wiki page as per upgrade instructions -
http://activemq.apache.org/objectmessage.html.
It says that i need to org.apache.activemq.SERIALIZABLE_PACKAGES system
property to whitelist the packages. However, it isn't
Thank you Tim for your response.
When I an mqtt transport connector to my broker-config "
" and I try to
connect to it using apache paho java, I am getting this exception :
Exception in thread "main" java.lang.IllegalArgumentException:
mqtt://0.0.0.0:1884
at
The TCP transport speaks OpenWire, so it's not valid to connect to it with
an MQTT client.
Tim
On May 18, 2017 3:07 AM, "aragoubi" wrote:
I have an embedded broker, and I am connection a Paho client to it.
This my broker config file :
>From last 3 days' GC logs I observe something consistently :
When full GC happens which takes about 8 and odd seconds, 15 minutes later
our servers loose connection to the broker; all further attempts to
reconnect fail with "Timeout" exception. New connection attempts also fail
with same
I have an embedded broker, and I am connection a Paho client to it.
This my broker config file :
http://activemq.apache.org/schema/core; useJmx="true"
useShutdownHook="false" brokerName="mimo.broker1">
I am getting
I observed closely for last 3 days, but couldn't identify anything wrong with
CPU, memory, Network I/O, Disk I/O, etc
a) CPU usage on this EC2 instance (has 8 vCPUs) has never crossed 35%
b) Memory usage varies between 1GB to 18 GB (Total available is 32 GB and
Xmx assigned for this broker process
15 matches
Mail list logo