mething is creating a network connection to your broker
>
> On 30 Jul 2009, at 18:58, GaryG wrote:
>
>>
>> Thank you for pointing that out! Since we only have one broker, I
>> disabled
>> the multicast discovery.
>>
>> Unfortunately, that didn
I just did another test - where I didn't have any clients connected to JMS -
just ran the server by itself.
Same problem. It restarted even though no message were coming across.
So, definitely something causing the server to die.
GaryG wrote:
>
> On the client side, i&#x
sageProducer mp = .
mp.send(msg);
I'm still stumped...
GaryG wrote:
>
> Thank you for pointing that out! Since we only have one broker, I
> disabled the multicast discovery.
>
> Unfortunately, that didn't fix the problem. The restarts are still
> happening. Sometim
command to the
process, but I have no idea what that could be.
_Gary
rajdavies wrote:
>
> first - try disabling multicast discovery in the activemq configuration
>
> On 29 Jul 2009, at 22:17, GaryG wrote:
>
>>
>> We've recently updated to ActiveMQ 5.2.0, and are ru
We've recently updated to ActiveMQ 5.2.0, and are running it as a standalone
server, with a config file very similar to the basic example provided out of
the box. There has been no code change in the Java code that talks to the
AMQ server. Yet, once started up, the ActiveMQ server process is res
When you say "client" are you talking about the client connection should
automatically send keep-alive pings, or is this something our code has to do
manually?
James.Strachan wrote:
>
> Note that the ActiveMQ client should send keep-alive pings to keep
> connections alive if a JMS connection
I'm seeing tons of exceptions on the broker:
2007-02-23 07:15:48,528 [xxsxxx:61616] ERROR TransportConnector
- Could not accept connection : java.net.SocketException: Too many open
files
java.net.SocketException: Too many open files
at java.net.PlainSocketImpl.soc
Last night after it died again, I changed the usageMemory manager settings to
256 MB. It's been up the whole night. For completeness sake, here's the
Java process that's running:
/usr/java/jdk/bin/java -Xmx512M
-Dorg.apache.activemq.UseDedicatedTaskRunner=true
-Dderby.system.home=/opt/activemq-
AMQ Broker is down again. Same situation. However, running "jstack" on the
PID doesn't work, it hangs connecting to the process.
So, I opened up the JMX console, and am providing you some of stats that
looked interesting.
My main questions regarding this output are:
1) Why does Broker memory
I was wondering if anyone knows of consultants (consulting companies) that
might specialize in ActiveMQ services. I'd like to have the info handy if
we ever need to bring someone in to help us solve issues and tune.
Thanks.
--
View this message in context:
http://www.nabble.com/ActiveMQ-consu
Chris, in this specific case we're using Topics, not Queues, but I've seen
the same issue happen for Queues. Next time it "hangs" I'll get a stack
dump and post it. Should be sometime this evening (I've not seen it run
reliably for more then 8 hours)
Thank you.
_Gary
Christopher G. Stach II
logging for actual messages flowing
across...Can someone provide me an example log4j file that might show more
logs and maybe show some exceptions on the broker that i'm not seeing??
Any suggestions are appreciated!
Thanks,
Gary
GaryG wrote:
>
> I have not looked at the JMX stats.
l the client due to inactivity
> (but maybe the client hasn't noticed yet)
>
> On 2/21/07, GaryG <[EMAIL PROTECTED]> wrote:
>>
>> I'm having a problem with regular, non-persistent topics not getting
>> messages
>> they're sent.
>>
>> The
I'm having a problem with regular, non-persistent topics not getting messages
they're sent.
The setup we have works for a while with no problem, but after a while
(today after 5 hours), one particular topic receiver stops getting any
messages. I can clearly see in my sender's logs that messages
quot;nohup /opt/activemq-4.1.0/bin/activemq > /dev/null &"
Perhaps that should be put in your documentation as the only way to make
sure the broker can be ran from command line as a background process without
dying.
Christopher G. Stach II wrote:
>
> GaryG wrote:
>> 1.
1. Is JSW enabled by default in AMQ? Like I said, I don't see it running.
2. I'll try JVM 1.5.0_09
3. By turning on the logging, are you talking about log4j for the AMQ?
I've already got it set to debug, what other debug options do you need
turned on?
Also, it seems that when I run the bro
02:58:43,680 [eckpoint Worker] DEBUG JDBCPersistenceAdapter
- Cleaning up old messages.
2007-02-20 02:58:43,680 [eckpoint Worker] DEBUG DefaultJDBCAdapter
- Executing SQL: DELETE FROM ACTIVEMQ_MSGS WHERE ( EXPIRATION<>0 AND
EXPIRATION
> On 2/20/07, GaryG <[EMAIL
Exception occured. Server is down.
--
James.Strachan wrote:
>
> On 2/20/07, GaryG <[EMAIL PROTECTED]> wrote:
>>
>> I am not using a Java Service Wrapper. Not sure what that is.
>>
>> Broker just died again last night.
>>
>> I am using the
xed
them by disabling the shutdown hook)
Does the broker HAVE to be used as "embedded" in a java process to keep it
from dying?
Christopher G. Stach II wrote:
>
> GaryG wrote:
>> I'm having a problem with my Broker shutting down for no reason.
>>
>> I&
I'm having a problem with my Broker shutting down for no reason.
I'm running it with mostly default configuration from command line:
/opt/activemq-4.1.0/bin/activemq > /dev/null &
My config file sets up the broker with Derby persistence adapter.
http://activemq.org/config/1.0";>
Here are th
I still can't get this working. Setting the sequence id to 0 doesn't do
anything. In fact, when i sent N number of messages to a variety of message
groups, and print out the ==msg.getStringProperty("JMSXGroupSeq")==
what prints is always 0. Is there a configuration option i don't know about
to
James.Strachan wrote:
>
>> Does this mean that MessageGroups only work when there's only one broker,
>> and don't work in Master-Slave broker configuration??
>
> They work with a single broker or with Master-Slave. But they don't
> work with networks of brokers.
>
>
Then what am I doing wro
hey
continue going to one of the other guys.
So the question is...if one of the consumers dies, and then comes back
(common scenario), how do I get the broker to forward messages to him once
again??
Thanks again for the help!
-GaryG
--
View this message in context:
http://www.nabble.co
[backfilling some messages]
GaryG wrote:
>
>
> On 2/5/07, Givental, Gary wrote:
>> Ah yes, I should have clarified that :)
>>
>> The nature of the applications makes that impossible. We need to
>> ensure that A) all the tasks are processed in sequential ord
[backfilling some messages]
> James,
>
> I appreciate your help on this.
>
> To clarify, here's the gist of what I'm trying to accomplish:
>
> Essentially it is a worker farm that is controlled via a single master
> controller. There are some Topics on which status information is
> published b
t;invoked purge command on Q = " + qName);
-
James.Strachan wrote:
>
> Persistence v non persistence only applies to what happens to messages
> if you reboot the broker; otherwise the semantics are pretty similar.
>
> If you don't want a message to be sent to consumers which are not
w the Topics work.
Maybe this means I should be using Topics in all cases?
Thanks for any help!
-GaryG
YoungSoul wrote:
>
> As far as I know - and someone please correct me if I am wrong...
>
> The NON_PERSISTENT has to do with whether or not the jms service provider
> ( activ
nd how it should work? I
understand the messages persisted to a DB for backup, how is that different
from journaling? If I want delivery assurance, even if a consumer is down,
do I have to turn on DeliveryMode.PERSISTENT on the producer, AND use a
DurableSubscriber on the consumer end?
I app
28 matches
Mail list logo
