I'm using 5.8.0
Mark
On 5/13/2013 8:29 PM, ceposta [via
ActiveMQ] wrote:
No, it's probably the same cost. But the cost is in
establishing the
underlying connection, not in creating the session. It just
happens that if
No, it's probably the same cost. But the cost is in establishing the
underlying connection, not in creating the session. It just happens that if
you haven't started the connection by the time you try to create the
session, creating the session will set up the underlying connection data
structures b
Well, what happens when you "create a connection" but
don't start it, it
will open the transport and start wire format negotiation... when
you do
connection.start().. or when you try to open a session, it will
ensure that
Nice investigation!
>
> In a well-tuned system/network, I would think that sending a
> 40-character text string to ActiveMQ would be nearly instantaneous
> from a human's perspective, right?
>
> Yes, it should be super fast.
> What I learned from this is that I can reduce the o
OK, here's some useful info... I used:
tcpdump tcp port 61616 and host dell7
I noticed that if I use:
?wireFormat.maxInactivityDurationInitialDelay=3
in my client to extend the timeout to 30 seconds instead of the
default 10 seconds, then my
Hi,
I am using activemq 5.7 running on Linux with JDK 1.6 for setting up a
shared file system master slave broker.
There are two activemq nodes which access a NFSV4 shared file system for
storage.
Initially , i can start one of the nodes as the master and it gets the
Kahadb lock. After this, i
Thanks! I'm studying up on tcpdump's man page now (about 30 pages
of technical details!). Wireshark isn't installed by default, so I
put in a request to have it installed on Tuesday. I won't be back
in until Thursday, so I'll resume my diagnostics then.
T
Thanks for posting your findings!!
On Mon, May 13, 2013 at 12:08 PM, hengyunabc wrote:
> OK, I have found the reason.
> ActiveMQ5.5.0 use spring 3.0.3 and camel 2.7.0,
> ActiveMQ5.8.0 use spring 3.1.3 and camel 2.10.3.
>
> In spring 3.0.3 and camel 2.7.0, default cache level is CACHE_CONSUMER.
You can use wireshark (or tcpdump) on the broker machine to see if the
client's WireFormatInfo is coming through and whether the broker is sending
one. Wireshark does have a built in activemq command codec so you can see
the command objects going through. You can also try things like ping or
tracer
OK, I have found the reason.
ActiveMQ5.5.0 use spring 3.0.3 and camel 2.7.0,
ActiveMQ5.8.0 use spring 3.1.3 and camel 2.10.3.
In spring 3.0.3 and camel 2.7.0, default cache level is CACHE_CONSUMER.
In spring 3.1.3 and camel 2.10.3, default cache level is CACHE_AUTO.
How the CACHE_AUTO works? See
I'm also suspecting it is a network issue, as I surmise you are by
the questions you ask. But my strength is programming, not
sysadmin. So I want to answer your questions, but don't know the
RedHat tricks or tools to determine the answers. Can you hold my
hand
Mark,
When the connection to the broker is first established, the wire format is
negotiated by each side sending it's preferred info. Looks like the client
is sending its info, but not getting anything back. Maybe take a thread
dump to see what's going on on the broker side... can you verify the cl
I'm getting the error shown in the Subject, not at first, but after ActiveMQ
has been working just fine for several hours. Then once it happens, all my
clients that interact with the broker reports this error. I've found this
page:
http://activemq.apache.org/javaxjmsjmsexception-wire-format-negoc
I just tried a build and seems source/javadoc are built fine in 5.9.
mvn clean install -Pdeploy -Dmaven.test.skip=true
eg, i can see
activemq-broker/target/activemq-broker-5.9-SNAPSHOT-javadoc.jar
activemq-broker/target/activemq-broker-5.9-SNAPSHOT-sources.jar
On Mon, May 13, 2013 at 1:43 AM,
I would have to plug it into Tim's test to know 100% for sure. But I would
start by disable audit on the DLQ (which doing so gives rise to the
possibility of dups), and since the same message with same message id will
be delivered to original queue, might have to disable audit on that too.
Give it
Thanks for posting your solution!
On Mon, May 13, 2013 at 5:44 AM, Michalis wrote:
> I tried JtdsDataSource and everything worked just fine!
>
> class="net.sourceforge.jtds.jdbcx.JtdsDataSource">
>
>
>
>
>
Paul, that is correct.
On Sun, May 12, 2013 at 7:01 PM, Paul Gale wrote:
> >I saw this document from here
> http://activemq.apache.org/jdbc-master-slave.html and i think in here they
> allow brokers to have more than 2.
> >Did i misunderstand what you mean?
>
> In master-slave you can have as m
Paul, I'll update the wiki tonight with your suggestions.
You asked earlier about:
"Can the following options also be used on a STOMP transport connector?
watchAdvisoryTopics, alwaysSessionAsync and dispatchAsync"
*Transport connectors* are a broker configuration, ie,
The options you asked abo
I tried JtdsDataSource and everything worked just fine!
--
View this message in context:
http://activemq.2283324.n4.nabble.com/SqlServer-Master-Slave-tp4666887p4666953.html
Sen
Hi,
I am using ActiveMQ 5.8, and getting problems with multicast. Before
posting it here for help, I was planning to do some debugging. Maybe it is
just an error on my side. But couldn't do any debugging, as I do not manage
to link the source code/javadoc of ActiveMQ...
I include ActiveMQ with M
20 matches
Mail list logo
