Hi:
I'm using AMQ 5.8.0 , on client server side.
Client side is a web application running on Tomcat 6 and its running ok
Connection transport is in failover mode
How is it possible a java.lang.NoClassDefFoundError:
org/apache/activemq/util/IOExceptionSupport exception if I didn't
restart Tomcat server ?
Any ideas ?
This sounds like you have a JAR / library conflict somewhere.
Specifically, the class that you mention (IOExceptionSupport) was moved
I am hard pressed to find much documentation on using/coding an embedded
broker. The single example that comes with the distribution instantiates a
Broker() object, but in the FAQ it is illustrated using a BrokerService()
object. I don't understand the difference.
In the end I need to configure
So I would suggest that you check your classpath for the ActiveMQ
dependencies and make sure that you don't have a 5.8 version lingering
somewhere.
Thanks Timothy
But I guess that isn't not the problem .
I've checked for other AMQ versions and there is not any more.
The problem happened
The journal files were cut down in size to avoid running into the issue, but
there is still potential to have a message on the DLQ that is a 'useful
artifact' which is in the journal, no?
context:property-placeholder system-properties-mode=OVERRIDE/-broker
Hey,
I want to read about ActiveMQ transactions in detail, I have already googled
it but found not much other than
http://activemq.apache.org/should-i-use-transactions.html
http://activemq.apache.org/how-do-transactions-work.html
So if there is some blog or any thing is there, please help me.
Hi!
We are having som issues with Virtual Topics running:
ActiveMQ 5.9.0, Camel 2.12.1, LevelDB.
No network of brokers, No replication.
Sending 1 of large messages to virtual topic is working perfectly.
But when starting to consume from the Virtual Topics-queues, the consumer
log starts to
most of that is covered in the jms spec documentation, it is standard.
Maybe post some specific questions or concerns with some sample code
and we can take if from there.
On 22 November 2013 13:54, Sophia Wright sophiawrigh...@gmail.com wrote:
Hey,
I want to read about ActiveMQ transactions
or you can be more selective, see:
http://activemq.apache.org/59-migration-guide.html
On 21 November 2013 18:33, Leonardo K. Shikida shik...@gmail.com wrote:
drop and recreate all JMS tables
[]
Leo
On Thu, Nov 21, 2013 at 12:34 PM, Leonardo K. Shikida
shik...@gmail.comwrote:
Hi
I
Right. It means that particular file that holds the message cannot be
deleted/archived.
On Fri, Nov 22, 2013 at 6:48 AM, barry.barn...@wellsfargo.com wrote:
If there is a 'useful' artificat in the journal which is 'tied' to a message
on the DLQ, that means the journal can't be cleared,
This question was asked a while ago and the answers involved links and APIs
that no longer exist. I am unable to find any documentation to figure out
what classes correspond to what xml options, and if one is able to guess at
the classes, how to link them to the broker.
In the binary
Apollo API != ActiveMQ 5.x API.
To create an embedded broker with ActiveMQ 5.x with SSL take a look at this:
https://github.com/apache/activemq/blob/trunk/activemq-amqp/src/test/java/org/apache/activemq/transport/amqp/AMQ4563Test.java#createBroker(...)
To create an embedded broker with Apollo
Okay but I have actually already started down that path (using the *DTO
classes). I just couldn't see how they were linked to the brokerDTO. But I
guess many of them are nested and that is why. (Unfortunately I tried the
SslDTO first which is nested so I didn't see the connection.) So I guess the
Yah, awesome! We love contributions.
On Fri, Nov 22, 2013 at 11:32 AM, Brian Reinhold
brianreinh...@lampreynetworks.com wrote:
Okay but I have actually already started down that path (using the *DTO
classes). I just couldn't see how they were linked to the brokerDTO. But I
guess many of them
The checkpoint worker (which is responsible for determining which data
log files should be removed) runs every 30 seconds.
One can learn a lot about how the data log purge is happening by
enabling its logger. See here for more details:
Ran failover test again and after about 25 or so fail overs I got the below
errors on the master. I did not see any other errors. I will try to run
with debug turned on next week to see it helps with debugging.
Note: even after this error i was able to do few more failover before things
stopped
You should probably try:
transportConnector name=openwire uri=tcp://1.2.3.4:61616
publishedAddressPolicy
publishedAddressPolicy publishedHostStrategy=IPADDRESS /
/publishedAddressPolicy
/transportConnector
--
View this message in context:
17 matches
Mail list logo
