Well atleast I am not the only one, I tried to implement timeToLive but it seems that
the only configuration refrence to timeToLive is for MDB. I have a normal JMS
Consumer listening for messages. I am running Jboss 3.2.5 with 4 - 7 different
topics and queues. After I turn on the trace log
Solution!!!
After going through all the logs and comparing them to the logs when the messages are
received, I noticed that the messages were expiring.
What is wierd is if I put any value between 1500ms and 15ms for timeToLive, the
messages will expire. The only value that works as of rig
My apologies for throwing a bunch of messages in here quite rapidly.
If I would have taken the time to read the README FIRST post at:
http://jboss.org/index.html?module=bb&op=viewtopic&t=43573
I would have found out how to turn on logging.
I still feel like this problem should be a lot easier to
A few last notes:
There is no firewall running on either windows or linux.
All my networking is setup correctly. I've also tried setting the ip address for the
JMSProviderLoader with the following line:
My jboss server is on the same subnet as the clients.
Thanks again.
View the original
A few last notes:
There is no firewall running on either windows or linux.
All my networking is setup correctly. I've also tried setting the ip address for the
JMSProviderLoader with the following line:
mbean code="org.jboss.jms.jndi.JMSProviderLoader"
name="jboss.mq:service=JMSProvid
Hello,
Has anyone made any progress with this issue? I am having the exact same problem.
I've been scouring the forums and documenation for any help with it.
I'm running JBoss version 4.0.0 on both linux and windows. My topics and queues all
work perfectly when all are running on a single ma
