You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@activemq.apache.org by GaryG <gg...@us.ibm.com> on 2007/02/21 04:16:21 UTC
Non-Persistent Topic not getting messages
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 are being
sent, but nothing is coming through. There are other topics in the system
that are configured exactly the same way that *are* getting messages.
There are no messages in the AMQ logs indicating any kind of disconnect.
The only difference I can see is that this particular topic is getting
ObjectMessage(s), while I've switched the others to "MapMessage(s)".
Is there an issue with sending across a large number of ObjectMessage(s) ??
It seems that whenever I've used that, after a while messages stop coming
through. This has happened a number of times now.
Thanks,
Gary
--
View this message in context: http://www.nabble.com/Non-Persistent-Topic-not-getting-messages-tf3264593s2354.html#a9074729
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: [Spam: 5.0] Non-Persistent Topic not getting messages
Posted by James Strachan <ja...@gmail.com>.
On 2/23/07, GaryG <gg...@us.ibm.com> wrote:
>
> 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?
Sorry I mean that the internals of the ActiveMQ JMS Client should do
the keep-alive stuff
--
James
-------
http://radio.weblogs.com/0112098/
Re: [Spam: 5.0] Non-Persistent Topic not getting messages
Posted by GaryG <gg...@us.ibm.com>.
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 isn't doing much
>
--
View this message in context: http://www.nabble.com/Non-Persistent-Topic-not-getting-messages-tf3264593s2354.html#a9122086
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: Non-Persistent Topic not getting messages
Posted by James Strachan <ja...@gmail.com>.
On 2/21/07, GaryG <gg...@us.ibm.com> wrote:
>
> I have not looked at the JMX stats. For whatever reason, I haven't been able
> to connect remotely to the broker.
>
> Aside from that...Why would a broker kill clients due to inactivity?
Some OSes/platforms don't detect a socket death for hours or days; so
inactivity timeouts allow the broker to be more aggressive closing
dead connections faster.
> Can
> this be configured/turned off?
>
Of course :) ActiveMQ is completely configurable
http://activemq.apache.org/configuring-wire-formats.html
> In our case, the producers of messages to this topic are sending messages
> every minute, and I had 4 of them going, so there was plenty of activity.
Note that the ActiveMQ client should send keep-alive pings to keep
connections alive if a JMS connection isn't doing much
--
James
-------
http://radio.weblogs.com/0112098/
Re: Non-Persistent Topic not getting messages
Posted by GaryG <gg...@us.ibm.com>.
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-4.1.0/data
-Dderby.storage.fileSyncTransactionLog=true -Dcom.sun.management.jmxremote
-Djavax.net.ssl.keyStorePassword=password
-Djavax.net.ssl.trustStorePassword=password
-Djavax.net.ssl.keyStore=/opt/activemq-4.1.0/conf/broker.ks
-Djavax.net.ssl.trustStore=/opt/activemq-4.1.0/conf/broker.ts -classpath
-Dactivemq.home=/opt/activemq-4.1.0 -Dactivemq.base=/opt/activemq-4.1.0 -jar
/opt/activemq-4.1.0/bin/run.jar
you can see it's 512MB for heap, and that's reflected in JMX as well.
Current the broker memory in JMX shows max at 256MB as specified, and memory
usage is 19%, up from 3% when it started out.
I'm still concerned that this is just going to continue climbing...it seems
like memory's not being released somewhere! We're not using persistent
messages, so I can understand that more memory is being used for journaling.
But shouldn't this be getting GCed???
I'd be a real pain to have to monitor the memory use via JMX for the broker,
and have to restart the broker every 24hours.
Christopher G. Stach II wrote:
>
>
> There's an issue open for the waitForSpace issue. I'm not sure if it
> applies to your situation. Anyway, you may want to look into the
> usageManager settings in the broker configuration to set the limit
> higher. A 20MiB default seems weird. I didn't think that there was a
> default.
>
> --
> Christopher G. Stach II
>
>
>
--
View this message in context: http://www.nabble.com/Non-Persistent-Topic-not-getting-messages-tf3264593s2354.html#a9099799
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: Non-Persistent Topic not getting messages
Posted by "Christopher G. Stach II" <cg...@ldsys.net>.
GaryG wrote:
> 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 limit seem to be 20 MB, when the Broker java
> process is explicitly started with 512MB. I thought this was the setting by
> default? Am I missing something? Should there be some explicit option set
> in the activemq.xml to set the memory limit much higher?
>
> 2) Why is there a mismatch between JMS summary output for memory and this
> obscure tab for the Broker specifically? Are they not the same thing?
>
> =========
>
> JMX
> ----
>
> Live Threads
> ============
>
> main
> --------------
> Name: main
> State: WAITING on [Z@16e3762
> Total blocked: 33 Total waited: 5
>
> Stack trace:
> java.lang.Object.wait(Native Method)
> java.lang.Object.wait(Object.java:474)
> org.apache.activemq.console.command.StartCommand.waitForShutdown(StartCommand.java:107)
> org.apache.activemq.console.command.StartCommand.runTask(StartCommand.java:68)
> org.apache.activemq.console.command.AbstractCommand.execute(AbstractCommand.java:50)
> org.apache.activemq.console.command.ShellCommand.runTask(ShellCommand.java:82)
> org.apache.activemq.console.command.AbstractCommand.execute(AbstractCommand.java:50)
> org.apache.activemq.console.command.ShellCommand.main(ShellCommand.java:46)
> sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> java.lang.reflect.Method.invoke(Method.java:585)
> org.apache.activemq.console.Main.runTaskClass(Main.java:159)
> org.apache.activemq.console.Main.main(Main.java:91)
> -------------------
>
> Name: ActiveMQ Transport Server: tcp://atla-dev-aic2.mss.iss.net:61616
> State: RUNNABLE
> Total blocked: 2 Total waited: 6
>
> Stack trace:
> java.net.PlainSocketImpl.socketAccept(Native Method)
> java.net.PlainSocketImpl.accept(PlainSocketImpl.java:384)
> java.net.ServerSocket.implAccept(ServerSocket.java:450)
> java.net.ServerSocket.accept(ServerSocket.java:421)
> org.apache.activemq.transport.tcp.TcpTransportServer.run(TcpTransportServer.java:153)
> java.lang.Thread.run(Thread.java:595)
>
> ------------------
> ALL the transports look like this(ip obscured). Looks like they're all out
> of memory.
> Either RAM or DISK???
>
> Name: ActiveMQ Transport: tcp:///xxxxxxxxx:60230
> State: WAITING on java.lang.Object@7834eb
> Total blocked: 24 Total waited: 1
>
> Stack trace:
> java.lang.Object.wait(Native Method)
> java.lang.Object.wait(Object.java:474)
> org.apache.activemq.memory.UsageManager.waitForSpace(UsageManager.java:91)
> org.apache.activemq.memory.UsageManager.waitForSpace(UsageManager.java:88)
> org.apache.activemq.broker.region.Topic.send(Topic.java:239)
> org.apache.activemq.broker.region.AbstractRegion.send(AbstractRegion.java:292)
> org.apache.activemq.broker.region.RegionBroker.send(RegionBroker.java:380)
> org.apache.activemq.broker.TransactionBroker.send(TransactionBroker.java:193)
> org.apache.activemq.broker.BrokerFilter.send(BrokerFilter.java:126)
> org.apache.activemq.broker.CompositeDestinationBroker.send(CompositeDestinationBroker.java:98)
> org.apache.activemq.broker.MutableBrokerFilter.send(MutableBrokerFilter.java:136)
> org.apache.activemq.broker.TransportConnection.processMessage(TransportConnection.java:480)
> org.apache.activemq.command.ActiveMQMessage.visit(ActiveMQMessage.java:604)
> org.apache.activemq.broker.TransportConnection.service(TransportConnection.java:284)
> org.apache.activemq.broker.TransportConnection$1.onCommand(TransportConnection.java:177)
> org.apache.activemq.transport.TransportFilter.onCommand(TransportFilter.java:65)
> org.apache.activemq.transport.WireFormatNegotiator.onCommand(WireFormatNegotiator.java:133)
> org.apache.activemq.transport.InactivityMonitor.onCommand(InactivityMonitor.java:122)
> org.apache.activemq.transport.TransportSupport.doConsume(TransportSupport.java:84)
> org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:137)
> java.lang.Thread.run(Thread.java:595)
>
> ---------------------------
>
> JMX Summary:
>
> Memory
> Current heap size:
> 15,134 kbytes
> Committed memory:
> 25,088 kbytes
> Maximum heap size:
> 504,896 kbytes
> Objects pending for finalization:
> 0
> Garbage collector:
> Name = 'PS MarkSweep', Collections = 359, Total time spent = 33.082 seconds
> Garbage collector:
> Name = 'PS Scavenge', Collections = 50, Total time spent = 0.121 seconds
>
> =========================
>
> In JMX Consoler, clicking on MBeans tab, then selecting:
> org.apache.activemq -->amqDev2 --> Broker
>
> Under Attributes tab, the MemoryLimit is 20 MB, even though the java process
> for AMQ was started with 512MB.
> The memory % used says 100%.
>
> But this doesn't match the Summary Memory stats. What is this limit?
>
There's an issue open for the waitForSpace issue. I'm not sure if it
applies to your situation. Anyway, you may want to look into the
usageManager settings in the broker configuration to set the limit
higher. A 20MiB default seems weird. I didn't think that there was a
default.
--
Christopher G. Stach II
Re: Non-Persistent Topic not getting messages
Posted by GaryG <gg...@us.ibm.com>.
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 limit seem to be 20 MB, when the Broker java
process is explicitly started with 512MB. I thought this was the setting by
default? Am I missing something? Should there be some explicit option set
in the activemq.xml to set the memory limit much higher?
2) Why is there a mismatch between JMS summary output for memory and this
obscure tab for the Broker specifically? Are they not the same thing?
=========
JMX
----
Live Threads
============
main
--------------
Name: main
State: WAITING on [Z@16e3762
Total blocked: 33 Total waited: 5
Stack trace:
java.lang.Object.wait(Native Method)
java.lang.Object.wait(Object.java:474)
org.apache.activemq.console.command.StartCommand.waitForShutdown(StartCommand.java:107)
org.apache.activemq.console.command.StartCommand.runTask(StartCommand.java:68)
org.apache.activemq.console.command.AbstractCommand.execute(AbstractCommand.java:50)
org.apache.activemq.console.command.ShellCommand.runTask(ShellCommand.java:82)
org.apache.activemq.console.command.AbstractCommand.execute(AbstractCommand.java:50)
org.apache.activemq.console.command.ShellCommand.main(ShellCommand.java:46)
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
java.lang.reflect.Method.invoke(Method.java:585)
org.apache.activemq.console.Main.runTaskClass(Main.java:159)
org.apache.activemq.console.Main.main(Main.java:91)
-------------------
Name: ActiveMQ Transport Server: tcp://atla-dev-aic2.mss.iss.net:61616
State: RUNNABLE
Total blocked: 2 Total waited: 6
Stack trace:
java.net.PlainSocketImpl.socketAccept(Native Method)
java.net.PlainSocketImpl.accept(PlainSocketImpl.java:384)
java.net.ServerSocket.implAccept(ServerSocket.java:450)
java.net.ServerSocket.accept(ServerSocket.java:421)
org.apache.activemq.transport.tcp.TcpTransportServer.run(TcpTransportServer.java:153)
java.lang.Thread.run(Thread.java:595)
------------------
ALL the transports look like this(ip obscured). Looks like they're all out
of memory.
Either RAM or DISK???
Name: ActiveMQ Transport: tcp:///xxxxxxxxx:60230
State: WAITING on java.lang.Object@7834eb
Total blocked: 24 Total waited: 1
Stack trace:
java.lang.Object.wait(Native Method)
java.lang.Object.wait(Object.java:474)
org.apache.activemq.memory.UsageManager.waitForSpace(UsageManager.java:91)
org.apache.activemq.memory.UsageManager.waitForSpace(UsageManager.java:88)
org.apache.activemq.broker.region.Topic.send(Topic.java:239)
org.apache.activemq.broker.region.AbstractRegion.send(AbstractRegion.java:292)
org.apache.activemq.broker.region.RegionBroker.send(RegionBroker.java:380)
org.apache.activemq.broker.TransactionBroker.send(TransactionBroker.java:193)
org.apache.activemq.broker.BrokerFilter.send(BrokerFilter.java:126)
org.apache.activemq.broker.CompositeDestinationBroker.send(CompositeDestinationBroker.java:98)
org.apache.activemq.broker.MutableBrokerFilter.send(MutableBrokerFilter.java:136)
org.apache.activemq.broker.TransportConnection.processMessage(TransportConnection.java:480)
org.apache.activemq.command.ActiveMQMessage.visit(ActiveMQMessage.java:604)
org.apache.activemq.broker.TransportConnection.service(TransportConnection.java:284)
org.apache.activemq.broker.TransportConnection$1.onCommand(TransportConnection.java:177)
org.apache.activemq.transport.TransportFilter.onCommand(TransportFilter.java:65)
org.apache.activemq.transport.WireFormatNegotiator.onCommand(WireFormatNegotiator.java:133)
org.apache.activemq.transport.InactivityMonitor.onCommand(InactivityMonitor.java:122)
org.apache.activemq.transport.TransportSupport.doConsume(TransportSupport.java:84)
org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:137)
java.lang.Thread.run(Thread.java:595)
---------------------------
JMX Summary:
Memory
Current heap size:
15,134 kbytes
Committed memory:
25,088 kbytes
Maximum heap size:
504,896 kbytes
Objects pending for finalization:
0
Garbage collector:
Name = 'PS MarkSweep', Collections = 359, Total time spent = 33.082 seconds
Garbage collector:
Name = 'PS Scavenge', Collections = 50, Total time spent = 0.121 seconds
=========================
In JMX Consoler, clicking on MBeans tab, then selecting:
org.apache.activemq -->amqDev2 --> Broker
Under Attributes tab, the MemoryLimit is 20 MB, even though the java process
for AMQ was started with 512MB.
The memory % used says 100%.
But this doesn't match the Summary Memory stats. What is this limit?
--
View this message in context: http://www.nabble.com/Non-Persistent-Topic-not-getting-messages-tf3264593s2354.html#a9093767
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: Non-Persistent Topic not getting messages
Posted by GaryG <gg...@us.ibm.com>.
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 wrote:
>
>
> We currently have some issues where queues stop delivering. Can you
> generate a stack dump when it's hung?
>
> --
> Christopher G. Stach II
>
>
>
--
View this message in context: http://www.nabble.com/Non-Persistent-Topic-not-getting-messages-tf3264593s2354.html#a9089996
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: Non-Persistent Topic not getting messages
Posted by "Christopher G. Stach II" <cg...@ldsys.net>.
GaryG wrote:
> I've got the JMX running. Again the architecture ran fine for about 3 hours,
> then all my topics seemed to stop receiving messages.
>
> So, here's the situation:
>
> 1) the producers ARE sending messages and there are no exception from AMQ
> API when they're sent.
> 2) AMQ Broker is up, and amq logs indicate no exceptions, or any consumers
> disconnected
> 3) JMX console shows all the expected consumers/producers connected on all
> the Topics that I expect to be there. The topics all show status "Active".
> THere is no indication of any error. Browsing messages for some of these
> topics, I do see some messages, and they are all prior to when the messages
> stopped going across.
>
> 4) Restarting the broker, seems to fix the problem - everyone reconnects
> (from code I wrote), and messages are flowing across again. However, this
> has not been consistent. As I pointed out in previous posts, sometimes even
> doing a broker restart does NOT solve the problem. I've had at least 2
> occurances now where after AMQ broker restart, some topics would start
> getting messages again, but not others, and it took multiple restarts to get
> things going again.
>
> Is anyone aware of what kind of failure conditions might cause this scenario
> to happen? Is there any way to tell when it happens? Are there exceptions
> that might not be getting back to producers/consumers?
>
> In AMQ log4j settings, i followed the instructions and set the logging level
> to DEBUG. but I still don't see 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!
We currently have some issues where queues stop delivering. Can you
generate a stack dump when it's hung?
--
Christopher G. Stach II
Re: Non-Persistent Topic not getting messages
Posted by GaryG <gg...@us.ibm.com>.
I've got the JMX running. Again the architecture ran fine for about 3 hours,
then all my topics seemed to stop receiving messages.
So, here's the situation:
1) the producers ARE sending messages and there are no exception from AMQ
API when they're sent.
2) AMQ Broker is up, and amq logs indicate no exceptions, or any consumers
disconnected
3) JMX console shows all the expected consumers/producers connected on all
the Topics that I expect to be there. The topics all show status "Active".
THere is no indication of any error. Browsing messages for some of these
topics, I do see some messages, and they are all prior to when the messages
stopped going across.
4) Restarting the broker, seems to fix the problem - everyone reconnects
(from code I wrote), and messages are flowing across again. However, this
has not been consistent. As I pointed out in previous posts, sometimes even
doing a broker restart does NOT solve the problem. I've had at least 2
occurances now where after AMQ broker restart, some topics would start
getting messages again, but not others, and it took multiple restarts to get
things going again.
Is anyone aware of what kind of failure conditions might cause this scenario
to happen? Is there any way to tell when it happens? Are there exceptions
that might not be getting back to producers/consumers?
In AMQ log4j settings, i followed the instructions and set the logging level
to DEBUG. but I still don't see 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. For whatever reason, I haven't been
> able to connect remotely to the broker.
>
> Aside from that...Why would a broker kill clients due to inactivity? Can
> this be configured/turned off?
>
> In our case, the producers of messages to this topic are sending messages
> every minute, and I had 4 of them going, so there was plenty of activity.
> Its the consumer for that topic that was not seeing any messages.
>
>
> James.Strachan wrote:
>>
>> There's no real difference with message types. What do the JMX stats
>> show in JConsole? Did the broker kill the client due to inactivity
>> (but maybe the client hasn't noticed yet)
>>
>> On 2/21/07, GaryG <gg...@us.ibm.com> wrote:
>>>
>>> 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 are being
>>> sent, but nothing is coming through. There are other topics in the
>>> system
>>> that are configured exactly the same way that *are* getting messages.
>>>
>>> There are no messages in the AMQ logs indicating any kind of disconnect.
>>>
>>> The only difference I can see is that this particular topic is getting
>>> ObjectMessage(s), while I've switched the others to "MapMessage(s)".
>>>
>>> Is there an issue with sending across a large number of ObjectMessage(s)
>>> ??
>>> It seems that whenever I've used that, after a while messages stop
>>> coming
>>> through. This has happened a number of times now.
>>>
>>> Thanks,
>>> Gary
>>> --
>>> View this message in context:
>>> http://www.nabble.com/Non-Persistent-Topic-not-getting-messages-tf3264593s2354.html#a9074729
>>> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>>>
>>>
>>
>>
>> --
>>
>> James
>> -------
>> http://radio.weblogs.com/0112098/
>>
>>
>
>
--
View this message in context: http://www.nabble.com/Non-Persistent-Topic-not-getting-messages-tf3264593s2354.html#a9089713
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: Non-Persistent Topic not getting messages
Posted by GaryG <gg...@us.ibm.com>.
I have not looked at the JMX stats. For whatever reason, I haven't been able
to connect remotely to the broker.
Aside from that...Why would a broker kill clients due to inactivity? Can
this be configured/turned off?
In our case, the producers of messages to this topic are sending messages
every minute, and I had 4 of them going, so there was plenty of activity.
Its the consumer for that topic that was not seeing any messages.
James.Strachan wrote:
>
> There's no real difference with message types. What do the JMX stats
> show in JConsole? Did the broker kill the client due to inactivity
> (but maybe the client hasn't noticed yet)
>
> On 2/21/07, GaryG <gg...@us.ibm.com> wrote:
>>
>> 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 are being
>> sent, but nothing is coming through. There are other topics in the
>> system
>> that are configured exactly the same way that *are* getting messages.
>>
>> There are no messages in the AMQ logs indicating any kind of disconnect.
>>
>> The only difference I can see is that this particular topic is getting
>> ObjectMessage(s), while I've switched the others to "MapMessage(s)".
>>
>> Is there an issue with sending across a large number of ObjectMessage(s)
>> ??
>> It seems that whenever I've used that, after a while messages stop coming
>> through. This has happened a number of times now.
>>
>> Thanks,
>> Gary
>> --
>> View this message in context:
>> http://www.nabble.com/Non-Persistent-Topic-not-getting-messages-tf3264593s2354.html#a9074729
>> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>>
>>
>
>
> --
>
> James
> -------
> http://radio.weblogs.com/0112098/
>
>
--
View this message in context: http://www.nabble.com/Non-Persistent-Topic-not-getting-messages-tf3264593s2354.html#a9082675
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: Non-Persistent Topic not getting messages
Posted by James Strachan <ja...@gmail.com>.
There's no real difference with message types. What do the JMX stats
show in JConsole? Did the broker kill the client due to inactivity
(but maybe the client hasn't noticed yet)
On 2/21/07, GaryG <gg...@us.ibm.com> wrote:
>
> 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 are being
> sent, but nothing is coming through. There are other topics in the system
> that are configured exactly the same way that *are* getting messages.
>
> There are no messages in the AMQ logs indicating any kind of disconnect.
>
> The only difference I can see is that this particular topic is getting
> ObjectMessage(s), while I've switched the others to "MapMessage(s)".
>
> Is there an issue with sending across a large number of ObjectMessage(s) ??
> It seems that whenever I've used that, after a while messages stop coming
> through. This has happened a number of times now.
>
> Thanks,
> Gary
> --
> View this message in context: http://www.nabble.com/Non-Persistent-Topic-not-getting-messages-tf3264593s2354.html#a9074729
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
>
--
James
-------
http://radio.weblogs.com/0112098/