I've seen Java processes that run out of heap hard-crash without logging
anything (sometimes they do, sometimes not, even from run to run). Could
you simply have used more heap than your JVM had available?
Do you get any additional useful logging at DEBUG or TRACE?
Tim
On Thu, Jul 20, 2017 at 12
Luckily, you don't need access to the code TIBCO BW generates in order to
test this. You can set a breakpoint on the
http://grepcode.com/file/repo1.maven.org/maven2/org.apache.activemq/activemq-all/5.10.0/org/apache/activemq/ActiveMQMessageConsumer.java#ActiveMQMessageConsumer.acknowledge%28%29
met
Hi All,
I have activemq 15.3.3 running on 2 hosts setup as Fault tolerant. Kahadb is
ZFS mount used by both active mq hosts. Seeing a weird issue, Master is
getting stopped without any errors in log file. I have attached both the
server logs. I am using default settings in activemq.xml
If you see
I've submitted https://issues.apache.org/jira/browse/AMQ-6773 to capture
the deadlocks you encountered and your proposal that we invoke that
onMessage() method without holding the lock.
Can you please update it to provide the version of ActiveMQ you were using,
as well as any additional informatio
... and the winner is...
https://blogs.apache.org/activemq/entry/new-activemq-logo
Thanks for all the participants, both who voted and for all the submissions.
--
Clebert Suconic
There's a recent fix on artemis master.. due as 2.3.0 next week. Can
you try that one?
The example works. But on one host my configuration is also working. Try it
on two different hosts.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Artemis-master-slave-startup-results-in-two-live-broker-tp4728676p4728684.html
Sent from the ActiveMQ - User mailing list ar
Artemis ships with an example that mimics your use-case called
'replicated-failback-static'. Does this example work for you? You can run
it from the /examples/features/ha/replicated-failback-static
directory using 'mvn verify'.
Justin
On Wed, Jul 19, 2017 at 9:56 AM, martk <123mar...@web.de> w
Extract of the master.xml ("check-for-live-server" set to false remains the
same results):
true
tcp://192.168.0.10:61600
tcp://192.168.0.11:61600
tcp://0.0.0.0:61600
Your XML didn't come through for some reason. I can't see what your
configuration is.
Justin
On Wed, Jul 19, 2017 at 9:37 AM, martk <123mar...@web.de> wrote:
> Hi everyone,
>
> I am using a master/slave setup with replication and Artemis 2.1.0.
>
> If I do a kill of the master the slave gets l
Hi everyone,
I am using a master/slave setup with replication and Artemis 2.1.0.
If I do a kill of the master the slave gets live (as configured). But after
starting the master again it directly gets live and there is no replication
any more. The slave still continues as live.
The master contain
Sorry, I messed up my boolean logic when I wrote my reply. I meant to write
that I have verified that my conduitSubscriptions is set to TRUE so this
should not be the cause. By mistake I have typed false...
I'll try to watch the the enqueue counts to see if I can figure out the
origin.
Thanks,
T
If you set conduitSubscriptions to true, does the behavior become the
expected behavior? If so, you can read a description of why having it false
would cause this to happen halfway down
http://activemq.apache.org/networks-of-brokers.html.
You can determine where the duplication occurs by watching
I am using just regular topics. In my example above C and D connect to their
embedded brokers via VM transport, create a consumer and register a
listener.
I have debugged it just to make sure and conduitSubscriptions are set to
false, i.e. org.apache.activemq.network.NetworkBridgeFactory#createBri
14 matches
Mail list logo
