Sorry for the delay here is the artemis-service.xml
artemis-broker-0.0.0.0
ActiveMQ Artemis: broker @ 0.0.0.0
Apache ActiveMQ Artemis is a reliable messaging
broker
C:\Apache\apache-artemis-2.0.0\bin\broker\log
roll
%JAVA_HOME%\bin\java.exe
-Xbootclasspath/a:%ARTE
I think the simplest way is to set it on the URL, e.g.:
ServerLocator locator =
ActiveMQClient.createServerLocator("vm://0?consumerWindowSize=1024);
ClientSessionFactory factory = locator.createSessionFactory();
ClientSession session = factory.createSession();
session.start();
ClientC
Hi,
How do I set the client prefetch when using the Artemis Core API? I've
seen examples of setting it in the URL when using the JMS API but couldn't
find anything that worked for the Core API.
I am creating my client consumer as so:
ServerLocator locator = ActiveMQClient.createServerLocatorWit
Tim how can I provide with more detailed logs? I can try and adjust broker side
to have more debugs but client is unlikely to extend its messages
Thx
Marcin
Od: "Timothy Bish"
Do: "users"
Wysłane: środa, 26 kwiecień 2017 22:16:34
Temat: Re: Occasionally EOF on connection
On 04/26/201
On 04/26/2017 04:00 PM, Tim Bain wrote:
Your right, a connection to localhost should be rock-solid. Sorry I missed
that.
Is there any possibility that a firewall (either OS or application) might
be interfering with your connections? I feel like I'm grasping at straws a
little bit, but I can't ex
Your right, a connection to localhost should be rock-solid. Sorry I missed
that.
Is there any possibility that a firewall (either OS or application) might
be interfering with your connections? I feel like I'm grasping at straws a
little bit, but I can't explain EOFs on both sides of the connection
Pluggable storage lockers (
http://activemq.apache.org/pluggable-storage-lockers.html) could let you
work around any issues with the locking behavior under this configuration.
The code for the current Oracle interface is at
https://github.com/apache/activemq/blob/master/activemq-jdbc-store/src/mai
Thanks Steve, good point.
In this standard Oracle RAC configuration the SCAN listener effectively
plays the role of load balancer. Active MQ connects to the database through
port 1610 and then is directed to node a or node b on port 1521.
I’ve found an Oracle DocID: How To Configure Server Side T
I have not used oracle rac but it sounds like active mq is tied to a single
instance rather than any available oracle server. Have you considered putting a
load balancer in front that can determine whether the back end is up and can
route requests appropriately? Not sure if this would work as n
I interpret that document to be written in the context of a requirement
that the broker not lose persistent messages in the event of a restart or
failover, since those are the requirements of most ActiveMQ users using a
persistence store. (Typically, either you need 100% persistence and you use
a p
ApacheCon is just three weeks away, in Miami, Florida, May 15th - 18th.
http://apachecon.com/
There's still time to register and attend. ApacheCon is the best place
to find out about tomorrow's software, today.
ApacheCon is the official convention of The Apache Software Foundation,
and includes t
My answer was based on ActiveMQ Artemis. Sorry for the confusion.
On Wed, Apr 26, 2017 at 1:56 PM, khandelwalanuj <
anuj.cool.khandel...@gmail.com> wrote:
> Yes I was talking about ActiveMQ 5.x
>
> Can you also clarify about the first point where it says that journaled
> JDBC
> store is incompat
Tim,
Thanks for the detailed reply. I will share with our app design/development
team for more in-depth discussion and post back with status on any
workarounds or coding we come up with.
Also, may consider entering a feature request as you suggested. Agree it may
be a bigger update than team wan
Yes I was talking about ActiveMQ 5.x
Can you also clarify about the first point where it says that journaled JDBC
store is incompatible with the JDBC master/slave. What does it exactly mean
? Link which says this:
https://access.redhat.com/documentation/en-US/Fuse_Message_Broker/5.4/html/Clusterin
Auke,
Pooling your connections is definitely a good thing, but since you say that
the system still exhibits the performance slowdown, your next step is what
I said in my first response: to characterize which OS resource (CPU,
network, disk, memory) is the limiting one, and on which broker or clien
Anuj and Martyn, were your question and your answer about ActiveMQ 5.x or
Artemis? I think the question was about 5.x and Martyn's answer was about
Artemis. If so, see a 5.x response below.
I don't believe that there is any reason other than the potential for
message loss that you described (corre
Hi
On Wed, Apr 26, 2017 at 6:51 AM, khandelwalanuj <
anuj.cool.khandel...@gmail.com> wrote:
> Hi,
>
> I was evaluating ActiveMQ's JDBC based persistent store with journaling
> enabled. Have couple of doubts:
>
> 1. I was reading
> https://access.redhat.com/documentation/en-US/Fuse_
> Message_Brok
17 matches
Mail list logo
